First X11 session login problem [CLOSED]

By lyeinyoureye (User), on Thu Jun 23 03:48:36 2005: First X11 session login problem [CLOSED].

I use ~/.xsession to run adesklets when I login to openbox. The weird thing is, sometimes only the weather forecast loads, other times, only modubar loads, and sometimes both load. This only happens right after I boot. If I login twice everything loads the second...etc... time np.
Any ideas?

By syfou (Core Developer & Desklet Author), on Thu Jun 23 13:03:21 2005.

That's weird, and I do not see how it can happen right now. Launching adesklets without parameters always starts these events:

All the files matching /tmp/adesklets_uid$UID_*.lock are all read, and all the pids they containted are killed if they exist, then those files are deleted. Those lock files are used to avoid to have duplicate of the sames instances of the same desklet running for a given user.
$HOME/.adesklets is parsed, and contained desklets are started in sequence.

Could you:

Check what you have in term of /tmp/adesklets_uid$UID_*.lock file before starting your first X11 session (with the proper $UID, of course).
Post a copy of your $HOME/.xsession, if it is not too long
Post a copy of your $HOME/.adesklets

There is a small possibility, if you get at least a file at (1), that there is a leak in the way your session manager handles the logout. If it is the case, I suggest you include some post-session script like the following (in bash):

Code:


LOCKS=`ls /tmp/adesklets_uid$UID_*.lock`
kill `cat $LOCKS` & { sleep 1; kill -9 `cat $LOCKS` }
rm -f $LOCKS

I will be out of town for the week-end (tomorrow is an holiday where I live), but I should get back to you on monday.

By lyeinyoureye (User), on Thu Jun 23 21:45:50 2005.

~/.xsession

Code:

numlockx &
[ -f ~/.fehbg ] && source ~/.fehbg &
fbpanel &
xmms -p &
xcompmgr &
adesklets &

exec openbox

~/.adesklets

Code:


[/home/hdb2/desklets/modubar-0.0.1/modubar.py]
id=0 screen=0 x=555 y=638

[/home/hdb2/desklets/weatherforecast-0.2.0/weatherforecast.py]
id=1 screen=0 x=524 y=27

the contents of the modubar and weatherforecast uid's respectively

Code:

11041 11044

Code:

11042 11043

Even when both uid's are present sometimes only one, or the other, or both will start. If I reboot/shutdown right after this, then I'll only have the uid/s of the active process. However both uids were present before starting X, and only weatherforecast launched.

By syfou (Core Developer & Desklet Author), on Tue Jun 28 17:29:27 2005.

All your configuration files are absolutely pristine -- I have to say I am stumped by this behavior, witch I never experienced myself; there is a way to know for sure what happens, but it involves a little work from you. What you would need to do is compiling a "debug" version of adesklets, then dig though the generated log files, or hand them out to me (how doing this is explained in the subsection 5.2.1 of adesklets 0.4.10 documentation).

Another slight possibility (but this is far fetched) would be the presence of some OO killer or ressources control on your system: maybe should you try not invoking adesklets in the background in your $HOME/.xsession.

Unfortunately, I am only back in Montr?al for a couple hours; I should be back around next Monday to tackle down this issue with you.

By joecracker (User), on Tue Jul 5 15:13:05 2005.

I experienced the same behaviour with fluxbox. Randomly some adesklets were missing after startup.

I could get rid of this behaviour by making sure, that the background image is set before any adesklet is started.

To accomplish this I commented out the setting of the background in the style-file located in ~/.fluxbox/styles and added the same line into ~/.fluxbox/startup.

Snippet from my ~/.fluxbox/startup:

Code:


# You can set your favourite wallpaper here if you don't want
# to do it from your style.
Esetroot  ~/pix/backgrounds/co2metal-1081909831.jpg
# Applications you want to run with fluxbox.
# MAKE SURE THAT APPS THAT KEEP RUNNING HAVE AN ''&'' AT THE END.
aterm &
adesklets &
# 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/bin/fluxbox

Maybe there is a similiar problem and solution with other wms.

By syfou (Core Developer & Desklet Author), on Tue Jul 5 18:26:58 2005.

Thanks for the hint, joecraker. I am also a fluxbox user, and I usually use the $HOME/.fluxbox/startup script to start adesklets myself. This said, I do not experience this "missing desklet" symptom regardless of the sequence I set up on my home system (launching adesklets before/after the WM, before/after setting the background image)... From a programmatic standpoint, I do not see any validation for this behavior either. :?

Of course, this doesn't mean this is not correlated and that it cannot help people, just that I do not understand it if it does. :lol:

Main index > Usage problems > First X11 session login problem [CLOSED]

By lyeinyoureye (User), on Thu Jun 23 03:48:36 2005: First X11 session login problem [CLOSED].

By syfou (Core Developer & Desklet Author), on Thu Jun 23 13:03:21 2005.

Code:

By lyeinyoureye (User), on Thu Jun 23 21:45:50 2005.

Code:

Code:

Code:

Code:

By syfou (Core Developer & Desklet Author), on Tue Jun 28 17:29:27 2005.

By joecracker (User), on Tue Jul 5 15:13:05 2005.

Code:

By syfou (Core Developer & Desklet Author), on Tue Jul 5 18:26:58 2005.

adesklets is proud to be hosted on: