Bug 771826 - [abrt] control-center-3.2.2-1.fc16: Process /usr/bin/gnome-control-center was killed by signal 6 (SIGABRT)
Summary: [abrt] control-center-3.2.2-1.fc16: Process /usr/bin/gnome-control-center was...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk3
Version: 16
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2de25def11f62d099a0395bafb2...
: 708654 767423 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-05 06:53 UTC by Per Sandberg
Modified: 2013-02-13 18:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 18:20:09 UTC
Type: ---


Attachments (Terms of Use)
File: dso_list (19.19 KB, text/plain)
2012-01-05 06:54 UTC, Per Sandberg
no flags Details
File: build_ids (8.21 KB, text/plain)
2012-01-05 06:54 UTC, Per Sandberg
no flags Details
File: maps (56.01 KB, text/plain)
2012-01-05 06:54 UTC, Per Sandberg
no flags Details
File: backtrace (36.15 KB, text/plain)
2012-01-05 06:54 UTC, Per Sandberg
no flags Details

Description Per Sandberg 2012-01-05 06:53:58 UTC
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        gnome-control-center user-accounts
executable:     /usr/bin/gnome-control-center
kernel:         3.1.6-1.fc16.i686.PAE
pid:            4630
pwd:            /home/per
reason:         Process /usr/bin/gnome-control-center was killed by signal 6 (SIGABRT)
time:           Wed 04 Jan 2012 07:17:23 PM CET
uid:            1000
username:       per
var_log_messages: Jan  4 19:17:26 lufsen abrt[4693]: Saved core dump of pid 4630 (/usr/bin/gnome-control-center) to /var/spool/abrt/ccpp-2012-01-04-19:17:23-4630 (185450496 bytes)

backtrace:      Text file, 37020 bytes
build_ids:      Text file, 8407 bytes
dso_list:       Text file, 19647 bytes
maps:           Text file, 57354 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=8
:HOSTNAME=lufsen.sandat.dyndns.org
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=8427510e92244e56565a1bfa0000000c-1325333343.630824-2098183266
:GNOME_KEYRING_CONTROL=/tmp/keyring-3VdU0N
:IMSETTINGS_MODULE=none
:USER=per
:USERNAME=per
:MAIL=/var/spool/mail/per
:PATH=/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/per/.local/bin:/home/per/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/per
:XMODIFIERS=@im=none
:GNOME_KEYRING_PID=4300
:LANG=en_US.UTF-8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/per
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=per
:CVS_RSH=ssh
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-dIveKFcAvg,guid=3213d9d362931cb45ba292db00000740
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/per
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-per-ygFgfX/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/4304,unix/unix:/tmp/.ICE-unix/4304
:SSH_AUTH_SOCK=/tmp/keyring-3VdU0N/ssh
:GPG_AGENT_INFO=/tmp/keyring-3VdU0N/gpg:0:1
:GJS_DEBUG_OUTPUT=stderr
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:DESKTOP_STARTUP_ID=gnome-shell-28013-lufsen.sandat.dyndns.org-gnome-control-center-6_TIME369477804
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/gnome-user-accounts-panel.desktop
:GIO_LAUNCHED_DESKTOP_FILE_PID=4630

Comment 1 Per Sandberg 2012-01-05 06:54:01 UTC
Created attachment 550824 [details]
File: dso_list

Comment 2 Per Sandberg 2012-01-05 06:54:03 UTC
Created attachment 550825 [details]
File: build_ids

Comment 3 Per Sandberg 2012-01-05 06:54:05 UTC
Created attachment 550826 [details]
File: maps

Comment 4 Per Sandberg 2012-01-05 06:54:08 UTC
Created attachment 550827 [details]
File: backtrace

Comment 5 abrt-bot 2012-03-30 11:43:42 UTC
Backtrace analysis of bugs across components suggests the actual bug is in component gtk3 instead of component control-center, reassigning to gtk3.

Bugs which were found to be similar to this bug: 
  rhythmbox: bug #708654
  totem: bug #767423

This comment is automatically generated.

Comment 6 abrt-bot 2012-03-30 11:43:53 UTC
*** Bug 767423 has been marked as a duplicate of this bug. ***

Comment 7 abrt-bot 2012-03-30 11:44:07 UTC
*** Bug 708654 has been marked as a duplicate of this bug. ***

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

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 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Fedora End Of Life 2013-02-13 18:20:12 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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.