Bug 810465

Summary: [abrt] gnome-applet-alarm-clock-0.3.2-1.fc16: Process /usr/bin/alarm-clock-applet was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: ccc2007chaos
Component: gnome-applet-alarm-clockAssignee: Christoph Wickert <cwickert>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: cwickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:1e88e6a56e289580112aaefd62e28d0a1f00062c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 13:22:50 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: dso_list
none
File: build_ids
none
File: maps
none
File: backtrace none

Description ccc2007chaos 2012-04-06 09:35:27 UTC
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        alarm-clock-applet
executable:     /usr/bin/alarm-clock-applet
kernel:         3.3.0-8.fc16.i686
pid:            3578
pwd:            /home/marios
reason:         Process /usr/bin/alarm-clock-applet was killed by signal 6 (SIGABRT)
time:           Mon 02 Apr 2012 15:15:35 EEST
uid:            1000
username:       marios

backtrace:      Text file, 27890 bytes
build_ids:      Text file, 4305 bytes
dso_list:       Text file, 9876 bytes
maps:           Text file, 30510 bytes

environ:
:XDG_VTNR=2
:XDG_SESSION_ID=4
:SSH_AGENT_PID=2840
:HOSTNAME=laptop.lan
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:TERM=dumb
:SHELL=/bin/bash
:HISTSIZE=1000
:XDG_SESSION_COOKIE=a1a439c5f3d707da8226cf5b00000011-1333346313.381145-674533435
:QTDIR=/usr/lib/qt-3.3
:GNOME_KEYRING_CONTROL=/tmp/keyring-ers2Dq
:QTINC=/usr/lib/qt-3.3/include
:IMSETTINGS_MODULE=none
:USER=marios
:SSH_AUTH_SOCK=/tmp/keyring-ers2Dq/ssh
:USERNAME=marios
:MAIL=/var/spool/mail/marios
:DESKTOP_SESSION=compiz-gnome
:PATH=/usr/java/default/bin:/usr/lib/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/marios/.local/bin:/home/marios/bin
:QT_IM_MODULE=xim
:PWD=/home/marios
:JAVA_HOME=/usr/java/default
:XMODIFIERS=@im=none
:KDE_IS_PRELINKED=1
:LANG=en_US.utf8
:GNOME_KEYRING_PID=2693
:GDM_LANG=en_US.utf8
:KDEDIRS=/usr
:GDMSESSION=compiz-gnome
:SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
:HISTCONTROL=ignoredups
:SHLVL=1
:XDG_SEAT=seat0
:HOME=/home/marios
:LOGNAME=marios
:QTLIB=/usr/lib/qt-3.3/lib
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-u8wH8JOSzP,guid=88278a184fb7f955022dd19c0000066f
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=2
:DISPLAY=:0.0
:XDG_RUNTIME_DIR=/run/user/marios
:XAUTHORITY=/var/run/gdm/auth-for-marios-zVDBUv/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/2699,unix/unix:/tmp/.ICE-unix/2699
:GPG_AGENT_INFO=/tmp/keyring-ers2Dq/gpg:0:1
:LC_TIME=en_GB.utf8
:LC_NUMERIC=en_GB.utf8
:LC_MONETARY=en_GB.utf8
:LC_MEASUREMENT=en_GB.utf8
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/alarm-clock-applet.desktop
:GIO_LAUNCHED_DESKTOP_FILE_PID=3578

var_log_messages:
:Apr  2 15:15:35 laptop abrt[9700]: File '/usr/bin/alarm-clock-applet' seems to be deleted
:Apr  2 15:15:37 laptop abrt[9700]: Saved core dump of pid 3578 (/usr/bin/alarm-clock-applet) to /var/spool/abrt/ccpp-2012-04-02-15:15:35-3578 (50135040 bytes)

Comment 1 ccc2007chaos 2012-04-06 09:35:32 UTC
Created attachment 575683 [details]
File: dso_list

Comment 2 ccc2007chaos 2012-04-06 09:35:35 UTC
Created attachment 575684 [details]
File: build_ids

Comment 3 ccc2007chaos 2012-04-06 09:35:39 UTC
Created attachment 575685 [details]
File: maps

Comment 4 ccc2007chaos 2012-04-06 09:35:42 UTC
Created attachment 575686 [details]
File: backtrace

Comment 5 Christoph Wickert 2012-04-06 09:41:47 UTC
Thanks for submitting this crash report. Do you remember what you did when the applet crashed? Are you able to reproduce the crash reliably?

Comment 6 ccc2007chaos 2012-04-06 14:13:01 UTC
(In reply to comment #5)
> Thanks for submitting this crash report. Do you remember what you did when the
> applet crashed? Are you able to reproduce the crash reliably?

I really don't remember anything more than that it just crashed. I only saw the ABTR report of the bug but I couldn't find out what happened.

Comment 7 Fedora End Of Life 2013-01-16 12:49:06 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 8 Fedora End Of Life 2013-02-13 13:22:52 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.