| Summary: | segfault in gdk_x11_window_foreign_new_for_display | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Brian J. Murrell <brian> |
| Component: | gtk3 | Assignee: | Matthias Clasen <mclasen> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | ccecchi, jfilak, mclasen, rdieter |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-05 14:46:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Brian J. Murrell
2013-12-11 16:32:16 UTC
This just hit me in gnome-terminal also:
Program received signal SIGSEGV, Segmentation fault.
gdk_x11_window_foreign_new_for_display (display=display@entry=0x1f0e090,
window=98566148) at gdkwindow-x11.c:1241
1241 gdkwindow-x11.c: No such file or directory.
(gdb) bt
#0 gdk_x11_window_foreign_new_for_display (display=display@entry=0x1f0e090,
window=98566148) at gdkwindow-x11.c:1241
#1 0x000000382b44aa75 in gdk_x11_display_translate_event (
translator=<optimized out>, display=0x1f0e090, event=0x2babdf0,
xevent=0x7fff887e5f10) at gdkdisplay-x11.c:996
#2 0x000000382b44f572 in _gdk_x11_event_translator_translate (
translator=0x1f0e090, display=0x1f0e090,
xevent=xevent@entry=0x7fff887e5f10) at gdkeventtranslator.c:51
#3 0x000000382b44f0fd in gdk_event_source_translate_event (
xevent=0x7fff887e5f10, event_source=0x1ee4460) at gdkeventsource.c:240
#4 _gdk_x11_display_queue_events (display=0x1f0e090) at gdkeventsource.c:338
#5 0x000000382b425e78 in gdk_display_get_event (
display=display@entry=0x1f0e090) at gdkdisplay.c:327
#6 0x000000382b44ed12 in gdk_event_source_dispatch (
source=source@entry=0x1ee4460, callback=<optimized out>,
user_data=<optimized out>) at gdkeventsource.c:360
#7 0x00000038270492a6 in g_main_dispatch (context=0x1ef4c40) at gmain.c:3066
#8 g_main_context_dispatch (context=context@entry=0x1ef4c40) at gmain.c:3642
#9 0x0000003827049628 in g_main_context_iterate (
context=context@entry=0x1ef4c40, block=block@entry=1,
dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3713
#10 0x00000038270496dc in g_main_context_iteration (context=0x1ef4c40,
context@entry=0x0, may_block=may_block@entry=1) at gmain.c:3774
#11 0x0000003827c9c954 in g_application_run (application=0x1f320c0, argc=0,
argv=0x0) at gapplication.c:1635
#12 0x00000000004114df in main ()
And it was running on screen 0, not screen 1. All my terminals gone. :-(
I think I am going to have to revert back to F19 until this is fixed. It's a show-stopper for anyone who has multiple screens I think.
Has anyone had a chance to look at this yet? In particular, is the link to the gtk+ that I posted: https://mail.gnome.org/archives/commits-list/2013-November/msg06825.html the solution, or even relevant? Because if it's the solution, it seems a shame for this issue to stall out but for lack of application of patch that's already been committed upstream. I guess I could try a local build of gtk+ with that patch applied. I just need to find the time to do it. Ahhh. It seems the patch I posted about went into 3.10.4 and my F20 was on 3.10.4 when I had to abandon using it and go back to F19. Now that 3.10.6 is in F20, it might be time for another try. This is fixed in gtk+ 3.10.6 which is in F20 now. |