[Kubuntu 9.04] Amarok crashes if an input file is given.

Bug #352811 reported by Rafael Belmonte
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: amarok

Amarok crashes when it receive an input audio file.
Command amarok file.mp3 cause amarok to crash.
When I open in Dolphin a MP3 audio file, it is expected to be open with amarok, but amarok crashes.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: amarok 2:2.0.2mysql5.1.30-0ubuntu2
ProcEnviron:
 LANGUAGE=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: amarok
Uname: Linux 2.6.28-11-generic x86_64

Revision history for this message
Rafael Belmonte (eaglescreen) wrote :
Revision history for this message
Rafael Belmonte (eaglescreen) wrote :

This is not happening always.

Revision history for this message
Rafael Belmonte (eaglescreen) wrote :

It seems that after debugging the program, it does not crash.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Since we can't reproduce this bug and there isn't a backtrace, I am closing this bug. Thanks for the report nevertheless, and if you can reproduce this bug/are able to get a backtrace, please reopen it.

Changed in amarok (Ubuntu):
status: New → Invalid
Revision history for this message
poppop (alex-popdesign-fr) wrote :

I still have this problem.

Changed in amarok (Ubuntu):
status: Invalid → New
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Could you please obtain a backtrace by following the instructions at https://wiki.kubuntu.org/Backtrace please? Thanks in advance.

Changed in amarok (Ubuntu):
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in amarok (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
poppop (alex-popdesign-fr) wrote :

The problem occurs when amarok is not started.

I obtain the following log when I do this :
1. Open a terminal
2. type amarok <path to any mp3 file>

######## LOG

amarok ./audio.mp3
Object::connect: No such signal MountPointManager::mediumConnected( int ) in /build/buildd/amarok-2.0.90mysql5.1.30/amarok-2.0.90/src/MountPointManager.cpp:91
Object::connect: (sender name: 'MountPointManager')
Object::connect: (receiver name: 'MountPointManager')
<unknown program name>(8360)/: Communication problem with "amarok" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

alex@bell:~/folder$ KCrash: Application 'amarok' crashing...
sock_file=/home/alex/.kde/socket-bell/kdeinit4__0

########################

As I do not have a debug-compiled amarok so I can't report the backtrace.
I guess the problem is the same as the one occuring when you double-click on a MP3 file in dolphin and amarok is not started.

Changed in amarok (Ubuntu):
status: Invalid → New
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Could you please obtain a backtrace by following the instructions at https://wiki.kubuntu.org/Backtrace please? Thanks in advance.
Testing with 2.1 would be welcome too.

Changed in amarok (Ubuntu):
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in amarok (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Daniele E. Domenichelli (daniele.domenichelli) wrote :
Download full text (7.6 KiB)

I'm having the same problem on Kubuntu Karmic 9.10 with ppa:kubuntu-ppa/backports enabled

gdb reports nothing...

(gdb) backtrace full
No stack.
(gdb) info registers
The program has no registers now.

Anyway here is a backtrace from crash reporting assistant:

Application: Amarok (amarok), signal: Segmentation fault
The current source language is "auto; currently c".
[Current thread is 1 (Thread 0x7ffff7eb47a0 (LWP 8498))]

Thread 5 (Thread 0x7fffe248a910 (LWP 8499)):
#0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:220
#1 0x00007fffe723fc91 in ?? () from /usr/lib/libxine.so.1
#2 0x00007fffeff4ca04 in start_thread (arg=<value optimized out>) at pthread_create.c:300
#3 0x00007ffff50a680d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4 0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7fffe0d3e910 (LWP 8500)):
[KCrash Handler]
#5 0x00007fffe725a220 in xine_post_input () from /usr/lib/libxine.so.1
#6 0x00007fffe74c59e4 in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#7 0x00007fffe74aaed2 in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#8 0x00007fffe74ab06d in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#9 0x00007fffe74adaf2 in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#10 0x00007fffe749b505 in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#11 0x00007ffff62c5efc in QApplicationPrivate::notify_helper (this=0x752140, receiver=0x8c5820, e=0xa52320) at kernel/qapplication.cpp:4056
#12 0x00007ffff62cd1ce in QApplication::notify (this=0x7fffffffc360, receiver=0x8c5820, e=0xa52320) at kernel/qapplication.cpp:4021
#13 0x00007ffff72498ea in App::notify (this=0x0, receiver=0x7fffe74d5db9, event=0x867cb0) at /build/buildd/amarok-2.2.2/src/App.cpp:856
#14 0x00007ffff59a1c2c in QCoreApplication::notifyInternal (this=0x7fffffffc360, receiver=0x8c5820, event=0xa52320) at kernel/qcoreapplication.cpp:610
#15 0x00007ffff59a280a in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x8c5920) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#16 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x8c5920) at kernel/qcoreapplication.cpp:1247
#17 0x00007ffff59ca533 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#18 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210
#19 0x00007fffee639bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#20 0x00007fffee63d598 in ?? () from /lib/libglib-2.0.so.0
#21 0x00007fffee63d6c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#22 0x00007ffff59ca1a6 in QEventDispatcherGlib::processEvents (this=0x8c5ac0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#23 0x00007ffff59a0532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#24 0x00007ffff59a0904 in QEventLoop::exec (this=0x7fffe0d3dfb0, flags=) at kernel/qeventloop.cpp:201
#25 0x00007ffff58b86cb in QThread:...

Read more...

Changed in amarok (Ubuntu):
status: Invalid → New
Revision history for this message
Daniele E. Domenichelli (daniele.domenichelli) wrote :

I found that amarok works for a user and doesn't work for another, so I made some testing:

- Create a new user -> Amarok works

On user that was crashing

- remove amarok cofig files -> nothing changes
- remove .kde folder -> nothing changes
- remove .xine folder -> Amarok works again...

So it must be a xine related problem

but then, after running amarok, restoring the old .xine folder, doesn't crash anymore.

Anyway a quick fix for people having this issue could be deleting the .xine folder in home directory

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Please file a separate bug report at bugs.kde.org against phonon. It is unlikely that this and the original crash are related.

Changed in amarok (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.