| Summary: | Crash when entring a specific command to autostart in System Settings | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Jiehong <email> |
| Component: | kcm_autostart | Assignee: | Laurent Montel <montel> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | aacid, jpwhiting, kde |
| Priority: | NOR | Flags: | jpwhiting:
gardening+
|
| Version: | 5.1.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screencast showing the issue (here in Gnome as well) | ||
|
Description
Jiehong
2014-11-13 12:57:02 UTC
This one should be fun to figure out. I was able to recreate the crash following the steps you described. Then trying with systemsettings5 in gdb it doesn't crash at all :/ I can not reproduce this crash with the following combinations systemsettings 5.4.1 + Qt 5.50 systemsettings 5.3.2 + Qt 5.4.1 Could any of you please install valgrind and then run valgring systemsettings5 in a terminal, try to reproduce the crash and add here the valgrind output? When I run systemsettings5 in valgrind here I get this after hitting OK button: [jeremy@chrom ~]$ valgrind systemsettings5 ==19048== Memcheck, a memory error detector ==19048== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==19048== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==19048== Command: systemsettings5 ==19048== Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. ==19048== Syscall param writev(vector[...]) points to uninitialised byte(s) ==19048== at 0xA97884D: ??? (in /usr/lib/libc-2.22.so) ==19048== by 0xDE6EDA8: ??? (in /usr/lib/libxcb.so.1.1.0) ==19048== by 0xDE6F19C: ??? (in /usr/lib/libxcb.so.1.1.0) ==19048== by 0xDE6F8F6: ??? (in /usr/lib/libxcb.so.1.1.0) ==19048== by 0xDE70522: ??? (in /usr/lib/libxcb.so.1.1.0) ==19048== by 0xDE705A0: xcb_wait_for_reply (in /usr/lib/libxcb.so.1.1.0) ==19048== by 0x17FFEA69: QXcbConnection::sync() (in /usr/lib/libQt5XcbQpa.so.5.5.0) ==19048== by 0x1801CB4E: QXcbWindow::requestActivateWindow() (in /usr/lib/libQt5XcbQpa.so.5.5.0) ==19048== by 0x81CBDE3: QWindow::requestActivate() (in /usr/lib/libQt5Gui.so.5.5.0) ==19048== by 0x412E2F: SettingsBase::initApplication() (SettingsBase.cpp:126) ==19048== by 0x4171F4: SettingsBase::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (moc_SettingsBase.cpp:122) ==19048== by 0x9BDEEB0: QObject::event(QEvent*) (in /usr/lib/libQt5Core.so.5.5.0) ==19048== Address 0x178a369e is 4,558 bytes inside a block of size 21,152 alloc'd ==19048== at 0x4C2AC85: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==19048== by 0xDE6E75B: xcb_connect_to_fd (in /usr/lib/libxcb.so.1.1.0) ==19048== by 0xDE72490: xcb_connect_to_display_with_auth_info (in /usr/lib/libxcb.so.1.1.0) ==19048== by 0xD5414B9: _XConnectXCB (in /usr/lib/libX11.so.6.3.0) ==19048== by 0xD5321E1: XOpenDisplay (in /usr/lib/libX11.so.6.3.0) ==19048== by 0x180013C0: QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) (in /usr/lib/libQt5XcbQpa.so.5.5.0) ==19048== by 0x1800704C: QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) (in /usr/lib/libQt5XcbQpa.so.5.5.0) ==19048== by 0x17DC423C: ??? (in /usr/lib/qt/plugins/platforms/libqxcb.so) ==19048== by 0x81B4581: QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (in /usr/lib/libQt5Gui.so.5.5.0) ==19048== by 0x81C07C1: QGuiApplicationPrivate::createPlatformIntegration() (in /usr/lib/libQt5Gui.so.5.5.0) ==19048== by 0x81C16DC: QGuiApplicationPrivate::createEventDispatcher() (in /usr/lib/libQt5Gui.so.5.5.0) ==19048== by 0x9BB3DF5: QCoreApplication::init() (in /usr/lib/libQt5Core.so.5.5.0) ==19048== Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. then it shows me a messagebox saying emacs isn't a command. On my side, running systemsettings5 with gdb does not lead to a crash nor a coredump. With valgrind either. Just launching `systemsettings5` will generate a coredump (which is 8.0 MiB in lz4, so I cannot attach it here). This is still the case with systemsettings5 5.4.1 and Qt 5.5.0 (Archlinux). I've tried a screencast for you to see. Created attachment 94730 [details]
Screencast showing the issue (here in Gnome as well)
That didn't crash though, which is the title of the bug report. Are we happy that's fixed? Rest looks like: 237137 @David: it still crashes for me though, as seen in the screencast *** This bug has been marked as a duplicate of bug 353462 *** |