Hide Forgot
libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 3 cmdline: /usr/libexec/evolution/3.2/evolution-alarm-notify crash_function: elf_machine_lazy_rel executable: /usr/libexec/evolution/3.2/evolution-alarm-notify kernel: 3.1.2-1.fc16.x86_64 pid: 1926 pwd: /home/artem reason: Process /usr/libexec/evolution/3.2/evolution-alarm-notify was killed by signal 11 (SIGSEGV) time: Ср. 30 нояб. 2011 10:15:33 uid: 1000 username: artem var_log_messages: Nov 30 10:15:34 sipo1 abrt[1939]: Saved core dump of pid 1926 (/usr/libexec/evolution/3.2/evolution-alarm-notify) to /var/spool/abrt/ccpp-2011-11-30-10:15:33-1926 (2256896 bytes) xsession_errors: backtrace: Text file, 84058 bytes dso_list: Text file, 8937 bytes maps: Text file, 36405 bytes smolt_data: Binary file, 3402 bytes environ: :XDG_VTNR=1 :XDG_SESSION_ID=3 :HOSTNAME=sipo1 :IMSETTINGS_INTEGRATE_DESKTOP=yes :SHELL=/bin/bash :TERM=dumb :HISTSIZE=1000 :XDG_SESSION_COOKIE=9675cc8eef0eaec146dbf7bd0000000b-1322633725.994205-1118588223 :GNOME_KEYRING_CONTROL=/tmp/keyring-Lyh3m9 :'IMSETTINGS_MODULE=X compose table' :USER=artem :USERNAME=artem :MAIL=/var/spool/mail/artem :PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/artem/.local/bin:/home/artem/bin :DESKTOP_SESSION=gnome :QT_IM_MODULE=xim :PWD=/home/artem :XMODIFIERS=@im=none :KDE_IS_PRELINKED=1 :GNOME_KEYRING_PID=1670 :LANG=ru_RU.UTF-8 :KDEDIRS=/usr :GDMSESSION=gnome :HISTCONTROL=ignoredups :HOME=/home/artem :XDG_SEAT=seat0 :SHLVL=1 :LOGNAME=artem :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-F6MVhiC6U3,guid=1cc10532c02e2364c7be09e8000001ed :'LESSOPEN=||/usr/bin/lesspipe.sh %s' :WINDOWPATH=1 :XDG_RUNTIME_DIR=/run/user/artem :DISPLAY=:0 :XAUTHORITY=/var/run/gdm/auth-for-artem-rUK4gX/database :_=/usr/bin/gnome-session :GNOME_DESKTOP_SESSION_ID=this-is-deprecated :SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1678,unix/unix:/tmp/.ICE-unix/1678 :GPG_AGENT_INFO=/tmp/keyring-Lyh3m9/gpg:0:1 :SSH_AUTH_SOCK=/tmp/keyring-Lyh3m9/ssh :DESKTOP_AUTOSTART_ID=103f2e7c5c92dc6e0c132263372715517400000016780033
Created attachment 538410 [details] File: dso_list
Created attachment 538411 [details] File: smolt_data
Created attachment 538412 [details] File: maps
Created attachment 538413 [details] File: backtrace
Thanks for a bug report. The crash is quite low in the library, when it's being opened. Maybe the first warning in the backtrace is related to the crash: > warning: core file may not match specified executable file. I'm wondering, can you reproduce the crash when you run the alarm notification daemon manually, from a console, please? You can do that with: $ /usr/libexec/evolution/3.2/evolution-alarm-notify Also, thinking of the above warning, is this reproducible after restart of the machine? I'm wondering whether you did a software update, but the alarm-notify wasn't updated properly, or it was kept in memory during the update, and subsequent run of it broke in this way?
This problem with job kernel from hardware. After - kernel crush with segmentation fault
Thanks for an update. Does it mean it can be closed as NotABug? At least not in evolution, thus either closed or moved to kernel?
Backtrace analysis of bugs across components suggests the actual bug might be in component glibc instead of component evolution. You might want to inspect the backtrace from the bug listed below to find out the correct component. Bug #797421 from component empathy was found to be similar to this bug. This comment is automatically generated.
*** Bug 797421 has been marked as a duplicate of this bug. ***
The given bug is connected with the physical equipment. The system payment doesn't support processors with 125 watts a thermal emission because of a weak power supply system. From here also stability of work, but only in an Unix systems is observed not. In an operating system windows any instability of work it is not observed.
*** Bug 759352 has been marked as a duplicate of this bug. ***
*** Bug 772382 has been marked as a duplicate of this bug. ***
*** Bug 759570 has been marked as a duplicate of this bug. ***
*** Bug 771302 has been marked as a duplicate of this bug. ***
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
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.