SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 2014-02-28 21:14:58

schwim
#! Die Hard
From: Interweb's #1 Devotee
Registered: 2012-10-11
Posts: 1,031
Website

Debian Sid #! clone: need some help

Hey there folks,

Since not much is going on the in the world of #!, I thought as a learning exercise, I would try to duplicate my install on Debian Sid.  I know there's some stellar upgrade topics in the forum here, but for the sake of learning I thought it would be pretty nifty to start out with a bare netinstall and go from there.

I didn't get super far.  My first issue is that I can't get openbox to use my autostart.sh.

LightDM for manager.

chwim@vb-DebianBare:~$ update-alternatives --config x-session-manager
There is only one alternative in link group x-session-manager (providing /usr/bin/x-session-manager): /usr/bin/openbox-session
Nothing to configure.
schwim@vb-DebianBare:~$

I placed autostart.sh in ~/.config/openbox and  chmodded the file to make sure it was executable.

It's a very simple file, thus far.

## Wallpaper and tint2
DISPLAY=:0.0 /home/schwim/.scripts/wallpaper_changer && \
sleep 2s && \
tint2 \
) &

## Start Thunar Daemon
thunar --daemon &

# Autostart the Dropbox deamon
(sleep 15s && ~/.scripts/dropbox-dist/dropboxd) &

All of these commands work in the terminal.

Startup seems to be openbox without the session, although it shows my only alternative is session.  I ran

sudo ./lightdm-set-defaults --session openbox-session

No changes on restart.

In my very limited knowledge, I'm at a stopping point and I've run out of Googling ideas.

Does anyone have an idea on what I'm neglecting to do?  Any thoughts or suggestions would be welcome.

Thanks for your time!

Offline

Be excellent to each other!

#2 2014-02-28 21:25:14

joek
#! Junkie
Registered: 2011-09-06
Posts: 497

Re: Debian Sid #! clone: need some help

Have you made sure it's in the correct place? (~/.config/openbox/autostart, I think). Note that IIRC, older versions of OB require the file to be called `autostart.sh` while newer ones want it to be called `autostart`. Check which the version of OB you have installed wants. (It should have it in the man page...)

Does it need execute permissions?

Last edited by joek (2014-02-28 21:27:25)

Offline

#3 2014-02-28 22:20:19

schwim
#! Die Hard
From: Interweb's #1 Devotee
Registered: 2012-10-11
Posts: 1,031
Website

Re: Debian Sid #! clone: need some help

Hi there joek,

I should have mentioned, but I have two files in ~/.config/openbox/ named autostart and autostart.sh to cover all the bases.  Also, I ran chmod u+x on both files.  The problem is occurring in spite of this.

Offline

#4 2014-02-28 22:53:20

schwim
#! Die Hard
From: Interweb's #1 Devotee
Registered: 2012-10-11
Posts: 1,031
Website

Re: Debian Sid #! clone: need some help

Hmm.  The plot thickens.

I thought I'd edit lightdm's config to ensure that it booted into openbox-session, so I opened the file and uncommented the relevant lines:

#
# General configuration
#
# start-default-seat = True to always start one seat if none are defined in the configuration
# greeter-user = User to run greeter as
# minimum-display-number = Minimum display number to use for X servers
# minimum-vt = First VT to run displays on
# lock-memory = True to prevent memory from being paged to disk
# user-authority-in-system-dir = True if session authority should be in the system location
# guest-account-script = Script to be run to setup guest account
# log-directory = Directory to log information to
# run-directory = Directory to put running state in
# cache-directory = Directory to cache to
# sessions-directory = Directory to find sessions
# remote-sessions-directory = Directory to find remote sessions
# greeters-directory = Directory to find greeters
#

[LightDM]
#start-default-seat=true
#greeter-user=lightdm
#minimum-display-number=0
#minimum-vt=7
#lock-memory=true
#user-authority-in-system-dir=false
#guest-account-script=guest-account
#log-directory=/var/log/lightdm
#run-directory=/var/run/lightdm
#cache-directory=/var/cache/lightdm
#sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions
#remote-sessions-directory=/usr/share/lightdm/remote-sessions
#greeters-directory=/usr/share/lightdm/greeters:/usr/share/xgreeters

#
# Seat defaults
#
# type = Seat type (xlocal, xremote)
# xdg-seat = Seat name to set pam_systemd XDG_SEAT variable and name to pass to X server
# xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
# xserver-layout = Layout to pass to X server
# xserver-config = Config file to pass to X server
# xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
# xserver-share = True if the X server is shared for both greeter and session
# xserver-hostname = Hostname of X server (only for type=xremote)
# xserver-display-number = Display number of X server (only for type=xremote)
# xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
# xdmcp-port = XDMCP UDP/IP port to communicate on
# xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
# unity-compositor-command = Unity compositor command to run (can also contain arguments e.g. unity-system-compositor -special-option)
# unity-compositor-timeout = Number of seconds to wait for compositor to start
# greeter-session = Session to load for greeter
# greeter-hide-users = True to hide the user list
# greeter-allow-guest = True if the greeter should show a guest login option
# greeter-show-manual-login = True if the greeter should offer a manual login option
# greeter-show-remote-login = True if the greeter should offer a remote login option
# user-session = Session to load for users
# allow-guest = True if guest login is allowed
# guest-session = Session to load for guests (overrides user-session)
# session-wrapper = Wrapper script to run session with
# greeter-wrapper = Wrapper script to run greeter with
# guest-wrapper = Wrapper script to run guest sessions with
# display-setup-script = Script to run when starting a greeter session (runs as root)
# greeter-setup-script = Script to run when starting a greeter (runs as root)
# session-setup-script = Script to run when starting a user session (runs as root)
# session-cleanup-script = Script to run when quitting a user session (runs as root)
# autologin-guest = True to log in as guest by default
autologin-user = schwim
autologin-user-timeout = 0
autologin-session = openbox-session
# autologin-in-background = True if autologin session should not be immediately activated
# exit-on-failure = True if the daemon should exit if this seat fails
#

[SeatDefaults]
#type=xlocal
#xdg-seat=seat0
#xserver-command=X
#xserver-layout=
#xserver-config=
#xserver-allow-tcp=false
#xserver-share=true
#xserver-hostname=
#xserver-display-number=
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
#unity-compositor-command=unity-system-compositor
#unity-compositor-timeout=60
#greeter-session=example-gtk-gnome
#greeter-hide-users=false
#greeter-allow-guest=true
#greeter-show-manual-login=false
#greeter-show-remote-login=true
#user-session=default
#allow-guest=true
#guest-session=UNIMPLEMENTED
#session-wrapper=lightdm-session
#greeter-wrapper=
#guest-wrapper=
#display-setup-script=
#greeter-setup-script=
#session-setup-script=
#session-cleanup-script=
#autologin-guest=false
#autologin-user=
#autologin-user-timeout=0
#autologin-in-background=false
#autologin-session=UNIMPLEMENTED
#exit-on-failure=false

#
# Seat configuration
#
# Each seat must start with "Seat:".
# Uses settings from [SeatDefaults], any of these can be overriden by setting them in this section.
#
#[Seat:0]

#
# XDMCP Server configuration
#
# enabled = True if XDMCP connections should be allowed
# port = UDP/IP port to listen for connections on
# key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
#
# The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn.  Alternatively
# it can be a word and the first 7 characters are used as the key.
#
user-session=openbox-session

[XDMCPServer]
#enabled=false
#port=177
#key=

#
# VNC Server configuration
#
# enabled = True if VNC connections should be allowed
# command = Command to run Xvnc server with
# port = TCP/IP port to listen for connections on
# width = Width of display to use
# height = Height of display to use
# depth = Color depth of display to use
#

[VNCServer]
#enabled=false
#command=Xvnc
#port=5900
#width=1024
#height=768
#depth=8

Rebooted and lightdm opened with a login box.

So not only can't I get openbox to respect the config file, lightdm doesn't seem to either.

What in the hell am I doing wrong?

Offline

#5 2014-03-01 20:06:24

joek
#! Junkie
Registered: 2011-09-06
Posts: 497

Re: Debian Sid #! clone: need some help

I don't use (and have never used) LightDM, so I'm afraid I probably can't be much help, but the ArchWiki suggests that you have to be part of the autologin group to use the autologin.

You can check which groups you are a member of with the `groups` command. If you are not part of the autologin group, you can:

groupadd autologin
gpasswd -a schwim autologin

You may need root permissions for these commands.

Offline

#6 2014-03-01 21:04:06

schwim
#! Die Hard
From: Interweb's #1 Devotee
Registered: 2012-10-11
Posts: 1,031
Website

Re: Debian Sid #! clone: need some help

Hi there Joek and thanks for your continued help.  I really appreciate it.

I ended up scrapping the install and trying again with slim(mixed capitals and lowercase where you'd like).  I found lightdm to be awfully frustrating. I'm having much better luck with slim and I found that the problem with openbox was a corrupt autostart.sh(you can see my mistakes in the bracketing in the initial post).  Once I fixed that, openbox began using it.

I'm a bit further on in my journey and am learning a bunch, but am still finding some things to be less than intuitive.  The absurd number of different methods you need to deal with for getting theming, icons, fonts, etc to work in all aspects of the DE come to mind here.  I've still not completely worked out the kinks and have begun to suspect that I likely won't in the end.

If I can end up with a usable system that closely resembles my #! install, I'll be a happy camper.

Offline

#7 2014-03-01 22:27:46

joek
#! Junkie
Registered: 2011-09-06
Posts: 497

Re: Debian Sid #! clone: need some help

Ah, I should have noticed that floating bracket!

Well, I'm glad you've got that figured out, and that you've managed to get a Display Manager working -- good luck with the rest of the configuration! You'll learn something, at least!

Offline

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: acrobat

Debian Logo