How to deactivate SuSEPlugger and SuSEWatcher on GNOME startup
The SuSEPlugger and SuSEWatcher services can be easily deactivated in KDE sessions, but not in GNOME (SuSE 9.3). The new GNOME login automatically starts these services. What scripts should be edited to deactivate them?
The Tuesday 2005-05-31 at 12:51 +0200, Mike Béla wrote:
The SuSEPlugger and SuSEWatcher services can be easily deactivated in KDE sessions, but not in GNOME (SuSE 9.3). The new GNOME login automatically starts these services. What scripts should be edited to deactivate them?
I didn't find a way, except renaming the binaries: /opt/kde3/bin/DAMMsuseplugger /opt/kde3/bin/DAMMsusewatcher The names reflect my frustation... Another thing. When I login with any new user, it says "new hardware found" - hardrware that is already working. Why does have any other user but root to be told about such things? -- Cheers, Carlos Robinson
Op dinsdag 31 mei 2005 13:14, schreef Carlos E. R.:
Another thing. When I login with any new user, it says "new hardware found" - hardrware that is already working. Why does have any other user but root to be told about such things?
Indeed that is annoying. Is that with kde or with gnome or with both? -- Richard Bos Without a home the journey is endless
The Tuesday 2005-05-31 at 21:25 +0200, Richard Bos wrote:
Op dinsdag 31 mei 2005 13:14, schreef Carlos E. R.:
Another thing. When I login with any new user, it says "new hardware found" - hardrware that is already working. Why does have any other user but root to be told about such things?
Indeed that is annoying. Is that with kde or with gnome or with both?
I think with both. Not only annoying, but dangerous: a user must not have that kind of power/temptation. -- Cheers, Carlos Robinson
On Wednesday 01 June 2005 01:42, Carlos E. R. wrote:
The Tuesday 2005-05-31 at 21:25 +0200, Richard Bos wrote:
Op dinsdag 31 mei 2005 13:14, schreef Carlos E. R.:
Another thing. When I login with any new user, it says "new hardware found" - hardrware that is already working. Why does have any other user but root to be told about such things?
Indeed that is annoying. Is that with kde or with gnome or with both?
I think with both. Not only annoying, but dangerous: a user must not have that kind of power/temptation.
Power? It's not like it's suid. He's not going to be able to do anything damaging without the root password You could just remove suseplugger.desktop from /opt/kde3/share/autostart and start it manually with the user you want to use as an admin login. Perhaps susewatcher.desktop too, come to think of it.
You could just remove suseplugger.desktop from /opt/kde3/share/autostart and start it manually with the user you want to use as an admin login. Perhaps susewatcher.desktop too, come to think of it.
That wouldn't affect GNOME... -- James Ogley james@usr-local-bin.org GNOME for SuSE: http://usr-local-bin.org/rpms
On Wednesday 01 June 2005 07:44, James Ogley wrote:
You could just remove suseplugger.desktop from /opt/kde3/share/autostart and start it manually with the user you want to use as an admin login. Perhaps susewatcher.desktop too, come to think of it.
That wouldn't affect GNOME...
I don't use gnome. You do. So why not tell us where the autostart things are in gnome?
I don't use gnome. You do. So why not tell us where the autostart things are in gnome?
This is the thing, in the SuSE GNOME install on 9.3, starting SuSEwatcher and SuSEplugger is hard-coded, which is why it'll need me to do a rebuilt gnome-session package - clicking that you don't want them to start at next login when you quit them only affects the KDE setup. -- James Ogley james@usr-local-bin.org GNOME for SuSE: http://usr-local-bin.org/rpms
The Wednesday 2005-06-01 at 20:34 +0100, James Ogley wrote:
I don't use gnome. You do. So why not tell us where the autostart things are in gnome?
This is the thing, in the SuSE GNOME install on 9.3, starting SuSEwatcher and SuSEplugger is hard-coded, which is why it'll need me to do a rebuilt gnome-session package - clicking that you don't want them to start at next login when you quit them only affects the KDE setup.
Why!? Why did SuSE do such a nasty thing, I wonder? :-/ Therefore, my "trick" of renaming the binaries, or uninstalling them, is the "proper" thing to do. -- Cheers, Carlos Robinson
Why!? Why did SuSE do such a nasty thing, I wonder? :-/
Well, it's inevitable that a company and dev team that's been KDE-centric for so long would make the error in terms of coding SuSE* to only interact with KDE correctly, plus, they're both so tied to KDE [did you know that when you login to GNOME on SuSE 9.3 all the KDE services are also started because the SuSE apps need them?] that it makes sense for that reason. As for hard-coding them, beats me, a simple check for a touched file in ~/.skel, which if it didn't exist adds them to ~/.gnome2/session-manual would do the job - that way people can easily remove them using the GNOME sessions GUI. Anyway, keep an eye out for a new gnome-session package, since it seems to be a hot issue at the moment, I'll try to do it on Saturday once I've got my next essay out of the way.
Therefore, my "trick" of renaming the binaries, or uninstalling them, is the "proper" thing to do.
I wouldn't say it's the proper thing to do - it mis-represents what is presently installed as far as your RPM database is concerned, but certainly for the time being it will have the desired effect, and once gnome-session is updated, you can rename them back. -- James Ogley james@usr-local-bin.org GNOME for SuSE: http://usr-local-bin.org/rpms
On Wed, 2005-06-01 at 17:41, Carlos E. R. wrote:
Why!? Why did SuSE do such a nasty thing, I wonder? :-/
Therefore, my "trick" of renaming the binaries, or uninstalling them, is the "proper" thing to do.
Like all "improvements" its only someone elses opinion. I use a renaming and linking hack to make Mozilla the default browser for links I click in evolution and have done since 8.2. I think 10.0 should come out early and correct these things. I have dialup so I am collecting these hacks for the time when I get 9.3 or decide to get 9.2 and wait for 10.x. IMHO this fix is a bug making these programs hard coded to run. It should be fixed in an update. ___ _ _ _ ____ _ _ _ | | | | [__ | | | |___ |_|_| ___] | \/
The Wednesday 2005-06-01 at 02:02 +0200, Anders Johansson wrote:
Another thing. When I login with any new user, it says "new hardware found" - hardrware that is already working. Why does have any other user but root to be told about such things?
Indeed that is annoying. Is that with kde or with gnome or with both?
I think with both. Not only annoying, but dangerous: a user must not have that kind of power/temptation.
Power? It's not like it's suid. He's not going to be able to do anything damaging without the root password
You could just remove suseplugger.desktop from /opt/kde3/share/autostart and start it manually with the user you want to use as an admin login. Perhaps susewatcher.desktop too, come to think of it.
That's not it. Remember that I have renamed the susewatcher binary to /opt/kde3/bin/DAMMsusewatcher, there is no way it can start. It doesn't exist. However, when I login with a new user, it says "new hardware found". And a user should never even be told about such things he doesn't know about nor is authorized to handle/think/whatever. -- Cheers, Carlos Robinson
On Wednesday 01 June 2005 11:43, Carlos E. R. wrote:
That's not it. Remember that I have renamed the susewatcher binary to /opt/kde3/bin/DAMMsusewatcher, there is no way it can start. It doesn't exist.
It's suseplugger, not susewatcher, that monitors for new hardware. susewatcher monitors for updates, and I suspect you no longer see the suse logo icon in the systray
The Wednesday 2005-06-01 at 18:24 +0200, Anders Johansson wrote:
On Wednesday 01 June 2005 11:43, Carlos E. R. wrote:
That's not it. Remember that I have renamed the susewatcher binary to /opt/kde3/bin/DAMMsusewatcher, there is no way it can start. It doesn't exist.
It's suseplugger, not susewatcher, that monitors for new hardware. susewatcher monitors for updates, and I suspect you no longer see the suse logo icon in the systray
That doesn't matter; remember, again, I said that I renamed both to: /opt/kde3/bin/DAMMsuseplugger /opt/kde3/bin/DAMMsusewatcher I posted that data on this same thread 36 hours ago. I see you did not read what I said before answering. There is no way any of them can be started, unless hardlinked somewhere, or using a library somewhere. The binaries are unreachable. However, new users are prompted with "new hardware found". It's got to be something else. -- Cheers, Carlos Robinson
However, new users are prompted with "new hardware found". It's got to be something else. The only way new users would be prompted for new hardware is because the
Carlos E. R. wrote: main user has turned off suseplugger, and there is new hardware that has not been installed, since there is only one hardware installation cache, /var/lib/hardware/unique-keys. If all hardware is installed, new users won't be prompted, AFAIK. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
The Wednesday 2005-06-01 at 20:46 -0500, Joe Morris (NTM) wrote:
Carlos E. R. wrote:
However, new users are prompted with "new hardware found". It's got to be something else.
The only way new users would be prompted for new hardware is because the main user has turned off suseplugger, and there is new hardware that has not been installed, since there is only one hardware installation cache, /var/lib/hardware/unique-keys. If all hardware is installed, new users won't be prompted, AFAIK.
The root user had never logged in, as root, I think. In any case, when I did log in as root a few days ago, I was told that "new hardware was found", namely, the ethernet card that has been working for years, and continues to be installed and working. So I told it to go away. I just want it to shut up for ever: if I want to mantain hardware, I'm clever enough to fire up yast. And yast says nothing about new hardware, it is happy and content. What do you sugest, that I start as root again, say ok to new hardaware found, "a la windows", allow it to proceed and perhaps break something that is already working? Can't just I say, good doggy, now be good and shut up? I don't understand. -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The root user had never logged in, as root, I think. To kde I'll assume. Same here, except by accident from console 1. In any case, when I did log in as root a few days ago, I was told that "new hardware was found", namely, the ethernet card that has been working for years, and continues to be installed and working. So I told it to go away.
Thus the problem. It is working, but it does not mean it is in the Yast hardware database. Once it is there, it will not prompt unless something changes (and it won't even if something changes if suseplugger can't run, i.e. since you renamed them).
I just want it to shut up for ever: if I want to mantain hardware, I'm clever enough to fire up yast. And yast says nothing about new hardware, it is happy and content.
What does it show for the NIC in Yast>Hardware>Hardware Information? Just running it seems to create new unique keys, so that might solve your problem. Hope so. :-)
What do you sugest, that I start as root again, say ok to new hardaware found, "a la windows", allow it to proceed and perhaps break something that is already working? Not necessarily, just that the fact the module loads and the card works doesn't mean it is "found" hardware as far as Yast is concerned (though since that is what Yast was supposed to do it should have). Can't just I say, good doggy, now be good and shut up? I'm sure you can. I was just pointing out that suseplugger is quiet for all users once it has "found" all present hardware. It will only prompt a "new" user about new hardware if there is new hardware. If you made sure it was all "found", that puppy WOULD be quiet. My point was there was another way to shut it up, which was IIUC the designed way. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
The SuSEPlugger and SuSEWatcher services can be easily deactivated in KDE sessions, but not in GNOME (SuSE 9.3). The new GNOME login automatically starts these services. What scripts should be edited to deactivate them?
At this time you can't, at some point, when I have time, I'm going to produce an updated gnome-session package that won't run them, but will provide directions for how to enable them if desired. -- James Ogley james@usr-local-bin.org GNOME for SuSE: http://usr-local-bin.org/rpms
The Tuesday 2005-05-31 at 12:35 +0100, James Ogley wrote:
At this time you can't, at some point, when I have time, I'm going to produce an updated gnome-session package that won't run them, but will provide directions for how to enable them if desired.
Another point. I noticed that my gnome calls kdesu instead gnomesu; it calls kde help viewer to display gnome help pages (click help on some applets, for instance, the weather applet). Worse, I get help in Spanish (the language of my kde setup) instead of English, the language in which my gnome is set. Is this adjustable? I don't like it. -- Cheers, Carlos Robinson
Another point. I noticed that my gnome calls kdesu instead gnomesu; it calls kde help viewer to display gnome help pages (click help on some applets, for instance, the weather applet). Worse, I get help in Spanish (the language of my kde setup) instead of English, the language in which my gnome is set.
Yes, there is, in gconf-editor, go through all the help related URL types in /desktop/gnome/url-handlers, ghelp, help, info, man, and where they're listed as gnome-help-NLD, change it to gnome-help. I'd not noticed that before, I'd better do an updated gnome-vfs2 package when I do the gnome-session too I guess ;) -- James Ogley james@usr-local-bin.org GNOME for SuSE: http://usr-local-bin.org/rpms
The Wednesday 2005-06-01 at 06:49 +0100, James Ogley wrote:
Another point. I noticed that my gnome calls kdesu instead gnomesu; it calls kde help viewer to display gnome help pages (click help on some applets, for instance, the weather applet). Worse, I get help in Spanish (the language of my kde setup) instead of English, the language in which my gnome is set.
Yes, there is, in gconf-editor, go through all the help related URL types in /desktop/gnome/url-handlers, ghelp, help, info, man, and where they're listed as gnome-help-NLD, change it to gnome-help.
Yes! It works! :-) I have changed ghelp and help for the moment, and I got the traditional gnome help windows. Ah, man and info already had "gnome-help". Thanks! What does that -NLD stand for, I wonder? It is a perl script.
I'd not noticed that before, I'd better do an updated gnome-vfs2 package when I do the gnome-session too I guess ;)
I'll have to try remember this. I have found other interesting things in that file :-) -- Cheers, Carlos Robinson
What does that -NLD stand for, I wonder? It is a perl script.
Novell Linux Desktop I would think... -- James Ogley james@usr-local-bin.org GNOME for SuSE: http://usr-local-bin.org/rpms
participants (7)
-
Anders Johansson -
Carl William Spitzer IV -
Carlos E. R. -
James Ogley -
Joe Morris (NTM) -
Mike Béla -
Richard Bos