Amarok does not quit (and therefore cannot be started again)

Bug #579776 reported by Andrew
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: amarok

== What I do ==

1) Run 'amarok' in the terminal.
2) Click on Amarok -> Quit.

== What I expect to happen ==

The Amarok process quits. I can start Amarok again later by running 'amarok' in the terminal.

== What actually happens ==

Amarok disappears from the screen. If I try running 'amarok' again later, Amarok does not appear and the following error message is displayed in the terminal:

Amarok is already running!
<unknown program name>(3000)/: Communication problem with "amarok" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: amarok 2:2.3.0-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed May 12 23:02:32 2010
ExecutablePath: /usr/bin/amarok
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: amarok
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1565): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (Do:1577): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.
 (gnome-terminal:1984): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
 (gnome-terminal:2644): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

Revision history for this message
Andrew (andrewkvalheim) wrote :
Revision history for this message
Zeyelth (zeyelth) wrote :

I had the same problem with package "amarok 2:2.3.0-0ubuntu4" (Ubuntu 10.04, 64bit). Updating to "amarok 2:2.3.1-1ubuntu1~lucid1~ppa2" by adding the "ppa:kubuntu-ppa/backports" repository seems to have fixed it.

Revision history for this message
Andrew (andrewkvalheim) wrote :

This problem is not present in the current version, amarok 2:2.3.2-0ubuntu4.

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