RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1069638 - [abrt] gnome-shell: g_wakeup_new(): gnome-shell killed by SIGTRAP
Summary: [abrt] gnome-shell: g_wakeup_new(): gnome-shell killed by SIGTRAP
Keywords:
Status: CLOSED DUPLICATE of bug 1030948
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.0
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard: abrt_hash:6084e63f9e94fa2f58b04723f6e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-25 12:50 UTC by Alois Mahdal
Modified: 2014-02-25 18:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-25 18:22:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
File: backtrace (100.94 KB, text/plain)
2014-02-25 12:50 UTC, Alois Mahdal
no flags Details
File: cgroup (168 bytes, text/plain)
2014-02-25 12:50 UTC, Alois Mahdal
no flags Details
File: core_backtrace (32.12 KB, text/plain)
2014-02-25 12:50 UTC, Alois Mahdal
no flags Details
File: dso_list (21.13 KB, text/plain)
2014-02-25 12:50 UTC, Alois Mahdal
no flags Details
File: environ (2.61 KB, text/plain)
2014-02-25 12:50 UTC, Alois Mahdal
no flags Details
File: limits (1.29 KB, text/plain)
2014-02-25 12:50 UTC, Alois Mahdal
no flags Details
File: maps (99.90 KB, text/plain)
2014-02-25 12:51 UTC, Alois Mahdal
no flags Details
File: open_fds (68.05 KB, text/plain)
2014-02-25 12:51 UTC, Alois Mahdal
no flags Details
File: proc_pid_status (1.06 KB, text/plain)
2014-02-25 12:51 UTC, Alois Mahdal
no flags Details
File: var_log_messages (39.67 KB, text/plain)
2014-02-25 12:51 UTC, Alois Mahdal
no flags Details

Description Alois Mahdal 2014-02-25 12:50:28 UTC
Description of problem:
This happened after installing tigervnc-1.2.80-0.23.20130314svn5065.el7.x86_64
on RHEL7 server with @desktop, launching `vncserver` under admin (ordinary user)
and connecting toi the (:1) session from within active GNOME session.

Note that I started the VNC server via SSH, using ssh root@host, then `su admin` (i.e. non-login) and finally `vncserver`.

This brought system into state when multiple gnome-shell processes were started, `top` showing that one of them eating up to 79% CPU.  This went on until I killed the VNC server (`vncserver -kill :1`). During the state, 3 crashes of gnome-session were reported (3 crashes early on---delaying the `vncserver -kill` did not result in more crashes).

Version-Release number of selected component:
gnome-shell-3.8.4-22.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: g_wakeup_new
executable:     /usr/bin/gnome-shell
kernel:         3.10.0-86.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_wakeup_new at gwakeup.c:163
 #3 g_main_context_new at gmain.c:614
 #4 g_dbus_connection_send_message_with_reply_sync at gdbusconnection.c:2227
 #5 g_dbus_connection_call_sync_internal at gdbusconnection.c:5564
 #6 g_dbus_connection_call_sync at gdbusconnection.c:5790
 #7 ffi_call_unix64 at ../src/x86/unix64.S:76
 #8 ffi_call at ../src/x86/ffi64.c:522
 #9 gjs_invoke_c_function at gi/function.c:893
 #10 function_call at gi/function.c:1202
 #11 CallJSNative at jscntxtinlines.h:701

Comment 1 Alois Mahdal 2014-02-25 12:50:32 UTC
Created attachment 867387 [details]
File: backtrace

Comment 2 Alois Mahdal 2014-02-25 12:50:34 UTC
Created attachment 867388 [details]
File: cgroup

Comment 3 Alois Mahdal 2014-02-25 12:50:37 UTC
Created attachment 867389 [details]
File: core_backtrace

Comment 4 Alois Mahdal 2014-02-25 12:50:39 UTC
Created attachment 867390 [details]
File: dso_list

Comment 5 Alois Mahdal 2014-02-25 12:50:41 UTC
Created attachment 867391 [details]
File: environ

Comment 6 Alois Mahdal 2014-02-25 12:50:43 UTC
Created attachment 867393 [details]
File: limits

Comment 7 Alois Mahdal 2014-02-25 12:51:03 UTC
Created attachment 867394 [details]
File: maps

Comment 8 Alois Mahdal 2014-02-25 12:51:07 UTC
Created attachment 867395 [details]
File: open_fds

Comment 9 Alois Mahdal 2014-02-25 12:51:13 UTC
Created attachment 867396 [details]
File: proc_pid_status

Comment 10 Alois Mahdal 2014-02-25 12:51:17 UTC
Created attachment 867397 [details]
File: var_log_messages

Comment 12 Alois Mahdal 2014-02-25 16:01:30 UTC
Bugzilla returned 400 when abrt was uploading attachments to this bug, so to make sure nothing is lost, I've uploaded the whole problem dir to our scratch space:

http://nfs.englab.brq.redhat.com/scratch/amahdal/bug.rh/1069638/ccpp-20140225-061312-3737.tar.gz

Comment 13 Alois Mahdal 2014-02-25 16:24:34 UTC
I have realized that the tigervnc build is probably incompatible (at least the module in tigervnc-server-module has different ABI than the X server).

I have installed the RPMs manually so it's most probably not a valid test case.

Comment 14 Matthias Clasen 2014-02-25 18:22:23 UTC
Looks like the same issue as bug 1030948

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


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