Bug 699115 - [abrt] control-center-3.0.0.1-3.fc15: renew_subscription: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
Summary: [abrt] control-center-3.0.0.1-3.fc15: renew_subscription: Process /usr/bin/gn...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0bfc23aae1291f882ae4dfd9faf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-23 09:15 UTC by Mark Watts
Modified: 2011-06-01 18:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-29 16:09:01 UTC
Type: ---


Attachments (Terms of Use)
File: event_log (20.09 KB, text/plain)
2011-04-23 09:15 UTC, Mark Watts
no flags Details
File: build_ids (7.61 KB, text/plain)
2011-04-23 09:15 UTC, Mark Watts
no flags Details
File: dsos (53.61 KB, text/plain)
2011-04-23 09:15 UTC, Mark Watts
no flags Details
File: maps (68.56 KB, text/plain)
2011-04-23 09:15 UTC, Mark Watts
no flags Details
File: backtrace (23.51 KB, text/plain)
2011-04-23 09:15 UTC, Mark Watts
no flags Details

Description Mark Watts 2011-04-23 09:15:25 UTC
abrt version: 2.0.1
uid: 500
cmdline: gnome-control-center datetime
component: control-center
executable: /usr/bin/gnome-control-center
crash_function: renew_subscription
kernel: 2.6.38.2-9.fc15.x86_64
package: control-center-3.0.0.1-3.fc15
reason: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
architecture: x86_64
username: mwatts
os_release: Fedora release 15 (Lovelock)
time: 1303504718
rating: 4

Text file: event_log, 20573 bytes
Text file: build_ids, 7790 bytes
Binary file: coredump, 42762240 bytes
Text file: dsos, 54900 bytes
Text file: maps, 70201 bytes
Text file: backtrace, 24077 bytes

environ
-----
XDG_SESSION_ID=1
HOSTNAME=samantha.eris.qinetiq.com
IMSETTINGS_INTEGRATE_DESKTOP=yes
SHELL=/bin/bash
TERM=dumb
HISTSIZE=1000
XDG_SESSION_COOKIE=24ebb639d4a741dd4078b0f800000008-1303492830.707732-1354080996
IMSETTINGS_MODULE=none
USER=mwatts
USERNAME=mwatts
MAIL=/var/spool/mail/mwatts
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/mwatts/bin
DESKTOP_SESSION=gnome
QT_IM_MODULE=xim
PWD=/home/mwatts
XMODIFIERS=@im=none
LANG=en_US.utf8
GDM_LANG=en_US.utf8
GDMSESSION=gnome
HISTCONTROL=ignoredups
HOME=/home/mwatts
SHLVL=1
LOGNAME=mwatts
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-SI5eAo1AxS,guid=193f7d481b6355a92a331dd70000000b
'LESSOPEN=||/usr/bin/lesspipe.sh %s'
WINDOWPATH=1
XDG_RUNTIME_DIR=/run/user/mwatts
DISPLAY=:0
G_BROKEN_FILENAMES=1
XAUTHORITY=/var/run/gdm/auth-for-mwatts-shtsLU/database
_=/usr/bin/gnome-session
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1104,unix/unix:/tmp/.ICE-unix/1104
ORBIT_SOCKETDIR=/tmp/orbit-mwatts
GNOME_KEYRING_CONTROL=/tmp/keyring-pEVJUB
GPG_AGENT_INFO=/tmp/keyring-pEVJUB/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-pEVJUB/ssh
GJS_DEBUG_OUTPUT=stderr
'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
DESKTOP_STARTUP_ID=gnome-shell-1294-samantha.eris.qinetiq.com-gnome-control-center-11_TIME11260747
GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/gnome-datetime-panel.desktop
GIO_LAUNCHED_DESKTOP_FILE_PID=15498

Comment 1 Mark Watts 2011-04-23 09:15:28 UTC
Created attachment 494389 [details]
File: event_log

Comment 2 Mark Watts 2011-04-23 09:15:31 UTC
Created attachment 494390 [details]
File: build_ids

Comment 3 Mark Watts 2011-04-23 09:15:34 UTC
Created attachment 494391 [details]
File: dsos

Comment 4 Mark Watts 2011-04-23 09:15:37 UTC
Created attachment 494392 [details]
File: maps

Comment 5 Mark Watts 2011-04-23 09:15:40 UTC
Created attachment 494393 [details]
File: backtrace

Comment 7 Sitsofe Wheeler 2011-06-01 18:52:24 UTC
Is this really fixed? I seemingly had this crash with control-center-3.0.1.1-5.fc15.x86_64 which apparently has the above patch in it...


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