Awesome seems to kill apps from xinitrc

g_SG · 2009-05-17 06:45:05

Und hello everyone.

I just moved to AwesomeWM from Xmonad, and I want some apps to be autostarted when my X session is ready. Obviously, I used to use .xinitrc for that (script as follows). However, Awesome seems to be killing some of those apps.
The funny thing is that not all of the apps specified are missing, though. My default terminal is urxvtc, and it runs normally from inside Awesome, which means urxvtd is started normally. Other apps, such as nitrogen, wmname and the urxvtcs, however, don't get started.

.xinitrc wrote:

#!/bin/bash
## test for an existing bus daemon, just to be safe
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
## if not found, launch a new one
eval `dbus-launch --sh-syntax --exit-with-session`
fi
# X apps to set up the desktop
xset r rate 250 50 & # ok
#xsetroot -cursor_name left_ptr &
xmodmap $HOME/.Xmodmap & # ok
#nitrogen --restore & # broken
urxvtd -o -q -f & # ok
wmname LG3D & # broken
urxvtc -e screen -RR & # broken
urxvtc -e ncmpcpp & # broken
urxvtc -e htop & # broken
#conky -c ~/.conkyrc | while true; read line; do xsetroot -name "$line"; done &
#while true; do dwm; done
sleep 1
exec awesome

As a workaround, I tried to follow the instructions from the Awesome wiki, but they do no good either.

Any thoughts?

Last edited by g_SG (2009-05-17 07:19:30)

ak-89 · 2009-05-17 07:41:28

I don't know about nitrogen and wmname, but try to move that "sleep 1" right before urxvtcs or add there another one. I tried and that worked, I think urxvtd has not started yet when you try to start those consoles.

Try to put "nitrogen --restore" in to your theme-file instead of .xinitrc, you should see there "wallpaper_cmd".

g_SG · 2009-05-17 08:23:41

I added another sleep 1 before the urxvtcs, and it didn't work either. I guess Awesome is actually killing the apps. Sometimes, when I'm lucky, the windows do show up right before awesome starts and then they disappear.
Another weird fact is that that very .xinitrc file used to work fine just yesterday, back when I used Xmonad.
About the wallpaper_cmd on the theme file, that seems to be another problem I've been having with Awesome. It doesn't load. And, when I use the default awsetbg, it shows a nonsensical error message (something about not being able to use 'display'. It shows a command I should run to reproduce the error, but, when I do, nothing wrong happens), but I got over that already.

ak-89 · 2009-05-17 08:31:29

Is there anything strange in VT1? Apps started in xinitrc outputs errors etc to VT1 or whatever VT you used to start X. Start X with "startx &> $HOME/.xinit.log" or "xinit &> $HOME/.xinit.log" and then you have outputs of those apps in .xinit.log-file. Then you can paste it here or read it in X.

g_SG · 2009-05-17 08:38:51

Apparently, there's nothing unusual in the logs. Just some annoying problems with my video driver.

log wrote:

xauth: creating new authority file /home/guilherme/.serverauth.25130

X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.27-ARCH i686
Current Operating System: Linux leptok 2.6.29-ARCH #1 SMP PREEMPT Sat May 9 12:47:43 UTC 2009 i686
Build Date: 17 December 2008 08:20:05PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun May 17 05:36:57 2009
(==) Using config file: "/etc/X11/xorg.conf"
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:0:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:1:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:5) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:1) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:3) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:4:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:5:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:6:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:7:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:15:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:31:0) found
(EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/sis315_dri.so failed (/usr/lib/xorg/modules/dri/sis315_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Duplicate shape name "RTRN"
> Using last definition
> Warning: Duplicate shape name "RTSH"
> Using last definition
> Warning: Don't know how to merge sections yet
> Warning: Don't know how to merge sections yet
> Warning: Don't know how to merge sections yet
> Warning: Don't know how to merge sections yet
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
Xlib: extension "Generic Event Extension" missing on display ":0.0".
sh: sensors: command not found
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
sh: acroread: command not found
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".

whordijk · 2009-05-17 12:37:37

You can also include an autostart sequence in your rc.lua to avoid conflicts with your .xinitrc and vice versa, here's mine:

-- {{ Autostart
awful.util.spawn("numlockx")
awful.util.spawn("mpdscribble")
awful.util.spawn("thunar --daemon")
-- }}

Nezmer · 2009-05-17 14:39:11

I can see from the Xlib warnings that you run an outdated X server . If your system is not up-to-date , please post the versions of the packages that might be related to the problem (e.g X packages , awesome , xcb packages ...etc) .

g_SG · 2009-05-17 17:56:10

Yup. I forgot to mention that. My xorg-xserver package is outdated (and so are its dependencies xorg-video-vesa, xorg-input-evdev-xorg-input-mouse,xorg-input-keyboard and xorg-input-synaptics). That's because the video driver I use (some nasty workaround for the SiS 671/771 chipset originally made for Ubuntu) is not compatible with the new Xserver, and there's no updated version. My Awesome version is the one from extra (3.3pre20090421-1). But I don't see how this might cause Awesome to selectively kill clients that are autostarted.

The awful.util.spawn thing doesn't work either. There's no sign of the apps I spawned.

Last edited by g_SG (2009-05-17 18:01:17)

Nezmer · 2009-05-17 20:52:22

I don't know If that's related to your problem . the current stable awesome release has problems with the updated xcb packages . That's why we have a git snapshot in extra (to play nice with the current xcb packages). I think your xcb packages are outdated too which could be a possible source of your problems .

You should double-check your rc.lua too . One typo could render the whole file useless .

g_SG · 2009-05-17 20:58:45

No, my xcb packages are all up-to-date. I'll try the git version anyway, and I'll post the result in a minute.
About the rc.lua, `awesome -k` finds no errors, and the theme and functions are working normally, so I guess there's nothing wrong. Again, I'll check it and post the result here in a few. Thanks. It's really annoying that each version has a configuration format that's incompatible with the others.

Edit: Well, I found no errors in rc.lua. I'll post it here anyway. It's a modified, not-completely-working, gigamo's config, because I don't know Lua. Anyway, I don't know how a malfunctioning rc.lua could cause this kind of problem. Here it is:

rc.lua: http://pastebin.com/f422ae049
functions.lua: http://pastebin.com/f7a0258c9

Last edited by g_SG (2009-05-17 22:18:42)

Arch Linux

#1 2009-05-17 06:45:05

Awesome seems to kill apps from xinitrc

#2 2009-05-17 07:41:28

Re: Awesome seems to kill apps from xinitrc

#3 2009-05-17 08:23:41

Re: Awesome seems to kill apps from xinitrc

#4 2009-05-17 08:31:29

Re: Awesome seems to kill apps from xinitrc

#5 2009-05-17 08:38:51

Re: Awesome seems to kill apps from xinitrc

#6 2009-05-17 12:37:37

Re: Awesome seems to kill apps from xinitrc

#7 2009-05-17 14:39:11

Re: Awesome seems to kill apps from xinitrc

#8 2009-05-17 17:56:10

Re: Awesome seems to kill apps from xinitrc

#9 2009-05-17 20:52:22

Re: Awesome seems to kill apps from xinitrc

#10 2009-05-17 20:58:45

Re: Awesome seems to kill apps from xinitrc

Board footer