https://bugs.kde.org/show_bug.cgi?id=386661
--- Comment #4 from joergis...@web.de ---
tried with gdb this way:
gdb /usr/bin/systemsettings
then I typed in "run"
this is the outcome:
Starting program: /usr/bin/systemsettings5
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe42aa700 (LWP 7431)]
Using Wayland-EGL
Using the 'wl-shell' shell integration
[New Thread 0x7fffd6cbe700 (LWP 7432)]
[New Thread 0x7fffcfbb8700 (LWP 7433)]
KActivities: Database connection:
"kactivities_db_resources_140737104726208_readonly"
query_only: QVariant(qlonglong, 1)
journal_mode: QVariant(QString, "wal")
wal_autocheckpoint: QVariant(qlonglong, 100)
synchronous: QVariant(qlonglong, 0)
Nothing to load - the client id is empty
Nothing to load - the client id is empty
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property
"minimumHeight"
[New Thread 0x7fffcd230700 (LWP 7434)]
[New Thread 0x7fffc7fff700 (LWP 7436)]
Thread 5 "QSGRenderThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffcd230700 (LWP 7434)]
wl_proxy_create_wrapper (proxy=0x0) at ../src/wayland-client.c:2038
2038 ../src/wayland-client.c: No such file or directory.
(gdb) kill
Kill the program being debugged? (y or n) y
(gdb) quit
You can see that I had to kill the programm. The strange thing was: it Launched
the "about systemsettings" window which it never did when I tried. (It also
only does it when the application is launched with gdb, so nothing has changed)
But after having launched this window, i was no longer able to interact with
the programm. I klicked on every item, even on the close buttons of both
windows (the usual systemsettings one and the window with the "about
systemsettings" content) but nothing happened.
Tell me if you need a more detailed backtrace. I'm willing to give you one, but
I don't know how to do that (since the KDE_Crash_Dialog doesn't launch after
the window has vanished), so perhaps you need to send me a link to a tutorial
or so.
(I already checked this one out
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Backtraces
this is where I had the Idea with dbg from)
--
You are receiving this mail because:
You are watching all bug changes.
