Trying to run xchat always gives an "Floating Point Exception". 4.0.6 works flawlessly, 4.1.90 and higher always give this error. Tried binaries and sources from xchat 2.4.0, 2.4.1. Tried terminal, Terminal, multi-gnome-terminal, eterm, all with the same result, so i't not a terminal fault. Reproducible: Always Steps to Reproduce: 1. 2. 3.
I was wondering, do you by any chance use a transparent window for xchat?
(In reply to comment #1) > I was wondering, do you by any chance use a transparent window for xchat? No. this particular machine is pretty slow, so no "fancy" stuff. Just a plain X.Org X11R6.8.1. I just tried to upgrade to RC2, same results still.
I installed 4.0.6, and then, instead of using the installer, i installed package by package, after each one starting X and running x-chat. The error occured after the installation of xfce4-mcs-plugins. I immediately reverted to the 4.0.6 version of the package, x-chat ran again. xfwm4 needs libxfce4mcs-client-1.0 - installed - ok xfwm4 needs libxfce4util-1.0 - installed - ok xfwm4 needs libxfcegui4-1.0 - installed - ok xfwm4 needs xfce-mcs-manager - installed - ok xfwm4 - installed - ok xfceutils - installed - ok xfwm4-themes - installed - ok xfdesktop - installed - ok calendar - installed - ok xfce4-mcs-plugins - installed - Floating Point Exception on x-chat
Hmm, Benedikt, what do you think, can it be icontheme related? Pedro, could you try and get a backtrace from gdb? That may help us find the cause. $ gdb xchat gdb> run *crash* gdb>bt <output of backtrace>
If its icon theme related, then its definetly a bug in xchat. But afterall, I've really no clue about this problem. Pedro, do you use anti-aliasing for fonts and hinting?
Here is the gdb of 2 xchat versions, and I also included the strace: xchat 2.0.7: Program received signal SIGFPE, Arithmetic exception. 0x080739de in gtk_xtext_adjustment_set (buf=0x219, fire_signal=0) at xtext.c:726 726 adj->page_size = (gdb) bt #0 0x080739de in gtk_xtext_adjustment_set (buf=0x219, fire_signal=0) at xtext.c:726 #1 0x080785fe in gtk_xtext_calc_lines (buf=0x0, fire_signal=0) at xtext.c:4198 #2 0x08078a57 in gtk_xtext_size_allocate (widget=0x8105708, allocation=0x8103bf8) at xtext.c:1058 #3 0xb7bd711e in g_cclosure_marshal_VOID__BOXED () from /usr/lib/libgobject-2.0.so.0 #4 0xb7bc2977 in g_signal_type_cclosure_new () from /usr/lib/libgobject-2.0.so.0 #5 0xb7bc2310 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #6 0xb7bd58df in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #7 0xb7bd5077 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #8 0xb7bd5374 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #9 0xb7f171bf in gtk_widget_size_allocate () from /usr/lib/libgtk-x11-2.0.so.0 xchat 2.4.1: Program received signal SIGFPE, Arithmetic exception. 0x08078675 in g_free () (gdb) bt #0 0x08078675 in g_free () #1 0x0810fe80 in ?? () #2 0x0807c1c8 in g_free () #3 0xb7bd711e in ?? () #4 0xb7bc2977 in ?? () #5 0xb7bc2310 in ?? () #6 0xb7bd58df in ?? () #7 0xb7bd5077 in ?? () #8 0xb7bd5374 in ?? () #9 0xb7f171bf in ?? () #10 0xb7de329c in ?? () #11 0xb7bd711e in ?? () #12 0xb7bc2977 in ?? () #13 0xb7bc2310 in ?? () #14 0xb7bd58df in ?? () #15 0xb7bd5077 in ?? () strace xchat 2.4.1: gettimeofday({1102936466, 616628}, NULL) = 0 write(3, "\2\0\4\0004\0\300\1\2\0\0\0\0\0\0\0\2\0\4\0006\0\300\1"..., 3664) = 3664 read(3, "P\0024\1\3\301\1\0\0\1\1\0\0\0\0\0\0\0\0\1\1\1\1\1\0\0"..., 32) = 32 read(3, "P\0024\1\301\301\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32) = 32 read(3, "\0262\212\1M\0\300\1M\0\300\1L\0\300\1\2\0\2\0\"\3\33\0"..., 32) = 32 read(3, "\1\30\214\1\0\0\0\0006\0\0\0\0\0\0\0\0\4\0\3\0\0\0\0\30"..., 32) = 32 --- SIGFPE (Floating point exception) @ 0 (0) --- +++ killed by SIGFPE +++ strace xchat 2.0.7: gettimeofday({1102936521, 608013}, NULL) = 0 write(3, "\2\0\4\0004\0\300\1\2\0\0\0\0\0\0\0\2\0\4\0006\0\300\1"..., 3664) = 3664 read(3, 0xbfffca10, 32) = -1 EAGAIN (Resource temporarily unavailable) select(4, [3], NULL, NULL, NULL) = 1 (in [3]) read(3, "\0262\212\1M\0\300\1M\0\300\1L\0\300\1\2\0\2\0\"\3\33\0"..., 32) = 32 read(3, "\1\30\214\1\0\0\0\0006\0\0\0\0\0\0\0\0\4\0\3\0\0\0\0\30"..., 32) = 32 --- SIGFPE (Floating point exception) @ 0 (0) --- +++ killed by SIGFPE +++
Ok, this really looks like an Xchat bug to me. Pedro, would it be possible for you to upgrade your xchat to 2.4 and check again?
The same happens on 2.0.6, 2.4.0 and 2.4.1.
Maybe the Gtk+ theme engine?
Assuming the possibility of being a Gtk+ theme problem, then why this problem only occurs in xfce, and NOT in gnome, kde, blackbox, wmaker, and enlightenment? (yes, i tested on all those).
As already said, it is possible that a certain bug in xchat or gtk+ is exposed by Xfce, while it is not exposed by Gnome or WindowMaker. Still, that doesn't necessary mean, that Xfce contains a bug; and the problem is that xchat crashes, which simply cannot be caused by Xfce, since xchat contains no code from Xfce and Unix/Linux systems follow the "process separation scheme", which means that no process can act in the context of another process (with the exception of tracing and memory sharing, but thats excluded here, since Xfce neither shares memory with xchat nor does it trace the execution of xchat).
I see. thanks for the explanation. Now, is there a way to bypass my problem? Not being a xfce bug, i assume no changes will be needed in the code. So, with the strace and gdb logs i posted, do you think there is a local solution (or a list of possible solutions, i'm willing to try them all) i might try?
Have you tried to ask the X-Chat guys concerning this problem?
Yes i did, they said that "if the problem occurs only with xfce and not with gnome, kde, wmaker and E, then it is definitely a xfce problem of incomplatibility with your system"
Wow, thats probably the lamest excuse in this situation.
i believe i've seen and/or heard of this before, mainly when xchat has it's pseudo-transparency enabled. it had something to do with something i changed in xfdesktop between 4.0.x and 4.2.x, though i don't really know what. either way, it's definitely a bug in xchat. if the xchat devs don't feel like looking into the bug, that's their problem. X clients should not rely on the presence (or lack) of a particular feature in a desktop environment to function properly (even if they're only doing so unintentionally). if the xchat guys can tell me what in xfdesktop is causing xchat to crash, *and* can give me a good reason why i should be doing something differently, i'll consider changing xfdesktop. at any rate, xchat 2.4.1 works fine on my machine (without pseudo-transparency enabled).
I already said i don't have any kind of transparency or non-default settings for anything. I'm still awaiting a comment on the strace and gdb outputs. I guess that if they were requested, some feedback would be in order.
Ok, well, let's see. 1) An application crashes 2) Let's assume the bug is in the desktop environment?!? That makes no sense. The bug is in XChat. Apparently it gets triggered by somthing Xfce is doing, that doesn't mean the bug is in Xfce though. The bug appears to be in a text handling function, so it might be related to font settings or font rendering.
I'm afraid there is no way this can be interpreted as a bug in Xfce. If there is more information that suggests otherwise, please reopen the report.