Red Hat Bugzilla – Bug 804743
[abrt] evolution-3.3.91-1.fc17: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Last modified: 2013-07-31 23:53:24 EDT
libreport version: 2.0.8 abrt_version: 2.0.7 backtrace_rating: 4 cmdline: evolution comment: Was using the system normally, and Shell froze (as it has a propensity to do lately). Switch to a VT and kill -9ed shell (regular kill isn't enough). When I switched back to the X VT, this crash notification showed up after Shell had reloaded. crash_function: _gdk_device_xi2_reset_scroll_valuators executable: /usr/bin/evolution kernel: 3.3.0-0.rc7.git0.3.fc17.x86_64 pid: 19236 pwd: /home/adamw reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) time: Mon 19 Mar 2012 09:52:45 AM PDT uid: 1001 username: adamw backtrace: Text file, 43845 bytes dso_list: Text file, 19223 bytes maps: Text file, 91512 bytes environ: :GIT_PS1_SHOWDIRTYSTATE=true :XDG_VTNR=1 :XDG_SESSION_ID=2 :HOSTNAME=adam.localdomain :IMSETTINGS_INTEGRATE_DESKTOP=yes :SHELL=/bin/bash :TERM=dumb :HISTSIZE=1000 :QTDIR=/usr/lib64/qt-3.3 :GNOME_KEYRING_CONTROL=/tmp/keyring-1Z9IkZ :QTINC=/usr/lib64/qt-3.3/include :IMSETTINGS_MODULE=none :USER=adamw :USERNAME=adamw :MAIL=/var/spool/mail/adamw :PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/adamw/bin :DESKTOP_SESSION=gnome :QT_IM_MODULE=xim :PWD=/home/adamw :XMODIFIERS=@im=none :KDE_IS_PRELINKED=1 :GNOME_KEYRING_PID=1540 :LANG=en_US.utf8 :GDM_LANG=en_US.utf8 :KDEDIRS=/usr :'PS1=[\\[\\e[0;32m\\]\\u\\[\\e[0m\\]@\\[\\e[0;34m\\]\\h\\[\\e[0m\\] \\W\\[\\e[0;33m\\]$(__git_ps1 \" (%s)\")\\[\\e[0m\\]]\\[\\e[0;32m\\]\\$ \\[\\e[0m\\]' :GIT_PS1_SHOWUNTRACKEDFILES=true :GDMSESSION=gnome :SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass :HISTCONTROL=ignoredups :XDG_SEAT=seat0 :HOME=/home/adamw :SHLVL=1 :LOGNAME=adamw :QTLIB=/usr/lib64/qt-3.3/lib :CVS_RSH=ssh :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-lsiONA6EVk,guid=09966dbb64ab557a59069d6000000022 :'LESSOPEN=||/usr/bin/lesspipe.sh %s' :WINDOWPATH=1 :XDG_RUNTIME_DIR=/run/user/adamw :DISPLAY=:0 :XAUTHORITY=/var/run/gdm/auth-for-adamw-qlX0mT/database :_=/usr/bin/gnome-session :GNOME_DESKTOP_SESSION_ID=this-is-deprecated :SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1545,unix/unix:/tmp/.ICE-unix/1545 :GPG_AGENT_INFO=/tmp/keyring-1Z9IkZ/gpg:0:1 :SSH_AUTH_SOCK=/tmp/keyring-1Z9IkZ/ssh :GJS_DEBUG_OUTPUT=stderr :'GJS_DEBUG_TOPICS=JS ERROR;JS LOG' :G_MESSAGES_DEBUG=all :GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/evolution.desktop :GIO_LAUNCHED_DESKTOP_FILE_PID=19236 :DESKTOP_STARTUP_ID=gnome-shell-30239-adam.localdomain-evolution-2_TIME113395556 var_log_messages: :Mar 18 09:14:34 adam abrt[14231]: File '/usr/bin/evolution' seems to be deleted :Mar 19 09:52:45 adam kernel: [114657.575785] evolution[19236]: segfault at 70 ip 0000003e35e3f0d0 sp 00007fff4d4814a8 error 4 in libgdk-3.so.0.318.0[3e35e00000+83000] :Mar 19 09:52:48 adam abrt[21209]: Saved core dump of pid 19236 (/usr/bin/evolution) to /var/spool/abrt/ccpp-2012-03-19-09:52:45-19236 (344637440 bytes) xsession_errors: :evolution-alarm-notify-WARNING **: alarm.c:254: Requested removal of nonexistent alarm! :evolution-shell-Message: Network disconnected. Forced offline. :evolution-shell-Message: Connection established. Going online. :evolution-shell-Message: Network disconnected. Forced offline. :evolution-shell-Message: Connection established. Going online. :evolution-alarm-notify-WARNING **: alarm.c:254: Requested removal of nonexistent alarm! :evolution-shell-Message: Network disconnected. Forced offline. :evolution-shell-Message: Connection established. Going online.
Created attachment 571198 [details] File: dso_list
Created attachment 571199 [details] File: backtrace
Created attachment 571200 [details] File: maps
Thanks for a bug report. I have no idea about GDK internals, but based on the function name _gdk_device_xi2_reset_scroll_valuators (device=0x0) at gdkdevice-xi2.c:862 and the backtrace, where the crashing thread doesn't show anything but main.c from evolution, which simply runs gtk_main(), it seems to me that restart of gnome-shell invalidated device on which the evolution was running, thus a request for window update crashed the application. I guess other applications like gedit, maybe with long enough text which will show scroll-bars, may crash as well. Being it true I would move this to gtk3/gdk.
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 805073 has been marked as a duplicate of this bug. ***
*** Bug 833857 has been marked as a duplicate of this bug. ***
*** Bug 832355 has been marked as a duplicate of this bug. ***
*** Bug 826281 has been marked as a duplicate of this bug. ***
*** Bug 838325 has been marked as a duplicate of this bug. ***
*** Bug 855219 has been marked as a duplicate of this bug. ***
*** Bug 857880 has been marked as a duplicate of this bug. ***
*** Bug 855993 has been marked as a duplicate of this bug. ***
*** Bug 887491 has been marked as a duplicate of this bug. ***
I was writing message into notification (the one which appears in the middle), when it suddenly had got stuck (I could only move with mouse cursor and nothing else). I had to go to console and restart gnome-shell. backtrace_rating: 4 Package: empathy-3.6.3-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.