Kubuntu Forums - Miscellaneous

What is the project's philosophy with regard to vulnerability management?

gordonmessmer — Sat, 18 Jul 2026 19:52:03 GMT

I'm working on a conference talk in which I will discuss the trade-offs inherent to long term releases.

Specifically: distributing software for a longer period than it is maintained upstream is very labor intensive, and different long-term systems approach the problem in different ways. RHEL starts with Fedora but removes ~90% of the packages and features in order to reduce the labor costs over the life of a release. Ubuntu similarly starts with Debian but splits repositories into a small "main" repo component that they promise to maintain and a large "universe" component that they document as merely a snapshot for which they do not promise any updates. Debian is probably effectively similar to Ubuntu, but they don't divide their repo the same way so it's hard to make any clear statements about user expectation of patch coverage over the distribution.

I am curious about how the maintainers of systems derived from Ubuntu LTS releases think about security risks and patch coverage.

Are there any packages in "universe" that are used in a default installation of your desktop? Do you monitor those packages for new CVEs?

Are there any packages in "universe" that you patch because your users would otherwise be at risk? Do you update those packages by backporting patches or by rebasing to new upstream releases?

Do you provide guidance to users about the packages they install from the Ubuntu "universe" repo collection using apt?

Do you recommend using software sources like Flatpak or Snap to give users access to application releases that are maintained and get security patches?

Is there anything else that you want users to know about your approach to vulnerability remediation or related security topics?

If this is not the best place to ask a question of the maintainers, where should I ask?

no more discover

die.boer — Mon, 13 Jul 2026 17:24:07 GMT

so this is my new way off updating everything in terminal

Code:

sudo nala update && sudo nala full-upgrade && sudo snap refresh && [ -f /var/run/reboot-required ] && echo ">>> Reboot recommended <<<"

thoughts maybe ?

[SOLVED]Is this Krusader? What changed?

Qqmike — Sun, 12 Jul 2026 19:33:05 GMT

Catchy subject title, huh?

Been awhile since I've used Krusader. Used to use it a few years ago a lot for accessing and modifying files as root, like /boot/efi.
So, today, I installed krusader through Synaptic.
Opened it. And all I see is a menu of icons at the top. Back Up Home Select All Reload Text File etc. etc > >
Nothing about "Tools" (>run as root), or anything like that.
I've tried several things to get at it, like
-- rt-click show hidden menu (or whatever) -- this is not working;
-- edited the .config file krusaderrc for menubar=enabled (it had said "disabled");
-- configure the main toolbar -- there was nothing like Tools or Start as Root etc.

Is this a "full version" of Krusader? or what am I missing here? or do I need to put this down for awhile and come back to it?

BTW, in K 22.04 here.

Kubuntu user causes monitor to display at wrong resolution-- for just one user only.

taxpayer — Sat, 11 Jul 2026 17:48:03 GMT

This morning I discovered that my screen appears to be set for the wrong resolution and displays everything larger than it should be. I assumed that this was due to a setting on the monitor, but eventually determined that both the monitor and kubuntu (display configuration) are set for 2560X1440. Eventually I tried setting up a second user, and was surprised to find that the problem was solved; for this new user everything displays properly.
So something is wrong with the settings for my initial user but OK for the new user. Where might I look to figure this out?

Trying to reduce dmesg btrfs spamming to reduce SSD wear - and now what?

oshunluvr — Mon, 29 Jun 2026 20:32:04 GMT

So I got tired of a set of dmesg entries filling up my logs, specifically these two:

Code:

[Mon Jun 29 02:16:11 2026] ata11.00: Enabling discard_zeroes_data
[Mon Jun 29 02:16:11 2026] ata12.00: Enabling discard_zeroes_data

and a couple more related to them. This is a 24/7 server so logging goes on continually so I thought I might get a few mores years out of the root storage device if I log less.

Some internet sleuthing and my own observations led me to this conclusion: The drives attached to ata11+12 are older (as in a decade) SSD's and both were btrfs formatted without a partition table. This was the source of the message - letting me know that the drives were able to support trim (discard) correctly. The newer SSDs don't do this nor do the HDs. So I reformatted both SSDs with a partition table and a single partition and those messages are gone.

UFW logs a lot but it's set to "low" and I want some logging from it so I guess I live with those (15-60 a day). However, one of my Roku TVs is causing these messages! Hopeully this will fix this one:

Code:

sudo ufw allow from 192.168.1.15

and I set it's IP the fixed address.

Finally, I'm seeing - about every 30 minutes - this:

Code:

sdb: sdb1 sdb2 sdb3 sdb4

Sort of an announcement of the partitions on this hard drive It's not even mounted. Still working on that one...