! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Terminal crash upon opening another, no backtrace
Status:
RESOLVED: DUPLICATE
Product:
Xfce4-terminal
Component:
General

Comments

Description nicolas.stalder 2013-05-22 10:52:21 CEST
Setup: One X session, two gfx cards with one monitor each.

Upon starting xfce4-terminal on one monitor, and then again on another, the first crashes.

https://gist.github.com/anonymous/5626044
The program 'xfce4-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 454 error_code 8 request_code 1 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.)

Running in gdb doesn't say much more:
https://gist.github.com/anonymous/5626099

(gdb) break gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (gdk_x_error) pending.
(gdb) run --sync
Starting program: /usr/bin/xfce4-terminal --sync
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe9c03700 (LWP 2108)]
[New Thread 0x7fffe3fff700 (LWP 2109)]
[New Thread 0x7fffe325c700 (LWP 2112)]
The program 'xfce4-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 1147 error_code 8 request_code 1 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.)
[Thread 0x7fffe3fff700 (LWP 2109) exited]
[Thread 0x7fffe9c03700 (LWP 2108) exited]
[Thread 0x7ffff7fb5940 (LWP 2104) exited]
[Inferior 1 (process 2104) exited with code 01]
(gdb) bt
No stack.

This is up-to-date Arch Linux, and the problem didn't exist until recently.

Some recent changes:
gtk2 (2.24.17-1 -> 2.24.18-1)
vte-common (0.34.4-1 -> 0.34.5-1)
xorg-appres (1.0.3-3 -> 1.0.4-1)
xorg-fonts-alias (1.0.2-2 -> 1.0.3-1)
xorg-xrefresh (1.0.4-3 -> 1.0.5-1)

Seems not to be a duplicate of this bug:
https://bugzilla.xfce.org/show_bug.cgi?id=2339

Rolling back gtk2 and vte-common does not help.
Comment 1 dark-wulf 2013-06-06 16:28:55 CEST
I get the same error on gentoo x86_64 but i got only one nvidia card and dual-screen with separated x-server, i not sure but i think it happened after some X updates

If i start it with "xfce4-terminal --disable-server" then it works on both screens
Comment 2 Chris M 2014-01-22 06:15:19 CET
I'm hitting this same issue. I'm also on gentoo x86_64. I have 2 video cards with 1 monitor each. I can start as many xfce4-terminals as I want as long as they're all on the same screen. As soon as I try to launch one on the 2nd screen, all of the terminal windows on the 1st screen disappear & I get the same error message as in the original post.

This just started yesterday when I upgraded to version 0.6.2. I'm not positive which version I had before but I'd guess it was probably 0.4.8.

Tonight I upgraded again, to 0.6.3 to see if the problem would go away but it did not.

I tried adding '--disable-server' and the problem does go away if I use that.
Comment 3 Igor editbugs 2016-07-13 16:12:04 CEST
Duplicate.

*** This bug has been marked as a duplicate of bug 10124 ***

Bug #10109

Reported by:
nicolas.stalder
Reported on: 2013-05-22
Last modified on: 2016-07-13

People

Assignee:
Nick Schermer
CC List:
4 users

Version

Attachments

Additional information