rhythmbox restarts after exit

Asked by Chris Roddy

Binary package hint: rhythmbox

I first filed this as a question, as I am only able to reproduce it on one of my two Ubuntu systems. I am using version 0.11.5-0ubuntu2.

When I exit Rhythmbox, it restarts itself (or something else restarts it) immediately, with a new process id. It does respond to SIGTERM however, and does not respawn itself after being terminated. pstree shows it as a child process of init, which doesn't tell me much.

I can reproduce this behavior regardless of how I start Rhythmbox. It still restarts itself at exit if I start it from the GNOME Applications menu, or simply running "rhythmbox" from a terminal. The new process is not attached to the old controlling terminal in the latter case.

I can reproduce this behavior regardless of how I exit Rhythmbox. It still restarts itself if I exit by selecting Music -> Quit from the menu bar, close the main window, or select Quit from the notification area icon.

It does not appear to be in my GNOME session at all. When it is running, it appears in gnome-session-properties as style "Normal", and if I remove it, it simply starts itself again.

I am using a fully updated Hardy beta system. I cannot reproduce this problem at all on my other Hardy system. This problem first appeared a couple of weeks ago; I had already upgraded from Gutsy and I'd used Rhythmbox a great deal before this issue appeared.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu rhythmbox Edit question
Assignee:
No assignee Edit question
Solved by:
Chris Roddy
Solved:
Last query:
Last reply:

This question was originally filed as bug #215283.

Revision history for this message
Basilio Kublik (sourcercito) said :
#1

seems like a local configuration issue, which is confirmed due the fact it's only reproducible in one specific system.

Revision history for this message
Chris Roddy (cmr) said :
#2

oh my, this is a mess. now the problem has been filed three times, first as a question, then as a bug, and now as a new question.

i agree that it is a local configuration issue. i am closing this as a duplicate of my original question.