Bug 2152722 - Crash when connecting to server, BadWindow from X11, after an update to Fedora
Summary: Crash when connecting to server, BadWindow from X11, after an update to Fedora
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: hexchat
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Patrick Griffis
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-12 19:55 UTC by Pete Zaitcev
Modified: 2023-07-31 20:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-31 20:22:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pete Zaitcev 2022-12-12 19:55:43 UTC
Description of problem:

Hexchat crashes when it tries to display a network list pop-up.

This started happening in the middle of lifecycle for Fedora 36.
So, it's quite likely that the bug is actually not in Hexchat.
But it is the only application affected, and I don't know how
to identify the proper component.

Version-Release number of selected component (if applicable):

[zaitcev@lebethron ~]$ hexchat
Gtk-Message: 13:35:29.853: Failed to load module "pk-gtk-module"

(hexchat:9676): Gdk-ERROR **: 13:35:35.064: 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 3943 error_code 3 request_code 38 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.)
Trace/breakpoint trap (core dumped)


How reproducible:


Steps to Reproduce:
1. Run Hexchat
2. Hit Ctrl-S
3. Select a network, click connect

Actual results:

Crash

Expected results:

Working as usual.

Additional info:

Bug #2105782 may be the same bug, only triggered by ABRT. But surprisingly,
it was reported in July. This only started happening to me now, and I update
regularly. So, it cannot be the same update, and may not be the same bug.

Comment 1 Pete Zaitcev 2023-07-31 20:22:42 UTC
Works in F38.


Note You need to log in before you can comment on or make changes to this bug.