Fri Apr 14, 2017 1:51 pm
I've been a real happy KDE Neon user so far and I'm quite excited about the fresh look and experience!
But now I'm having this quite annoying bug in my KDE Neon Desktop, where my whole desktop is displayed in the wrong place on every startup. I can manually fix it every time by going into the displaysettings and switching into another displayresolution and back again, but thats fairly annoying after some time.
And theres another side to the Bug: all my popup-menus such as start-menu, date & time, wifi-settings, audio-settings, etc are being displayed in totally random spots as well, which change all the time. So sometimes they're even off the edge of the screen which makes me unable to use them. :/ this is actually the most annying part of the bug.
Obviously I have been researching the internet for quite a while to look out to somebody whos had this issue before, but unfortunately without success so far. I've been trying couple of things to fix this, mainly following instructions from different posts all over the web. But this bug is teasing me for a while now so I cant reproduce everything I've tried. There seem to be so many screen-, display- and windowservices on KDE Plasma, so its kinda difficult to bugfix things without having a clue how things reall work there..
Also: Been havig the same issue on KDE Plasma 5.X when I was running it on Manjaro Linux last year. But then I switched to Linux Mint KDE.
So maybe my Laptop Specs will give any hint:
Type: Thinkpad T420s
CPU: Intel-Core i7 2,8 GHz
Graphics: Discrete NVIDIA NVS 4200M
+ Integrated Intel HD Graphics 3000
Graphics info from terminal:
Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
Display Server: X.Org 1.18.4 Drivers: (unloaded: fbdev,vesa) Resolution: email@example.com
GLX Renderer: Mesa DRI Intel Sandybridge Mobile GLX Version: 3.0 Mesa 17.1.0-devel
Anyone any ideas on what to do/ what to look for on the internet?
thanks in advance for your help! will really apreciate any hint!
Fri Apr 14, 2017 2:53 pm
Maybe, this helps:
$ apt search bumblebee
Full Text Search... Done
bumblebee/xenial 3.2.1-10 amd64
NVIDIA Optimus support for Linux
bumblebee-dbg/xenial 3.2.1-10 amd64
NVIDIA Optimus support - debugging symbols
bumblebee-nvidia/xenial 3.2.1-10 amd64
NVIDIA Optimus support using the proprietary NVIDIA driver
Fri Apr 14, 2017 6:47 pm
hey man thanks for the effort. so I went and checked my bumblebee-settings and tried to switch my graphics-drivers
but for some reason bumblebee wont recognize my nvidia-current package. so running on nouveau driver currently, but I've been using this driver a while before the bug popped up already, so im supposing the source of the problem to be somewhere else. and im fine with nouveau so far..
someone else an idea? apreciate any help!
Sat Apr 15, 2017 12:47 pm
When I create a new user, the problem doesnt appear. so the problem must be somewhere in my configs, right?
But renaming/removing any of either .config .kde .local or .cache folders im my home directory didnt solve the problem, I've tried it with all of them at once.
does anyone know whereelse might be config-files to refresh ?
Tue Apr 18, 2017 7:20 am
For some reason yesterday my desktop suddenly was fine for a while, even when restarting several times the deskop and all its widgets were in the right place. But then I started adding some widgets and during that process the plasmashell crashed, so it restarted automatically.
But it restarted into the buggy desktop again and all my problems came back. Now I'm focusing my bugsearch on the plasmashell.
when I manually restarted plasmashell with sudo restart plasmashell it gave me a list of outputs that to me look like a couple of things arent working correctly.
I will look through step by step, but incase some of you are real quick at finding suspicious lines, heres the output:
thanks in advance for any help
Tue Apr 18, 2017 3:30 pm
Don't do this as 'root' with 'sudo:
Login is initialized only for normal user after desktop login:
# Normal User: Login-Environment initialized
$ set | grep XDG
[2: (0 0)]1[<normal_user>@neon..:/home/<normal_user>/]
# <SuperUser>/root: Nothing there!!!
$ sudo su -
# set | grep XDG
[2: (0 1)]1[root@neon..:/root/]
Sat May 06, 2017 9:44 am
Okay so I made a whole new system-setup. I'm now trying Kubuntu 17.4 on Plasma 5.9.4 but the same problem occured as soon as I started adding
widgets to my Plasma Desktop. Since I only started adding Widgets ~ 10 days after my new system installation I know for sure that the bug was caused by adding widgets to my desktop. (already had widgets in the system panel before, without causing any problems)
please excuse my ignorance, i'm still new to linux so im not sure what I'm supposed to do with the code you posted. was this meant to go somewhere into a config file?
Since im on Kubuntu now, I guess it will be obsolete anyways.
does anyone have an idea how to prevent my desktop-problem?
Sat May 06, 2017 11:31 am
im not sure what I'm supposed to do with the code you posted.
was this meant to go somewhere into a config file?
You did make a typical beginner's mistake, that I made myself when
I still didn't understand how this all works.
I wanted to warn You away from taking steps that You as a beginner
most probably cannot know.
I give You another example for the basic idea I wanted You to understand:
If You start "KDE Partition Manager" normally after normal login
it uses the configuration files in Your HOME directory.
If You start it as 'root'-user (by using: 'sudo partitionmanager')
it still uses Your configuration files, but now they are taken ownership of
by the user 'root'.
They should be like this
$ command ls -l .config/partitionmanagerrc
-rw------- 1 You You 1 Apr 23 16:11 .config/partitionmanagerrc
but after using 'sudo' they will look like this:
$ command ls -l .config/partitionmanagerrc
-rw------- 1 root root 1 Apr 23 16:11 .config/partitionmanagerrc
which means: From now on, You won't have access.
The topic here is: Unforeseen consequences of using 'sudo'.
Sat May 06, 2017 3:37 pm
Thanks NoNameNoBlame for explaining, I think I'm now understanding this better.
As far as I can translate this to my knowledge level I should probably check before I use
sudo for any action that I wanna have done within my system.
Registered users: 4m, abury, Baidu [Spider], Bing [Bot], bluesky, boudewijn, DaniilDragon, Deevad, Exabot [Bot], Google [Bot], hellozee, Lembritt, m4TZ, mcoudert, Merlimau, rblackwell, TheraHedwig, thunder422, Underrr, vishalrao, Yahoo [Bot]