HAL, Xorg, and Fluxbox on Slackware 13.0

Cotobear · 08-30-2009, 01:46 PM

Hey everyone,

So has anyone tried loading up Fluxbox on there shiny new 13.0 installation? My first thought was:

Will HAL and Xorg still work together to configure X without an xorg.conf file?

It seems that the short answer (in my case anyway) is no. In fact, it seems Fluxbox fails completely if no xorg.conf file is detected. I have yet to experiment with creating an xorg.conf file that properly works with both Fluxbox and KDE.

Has anyone done much with this yet?

Coto

H_TeXMeX_H · 08-30-2009, 01:52 PM

Well, fluxbox works fine for me with no xorg.conf. But, after I installed the nvidia drivers I needed to make an xorg.conf ... and fluxbox still works fine. Does it post any errors ?

Cotobear · 08-30-2009, 02:05 PM

Got it to work.

Since I was just checking to see it did work, I just ran "startfluxbox" instead of changing the windows manager through xwmconfig and then running startx.

If I remember correctly though, this was never a problem. I guess with this new system, it's what you have to do.

forum1793 · 08-30-2009, 02:28 PM

If you don't change the window manager, even if typing startfluxbox aren't you still using kdm?

Cotobear · 08-30-2009, 03:14 PM

Quote:

Originally Posted by forum1793

If you don't change the window manager, even if typing startfluxbox aren't you still using kdm?

I prefer to start from the console

, so no kdm. Interesting point though. I wonder how kdm starts a windows manager and if you might get a problem from doing it this way.

jkirchner · 08-30-2009, 04:02 PM

I used xwmconfig to change to fluxbox and she fired right up with startx. I like starting from console too.

linuxpokernut · 08-30-2009, 05:25 PM

This is interesting, I was thinking about running fluxbox and KDE in 13.1 when I load it up. I play a lot of games and in Ubuntu the compbiz/KDE took up most of my 2 gigs of ram and ran games slower (than 3.5 in slackware 12.2)

I always start from console so that shouldn't be an issue.

alkos333 · 08-31-2009, 02:10 PM

One of the issues that I ran into was that my keyboard mapping got screwed up. Subsequently, all of the combos that I set up in ~/.fluxbox/keys stopped working. I think the new X is either identifying the keyboard wrong, or I had it set up the wrong way previously.

Melkor · 08-31-2009, 02:17 PM

Quote:

Originally Posted by jkirchner

I used xwmconfig to change to fluxbox and she fired right up with startx. I like starting from console too.

I also used xwmconfig to switch the default wm to Fluxbox and it worked fine for me when I typed "startx" from the console.

dracolich · 09-01-2009, 09:43 PM

Quote:

Originally Posted by alkos333

One of the issues that I ran into was that my keyboard mapping got screwed up. Subsequently, all of the combos that I set up in ~/.fluxbox/keys stopped working. I think the new X is either identifying the keyboard wrong, or I had it set up the wrong way previously.

I just finished upgrading from 12.2 to 13 on my Pavilion ze4315 and this is the biggest issue I'm having. I still have to use my xorg.conf for Fluxbox to work. I'll browse the xorg log, xorg.conf and xev later. I just now found that my End key does what the Window key (keycode 115) is supposed to do. And even though my omnibook driver is loaded only one of my quick access keys responds.

Also, if I have to quit X with Ctrl+Alt+BkSpc, Fluxbox (or KDE) won't restart properly until I reboot. Probably a radeon driver issue between my laptop's ati Mobility U1 and the new Xorg.

dracolich · 09-02-2009, 08:11 PM

I solved the keyboard issue by adding

Code:

Section "ServerFlags"
Option "AllowEmptyInput""false"
Option "AutoAddDevices" "false"
EndSection

to xorg.conf

And solved my desktop issue. If the 3ddesktop daemon is running before startx it paints the background on top of my desktop.