Crash on launch in QPaintDevice::~QPaintDevice ()

Bug #91552 reported by gumpish
8
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: amarok

Just launched it from the Applications menu and it instantly produced a crash, no window was ever displayed.

Revision history for this message
gumpish (launchpad-5-gumpish) wrote :
Revision history for this message
Krister Andersen (krister-andersen) wrote :

I am having the same issue.
When launching amarok from a terminal window I receive the following error:
Floating point exception (core dumped)

This is happening on both of the PCs where I am running Ubuntu at the moment.
It started happening after the last security updates I believe.
I have tried running amarok with different switches - but to no avail.
Have attached the bug report from one of my PCs.

Revision history for this message
Krister Andersen (krister-andersen) wrote :

Have tried running amarok with a new home directory for the user directly on the root partition and it worked then. Checked the permissions and they are the same with /home mounted or without /home mounted. However no .kde directory is created when I launch amarok with /home mounted as an ext3 partition but it is created when it is written directly to my root partition. Very strange. I copied the .kde directory onto the partition however this did not make any difference.

Revision history for this message
Doug (boarder-dougca) wrote :

Amarok is also crashing for me after I launch it. I have included the crash report.

Revision history for this message
Andrew Ash (ash211) wrote :

Relevant extract from the crash reports:

Core was generated by `amarok'.
 Program terminated with signal 8, Arithmetic exception.
 #0 0xb79faac0 in QPaintDevice::~QPaintDevice () from /usr/lib/libqt-mt.so.3
 #0 0xb79faac0 in QPaintDevice::~QPaintDevice () from /usr/lib/libqt-mt.so.3
 No symbol table info available.
 #1 0xb79fab83 in QPaintDevice::x11AppDpiY () from /usr/lib/libqt-mt.so.3
 No symbol table info available.
 #2 0xb79fac00 in QPaintDevice::x11AppDpiY () from /usr/lib/libqt-mt.so.3
 No symbol table info available.
 #3 0xb79d00f6 in qt_init_internal () from /usr/lib/libqt-mt.so.3
 No symbol table info available.
 #4 0xb79d0be2 in qt_init () from /usr/lib/libqt-mt.so.3
 No symbol table info available.
 #5 0xb7a4a26c in QApplication::construct () from /usr/lib/libqt-mt.so.3
 No symbol table info available.
 #6 0xb7a4a68c in QApplication::QApplication () from /usr/lib/libqt-mt.so.3
 No symbol table info available.
 #7 0x0804cba7 in ?? ()
 No symbol table info available.
 #8 0xbf935ae8 in ?? ()
 No symbol table info available.
 #9 0x080506c4 in vtable for __cxxabiv1::__si_class_type_info ()
 No symbol table info available.
 #10 0x00000000 in ?? ()
 No symbol table info available.

Changed in amarok:
status: Unconfirmed → Confirmed
Revision history for this message
Harald Sitter (apachelogger) wrote :

Both logs are useless, please try to obtain a useful backtrace (https://wiki.ubuntu.com/DebuggingKDE should provide informations on how to do that)

Changed in amarok:
status: Confirmed → Incomplete
Revision history for this message
Connor Imes (ckimes) 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:
status: Incomplete → 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.