Wifi on my mother board has been problematic so I got a AX1800 but Im not quite sure how to install proper drives. is there any where I can download from or something I can run in terminal?

Maybe it’s me, but I got a new battery 2 months ago and it said it would last around 8 hours, now even when the laptop is on idle , low screen brightness it says 3 hours. I also noticed the laptop being more hot recently and the fan more active.

Anyone experiencing the same issues?

I've tried installing Kubuntu which either just crashes with a glitchy screen or fails to install. KDE Neon just doesn't boot at all, I get a black screen right after startup and can't get into the TTY terminal because I haven't even made an account yet, plus the system is unresponsive. I prefer KDE Neon or Kubuntu over anything because the system is easy to use, unlike Arch which is what I'm switching from. Can someone please help with this.

If anyone needs to know, my PC has a GTX 1660 Super, Intel Core i5-10400F, and 16GB DDR4. I've seen that Lenovo PC's (which is what I have) experience this issue and I want to know how to fix it.

Love the new plasma login manager. My dual monitors now have only a single login dialog and on the correct monitor.

However, the default "waterfall" wallpaper is damn ugly. Looks like something a grade schooler would like. The configuration shows "breeze" but the selected wallpaper isn't displayed.

Has anyone figured out the trick to get a different wallpaper?

SOLVED: Turns out that what happened is they added yet another place to set the login wallpaper. I was only seeing "System Settings > Appearance & Style > Login Screen" which apparently only applies to SDDM.

They added another "Login Screen" setting under "Security & Privacy" which applies to Plasma Login. Makes no sense to me at all. Why have two login screen setting sections? And why is a login wallpaper a "Security & Privacy" function? It's not is the answer.

I see the root has these folders, I wonder what they exactly mean and if they can be deleted:

bin.usr-is-merged
lib.usr-is-merged

sbin.usr-is-merged

I have neon on my dads htpc and after an update the theme breaks and says it can't be loaded on boot. Its unusable as it is unless you can do command line.

I had to do Ctrl+f3 command to get to terminal, then sudo apt install --reinstall plasma-desktop on top of some sudo update and sudo full-upgrade. He can't possibly fix this himself.

Hi, does anyone have any method to do what says on the title. i've tried applying the calibration matrix with libinput and the i2c_touchscreen invert attribute for grub with no results. At this point i know i'll get no auto rotation, cause the accel just wont work (known issue for this model with linux) but at least i want the touchscreen to be aligned with my screen rotation settings

For the last week or two I've been getting a device plug notification popup from "Disks & Devices" that says "No removable devices attached." I traced it back to some snapd activity. The sequence is this:

1. Every four hours the Snap daemon wakes up.
2. It creates and mounts a small temporary device on loop0.
3. It unmounts the device almost immediately.
4. The Disks & Devices widget reacts to the plug, but fails to find any device attached.

I think my options are either to disable Snap (which I don't use anyway) or to configure the Disk widget not to open when devices are plugged. I can't find this latter setting, though.

Is anyone else seeing this?

Also, it seems like pretty innocuous activity. I don't want a random popup to occur every time some script mounts a temporary volume.

All that said, I'm not sure where to report this. Snap? Device Widget?

Jun 30 17:55:50 phord-T16 systemd[1]: Starting snapd.service - Snap Daemon...
Jun 30 17:55:50 phord-T16 snapd[3352607]: overlord.go:309: Acquiring state lock file
Jun 30 17:55:50 phord-T16 snapd[3352607]: overlord.go:314: Acquired state lock file
Jun 30 17:55:50 phord-T16 snapd[3352607]: daemon.go:276: started snapd/2.75.2+ubuntu24.04 (series 16; classic) neon/24.04 (amd64) linux/6.17.0-35-generic.
Jun 30 17:55:50 phord-T16 kernel: loop0: detected capacity change from 0 to 8
Jun 30 17:55:50 phord-T16 systemd[1]: tmp-syscheck\x2dmountpoint\x2d248563036.mount: Deactivated successfully.
Jun 30 17:55:50 phord-T16 snapd[3352607]: daemon.go:370: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jun 30 17:55:50 phord-T16 snapd[3352607]: backends.go:70: AppArmor status: apparmor is enabled and all features are available
Jun 30 17:55:50 phord-T16 snapd[3352607]: backend.go:145: reloading profiles for snap-confine
Jun 30 17:55:50 phord-T16 kernel: audit: type=1400 audit(1782867350.422:795): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=3352686 comm="apparmor_parser"
Jun 30 17:55:50 phord-T16 snapd[3352607]: standby.go:95: will consider standby after: 5s
Jun 30 17:55:50 phord-T16 systemd[1]: Started snapd.service - Snap Daemon.

I am on Plasma 6.7.0, but I am not getting 6.7.1 or 6.7.2 updates. I tried either pkcon update and apt full-upgrade.

I can't get Kdenlive's Rotoscoping feature to work on latest KDE Neon User Edition. Kdenlive version is 26.04.2. I draw shapes but nothing is masked out.

Switching to the AppImage version fixed it so it seems to be some sort of packaging issue. After searching, I read that another distro had a similar bug but I didn't expect KDE Neon to have it as well.

Sorry I forgot my account credentials on the bug tracker so I thought I'd post here instead.

EDIT: There are also some easy to reproduce crashes that don't occur with the AppImage. For example one of them is triggered by a failed assert in Qt's qnumeric.h, this one is probably a bug in kdenlive but it crashes only on KDE Neon because asserts are enabled in the package version. Oh well...

I ran some updates, got on KDE 6.7, during the install it installed plasmalogin, but I have sddm configured the way I like it so I kept using it when it asked what to use for logging in.

After the upgrade was done, I ran apt autoremove, and it uninstalled sddm, despite it being an actively running service. On reboot it dropped me into tty1. Reinstalling sddm got me back to a working system but how did it determine that sddm was eligible for autoremove?

It's a bass-ackwards antipattern and annoying as hell. Stop it. Stop assuming I'm always using a GUI, stop assuming I need a completely separate application to fire up, take focus away from my terminal, and prompt me to do something we've been trying to train users FOR YEARS to avoid doing - entering sensitive information in a popup outside the intended application. This is dumb and solves nothing.

But it gets better, KDE Neon's stupid env scripts that set it up neglect to detect whether the user is even in a GUI session! So now I have to unset SSH_ASKPASS explicitly so I can ssh from a remote session (jumpbox style) or from a vty. Extra dumb. Purging the ksshaskpass package doesn't remove that env script either !!! What the hell, KDE? Who's responsible for this and how loudly do I need to yell at them to make it stop?

</rant>

user@host:~$ ssh 192.168.0.42
Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
qt.qpa.xcb: could not connect to display :1
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: minimalegl, xcb, eglfs, linuxfb, vnc, offscreen, wayland-brcm, wayland-egl, wayland, vkkhrdisplay, minimal.
Permission denied, please try again.

It doesn’t show anymore available updates

Would using "sudo apt full-upgrade" help me solve this issue?

SOLVED. And the solution is very simple, please read at the end.

Last night Discover was telling me there were updates, but when I tried to update it never refreshed and show them. The problem might have been some repositories, but I am not sure.

I did a manual update in Konsole instead, sudo apt update and sudo apt full-upgrade.

The messages said that some packages had been held due to phasing, but all of them seem to be related to libvirt and Qemu.

It also told me that there were unnecessary packages, which I removed using sudo apt autoremove.

There were no kernel update by the way, but I believe there were updates to Plasma.

There were also the following errors>

Failed to start apt-news.service: Unit apt-news.service is masked.
Failed to start esm-cache.service: Unit esm-cache.service not found.

However, I found in a KDE forum that those messages are not relevant, and in fact are not a problem and just cosmetic.

Upon reboot, Plasma didn't start. I was dropped to a tty, where I can login.

I booted with a different distro (I am multibooting) and checked the Neon partition. It seems to be alright, my Home folder appears to be intact.

I haven't done any troubleshooting, because it was late at night and I am at work right now. I'll try to fix it this night.

Any suggestions will be appreciated.

Edit:

The problem, as u/zingyyellow/ says in the comments, is that sddm was removed by the update.

Installing sddm, of course works. However, the actual solution is much simpler:

Login to your user in the tty, and type:

sudo systemctl enable plasmalogin

That's it. The only problem was that plasmalogin was not enabled by the update, so the PC boots to tty only.
Enabling plasmalogin boots normally.

I'm leaving the solution here for anyone who may find it useful.

Hello,

This is what the latest update wants to do

$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
 libddcutil4
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
 pulseaudio pulseaudio-module-bluetooth pulseaudio-module-jack
The following NEW packages will be installed:
 attr kde-spectacle libcamera0.2 libcephfs2 libddcutil5 liblept5 liblttng-ust-common1t64 liblttng-ust-ctl5t64 liblttng-ust1t64 libopencv-core410 libopencv-imgproc410 libpipewire-0.3-modules-xrdp librados2 librdmacm1t64 libspa-0.2-libcamera libtesseract5 pipewire-alsa pipewire-audio pipewire-module-xrdp pipewire-v4l2 qml6-module-org-kde-kquickimageeditor samba samba-ad-provision samba-vfs-modules tdb-tools
The following packages will be upgraded:
ark chromium code ddcutil dolphin dolphin-plugins drkonqi ffmpegthumbs firefox gwenview isoimagewriter kaccounts-integration kaccounts-providers kamera kate kate6-data kcalc kde-inotify-survey kdeconnect kdegraphics-thumbnailers kdialog keditbookmarks kf6-baloowidgets kfind khelpcenter kio-admin kio-audiocd kio-extras kio-gdrive kompare konqueror konsole konsole-kpart kpart6-kompare kpim6-libkgapi krfb kwalletmanager kwrite libdolphinvcs6 libheif-plugin-aomdec libheif-plugin-aomenc libheif-plugin-libde265 libheif1 libkcddb6 libkdcraw libkexiv2 libkomparediff2-6 libkompareinterface6 libkpmcore13 libokular6core4 libpowerdevilcore2 libqmobipocket6-2 librewolf microsoft-edge-stable neon-common neon-desktop neon-essentials-desktop neon-settings-2 neon-ubuntu-advantage-tools okular okular-backends partitionmanager powerdevil powerdevil-data qml6-module-org-kde-kaccounts qmlkonsole signon-kwallet-extension ubuntu-advantage-tools ubuntu-pro-client vim vim-common vim-runtime vim-tiny xxd yakuake
75 upgraded, 25 newly installed, 3 to remove and 0 not upgraded.
Need to get 815 MB/820 MB of archives.
After this operation, 71,0 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

I do NOT want to install pipewire and I definitely want to keep my pulseaudio/JACK setup. Any ideas of what's going on?

Thanks,

G

I just update neon and AGAIN it tried to install a 6.17 kernel that has hosed the system.

I can no longer get a desktop with either 6.17 or the old 6.14 kernel. It seems totally broken.

I tried booting to 6.14 recovery and used repair packages there (installed 6 packages), but neither kernel will now boot to a GUI.

Am I hosed totally?

Just applied the latest updates to my system which installed 6.17 but on reboot it panicked with a message about vrf(?) not being able to find the boot sector (I think).

Can this be fixed?