You are not logged in.
Recently my wallpaper started reverting to the default gray after waking from sleep/suspend, and logging in, replacing my chosen wallpaper. Logging out and back in reinstates the wallpaper of my choice.
Last edited by isosceles (2015-11-17 03:35:24)
Offline
Recently
What had you changed in the system immediately before the change in behaviour?
Please post the content of ~/.config/openbox/autostart
Offline
my wallpaper started reverting to the default
is this the same as on the login screen?
how are you setting the wallpaper?
if you are using the default, nitrogen, there's a file that sometimes gets corrupted, i think it's in ~/.config/nitrogen.
take a look, optionally edit manually or delete and choose wallpaper again.
Offline
isosceles wrote:Recently
What had you changed in the system immediately before the change in behaviour?
Please post the content of ~/.config/openbox/autostart
I don't recall changing anything recently... if I did I'd have followed that lead.
autostart contents:
## Openbox autostart
## ====================
## When you login to your BunsenLabs Openbox session, this autostart script
## will be executed to set-up your environment and launch any applications
## you want to run at startup.
##
## Note*: some programs, such as 'nm-applet' are run via XDG autostart.
## Run
## /usr/lib/i386-linux-gnu/openbox-xdg-autostart --list
## or
## /usr/lib/x86_64-linux-gnu/openbox-xdg-autostart --list
## to list any XDG autostarted programs.
##
## More information about this can be found at:
## [url]http://openbox.org/wiki/Help:Autostart[/url]
##
## If you do something cool with your autostart script and you think others
## could benefit from your hack, please consider sharing it at:
## [url]http://bunsenlabs.org[/url]
##
## GNOME PolicyKit and Keyring
eval $(gnome-keyring-daemon -s --components=pkcs11,secrets,ssh,gpg) &
## for authentication
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
## Set root window colour
hsetroot -solid "#2E3436" &
nitrogen --restore &
bl-compositor --start &
#(sleep 2; tint2) &
## To start a saved tint2 session, comment out the line above, and uncomment:
(sleep 2s && bl-tint2-session) &
## Run the conky
#conky -q &
## To start a saved Conky session, comment out the line above, and uncomment:
(sleep 2s && bl-conky-session --autostart) &
## Volume control for systray
(sleep 2; volti) &
## Volume keys daemon
xfce4-volumed &
## Start Clipboard manager
(sleep 3; clipit) &
## Start Thunar Daemon
thunar --daemon &
## Enable power management
xfce4-power-manager &
## Start xscreensaver
xscreensaver -no-splash &
## Detect and configure touchpad. See 'man synclient' for more info.
if egrep -iq 'touchpad' /proc/bus/input/devices; then
synclient VertEdgeScroll=1 &
synclient TapButton1=1 &
fi
## Set keyboard settings - 250 ms delay and 25 cps (characters per second) repeat rate.
## Adjust the values according to your preferances.
xset r rate 250 25 &
## Turn on/off system beep
xset b off &
## The following command runs hacks and fixes for #! LiveCD sessions.
## Safe to delete after installation.
#bl-cowpowers &
## bl-welcome - post-installation script, will not run in a live session and
## only runs once. Safe to remove.
(sleep 10; bl-welcome --firstrun) &
## bl-fortune - have the system come up with a little adage (not yet enabled)
#(sleep 120; bl-fortune) &
(sleep 120; bl-fortune) &
bl-compositor --restart
[ MOD EDIT - Please use [ code ] tags ]
Last edited by damo (2015-11-15 18:35:11)
Offline
isosceles wrote:my wallpaper started reverting to the default
is this the same as on the login screen?
how are you setting the wallpaper?
if you are using the default, nitrogen, there's a file that sometimes gets corrupted, i think it's in ~/.config/nitrogen.
take a look, optionally edit manually or delete and choose wallpaper again.
Yes, same as the login screen. I do use Nitrogen to set my wallpaper. I've just deleted the config file, reselected my image of choice and it's fine now. Thanks for the help.
Offline
If you think that fixed things, then please edit the title of your first post and add [SOLVED]. It may help others looking for an answer
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
@Hoas & @damo, i just noticed (both on my own vanilla bl and on the autostart above) that autostart executes hsetroot & nitrogen in quick succession.
this is pointless for many reasons:
openbox-session already looks for a bg setter to make the bg gray, see /usr/lib/openbox/openbox-autostart (*)
hsetroot is not installed
it would only last a split second anyway because nitrogen
(*) actually op's problem negates the first one. it would seem like starting openbox through the display manager does not execute that script?
Offline
@Hoas & @damo, i just noticed (both on my own vanilla bl and on the autostart above) that autostart executes hsetroot & nitrogen in quick succession.....
I think the hsetroot line is a hold-over from the cb autostart, but it should be commented out (it is in my BL autostart). Anyway, I've raised a github issue - thanks for the catch
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
If you think that fixed things, then please edit the title of your first post and add [SOLVED]. It may help others looking for an answer
Thanks for the reminder... always forget that. That said, I didn't find the cause. Just another computing mystery to me.
Last edited by isosceles (2015-11-17 03:36:29)
Offline
That said, I didn't find the cause. Just another computing mystery to me.
it would have been nice to take a look at that corrupt nitrogen file.
do you have multiple monitors? iirc, it might have something to do with that.
in any case, a known problem with nitrogen.
Offline
it would have been nice to take a look at that corrupt nitrogen file.
do you have multiple monitors? iirc, it might have something to do with that.
in any case, a known problem with nitrogen.
Yeah, too bad I don't have a backup to retrieve the lost file from. I have one monitor.
Offline