[jaunty] amarok 2.0.1.1 always crashes on startup on PPC

Bug #319331 reported by Matteo Settenvini
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
amarok (Debian)
Fix Released
Unknown
amarok (Ubuntu)
Fix Released
Medium
Jonathan Thomas

Bug Description

Binary package hint: amarok

Everytime I start amarok, I first get this error:

KLibLoader cannot load this plugin:
libamarok_collection-sqlcollection
Error message:
QLibrary::load_sys: Cannot load /usr/lib/kde4/libamarok_collection-sqlcollection.so (/usr/lib/kde4/libamarok_collection-sqlcollection.so: R_PPC_REL24 relocation at 0x09b7796c for symbol `strcpy' out of range)

then, loading of the app proceeds, just to give a SIGSEGV a few moments later.
I installed the *-dbg packages for Qt4, kdelibs and amarok, and I got this backtrace:

Applicazione: Amarok (amarok), segnale SIGSEGV
0x0e361a04 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 14531)]

Thread 5 (Thread 0xf287b470 (LWP 15019)):
#0 0x0a65c15c in ?? () from /usr/lib/libpulse.so.0
#1 0x0a64d830 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#2 0x0a64eeec in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#3 0x0a64eff0 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#4 0x0a65befc in ?? () from /usr/lib/libpulse.so.0
#5 0x0a684a74 in ?? () from /usr/lib/libpulse.so.0
#6 0x0c7e5e94 in start_thread () from /lib/libpthread.so.0
#7 0x0e39bee0 in clone () from /lib/libc.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 4 (Thread 0xf6892470 (LWP 15039)):
#0 0x0c7eaa78 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x0e3aa1dc in pthread_cond_wait () from /lib/libc.so.6
#2 0x0a5898ec in ?? () from /usr/lib/libjack.so.0
#3 0x0c7e5e94 in start_thread () from /lib/libpthread.so.0
#4 0x0e39bee0 in clone () from /lib/libc.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 3 (Thread 0xf6092470 (LWP 15059)):
#0 0x0c7e9134 in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0
#1 0x0e3aa4ec in pthread_mutex_unlock () from /lib/libc.so.6
#2 0x0a683cac in ?? () from /usr/lib/libpulse.so.0
#3 0x0a65c14c in ?? () from /usr/lib/libpulse.so.0
#4 0x0a64d830 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#5 0x0a64eeec in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#6 0x0a64eff0 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#7 0x0a65befc in ?? () from /usr/lib/libpulse.so.0
#8 0x0a684a74 in ?? () from /usr/lib/libpulse.so.0
#9 0x0c7e5e94 in start_thread () from /lib/libpthread.so.0
#10 0x0e39bee0 in clone () from /lib/libc.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 2 (Thread 0xf588d470 (LWP 15428)):
#0 0x0e393a28 in select () from /lib/libc.so.6
#1 0x0e7db7cc in ?? () from /usr/lib/libQtCore.so.4
#2 0x0e6e5598 in ?? () from /usr/lib/libQtCore.so.4
#3 0x0c7e5e94 in start_thread () from /lib/libpthread.so.0
#4 0x0e39bee0 in clone () from /lib/libc.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (Thread 0xf7fa3000 (LWP 14531)):
[KCrash Handler]
#5 SqlPodcastProvider (this=0x109514b0) at /build/buildd/amarok-2.0.1.1/src/podcasts/sql/SqlPodcastProvider.cpp:51
#6 0x0f9d8c38 in PlaylistManager (this=0x1079fee0) at /build/buildd/amarok-2.0.1.1/src/playlistmanager/PlaylistManager.cpp:71
#7 0x0f9d8d20 in PlaylistManager::instance () at /build/buildd/amarok-2.0.1.1/src/playlistmanager/PlaylistManager.cpp:55
#8 0x0fa356d0 in MainWindow::init (this=0x10039340) at /build/buildd/amarok-2.0.1.1/src/MainWindow.cpp:283
#9 0x0fa1cc10 in App::continueInit (this=0xffea410c) at /build/buildd/amarok-2.0.1.1/src/App.cpp:553
#10 0x0fa1fffc in App (this=0xffea410c) at /build/buildd/amarok-2.0.1.1/src/App.cpp:182
#11 0x10005280 in main (argc=1, argv=0xffea47f4) at /build/buildd/amarok-2.0.1.1/src/main.cpp:128

maybe something glibc-related?

Related branches

Revision history for this message
Matteo Settenvini (tchernobog) wrote :

Can someone try another build of Amarok for PPC?

Revision history for this message
Matteo Settenvini (tchernobog) wrote :

It's still happening with version 2:2.0.2mysql5.1.30-0ubuntu1.
It's some months amarok is unusable for me.
Can someone point me in the right direction in order to fix this bug?

Changed in amarok:
status: Unknown → Fix Released
Changed in amarok:
importance: Undecided → Medium
status: New → Triaged
Changed in amarok:
assignee: nobody → echidnaman
status: Triaged → In Progress
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

I've incorporated the Debian patch into our packages. This just needs sponsoring/uploading.

Revision history for this message
Matteo Settenvini (tchernobog) wrote :

Since this is a powerpc-related bug, I added Peter Carrillo to the subscribers.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package amarok - 2:2.0.2mysql5.1.30-0ubuntu2

---------------
amarok (2:2.0.2mysql5.1.30-0ubuntu2) jaunty; urgency=low

  * Link libmysqld to amarok executable (patch
    03_mysqle_link_to_amarok_executable.diff from Debian) Fixes crashes on
    startup for PowerPC (LP: #319331)
  * Disable 02_mysqle_fix_linkage.diff, kinda depreciated by the above

 -- Jonathan Thomas <email address hidden> Wed, 18 Mar 2009 14:18:29 -0400

Changed in amarok:
status: In Progress → 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.