Bug 1380505

Summary: [abrt] gnome-shell: up_exported_daemon_get_lid_is_closed(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Nuno <amado86>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: fmuellner, mikhail.rokhin, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/967e91cdb82af62681ed1ad660f25a061b1da1db
Whiteboard: abrt_hash:86a40b5610e511c7b7135321756a183e22ba13b8;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:07:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Nuno 2016-09-29 19:11:52 UTC
Description of problem:
Happened during logon

Version-Release number of selected component:
gnome-shell-3.22.0-1.fc25

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: up_exported_daemon_get_lid_is_closed
executable:     /usr/bin/gnome-shell
global_pid:     1080
kernel:         4.8.0-0.rc8.git0.1.fc25.i686+PAE
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 up_exported_daemon_get_lid_is_closed at up-daemon-generated.c:747
 #1 up_client_get_lid_is_closed at up-client.c:208
 #2 meta_monitor_config_init at backends/meta-monitor-config.c:264
 #3 g_type_create_instance at gtype.c:1866
 #4 g_object_new_internal at gobject.c:1783
 #7 meta_monitor_config_new at backends/meta-monitor-config.c:807
 #8 meta_monitor_manager_constructed at backends/meta-monitor-manager.c:325
 #9 g_object_new_internal at gobject.c:1823
 #12 meta_backend_native_create_monitor_manager at backends/native/meta-backend-native.c:277
 #13 create_monitor_manager at backends/meta-backend.c:275

Potential duplicate: bug 1322119

Comment 1 Nuno 2016-09-29 19:11:57 UTC
Created attachment 1206023 [details]
File: backtrace

Comment 2 Nuno 2016-09-29 19:11:58 UTC
Created attachment 1206024 [details]
File: cgroup

Comment 3 Nuno 2016-09-29 19:12:00 UTC
Created attachment 1206025 [details]
File: core_backtrace

Comment 4 Nuno 2016-09-29 19:12:01 UTC
Created attachment 1206026 [details]
File: dso_list

Comment 5 Nuno 2016-09-29 19:12:02 UTC
Created attachment 1206027 [details]
File: environ

Comment 6 Nuno 2016-09-29 19:12:04 UTC
Created attachment 1206028 [details]
File: exploitable

Comment 7 Nuno 2016-09-29 19:12:05 UTC
Created attachment 1206029 [details]
File: limits

Comment 8 Nuno 2016-09-29 19:12:07 UTC
Created attachment 1206030 [details]
File: maps

Comment 9 Nuno 2016-09-29 19:12:08 UTC
Created attachment 1206031 [details]
File: mountinfo

Comment 10 Nuno 2016-09-29 19:12:10 UTC
Created attachment 1206032 [details]
File: namespaces

Comment 11 Nuno 2016-09-29 19:12:11 UTC
Created attachment 1206033 [details]
File: open_fds

Comment 12 Nuno 2016-09-29 19:12:12 UTC
Created attachment 1206034 [details]
File: proc_pid_status

Comment 13 Nuno 2016-09-29 19:12:13 UTC
Created attachment 1206035 [details]
File: var_log_messages

Comment 14 M_M 2017-02-21 19:13:33 UTC
Similar problem has been detected:

Failure after 'dnf update' and reboot

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: up_exported_daemon_get_lid_is_closed
executable:     /usr/bin/gnome-shell
global_pid:     1263
kernel:         4.9.10-200.fc25.x86_64
package:        gnome-shell-3.22.3-1.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            42

Comment 15 Fedora End Of Life 2017-11-16 14:39:09 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 16 Fedora End Of Life 2017-12-12 10:07:14 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.