LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Desktop (https://www.linuxquestions.org/questions/linux-desktop-74/)
-   -   Logging in with Openbox issues (https://www.linuxquestions.org/questions/linux-desktop-74/logging-in-with-openbox-issues-4175475302/)

\/4A 08-30-2013 07:37 AM

Logging in with Openbox issues
 
Hello,

I' ve just installed Fedore 19 LXDE and while I can log into my user a/c using LXDE with no problem, selecting Openbox as the desktop does bring issues: it just gives a blank screen.

Would really appreciate some guidance on how I can go about slving this pls.

descendant_command 08-31-2013 01:42 AM

That's openbox :)
What were you expecting?

\/4A 08-31-2013 07:37 AM

Quote:

Originally Posted by descendant_command (Post 5019226)
That's openbox :)
What were you expecting?

:confused:HUH?? Openbox is just a blank black screen with no icons or panels? Well then is it used for troubleshooting or something?

RockDoctor 08-31-2013 09:07 AM

No, openbox is just a window manager - it doesn't put icons on the screen, it doesn't come with panels. That's why pcmanfm and lapanel are included in LXDE

slacker_ 09-01-2013 04:45 PM

Quote:

Originally Posted by RockDoctor (Post 5019358)
No, openbox is just a window manager - it doesn't put icons on the screen, it doesn't come with panels. That's why pcmanfm and lapanel are included in LXDE

That's actually the brilliant part of openbox. You can set it up to start your panel, and your compositing, and everything in the "autostart" file. I'm currently using it on slackware 14 and it's going well, except...

My issue is that nothing in my autostart is actually being called. I set it up according to the openbox wiki:

Code:

##Programs that will run after OB starts
#set wallpaper
hsetroot ~/pictures/my_wallpaper.jpg &

#everyone needs compositing!
xcompmgr -c -t-5 -l-5 -r-5 -o.55 -f &

#latin characters aren't enough!
scim -d &

#a simple panel
tint2 &

Not sure why it isn't working.

RockDoctor 09-02-2013 06:49 AM

I'm not sure either, so I booted up Fedora 19 :
1. modified my .xinitrc to start openbox (and a terminal, just-in-case) instead of LXDE:
Code:

~$ cat .xinitrc
#!/bin/sh
#exec startlxde
lxterminal &
exec openbox-session

2. created a simple .config/openbox/autostart file and made it executable:
Code:

~$ cat .config/openbox/autostart
# test of autostart
lxpanel -p LXDE &

The above setup works for me (F19 booting to the CLI; then running startx).
HTH

slacker_ 09-02-2013 09:17 AM

Quote:

Originally Posted by RockDoctor (Post 5020220)
I'm not sure either, so I booted up Fedora 19 :
1. modified my .xinitrc to start openbox (and a terminal, just-in-case) instead of LXDE:

2. created a simple .config/openbox/autostart file and made it executable:

The above setup works for me (F19 booting to the CLI; then running startx).
HTH

I boot to cli and run startx as well. Haven't gotten my initial configurations done to the point where I feel comfortable enough booting right to a display manager.

That's a lot simpler than my .xinitrc: I have some settings regarding keymaps and resources at the top, then it had some code in the middle to create a default user dir and populate it if one didn't exist. I commented that out, and this block:
Code:

if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
  exec ck-launch-session dbus-launch --exit-with-session openbox
else

and it works perfectly well. Below that block is the exec openbox-session line.

Now I don't know which chunk messed up the autostart loading, any ideas?

RockDoctor 09-02-2013 11:22 AM

All I have is a guess. In your original, does changing
Code:

if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
  exec ck-launch-session dbus-launch --exit-with-session openbox

to
Code:

if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
  exec ck-launch-session dbus-launch --exit-with-session openbox-session

give you a working setup?

slacker_ 09-03-2013 07:39 PM

Quote:

Originally Posted by RockDoctor (Post 5020362)
All I have is a guess. In your original, does changing
Code:

if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
  exec ck-launch-session dbus-launch --exit-with-session openbox

to
Code:

if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
  exec ck-launch-session dbus-launch --exit-with-session openbox-session

give you a working setup?

I'll have to try that when my X is working again. I was doing some kernel configuration following the slackbook tutorial. In it it says to merge your root and user Xauthorities so that root can launch X apps when you're under su. Well, now my startx is failing and I don't know how to recover that. I have a thread regarding that issue though.


All times are GMT -5. The time now is 06:11 PM.