Posts by Cloudstone

Cloudstone · Help & Support (Stable)

Solved it guys! Thanks for the help.

It had to do with the TV being connected to my computer via an HDMI cable. I saved a shell script in xrandr for my setup, and added that line into my autostart config file, right before conky start. That solved everything. Now I boot into a single-screen and my wallpaper of choice.

## Set display for one monitor
xrandr --output DP-1 --off --output HDMI-0 --off --output DVI-I-2 --mode 1920x1200 --pos 0x0 --rotate normal --output DVI-I-1 --off --output DVI-I-0 --off --output DVI-I-3 --off --output DP-0 --off

Thanks again!

Cloudstone · Help & Support (Stable)

OK, I just moved my wallpaper folder from my other HD to my ~/images/wallpapers folder, reconfigured my config files to the new directory (both menu.xml and nitrogen.cfg), did a reboot and again the same thing. The standard #! wallpaper was set. However, when I opened Nitrogen I found that atleast my own wallpaper folder was loaded. So now I just had to click apply and my wallpaper was set.

Cloudstone · Help & Support (Stable)

photonucleon wrote:

Cloudstone wrote:
iann wrote:
Try that on the command line and see if you get an error. There might also be something earlier in autostart that is causing it to crash or hang.
Sorry but try what exactly? Do you mean that I should edit the menu.xml file in the terminal?
Try the command on the command line by opening the terminal and enter
nitrogen --restore
and see if any errors appear in the terminal window.

Ok, I did that and this is the output:

cloudstone@crunchbang:~$ nitrogen --restore
/usr/share/themes/shearwater/gtk-2.0/gtkrc:339: Unable to locate image file in pixmap_path: "panel-bg-dark.png"
/usr/share/themes/shearwater/gtk-2.0/gtkrc:339: Unable to locate image file in pixmap_path: "panel-bg-dark.png"

Cloudstone · Help & Support (Stable)

Thanks a lot for your replies. I've got a lot to study about now smile

iann wrote:

Try that on the command line and see if you get an error. There might also be something earlier in autostart that is causing it to crash or hang.

Sorry but try what exactly? ops Do you mean that I should edit the menu.xml file in the terminal? The only thing before nitrogen in my openbox autostart file is:

## GNOME PolicyKit and Keyring
eval $(gnome-keyring-daemon -s --components=pkcs11,secrets,ssh,gpg) &

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

damo wrote:

Did you add the image directory path in Nitrogen -> Preferences, (the config file is .config/nitrogen/nitrogen.cfg) then restart Openbox?

Yes, I can confirm that the directory path in nitrogen.cfg has the same path as my wallpaper folder (dirs=/media/Extra/Images/wp;).

pvsage wrote:

Is the separate HD internal or external? In either case, it's possible the drive isn't being mounted automatically at login and needs to be added to /etc/fstab.

It's an internal HD. That does sound like something that could be the case, however my /etc/fstab folder is completely empty. No hidden files either. What exactly do I need to add in order for the drive to be mounted at login?

Snap wrote:

Sometimes the timing (sleep time) is important depending on the different hardwares. I had to set mine in order to make nitrogen to behave besides the right configurations. For some reason, in my system, conky must be the last thing launched in autostart or nitrogen gets messed up. Once I've found the right delays everything works flawlessly.

Hmm, sounds interesting. How does the sleep time change depending on the hardware? I have a relatively fast computer (i5 3,4GHz, 8GB RAM). Where do you edit sleep time?

Cloudstone · Help & Support (Stable)

Thanks for your reply!

I just checked my menu.xml, and replaced the adress with the folder that my wallpapers are in ( /media/Extra/Images/wp ). They are on a separate harddrive, but that shouldn't matter right? I just rebooted and now there were no files loaded in Nitrogen so I had to again readd my wallpaper folder.

As for the autostart-file; I can confirm that the command line looks like it should:

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

and so on.

Any ideas? Thanks again!

Cloudstone · Help & Support (Stable)

Hi!

I just started getting things running and I'm pleased with the OS as a whole! However, #! doesn't seem to want to save some of my settings (desktop wallpaper, display settings in ARandR). Every time I boot into #!, I need to set my wallpaper again, and also deactivate my HDMI in ARandR so that conky will show up on my screen and not my TV. My computer is always hooked up to the TV with an HDMI cable.

Btw, I should add that I'm a newbie and that I searched the wiki and the forums for a solution but couldn't find one.

Anyone know why #! isn't saving these settings for me?
Thanks a lot. :-)

EDIT:
Some more information for you.

When I select "Choose Wallpaper" from openbox, the folder with my wallpapers that I previously added to the list is gone. However it's there in the preferences list. So I need to remove it from preferences, re-add it and then my images appear again in the list. And what's strange is that the image I previously selected as my wallpaper is "Currently set background", even though it isn't. I have to re-add my folder in Nitrogen every time I close it.

Cloudstone · Help & Support (Testing/Unstable)

Thanks for your reply! Unfortunately though, I don't know how to add a kernel option to the grub menu.. I boot directly into the USB and then i'm greeted with three options; live session, install and memory test. Is there no way to add a kernel boot option into the live session or do I have to install crunchbang first?

Any help is greatly appreciated. Thanks!

Cloudstone · Help & Support (Testing/Unstable)

First of all I want to say hi, I'm Amir from Sweden, long time hardware fanatic now finally trying to learn Linux and after a bit of reading I want to give crunchbang a try. I've been lurking here for a short while and the level of aid and friendliness in this community is astounding and I'm looking forward to some day being able to aid others myself. But first things first... I can't seem to be able to boot into a live session from the USB! I've tried with a Linux Mint Debian Edition too, same thing happens there. I see the desktop then everything except the mouse freezes. I know the USB is bootable because it works on another computer.

I then hit ctrl+alt+F1 and the following message greeted me:
[ 58.907914] [drm] nouveau 0000:01:00.0: GPU lockup - switching to software fbcon

Seems like it's my nvidia card holding up. And so I need to install the nvidia drivers later after the install. How can I fix this so that I can boot into a live session?

Here are my system specs:
MB - Asus Z87-A
CPU - i5 4670k @ 3.4 Ghz (stock for now, will eventually overclock later)
Mem - 2x4GB Corsair Vengeance @ 1500Mhz
GPU - Asus GeForce GTX580

Thanks again

CrunchBang Linux

SEARCH

#1 Re: Help & Support (Stable) » [SOLVED] #! Doesn't save wallpaper and display settings after reboot » 2014-02-12 11:13:07

#2 Re: Help & Support (Stable) » [SOLVED] #! Doesn't save wallpaper and display settings after reboot » 2014-02-11 21:51:43

#3 Re: Help & Support (Stable) » [SOLVED] #! Doesn't save wallpaper and display settings after reboot » 2014-02-11 21:42:23

#4 Re: Help & Support (Stable) » [SOLVED] #! Doesn't save wallpaper and display settings after reboot » 2014-02-11 21:22:05

#5 Re: Help & Support (Stable) » [SOLVED] #! Doesn't save wallpaper and display settings after reboot » 2014-02-11 19:02:03

#6 Help & Support (Stable) » [SOLVED] #! Doesn't save wallpaper and display settings after reboot » 2014-02-11 13:21:51

#7 Re: Help & Support (Testing/Unstable) » GPU Lockup problem » 2013-10-22 16:00:19

#8 Help & Support (Testing/Unstable) » GPU Lockup problem » 2013-10-21 16:21:31

Board footer