A new cairo "stable" release is out and it seems to trigger another bug with NX. When I update the remote system to the new cairo release the Xfce session gives lots of such errors:
The program 'xfce4-netload-plugin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 225 error_code 2 request_code 25 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'wrapper' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 325 error_code 2 request_code 25 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) xfce4-panel-Message: Plugin netload-12 has been automatically restarted after crash. xfce4-panel-Message: Plugin systemload-14 has been automatically restarted after crash. The program 'xfce4-mixer-plugin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 217 error_code 2 request_code 25 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) xfce4-panel-Message: Plugin xfce4-mixer-plugin-11 has been automatically restarted after crash. The program 'xfce4-netload-plugin' received an X Window System error. This probably reflects a bug in the program. ...
All gtk windows seem to instantly crash. The panel and also the menu at right click.
Any idea how to debug this? Do we need to build NX with debug symbols or some gtk/Xfce packages?
PS: We don't seem to have a generic way in NX-libs to apply distro C(XX)FLAGS. I see wild hacks all around. Any idea how to improve this?
-Andy ArchLinux
Hi Andreas,
can you resend your report to X2Go BTS with the following mail layout:
""" To: submit@bugs.x2go.org Subject: NX and cairo 1.12.4 Body: Package: x2goagent Severity: important Version: 3.5.0.15
<your mail text> """
Thanks, Mike
On Sa 06 Okt 2012 21:52:56 CEST Andreas Radke wrote:
A new cairo "stable" release is out and it seems to trigger another bug with NX. When I update the remote system to the new cairo release the Xfce session gives lots of such errors:
The program 'xfce4-netload-plugin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 225 error_code 2 request_code 25 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'wrapper' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 325 error_code 2 request_code 25 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) xfce4-panel-Message: Plugin netload-12 has been automatically restarted after crash. xfce4-panel-Message: Plugin systemload-14 has been automatically restarted after crash. The program 'xfce4-mixer-plugin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 217 error_code 2 request_code 25 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) xfce4-panel-Message: Plugin xfce4-mixer-plugin-11 has been automatically restarted after crash. The program 'xfce4-netload-plugin' received an X Window System error. This probably reflects a bug in the program. ...
All gtk windows seem to instantly crash. The panel and also the menu at right click.
Any idea how to debug this? Do we need to build NX with debug symbols or some gtk/Xfce packages?
PS: We don't seem to have a generic way in NX-libs to apply distro C(XX)FLAGS. I see wild hacks all around. Any idea how to improve this?
-Andy ArchLinux
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
The error keeps crashing gtk widgets also in the new 1.12.6 release.
I've tried to get some useful output with gdb attaching to the remote nxagent process. But it doesn't give any useful out. I've built nx-libs and cairo with debug symbols unstripped.
Any hint how to get better debug info?
-Andy
Hi Alex, hi Andy,
On Di 23 Okt 2012 14:20:41 CEST Andreas Radke wrote:
The error keeps crashing gtk widgets also in the new 1.12.6 release.
I've tried to get some useful output with gdb attaching to the remote nxagent process. But it doesn't give any useful out. I've built nx-libs and cairo with debug symbols unstripped.
Any hint how to get better debug info?
-Andy
@Alex: can you give some infos on debugging nx-libs to Andy?
Thanks! Mike
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 24.10.2012 11:08, schrieb Mike Gabriel:
Hi Alex, hi Andy,
On Di 23 Okt 2012 14:20:41 CEST Andreas Radke wrote:
The error keeps crashing gtk widgets also in the new 1.12.6 release.
I've tried to get some useful output with gdb attaching to the remote nxagent process. But it doesn't give any useful out. I've built nx-libs and cairo with debug symbols unstripped.
Any hint how to get better debug info?
-Andy
@Alex: can you give some infos on debugging nx-libs to Andy?
Thanks! Mike
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Hi,
as nx-libs based on Xorg sources, debugging of nx-libs is just the same as debugging of Xorg. There is a lot of information about it in Internet. Just google.
regards, Alex
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
-
Andreas Radke -
Mike Gabriel -
Oleksandr Shneyder