"No Wallpaper" option permanent

[Member andfree]

Helpful

Up

0

::

Moving the window manager startup file and setting all “true” options to “false” in ~/.desktop-session.conf didn’t help.

[Anonymous]

Helpful

Up

0

::

$ chown -R dragon:dragon /home/dragon/.*
$ sudo chown -R dragon:dragon /home/dragon/.*

[Member sleekmason]

Helpful

Up

0

::

Try deleting the offending wallpaper from /usr/share?

And/or, Take a picture of black and switch to that.

[Member andfree]

Helpful

Up

0

::

Now I’m on the other laptop and all the files under home are owned by the user (the “chown” & “find” commands gave nothing as output). But the no-wallpaper doesn’t stay.

sleekmason wrote:

Try deleting the offending wallpaper from /usr/share?

I removed the whole /usr/share/wallpaper directory, but I only got rid of wallpaper on grub. On login & on desktop it’s still remains.

I also put a “#” before the line “DEFAULT=/usr/share/wallpaper/metro-station.jpg” in ~/.desktop-session/wallpaper.conf. It didn’t help.

sleekmason wrote:

Take a picture of black and switch to that.

My purpose is to load nothing that is not necessary, therefore none picture, even a black one.

• This reply was modified 5 years, 2 months ago by andfree.

[Forum Admin Dave]

Helpful

Up

0

::

I am guessing that the no wallpaper being set seemingly works with a min option do to an auto login setup ( nothing is loaded therefor black). @caprea do you have autologin enabled?

@andfree Great you have changed the startup and desktop-session.conf but like you said it will not help for a min option. Now with the settings changed the next step is to select the “icewm” option not “min-icewm” and the no wallpaper will work.

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member andfree]

Helpful

Up

0

::

Dave wrote:

Great you have changed the startup and desktop-session.conf but like you said it will not help for a min option. Now with the settings changed the next step is to select the “icewm” option not “min-icewm” and the no wallpaper will work.

I suppose this means there’s nothing I can do to get rid of the slim background in min-icewm and all I can do is to turn into icewm, after manually having disabled all these things loaded in this desktop, so as to make icewm as lightweight as min-icewm is.

[Anonymous]

Helpful

Up

0

::

FWIW, generating membuffer from a solid color does not result in noticeable “less memory consumed” vs loading/buffering a solid-colored imagefile (I have tested)

nothing I can do to get rid of the slim background

try:
sudo mv /usr/share/slim/themes/antiX/background.jpg /usr/share/slim/themes/antiX/background.jpg_bak
or you could
sudo mtpaint /usr/share/slim/themes/antiX/background.jpg
and edit so that it contains the solid color of your choice, then Save

My higher-priority issue would be: figure out who snuck onto the system and st0led your file permissions

[Member andfree]

Helpful

Up

0

::

Anonymous wrote:

My higher-priority issue would be: figure out who snuck onto the system and st0led your file permissions

I ran the “sudo chown” and the “find” commands and everything under home seems to be owned by the user now. I suppose it was me that I had “snuck onto the system” and, because of my habit to use always “sudo”, I had created several files owned by the root. Does it make sense?

[Forum Admin Dave]

Helpful

Up

0

::

For slim background as skidoo says…
https://wiki.archlinux.org/index.php/SLiM#Custom_background

For the desktop, yes disabling everything and moving to icewm should make it as light as the min option other than what may be used by the wallpaper that maybe set. If you have no wallpaper it will load the color you have selected.

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Moderator caprea]

Helpful

Up

0

::

@caprea do you have autologin enabled?
Yep.

[Member andfree]

Helpful

Up

0

::

Anonymous wrote:

try:
sudo mv /usr/share/slim/themes/antiX/background.jpg /usr/share/slim/themes/antiX/background.jpg_bak

This caused trouble. X was not loaded automatically. After “startx”, it was stuck. I rebooted with “alt + prt sc + reisub” and ran this to restore to the original situation:
sudo mv /usr/share/slim/themes/antiX/background.jpg_bak /usr/share/slim/themes/antiX/background.jpg

Anonymous wrote:

or you could
sudo mtpaint /usr/share/slim/themes/antiX/background.jpg
and edit so that it contains the solid color of your choice, then Save

This worked. I made it all black. But, unfortunately, htop shows the same, if not slightly increased, memory consumption.

[Forum Admin Dave]

Helpful

Up

0

::

What size have you made the black image?
I have not tested this as you are but I would think that the smaller the image the less buffer space it would take

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Anonymous]

Helpful

Up

0

::

What size have you made the black image?

size (dimensions) shouldn’t matter. Consider stretched, vs tiled, vs centered:
The factors involved in the size of membuffer for the root window: display size (dimensions), and display palette color depth.
Source image is released after reading. The imagedata is rescaled and/or merged with bgcolor (if necessary, for “centered” presentation).

htop shows the same, if not slightly increased, memory consumption.

As I mentioned in an another topic, I’ve noticed the current version of slim exhibits cumulative “memory leak” with each logout/login. So, for an apples-to-apples comparison of the before (original) and after (black image) mem usage, I recommend: boot+login+test then replace imagefile and reboot+login+test

This caused trouble. X was not loaded automatically. After “startx”, it was stuck.

Thanks for reporting the result. Absence of imagefile for background is one several whatif’s I’ve not yet gotten ’round to testing.

edit:
extra “too much info” removed

[Anonymous]

Helpful

Up

0

::

andfree, I found code buried within panel.cpp that may explain the “hang/stall” that you experienced. I have never, ever, seen docs mentioning this, but…

To prevent SLiM from choking when background.jpg is missing (and to invoke solid-color bg painting),
must specify within the themefile
( or within both the slim.conf+slim.template of your antiX system ~~ but I’m not coaching/advising you to touch those )
background_style ____ color
( valid values for this option are: stretch | tile | center | color )

^—- with that line in place ( edit /usr/share/slim/themes/antiX/antix.theme )
SLiM will paint a default bgcolor, unless the themefile also contains a line specifying desired hexidecimal RRGGBB color, e.g. for full-on bright red:
background_color ____ #FF0000

Default bgcolor = black; default fgcolor = white
so, in your case (desiring black) you could just skip (omit) the line mentioning background_color option.
I’m inviting you to test:
1) background.jpg is absent, and themefile specifies background_style ____ color
2) background.jpg is absent, and themefile specifies both background_style AND background_color

edit:
also asking you to view /var/log/slim.log and check whether it logged the “could not load background image for theme” event(s)

[Anonymous]

Helpful

Up

0

::

related note:
SLiM will alphablend any semi-transparent portions of a panel.png over the background image, but ignores any transparency of a background.png
In other words ~~ background_color does not bleed through any transparent portions of the background image.

[Author]

Posts