Is it stable enough to be a daily driver? It looks like a rolling release distro with daily dev builds.

Has anyone attempted to use it as a daily driver? What's your experience like? Do you wake up to a system with new bugs or broken features due to an overnight update/upgrade?

I'm running KDE Neon.

I have a problem where some time at least a few hours (but usually less than 24) after rebooting I can't drag/drop icons on the desktop anymore. The whole plasma shell just freezes.

I have traced this down to xdg-document-portal. Something is running this program as root (not sure what) and it is fuse mounting /run/user/1000/doc as root which means that the user processes can't use it at all.

Anyone know how to stop this or figure out what is spawning it as root?

myself     41500  0.1  0.0 888828  7168 ?        Ssl  16:35   0:00  \_ /usr/libexec/xdg-document-portal
root        8515  0.0  0.1 481216 16584 ?        Sl   Jan27   0:00 /usr/libexec/xdg-desktop-portal

ls shows:

d?????????  ? ?     ?       ?            ? doc

sudo ls:

dr-x------  2 root  root    0 Dec 31  1969 doc

And mount shows:

portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=0,group_id=0)

Shutting down (sudo kill -2) the root xdg-document-portal process fixes the problem. But I would like to know what is causing it and how to fix it permanently. Obviously a root process shouldn't be mounting things with those kinds of perms into /run/user/1000.... right?

I do have flatpak installed, but this happens even if I don't (consciously) run any flatpak applications. I suppose its possible something is running a flatpak in the background...?

Unable to update due to getting an error and then stops.

unpacking:  plasma-discover (6.2.5-0zneon+24.04+noble+release+build18) over (6.2.5-0zneon+24.04+noble+release+build13)
dpkg: error processing archive /var/cache/apt/archives/plasma-discover_6.2.5-0zneon+24.04+noble+release+build18_amd64.deb (--unpack):
trying to overwrite '/usr/share/icons/hicolor/128x128/apps/plasmadiscover.png', which is also in package plasma-discover-common 6.2.5-0zneon+24.04+noble+release+build13
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/plasma-discover_6.2.5-0zneon+24.04+noble+release+build18_amd64.deb

Error: Installation has failed.
If you'd like to file a bug report please include '/var/log/nala/dpkg-debug.log'

Error: error processing archive /var/cache/apt/archives/plasma-discover_6.2.5-0zneon+24.04+noble+release+build18_amd64.deb (--unpack):

Error: error processing archive /var/cache/apt/archives/plasma-discover_6.2.5-0zneon+24.04+noble+release+build18_amd64.deb (--unpack):
trying to overwrite '/usr/share/icons/hicolor/128x128/apps/plasmadiscover.png', which is also in package plasma-discover-common 6.2.5-0zneon+24.04+noble+release+build13
trying to overwrite '/usr/share/icons/hicolor/128x128/apps/plasmadiscover.png', which is also in package plasma-discover-common 6.2.5-0zneon+24.04+noble+release+build13

Errors were encountered while processing:
/var/cache/apt/archives/plasma-discover_6.2.5-0zneon+24.04+noble+release+build18_amd64.deb

Have tried sudo apt --fix-broken install with no help.

Any suggestions?

I want to update kdeneon with all updates to 6.12.10 LTS but I can't find the debs for kernel image, headers, or modules.

What's the link to find these debs (or use apt?)

I have a Beelink SER9 Mini PC with AMD Ryzen AI 9 HX 370 CPU and 890m GPU, running KDE Neon latest witth all available updates, 6.10.14-061014-generic kernel, Plasma 6.2, and currently Wayland graphics (tho I prefer X11). I've modified the amdgpu-install script to accept Neon - that works but requires linux-headers for 6.10.14, which I'm unable to find and install. Has anyone on this sub-reddit gotten neon/amdgpu to work on an 890m or similar GPU, and if so could you provide website/downloads/links, kernel version, linux-headers links/install methods etc for that kernel version, so I can replicate your success. I know Canonical got a successful amdgpu install on an 890m running Ubuntu with 6.10 (or later?) kernel to work, as they posted some benchmark results, and so I posted a similar question to this one - on one of their community forums - and got zero responses

I have new system (Beelink MINI S N100) that came with Win 11 installed. I shrank its partition and installed KDE Neon (all on the same disk). Neon loads and runs without issue as long as I use F7 during POST and select that partition. When booting without intervention the system loads Win 11. I want it to boot to Neon directly.

I've read through dozens of posts that 'solve' this but I'm not able to duplicate the solutions given.

In UEFI there is no boot option for the KDE Linux/Neon partition so I can't give it boot priority. There is one for "[Hard Disk: Windows Boot Manager]" and other generic options NVME, USB, DVD, UEFI Shell etc. Boot mode select is set to UEFI.

I've modified grub to make Neon the first boot option, it is at the top of the list. The issue is that the only way I can get to the grub menu is to hit F7 during POST and select KDE Neon.

How can I make grub 'first' in the boot sequence so it loads KDE Neon?

Disk partitions are as follows, when viewed from KDE Neon. ALL are GUID Partition tables

Partition 1 - 105MB FAT32 mounted as: /boot/efi/ device: /dev/sda1 Partition type: EFI System

Partition 2 - 134MB 'unknown', not mounted, device: /dev/sda2 Partition type : Microsoft Reserved

Partition 3 - 74GB NTFS not mounted, device: /dev/sda3/ Partition type: Basic Data (This is the Win 11 partition)

Partition 5 - 436GB ext4 Mounted at: Filesystem Root device: /dev/sda5 Partition type: Linux Filesystem (This is the KDE partition)

Partition 4 - 1.9GB NTFS not mounted, device: /dev/sda4 (Windows recovery partition)

I'm have pretty Thinkbook 14 2024 with amd 8845hs. And I'm trying install kde neon, but have some troubles!

On sleep by close lid, and take power supply to type c port, laptop start charging after about 2 second (led start flashing) and if I'm open led - nothing. If click power button - it's just started on, like after power off.

I'm thing trouble in sleep mode, but I'm don't know what googling for solve it. Can u help me pls?

Upon start discover launches with a windows indicating the server failed the authenticity check at autoconfig.kde.org "The issuer certificate of a locally looked up certificate could not be found"

Im not sure how to correct this issue

I was happily working in my Wayland session when I set the display settings. It's either the screen profile or the refresh rather. Funny things happened. My screen turned black and after waiting, it stayed black. I am able to long to the x11 session but so far I'm not able to find the display setting that broke my Wayland session. When I go in x11 to the same place the configuration values are less. The one I set is not there.

It really makes me wonder if it's not a bug. How can setting a display setting not return to original values after a timeout?

I'm an arch user by default so my navigation with Debian is limited. But I tried installing plasma-bigscreen, and the session shows just a blank white screen. I have installed the correct driver's as far as I'm aware, and this is a fresh untampered install. Here are the components for Bigscreen I installed:

Plasma-bigscreen, plasma-mobile, plasma-settings

I have been running Neon as my gaming rig for the last few months already and every update works properly. The last update madr some wierd changes where cracking/popping noise experienced. Ibuse timeshift to restore back to an known working state to temporarily fix it. I spent a weekend figuring this out with pipewire/wirepipe fixes and seems nothing is working. Can someone help please?

I've been running Handbrake as a flatpak for quite a while and it's worked great. All of a sudden it quits after 5 seconds or so after I start it. Even if I'm not using it at all. I cannot figure out any way to find out what is happening. I get no error message. I've even launched the flatpak in a terminal but still no feedback error after it quits.

Any suggestions?

My I log into my PC the screen turns black and then takes me back to the login screen. I'd like to try to save the installation if at all possible.

Edit: Fixed, mozilla.list had two identical entries

Hi, I'm back (if you saw my last post, you'd know I had to reinstall)

Upon trying to upgrade KDE Neon to 24.04.1 LTS, I received the following error:

apt_pkg.Error: E:Conflicting values set for option Signed-By regarding source https://packages.mozilla.org/apt/ mozilla: /etc/apt/keyrings/packages.mozilla.org.asc != /etc/apt/keyrings/org.kde.neon.packages.mozilla.org.asc, E:The list of sources could not be read.

How do I remove the conflicting values/make them no longer conflict (and would it probably be best to install Firefox from Discover)?

I don't have fingerprint option in settings, but the fprintd is installed, login screen says that i can setup a fingerprint and also fingerprint is searcheable in settings (the result is users tab) but there i don't have any option to setup that. Am I just stupid?

I've been stressing over this since the rebase to 24.04 happened, as I have a firmware upgrade that refuses to go through. The issue is described at some length in this post, but I'll summarize here:

1. There are outdated/blacklisted entries within \EFI subdirectories.
2. fwupdmgr refuses to update the firmware because of these entries, even when provided the "--force" option.
3. One fix suggested in the above post is to run Boot-Repair, which I've done--no joy.
4. The other primary solution mentioned is to run the following command, which will provide a list of entries that are currently in use:

​

efibootmgr |grep 'Boot[0-9][]'|sed -e 's/[] .//g'|while read i; do efibootdump $i | echo "$i:" sed -e 's/^.*File(\([^)]*\)).*$/\1/g'; done

The solution recommends deleting all the entries that throw error messages, provided they're not found in the list generated by that command.

I don't know enough about EFI and boot workings by half, and as my machine is 7 years old at this point, I've accummulated a fair number of EFI entries in various folders (including some from Microsoft, even though I bought an XPS 13 Developer Edition?).

I guess I'm just looking for some confirmation that the above is safe. I'm usually OK with jumping in feet first on normal, system level issues, knowing I can probably get a shell at some point and try again if something borks. But the prospect of making my (personal) daily driver unbootable is more than a little daunting. I do have a backup of the entire /boot directory (which includes the above) by the way.

Thanks in advance for any help, I'm happy to provide any logs/command output that will assist!

I was installing OBS Studio, and I noticed that for some reason, the task manager didn't seem to be responsive. Since pressing my power button didn't do anything (normally set to bringing up the power options), I decided to force restart After powering back on, it brings up this screen I am able to get into tty4 with Ctrl + Alt + F4 I'm running on a Surface Laptop Go Version is User Edition 6.8.0-49- generic x86_64

Vivaldi opens a black window, while Google Chrome is completely transparent and I can see the wallpaper image. In both, I only have the status bar at the top.

After I updated two machines running KDEneon, I cannot enter any text in the password prompt to unencrypt my disk drive. I can enter Ctrl-Alt-Delete to reboot then go into the boot menu and boot up with a prior kernel option.

I installed Neon last night, got all my GUI pretties setup, rebooted for the umpteenth time and suddenly logging in to Wayland session just goes right back to login screen. X11 session logs in fine.

At first I thought maybe it was something to do with a splash screen I'd installed, but still no-go after reverting to default.

Logging in to X11, where do I look to see why Wayland won't login anymore?

As the title says, a recent KDE Neon update broke the appearance of Flatpak apps (as shown in the images).

Does anyone know what could be causing this issue? Could it be related to theme compatibility, missing dependencies, or a configuration error?

I'm open to any suggestions or ideas to fix this. Thanks in advance!

https://preview.redd.it/r4vshspdkg6e1.png?width=818&format=png&auto=webp&s=fb5db6e764368b95fce262a9068685e8d4755af2

https://preview.redd.it/xwgbowpdkg6e1.png?width=914&format=png&auto=webp&s=5a12e6711af9b9c3d57e9a2b42c23e5c354a17f7

https://preview.redd.it/5igq9rpdkg6e1.png?width=910&format=png&auto=webp&s=72eaccfe1f5bc8ab3eb6d0992cb83f5a9064b08d

After a long time on Fedora, we returned to KDE Neon.

Hello everyone, i would like know,where is the path folder about information LOGO, when there is startup, before login. Because i want change and move to down of the screen. thanks

I normally dont use the non free drivers and when I have used the nvidia drivers its been hit or miss for performance. Just wondering if anyone's used them on the newest neon.