I installed windomaker and fluxbox with apt-get, but gdm does not show them!I add them in gdm's configuration file but the problem still exists! Any idea guys? Thanks!!!
__________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/
On Sat, 2003-11-29 at 21:31, nipson anomhmata wrote:
I installed windomaker and fluxbox with apt-get, but gdm does not show them!I add them in gdm's configuration file but the problem still exists! Any idea guys? Thanks!!!
what apt repository did you get those from? I'd like to know.. :)
On Sun, 2003-11-30 at 09:07, jason pratt wrote:
On Sat, 2003-11-29 at 21:31, nipson anomhmata wrote:
I installed windomaker and fluxbox with apt-get, but gdm does not show them!I add them in gdm's configuration file but the problem still exists! Any idea guys? Thanks!!!
what apt repository did you get those from? I'd like to know.. :)
Hi
Windowmaker is from Dag's repo. Here's my /etc/apt/sources.list [comments removed] which is the default when you install apt-get from freshrpms.net.
[kevin@www2 kevin]$ cat /etc/apt/sources.list # Fedora Core 1 rpm http://ayo.freshrpms.net fedora/linux/1/i386 core updates # ATrpms for Fedora Core 1 rpm http://apt.physik.fu-berlin.de fedora/1/en/i386 at-testing # FreshRPMS for Fedora Core 1 rpm http://ayo.freshrpms.net fedora/linux/1/i386 freshrpms # NewRPMS for Fedora Core 1 rpm http://newrpms.sunsite.dk/apt/ redhat/en/i386/fc1 newrpms # Dag Wieers' rpms for Fedora Core 1 rpm http://apt.sw.be redhat/fc1/en/i386 dag #JPackage for Fedora Core 1 rpm ftp://jpackage.hmdc.harvard.edu/JPackage 1.5/generic free rpm ftp://jpackage.hmdc.harvard.edu/JPackage 1.5/fedora-1 free # Planet CCRMA for Fedora Core 1 rpm http://www-ccrma.stanford.edu/planetccrma/apt fedora/1/i386 planetcore planetccrma
Kevin
On Sun, 2003-11-30 at 12:21, Kevin Brouelette wrote:
Hi
Windowmaker is from Dag's repo. Here's my /etc/apt/sources.list [comments removed] which is the default when you install apt-get from freshrpms.net.
Great thanks! ok now where his question was headed.. how do I add this to the optional desktop/windowmanagers in gdm? i'd like to add both of these if it's possible.
thanks.
On Sat, 2003-11-29 at 20:31, nipson anomhmata wrote:
I installed windomaker and fluxbox with apt-get, but gdm does not show them!I add them in gdm's configuration file but the problem still exists! Any idea guys? Thanks!!!
This worked for me (from http://www.fluxbox.org/docs/en/faq.php#fedora):
<quote> The fedora distribution uses a different setup again. Instead of the dm-specific locations, it requires session files to be in /etc/X11/dm/Sessions.
So, to get Fluxbox into its session menu, create the file: /etc/X11/dm/Sessions/fluxbox with contents:
[Desktop Entry] Encoding=UTF-8 Name=Fluxbox Type=Application Icon= Exec=fluxbox You may need to put the full path to fluxbox in the Exec line if it is in a non-standard location.
</quote>
Paul Morgan wrote:
This worked for me (from http://www.fluxbox.org/docs/en/faq.php#fedora):
<quote> The fedora distribution uses a different setup again. Instead of the dm-specific locations, it requires session files to be in /etc/X11/dm/Sessions.
So, to get Fluxbox into its session menu, create the file: /etc/X11/dm/Sessions/fluxbox with contents:
[Desktop Entry] Encoding=UTF-8 Name=Fluxbox Type=Application Icon= Exec=fluxbox You may need to put the full path to fluxbox in the Exec line if it is in a non-standard location.
</quote>
I tried that. (Actually, since the files were all named <manager>.desktop, I named it fluxbox.desktop.) No luck; I'd choose a fluxbox session, log in, and just get a blank blue screen with a mouse cursor (that did move around). I had to ctrl-alt-bs out of X, after which I would get the nVidia driver splash screen followed by the computer going into some sort of hibernation mode, taking some keypressing to get out of and back to the graphical login.
I noticed the *.desktop files had the execute bits set, and set them on fluxbox.desktop; no change. I noticed that /etc/X11/gdm/Sessions had a Fluxbox file in it, but noticed that, unlike the other files therein, it just exec'd /usr/bin/fluxbox rather than doing
exec /etc/X11/xdm/Xsession fluxbox
analogously to the GNOME and KDE files in the same directory, so I made that change. No difference.
Finally, I figured I should try the directions exactly as written, and changed the name of the added file from fluxbox.desktop to just plain fluxbox. Then the login no longer displayed fluxbox as a choice for sessions.
Any suggestions about what to do to let me use fluxbox would be greatly appreciated; for me personally, it's just an experiment, but for the person who's getting the 200 MHz Pentium Pro box I've had sitting around and put Fedora Core on, having access to a lower-overhead window manager is very much worthwhile.
James Jones
On Sat, 20 Dec 2003 14:48:43 -0600 James Jones jamesjones01@mchsi.com wrote:
Paul Morgan wrote:
This worked for me (from http://www.fluxbox.org/docs/en/faq.php#fedora):
<quote> The fedora distribution uses a different setup again. Instead of the dm-specific locations, it requires session files to be in /etc/X11/dm/Sessions.
So, to get Fluxbox into its session menu, create the file: /etc/X11/dm/Sessions/fluxbox with contents:
[Desktop Entry] Encoding=UTF-8 Name=Fluxbox Type=Application Icon= Exec=fluxbox You may need to put the full path to fluxbox in the Exec line if it is in a non-standard location.
</quote>
I tried that. (Actually, since the files were all named <manager>.desktop, I named it fluxbox.desktop.) No luck; I'd choose a fluxbox session, log in, and just get a blank blue screen with a mouse cursor (that did move around). I had to ctrl-alt-bs out of X, after which I would get the nVidia driver splash screen followed by the computer going into some sort of hibernation mode, taking some keypressing to get out of and back to the graphical login.
I noticed the *.desktop files had the execute bits set, and set them on fluxbox.desktop; no change. I noticed that /etc/X11/gdm/Sessions had a Fluxbox file in it, but noticed that, unlike the other files therein, it just exec'd /usr/bin/fluxbox rather than doing
exec /etc/X11/xdm/Xsession fluxbox
analogously to the GNOME and KDE files in the same directory, so I made that change. No difference.
Finally, I figured I should try the directions exactly as written, and changed the name of the added file from fluxbox.desktop to just plain fluxbox. Then the login no longer displayed fluxbox as a choice for sessions.
Any suggestions about what to do to let me use fluxbox would be greatly appreciated; for me personally, it's just an experiment, but for the person who's getting the 200 MHz Pentium Pro box I've had sitting around and put Fedora Core on, having access to a lower-overhead window manager is very much worthwhile.
James Jones
I use fluxbox as my window manager on Fedora Core 1.
Fluxbox has a problem with the locale-related environment variables on Fedora Core 1. Actually the problem is font-related. It's complicated... When you run fluxbox and just got a blue screen, if you wait a while (quite a while) it will ultimately start up. The solution is to set LC_ALL=C prior to starting up fluxbox.
Create a .xsession file with the following contents:
export LC_ALL=C startfluxbox
(make sure startfluxbox is in your path)
Alternatively, if you're building fluxbox from source, you can apply the following patch so you don't have to do the export LC_ALL=C
diff --unified --recursive --exclude=CVS fluxbox-0.9.6/src/main.cc fluxbox-0.9.6-patched/src/main.cc --- fluxbox-0.9.6/src/main.cc 2003-10-02 12:14:41.000000000 -0400 +++ fluxbox-0.9.6-patched/src/main.cc 2003-12-05 11:18:56.000000000 -0500 @@ -134,6 +134,8 @@ }
int main(int argc, char **argv) { + + setenv("LC_ALL","C",1);
std::string session_display = ""; std::string rc_file;
Save the patch as lcall.patch in the same directory as the fluxbox-0.9.6 directory. Apply the patch by running patch -p1 < ../lcall.patch from inside the fluxbox-0.9.6 directory.
On the GDM login screen, select Session -> default then log in.
If you want to use fluxbox as your gnome window manager, add the following line to the end of your ~/.fluxbox/startup file:
exec gnome-session
My ~/.fluxbox/startup file contains only the following lines:
fluxbox & exec gnome-sessioncd
You also need to copy /usr/share/gnome/default.session to ~/.gnome2/session and remove these lines:
1,id=default1 1,Priority=10 1,RestartCommand=gnome-wm --default-wm gnome-wm --sm-client-id default1 2,id=default2 2,Priority=40
This will prevent metacity from even trying to start.
Theoretically, all you should have to do is set WINDOW_MANAGER=fluxbox in your .bashrc. That should cause gnome-wm to use fluxbox intead of metacity. But, the locale problem and the fact that fluxbox interacts strangely with gnome-session make that solution unworkable.
If you want to use Fluxbox along with gnome and you like the Bluecurve theme, I made a FluxBluecurve style for fluxbox that approximates it. Search for it at themes.freshmeat.net It includes another patch that makes fluxbox tile pixmaps correctly.
Good luck.
David Muse david.muse@firstworks.com
David Muse wrote:
I use fluxbox as my window manager on Fedora Core 1.
Fluxbox has a problem with the locale-related environment variables on Fedora Core 1. Actually the problem is font-related. It's complicated... When you run fluxbox and just got a blue screen, if you wait a while (quite a while) it will ultimately start up. The solution is to set LC_ALL=C prior to starting up fluxbox.
Create a .xsession file with the following contents:
export LC_ALL=C startfluxbox
(make sure startfluxbox is in your path)
Hmmm. "rpm -ql fluxbox | grep startfluxbox" turns up nothing. "rpm -q fluxbox" says I have fluxbox-0.1.14-0.fdr.6.1. Do I have the correct RPM?
http://www.xs4all.nl/~hanb/software/fluxbox/startfluxbox.html shows what appears to be the contents of startfluxbox, and that matches what's in /usr/X11R6/bin/startfluxbox on the computer I have running Mandrake, so I'll create that in that place and see how far I can get.
Thanks very much for the advice. I will followup with the results I get.
James
James Jones wrote:
Thanks very much for the advice. I will followup with the results I get.
OK. I created the startfluxbox script, changing the path to fluxbox itself to fit where the Fedora RPM puts it, and also adding /usr/share/fluxbox/startup which wasn't there but which startfluxbox references. I put the "export LC_ALL=C" in /usr/share/fluxbox/startup.
That done, and with a .xsession of
startfluxbox
I can run fluxbox fine by asking for a default session (it takes maybe five or six seconds to start up). Asking for a fluxbox session explicitly bypasses startfluxbox, I presume, and thus /usr/share/fluxbox/startup, and hence takes a long time (I have yet to wait long enough to say how long it is). I'll experiment with the fluxbox.desktop file, maybe making it
Exec=startfluxbox
to see whether that works.
James
On Sat, 20 Dec 2003 18:10:19 -0600 James Jones jamesjones01@mchsi.com wrote:
David Muse wrote:
I use fluxbox as my window manager on Fedora Core 1.
Fluxbox has a problem with the locale-related environment variables on Fedora Core 1. Actually the problem is font-related. It's complicated... When you run fluxbox and just got a blue screen, if you wait a while (quite a while) it will ultimately start up. The solution is to set LC_ALL=C prior to starting up fluxbox.
Create a .xsession file with the following contents:
export LC_ALL=C startfluxbox
(make sure startfluxbox is in your path)
Hmmm. "rpm -ql fluxbox | grep startfluxbox" turns up nothing. "rpm -q fluxbox" says I have fluxbox-0.1.14-0.fdr.6.1. Do I have the correct RPM?
Ahh, sorry, I use fluxbox-0.9.6 which I compile from source. Fluxbox 0.1.14 doesn't have a startfluxbox script but 0.9.6 does. Also, the patches and FluxBluecurve theme are for 0.9.6
Sorry for the confusion.
Dave
On Sat, 20 Dec 2003 21:37:15 -0600 James Jones jamesjones01@mchsi.com wrote:
James Jones wrote:
Thanks very much for the advice. I will followup with the results I get.
OK. I created the startfluxbox script, changing the path to fluxbox itself to fit where the Fedora RPM puts it, and also adding /usr/share/fluxbox/startup which wasn't there but which startfluxbox references. I put the "export LC_ALL=C" in /usr/share/fluxbox/startup.
That done, and with a .xsession of
startfluxboxI can run fluxbox fine by asking for a default session (it takes maybe five or six seconds to start up). Asking for a fluxbox session explicitly bypasses startfluxbox, I presume, and thus /usr/share/fluxbox/startup, and hence takes a long time (I have yet to wait long enough to say how long it is). I'll experiment with the fluxbox.desktop file, maybe making it
Exec=startfluxboxto see whether that works.
James
I suspect that it will. Although it seems like I tried putting "export LC_ALL=C" my startup file and it didn't work. I can't think of a reason why it wouldn't though so maybe I'm just not remembering it right :)
Dave