Bug 321972 - Amarok closes unexpectedly when any additional window (about, track details, add media, edit queue, etc.) closes.
Summary: Amarok closes unexpectedly when any additional window (about, track details, ...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.7.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: 2.8
Assignee: Amarok Developers
URL:
Keywords:
: 321276 321777 321844 321914 321920 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-07-04 22:31 UTC by telemetron
Modified: 2013-07-10 07:35 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description telemetron 2013-07-04 22:31:25 UTC
As summary. Any window/dialog beyond the main window opens fine, but on close of the dialog the entire program closes. Was getting bug report prompt, but when I went through the entire process, my submission was marked as a duplicate of a completely unrelated issue and I was informed that the crash is caused by phonon-backend-gstreamer.
I have now changed to phonon-backend-vlc, and the problem continues but does not instigate a bug report, implying that the trigger for the crash report is in fact related to gstreamer, but that the problem behavior is not.
This behavior started a few days ago, and a google search led me to this similar report: http://ubuntuforums.org/showthread.php?t=2157427
In an effort to provide more useful information I tried to generate a backtrace with gdb (since the bug report utility isn't starting) but it reports nothing when using 'thread apply all bt' and simply using 'bt' generates the response 'No stack.'
Here is the console output from the time when the program closes:

FIXME: handle dialog end. 
amarok: BEGIN: virtual TagDialog::~TagDialog() 
amarok: END__: virtual TagDialog::~TagDialog() [Took: 0s] 
The program 'amarok' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 4877 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

After hunting through my system for any other KDE specific applications, I have found that the same thing happens with all of them. That would seem to make this a KDE problem and not an Amarok specific one, and hopefully if anyone else starts reporting bugs in the next few days you can give them better info than the clearly preposterous attribution to gstreamer.
Comment 1 Myriam Schweingruber 2013-07-05 08:55:44 UTC
This seems to be Ubuntu specific, I asked the Kubuntu devs to have a look at it

Just to have the report complete: which exact Ubuntu flavor are you using?
Comment 2 telemetron 2013-07-05 15:25:39 UTC
13.04 (32 bit, with the unity desktop, in case it matters)
KDE version is 4.10.4

Thank you.
Comment 3 Myriam Schweingruber 2013-07-06 00:33:04 UTC
Thank you for the fast feedback.
Comment 5 Myriam Schweingruber 2013-07-10 07:32:37 UTC
*** Bug 321276 has been marked as a duplicate of this bug. ***
Comment 6 Myriam Schweingruber 2013-07-10 07:33:09 UTC
*** Bug 321777 has been marked as a duplicate of this bug. ***
Comment 7 Myriam Schweingruber 2013-07-10 07:33:37 UTC
*** Bug 321844 has been marked as a duplicate of this bug. ***
Comment 8 Myriam Schweingruber 2013-07-10 07:34:30 UTC
*** Bug 321914 has been marked as a duplicate of this bug. ***
Comment 9 Myriam Schweingruber 2013-07-10 07:35:16 UTC
*** Bug 321920 has been marked as a duplicate of this bug. ***