Bug 794955 - f17 alpha tc2 KDE Daemon (kdeinit4), signal: Segmentation fault
Summary: f17 alpha tc2 KDE Daemon (kdeinit4), signal: Segmentation fault
Keywords:
Status: CLOSED DUPLICATE of bug 805308
Alias: None
Product: Fedora
Classification: Fedora
Component: kdelibs
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-18 04:44 UTC by Reartes Guillermo
Modified: 2012-05-14 18:02 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-05-14 18:02:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
messages suspend (at the end) (209.77 KB, application/octet-stream)
2012-02-18 04:44 UTC, Reartes Guillermo
no flags Details


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 284052 0 None None None Never

Description Reartes Guillermo 2012-02-18 04:44:12 UTC
Created attachment 564039 [details]
messages suspend (at the end)

Description of problem:

After suspending the KDE live-cd alpha tc2:


Application: KDE Daemon (kdeinit4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6762ae7880 (LWP 2053))]

Thread 3 (Thread 0x7f673e63a700 (LWP 2062)):
#0  0x00007f676113906d in read () from /lib64/libpthread.so.0
#1  0x00007f675bcd8d5f in ?? () from /lib64/libglib-2.0.so.0
#2  0x00007f675bc9de9a in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x00007f675bc9e392 in ?? () from /lib64/libglib-2.0.so.0
#4  0x00007f675bc9e514 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#5  0x00007f67614e9976 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#6  0x00007f67614ba82f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#7  0x00007f67614baab8 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#8  0x00007f67613bf588 in QThread::exec() () from /lib64/libQtCore.so.4
#9  0x00007f676149b67f in ?? () from /lib64/libQtCore.so.4
#10 0x00007f67613c24cb in ?? () from /lib64/libQtCore.so.4
#11 0x00007f6761132d24 in start_thread () from /lib64/libpthread.so.0
#12 0x00007f675f75951d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f673685a700 (LWP 2077)):
#0  0x00007f675f750a9f in poll () from /lib64/libc.so.6
#1  0x00007f675bc9e3f6 in ?? () from /lib64/libglib-2.0.so.0
#2  0x00007f675bc9e83a in g_main_loop_run () from /lib64/libglib-2.0.so.0
#3  0x00007f67499a2566 in ?? () from /lib64/libgio-2.0.so.0
#4  0x00007f675bcc07f5 in ?? () from /lib64/libglib-2.0.so.0
#5  0x00007f6761132d24 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f675f75951d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f6762ae7880 (LWP 2053)):
[KCrash Handler]
#5  0x0000000001eb5050 in ?? ()
#6  0x00007f67614cdcc2 in QObject::property(char const*) const () from /lib64/libQtCore.so.4
#7  0x00007f6761835c8c in ?? () from /lib64/libQtDBus.so.4
#8  0x00007f6761836966 in ?? () from /lib64/libQtDBus.so.4
#9  0x00007f6761836a5b in ?? () from /lib64/libQtDBus.so.4
#10 0x00007f67614d00ee in QObject::event(QEvent*) () from /lib64/libQtCore.so.4
#11 0x00007f67606512dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQtGui.so.4
#12 0x00007f676065585a in QApplication::notify(QObject*, QEvent*) () from /lib64/libQtGui.so.4
#13 0x00007f67624d3a46 in KApplication::notify(QObject*, QEvent*) () from /lib64/libkdeui.so.5
#14 0x00007f67614bb82e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQtCore.so.4
#15 0x00007f67614befb1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQtCore.so.4
#16 0x00007f67614e97c3 in ?? () from /lib64/libQtCore.so.4
#17 0x00007f675bc9e04c in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#18 0x00007f675bc9e3a1 in ?? () from /lib64/libglib-2.0.so.0
#19 0x00007f675bc9e514 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#20 0x00007f67614e9956 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#21 0x00007f67606f0c0e in ?? () from /lib64/libQtGui.so.4
#22 0x00007f67614ba82f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#23 0x00007f67614baab8 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#24 0x00007f67614bf2fc in QCoreApplication::exec() () from /lib64/libQtCore.so.4
#25 0x00007f6744bfd4e0 in kdemain () from /usr/lib64/libkdeinit4_kded4.so
#26 0x0000000000408202 in _start ()


Version-Release number of selected component (if applicable):



How reproducible:

sometimes

Steps to Reproduce:
1. boot 
2. suspend
3. resume
  
Additional info:

video es intel arrandale gma

Comment 1 Kevin Kofler 2012-02-18 09:27:08 UTC
I think we need a backtrace with at least qt-debuginfo installed to know more about this, possibly also kdelibs-debuginfo.

Comment 2 Rex Dieter 2012-05-14 18:02:35 UTC

*** This bug has been marked as a duplicate of bug 805308 ***


Note You need to log in before you can comment on or make changes to this bug.