Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#896 - fluxbox-devel does not exit properly

Attached to Project: Arch Linux
Opened by Scott Robbins (scottro111) - Monday, 10 May 2004, 00:33 GMT
Last edited by Eric Johnson (eric) - Tuesday, 11 May 2004, 13:13 GMT
Task Type Bug Report
Category Packages: Unstable
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture not specified
Severity Very Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

As mentioned in forum thread

http://bbs.archlinux.org/viewtopic.php?t=4378
the latest version of fluxbox-devel (0.9.9-1) will, if one selects exit from the RootMenu, hang and freeze. The only way to exit X is use ctl+alt+bkspace.

Apparently only some users are experiencing this issue. Others are not having problems.

This task depends upon

Closed by  Tobias Kieslich (tobias)
Sunday, 06 February 2005, 15:29 GMT
Reason for closing:  Won't fix
Additional comments about closing:  I close it since no one can reproduce it anymore
Comment by Scott Robbins (scottro111) - Monday, 10 May 2004, 15:10 GMT
As suggested in the thread listed above, I found that if I remove the enable of kde, gnome and slit, the problem disappears.

However,in FreeBSD at least, all of these are enabled by default, and do not have this problem.
Comment by Scott Robbins (scottro111) - Monday, 10 May 2004, 15:54 GMT
Again, as mentioned in the thread above, I recompiled and left in all defaults save the slit. Adding --disable-slit to config options does solve the problem.

I ~think~ it is an Arch issue however. In Slackware, using the sources from Fluxbox's site, and leaving all defaults (which include the slit) I don't have this problem.
Comment by Scott Robbins (scottro111) - Thursday, 22 July 2004, 04:51 GMT
As per http://bbs.archlinux.org/viewtopic.php?p=36125#36125
one quick fix is to change the init file's default
session.screen0.slit.autoHide: False

to

session.screen0.slit.autoHide: True

This fixes the problem.

Comment by Tobias Kieslich (tobias) - Thursday, 22 July 2004, 22:03 GMT
I still have not reproduced the issue so far, this is why I have to rely any given information. I will compare the changes slackware and gentoo make on the sources to my tweaks and set the init as you suggested.
Thanks for pointing that out.
-neri
Comment by Tobias Kieslich (tobias) - Sunday, 08 August 2004, 15:35 GMT
I rebuilt fluxbox with the standard init tweaked. In the meantime I found a box on which I can reproduce the issue, but have no clue where that comes from. Argh.
Comment by Scott Robbins (scottro111) - Sunday, 08 August 2004, 17:39 GMT
Heh, now if only no one used the slit. Just tested the new version and it does fix the problem. I don't use the slit.

A thought--I wonder if those that do use the slit, if they have a slit file (or directory--as I said, I don't use it, so don't know which it is) in their ~/.fluxbox directory don't have the problem.

Sorry to be giving you more work--I'm not a coder at all, so don't even know where to begin looking.

On the bright side, the new version does avoid the problem. I'll post a mention of it in the threads on forums.

Thanks for your hard work.

Comment by Scott Robbins (scottro111) - Wednesday, 11 August 2004, 15:52 GMT
Interesting--again according to the thread on forums

http://bbs.archlinux.org/viewtopic.php?p=38607#38607

it seems that the problem might be with fluxbox after all. Sigh

I'm ~so~ glad I'm not a maintainer. :)
Comment by Tobias Kieslich (tobias) - Tuesday, 09 November 2004, 16:15 GMT
This bug is a damn miracle. The box where it appeared just runs fine again. Anyone who can produce that error plase do that:
Try to disable your display manger(kdm;xdm;gdm whatever) and start fluxbox via startx from a console. Make sure it does freeze the X shutdown. Get yourself a sshd running on that box and logon it from another one. Use startx from the other box and watch the output and especially the errors. I know you can do that via ALT+CTRL+F1 but sshd makes it easier to watch in realtime especially the shutdown when your monitor turns blind.
Thanks.
Comment by arjan timmerman (blaasvis) - Sunday, 06 February 2005, 14:08 GMT
is this resolved now ?
Comment by Scott Robbins (scottro111) - Sunday, 06 February 2005, 14:13 GMT
It seems to be. I just did a fresh install, and had forgotten about the bug. I installed fluxbox-devel, and it seems to work without problem.

Comment by Tobias Kieslich (tobias) - Sunday, 06 February 2005, 15:26 GMT
Woah, perfectly coincidentally I'm just building 0.9.12 and I didn't see this error on the testbuild.
I just got no fonts when antialias: false, but this another issue. From myside it can be closed.

Loading...