Re: Fbpager quirk

On Fri, 29 Jun 2007 16:58:28 -0400, Peter N Spotts wrote:

> On Fri, 29 Jun 2007 16:23:36 +0000 (UTC) Lionel B
> <[email protected]> wrote:
> 
>> On Fri, 29 Jun 2007 08:33:27 -0400, Peter N Spotts wrote:
>> 
>> > On Fri, 29 Jun 2007 10:50:31 +0000 (UTC) Lionel B
>> > <[email protected]> wrote:
>> > 
>> >> On Thu, 28 Jun 2007 08:08:15 -0400, Peter N Spotts wrote:
>> >> 
>> >> > Folks,
>> >> > 
>> >> > I'm using Fluxbox v 1.0rc3 on Ubuntu Fiesty and use fbpager with
>> >> > Fluxbox. I have fbpager set up to run in the lower right corner of
>> >> > my screen with four virtual desktops. When I log in from a cold
>> >> > start, fbpager shows only two virtual desktops out of four I have
>> >> > set up. In fact, the pager looks as though it is setting itself up
>> >> > slightly off screen, then showing the two desktops. When I use
>> >> > gnome-system-monitor to shut fbpager down, and then I restart it,
>> >> > fbpager appears on the screen as I originally intended, with all
>> >> > four desktops showing.
>> >> > 
>> >> > What might be causing the cold-start conundrum?
>> >> 
>> >> Some details would help:
>> >> 
>> >> How do you start X? Do you use a display manager (gdm, kdm, xdm,
>> >> wdm, ...) or do you just use startx?
>> >> 
>> >> How/from what script do you start fbpager?
>> >> 
>> > I think it's Ubuntu's version of gdm. Then I have fbpager & listed in
>> > the startup file in /home/~/.fluxbox.
>> 
>> Could you perhaps post your ~/.fluxbox/startup here?
>> 
>> 
> Sure. And I quote:
> 
> 
> # fluxbox startup-script:
> #
> # Lines starting with a '#' are ignored.
> 
> # You can set your favourite wallpaper here if you don't want # to do it
> from your style.
> #
> # bsetbg -f ~/pictures/wallpaper.png
> #
> # This sets a black background
> 
> /usr/bin/fbsetroot -solid black
>> # This shows the fluxbox-splash-screen #fbsetbg -C
> /usr/share/fluxbox/splash.jpg
> 
> # Other examples. Check man xset for details. #
> # Turn off beeps:
> # xset -b
> #
> # Increase the keyboard repeat-rate:
> # xset r rate 195 35
> #
> # Your own fonts-dir:
> # xset +fp /home/pspotts/.font
> #
> # Your favourite mouse cursor:
> # xsetroot -cursor_name right_ptr
> #
> # Change your keymap:
> # xmodmap ~/.Xmodmap
> 
> 
> 
> # Applications you want to run with fluxbox. # MAKE SURE THAT APPS THAT
> KEEP RUNNING HAVE AN ''&'' AT THE END. #
> xscreensaver -no-splash &
> fbsetbg -f /home/pspotts/Backgrounds/M81.jpg & fbpager &
> #conky -b &
> gkrellm &
> fetchmail -a -d 60 &
> mail-notification &
> jpilot -i &
> liferea --mainwindow-state=hidden &
> pidgin &
> 
> 
> # And last but not least we start fluxbox. # Because it is the last app
> you have to run it with ''exec'' before it.
> 
> exec /usr/local/bin/fluxbox
> # or if you want to keep a log:
> # exec /usr/bin/fluxbox -log ~/.fluxbox/log

Hmmm, looks ok to me. Does it make any difference if you comment out 
*everything* except for the two lines:

  fbpager &
  exec /usr/local/bin/fluxbox

Otherwise, I'm not sure how gdm ultimately invokes .fluxbox/startup under 
your setup (this tends to be insanely overcomplicated and also varies 
between distros). Just a guess, but it may be that the login procedure is 
starting other (possibly Gnome) stuff that interacts badly with fluxbox/
fbpager.

As an experiment you could go for a "clean" X startup as follows: set up 
a .xinitrc file in your home directory containing the same commands as 
your .fluxbox/startup. Then boot into runlevel 3 (i.e. non-GUI), start 
your X server with the 'startx' command and see what you get.

If this gives you sensible behaviour you could then try tracing the logic 
through the scripts triggered by gdm to find out what else is being run.

-- 
Lionel B


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/