X(openbox?) won't open automatically

auxym · 2014-03-04 19:48:40

I don't think gnome is the problem. In fact, I did not have gnome show up when I did my dist-upgrade.

In fact, it seems slim never gets to execute it's login_cmd. I edit my /etc/slim.conf with the following lines:

login_cmd echo %session >> /home/<user>/startup

I then rebooted, logged in to slim, then switched to a tty and checked the file. Nothing is being written. /var/log/slim.log has only the following line:

slim : waiting for X server to begin accepting connections

BTW, you can forget my previous comment about xrdb, it was because I was invoking it in a tty without X running. Now, it seems something weird is going on with slim not being able to connect to X?

EDIT
Ok fixed it.

$ sudo apt-get remove slim 
$ sudo apt-get install slim

(Y when prompted to overwrite slim.conf)

(then edit /etc/slim.conf to set the theme to "waldorf", don't touch anything else)

$ sudo service slim start

And it works.

Last edited by auxym (2014-03-04 20:16:40)

damo · 2014-03-04 20:40:58

Good news Sounds like a broken slim config somewhere? Don't know if it's related, but I 've just (twice) done a dist-upgrade to jessie on a new install, after commenting out the crunchbang repos. Each time the slim login screen was "broken", with no text appearing, so I had to type in blind.

The slim.conf was unchanged. It was only the waldorf theme that didn't work - the others and my own were fine. Go figure

auxym · 2014-03-04 21:27:08

damo wrote:

Good news Sounds like a broken slim config somewhere? Don't know if it's related, but I 've just (twice) done a dist-upgrade to jessie on a new install, after commenting out the crunchbang repos. Each time the slim login screen was "broken", with no text appearing, so I had to type in blind.
The slim.conf was unchanged. It was only the waldorf theme that didn't work - the others and my own were fine. Go figure

Yeah, go figure. After my slim reinstall I set the theme to waldorf and it doesn't seem to be broken. I had a look at the new slim.conf and could not see what had changed. Shame I didn't back up the old file, could have diffed them.

And to anyone trying to fix this, you don't need to type blind, hit ctrl-alt-f1 on the blank screen to switch to tty and log in there.

Last edited by auxym (2014-03-04 21:27:36)

damo · 2014-03-04 21:32:33

I didn't have a blank screen - the graphics were all there, login box etc, just no text was showing

ew · 2014-03-05 11:43:21

Jimbo_G wrote:

I agree that it's not very clear how to upgrade and what to watch out for if you do upgrade. From my point of view this is actually a good thing as it means I can't be tempted to break my computer and have to keep asking for help on here

Yes, and that's fine. But this issue with the gnome-desktop being dragged in, is a issue you don`t want. Anyone that's remotely as OCD as me, will have to reinstall #!, because that's the only way to ensure that every single unneeded package is removed. Getting the openbox-session to work again, isn't a real solution. Regardless how well you clean up, you will always wonder if you drag on a lot of extra packages that you don`t need

CrunchBang Linux

SEARCH

#26 2014-03-04 19:48:40

Re: X(openbox?) won't open automatically

#27 2014-03-04 20:40:58

Re: X(openbox?) won't open automatically

#28 2014-03-04 21:27:08

Re: X(openbox?) won't open automatically

#29 2014-03-04 21:32:33

Re: X(openbox?) won't open automatically

#30 2014-03-05 11:43:21

Re: X(openbox?) won't open automatically

Board footer