Bug#473010:

Yes this has been fixed since FVWM 2.5.26. Since you asked, the reason it crashed was because format == NULL, and as you might realise, you can't dereference NULL; that will cause a SEGFAULT. -- Thomas Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject o

Bug#473010: Also happens with x-window-manage

When looking for temporary ways around this bug, I tried x-window-manage and got the same error: fvwm2[29972]: segfault at 0004 eip 0808517e esp bf8a1800 error 4 x-window-manage[30152]: segfault at 0004 eip 0808517e esp bfaba1f0 error 4 So I suspect a shared library issue. I've ended up

Bug#473010: fvwm also segfaults under vnc4server

Package: fvwm Version: 1:2.5.25-1 Followup-For: Bug #473010 In case it helps, fvwm also segfaults under xvnc4server. I don't have a stack trace. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50,

Bug#473010: fvwm: FVWM crashes when started in tightvncserver

Package: fvwm Version: 1:2.5.25-1 Severity: normal Hi, while debugging another issue with FVWM in a tightvncserver instance, I came accross a SIGSEGV of FVWM when starting. It happens to the 2.5.25 debian package, but not the the latest CVS HEAD. Here is the gdb bt of a self compiled apt-get sou