http://bugzilla.opensuse.org/show_bug.cgi?id=1129464
http://bugzilla.opensuse.org/show_bug.cgi?id=1129464#c13
--- Comment #13 from Maurizio Galli
(In reply to Maurizio Galli from comment #8)
The output provided doesn't give any indications of errors and the fact that you're both able to load the desktop manually with the commands means it's not "broken".
Looks like it does not load at startup or fails to load at startup.
That's what I'm starting to wonder now: Were the symptoms we saw due to xfdesktop not being autostarted at session login? FYI, xfdesktop is now in my xfce session list, but it's not in the autostart list -- should it be in the xfce autostart list?
No it doesn't need to be added in the autostart list.
FYI, I have since done a reboot and xfdesktop started and the desktop still functions/looks right. But that may be because I have xfce auto-save my session at logout, which is in turn starting xfdesktop? (Settings -> Session -> General tab)
It could be that the update created cache problem that got resolved when you manually quit and restarted xfdesktop.
Please help me with the following:
1) check that xfdesktop is actually running and listed in Settings > Session and Startup > Session
Yes, it is.
Good
It's a bit premature but I suspect Nvidia and new Kernel might be to blame. I cannot test this theory right away because all my devices are Intel GPU.
This breakage happened to me after a daily upgrade (Tumbleweed) that did not include NVIDIA or kernel updates (in particular, this happened before the update to Linux kernel 5.1.)
Noted but the snapshot 20190314 did have kernel 5 in it, unless I'm mistaken.
If meanwhile any of the next snapshot updates resolves the issue please let me know.
That will be hard to recognize because it appears to be functionally resolved now. (Tho we still don't know the root cause why it happened to us.)
Ok. So far I wasn't successful at reproducing this issue and if it's resolved for you too it might be hard to get to the root of the problem. -- You are receiving this mail because: You are on the CC list for the bug.