Bug 887752 - [abrt] gnome-shell-3.6.2-5.fc18: _gdk_x11_display_error_event: Process /usr/bin/gnome-shell was killed by signal 5 (SIGTRAP)
Summary: [abrt] gnome-shell-3.6.2-5.fc18: _gdk_x11_display_error_event: Process /usr/b...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f6f60f87bb7b96bcf8be703ec91...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-17 09:06 UTC by bobpoljakov
Modified: 2015-06-29 11:43 UTC (History)
38 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 11:43:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (48.44 KB, text/plain)
2012-12-17 09:06 UTC, bobpoljakov
no flags Details
File: cgroup (127 bytes, text/plain)
2012-12-17 09:06 UTC, bobpoljakov
no flags Details
File: core_backtrace (2.11 KB, text/plain)
2012-12-17 09:06 UTC, bobpoljakov
no flags Details
File: dso_list (22.90 KB, text/plain)
2012-12-17 09:06 UTC, bobpoljakov
no flags Details
File: environ (1.41 KB, text/plain)
2012-12-17 09:06 UTC, bobpoljakov
no flags Details
File: limits (1.29 KB, text/plain)
2012-12-17 09:06 UTC, bobpoljakov
no flags Details
File: maps (119.83 KB, text/plain)
2012-12-17 09:06 UTC, bobpoljakov
no flags Details
File: open_fds (1.40 KB, text/plain)
2012-12-17 09:06 UTC, bobpoljakov
no flags Details
File: proc_pid_status (939 bytes, text/plain)
2012-12-17 09:06 UTC, bobpoljakov
no flags Details
File: var_log_messages (1.76 KB, text/plain)
2012-12-17 09:06 UTC, bobpoljakov
no flags Details

Description bobpoljakov 2012-12-17 09:06:00 UTC
Description of problem:
1. Started a search in evolution (search type: body contains)
2. Killed evolution, problem solved

Version-Release number of selected component:
gnome-shell-3.6.2-5.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: _gdk_x11_display_error_event
executable:     /usr/bin/gnome-shell
kernel:         3.6.10-5.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2416
 #6 handle_error at xcb_io.c:212
 #7 handle_response at xcb_io.c:324
 #10 after_process_all_updates at gdkwindow.c:4135
 #11 gdk_window_process_all_updates at gdkwindow.c:4208
 #12 gdk_window_update_idle at gdkwindow.c:3815
 #18 meta_run at core/main.c:545

Potential duplicate: bug 743586

Comment 1 bobpoljakov 2012-12-17 09:06:08 UTC
Created attachment 664730 [details]
File: backtrace

Comment 2 bobpoljakov 2012-12-17 09:06:11 UTC
Created attachment 664731 [details]
File: cgroup

Comment 3 bobpoljakov 2012-12-17 09:06:14 UTC
Created attachment 664732 [details]
File: core_backtrace

Comment 4 bobpoljakov 2012-12-17 09:06:16 UTC
Created attachment 664733 [details]
File: dso_list

Comment 5 bobpoljakov 2012-12-17 09:06:19 UTC
Created attachment 664734 [details]
File: environ

Comment 6 bobpoljakov 2012-12-17 09:06:21 UTC
Created attachment 664735 [details]
File: limits

Comment 7 bobpoljakov 2012-12-17 09:06:25 UTC
Created attachment 664736 [details]
File: maps

Comment 8 bobpoljakov 2012-12-17 09:06:28 UTC
Created attachment 664737 [details]
File: open_fds

Comment 9 bobpoljakov 2012-12-17 09:06:31 UTC
Created attachment 664738 [details]
File: proc_pid_status

Comment 10 bobpoljakov 2012-12-17 09:06:34 UTC
Created attachment 664739 [details]
File: var_log_messages

Comment 11 thomas.michel 2012-12-31 10:12:18 UTC
I was using remmina to connect to a windows PC. When logging off of the Windows PC, gnome shell crashed.

backtrace_rating: 4
Package: gnome-shell-3.6.2-6.fc18
OS Release: Fedora release 18 (Spherical Cow)

Comment 12 Martin Bengtsson 2013-02-19 13:17:39 UTC
adding a displaylink usb dock and used xrandr:

xrandr --output DVI-1 --off

related to Problem 366271


backtrace_rating: 4
Package: gnome-shell-3.6.3-2.fc18
OS Release: Fedora release 18 (Spherical Cow)

Comment 13 hrafnkellbrimar 2013-03-01 00:12:14 UTC
I tried to resize a Remmina window during rdp session, then Gnome Shell crashed.

backtrace_rating: 4
Package: gnome-shell-3.6.3-2.fc18
Architecture: i686
OS Release: Fedora release 18 (Spherical Cow)

Comment 14 ThanhNT 2013-03-22 16:44:14 UTC
I don't known

backtrace_rating: 4
Package: gnome-shell-3.6.3.1-1.fc18
OS Release: Fedora release 18 (Spherical Cow)

Comment 15 smitna 2013-05-18 06:29:17 UTC
From Remmina, I pressed the "Resize the window to fit in remote resolution" button.
VNC connection tunnelled over ssh.

backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: _gdk_x11_display_error_event
executable:     /usr/bin/gnome-shell
kernel:         3.9.2-200.fc18.i686.PAE
package:        gnome-shell-3.6.3.1-1.fc18
reason:         Process /usr/bin/gnome-shell was killed by signal 5 (SIGTRAP)
uid:            1000
ureports_counter: 1
xsession_errors: (gnome-shell:2788): Clutter-WARNING **: Actor '<searchEntry>[<StEntry>:0x9714048]' should not be mapped if parent '<overview>[<StWidget>:0x94d45d0]'is not visible

Comment 16 david sutherland 2013-10-15 04:44:17 UTC
Was watching you-tube video when the it stopped and the operating system froze 

reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        gnome-shell --sm-client-id 10e985ddac28b2ceed137677430923445500000010350000
crash_function: _gdk_x11_display_error_event
executable:     /usr/bin/gnome-shell
kernel:         3.10.12-100.fc18.x86_64
package:        gnome-shell-3.6.3.1-2.fc18
reason:         Process /usr/bin/gnome-shell was killed by signal 5 (SIGTRAP)
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 17 Fedora End Of Life 2013-12-21 09:56:30 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 18 Kevin R. Page 2014-01-15 21:23:28 UTC
Detected on Fedora 20, gnome-shell-3.10.2.1-3.fc20

https://retrace.fedoraproject.org/faf/reports/39822/

Please update Version to Fedora 20.

Comment 19 31ui|\| 2014-01-22 14:25:27 UTC
gnome 3 crashed while pluging USB Mouse into my USB 3.0 port. still not fixed in Fedora 20 as others have previously stated

Comment 20 F.Prates 2014-01-31 09:30:52 UTC
Another user experienced a similar problem:

when i hit the keyboard disable touchpad key at first, gnome-shell restart itself, notifying me a crash has just happened.

further iterations don't trigger the problem for that session.

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: _gdk_x11_display_error_event
executable:     /usr/bin/gnome-shell
kernel:         3.12.8-300.fc20.x86_64
package:        gnome-shell-3.10.3-2.fc20
reason:         gnome-shell killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 21 cyplo 2014-06-09 18:40:48 UTC
Another user experienced a similar problem:

On the launch of a Steam game -  Shadowrun.
Did not happen before, most probably recent yum upgrade broke something.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: _gdk_x11_display_error_event
executable:     /usr/bin/gnome-shell
kernel:         3.14.5-200.fc20.x86_64
package:        gnome-shell-3.10.4-5.fc20
reason:         gnome-shell killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 22 Dario Castellarin 2014-06-19 16:52:37 UTC
Another user experienced a similar problem:

I was playing The Fall game from Steam, not sure if related though.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: _gdk_x11_display_error_event
executable:     /usr/bin/gnome-shell
kernel:         3.14.8-200.fc20.x86_64
package:        gnome-shell-3.10.4-5.fc20
reason:         gnome-shell killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 23 Joel Burleson-Davis 2014-09-08 17:18:26 UTC
Another user experienced a similar problem:

This error pops up semi-randomly on login from gdm.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: _gdk_x11_display_error_event
executable:     /usr/bin/gnome-shell
kernel:         3.15.10-201.fc20.x86_64
package:        gnome-shell-3.10.4-8.fc20
reason:         gnome-shell killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            226001113

Comment 24 Philipp Gampe 2014-11-03 16:14:06 UTC
Happens if I try to suspens the notebook (which fails, because of nouveau).

I use a multi-monitor setup which is very likely to be related to this problem, because it does not happen without configuring the external Monitor.

I my external monitor is attached to a KVM switch, which is attached to my docking holding my notebook.

If my minitor is powered off (power switch) while it was powered on before I suspended my notebook, the Gnome Shell crashes. The crash is only shown on the external monitor and the notebook screen stays blank.

Comment 25 Philipp Gampe 2014-11-03 16:28:34 UTC
Another user experienced a similar problem:

I use a multi-monitor setup with a notebook, where the external monitor is not always powered on, but appears to be active, because it is attached to KVM.
This leads to a crash after un-suspending the notebook.

The same happens if I remove the notebook from the dockin, while is notebook is in suspend mode.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: _gdk_x11_display_error_event
executable:     /usr/bin/gnome-shell
kernel:         3.16.4-200.fc20.x86_64
package:        gnome-shell-3.10.4-9.fc20
reason:         gnome-shell killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 26 Fedora End Of Life 2015-05-29 08:49:46 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 27 Fedora End Of Life 2015-06-29 11:43:01 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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