Gnome-appearance-properties gets installed with a default collection of wallpapers, themes, backgrounds, or whatever they're called; I have plenty of my own that I like better, and always delete those. But some screensavers, such as Slip in xscreensaver, still find them -- apparently in /usr/share/backgrounds. I'd like to get rid of them. But they seem to be protected in some way, at least against my userid.
Will it foul something up to the nines if I just go to the CLI as root, cd down as far as the bottom directories, and just use rm a/o rmdir on them all?
How about if I eliminate only what rm will take, and leave all the directories in place, but empty?
Or maybe put some of my own collection in instead?
Beartooth wrote:
Gnome-appearance-properties gets installed with a default collection of wallpapers, themes, backgrounds, or whatever they're called; I have plenty of my own that I like better, and always delete those. But some screensavers, such as Slip in xscreensaver, still find them -- apparently in /usr/share/backgrounds. I'd like to get rid of them. But they seem to be protected in some way, at least against my userid.
Will it foul something up to the nines if I just go to the CLI as root, cd down as far as the bottom directories, and just use rm a/o rmdir on them all?
How about if I eliminate only what rm will take, and leave all the directories in place, but empty?
Or maybe put some of my own collection in instead?
I like "put my own collection in as additions" just in case. There probably wouldn't be a problem with deleting, but adding your own is sure to avoid any issue with something looking for an image.
Beartooth spake thusly:
Gnome-appearance-properties gets installed with a default collection of wallpapers, themes, backgrounds, or whatever they're called; I have plenty of my own that I like better, and always delete those. But some screensavers, such as Slip in xscreensaver, still find them -- apparently in /usr/share/backgrounds. I'd like to get rid of them. But they seem to be protected in some way, at least against my userid.
"gnome-appearance-properties" is part of the "[GNOME] control-center" package. That package does not come with any wallpaper.
The packages that *do* comee with wallpaper (assuming you only have GNOME installed - vs. GNOME & KDE, XFCE.....) include
desktop-backgrounds-basic
gnome-backgrounds & the leonidas-backgrounds*
packages.
Do a search for them with yum, packagekit, or yumex and remove any or all of them that you may have installed and your system wallpapers shouuld be gone.
Personally, I like them, but most of the ones I use are also found elsewhere and I just keep them in ~/Pictures/backgrounds.
Scott
Scott Beamer wrote:
Do a search for them with yum, packagekit, or yumex and remove any or all of them that you may have installed and your system wallpapers shouuld be gone.
I don't think that's possible, the default wallpapers are dragged in by dependencies.
Kevin Kofler
On 03/07/09 22:19, Beartooth wrote:
Gnome-appearance-properties gets installed with a default collection of wallpapers, themes, backgrounds, or whatever they're called; I have plenty of my own that I like better, and always delete those.
rpm -qa | grep backgrounds
sudo rpm -e --nodeps "those backgrounds you found"
Regards,
Frank
Frank Murphy wrote:
sudo rpm -e --nodeps "those backgrounds you found"
IMO the --nodeps option is always a bad suggestion. Anyone that knows enough to use it reasonably will also know enough to find it in the man page. For everyone else, it should be considered off-limits. :)
On 06/07/09 20:33, Todd Zullinger wrote:
Frank Murphy wrote:
sudo rpm -e --nodeps "those backgrounds you found"
IMO the --nodeps option is always a bad suggestion. Anyone that knows enough to use it reasonably will also know enough to find it in the man page. For everyone else, it should be considered off-limits. :)
Normally I would agree.
Unfortunately man pages can be takes too literally at times.
"installing or upgrading" Can't use it for uninstalling so ;)
Regards,
Frank
On Mon, 06 Jul 2009 15:33:39 -0400, Todd Zullinger wrote:
Frank Murphy wrote:
sudo rpm -e --nodeps "those backgrounds you found"
IMO the --nodeps option is always a bad suggestion. Anyone that knows enough to use it reasonably will also know enough to find it in the man page. For everyone else, it should be considered off-limits. :)
OK, afaik I never heard of it. So are you saying just omit it? I.e., do an rpm -e on whatever rpm -qa | grep backgrounds found?
Or is it not that simple??
Beartooth wrote:
OK, afaik I never heard of it. So are you saying just omit it? I.e., do an rpm -e on whatever rpm -qa | grep backgrounds found?
My suggestion is that if you have to use --nodeps to remove a package, you should only do it if you very well what it does. It's akin to walking around with a loaded gun in your pocket, with the safety off and a hair trigger. Quite easy to end up with a hold in your body in a place you don't want one. :)
On 06/07/09 21:03, Todd Zullinger wrote:
Beartooth wrote:
OK, afaik I never heard of it. So are you saying just omit it? I.e., do an rpm -e on whatever rpm -qa | grep backgrounds found?
My suggestion is that if you have to use --nodeps to remove a package, you should only do it if you very well what it does. It's akin to walking around with a loaded gun in your pocket, with the safety off and a hair trigger. Quite easy to end up with a hold in your body in a place you don't want one. :)
For the backgrounds as such, it should be fine.
Best bet is to seek advice on a per use basis.
Regards,
Frank