BL stretch BUG: nitrogen --restore fails

DustyB · 2017-09-16 14:44:47

I have found this bug as well and it somehow has something to do with "autostart" when I change the autostart order for different programs it is either nitrogen or tint2 that fails to start .. finally while experimenting i found that everything goes back to normal if "conky" is #ed out in autostart .. then again i am a lay man in the company of many great men here so there is quite a big possibility that i am wrong

## 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/x86_64-linux-gnu/openbox-xdg-autostart --list
## to list any XDG autostarted programs.
##
## More information about this can be found at:
## http://openbox.org/wiki/Help:Autostart
##
## If you do something cool with your autostart script and you think others
## could benefit from your hack, please consider sharing it at:
## http://forums.bunsenlabs.org (registration required)
##

### SETTINGS START

## Turn on/off system beep.
xset b off

## 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

## Add keyboard mapping.
#xmodmap -e "keysym Insert = Multi_key"

## Disable CapsLock
setxkbmap -option ctrl:nocaps
# alternative: use as compose key
#setxkbmap -option compose:caps

## Group start:
## 1. nitrogen - restores wallpaper
## 2. compositor
## 3. sleep - give compositor time to start
## 4. conky conky -q && \
## 5. tint2 panel
(\
nitrogen --restore && \
bl-compositor --start && \
sleep 2s && \
tint2 \
) &

## Start PulseAudio
## (This replaces /etc/xdg/autostart/pulseaudio.desktop
## which is disabled by ~/.config/autostart/pulseaudio.desktop.)
## NOTE: PulseAudio must be started before volumeicon
bl-start-pulseaudio-x11

## Volume control for systray
(sleep 2s && volumeicon) &

## Volume keys daemon
xfce4-volumed &

## Enable power management
xfce4-power-manager &

## Start Thunar Daemon
thunar --daemon &

### TOUCHPAD: comment out the next two entries if you don't have one

## Configure touchpad. See 'man synaptics' for more info.
synclient VertEdgeScroll=1 HorizEdgeScroll=1 TapButton1=1 2>/dev/null

## Disable touchpad while typing
syndaemon -i .5 -K -t -R -d &

### TOUCHPAD END

## GNOME PolicyKit authentication
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &

## Start the battery applet
# fdpowermon &

## Start Clipboard manager
# clipit &

### SETTINGS END

Last edited by DustyB (2017-09-17 09:35:09)

Head_on_a_Stick · 2017-09-16 14:48:52

Anybody who experiences this problem should probably post their entire openbox autostart file.

This will print out a de-commented version:

grep -v '^#' ~/.config/openbox/autostart

We changed that file a while ago to tidy it up and these problems sound like they may be caused by the old version.

tknomanzr · 2017-09-16 17:11:20

I am unable to replicate this. However, does rearranging ~/.config/openbox/autostart to look like this help?

## Set a wallpaper then start the Conky session (the default conkyrc will run if no sessions have been set)
nitrogen --restore; bl-conky-session --autostart &

This will ensure that bl-conky-session only runs once nitrogen has restored it's wallpaper.

KrunchTime · 2017-09-17 00:01:38

johnraff wrote:

^Are you sure it's not the wrong syntax in ~/.config/nitrogen/bg-saved.cfg?
in Stretch it now begins with
[xin_-1]
not the former
[:0.0]
I've had no issues with restoring wallpaper in helium-dev since making that change.

That's a new one to me. I wasn't aware of anything else being required other than adding the appropriate entry in ~/.config/openbox/autostart.

Head_on_a_Stick wrote:

Anybody who experiences this problem should probably post their entire openbox autostart file.
...
We changed that file a while ago to tidy it up and these problems sound like they may be caused by the old version.

I'm opting to include most of the comments for better readability. This is from my BL-Unstable install on my desktop, installed in June 2017.

### SETTINGS START

## Turn on/off system beep.
xset b off &

## 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 &

## Set root window color
## hsetroot -solid "#2E3436" &

### SETTINGS END

## GNOME PolicyKit authentication
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &

## Set a wallpaper
nitrogen --restore &

## Compton
## NOTE: composition must be started before tint2
bl-compositor --start &

## Start the tint2 session (the default tint2 will run if no sessions have been set)
(sleep=2s && bl-tint2-session) &

## Start the Conky session (the default conkyrc will run if no sessions have been set)
bl-conky-session --autostart &

## Start PulseAudio
## (This replaces /etc/xdg/autostart/pulseaudio.desktop
## which is disabled by ~/.config/autostart/pulseaudio.desktop.)
## NOTE: PulseAudio must be started before volumeicon
bl-start-pulseaudio-x11 &

## Volume control for systray
(sleep 2s && pnmixer) &

## Start xscreensaver
xscreensaver -no-splash &

## Start redshift
redshift -l [redacted] &

## Conky Accuweather 10-day forecast
(sleep 60s && conky -c /home/<user>/bin/1_accuweather/.conkyrc_1_images_2016) &

## Conky Accuweather hourly forecast
(sleep 70s && conky -c /home/<user>/bin/1_accuweather/.conkyrc_1_hourly_2016) &

## Conky NWS 6-day forecast
(sleep 80s && conky -c /home/<user>/bin/3_conky_forecast_nws/.conkyrc_nws_Long_Messages_Wide) &

I've began using feh and it is working fine so far. In fact, I think I now prefer feh over nitrogen. Yeah, I know...you can't pick from a list in feh, but I have so many images to choose from that it is sometimes laborious to find the exact image I want when using nitrogen.

Last edited by KrunchTime (2017-09-17 00:13:40)

Head_on_a_Stick · 2017-09-17 00:57:36

^ Yes, that's the old autostart file with all the unnecessary fork()s and potential conflicts in place.

Update to the new version, it's much better:

https://github.com/BunsenLabs/bunsen-co … /autostart

The changes will have to be merged manually, of course 8)

KrunchTime · 2017-09-17 01:09:19

...unnecessary fork()s and potential conflicts... ? I just diff'd the original file with what I now have and there isn't much difference. By forks, are you referring to the use of &? I can't remember specific details, but I've found the stock autostart file not to work optimally for me. What I provided above seems to work better, other than the possible issue with nitrogen.

johnraff · 2017-09-17 02:40:39

KrunchTime wrote:

I wasn't aware of anything else being required other than adding the appropriate entry in ~/.config/openbox/autostart.

What's expected when installing helium-dev is that you allow the system to install all the default user config files from /usr/share/bunsen/skel, along with all the other configuration. This will be done automatically in a new install.

If you import old config files from other systems then it's at your own risk, and the least we can expect when responding to bug reports is that you tell us what changes you've made to the default system. (The same problem ocurred over keyboard shortcuts not present in your obsolete rc.xml.)

johnraff · 2017-09-17 02:43:29

KrunchTime wrote:

I can't remember specific details, but I've found the stock autostart file not to work optimally for me. What I provided above seems to work better, other than the possible issue with nitrogen.

Really, a bug report on what problems you had with the stock autostart file would have been much more useful for us.

If you have issues with your customized file, then please post a request for help in "Help andSupport".

KrunchTime · 2017-09-17 23:40:12

johnraff wrote:

What's expected when installing helium-dev is that you allow the system to install all the default user config files from /usr/share/bunsen/skel, along with all the other configuration.

Did that, saved the defaults, and then replaced the defaults with my previously saved configs from BL-Hydrogen.

johnraff wrote:

If you import old config files from other systems then it's at your own risk, and the least we can expect when responding to bug reports is that you tell us what changes you've made to the default system. (The same problem ocurred over keyboard shortcuts not present in your obsolete rc.xml.)

Noted...I'll try to remember that in the future.

dbvolvox · 2018-05-14 15:24:35

johnraff wrote:

^Are you sure it's not the wrong syntax in ~/.config/nitrogen/bg-saved.cfg?
in Stretch it now begins with
[xin_-1]
not the former
[:0.0]
I've had no issues with restoring wallpaper in helium-dev since making that change.

I needed to do this on my recent install of the Helium release.

jesito · 2019-02-10 06:12:11

dbvolvox wrote:

johnraff wrote:
^Are you sure it's not the wrong syntax in ~/.config/nitrogen/bg-saved.cfg?
in Stretch it now begins with
[xin_-1]
not the former
[:0.0]
I've had no issues with restoring wallpaper in helium-dev since making that change.
I needed to do this on my recent install of the Helium release.

Me too. I've just installed Helium (64bits) from the stock image and got the same problem.
To me it seems that at any time we add a new wallpaper it gets added with the old [:0.0] instead of the new [xin_-1]...

This is my bg-saved.cfg just after adding a new wallpaper:

[xin_-1]
file=/home/jesito/Pictures/wallpapers/wallpaper-1024x768.jpg
mode=4
bgcolor=#000000

[:0.0]
file=/home/jesito/Pictures/wallpapers/537554_jestingstock-com-hd-camera-lens-wallpapers_1680x1050_h.jpg
mode=4
bgcolor=#000000

At restart it keeps showing the first wallpaper, if replacing [:0.0] in the second by [xin_-1] it shows the later.

hathor · 2019-02-28 07:36:42

Change nitrogen by oboinus

hhh · 2019-03-01 01:08:58

^ Moving forward, it's not available in buster. It depends on feh anyway, and you can set a background with feh and add the following to your Openbox openstart to make it persistent (comment out nitrogen --restore, of course)...

sh ~/.fehbg &

PackRat · 2019-03-01 02:11:41

You can also use something like:

feh ~/wallpaper -g 640x480 --scale-down

in a menu or *.desktop file to get a slideshow window for your wallpapers. Use the left/right arrow keys to cycle through the images; up/down to zoom. RIght click on the window for a menu with an option to set the image as wallpaper.

Change "~/wallpaper" to your wallpaper location and set the geometry to the same ratio as your screen and it's a pretty handy utility.

Last edited by PackRat (2019-03-01 02:12:08)

damo · 2019-03-01 02:25:08

^ I had forgotten about that. Great feature

#21 2017-09-16 14:44:47

Re: BL stretch BUG: nitrogen --restore fails

#22 2017-09-16 14:48:52

Re: BL stretch BUG: nitrogen --restore fails

#23 2017-09-16 17:11:20

Re: BL stretch BUG: nitrogen --restore fails

#24 2017-09-17 00:01:38

Re: BL stretch BUG: nitrogen --restore fails

#25 2017-09-17 00:57:36

Re: BL stretch BUG: nitrogen --restore fails

#26 2017-09-17 01:09:19

Re: BL stretch BUG: nitrogen --restore fails

#27 2017-09-17 02:40:39

Re: BL stretch BUG: nitrogen --restore fails

#28 2017-09-17 02:43:29

Re: BL stretch BUG: nitrogen --restore fails

#29 2017-09-17 23:40:12

Re: BL stretch BUG: nitrogen --restore fails

#30 2018-05-14 15:24:35

Re: BL stretch BUG: nitrogen --restore fails

#31 2019-02-10 06:12:11

Re: BL stretch BUG: nitrogen --restore fails

#32 2019-02-28 07:36:42

Re: BL stretch BUG: nitrogen --restore fails

#33 2019-03-01 01:08:58

Re: BL stretch BUG: nitrogen --restore fails

#34 2019-03-01 02:11:41

Re: BL stretch BUG: nitrogen --restore fails

#35 2019-03-01 02:25:08

Re: BL stretch BUG: nitrogen --restore fails

Board footer