Amarok 2.0.1 crashed with SIGSEGV

Bug #316126 reported by Bugger_man
8
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

OS: Ubuntu 8.10

I updated Amarok 1.4.5 to 2.0.1. After installation Amarok only show starting picture and after that it crash. I asked from developers is this a Amarok issue but developers said that problem is in other component. What component might cause a problem?

Link to Amarok developers thread: http://bugs.kde.org/show_bug.cgi?id=180219

Command line info:

user@ubuntu:~$ amarok
amarok(13076) Phonon::KdePlatformPlugin::createBackend: using backend: "Xine"
Object::connect: No such slot MainWindow::showStatistics()
Object::connect: (receiver name: 'MainWindow')
QLayout: Attempting to add QLayout "" to MainWindow "MainWindow", which already has a layout
<unknown program name>(13075)/: 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)" "

Crash info:

Application: Amarok (amarok), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb49106c0 (LWP 12959)]
[New Thread 0xb0be3b90 (LWP 12972)]
[New Thread 0xb13e4b90 (LWP 12971)]
[New Thread 0xb1de6b90 (LWP 12970)]
[New Thread 0xb2849b90 (LWP 12964)]
[KCrash handler]
#6 0xb64525f7 in ?? () from /usr/lib/libQtSvg.so.4
#7 0xb645a097 in ?? () from /usr/lib/libQtSvg.so.4
#8 0xb645a72d in ?? () from /usr/lib/libQtSvg.so.4
#9 0xb646ae53 in QSvgTinyDocument::load () from /usr/lib/libQtSvg.so.4
#10 0xb646ca6a in QSvgRenderer::load () from /usr/lib/libQtSvg.so.4
#11 0xb646f47e in QGraphicsSvgItem::QGraphicsSvgItem ()
   from /usr/lib/libQtSvg.so.4
#12 0xb6eb32b2 in MainControlsWidget (this=0x9902d28, parent=0x93a0c50)
    at /build/buildd/amarok-kde4-2.0.1.1/src/widgets/MainControlsWidget.cpp:55
#13 0xb6eb4109 in MainToolbar (this=0x9914d98, parent=0x0)
    at /build/buildd/amarok-kde4-2.0.1.1/src/widgets/MainToolbar.cpp:60
#14 0xb6e05d1c in MainWindow::init (this=0x93bb588)
    at /build/buildd/amarok-kde4-2.0.1.1/src/MainWindow.cpp:194
#15 0xb6df0202 in App::continueInit (this=0xbfd26324)
    at /build/buildd/amarok-kde4-2.0.1.1/src/App.cpp:553
#16 0xb6df362c in App (this=0xbfd26324)
    at /build/buildd/amarok-kde4-2.0.1.1/src/App.cpp:182
#17 0x0804c033 in main (argc=1, argv=0xbfd26824)
    at /build/buildd/amarok-kde4-2.0.1.1/src/main.cpp:128
#0 0xb8026430 in __kernel_vsyscall ()

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

You could try purging amarok-kde4 and reinstalling. (sudo apt-get purge amarok-kde4, then sudo apt-get install amarok-kde4)
It could be something like a bad configuration file or a corrupted svg cache.

Changed in amarok:
status: New → Incomplete
Revision history for this message
Bugger_man (ville-jokela-gmail) wrote : Re: [Bug 316126] Re: Amarok 2.0.1 crashed with SIGSEGV

Hi,

I made as you suggested. When I start the program I can see a starting
picture but after it nothing. There is no SIGSEGV message. Any other
suggestions?

On Sun, 2009-02-01 at 15:08 +0000, Jonathan Thomas wrote:
> You could try purging amarok-kde4 and reinstalling. (sudo apt-get purge amarok-kde4, then sudo apt-get install amarok-kde4)
> It could be something like a bad configuration file or a corrupted svg cache.
>
> ** Changed in: amarok (Ubuntu)
> Status: New => Incomplete
>

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

Nope, I don't have a clue what's wrong. :(

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

Is this still a problem with Amarok 2.0.2?

Changed in amarok (Ubuntu):
status: New → Incomplete
tags: removed: amarok crash
Revision history for this message
Bugger_man (ville-jokela-gmail) wrote :

Nope, Amarok 2.0.2 works fine with ubuntu 9.04. In my point of view this
bug can be closed.

On Fri, 2009-04-24 at 02:17 +0000, Jonathan Thomas wrote:
> Is this still a problem with Amarok 2.0.2?
>
> ** Changed in: amarok (Ubuntu)
> Status: New => Incomplete
>
> ** Tags removed: amarok crash
>

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

Great. Otherwise I don't know what we would have done...

Changed in amarok (Ubuntu):
status: Incomplete → Fix Released
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.