You are not logged in.
Hi everybody,
I installed shortly Arch on a new computer and probably after touching the openbox config files, I have the following problem:
when I launched Openbox thorugh Slim then I can not access the menu. Right click do just nothing
If I open a new console with Ctrl-Alt-F2 and launch startx then everything is going fine.
I just don't know where to look ... I looked into the openbox log file and found out the following:
XIO: fatal IO error 11 (Ressource temporairement non disponible) on X server ":0.0"
which I really don't understand since I see the openbox desktop as usual just no access to menu
It would be nice if somebody could help in that issue.
Regards
Fabien
Last edited by goulabf9 (2013-12-14 08:01:51)
Offline
which I really don't understand since I see the openbox desktop as usual just no access to menu
How can you determine if you really see the Openbox desktop if you cannot access at least the menu?
Offline
you have to check $HOME/.xinitrc and $HOME/.config/openbox/rc.xml and $HOME/.config/openbox/autostart and $HOME/.config/openbox/menu.xml for errors.
if it was working before, it must be one of the files you "touched". you can always just delete it, openbox will use some default from somewhere else.
Offline
Most display managers run "openbox-session" when they start openbox instead of "openbox". Do you have openbox-session in your .xinitrc? If not, what happens if you use openbox-session with startx?
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
Good morning,
thanks for the many replies. Indeed, I don't see the openbox desktop, I just see the wallpaper.
I deleted the configuration files an witht the default openbox files, openbox is starting normally.
openbox-session is executed in the xinitrc.
i will investigate some more in the next days. It is hard to find the mistake since the second time I run startx, openbox is starting normally. I mean:
Boot
console tty1 (I deactivated slim)
startx
openbox doesn't start (no menu, autostart is not executed (no tint2)
console tty2
startx again
openbox starts normally
It seems for me that openbox doesn't find the display the first time but why ?
this is not something which is written in the config files.
Regards
Fabien
Offline
but now the situation has changed, no?
btw, it probably wasn't my best advice to "just delete" the files; moving them would have been better. and what applies to openbox configs does not apply to xinitrc.
anyhows, you might want to look at Xorg log files (Xorg.0.log for the current session) in /var/log.
or try journalctl.
Last edited by ondoho (2013-12-10 07:08:19)
Offline
I suspect the problem lies either in your .xinitrc file, or your openbox autostart file. Something that should be backgrounded, isn't, but is daemonizing when you kill off startx the first time, meaning it's already running when you startx the second time.
Can you post your .config/openbox/autostart file as well as your .xinitrc.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Hi,
thanks for the replies. Here is my .xinitrc:
#!/bin/bash
export DE=openbox
# Dbus fix
if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
eval "$(dbus-launch --sh-syntax --exit-with-session)"
fi
/usr/bin/xdg-user-dirs-update
exec openbox-sessionand my autostart
tint2 &
volumeicon &
hsetroot -fill /usr/share/wallpapers/mywallpaper.png &
conky &
compton -cCGb &I will have a look on the Xorg log
Regards
Fabien
Offline
Hi again,
no error in Xorg
only some little warnings regarding fonts:
fonts.dir' not found (or not valid)
The directory "/usr/share/fonts/Type1/" does not exist.
[ 52.978] (WW) Falling back to old probe method for vesa
[ 52.978] (WW) Falling back to old probe method for modesetting
[ 52.978] (WW) Falling back to old probe method for fbdevRegards
Fabien
Offline
Sorry for the multiposting
I also found out that autostart is completely executed:
tint2, trays, etc ... are started
so no more idea ... is there any possibility to get an openbox log ?
Regards
Offline
it's been a while since i used a display manager; i'm not sure if the .xinitrc is even relevant to slim, doesn't it do it differently somehow?
in any case, you can comment out basically everything except the last "exec openbox-session" - just for troubleshooting!
and you can comment out the whole autostart, and see if that gives you back your ob menu.
(and then uncomment one-by-one til you find the culprit)
Offline
Just a guess (I also don't use a DM): Maybe slim is starting something from XDG autostart files that is taking over your desktop. Do you have other applications that can take over the root window if they are started (I am thinking like nautilus, pcmanfm, mostly file managers I have found have this sort of functionality (but then again it seems like right click would at least give you some type of context menu))? Also, are you absolutely sure you have slim launching openbox and not some other desktop session? Do you have multiple window managers and or desktop environments installed?
Offline
Though it's probably not the cause of the problem, I'd drop the dbus fix in your xinitrc, and just source /etc/X11/xinit/xinitrc.d/* as recommended on the wiki (https://wiki.archlinux.org/index.php/Openbox#D-Bus):
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fiYou might want to remove slim from the topic title, since we've established that it's not related to the problem.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Hi,
sorry I could not give status before, I was traveling.
The problem is solved !
I just don't know why. The only difference with before is that the menu is now without icons.
So it seems it had something to do with icons but what ?? No idea.
anyway thanks a lot for your hints
Regards
Fabien
Offline
Hi,
I confirm. No idea why but as soon as I activate icons in Openbox, or to be exact as soons as I generate a pipe menu with obmenu-generator then the first time I log in into Openboy, I have no menu at all. Without icons, no problem.
Regards,
Fabien
Offline