benedikt.meurer at unix-ag.uni-siegen.de
Tue Jan 13 23:06:14 CET 2004
Olivier Fourdan wrote:
> Hi Benny,
> There are a couple of issues I wanted to report about xfce4-session, but
> I kept forgetting... Anyway.
> Issue #1)
> Once I rapidly double-clicked the "quit" button, xfce4-session grayed
> out the screen and enter some kine a deadlock. The only issue I had was
> to kill X. This did not happen for a while, so I don't know if you fixed
Hm, not reproducible here. Can you attach a gdb to the xfce4-session process
when it happens again and send me a backtrace please.
> Issue #2)
> This is one is 100% reproducible and leads to a session crash.
> I often run brute force tests against xfwm4 to check its behaviour under
> high load.
> I run a script that open up a terminal, and then close it right away, in
> a loop. As a result, the terminals open and close very quickly. This
> leads to a session crash after a few minutes.
> $ cat ./dumb.sh
> sleep 1
> $ while `/bin/true`; do xterm -e ./dumb.sh & done
Works fine, except that the xterm from which the while... stuff is executed
dies after some time for some weird reason. xfce4-session reports an
unexpected socket close() at that time. Again a backtrace would be nice :-)
NetBSD Operating system: http://www.NetBSD.org/
pkgsrc "Work in progress": http://pkgsrc-wip.sf.net/
XFce desktop environment: http://www.xfce.org/
German Unix-AG Association: http://www.unix-ag.org/
OpenPGP Key: http://www.home.unix-ag.org/bmeurer/#gpg
More information about the Xfce4-dev