[Bug 288135] New: KDE Startup Crash
Alex Muravya
asmpub at sfw.su
Sat Dec 3 14:37:24 GMT 2011
https://bugs.kde.org/show_bug.cgi?id=288135
Summary: KDE Startup Crash
Product: kdelibs
Version: unspecified
Platform: Archlinux Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: kded
AssignedTo: unassigned-bugs at kde.org
ReportedBy: asmpub at sfw.su
Application: kded4 ($Id$)
KDE Platform Version: 4.7.3 (4.7.3)
Qt Version: 4.7.4
Operating System: Linux 3.0-ARCH x86_64
Distribution (Platform): Archlinux Packages
-- Information about the crash:
- What I was doing when the application crashed:
Started KDE. This bug occures every time I start KDE. Status is 6:Aborted. But
there's no abort from user happens.
The crash can be reproduced every time.
-- Backtrace:
Application: KDE Daemon (kdeinit4), signal: Aborted
[Current thread is 1 (Thread 0x7f5b8b75b760 (LWP 994))]
Thread 3 (Thread 0x7f5b72600700 (LWP 1046)):
#0 0x00007f5b85e1d42a in g_main_context_acquire () from
/usr/lib/libglib-2.0.so.0
#1 0x00007f5b85e1eb21 in ?? () from /usr/lib/libglib-2.0.so.0
#2 0x00007f5b85e1f532 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#3 0x00007f5b728c3456 in ?? () from /usr/lib/libgio-2.0.so.0
#4 0x00007f5b85e44026 in ?? () from /usr/lib/libglib-2.0.so.0
#5 0x00007f5b8a03bdf0 in start_thread () from /lib/libpthread.so.0
#6 0x00007f5b88deb39d in clone () from /lib/libc.so.6
#7 0x0000000000000000 in ?? ()
Thread 2 (Thread 0x7f5b71bf3700 (LWP 1047)):
#0 0xffffffffff60017b in ?? ()
#1 0x00007f5b71bf2b10 in ?? ()
#2 0x00007fffe97c27e7 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 1 (Thread 0x7f5b8b75b760 (LWP 994)):
[KCrash Handler]
#6 0x00007f5b88d4b965 in raise () from /lib/libc.so.6
#7 0x00007f5b88d4cddb in abort () from /lib/libc.so.6
#8 0x00007f5b88d447ae in ?? () from /lib/libc.so.6
#9 0x00007f5b88d44852 in __assert_fail () from /lib/libc.so.6
#10 0x00007f5b6ac63afb in snd_hctl_handle_events () from
/usr/lib/libasound.so.2
#11 0x00007f5b6ac6e899 in snd_mixer_handle_events () from
/usr/lib/libasound.so.2
#12 0x00007f5b6af2c68d in ?? () from /usr/lib/kde4/kded_kmixd.so
#13 0x00007f5b6af3eda7 in ?? () from /usr/lib/kde4/kded_kmixd.so
#14 0x00007f5b6af3ed0d in ?? () from /usr/lib/kde4/kded_kmixd.so
#15 0x00007f5b8a3c318e in QObject::event(QEvent*) () from
/usr/lib/libQtCore.so.4
#16 0x00007f5b89565ae4 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQtGui.so.4
#17 0x00007f5b8956a951 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQtGui.so.4
#18 0x00007f5b8b147bb6 in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#19 0x00007f5b8a3ac89c in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQtCore.so.4
#20 0x00007f5b8a3afc2f in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQtCore.so.4
#21 0x00007f5b8a3d71a3 in ?? () from /usr/lib/libQtCore.so.4
#22 0x00007f5b85e1e7fd in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#23 0x00007f5b85e1eff8 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x00007f5b85e1f1c9 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#25 0x00007f5b8a3d7606 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#26 0x00007f5b89608eee in ?? () from /usr/lib/libQtGui.so.4
#27 0x00007f5b8a3aba92 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQtCore.so.4
#28 0x00007f5b8a3abc97 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQtCore.so.4
#29 0x00007f5b8a3afeab in QCoreApplication::exec() () from
/usr/lib/libQtCore.so.4
#30 0x00007f5b79cced65 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#31 0x00000000004082a7 in _start ()
This bug may be a duplicate of or related to bug 287024.
Possible duplicates by query: bug 287877, bug 287024, bug 286082, bug 285389,
bug 284963.
Reported using DrKonqi
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list