Bug 359665 - drkonqui crash with core dump
Summary: drkonqui crash with core dump
Status: RESOLVED UPSTREAM
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: 5.5.4
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-22 11:52 UTC by Fabio Coatti
Modified: 2019-06-14 14:35 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 Fabio Coatti 2016-02-22 11:52:44 UTC
Hi all, I'm getting several core dumps from drkonqui; I don't know when it is fired up or by which app. The only other core dump I have in my dir refers to xembedsniproxy (already reported).
Below you can find a backtrace from core dump, even if I don't know if this can be useful to debug the issue. If more info can be useful, just let me know.

Thanks.

Reproducible: Always




Core was generated by `/usr/lib64/libexec/drkonqi -platform xcb -display :0 --appname klauncher --appp'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007f60e1429308 in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x00007f60e1429308 in raise () from /lib64/libc.so.6
#1  0x00007f60e142a75a in abort () from /lib64/libc.so.6
#2  0x00007f60e1ba2cc9 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5
#3  0x00007f60da4c2464 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007f60da4c7c5d in QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from /usr/lib64/libQt5XcbQpa.so.5
#5  0x00007f60e4a7b30d in ?? () from /usr/lib64/qt5/plugins/platforms/libqxcb.so
#6  0x00007f60e20124b2 in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) ()
   from /usr/lib64/libQt5Gui.so.5
#7  0x00007f60e201cb33 in QGuiApplicationPrivate::createPlatformIntegration() () from /usr/lib64/libQt5Gui.so.5
#8  0x00007f60e201dabd in QGuiApplicationPrivate::createEventDispatcher() () from /usr/lib64/libQt5Gui.so.5
#9  0x00007f60e1cdf514 in QCoreApplication::init() () from /usr/lib64/libQt5Core.so.5
#10 0x00007f60e1cdf596 in QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) () from /usr/lib64/libQt5Core.so.5
#11 0x00007f60e2020009 in QGuiApplication::QGuiApplication(QGuiApplicationPrivate&) () from /usr/lib64/libQt5Gui.so.5
#12 0x00007f60e27ec34d in QApplication::QApplication(int&, char**, int) () from /usr/lib64/libQt5Widgets.so.5
#13 0x0000000000433cc9 in main (argc=11, argv=0x7ffc00a09b78)
    at /usr/src/debug/kde-plasma/plasma-workspace-5.5.4/plasma-workspace-5.5.4/drkonqi/main.cpp:59
Comment 1 Harald Sitter 2019-06-14 14:35:10 UTC
The Qt XCB backend seems to fail to start up. Unfortunately the backtrace on its own isn't too useful, so I doubt anyone will be able to figure out what went wrong years after the fact.