Bug 311999

Summary: Amarok crashes when playing Guns N' Roses Lies album
Product: [Applications] amarok Reporter: Patrick Noffke <patrick.noffke>
Component: PlaybackAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED UPSTREAM    
Severity: major CC: matej
Priority: NOR    
Version: 2.6.0   
Target Milestone: 2.7   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Backtrace

Description Patrick Noffke 2012-12-20 17:44:59 UTC
If I do not have any tracks playing, and just add the GNR Lies album to the playlist, Amarok crashes (and doesn't open the Crash Reporting Assistant).

If I first have another track playing, then I can add the Lies album.  But when I try playing one of the tracks from Lies, it crashes.  When I restart Amarok, now the Lies album is still in my playlist, but again double-clicking a track to play it causes a crash.

Here is the listing of files for the Lies album:

$ ls -al ~/Music/Guns\ N\'\ Roses/G\ N\'\ R\ Lies/
total 272
drwxrwx--x. 2 pnoffke pnoffke  4096 Dec 19 10:17 .
drwxrwx--x. 3 pnoffke pnoffke  4096 Dec 19 10:06 ..
-rw-rw-r--. 1 pnoffke pnoffke 23070 Dec 19 10:08 01 - Reckless Life.ogg
-rw-rw-r--. 1 pnoffke pnoffke 21374 Dec 19 10:09 02 - Nice Boys.ogg
-rw-rw-r--. 1 pnoffke pnoffke 26175 Dec 19 10:12 03 - Move to the City.ogg
-rw-rw-r--. 1 pnoffke pnoffke 26449 Dec 19 10:14 04 - Mama Kin.ogg
-rw-rw-r--. 1 pnoffke pnoffke 50137 Dec 19 10:17 05 - Patience.ogg
-rw-rw-r--. 1 pnoffke pnoffke 23637 Dec 19 10:15 06 - Used to Love Her.ogg
-rw-rw-r--. 1 pnoffke pnoffke 34631 Dec 19 10:13 07 - You're Crazy.ogg
-rw-rw-r--. 1 pnoffke pnoffke 45069 Dec 19 10:10 08 - One in a Million.ogg


Reproducible: Always

Steps to Reproduce:
1. Open Amarok
2. Right-click on GNR Lies
3. Add to Playlist
4. Amarok crashes, and does not display Crash Reporting Assistant

-- then --
1. Open Amarok
2. Start playing another track (not from Lies)
3. Add Lies album to playlist (works)
4. Start playing first track (or any track) from Lies album
5. Amarok crashes
Actual Results:  
Crash

Expected Results:  
Play the track

Submitting via web site, since I get an error that there's a maximum of 65535 characters when using the Crash Reporting Assistant.
Comment 1 Patrick Noffke 2012-12-20 17:46:44 UTC
Created attachment 75942 [details]
Backtrace

This is the output from the Crash Reporting Assistant, which failed to create the new bug because the max comment size was 65535 characters.
Comment 2 Myriam Schweingruber 2012-12-21 15:40:39 UTC
We only need the part with the KCrashHandler, and it shows that this is actually a bug with gstreamer, please report this upstream:

Thread 30 (Thread 0x7f388f5f2700 (LWP 15689)):
[KCrash Handler]
#6  0x00007f3894d18188 in is_header_vorbis (pad=0x7f38800261e8, packet=0x7f387800b8d0) at gstoggstream.c:800
#7  0x00007f3894d00df8 in gst_ogg_demux_chain_peer (pad=pad@entry=0x7f3880026060, packet=0x7f387800b8d0, push_headers=push_headers@entry=1) at gstoggdemux.c:560
#8  0x00007f3894d035c8 in gst_ogg_demux_activate_chain (ogg=ogg@entry=0x16339a0, chain=chain@entry=0x7f388801d2d0, event=event@entry=0x7f388801d320) at gstoggdemux.c:2608
#9  0x00007f3894d08b57 in gst_ogg_demux_perform_seek_pull (ogg=ogg@entry=0x16339a0, event=event@entry=0x0) at gstoggdemux.c:3188
#10 0x00007f3894d0add8 in gst_ogg_demux_loop (pad=<optimized out>) at gstoggdemux.c:4400
#11 0x00000038b4482d64 in gst_task_func (task=0x7f38880205a0) at gsttask.c:327
#12 0x0000003899a6ac92 in g_thread_pool_thread_proxy (data=<optimized out>) at gthreadpool.c:309
#13 0x0000003899a6a495 in g_thread_proxy (data=0x7f3888005e80) at gthread.c:801
#14 0x0000003898207d14 in start_thread (arg=0x7f388f5f2700) at pthread_create.c:309
#15 0x0000003897af168d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115
Comment 3 Patrick Noffke 2013-01-03 15:02:21 UTC
As a developer myself, I would not ask a user of my software to report a problem upstream for a problem that (1) I understand much better than the user, and could add some useful details to the upstream project, and (2) they actually took the effort to report to me in the first place.
Comment 4 Patrick Noffke 2013-01-03 15:09:07 UTC
Reported here:
https://bugzilla.gnome.org/show_bug.cgi?id=691072
Comment 5 Myriam Schweingruber 2013-01-03 15:50:37 UTC
(In reply to comment #3)
> As a developer myself, I would not ask a user of my software to report a
> problem upstream for a problem that (1) I understand much better than the
> user, and could add some useful details to the upstream project, and (2)
> they actually took the effort to report to me in the first place.

JFYI: I am not a developer, but a bug triager.