can't get a crash report while amarok crashes.

Code: Select all

amarok -v
 Qt: 4.5.3
 KDE: 4.3.3 (KDE 4.3.3) "release 1"
(same error with KDE: 4.3.2 (KDE 4.3.2) "release 5")
 Amarok: 2.2.0
openSuse 11.1
rpm -qa amarok*
 amarok-lang-2.2.0-38.2
 amarok-debuginfo-2.2.0-38.2
 amarok-2.2.0-38.2
(same error with amarok-2.2.0-44.2)


Starting Amarok i see the splash screen and after that nothing happens.
Staring amarok from a shell i see many! lines:

Code: Select all

QObject::setParent: Cannot set parent, new parent is in a different thread

There is no KDE Crash Dialog.

Starting amarok with the gnu debugger gdb i get the same error
QObject::setParent: Cannot set parent, new parent is in a different thread
and have to Ctrl-C to get the gdb prompt.
Then at the gdb prompt giving the backtrace command: no stack.

Any ideas?

Edit 14.11.2009:
The error was in /home/r006/.kde4/share/apps/amarok/current.xspf
i have had this title
<track>
<location>http://metafiles.gl-systemhaus.de/hr/hrinfo_1.asx</location>

<identifier>http://metafiles.gl-systemhaus.de/hr/hrinfo_1.asx</identifier>
<title>HR info</title>
<creator>Hessischer Rundfunk</creator>
</track>
After removing this entry. Voila.. amarok works fine again.

But don't know why.


Regards
rws

"gdb amarok --args nofork"
"run"
[...wait for crash]
"thread apply all bt"


Then show us the output.

Thank you for your reply Mark,

i did:

Code: Select all

~> gdb amarok
(gdb) run --nofork
.
.
(many times this:)
QObject::setParent: Cannot set parent, new parent is in a different thread             

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa1314b90 (LWP 6103)]         
0xb65abf80 in vfprintf () from /lib/libc.so.6       
(gdb) thread apply all bt                           

Thread 19 (Thread 0xa02ceb90 (LWP 6108)):
#0  0xffffe430 in __kernel_vsyscall ()   
#1  0xb6507f62 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb664bb84 in pthread_cond_timedwait () from  lib/libc.so.6                   
#3  0xb719a57c in QWaitCondition::wait (this=0xa72dcd80, mutex=0xa72dcd7c, time=30000) at thread/qwaitcondition_unix.cpp:85                                             
#4  0xb718fbb6 in QThreadPoolThread::run (this=0xa9332118)                           
    at concurrent/qthreadpool.cpp:140                                                 
#5  0xb7199592 in QThreadPrivate::start (arg=0xa9332118)                             
    at thread/qthread_unix.cpp:188                                                   
#6  0xb65041b5 in start_thread () from /lib/libpthread.so.0                           
#7  0xb663f3ae in clone () from /lib/libc.so.6                                       


Thread 18 (Thread 0xa0b13b90 (LWP 6104)):
#0  0xffffe430 in __kernel_vsyscall ()   
#1  0xb6638401 in select () from /lib/libc.so.6
#2  0xb726b637 in QProcessManager::run (this=0x812c780) at io/qprocess_unix.cpp:296
#3  0xb7199592 in QThreadPrivate::start (arg=0x812c780) at thread/qthread_unix.cpp:188
#4  0xb65041b5 in start_thread () from /lib/libpthread.so.0                           
#5  0xb663f3ae in clone () from /lib/libc.so.6                                       

Thread 17 (Thread 0xa1314b90 (LWP 6103)):
#0  0xb65abf80 in vfprintf () from /lib/libc.so.6
#1  0xb65b0e00 in ?? () from /lib/libc.so.6     
---Type <return> to continue, or q <return> to quit---
#2  0xb65ac226 in vfprintf () from /lib/libc.so.6
#3  0xb665284e in __fprintf_chk () from /lib/libc.so.6
#4  0xb71912b9 in qt_message_output (msgType=QtWarningMsg,
    buf=0xa72d8d18 [color=#FF0000]"QObject::setParent: Cannot set parent, new parent is in a different thread"[/color]) at /usr/include/bits/stdio2.h:99
#5  0xb7191601 in qWarning (
    msg=0xb73287dc [color=#FF0000]"QObject::setParent: Cannot set parent, new parent is in a different thread"[/color]) at global/qglobal.cpp:2137
#6  0xb729d23c in QObjectPrivate::setParent_helper (this=0x88792c0, o=0x827a198)
    at kernel/qobject.cpp:1882
#7  0xb6973862 in QWidgetPrivate::setParent_sys (this=0x88792c0, parent=0x827a198, f=
      {i = -1598980728}) at kernel/qwidget_x11.cpp:1054
#8  0xb6938e50 in QWidget::setParent (this=0x880ddb0, parent=0x827a198, f=
      {i = -1598980672}) at kernel/qwidget.cpp:9220
#9  0xb693961e in QWidget::setParent (this=0xa0b17438, parent=0xa0b17438)
    at kernel/qwidget.cpp:9177
#10 0xb690d06f in QLayout::addChildWidget (this=0x8556788, w=0x880ddb0)
    at kernel/qlayout.cpp:972
#11 0xb68ee2ad in QBoxLayout::insertWidget (this=0x8556788, index=-1,
    widget=0x880ddb0, stretch=0, alignment={i = -1598980432})
    at kernel/qboxlayout.cpp:1025
#12 0xb68ee4a2 in QBoxLayout::addWidget (this=0x8556788, widget=0x880ddb0, stretch=0,
    alignment={i = -1598980376}) at kernel/qboxlayout.cpp:1092
#13 0xb7e8a1d1 in KHBox::childEvent(QChildEvent*) () from /usr/lib/libkdeui.so.5
#14 0xb729de77 in QObject::event (this=0x827a198, e=0xa0b18408)
    at kernel/qobject.cpp:1090
#15 0xb6934c60 in QWidget::event (this=0x827a198, event=0xa0b18408)
    at kernel/qwidget.cpp:7951
#16 0xb6cc59b3 in QFrame::event (this=0x827a198, e=0xa0b18408)
    at widgets/qframe.cpp:559
#17 0xb68de76c in QApplicationPrivate::notify_helper (this=0x813a000,
    receiver=0x827a198, e=0xa0b18408) at kernel/qapplication.cpp:4065
#18 0xb68e6b42 in QApplication::notify (this=0xbfffe8c4, receiver=0x827a198,
    e=0xa0b18408) at kernel/qapplication.cpp:4030
#19 0xb7dbe82d in KApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libkdeui.so.5
#20 0xb728d8fb in QCoreApplication::notifyInternal (this=0xbfffe8c4,
    receiver=0x827a198, event=0xa0b18408) at kernel/qcoreapplication.cpp:610
#21 0xb6939413 in QWidget::setParent (this=0x880ddb0, parent=0x827a198, f=
      {i = -1598978976}) at ../../src/corelib/kernel/qcoreapplication.h:213
#22 0xb693961e in QWidget::setParent (this=0xa0b17438, parent=0xa0b17438)
    at kernel/qwidget.cpp:9177
#23 0xb690d06f in QLayout::addChildWidget (this=0x8556788, w=0x880ddb0)
    at kernel/qlayout.cpp:972
#24 0xb68ee2ad in QBoxLayout::insertWidget (this=0x8556788, index=-1,
    widget=0x880ddb0, stretch=0, alignment={i = -1598978736})
    at kernel/qboxlayout.cpp:1025
#25 0xb68ee4a2 in QBoxLayout::addWidget (this=0x8556788, widget=0x880ddb0, stretch=0,
    alignment={i = -1598978680}) at kernel/qboxlayout.cpp:1092
#26 0xb7e8a1d1 in KHBox::childEvent(QChildEvent*) () from /usr/lib/libkdeui.so.5
#27 0xb729de77 in QObject::event (this=0x827a198, e=0xa0b18aa8)
    at kernel/qobject.cpp:1090
#28 0xb6934c60 in QWidget::event (this=0x827a198, event=0xa0b18aa8)
    at kernel/qwidget.cpp:7951
#29 0xb6cc59b3 in QFrame::event (this=0x827a198, e=0xa0b18aa8)
    at widgets/qframe.cpp:559
#30 0xb68de76c in QApplicationPrivate::notify_helper (this=0x813a000,
    receiver=0x827a198, e=0xa0b18aa8) at kernel/qapplication.cpp:4065
#31 0xb68e6b42 in QApplication::notify (this=0xbfffe8c4, receiver=0x827a198,
    e=0xa0b18aa8) at kernel/qapplication.cpp:4030
#32 0xb7dbe82d in KApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libkdeui.so.5
#33 0xb728d8fb in QCoreApplication::notifyInternal (this=0xbfffe8c4,
    receiver=0x827a198, event=0xa0b18aa8) at kernel/qcoreapplication.cpp:610
#34 0xb6939413 in QWidget::setParent (this=0x880ddb0, parent=0x827a198, f=
      {i = -1598977280}) at ../../src/corelib/kernel/qcoreapplication.h:213
#35 0xb693961e in QWidget::setParent (this=0xa0b17438, parent=0xa0b17438)
    at kernel/qwidget.cpp:9177
#36 0xb690d06f in QLayout::addChildWidget (this=0x8556788, w=0x880ddb0)
    at kernel/qlayout.cpp:972
#37 0xb68ee2ad in QBoxLayout::insertWidget (this=0x8556788, index=-1,
    widget=0x880ddb0, stretch=0, alignment={i = -1598977040})
    at kernel/qboxlayout.cpp:1025
#38 0xb68ee4a2 in QBoxLayout::addWidget (this=0x8556788, widget=0x880ddb0, stretch=0,
    alignment={i = -1598976984}) at kernel/qboxlayout.cpp:1092
#39 0xb7e8a1d1 in KHBox::childEvent(QChildEvent*) () from /usr/lib/libkdeui.so.5
#40 0xb729de77 in QObject::event (this=0x827a198, e=0xa0b19148)
    at kernel/qobject.cpp:1090


(In Thread 17 the red text is marked by me).

I stopped this at #1663, because every about 7 # i have gdb to continue
(---Type <return> to continue, or q <return> to quit---).

Can you see something? Or should i post more of this?

Regards
rws

What we would be interested in is the thread with the CrashHandler, which is often one of the lower threads.
It usually starts with:

Code: Select all

Thread # (thread blah blah):
CrashHandler

Mararok, is the way i'm doing ok so far?
Is there a way to tell gdb not to stop every some # ?
It'hard to it this way (keep gdb busy).

Regards
rws

I can't make sense of your backtrace. Please do this, then paste here:

Code: Select all

"amarok -m -d --nofork" &> amarok_debug.txt


Hi markey,

i do ~> amarok -m -d --nofork &> amarok_debug.txt

But the file is far to long (about 470kB) to post. How can i upload the file?

Regards
rws

use bzip2 to compress it or put it in a pastebin and give the URL here.
You could also file a bug report to
https://bugs.kde.org/enter_bug.cgi?product=amarok
and attach the text file there. The forum is not the best place for that I admit.

So i can't do an attachment to may posts? (Mamarok, you dont tell me how to do it. That was my last question).

So i opened a bugreport https://bugs.kde.org/show_bug.cgi?id=214024
and put the file here https://bugs.kde.org/attachment.cgi?id=38237

Should we follow-up here or have i to wait about replies from bugzilla?

Regards
rws

@rws: Due to server side space limitations and security issues users are not permitted to post attachments on the forums.

I'm getting the same error. I have amarok-dbg installed. I tried to run amarok with

Code: Select all

amarok --debug

and I wasn't able to get a backtrace.

I also attempted to run gdb against amarok as follows

Code: Select all

gdb amarok

and then get a backtrace. However, this too did not work.

As such, I am only able to run amarok using admin privileges (e.g. sudo amarok).

Does anyone know why this error occurs?

@Progmanos you could try with running the following:

Code: Select all

amarok -d --nofork

Also a bit more details on your exact Amarok version and distribution you are running would be helpful.

progmanos wrote:I'm getting the same error. I have amarok-dbg installed. I tried to run amarok with

Code: Select all

amarok --debug

and I wasn't able to get a backtrace.

I also attempted to run gdb against amarok as follows

Code: Select all

gdb amarok

and then get a backtrace. However, this too did not work.

As such, I am only able to run amarok using admin privileges (e.g. sudo amarok).

Does anyone know why this error occurs?

Code: Select all

gdb amarok --args nofork

Since you have been using sudo to run Amarok, the privileges for ~/.kde4 are likely hosed. Run the following command to repair them:

Code: Select all

sudo chown -R $(id -un):$(id -gn) /home/$(id -un)/.kde*