SUSEplugger crashing/hanging in 9.3
Hello everyone, I've just installed 9.3 after a brief experience with 9.2. I've noticed a strange behavior of SUSEplugger in Gnome: if I have my USB DVD-RW (LACIE DVD DL, with id=_NEC-DVD_RW_ND-3520A) plugged at startup, SUSEplugger hangs and does not show up in the tray (it shows up as a small window in the dekstop, and the "pci card" icon does not show up); if instead the USB DVD-RW is unplugged, SUSEplugger starts up correctly and quitely goes in the tray, then I can later plug my DVD-RW and it is recognized correctly. Also, from time to time SUSEplugger stays in the desktop with its tiny window instead of going in the Tray. If I ask to not start it at startup at next login, it basically ignores that (even if I set the Autostart=false statement in ~/.kde/share/config/susepluggerrc). Any ideas on this strange behavior of SUSEplugger? (this did not happen with 9.2, btw). Is this due to something not going on correctly with my USB drive? Thanks for any insight, Luca.
The Monday 2005-04-25 at 21:48 +0200, Luca wrote:
I've just installed 9.3 after a brief experience with 9.2. I've noticed a strange behavior of SUSEplugger in Gnome: if I have my USB DVD-RW (LACIE DVD DL, with id=_NEC-DVD_RW_ND-3520A) plugged at startup, SUSEplugger hangs and does not show up in the tray (it shows up as a small window in the dekstop, and the "pci card" icon does not show up); if instead the USB DVD-RW is unplugged, SUSEplugger starts up correctly and quitely goes in the tray, then I can later plug my DVD-RW and it is recognized correctly.
Same here. An empty useless window, I have to force kill it. How do I dissable susepluger completely? I'm tempted to uninstall it :-/ I don't have any thing on the usb. -- Cheers, Carlos Robinson
On 4/26/05, Carlos E. R.
Same here. An empty useless window, I have to force kill it. How do I dissable susepluger completely? I'm tempted to uninstall it :-/
I'm tempted too! Even though I don't know if I can still get the USB DVDRW/lashdisk to automount and show as an icon on the dekstop. Regarding stability I noticed that if I log out and log in again in gnome, then suseplugger/watcher randomly start in tray and/or desktop, with screwed up fonts in their menus (I use 10 on the desktop, they choose to go with 16 or more!). Hmmm guess something is broken here :-( I found some other complaints on a suse forum at: http://www.suseforums.net/index.php?showtopic=13273 but the guy did not find the exact cause of this behavior. Cheers, Luca.
The Tuesday 2005-04-26 at 23:34 +0200, Anders Johansson wrote:
On Tuesday 26 April 2005 14:35, Carlos E. R. wrote:
How do I dissable susepluger completely?
Right-click the icon and select 'quit' and when it asks you if it should be started automatically next time you log in, click on 'no'
Impossible. There is nowhere to click at, empty, except the "X" at the top-right corner of the window. It says nothing for a while, then gnome gets tired of waiting and asks if I want to force quit it - which I do. -- Cheers, Carlos Robinson
On Monday 25 April 2005 21:48, Luca wrote:
I've just installed 9.3 after a brief experience with 9.2. I've noticed a strange behavior of SUSEplugger in Gnome: if I have my USB DVD-RW (LACIE DVD DL, with id=_NEC-DVD_RW_ND-3520A) plugged at startup, SUSEplugger hangs and does not show up in the tray (it shows up as a small window in the dekstop, and the "pci card" icon does not show up); if instead the USB DVD-RW is unplugged, SUSEplugger starts up correctly and quitely goes in the tray, then I can later plug my DVD-RW and it is recognized correctly.
Is it really hanging hard? If you do a 'ps aux', what does the suseplugger process look like?
Also, from time to time SUSEplugger stays in the desktop with its tiny window instead of going in the Tray. If I ask to not start it at startup at next login, it basically ignores that (even if I set the Autostart=false statement in ~/.kde/share/config/susepluggerrc).
I wonder if perhaps this isn't a suseplugger problem but a systray problem between gnome and kde. When I run gaim in kde, I see similar problems. If I have gaim started automatically on boot, it won't go in the KDE systray, but if I start it manually later it will. In gnome it always goes into the systray. And suseplugger was developed as a KDE program. The two systrays are supposed to be compatible, but maybe there is some subtle difference that causes this Have you tried it in KDE? Do you see the same behaviour there?
On 4/26/05, Anders Johansson
I wonder if perhaps this isn't a suseplugger problem but a systray problem [...] systray. And suseplugger was developed as a KDE program. The two systrays are supposed to be compatible, but maybe there is some subtle difference that causes this
Have you tried it in KDE? Do you see the same behaviour there?
Good news! 5 minutes ago I updated the system through YOU (the icon became just read as I was reading Anders' post): the package gnome-filesystem has been updated (to gnome-filesystem-0.1-211.4.i586.patch.rpm) and after multiple reboots, log in/outs, etc.. it SEEMS that the issue is solved. BTW this package was among those that the guy on the mentioned SUSE forum identified as potential causes of this instability. I'll let you know if the problem pops up again, but as of know the mighty SUSE seems to have solved the issue. And yes, it definitely looked like a gnome problem and not a suseplugger one. Thanks to all those who replied, Luca.
The Wednesday 2005-04-27 at 00:27 +0200, Luca wrote:
5 minutes ago I updated the system through YOU (the icon became just read as I was reading Anders' post): the package gnome-filesystem has been updated (to gnome-filesystem-0.1-211.4.i586.patch.rpm) and after multiple reboots, log in/outs, etc.. it SEEMS that the issue is solved. BTW this package was among those that the guy on the mentioned SUSE forum identified as potential causes of this instability.
My system was updated (I remember that package), but I have the problem. -- Cheers, Carlos Robinson
The Tuesday 2005-04-26 at 23:33 +0200, Anders Johansson wrote:
Is it really hanging hard? If you do a 'ps aux', what does the suseplugger process look like?
cer 8615 0.1 1.0 23092 8328 ? S 11:31 0:00 suseplugger --quiet cer 8649 1.8 2.1 28984 16504 ? S 11:31 0:02 \_ suseplugger --quiet cer 8617 0.1 0.9 21760 7596 ? S 11:31 0:00 susewatcher --quiet cer 8650 0.0 1.0 21760 8020 ? S 11:31 0:00 \_ susewatcher --quiet cer 8652 0.1 0.9 21920 7556 ? S 11:31 0:00 \_ /opt/kde3/bin/kdeinit --suicide cer 8662 0.0 1.0 21920 8448 ? Ss 11:31 0:00 \_ kdeinit Starting up... cer 8695 0.0 1.2 22608 9472 ? S 11:31 0:00 \_ klauncher [kdeinit] klauncher cer 8726 0.0 1.1 22060 8704 ? S 11:31 0:00 \_ kded [kdeinit] kded cer 8732 0.2 1.5 25980 11892 ? S 11:31 0:00 \_ kded [kdeinit] kded The window is empty, does not even redraw its gray emptiness (if I click the window menu (minimize, maximize, etc) it stays there). If I tell it to close clicking the "X" at the right-top corner, it doesn't, till gnome forces quit it. My 9.3 system is fully updated. I can "kill -9" process 8732, and both suseplugger and susewatcher dies. Good! Now, I don't want them to ever start again. How? I'm using gnome, I don't want kde there. I don't want those automatisms, thankyou.
Have you tried it in KDE? Do you see the same behaviour there?
I tried to start another session with kde, with the command: startx kde -- :1 on a tty, and it hangs. No session, only a "starting desktop" or similar message, then a gray emptiness with an "X" mouse cursor. It worked fine in 9.1 -- Cheers, Carlos Robinson
On 4/27/05, Carlos E. R.
The window is empty, does not even redraw its gray emptiness (if I click the window menu (minimize, maximize, etc) it stays there). If I tell it to close clicking the "X" at the right-top corner, it doesn't, till gnome forces quit it.
My 9.3 system is fully updated.
It all seemed to work fine yesterday evening after the system update, but today the problem returned: I too have the tiny suseplugger window in the upper left corner, completely white (no pci-card image inside). If I log in and out of gnome maybe next time it does not hang, but it will stay in the desktop. Damn, I don't understand why this happens with such randomness. Carlos, just out of curiosity which motherboard do you have? Do you have any filesystems in /etc/fstab that is not available at boot time (e.g. an external drive)? I don't see any other reason why suseplugger would not start correctly. At warm reboot if I don't plug in my USB DVDRW (which, btw, is listed in /etc/fstab, and maybe that's my mistake) then suseplugger hangs, even though I configure its rc file to ignore this device.
I can "kill -9" process 8732, and both suseplugger and susewatcher dies. Good! Now, I don't want them to ever start again. How? I'm using gnome, I don't want kde there. I don't want those automatisms, thankyou.
I have tried to tell it not to start (by clicking the appropriate button when I tell it to QUIT, by selecting the option in its configuration panel and also by putting the Autostart=false parameter in the suseplugger rc file): no way, it will fire up again at next log in gnome. I start to not like that little program. Cheers, Luca.
The Wednesday 2005-04-27 at 18:55 +0200, Luca wrote:
It all seemed to work fine yesterday evening after the system update, but today the problem returned: I too have the tiny suseplugger window in the upper left corner, completely white (no pci-card image inside). If I log in and out of gnome maybe next time it does not hang, but it will stay in the desktop. Damn, I don't understand why this happens with such randomness.
I just went to the gnome control center, current session properties, and removed both susepluger and susewatcher; I don't know what will happen when I log in again. [...] Dunno... it started, then suddenly died before session restore was complete. There are strange things in gnome... it even calls kdesu to run Yast!
Carlos, just out of curiosity which motherboard do you have? Do you have any filesystems in /etc/fstab that is not available at boot time (e.g. an external drive)? I don't see any other reason why suseplugger would not start correctly.
Well, it lists my ZIP drive (parallel port), but it is not even connected to this computer now.
I have tried to tell it not to start (by clicking the appropriate button when I tell it to QUIT, by selecting the option in its configuration panel and also by putting the Autostart=false parameter in the suseplugger rc file): no way, it will fire up again at next log in gnome.
I can not click any button, none shows. The window is empty.
I start to not like that little program.
I never did. -- Cheers, Carlos Robinson
On Wed, 2005-04-27 at 22:04 +0200, Carlos E. R. wrote:
The Wednesday 2005-04-27 at 18:55 +0200, Luca wrote:
Well, it lists my ZIP drive (parallel port), but it is not even connected to this computer now.
Must be one of those new wireless ZIP drives. :-) -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
The Wednesday 2005-04-27 Luca and I were talking:
It all seemed to work fine yesterday evening after the system update, but today the problem returned: I too have the tiny suseplugger window in the upper left corner, completely white (no pci-card image inside). If I log in and out of gnome maybe next time it does not hang, but it will stay in the desktop. Damn, I don't understand why this happens with such randomness.
I just went to the gnome control center, current session properties, and removed both susepluger and susewatcher; I don't know what will happen when I log in again. [...] Dunno... it started, then suddenly died before session restore was complete. There are strange things in gnome... it even calls kdesu to run Yast!
Found something. I created a new user, then tested gnome there. There were icons (applets) in the panel for suseplugger and susewatcher. Then I noticed another unknown applet, one named "Notification Area 2.10.0 (copyright Red Hat)". Then I went back to my normal user, added that panel, and sure enough, the suseplugger and susewatcher promptly went inside. I have been able to remove them for ever - for ever being till the next login. They resurrect and appear again :-/ When I remove them, they both ask if I want to restart them next time. Of course, I say "NO!". I could be talking chinese, they both start again nect time. I renamed both apps to a suitable name... But I still would like to know how to dissable applications that ask if the user (not root!) wants to install new hardware that it has discovered. Or if he want's to find and apply patches. :-/ SuSE should add a list in Yast of what users should receive such notifications. -- Cheers, Carlos Robinson
participants (4)
-
Anders Johansson -
Carlos E. R. -
Ken Schneider -
Luca