Bug#415176: rhythmbox restarts on close unless doing "kill" on the command line
Sven Arvidsson wrote: > Hi, > > Any news on this bug? Have you had a chance to try logging in as a new > user and see if it happens with a fresh setup? > Hi, hm, no real news. i had the same bug on a different computer (my notebook) which has essentially the same configuration. but with the "0.10.0-1"version i have no problems. i can't reproduce the behavior now, not with the 0.9.6-9 nor with 0.10.0-1 (haven't got the 0.9.8-3 any more). so i guess it can be closed unless someone else has a problem. signature.asc Description: OpenPGP digital signature
Bug#415176: rhythmbox restarts on close unless doing "kill" on the command line
Hi, Any news on this bug? Have you had a chance to try logging in as a new user and see if it happens with a fresh setup? -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
Bug#415176: rhythmbox restarts on close unless doing "kill" on the command line
On Sun, 2007-03-18 at 16:35 +0100, Martin Ketzer wrote: > here it is (i don't think it actually contains secret information, at > least as far as i'm concerned): > [EMAIL PROTECTED]@[EMAIL PROTECTED]/bin/[EMAIL PROTECTED]@[EMAIL > PROTECTED]@[EMAIL PROTECTED]@PATH=/usr/local/bin:/usr/bin:/bin:/u > sr/bin/X11:/usr/[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL > PROTECTED]@PWD=/home/[EMAIL PROTECTED]@[EMAIL PROTECTED] > [EMAIL PROTECTED]@[EMAIL PROTECTED]/home/[EMAIL PROTECTED]@[EMAIL > PROTECTED]:[EMAIL PROTECTED]@[EMAIL PROTECTED]/home/simaketz/[EMAIL > PROTECTED]/tmp/ssh-dxBE > sp3947/[EMAIL PROTECTED]@GTK_RC_FILES=/etc/gtk/gtkrc:/home/simaketz/[EMAIL > PROTECTED]/ketzer:/tmp/.ICE-unix/[EMAIL PROTECTED]/tmp/keyring-Pbyq1T/[EMAIL > PROTECTED]:ab > stract=/tmp/dbus-cNqrSTadGF,[EMAIL > PROTECTED]@DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-cNqrSTadGF,guid=8c8b35feb7833e713c10050045fcfe34^@ Hmm, I was hoping for a DESKTOP_STARTUP_ID in there, but no such luck. You could compare this output between the rhythmbox session you launched, and the one that is started automatically. Another idea is to add a new user on your system, login and see if you can reproduce the problem with the default settings. > and second: > one time when i closed rhythmbox it had a bug-buddy-window popping up, > claiming some kind kind of crash happened. unfortunately i clicked it > away before realizing what it was and it wasn't reproduceable. so it may > be completely unrelated. on the other hand maybe gnome automatically > restarts crashed programs (i hope not, at least not without asking first) To the best of my knowledge, nothing should restart a crashed program automatically (unless set as restart in the session of course). -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
Bug#415176: rhythmbox restarts on close unless doing "kill" on the command line
Sven Arvidsson wrote: On Sun, 2007-03-18 at 11:42 +0100, Martin Ketzer wrote: > Can you run rhythmbox from the terminal in debug mode (rhythmbox -d) and > see if you can capture any interesting error messages when you close? > Keep in mind that debug mode is very verbose. > hm, i see nothing out of the ordinary. problem is, that the "exit" of rhythmbox starts a new instance (without -d). but i tried a few things. 1. mv /usr/bin/rhythmbox /usr/bin/rhythmbox.orig and execute "rhythmbox.orig" results in rhythmbox exiting normally without restart 2. write a shell-script named "rhythmbox" that does execute "rhythmbox.orig -d" and pipes the output into a file but that results again in rhythmbox exiting normally without restart (and nothing interesting in the log again). after that i renamed the original rhythmbox to it's usual name the restarting occurs again. odd... Yes, I'm quite curious myself to figure out what is causing this. The next time you close rhythmbox and the restart happens, can you run this? cat /proc/$(pidof rhythmbox)/environ Maybe it can give a clue as to what is starting rhythmbox again. Be sure to scan the output for any personal information before you mail it. here it is (i don't think it actually contains secret information, at least as far as i'm concerned): [EMAIL PROTECTED]@[EMAIL PROTECTED]/bin/[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@PATH=/usr/local/bin:/usr/bin:/bin:/u sr/bin/X11:/usr/[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@PWD=/home/[EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED]/home/[EMAIL PROTECTED]@[EMAIL PROTECTED]:[EMAIL PROTECTED]@[EMAIL PROTECTED]/home/simaketz/[EMAIL PROTECTED]/tmp/ssh-dxBE sp3947/[EMAIL PROTECTED]@GTK_RC_FILES=/etc/gtk/gtkrc:/home/simaketz/[EMAIL PROTECTED]/ketzer:/tmp/.ICE-unix/[EMAIL PROTECTED]/tmp/keyring-Pbyq1T/[EMAIL PROTECTED]:ab stract=/tmp/dbus-cNqrSTadGF,[EMAIL PROTECTED]@DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-cNqrSTadGF,guid=8c8b35feb7833e713c10050045fcfe34^@ and second: one time when i closed rhythmbox it had a bug-buddy-window popping up, claiming some kind kind of crash happened. unfortunately i clicked it away before realizing what it was and it wasn't reproduceable. so it may be completely unrelated. on the other hand maybe gnome automatically restarts crashed programs (i hope not, at least not without asking first) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415176: rhythmbox restarts on close unless doing "kill" on the command line
On Sun, 2007-03-18 at 11:42 +0100, Martin Ketzer wrote: > > Can you run rhythmbox from the terminal in debug mode (rhythmbox -d) and > > see if you can capture any interesting error messages when you close? > > Keep in mind that debug mode is very verbose. > > > hm, i see nothing out of the ordinary. problem is, that the "exit" of > rhythmbox starts a new instance (without -d). but i tried a few things. > > 1. mv /usr/bin/rhythmbox /usr/bin/rhythmbox.orig > and execute "rhythmbox.orig" > results in rhythmbox exiting normally without restart > > 2. write a shell-script named "rhythmbox" that does execute > "rhythmbox.orig -d" and pipes the output into a file > but that results again in rhythmbox exiting normally without restart > (and nothing interesting in the log again). > > after that i renamed the original rhythmbox to it's usual name the > restarting occurs again. odd... Yes, I'm quite curious myself to figure out what is causing this. The next time you close rhythmbox and the restart happens, can you run this? cat /proc/$(pidof rhythmbox)/environ Maybe it can give a clue as to what is starting rhythmbox again. Be sure to scan the output for any personal information before you mail it. -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
Bug#415176: rhythmbox restarts on close unless doing "kill" on the command line
Sven Arvidsson wrote: > On Sat, 2007-03-17 at 18:19 +0100, Martin Ketzer wrote: >>> Do you get any error messages if you launch rhythmbox from a terminal? >> yes, this: >> (rhythmbox:8341): Rhythmbox-WARNING **: Unable to start mDNS browsing: >> MDNS service is not running > > I think that's unrelated, only a warning about avahi not being > installed / not running. > >>> Are your sure you haven't set rhythmbox as "restart" in the session >>> preferences in GNOME? >> no, i haven't, "Style" is set to "normal". but maybe it's got something >> to do with gnome 2.16? > > I'm not sure, but I don't think so. > > Do you have this problem only with version 0.9.8 or also with 0.9.6 from > unstable? i have it since the upgrade from 0.9.6 to 0.9.8 (the versions should have been in the original report?) > > Can you run rhythmbox from the terminal in debug mode (rhythmbox -d) and > see if you can capture any interesting error messages when you close? > Keep in mind that debug mode is very verbose. > hm, i see nothing out of the ordinary. problem is, that the "exit" of rhythmbox starts a new instance (without -d). but i tried a few things. 1. mv /usr/bin/rhythmbox /usr/bin/rhythmbox.orig and execute "rhythmbox.orig" results in rhythmbox exiting normally without restart 2. write a shell-script named "rhythmbox" that does execute "rhythmbox.orig -d" and pipes the output into a file but that results again in rhythmbox exiting normally without restart (and nothing interesting in the log again). after that i renamed the original rhythmbox to it's usual name the restarting occurs again. odd... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415176: rhythmbox restarts on close unless doing "kill" on the command line
On Sat, 2007-03-17 at 18:19 +0100, Martin Ketzer wrote: > > Do you get any error messages if you launch rhythmbox from a terminal? > yes, this: > (rhythmbox:8341): Rhythmbox-WARNING **: Unable to start mDNS browsing: > MDNS service is not running I think that's unrelated, only a warning about avahi not being installed / not running. > > Are your sure you haven't set rhythmbox as "restart" in the session > > preferences in GNOME? > no, i haven't, "Style" is set to "normal". but maybe it's got something > to do with gnome 2.16? I'm not sure, but I don't think so. Do you have this problem only with version 0.9.8 or also with 0.9.6 from unstable? Can you run rhythmbox from the terminal in debug mode (rhythmbox -d) and see if you can capture any interesting error messages when you close? Keep in mind that debug mode is very verbose. -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
Bug#415176: rhythmbox restarts on close unless doing "kill" on the command line
Sven Arvidsson wrote: On Fri, 2007-03-16 at 20:33 +0100, Martin Ketzer wrote: When i close rhythmbox in any way (menu, status-icon, close-button) it just restarts - when i do a "killall rhythmbox" on the command line Hi, Do you get any error messages if you launch rhythmbox from a terminal? yes, this: (rhythmbox:8341): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running Are your sure you haven't set rhythmbox as "restart" in the session preferences in GNOME? no, i haven't, "Style" is set to "normal". but maybe it's got something to do with gnome 2.16? btw. a "close" (which results in a restart) gives me a new promt again after printing: (rhythmbox:8413): Rhythmbox-WARNING **: Unable to stop mDNS browsing: MDNS service is not running -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415176: rhythmbox restarts on close unless doing "kill" on the command line
On Fri, 2007-03-16 at 20:33 +0100, Martin Ketzer wrote: > When i close rhythmbox in any way (menu, status-icon, close-button) it > just restarts - when i do a "killall rhythmbox" on the command line Hi, Do you get any error messages if you launch rhythmbox from a terminal? Are your sure you haven't set rhythmbox as "restart" in the session preferences in GNOME? -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
Bug#415176: rhythmbox restarts on close unless doing "kill" on the command line
Package: rhythmbox Version: 0.9.8-3 Severity: normal --- Please enter the report below this line. --- When i close rhythmbox in any way (menu, status-icon, close-button) it just restarts - when i do a "killall rhythmbox" on the command line --- System information. --- Architecture: i386 Kernel: Linux 2.6.20 Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') --- Package information. --- Depends (Version) | Installed ==-+-= gconf2 (>= 2.10.1-2) | 2.16.1-1 libart-2.0-2 (>= 2.3.16) | 2.3.19-1 libatk1.0-0(>= 1.12.2) | 1.17.0-1 libaudiofile0 (>= 0.2.3-4) | 0.2.6-6 libavahi-client3 (>= 0.6.13) | 0.6.16-4 libavahi-common3 (>= 0.6.10) | 0.6.16-4 libavahi-glib1 (>= 0.6.12) | 0.6.16-4 libbonobo2-0 (>= 2.13.0) | 2.16.0-1 libbonoboui2-0 (>= 2.5.4) | 2.16.0-1 libc6 (>= 2.3.6-6) | 2.3.6.ds1-13 libcairo2 (>= 1.2.4) | 1.2.6-1 libdbus-1-3 (>= 0.94) | 1.0.2-1 libdbus-glib-1-2 (>= 0.71) | 0.71-3 libesd0 (>= 0.2.35) | OR libesd-alsa0 (>= 0.2.35) | 0.2.36-3 libexpat1 (>= 1.95.8) | 1.95.8-3.4 libfontconfig1 (>= 2.4.0) | 2.4.2-1.2 libfreetype6 (>= 2.2) | 2.2.1-5 libgconf2-4(>= 2.13.5) | 2.16.1-1 libgcrypt11 (>= 1.2.2) | 1.2.3-2 libglade2-0 (>= 1:2.5.1) | 1:2.6.0-4 libglib2.0-0 (>= 2.12.0) | 2.12.11-1 libgnome-keyring0 (>= 0.6.0) | 0.6.0-3 libgnome-media0| 2.16.1-1 libgnome2-0(>= 2.14.1) | 2.16.0-2 libgnomecanvas2-0 (>= 2.11.1) | 2.14.0-2 libgnomeui-0 (>= 2.13.0) | 2.16.1-1 libgnomevfs2-0(>= 2.13.92) | 1:2.16.3-7 libgnutls13 (>= 1.4.0-0) | 1.4.4-3 libgpg-error0 (>= 1.4) | 1.4-2 libgpod0.4.0 | 0.4.0-1 libgstreamer-plugins-base0.10-0 (>= 0.10.10) | 0.10.12-1 libgstreamer0.10-0(>= 0.10.10) | 0.10.12-1 libgtk2.0-0 (>= 2.8.0) | 2.10.9-1 libhal1 (>= 0.5) | 0.5.8.1-9 libice6 (>= 1:1.0.0) | 1:1.0.1-2 libjpeg62 | 6b-13 liblircclient0 | 0.8.0-9.2 libmusicbrainz4c2a (>= 2.1.4) | 2.1.4-1 libnautilus-burn3 | 2.14.3-8+b1 libnotify1 | 0.4.3-2 liborbit2(>= 1:2.14.1) | 1:2.14.4-1 libpango1.0-0 (>= 1.14.8) | 1.16.1-1 libpng12-0 (>= 1.2.13-4) | 1.2.15~beta5-1 libpopt0 (>= 1.10) | 1.10-3 libsexy2 | 0.1.10-1 libsm6 | 1:1.0.1-3 libsoup2.2-8 (>= 2.2.98) | 2.2.100-1 libtasn1-3 (>= 0.3.4) | 0.3.6-2 libtotem-plparser1 (>= 2.16.1) | 2.16.5-3 libx11-6 | 2:1.0.3-6 libxcursor1 (>> 1.1.2) | 1.1.7-4 libxext6 | 1:1.0.1-2 libxfixes3(>= 1:4.0.1) | 1:4.0.1-5 libxi6 | 1:1.0.1-4 libxinerama1 | 1:1.0.1-4.1 libxml2(>= 2.6.27) | 2.6.27.dfsg-1 libxrandr2 | 2:1.2.0-4 libxrender1| 1:0.9.1-3 python2.4 (>= 2.3.90) | 2.4.4-2 zlib1g(>= 1:1.2.1) | 1:1.2.3-13 python | 2.4.4-2 python-support(>= 0.2) | 0.5.6 dbus | 1.0.2-1 gstreamer0.10-gnomevfs | 0.10.12-1 gstreamer0.10-plugins-base | 0.10.12-1 gstreamer0.10-plugins-good | 0.10.5-4 gstreamer0.10-plugins-ugly | 0.10.5-1 libgstreamer0.10-0 | 0.10.12-1 gstreamer0.10-alsa | 0.10.12-1 OR gstreamer0.10-audiosink
