Hello, update 20180119
Plasma boots into black screen. I can login into icewm. I tried force reinstall plasma5-workspace as well as plasma patterns. I also tried renaming .kde4 to .kde4_backup but nothing helps.
Any ideas?
Install the package Mesa-dri.
See also https://forums.opensuse.org/showthread.php/529166-X-server-segfaulting-since-4-14-13 and https://lists.opensuse.org/opensuse-factory/2018-01/msg00311.html
You need to install Mesa-dri, that should do it. The Mesa driver was split into several packages with one of the latest updates.
Edit: not fast enough:)
Thank you for your prompt response. I installed Mesa-dri but still get a black screen. I can now open krunner and open konsole but if I try to open plasmashell it crashes right away
Then run “zypper dup” to make sure your system is fully up to date.
Maybe you have a version mix of Mesa packages, like in the other thread.
I just did that (ran zypper dup without any options) but it still crashes. Here is konsole output:
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:288:17: QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:288:17: QML Text: Binding loop detected for property "width"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:288:17: QML Text: Binding loop detected for property "width"
qt.svg: <input>:1500:789: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:1500:976: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:1551:795: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:1551:984: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:154:769: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:154:958: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:155:770: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:155:959: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:207:761: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:207:948: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:212:784: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:212:974: Could not add child element to parent element because the types are incorrect.
[KASTATSFAVS] 0x5604fb201850 0x0 "no client ID yet" initForClient "org.kde.plasma.kicker.favorites.instance-54"
[KASTATSFAVS] 0x5604fb201850 0x5604fdf08e30 "org.kde.plasma.kicker.favorites.instance-54" Loading the ordering ("preferred://browser", "systemsettings.desktop", "org.kde.dolphin.desktop", "org.kde.kate.desktop", "org.kde.konsole.desktop")
[KASTATSFAVS] 0x5604fb201850 0x5604fdf08e30 "org.kde.plasma.kicker.favorites.instance-54" Query is Query { Select: LinkedResources, Type: (":any"), Agent: ("org.kde.plasma.favorites.applications", "org.kde.plasma.favorites.contacts", "org.kde.plasma.favorites.documents"), Activity: (":current", ":global"), Url: ("*"), Order: HighScore, Limit: 0 }
KActivities: Database can not be opened in WAL mode. Check the SQLite version (required >3.7.0). And whether your filesystem supports shared memory
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: Application 'plasmashell' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 21 and type 'Read', disabling...
[1]+ Stopped plasmashell
That doesn’t tell anything.
Do you have a backtrace?
Also, please post the output of glxinfo (you may have to install the package Mesa-demo-x first), the file /var/log/Xorg.0.log, and your repo list:
zypper lr -d
here is a list of my repositories:
Repository priorities in effect: (See 'zypper lr -P' for details)
98 (raised priority) : 1 repository
99 (default priority) : 6 repositories
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+-------------------------------------+------------------------------------------------+---------+-----------+---------+----------+--------+----------------------------------------------------------------------------------+--------
1 | Packman-Repository | packman | Yes | (r ) Yes | Yes | 98 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/ |
2 | home_rawtherapee | RawTherapee Home Project (openSUSE_Tumbleweed) | Yes | (r ) Yes | No | 99 | rpm-md | http://download.opensuse.org/repositories/home:/rawtherapee/openSUSE_Tumbleweed/ |
3 | http-download.opensuse.org-1ff22bf3 | graphics | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/graphics/openSUSE_Factory/ |
4 | http-download.opensuse.org-c1ca865f | home:Alexx2000 | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/Alexx2000/openSUSE_Tumbleweed/ |
5 | openSUSE-20170801-0 | openSUSE-20170801-0 | No | ---- | ---- | 99 | yast2 | hd:///?device=/dev/disk/by-id/usb-090c_1000_12052385001327-0:0-part2 |
6 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/tumbleweed/repo/oss/ |
7 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
8 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/oss/ |
9 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/tumbleweed/repo/oss/ |
10 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
here is the Xorg log:
https://drive.google.com/open?id=1nBwJWtZ4PtFFm5TYrnGu1iPEf9G04wtA
here is glxinfo:
https://drive.google.com/open?id=1ZoCqwCNuskouglc3gQPE5M5_3v_kEi0C
Hm, that looks fine, actually.
Does it work if you boot with “nomodeset”?
What about a fresh user account? (or rename ~/.config/, not ~/.kde4 which is/was used by KDE4 as the name implies)
Haven’t tried nomodeset yet.
Removing .config folder did not solve the issue. Desktop showed up for a second and then plasma crashed
The system seems to be functioning. I can open programs, Alt-Tab works but there is no panel
How do I get bugtraces from opening plasmashell? gdb says it is missing debug symbols for plasma
That’s to be expected, because it’s plasmashell that would display the panel.
KDE’s crash reporter (drkonqi) should appear automatically when it crashes. There should be an icon in the system tray, click on it.
Or run it via gdb and then type “bt” after it crashed.
OTOH, a new Tumbleweed snapshot has been released today, with another Mesa update (to 17.3.3).
So I’d suggest to update again (with “zypper dup”), maybe it helps.
I ran zypper dup again but it did not help.
When I am trying to get back traces I get this:
Reading symbols from plasmashell...Missing separate debuginfo for /usr/bin/plasmashell
Try: zypper install -C "debuginfo(build-id)=a0679c320993a87aeea60fa965023f3f4c3e7438"
(no debugging symbols found)...done.
if I Ctrl + C and then type ‘bt’ I get ‘no stack’
I tried 'sudo zypper se debuginfo" but the only thing I see for plasma is “plasma5-radiotray-debuginfo” I tried installing it but gdb still missing the symbols…
Don’t press Ctrl+C, that will abort the application I think.
Just type ‘bt’ after it crashed and you get a gdb prompt.
I tried 'sudo zypper se debuginfo" but the only thing I see for plasma is “plasma5-radiotray-debuginfo” I tried installing it but gdb still missing the symbols…
That contains the debug symbols for plasma5-radiotray, obviously.
Btw, have you tried a fresh user account already?
Also, as it’s not even possible to get a backtrace of the crash, maybe some file(s) got corrupted.
Try to reinstall plasma5-workspace with “sudo zypper in -f plasma5-workspace”.
If that doesn’t help, run “rpm -Va” and post the output.
Another thing I would try is to delete ~/.cache/. This particularly contains compiled QML code (to speed up things), which Plasma heavily depends on.
But trying a fresh user account would mean a fresh ~/.cache/ too of course.
Here is the full terminal output on running ‘plasmashell stop’ and ‘plasmashell start’
https://drive.google.com/open?id=17D-D7-9551qSX688UWU0w-YELQRy3Pnu
Is anyone seeing anything wrong there?
Why are you doing that?
plasmashell doesn’t know the arguments “stop” or “start” (just as it doesn’t know “debug”). It’s not a service.
And you already posted plasmashell’s output. I see nothing indicating the problem there.
Please try the other things I suggested.
Except maybe this:
KActivities: Database can not be opened in WAL mode. Check the SQLite version (required >3.7.0). And whether your filesystem supports shared memory
Reminds me of https://forums.opensuse.org/showthread.php/512802-Plasma-5-crashes-at-start-up-after-update/page2
Delete ~/.local/share/kactivitymanagerd/ and see if it helps.
But you did already try to rename the whole ~/.local/, didn’t you?
And trying a fresh user account as I suggested would have the same effect.
wolfi323, you are the best! Renaming ~/.local/share/kactivitymanagerd/ solved the issue!
It is weird because I don’t even use KDE activities. I launched it once to take a look, that is it.
PS I did not try renaming ~/.local/ before that I tried ~/.config
kactivitymanagerd also tracks opened documents and applications. You use it implicitly, e.g. the “Recently used” items in the application menus get their entries from kactivitymanagerd.
Apparently its database got corrupted somehow then somehow.
Anyway, glad to hear it’s solved. 