kf5 doesn't work
Tags:
None
Registered Member 
|
Hi there and thx for reading and possibly answering if you can.
I don't know if it is the right place for my question, but I post it here. I'm using opensuse 13.1 x86_64, and I wanted to keep my kde4 and all its bells and whistles while installing kf5 it in a separate directory, /opt/kde5. So I used kdesec-build, for retrieving, compiling and installing kf5. So far, so good. But despite my efforts and the gracious help from wolfi323, the moderator of the opensuse forum, kf5 still doesn't work. I tried it from both a Xnest window, and a full kdm session with the help of the following starter script:
In both cases, startkde works, but no display, except maybe a kwm window around a pre-existing xterm shell. However, plasmashell is stuck in an endless loop, occupying 100% cpu. I'm pretty sure I'm not the only guy on this planet in that case. Who has already experienced this behavior. Actually I'm not upset: kf5 is still young and bugs may arise as usual. |
Manager
|
Moved to plasma Next forum and removed duplicate posting
OpenSuse Leap 42.1 x64, Plasma 5.x
|
Administrator
|
Please attach gdb to plasmashell and generate a backtrace so we can see where it is stuck.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
ok, did it but I doubt that it is useful
|
|
There's no backtrace.
plasma-shell is attached, a bunch of libs loaded and debug symbols installed - ultimately there's an error: 0x00007f552975632f in pthread_mutex_lock () from /lib64/libpthread.so.0 Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace and then you quit (gdb) ^CQuit -> how did you invoke gdb? If by hand and when loading libs finished and you're presented a prompt, enter "bt" |
|
Registered Member
|
so, I started a rescue session from kdm, then I launched my starter script as a separate process with &, then
ok will use bt next time. Thx for the tip. 
|
|
Registered Member
|
Okk, used bbb instead, and got the following backtrace:
What can I do next ? |
|
Administrator
|
You need to enter "bt" at this point. Looks like it may be stuck in a render loop though based on the initially printed line.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
|
|
Registered Member
|
ok, got the following output:
|
|
|
|
Registered Member
|
ok, I got this
|
|
Administrator
|
Please install the debugging symbols for the KF5 libraries. It appears to be completing part of it's startup at that point in time - which is an interesting loop. How long had "plasmashell" been running at this point in time?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Thread looks dormant, might be a livelock?
Can you make plasmashell run "--sync"? (edit startkde) |
|
Registered Member
|
I could, but no direct invocation of plasmashell in startkde
meanwhile, I recompile everything with -g3 CFLAGS. pffff 
|
Bookmarks
Who is online
Registered users: bartoloni, Bing [Bot], Google [Bot], Yahoo [Bot]
