You are not logged in.

#1 2008-06-19 12:04:42

Stalafin
Member
From: Berlin, Germany
Registered: 2007-10-26
Posts: 617

[SOLVED] Weird GNOME/ SLiM/ OpenBox behaviour

[SOLVED] If you want to know what I did, just scroll down to the edits..



I decided to give GNOME another try, and installed it from the repositories.

That one went smoothly, but right now I am experiencing some weird behaviour when starting GNOME, as well as in OpenBox.


Ignore the part that is commented out.... Just search for 'Next thing:' and you will jump straight to the other problem.


/*************************************** << commented out
First of all, I am using SLiM to start both GNOME and OpenBox. See my .xinitrc and slim.conf files for that:


.xinitrc

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#

#xscreensaver -no-splash & 

# the following variable defines the session which is started if the user
# doesn't explicitely select a session
DEFAULT_SESSION=openbox-session

[ -f /etc/X11/xinit/xinitrc ] && sh /etc/X11/xinit/xinitrc

case $1 in
    openbox)
        xscreensaver -no-splash &
        exec openbox-session
        ;;
    gnome)
        exec gnome-session
        ;;
    openbox-gnome)
        exec openbox-gnome-session
        ;;
    *)
        exec ${DEFAULT_SESSION}
        ;;
esac
# exec xterm
# exec wmaker
# exec gnome-session
# exec openbox-gnome-session
#exec openbox-session
# exec startxfce4
# exec icewm
# exec blackbox
# exec fluxbox

## turn off system beep
xset b off

slim.conf

# Start in daemon mode. Valid values: yes | no
# Note that this can overridden by the command line
# option "-d"
# daemon    yes

# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions           openbox, gnome, openbox-gnome 

# Executed when pressing F11 (requires imagemagick)
screenshot_cmd      import -window root /slim.png

# welcome message. Available variables: %host, %domain
welcome_msg         Welcome to %host

# shutdown / reboot messages
shutdown_msg       The system is halting...
reboot_msg         The system is rebooting...

# default user, leave blank or remove this line
# for avoid pre-loading the username.
#default_user        simone

# current theme, use comma separated list to specify a set to 
# randomly choose from
current_theme       archlinux-simplyblack

# Lock file
lockfile            /var/lock/slim.lock

# Log file
logfile             /var/log/slim.log

Basically this was taken from the wiki.



Now assume I start a gnome-session or an openbox-gnome-session. Initially my screen looks like the following:
omg277.png.xs.jpg


A GNOME-session then starts (with that splashscreen) when closing the left terminal. Can you explain me what that is all about? It's kinda weird.... big_smile

********************************************<< still commented out****** but after that one the comment is gone...>>*********************************/

Next thing:
When installing GNOME (I experienced that before), GNOME has the bad habit of interfering with my OpenBox, even if I don't actually start GNOME. First, GNOME decides to set the wallpaper (so my Nitrogen settings are overwritten); then for some reason the GTK-Theme, as well as my icon-theme (which I am defining via .gtkrc and .gtkrc.mine) are overwritten; I can fix that by setting GTK-theme, icons, etc. in GNOME (so eventually I will have the same settings in OpenBox).
And now what's REALLY annoying: GNOME uses its default GNOME-screensaver, so that my Xscreensaver (which I am starting in my .xinitrc) is gone. Why is that so? I am not starting anything GNOME, neither in my autostart.sh, nor in my .xinitrc.


Did anyone else experience such problems? How can I get rid of it?







EDIT: So for my second problem: I found a topic where one guy actually wanted to start the gnome-settings-daemon for his openbox session. For me it's the other way round. Here's the link: http://bbs.archlinux.org/viewtopic.php?pid=379012

$ ps ux | grep "gnome"
USER     5186  0.4  2.8  58552 28884 ?        Sl   15:02   0:00 gnome-settings-daemon
USER     5215  0.0  0.1  14640  2052 ?        Ss   15:02   0:00 gnome-screensaver

Thoseu evil-doers shalt not be there!


EDIT2: At least those weird things that are being started are because of /etc/X11/xinit/xinitrc (see the my .xinitrc for that). I guess I will just remove it....


EDIT3: Yeah, that actually fixed it... So, that leaves us with that !@#*%! gnome-settings-daemon, and the gnome-screensaver. Why are they being started??

Here goes my autostart.sh:

# Run system-wide support
. $GLOBALAUTOSTART

# Programs launched at startup


# Programs executed after startup
#(sleep 2 && pypanel) &

(sleep 1 && tpb) &
(sleep 2 && nitrogen --restore) &
(sleep 3 && conky) &
(sleep 4 && trayer --align right --widthtype request --height 26 --transparent true --alpha 240) &
(sleep 5 && tint) &

As you can clearly see, there is no gnome specified anywhere.


EDIT4: Here comes a little pstree! big_smile

$ pstree
init─┬─acpid
     ├─5*[agetty]
     ├─crond
     ├─2*[dbus-daemon]
     ├─dbus-launch
     ├─famd
     ├─gconfd-2
     ├─gnome-screensav
     ├─gvfsd
     ├─hald───hald-runner─┬─hald-addon-acpi
     │                    ├─hald-addon-cpuf
     │                    └─hald-addon-inpu
     ├─ipw3945d
     ├─login───bash
     ├─portmap
     ├─slim─┬─X
     │      └─openbox─┬─firefox3───run-mozilla.sh───firefox-bin───7*[{firefox-bin}]
     │                ├─gnome-settings-───{gnome-settings-}
     │                ├─openbox-session───tpb───{tpb}
     │                ├─openbox-session───conky
     │                ├─openbox-session───trayer
     │                ├─openbox-session───tint
     │                ├─pcmanfm
     │                ├─urxvt───bash───pstree
     │                ├─xchat-gnome
     │                └─xscreensaver
     ├─syslog-ng
     └─udevd

EDIT5: I fixed it. The problem was the .$GLOBALAUTOSTART variable set in .config/openbox/autostart.sh, that made a call to /etc/xdg/config/openbox/autostart.sh, in which there where defined procedures to start gnome-specific stuff (as well as kde and xfce specific stuff).
I commented the lines in /etc/xdg/config/openbox/autostart.sh, and that solved my problems. big_smile

Last edited by Stalafin (2008-06-19 14:16:51)

Offline

#2 2008-06-19 14:21:02

gnud
Member
Registered: 2005-11-27
Posts: 182

Re: [SOLVED] Weird GNOME/ SLiM/ OpenBox behaviour

It's generally better to use obconf and turn off the gnome/kde-support (in your local config files), than to edit your /etc/xdg/*. Now you will have to keep the system-wide file in sync manually, on updates. But I'm glad it worked out smile

Offline

#3 2008-06-19 14:31:29

Stalafin
Member
From: Berlin, Germany
Registered: 2007-10-26
Posts: 617

Re: [SOLVED] Weird GNOME/ SLiM/ OpenBox behaviour

Yeah, I guess you are right about that. But how would I turn gnome-support off (apart from deleting .&GLOBALAUTOSTARTH)?

Offline

#4 2008-06-19 14:37:53

gnud
Member
Registered: 2005-11-27
Posts: 182

Re: [SOLVED] Weird GNOME/ SLiM/ OpenBox behaviour

If you install the program obconf (I think it's in community), there is an option for it if I remember correctly. It's been a year since I used openbox.

Offline

#5 2008-06-19 14:57:06

Stalafin
Member
From: Berlin, Germany
Registered: 2007-10-26
Posts: 617

Re: [SOLVED] Weird GNOME/ SLiM/ OpenBox behaviour

There doesn't seem to be... Else I am struck with blindness.

Offline

#6 2008-06-19 15:17:59

gnud
Member
Registered: 2005-11-27
Posts: 182

Re: [SOLVED] Weird GNOME/ SLiM/ OpenBox behaviour

Hmm. I used openbox ages ago, before this new fancy-pants "openbox-session" tongue

You could always uninstall gnome-session. If not, it looks like you will have to fiddle with the global settings, or not run $GLOBALAUTOSTART. See http://icculus.org/openbox/index.php/Help:Autostart

Offline

#7 2009-02-21 10:33:06

tandycorp
Member
Registered: 2007-07-01
Posts: 65

Re: [SOLVED] Weird GNOME/ SLiM/ OpenBox behaviour

Old post I know but...
I have the exact same problem with gnome overriding my openbox configuration, like my nitrogen wallpaper that gets overrided by the ugly gnome wallpaper, a big green leaf.. Finally did you know how to safely resolve this without deleting the $GLOBALAUTOSTART variable in autostart.sh?

Offline

Board footer

Powered by FluxBB