for hours, firefox kept crashing for no reason. it reached a point where it finally gave me a reason to try firefox forks (which ive been meaning to do for a while)
each browser i tried had the same issue. when i try to drag it (i was trying to drag it to my other screen) it would instantly crash everything and all apps would close including the plasma shell.
i tried it with chromium and the issue persisted. turns out it happened with ANY window which isnt a dialog. if i drag settings, dolphin, or anything, it would crash.
i thought it was an issue with the wobbly windows, this update did break other stuff like 3rd party pagers and other plasmoids. but alas, disabling wobbly windows did not solve the crashing.
i have no idea what to do and i regret updating at all now.
im on KDE Neon with the following specs
KDE Plasma Version: 6.6.0
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.17.0-14-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 x 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
IT could be that you need to flush the local config files to reset it. Before you trying to do that, make a new user account and test if the crashes also happens there.
So it’s properly some config files that needs to be reset. You can do the big flush by deleting ~/.config directory/folder in you home directory. NOTE: It will reset you back to standard, saved settings will be reset etc.
Or which is more time consuming look through the .config folder and delete the settings of offending apps.
Also, if you open Dolphin dual pane - if it goes WELL, then you can start to move contents of .config-FORKED back into your fresh config folder until you get the bug back, then you can slowly isolate the actual issue.
The .config-FORK is just a backup folder, so yes the changes are permanent as long you want it that way. However if you want to pinpoint where the problem lies, you can move folders one by one from .config-FORK to .config
But if you are happy as it is, then leave it alone.
i am not, it happened again while i was trying to set up my old panels again. i really dont wanna deal with this. while i was making the panels the widget menu kept hanging and now the old issue is back. i really want to save my data and do a fresh install but i dont have time for that for the next 16 days : (
i am running that command again and reseting it. perhaps i can live like this for the next to weeks
Oh i had Kzones installed too. it was Disabled tho when i dragged my windows (which resulted in the crash). looks like the kzones issue was fixed according to the github issue you linked. i thought it was because of my sweet mars theme
Install the proprietary driver and see if that solves your problem. If you have not done so, I strongly recommend you install a system recovery tool like TIMESHIFT and create a restore point before embarking on any system admin tasks.
Use the regular repo to install it Timeshift:
sudo apt install timeshift
Launch the app from the start menu and run the wizard to create the backup config and restore point. Once you have done that, install the graphics driver.
First install the graphics driver ppa to get more up-to-date and complete Nvidia drivers list:
sudo add-apt-repository ppa:graphics-drivers/ppa
list the available drivers for your card.
ubuntu-drivers list
It will output a list of drivers named “nvidia-driver-xxx” where the xxx corresponds to a version number. Make note of the newest driver listed for your card.
Install the driver with:
sudo ubuntu-drivers install nvidia-driver-xxx
Reboot the computer and test. Upon reaching the login screen. you can choose between X11 and Wayland sessions at the bottom. Select the one you want and login.
Trust me when I say this will likely solve your problem. Disabling software is not a fix. Nouveau is known to be buggy with Nvidia cards. You absolutely need to use the proprietary driver if you want full performance and stability.
ok, i did have lots of performance issues show up outta nowhere BUT i am def not experienced enough to go through with the process rn. i might try it later if kzones doesnt work. btw thx for the well written steps you provided even though i cant follow them rn
