It may well be that this bug is specific to fvwm, but here
it is ONLY triggered by gimp.
I think I can trigger the crash reproducibly in my setup:
* I'm using a DesktopSize of 8x2 with two screens
("Xinerama on" is default).
* To trigger the crash, gimp (apparently) must be run on
a "desktop" pretty far to the right (i.e., not on the
first desktop (0,0) of the 16 desktops).
* So, on this dekstop (e.g. (7,1)), I open an xterm and then:
- $ gimp
- File > Open (an existing tiff or png ... file)
- File > Close View
- File > Quit
-> fvwm crashes
(On desktop (0,0): no crash; without "File > Close View" action:
no crash; ...)
Some suspicious lines from .xsession-errors (collected from several
different crashes, not every crash writes a message to
.xession-errors:) are:
*** Error in `x-window-manager': double free or corruption (out):
0x00000000008569a0 ***
*** Error in `x-window-manager': free(): invalid pointer: 0x0000000001081ed0 ***
*** Error in `x-window-manager': malloc(): memory corruption (fast):
0x000000000092f480 ***
*** Error in `x-window-manager': malloc(): memory corruption (fast):
0x00000000025b54e0 ***
*** Error in `x-window-manager': munmap_chunk(): invalid pointer:
0x0000000001ffe0d0 ***
*** Error in `x-window-manager': malloc(): memory corruption (fast):
0x0000000000dc8060 ***
Following these errors are fatal errors of several open programs:
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 78 requests (76 known processed) with 0 events remaining.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 133 requests (115 known processed) with 0 events remaining.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 261 requests (197 known processed) with 0 events remaining.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 83 requests (81 known processed) with 0 events remaining.
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X
server ":0.0"
...
Probably not related are some persistent fvwm charset problems:
[fvwm][convert_charsets]: WARNING -
Invalid byte sequence during conversion from UTF-8 to ISO-8859-1
Rarely, errors are also written to syslog/kern.log when fvwm crashes:
Mar 16 09:19:57 myname kernel: [146626.224888] x-window-manage[25095]: segfault
at 7f7d23cf9570 ip 00007f7d21bafb95 sp 00007ffc7712d650 error 4 in
libc-2.19.so[7f7d21b37000+19f000]
Mar 16 09:23:57 myname kernel: [146866.749516] x-window-manage[25548]: segfault
at 7f8211f86b30 ip 00007f820f593b95 sp 00007ffdcbdff6e0 error 4 in
libc-2.19.so[7f820f51b000+19f000]
As mentioned before (but not necessarily related), fvwm does not
display handles for several dialog windows, e.g., in gimp (File > Open)
or xpdf.
These crashes are really annoying; please let me know if I can
help you to remove this bug.
Olaf
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages fvwm depends on:
ii libc6 2.19-15
ii libcairo2 1.14.0-2.1
ii libfontconfig1 2.11.0-6.3
ii libfreetype6 2.5.2-3
ii libfribidi0 0.19.6-3
ii libgdk-pixbuf2.0-0 2.31.1-2+b1
ii libglib2.0-0 2.42.1-1
ii libice6 2:1.0.9-1+b1
ii libperl4-corelibs-perl 0.003-1
ii libpng12-0 1.2.50-2+b2
ii libreadline6 6.3-8+b3
ii librplay3 3.3.2-14
ii librsvg2-2 2.40.5-1
ii libsm6 2:1.2.2-1+b1
ii libstroke0 0.5.1-6.1
ii libtinfo5 5.9+20140913-1+b1
ii libx11-6 2:1.6.2-3
ii libxcursor1 1:1.1.14-1+b1
ii libxext6 2:1.3.3-1
ii libxft2 2.3.2-1
ii libxinerama1 2:1.1.3-1+b1
ii libxpm4 1:3.5.11-1+b1
ii libxrender1 1:0.9.8-1+b1
ii perl 5.20.2-2
ii zlib1g 1:1.2.8.dfsg-2+b1
Versions of packages fvwm recommends:
ii fvwm-icons 20070101-2
ii libx11-protocol-perl 0.56-6
ii perl-tk 1:804.032-3+b3
Versions of packages fvwm suggests:
ii cpp 4:4.9.2-2
pn fvwm-themes <none>
pn m4 <none>
ii menu 2.1.47
pn wm-icons <none>
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
