Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#67475 - [xorg]? Various applications crash when changing display configuration
Attached to Project:
Arch Linux
Opened by AntiCompositeNumber (AntiComposite) - Monday, 03 August 2020, 18:03 GMT
Last edited by freswa (frederik) - Tuesday, 04 August 2020, 17:22 GMT
Opened by AntiCompositeNumber (AntiComposite) - Monday, 03 August 2020, 18:03 GMT
Last edited by freswa (frederik) - Tuesday, 04 August 2020, 17:22 GMT
|
DetailsDescription:
After a recent update, various applications crash when I unplug or plug in an external display or use xrandr to configure my displays. Known affected applications: hexchat 2.14.3-2 volctl 0.6.3-1 keepassxc 2.6.0-2 dropbox 102.4.431-1 network-manager-applet 1.18.0-1 blueberry 1.3.9-1 udiskie 2.2.0-2 Running on i3 4.18.2-1 with libx11 1.6.10-2 Additional info: Hexchat crash when plugging in an external display: (hexchat:93550): Gdk-WARNING **: 13:03:18.079: GdkWindow 0x1e00082 unexpectedly destroyed The program 'hexchat' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 62981 error_code 143 request_code 139 minor_code 7) (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.) Same event, but with blueberry-tray (through journalctl): Aug 03 13:03:18 <hostname> blueberry-tray[93020]: GdkWindow 0x40000b unexpectedly destroyed Aug 03 13:03:18 <hostname> blueberry-tray[93020]: The program 'blueberry-tray.py' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 406 error_code 143 request_code 139 (RENDER) minor_code 7) (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 GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Spray of warnings and errors when turning on that display using xrandr: (hexchat:93787): Gdk-WARNING **: 13:04:05.749: GdkWindow 0x800077 unexpectedly destroyed (hexchat:93787): Gtk-CRITICAL **: 13:04:05.752: IA__gtk_image_set_from_pixbuf: assertion 'GTK_IS_IMAGE (image)' failed (hexchat:93787): Gtk-CRITICAL **: 13:04:05.753: IA__gtk_image_set_from_pixbuf: assertion 'GTK_IS_IMAGE (image)' failed (hexchat:93787): Gtk-CRITICAL **: 13:04:05.755: IA__gtk_image_set_from_pixbuf: assertion 'GTK_IS_IMAGE (image)' failed (hexchat:93787): Gtk-CRITICAL **: 13:04:05.757: IA__gtk_image_set_from_pixbuf: assertion 'GTK_IS_IMAGE (image)' failed (hexchat:93787): Gtk-CRITICAL **: 13:04:05.762: IA__gtk_image_set_from_pixbuf: assertion 'GTK_IS_IMAGE (image)' failed (hexchat:93787): Gtk-CRITICAL **: 13:04:05.764: IA__gtk_image_set_from_pixbuf: assertion 'GTK_IS_IMAGE (image)' failed (hexchat:93787): Gtk-CRITICAL **: 13:04:06.250: IA__gtk_image_set_from_pixbuf: assertion 'GTK_IS_IMAGE (image)' failed (hexchat:93787): Gtk-CRITICAL **: 13:04:06.250: IA__gtk_widget_set_tooltip_text: assertion 'GTK_IS_WIDGET (widget)' failed (hexchat:93787): GLib-GObject-WARNING **: 13:04:06.250: instance with invalid (NULL) class pointer (hexchat:93787): GLib-GObject-CRITICAL **: 13:04:06.250: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (hexchat:93787): GLib-GObject-WARNING **: 13:04:06.250: instance with invalid (NULL) class pointer (hexchat:93787): GLib-GObject-CRITICAL **: 13:04:06.250: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (hexchat:93787): GLib-GObject-WARNING **: 13:04:06.250: instance with invalid (NULL) class pointer (hexchat:93787): GLib-GObject-CRITICAL **: 13:04:06.251: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (hexchat:93787): GLib-GObject-WARNING **: 13:04:06.251: instance with invalid (NULL) class pointer (hexchat:93787): GLib-GObject-CRITICAL **: 13:04:06.251: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (hexchat:93787): GLib-GObject-WARNING **: 13:04:06.251: instance with invalid (NULL) class pointer (hexchat:93787): GLib-GObject-CRITICAL **: 13:04:06.251: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (hexchat:93787): GLib-GObject-WARNING **: 13:04:06.251: instance with invalid (NULL) class pointer (hexchat:93787): GLib-GObject-CRITICAL **: 13:04:06.251: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (hexchat:93787): GLib-GObject-WARNING **: 13:04:06.251: instance with invalid (NULL) class pointer (hexchat:93787): GLib-GObject-CRITICAL **: 13:04:06.251: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (hexchat:93787): GLib-GObject-WARNING **: 13:04:06.251: instance with invalid (NULL) class pointer (hexchat:93787): GLib-GObject-CRITICAL **: 13:04:06.251: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (hexchat:93787): GLib-GObject-WARNING **: 13:04:06.251: instance with invalid (NULL) class pointer (hexchat:93787): GLib-GObject-CRITICAL **: 13:04:06.251: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (hexchat:93787): Gtk-CRITICAL **: 13:04:06.251: IA__gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (hexchat:93787): Gtk-CRITICAL **: 13:04:06.251: IA__gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Same event, but with blueberry-tray: Aug 03 13:03:41 <hostname> blueberry-tray[93699]: GdkWindow 0x400002 unexpectedly destroyed Aug 03 13:03:41 <hostname> blueberry-tray[93699]: The program 'blueberry-tray.py' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 371 error_code 143 request_code 139 (RENDER) minor_code 7) (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 GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Aug 03 13:03:41 <hostname> audit[93699]: ANOM_ABEND auid=1000 uid=1000 gid=985 ses=2 pid=93699 comm="blueberry-tray" exe="/usr/bin/python3.8" sig=5 res=1 Aug 03 13:03:41 <hostname> kernel: traps: blueberry-tray[93699] trap int3 ip:7fdaa08bb314 sp:7fff41721e00 error:0 in libglib-2.0.so.0.6400.4[7fdaa087c000+85000] Aug 03 13:03:41 <hostname> kernel: audit: type=1701 audit(1596474221.410:523): auid=1000 uid=1000 gid=985 ses=2 pid=93699 comm="blueberry-tray" exe="/usr/bin/python3.8" sig=5 res=1 Aug 03 13:03:41 <hostname> systemd[866]: blueberry-tray.service: Main process exited, code=dumped, status=5/TRAP Aug 03 13:03:41 <hostname> systemd[866]: blueberry-tray.service: Failed with result 'core-dump'. Aug 03 13:03:41 <hostname> systemd[866]: blueberry-tray.service: Scheduled restart job, restart counter is at 13. Aug 03 13:03:41 <hostname> systemd[866]: Stopped Starts blueberry-tray. Aug 03 13:03:41 <hostname> systemd[866]: Started Starts blueberry-tray. Crash when turning off that display using xrandr: (hexchat:23956): Gdk-WARNING **: 12:53:03.638: GdkWindow 0xe00077 unexpectedly destroyed (hexchat:23956): Gtk-CRITICAL **: 12:53:04.362: IA__gtk_image_set_from_pixbuf: assertion 'GTK_IS_IMAGE (image)' failed (hexchat:23956): Gtk-CRITICAL **: 12:53:04.362: IA__gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed The program 'hexchat' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 1545575 error_code 3 request_code 18 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.) Full journal for turning off the display and then unplugging it: Aug 03 12:53:03 blueberry-tray[84301]: GdkWindow 0x800002 unexpectedly destroyed Aug 03 12:53:03 kernel: traps: volctl[77528] trap int3 ip:7fce814e3314 sp:7ffcafde8b30 error:0 in libglib-2.0.so.0.6400.4[7fce814a4000+85000] Aug 03 12:53:03 kernel: audit: type=1701 audit(1596473583.635:475): auid=1000 uid=1000 gid=985 ses=1 pid=77528 comm="volctl" exe="/usr/bin/python3.8" sig=5 res=1 Aug 03 12:53:03 kernel: traps: blueberry-tray[84301] trap int3 ip:7f2448725314 sp:7ffe0935d750 error:0 in libglib-2.0.so.0.6400.4[7f24486e6000+85000] Aug 03 12:53:03 kernel: audit: type=1701 audit(1596473583.635:476): auid=1000 uid=1000 gid=985 ses=2 pid=84301 comm="blueberry-tray" exe="/usr/bin/python3.8" sig=5 res=1 Aug 03 12:53:03 kernel: traps: nm-applet[84362] trap int3 ip:7f4d43294314 sp:7ffd1dd8db20 error:0 in libglib-2.0.so.0.6400.4[7f4d43255000+85000] Aug 03 12:53:03 kernel: audit: type=1701 audit(1596473583.645:477): auid=1000 uid=1000 gid=985 ses=1 pid=84362 comm="nm-applet" exe="/usr/bin/nm-applet" sig=5 res=1 Aug 03 12:53:03 audit[77528]: ANOM_ABEND auid=1000 uid=1000 gid=985 ses=1 pid=77528 comm="volctl" exe="/usr/bin/python3.8" sig=5 res=1 Aug 03 12:53:03 audit[84301]: ANOM_ABEND auid=1000 uid=1000 gid=985 ses=2 pid=84301 comm="blueberry-tray" exe="/usr/bin/python3.8" sig=5 res=1 Aug 03 12:53:03 audit[84362]: ANOM_ABEND auid=1000 uid=1000 gid=985 ses=1 pid=84362 comm="nm-applet" exe="/usr/bin/nm-applet" sig=5 res=1 Aug 03 12:53:03 blueberry-tray[84301]: The program 'blueberry-tray.py' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 356 error_code 143 request_code 139 (RENDER) minor_code 7) (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 GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Aug 03 12:53:03 systemd[866]: blueberry-tray.service: Main process exited, code=dumped, status=5/TRAP Aug 03 12:53:03 systemd[866]: blueberry-tray.service: Failed with result 'core-dump'. Aug 03 12:53:03 systemd[866]: blueberry-tray.service: Scheduled restart job, restart counter is at 9. Aug 03 12:53:03 systemd[866]: Stopped Starts blueberry-tray. Aug 03 12:53:03 systemd[866]: Started Starts blueberry-tray. Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2812, resource id: 75497478, major code: 10 (UnmapWindow), minor code: 0 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 143 (Unknown), sequence: 2816, resource id: 75497481, major code: 139 (Unknown), minor code: 7 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2822, resource id: 75497478, major code: 4 (DestroyWindow), minor code: 0 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3030, resource id: 75497764, major code: 19 (DeleteProperty), minor code: 0 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3031, resource id: 75497764, major code: 18 (ChangeProperty), minor code: 0 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3033, resource id: 75497764, major code: 8 (MapWindow), minor code: 0 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3034, resource id: 75497764, major code: 10 (UnmapWindow), minor code: 0 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 143 (Unknown), sequence: 3036, resource id: 75497766, major code: 139 (Unknown), minor code: 7 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3038, resource id: 75497764, major code: 4 (DestroyWindow), minor code: 0 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3161, resource id: 75497772, major code: 61 (ClearArea), minor code: 0 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 143 (Unknown), sequence: 3162, resource id: 75497774, major code: 139 (Unknown), minor code: 8 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3163, resource id: 75497772, major code: 10 (UnmapWindow), minor code: 0 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 143 (Unknown), sequence: 3167, resource id: 75497774, major code: 139 (Unknown), minor code: 7 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3173, resource id: 75497772, major code: 4 (DestroyWindow), minor code: 0 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3293, resource id: 75497785, major code: 10 (UnmapWindow), minor code: 0 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 143 (Unknown), sequence: 3297, resource id: 75497787, major code: 139 (Unknown), minor code: 7 Aug 03 12:53:04 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3303, resource id: 75497785, major code: 4 (DestroyWindow), minor code: 0 Aug 03 12:53:32 kernel: usb 1-1: USB disconnect, device number 8 Aug 03 12:53:32 kernel: usb 1-1.1: USB disconnect, device number 13 Aug 03 12:53:32 kernel: usb 1-1.2: USB disconnect, device number 15 Aug 03 12:53:32 kernel: usb 1-1.3: USB disconnect, device number 14 Aug 03 12:53:32 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3432, resource id: 75497798, major code: 10 (UnmapWindow), minor code: 0 Aug 03 12:53:32 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 143 (Unknown), sequence: 3436, resource id: 75497800, major code: 139 (Unknown), minor code: 7 Aug 03 12:53:32 keepassxc[25631]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3442, resource id: 75497798, major code: 4 (DestroyWindow), minor code: 0 Aug 03 12:53:32 blueberry-tray[91290]: GdkWindow 0x800002 unexpectedly destroyed Aug 03 12:53:32 blueberry-tray[91290]: The program 'blueberry-tray.py' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 303 error_code 143 request_code 139 (RENDER) minor_code 7) (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 GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Aug 03 12:53:32 audit[91290]: ANOM_ABEND auid=1000 uid=1000 gid=985 ses=2 pid=91290 comm="blueberry-tray" exe="/usr/bin/python3.8" sig=5 res=1 Aug 03 12:53:32 systemd[866]: blueberry-tray.service: Main process exited, code=dumped, status=5/TRAP Aug 03 12:53:32 kernel: traps: blueberry-tray[91290] trap int3 ip:7f9b267c4314 sp:7ffeb92b67e0 error:0 in libglib-2.0.so.0.6400.4[7f9b26785000+85000] Aug 03 12:53:32 kernel: audit: type=1701 audit(1596473612.775:478): auid=1000 uid=1000 gid=985 ses=2 pid=91290 comm="blueberry-tray" exe="/usr/bin/python3.8" sig=5 res=1 Aug 03 12:53:32 systemd[866]: blueberry-tray.service: Failed with result 'core-dump'. Aug 03 12:53:33 systemd[866]: blueberry-tray.service: Scheduled restart job, restart counter is at 10. Aug 03 12:53:34 systemd-logind[454]: System docked. Aug 03 12:53:34 kernel: dell_wmi: Unknown key with type 0x0000 and code 0xe070 pressed xrandr commands: xrandr --output HDMI1 --off --output VIRTUAL1 --off --output DP1 --off --output eDP1 --primary --mode 1920x1080 --pos 0x0 --rotate normal --output DP2 --off xrandr --output HDMI1 --off --output VIRTUAL1 --off --output DP1 --primary --mode 1920x1080 --pos 0x0 --rotate normal --output eDP1 --mode 1920x1080 --pos 1920x0 --rotate normal --output DP2 --off Steps to reproduce: Open hexchat or another affected application Connect, disconnect, enable, or disable an external display Application crashes |
This task depends upon
Closed by freswa (frederik)
Tuesday, 04 August 2020, 17:22 GMT
Reason for closing: Not a bug
Additional comments about closing: This is not a packaging bug. Please ask in the forum, the IRC or the ML for help to figure out the root cause.
Thank you :)
Tuesday, 04 August 2020, 17:22 GMT
Reason for closing: Not a bug
Additional comments about closing: This is not a packaging bug. Please ask in the forum, the IRC or the ML for help to figure out the root cause.
Thank you :)