Hide Forgot
+++ This bug was initially created as a clone of Bug 701604 +++ abrt version: 2.0.1 executable: /usr/bin/evolution cmdline: evolution component: evolution crash_function: magazine_chain_pop_head kernel: 2.6.38.4-20.fc15.x86_64 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) package: evolution-3.0.1-1.fc15 architecture: x86_64 username: litcanu uid: 500 os_release: Fedora release 15 (Lovelock) time: 1304418930 rating: 4 Text file: maps, 80067 bytes Text file: build_ids, 8282 bytes Binary file: coredump, 127524864 bytes Text file: dsos, 61429 bytes Text file: backtrace, 92461 bytes event_log ----- 2011-05-03-13:47:34> (exited with 0) 2011-05-03-13:47:34> Analyzing coredump '/home/litcanu/.abrt/spool/ccpp-2011-05-03-13:35:30-1634/coredump' 2011-05-03-13:47:35 All 202 debuginfo files are available 2011-05-03-13:47:36> (exited with 0) 2011-05-03-13:47:37> Analyzing coredump '/home/litcanu/.abrt/spool/ccpp-2011-05-03-13:35:30-1634/coredump' 2011-05-03-13:47:37 All 202 debuginfo files are available 2011-05-03-13:47:45> Backtrace is generated and saved, 92461 bytes 2011-05-03-13:47:45> Backtrace is generated and saved, 92461 bytes 2011-05-03-13:47:45> (exited with 0) 2011-05-03-13:47:45> Lock file './.lock' is locked by process 8177 environ ----- XDG_SESSION_ID=1 HOSTNAME=litcanu-acasa IMSETTINGS_INTEGRATE_DESKTOP=yes SHELL=/bin/bash TERM=dumb HISTSIZE=1000 XDG_SESSION_COOKIE=fc068490473c9c2a05c489fc0000000a-1304405807.496321-1970636444 IMSETTINGS_MODULE=none USER=litcanu USERNAME=litcanu MAIL=/var/spool/mail/litcanu PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/litcanu/bin DESKTOP_SESSION=gnome QT_IM_MODULE=xim PWD=/home/litcanu XMODIFIERS=@im=none LANG=en_US.utf8 GDM_LANG=en_US.utf8 GDMSESSION=gnome HISTCONTROL=ignoredups HOME=/home/litcanu SHLVL=1 LOGNAME=litcanu DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-qfrdp16Nh6,guid=030362a23d906d516285610e0000001c 'LESSOPEN=||/usr/bin/lesspipe.sh %s' WINDOWPATH=1 XDG_RUNTIME_DIR=/run/user/litcanu DISPLAY=:0 GTK_IM_MODULE=gtk-im-context-simple G_BROKEN_FILENAMES=1 XAUTHORITY=/var/run/gdm/auth-for-litcanu-EJ0fmD/database _=/usr/bin/gnome-session GNOME_DESKTOP_SESSION_ID=this-is-deprecated SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1312,unix/unix:/tmp/.ICE-unix/1312 ORBIT_SOCKETDIR=/tmp/orbit-litcanu GNOME_KEYRING_CONTROL=/tmp/keyring-AboXgX SSH_AUTH_SOCK=/tmp/keyring-AboXgX/ssh GPG_AGENT_INFO=/tmp/keyring-AboXgX/gpg:0:1 GJS_DEBUG_OUTPUT=stderr 'GJS_DEBUG_TOPICS=JS ERROR;JS LOG' DESKTOP_STARTUP_ID=gnome-shell-1500-litcanu-acasa-evolution-0_TIME59406 GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/evolution.desktop GIO_LAUNCHED_DESKTOP_FILE_PID=1634 --- Additional comment from litcanu onTue May 03 10:48:10 EDT 2011 --- Created attachment 496482 [details] File: maps --- Additional comment from litcanu onTue May 03 10:48:12 EDT 2011 --- Created attachment 496483 [details] File: build_ids --- Additional comment from litcanu onTue May 03 10:48:15 EDT 2011 --- Created attachment 496484 [details] File: dsos --- Additional comment from litcanu onTue May 03 10:48:18 EDT 2011 --- Created attachment 496485 [details] File: backtrace --- Additional comment from mcrha onWed May 04 06:22:01 EDT 2011 --- Thanks for a bug report. This can be related to an upstream bug [1], but as there is some issue in the backtrace itself, then let's start with obvious things. I would like to ask pango team for their opinion on this. > #4 0x000000313d82bfef in run_length_encode_types_utf8 > (panded_strongs=read_sleb128: Corrupted DWARF expression. > ) at fribidi.c:121 > #5 fribidi_analyse_string_utf8 (pmax_level=read_sleb128: Corrupted DWARF > expression. ) at fribidi.c:493 [1] https://bugzilla.gnome.org/show_bug.cgi?id=625139 --- Additional comment from behdad onWed May 04 18:04:14 EDT 2011 --- No comment. --- Additional comment from mcrha onThu May 05 05:40:03 EDT 2011 --- (In reply to comment #6) > No comment. Hmm, I'm not sure what to think about that. Anyway... Iulian, do you see this crash often, please? If so, could you try to reproduce this under valgrind, to check whether it'll show any memory issues being related to this crash, please? You can install valgrind and run evolution under it like this: $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt and then possibly try to reproduce the issue. Valgrind can sometimes avoid the crash itself, while writing memory issues it spot during the run, thus please attach the resulting log.txt file here, and I can examine it. Thanks in advance. --- Additional comment from litcanu onThu May 05 08:46:02 EDT 2011 --- No sorry, just once. Can't reproduce it unfortunately ... --- Additional comment from mcrha onThu May 05 12:12:09 EDT 2011 --- Thanks for the update, Pity you cannot reproduce this. I'm closing this, but please feel free to reopen if you find a way to investigate this further, maybe with a valgrind log as suggested in comment #7. --- Additional comment from braden onFri Jun 03 15:02:19 EDT 2011 --- Reopening. Since installing Fedora 15/Evolution 3.0, I've hit at least three crashes that abrt has identified as a duplicate of this bug. When it happens seems to be arbitrary; that is, I haven't identified anything specific that I can do to reproduce it. But in light of the frequency with which it's occurring, I think it warrants further attention. --- Additional comment from braden onFri Jun 03 15:06:37 EDT 2011 --- Created attachment 502831 [details] Backtrace --- Additional comment from mail onSun Jun 05 11:26:31 EDT 2011 --- Package: evolution-3.0.2-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- I have no idea - evolution is crashing all of the time now: three times in the past minute. I was merely downloading and browsing through email. I think the operation I performed just prior to the crash was to click on a mail folder to change the mail list display to that folder. I've been an evoltuion user for well over a decade. Evolution 3 sucks for me. I can't get any work done. --- Additional comment from mail onSun Jun 05 19:31:25 EDT 2011 --- Package: evolution-3.0.2-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Clicked Send/Receive --- Additional comment from mcrha onMon Jun 06 06:05:01 EDT 2011 --- Could you try with evolution-3.0.2-2 from updates testing, please? I introduced a very bad bug in 3.0.2-1, which is fixed in 3.0.2-2. --- Additional comment from mjs onSun Jun 12 20:42:19 EDT 2011 --- Package: evolution-3.0.2-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Crash occurred while marking RSS feeds as read using CTRL-A CTRL-K. Also, Exchange (OWA), IMAP, and POP accounts were in the process of synchronizing. --- Additional comment from ajose onTue Jun 14 19:42:37 EDT 2011 --- Package: evolution-3.0.2-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Uso el plugin de RSS del repositorio de Fedora Marco error con el RSS de Smashing Magazine Feed, al momento de querer leer los feeds para ver si veia algo raro fue cuando marco el error --- Additional comment from deadlycelt.uk onThu Jun 16 12:19:28 EDT 2011 --- Package: evolution-3.0.2-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Unexpected crash, not sure how to reproduce
Created attachment 505801 [details] File: backtrace
Thanks for a bug report. I do not think it's anyhow related to bug #701604, because that one crashed when computing size of a widget, where this backtrace shows a crash when building GtkRecentChooserMenu, which I cannot recall being used in evolution itself. Maybe this comes from a file chooser? Nonetheless, similar applies to this, as I just wrote to bug #701604 comment #19. Also some steps to reproduce will help here. The other bug seems to be related to evolution-rss.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Backtrace analysis found this bug to be similar to some already closed bugs from other components. You might want to check those bugs for additional information. Bugs which were found to be similar to this bug: gtk2: bug #531848, bug #547533 This comment is automatically generated.