r/kdeneon • u/BigAndWazzy • Jun 17 '21
r/kdeneon • u/BigAndWazzy • Jun 17 '21
Badge Sticker V2 - Higher quality and Dark Mode (Downloads in Comments)
r/kdeneon • u/Upstairs-Highlight-8 • Oct 12 '25
Just switched to KDE Neon
I have to say KDE Neon is pretty good. I was using Kubuntu as a daily for about 6 months. Decided to pull the trigger on KDE Neon and absoluetly fell in love. I don't know what it is, but I just feel like there's a huge difference. Seems a little bit faster than Kubuntu, as well as, smoother operation. Anyway, here's my desktop, for SnG's. If there is any advice or opinons on Neon, I'm open to it,
r/kdeneon • u/wd5gnr • Feb 29 '24
Quick Guide to KWIN "Tiling"
The update breaks all the tiling scripts. There's not much to do, but KWIN has a sort of kind of tiling mode.
First, open the Systems Settings and under Keyboard, open Shortcuts. Select KWin and find the "Toggle Tiles Editor" entry. It is probably Meta+T and it may or may not be turned on. Turn it on, apply, etc.
Now hit "Meta+T" or whatever you set it to (Meta is your Windows key, BTW). You'll see some tile layout. You can resize, delete, or split the tile horizontally or vertically (note: splitting vertical makes a horizontal break; splitting horiz makes a vertical break). You can also make floating tiles. Click in any of the tiles to exit once you have it looking like you want.
Now... nothing ;). To dock a window in one of these tiles, hold shift while moving it. If you are like me and have the habit of using window+drag to move windows you have to do that FIRST then press shift (you can't press Shift+Win and drag).
When editing the layouts, there are a few predefined you can load (no save that I can tell) and a setting for padding. That's it.
Hope that helps someone.
r/kdeneon • u/omenmedia • Oct 21 '22
Jammy-rebased KDE neon has been released. All editions are now based on Ubuntu 22.04.
r/kdeneon • u/[deleted] • Jan 01 '21
Here's my setup, I installed Neon yesterday and not gonna lie, kde is sick af
r/kdeneon • u/MrFantasma60 • Feb 18 '26
1.7 GB update?! Holy guacamole!
I guess there's no point waiting. Better get down to it.
- Clicks update
- Enter root password (12345) (yes, I have the same combination on my luggage)
- Goes back to Reddit in the meantime
- Time passes...
What?! The update is completed already?!
But I just started it literally TWO minutes ago! Seriously?
And... I don't even need to reboot?
No way! I better reboot just in case.
- Reboots
- Laptop takes 16 seconds to restart
- The whole update took less than 3 minutes!
Dammit KDE Neon!
Why do you have to be so GREAT!!!
By the way, since I am dual booting, I better boot to Windows and update it too.
I'll be back in... about 12 hours... I hope... If all goes well...
...
r/kdeneon • u/BeowulfRubix • Mar 01 '24
Why on earth was a major (apparently not well tested) update pushed out to User editions of Neon
Most basic point:
Does anyone want to actually enforce the "not a distro" fallacy, which has been counter-reality for years?
Just remove the User Edition, which would be a mistake and kill the testing community size.
That would be the right move, if daily driver users are not welcome. Which of course they have been.
Original post:
Please tell me that Neon will remain what it always was - a solid barebones KDE OS that works and respects the different editions
I thought that I was just doing a normal system update in Discover, then I find out that Plasma 6 has been installed, while breaking my machine. And I see the list of annoyed people is very long this time. Some people have to work for a living, and this kind of thing is not funny.... Especially for the User edition.
I am picking my way through the mess that I never asked for. And now back into my machine, which is a mess. Discover doesn't even work anymore. And I have no package errors anymore on update, at least according to pkcon and apt. Whatever is going on, now I have to pick through that more.
None of us expect perfection, but this was an over-eager rollout IMHO for the User edition. I used to use the Dev one, with no issues ever. But then moved to the User edition with a new laptop years ago.
Yes, I know that Neon is rolling release for KDE, but that's not an excuse for this. Yes, I know that Neon is to show off KDE, but that would be a cop out response.
Neon is good. Very. People depend on it as their daily driver. Kubuntu, etc. don't cut the mustard for me. And I want a Debian base, ideally Ubuntu, which is a nice coincidence with Neon.
Links to read before commenting:
Reassuring
But more user notice/manual veto needs to be given when major version changes happen. Let alone for User Edition.
Also, a realistic assessment that you have to read when replying:
Lighter hearted song and appreciation:
r/kdeneon • u/Recommendation_Fluid • Feb 21 '22
After a long and constant distro-hopping, I finally settled on KDE neon once again!
r/kdeneon • u/MonstersTrioFan • Dec 07 '23
Can anyone tell me how to fix this, everything is opening in the middle of the screen
r/kdeneon • u/AndyMan1 • Oct 24 '22
FYI be careful when upgrading to KDE Neon with 22.04 if you have full disk encryption
I just spent a few hours figuring out how to fix this. Writing it down for posterity.
As part of the release upgrade, you may get prompted to update /etc/cryptosetup-initramfs/conf-hook to the distro default, and it will let you look at a diff. Pay very close attention to this, and consider keeping your current version.
What happened to me was it removed the line:
KEYFILE_PATTERN=/crypto_keyfile.bin(Note: that pattern may be something like /etc/luks/*.keyfile. You may still have a backup under /etc/cryptsetup-initramfs/conf-hook.dpkg-old. check for that and use that value if it's there.)
And that caused boot to fail, dropping you into an initramfs prompt with an error that a UUID does not exist.
So first, make sure you don't lose that line.
But if you do get stuck, you need to hop into a live-usb and fix it. I mostly followed these instructions, but edited the file above rather than messing with crypttab: https://askubuntu.com/a/1098108
The short version is:
boot a live usb
mount your encrypted lvm
chroot into it
update that conf-hook file to be correct
update-initramfs and update-grub
reboot
longer version:
# boot a live USB/CD and open a terminal
# the nvme should correspond to your main partition. use blkid, fdisk -l, etc. to determine
$ sudo cryptsetup luksOpen /dev/nvme0n1p2 crypt
Enter passphrase for /dev/nvme0n1p6:
$ sudo mount /dev/mapper/crypt /mnt
$ for i in /dev /proc /sys /run; do sudo mount -R $i /mnt$i; done
$ sudo chroot /mnt
root@neon:/# mount -a
root@neon:/# echo 'KEYFILE_PATTERN=/crypto_keyfile.bin' >> /etc/cryptsetup-initramfs/conf-hook
root@neon:/# sudo update-initramfs -u -k all
root@neon:/# sudo update-grub
root@neon:/# exit
$ umount -R /mnt
$ sudo rebootIf that doesn't work, you may need to mount your lvm in a more specific way. I wasn't sure if this step was truly necessary or not, but reboot the live usb and replace the beginning of the steps above with the following:
# find the correct entry of luks-* from /etc/crypttab, e.g. luks-abc-123-efg
$ sudo cryptsetup luksOpen /dev/nvme0n1p2 luks-abc-123-efg
$ sudo mount /dev/mapper/luks-abc-123-efg /mnt
# continue from the mount and chroot stepsI got a bunch of help both from askubuntu and the IRC channel, so some of these steps may not be necessary, or I may have some specifics wrong. but hopefully that's enough to help you recover.
Hope that helps!
r/kdeneon • u/[deleted] • Feb 16 '21
Plasma 5.21 is out and this time we have improved its looks and usability: there's a new wallpaper, an easier-to-use application launcher, a new system monitor, and much more.
r/kdeneon • u/EarthlingKira • Apr 07 '24
Install KDE Neon 6.0 on NVIDIA RTX 4090 (4080/4070/4060) by loading the NVIDIA driver into the live iso
r/kdeneon • u/[deleted] • Feb 18 '20
iMac5,1 2006 Model running KDE NEON. Themed like Mac!
r/kdeneon • u/ScanBe • Jul 26 '22
How I got the fingerprint sensor to work
Just gonna post to archive what worked for me:
Specs:
Operating System: KDE neon 5.25
KDE Plasma Version: 5.25.3
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
Kernel Version: 5.15.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 16 × 12th Gen Intel® Core™ i7-1260P
Memory: 15.2 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: Dell Inc.
Product Name: XPS 9320
Basic Steps:
Ensure your device is supported
Ensure your device is listed on your machine: run
lsusbin the terminalExample return:
27c6:63bc Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISCIt's also a good idea to see how linux runs with your specific sensor.
Vendor ID = first 4 chars from ID listed in lsusb. Device ID = last 4 chars from ID listed in lsusb.
sudo apt install fprintdsudo apt install libpam-fprintdAdd your fingerprints via KDE User settings.
sudo pam-auth-updateand check the fingerprint box in the opened GUI(nav using arrows and spacebar), saved by pressing enter.Add these strings to both the sudo and sddm(kde for some users) files located in /etc/pam.d/
auth sufficient pam_unix.so try_first_pass likeauth nullokauth sufficient pam_fprintd.so
You are done.
When logging in, press enter with an empty password field, or press the arrow key, and scan your registered print(s).
When running
sudoin the terminal, press enter instead of a password then scan your registered print(s).When running privileged GUI windows, it should prompt you for either your password or registered print(s). NOTE: I have noticed a few windows still require a password and do not even prompt for alternative auth methods.
If you have previously used the fingerprint sensor, or it's just still not working, try this:
Remove fingerprints on sensor using whichever method works for you (AppImage worked for me)
Try to add your print(s) now.
fprintd terminal debugging:
sudo fprintd-enrollIf the device keeps disconnecting, or you get an unknown error, you probably need to update your sensor.
Example errors:
An unknown error has occured|Impossible to enroll:GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available|Verify Stop failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “net.reactivated.Fprint.Device” on object at path /net/reactivated/Fprint/Device/0
sudo apt install fwupdSee if your system can see the device using
fwupdmgr get-devices(NOTE: Mine couldn't using fwupdmgr but this method still worked for me)fwupdmgr refresh --forcefwupdmgr updateReboot immediately.
fprintd-enrollshould work now. Use the KDE User fingerprint GUI to add your print(s).If you still have the error device already claimed, run
sudo service fprintd stop
Summary of events:
Switched from Windows 11 (previously had fingerprints on Hello and forgot to delete them). I wiped my drive and installed KDE Neon (User Edition as of 25JUL2022), but after installing fprintd every attempt to add/configure prints resulted in an unknown error. Looked up different error records and figured I needed to delete my old prints - I did and it still didn't work. Next I updated my sensor and it still was shooting errors out. So i installed libpam-fprintd and added them to the Auth with pam.d - boom, I can add prints now... but they still wouldn't do anything. So, after adding the lines to the sudo and sddm files in the /etc/pam.d dir, now I can use prints for sudo, privileged windows (mostly), and the login screen.
I am new to Linux, I have distro hopped for the last couple weeks(from Ubuntu to Arch and all the top 20s/30s/etc lists I could find) and decided on KDE Neon for now, I like it.
Sorry for the bad formatting, I don't like it either.
Listed below are all the links I used to get this working:
https://fprint.freedesktop.org/ https://community.frame.work/t/reset-fingerprint-scanner/8699 https://community.frame.work/t/fingerprint-scanner-compatibility-with-linux-ubuntu-fedora-etc/1501/214 https://unix.stackexchange.com/questions/623929/fprintd-the-driver-encountered-a-protocol-error-with-the-device https://askubuntu.com/questions/878072/lenovo-finger-print-reader-already-claimed https://forum.kde.org/viewtopic.php?f=309&t=174078 https://forum.endeavouros.com/t/how-to-enable-fingerprint-support-in-kde-5-24/24401/6 https://linux-hardware.org/?view=search
r/kdeneon • u/cejno • Dec 04 '25
My aux on kde neon is not working
Last Update: I found the problem and the solution finally: https://imgur.com/a/P1DDFGx
So when you put "alsamixer" into terminal and press F6 then choose the Default 1, you can see from the picture my headphone was on Mute, of course I don't know for what reason they did that. So pressing letter 'm' is taking it out from the mute and it is working.
______________________________________________________________________________________________
I did everything I can, searched, used ChatGPT and tried everything and still I couldn’t make my aux works. Laptop speakers are working, my Bluetooth headphone is working with neon but the aux is not working. Even though I liked this distro so much I think I will have to go to xubuntu or something else. My laptop with neon works perfectly, everything works great and looks great but unfortunately I couldn’t fix this issue.
______________________________________________________________________________________________
Update: I purchased this: https://imgur.com/T04LA7C on Amazon and it is working this way. In case this is the solution for now if you are struggling with it or Bluetooth headphone.
Last Update: I found the problem and the solution finally: https://imgur.com/a/P1DDFGx
So when you put "alsamixer" into terminal and press F6 then choose the Default 1, you can see from the picture my headphone was on Mute, of course I don't know for what reason they did that. So pressing letter 'm' is taking it out from the mute and it is working.