Bug 1218003 - [abrt] control-center: update_sensitivity(): gnome-control-center killed by SIGSEGV
Summary: [abrt] control-center: update_sensitivity(): gnome-control-center killed by S...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 21
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:175c96583a1065db418b6c69d34...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-04 00:30 UTC by Joachim Frieben
Modified: 2015-12-02 19:53 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 19:52:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (60.03 KB, text/plain)
2015-05-04 00:30 UTC, Joachim Frieben
no flags Details
File: cgroup (190 bytes, text/plain)
2015-05-04 00:30 UTC, Joachim Frieben
no flags Details
File: core_backtrace (16.02 KB, text/plain)
2015-05-04 00:30 UTC, Joachim Frieben
no flags Details
File: dso_list (26.21 KB, text/plain)
2015-05-04 00:30 UTC, Joachim Frieben
no flags Details
File: environ (1.25 KB, text/plain)
2015-05-04 00:30 UTC, Joachim Frieben
no flags Details
File: exploitable (82 bytes, text/plain)
2015-05-04 00:30 UTC, Joachim Frieben
no flags Details
File: limits (1.29 KB, text/plain)
2015-05-04 00:30 UTC, Joachim Frieben
no flags Details
File: maps (125.09 KB, text/plain)
2015-05-04 00:30 UTC, Joachim Frieben
no flags Details
File: open_fds (1.56 KB, text/plain)
2015-05-04 00:30 UTC, Joachim Frieben
no flags Details
File: proc_pid_status (946 bytes, text/plain)
2015-05-04 00:30 UTC, Joachim Frieben
no flags Details
disconnect signals (3.20 KB, patch)
2015-05-28 09:18 UTC, Martin Hatina
no flags Details | Diff

Description Joachim Frieben 2015-05-04 00:30:11 UTC
Version-Release number of selected component:
control-center-3.14.4-2.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        gnome-control-center --overview
crash_function: update_sensitivity
executable:     /usr/bin/gnome-control-center
kernel:         3.19.5-200.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
var_log_messages: [System Logs]:\n-- Logs begin at Sun 2015-05-03 12:13:39 CEST, end at Sun 2015-05-03 23:32:54 CEST. --

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 update_sensitivity at cc-printers-panel.c:2562
 #6 g_object_notify_queue_thaw at gobject.c:290
 #7 g_object_thaw_notify at gobject.c:1293
 #8 g_permission_impl_update at gpermission.c:358
 #9 process_result at polkitpermission.c:512
 #10 changed_check_cb at polkitpermission.c:456
 #11 g_simple_async_result_complete at gsimpleasyncresult.c:763
 #12 check_authorization_cb at polkitauthority.c:835
 #13 g_simple_async_result_complete at gsimpleasyncresult.c:763
 #14 reply_cb at gdbusproxy.c:2623

Potential duplicate: bug 965422

Comment 1 Joachim Frieben 2015-05-04 00:30:15 UTC
Created attachment 1021435 [details]
File: backtrace

Comment 2 Joachim Frieben 2015-05-04 00:30:16 UTC
Created attachment 1021436 [details]
File: cgroup

Comment 3 Joachim Frieben 2015-05-04 00:30:18 UTC
Created attachment 1021437 [details]
File: core_backtrace

Comment 4 Joachim Frieben 2015-05-04 00:30:20 UTC
Created attachment 1021438 [details]
File: dso_list

Comment 5 Joachim Frieben 2015-05-04 00:30:21 UTC
Created attachment 1021439 [details]
File: environ

Comment 6 Joachim Frieben 2015-05-04 00:30:23 UTC
Created attachment 1021440 [details]
File: exploitable

Comment 7 Joachim Frieben 2015-05-04 00:30:24 UTC
Created attachment 1021441 [details]
File: limits

Comment 8 Joachim Frieben 2015-05-04 00:30:28 UTC
Created attachment 1021442 [details]
File: maps

Comment 9 Joachim Frieben 2015-05-04 00:30:29 UTC
Created attachment 1021443 [details]
File: open_fds

Comment 10 Joachim Frieben 2015-05-04 00:30:31 UTC
Created attachment 1021444 [details]
File: proc_pid_status

Comment 11 Martin Hatina 2015-05-27 09:50:03 UTC
Hi, can you post a steps to reproduce the problem, please?

Comment 12 Joachim Frieben 2015-05-27 11:27:53 UTC
Sorry, I have no memory of the circumstances of this incident.

Comment 13 Martin Hatina 2015-05-28 09:18:37 UTC
Created attachment 1031122 [details]
disconnect signals

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

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 21 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 15 Jan Kurik 2015-12-02 19:53:02 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.