Bug 386661 - system settings under wayland crashes when klicking on "about systemsettings" or on "about KDE" or on "configure"
Summary: system settings under wayland crashes when klicking on "about systemsettings"...
Status: RESOLVED DUPLICATE of bug 381630
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.11.3
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-08 20:17 UTC by joergister
Modified: 2018-04-16 10:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description joergister 2017-11-08 20:17:22 UTC
When klicking on the burger menu left from the searchbar and selecting one of these three options the programm simply terminates. 
When I start it via the Terminal by tiping "systemsettings5" all I get is this.

 systemsettings5 
QObject::connect: invalid null parameter
Using Wayland-EGL
Using the 'wl-shell' shell integration
KActivities: Database connection:  "kactivities_db_resources_140326598158528_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



After having selected one of the three mentioned options I also get this: 
Segmentation fault
and the programm terminates.
Comment 1 Christoph Feck 2017-11-23 23:34:22 UTC
Unless you can provide a backtrace, let's assume it is a duplicate.

*** This bug has been marked as a duplicate of bug 381032 ***
Comment 2 joergister 2017-11-25 14:17:57 UTC
well I would provide a backtrace and the debug package for systemsettings is installed.  But systemsettings simply vanishes when I klick on "about systemsettings". There is no popup of KDE_Crash_Dialog telling me that an application crashed. Neither on Neon nor on Neon unstable. 
I dont know how to get a backtrace if this popup is not in place. Is there another way? I would definitly check it out.
The strange thing: I can klick on "about konsole" or "about dolphin" and it works as it should. 
This behavior of vanishing from the screen when klicking on "about application_name" is only with systemsettings the case.
Comment 3 joergister 2017-11-25 14:18:33 UTC
well I'll try with gdb.
Comment 4 joergister 2017-11-25 17:11:21 UTC
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)
Comment 5 joergister 2017-11-25 17:15:13 UTC
Oh so sorry I need to add that this was on neon. Not neon-devel. 
(Neon-devel with wayland session does always crash in my virtualbox, neon in virtualbox aswell but ubuntu 17.10 with the new ubuntu desktop running wayland works fine in virtualbox, dont know whats the problem here)
Comment 6 Christoph Feck 2017-12-20 18:00:28 UTC
Thanks for the update; adjusting the duplicated accordingly.

*** This bug has been marked as a duplicate of bug 381630 ***