You are not logged in.
Hello Everybody!
I have a problem.. when in change my wallpaper via > Preferences >> Wallpaper and press button apply the change is efective.. but after logout - login or reboot the appear again the green/blue wallpaper again..
Any can help me with this little problem??
Last edited by Head_on_a_Stick (2018-05-20 20:07:29)
Offline
I'm not having this issue with my current official Helium 64 bit setup, but I did experience it several times while testing our alpha, beta and RC1 images. My quick-fix was to use feh to set the wallpaper instead, comment out the nitrogen entry in the Openbox autostart file and add the following line...
sh ~/.fehbg &@johnraff posted a fix, but since feh works I never tried it. I'll look for it and post back...
I don't care what you do at home. Would you care to explain?
Offline
Here it is...
You've probably still got an old-style nitrogen/bg-saved.conf. Make sure it has
[xin_-1]
at the top, not whatever it was before.
I don't care what you do at home. Would you care to explain?
Offline
Grr, I just got bit by this issue again. Moving this thread to Bug Reports.
I don't care what you do at home. Would you care to explain?
Offline
I set my wall via nitrogen to BL-Beam-grey.png, Zoomed Fill, Apply, logout and in, I still have the default wall. Nitrogen's GUI shows the grey version as "Currently set background". Running 'nitrogen -restore' in a terminal or clicking Apply in the GUI sets the grey wall, but it is lost again if I logout. ~/.config/nitrogen/bl-saved.cfg shows the following...
[xin_-1]
file=/usr/share/images/bunsen/wallpapers/default/BL-beam.png
mode=5
bgcolor=#001e44
[:0.0]
file=/home/rachel/Pictures/wallpapers/bunsen/default/BL-beam-grey.png
mode=5
bgcolor=#000000I have no svg files in my wallpaper folder, nor anything other than the default BL wallpapers.
The only terminal output is...
rachel@TyrellCorp:~$ nitrogen --restore
UNKNOWN ROOT WINDOW TYPE DETECTED, will attempt to set via normal X procedure
rachel@TyrellCorp:~$@joseh55|, let me know if you need a walk-through for using feh to set your wall while we try to resolve this.
I don't care what you do at home. Would you care to explain?
Offline
No problems saving a wallpaper setting on a fresh install. I'll try and see if and where it goes wrong.
I don't care what you do at home. Would you care to explain?
Offline
Confirming it was the [xin_-1] for me
https://forums.bunsenlabs.org/viewtopic … 494#p60494
volvox.biz a very tedious daily account of life during covid,
Offline
I set my wall via nitrogen to BL-Beam-grey.png, Zoomed Fill, Apply, logout and in, I still have the default wall. Nitrogen's GUI shows the grey version as "Currently set background". Running 'nitrogen -restore' in a terminal or clicking Apply in the GUI sets the grey wall, but it is lost again if I logout. ~/.config/nitrogen/bl-saved.cfg shows the following...
[xin_-1] file=/usr/share/images/bunsen/wallpapers/default/BL-beam.png mode=5 bgcolor=#001e44 [:0.0] file=/home/rachel/Pictures/wallpapers/bunsen/default/BL-beam-grey.png mode=5 bgcolor=#000000I have no svg files in my wallpaper folder, nor anything other than the default BL wallpapers.
The only terminal output is...
rachel@TyrellCorp:~$ nitrogen --restore UNKNOWN ROOT WINDOW TYPE DETECTED, will attempt to set via normal X procedure rachel@TyrellCorp:~$@joseh55|, let me know if you need a walk-through for using feh to set your wall while we try to resolve this.
Hi!
At this moment i resolv the inconvenient deleting this lines
######################
[xin_-1]
file=/usr/share/images/bunsen/wallpapers/default/BL-beam.png
mode=5
bgcolor=#001e44
#####################
and moving "nitrogen --restore" at the final lines of autostart script
Thank You for your answer.. I like very much bunsenlabs
If bunsenlabs need help translating to spanish i can help
Offline
If bunsenlabs need help translating to spanish i can help
See this Google+ group...
https://plus.google.com/communities/102 … 1db4cd86df
/Off Topic
I don't care what you do at home. Would you care to explain?
Offline
At this moment i resolv the inconvenient deleting this lines [...]
Works very well!
Offline
nitrogen --restore WFM on a fresh install. I'm wondering if setting a Blob theme is corrupting bg-saved.cfg, because here's what my new, working one looks like, the default entry has been overwritten and there's no second entry...
[xin_-1]
file=/home/deckard/Pictures/wallpapers/bunsen/default/BL-beam-grey.png
mode=5
bgcolor=#001e44I don't care what you do at home. Would you care to explain?
Offline
nitrogen --restore WFM on a fresh install. I'm wondering if setting a Blob theme is corrupting bg-saved.cfg, because here's what my new, working one looks like, the default entry has been overwritten and there's no second entry...
[xin_-1] file=/home/deckard/Pictures/wallpapers/bunsen/default/BL-beam-grey.png mode=5 bgcolor=#001e44
So should the extraneous entries be removed from bg-saved.cfg?
Real Men Use Linux
Offline
hhh wrote:nitrogen --restore WFM on a fresh install. I'm wondering if setting a Blob theme is corrupting bg-saved.cfg, because here's what my new, working one looks like, the default entry has been overwritten and there's no second entry...
[xin_-1] file=/home/deckard/Pictures/wallpapers/bunsen/default/BL-beam-grey.png mode=5 bgcolor=#001e44So should the extraneous entries be removed from bg-saved.cfg?
No, I'm just reporting what I'm seeing, I'm not proposing a fix. But my workaround of using feh instead works fine if you are bitten by this bug ATM.
I don't care what you do at home. Would you care to explain?
Offline
I can't reproduce this issue. Changing wallpaper directly via the menu or via a BLOB theme change works and survives logout/in. bg-saved.cfg has only a single entry the whole time. There is no entry starting [:0.0], and nor should there be.
If anyone is still getting this problem on a new install (not upgrade from Hydrogen/Deuterium) could you please post instructions on how to reproduce it?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
@johnraff, WFM with a fresh install. I have 2 partitions now breathing fresh helium, I'll keep one as a control and mess with the other, see what I can see over the next week or two.
I don't care what you do at home. Would you care to explain?
Offline
What if you deleted bg-saved.cfg so will nitrogen recreate it?
Real Men Use Linux
Offline
What if you deleted bg-saved.cfg so will nitrogen recreate it?
I tried that and it didn't work, but now with a fresh install I can't reproduce, bg-saved.conf is instantly and correctly overwritten every time.
I don't care what you do at home. Would you care to explain?
Offline
DeepDayze wrote:What if you deleted bg-saved.cfg so will nitrogen recreate it?
I tried that and it didn't work, but now with a fresh install I can't reproduce, bg-saved.conf is instantly and correctly overwritten every time.
Ahh I see...sounds like a bug to me.
Real Men Use Linux
Offline
It's happened again after installing Gimp and gimp-extras via the menu. The wall stuck for a couple of reboots, but now it's back to Beam...
[xin_-1]
file=
mode=5
bgcolor=#001e44
[:0.0]
file=/home/rachel/Pictures/wallpapers/KDE/Code_Poets_Dream/contents/images/1280x1024.jpg
mode=5
bgcolor=#000000Honestly, I'm ready to strip nitrogen, pnmixer, tint2 and a whole bunch more (conky, for one) out of BL. It's a great desktop, but it could be leaner and more reliable.
I don't care what you do at home. Would you care to explain?
Offline
I still can't reproduce this issue, even after installing those packages (what led you to think they were involved btw?) Have to test this on a VM unfortunately, because I'm setting the desktop differently on my main system, but it all seems solid enough.
@hhh how did you set that wallpaper? I'm really struggling to imagine where that [:0.0] entry came from. Are you sure there aren't some archaic config files left in your $HOME?
I'm also curious to hear what you object to about pnmixer. It worked fine in #! and still does for me in Helium. Maybe a separate topic?
There are alternatives to tint2 of course, if it turns out to be buggy - is it though? Or do you plan to work with no panel at all?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online