Bug 296847 - KMixCtrl crash upon system startup
Summary: KMixCtrl crash upon system startup
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdecore (show other bugs)
Version: 4.7
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-26 23:58 UTC by Joseph Yaroch
Modified: 2018-11-29 09:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Yaroch 2012-03-26 23:58:01 UTC
Application: kmixctrl (3.9)
KDE Platform Version: 4.7.2 (4.7.2) "release 5"
Qt Version: 4.7.4
Operating System: Linux 3.1.9-1.4-desktop i686
Distribution: "openSUSE 12.1 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
The application crashed during the course of a noraml system startup.  This occurred prior to any user input.

-- Backtrace:
Application: KMixCtrl (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5804710 (LWP 3860))]

Thread 2 (Thread 0xb0086b70 (LWP 3875)):
#0  0xb607fbb4 in poll () from /lib/libc.so.6
#1  0xb5a8cf7b in g_poll () from /usr/lib/libglib-2.0.so.0
#2  0xb5a7e466 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0xb5a7e7fa in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#4  0xb6e678a7 in QEventDispatcherGlib::processEvents (this=0xaf700478, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0xb6e3845d in QEventLoop::processEvents (this=0xb0086200, flags=...) at kernel/qeventloop.cpp:149
#6  0xb6e386a1 in QEventLoop::exec (this=0xb0086200, flags=...) at kernel/qeventloop.cpp:201
#7  0xb6d3b75b in QThread::exec (this=0x815c788) at thread/qthread.cpp:498
#8  0xb6e1909d in QInotifyFileSystemWatcherEngine::run (this=0x815c788) at io/qfilesystemwatcher_inotify.cpp:248
#9  0xb6d3e613 in QThreadPrivate::start (arg=0x815c788) at thread/qthread_unix.cpp:331
#10 0xb2254a9c in ?? () from /usr/X11R6/lib/libGL.so.1
#11 0x00000000 in ?? ()

Thread 1 (Thread 0xb5804710 (LWP 3860)):
[KCrash Handler]
#6  0xb70641e0 in deref (this=<optimized out>) at /usr/include/QtCore/qatomic_i386.h:132
#7  ~QString (this=0x810d040, __in_chrg=<optimized out>) at /usr/include/QtCore/qstring.h:883
#8  ~Area (this=0x810d030, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.7.2/kdecore/io/kdebug.cpp:203
#9  ~QHashNode (this=0x810d028, __in_chrg=<optimized out>) at /usr/include/QtCore/qhash.h:254
#10 QHash<unsigned int, KDebugPrivate::Area>::deleteNode2 (node=0x810d028) at /usr/include/QtCore/qhash.h:519
#11 0xb6d5cb9a in QHashData::free_helper (this=0x80eb4a8, node_delete=0xb70641a0 <QHash<unsigned int, KDebugPrivate::Area>::deleteNode2(QHashData::Node*)>) at tools/qhash.cpp:271
#12 0xb705f92d in freeData (x=<optimized out>, this=<optimized out>) at /usr/include/QtCore/qhash.h:568
#13 ~QHash (this=0x80e4524, __in_chrg=<optimized out>) at /usr/include/QtCore/qhash.h:284
#14 ~KDebugPrivate (this=0x80e4518, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.7.2/kdecore/io/kdebug.cpp:248
#15 destroy () at /usr/src/debug/kdelibs-4.7.2/kdecore/io/kdebug.cpp:702
#16 0xb7007459 in KCleanUpGlobalStatic::~KCleanUpGlobalStatic (this=0xb724417c, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.7.2/kdecore/kernel/kglobal.h:62
#17 0xb5fe5931 in __run_exit_handlers () from /lib/libc.so.6
#18 0xb5fe59bd in exit () from /lib/libc.so.6
#19 0x0804fbd5 in _start ()

Reported using DrKonqi
Comment 1 Christian Esken 2012-03-27 20:27:39 UTC
This looks like a general KDE issue. I see similar (crash within KCleanUpGlobalStatic::~KCleanUpGlobalStatic) bug reports for other applications as well, like Bug 257651 and Bug 274169 . There is no KMix referenced in the stack trace and the crash location seems to  clean up KDebugPrivate objetcs. Thus I'll assign this over to kdelibs
Comment 2 Andrew Crouthamel 2018-10-29 22:21:00 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-13 14:37:24 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
mark the bug 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 Bug Janitor Service 2018-11-29 09:38:47 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!