Bug 213287 - Konsole crashed from GNU Screen
Summary: Konsole crashed from GNU Screen
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-11-05 18:59 UTC by Toby Newman
Modified: 2018-10-21 04:37 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 Toby Newman 2009-11-05 18:59:50 UTC
Application that crashed: konsole
Version of the application: 2.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Konsole was running GNU Screen. I was afk, and connected to the screen session from another PC. When i returned, konsole had crashed

 -- Backtrace:
Application: Konsole (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  QList<QObject*>::indexOf (this=0x9012d50, o=0x0) at ../../include/QtCore/../../src/corelib/tools/qlist.h:637
#7  QObjectPrivate::setParent_helper (this=0x9012d50, o=0x0) at kernel/qobject.cpp:1866
#8  0x0078d851 in ~QObject (this=0x90125c8, __in_chrg=<value optimized out>) at kernel/qobject.cpp:846
#9  0x00790d9d in ~QSocketNotifier (this=0x90125c8, __in_chrg=<value optimized out>) at kernel/qsocketnotifier.cpp:228
#10 0x0078546f in QObjectPrivate::deleteChildren (this=0x8fd2898) at kernel/qobject.cpp:1847
#11 0x0078d7cf in ~QObject (this=0x8fd2820, __in_chrg=<value optimized out>) at kernel/qobject.cpp:836
#12 0x005a0ff6 in ~QDBusConnectionPrivate (this=0x8fd2820, __in_chrg=<value optimized out>) at qdbusintegrator.cpp:958
#13 0x0059b934 in QDBusConnectionPrivate::deleteYourself (this=0x8fd2820) at qdbusintegrator.cpp:970
#14 0x00592ea0 in ~QDBusConnection (this=0x90125c8, __in_chrg=<value optimized out>) at qdbusconnection.cpp:287
#15 0x00596f4f in ~QDBusDefaultConnection (this=0x5f6538, __in_chrg=<value optimized out>) at qdbusconnection.cpp:957
#16 ~QGlobalStaticDeleter (this=0x5f6538, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1632
#17 0x0047005f in ?? () from /lib/tls/i686/cmov/libc.so.6
#18 0x004700cf in exit () from /lib/tls/i686/cmov/libc.so.6
#19 0x0804dde9 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=1, envs=0x8f8baac "DISPLAY=:1.0", reset_env=false, tty=0x0, 
    avoid_loops=false, startup_id_str=0x8f8babd "Coolerflower;1257437328;144139;22970_TIME160887464") at ../../kinit/kinit.cpp:677
#20 0x0804ea35 in handle_launcher_request (sock=<value optimized out>, who=<value optimized out>) at ../../kinit/kinit.cpp:1169
#21 0x0804eeac in handle_requests (waitForPid=<value optimized out>) at ../../kinit/kinit.cpp:1362
#22 0x0804fbaf in main (argc=2, argv=0xbf820354, envp=0xbf820360) at ../../kinit/kinit.cpp:1793

Reported using DrKonqi
Comment 1 Dario Andres 2009-11-11 03:04:07 UTC
Weird crash, it doesn't seem to have Konsole functions in the backtrace so I don't know if the developers can do something about it. It could be a Qt bug (dbus related). 

Could you try at least to repeat the situation for some time and see if it happens again ?

Thanks
Comment 2 Dario Andres 2009-12-20 20:47:09 UTC
Waiting for feedback. Marking as NEEDSINFO.
Comment 3 Andrew Crouthamel 2018-09-20 03:06:57 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-21 04:37:38 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!