After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 361484 - crash in Evolution: I removed a filter from ...
crash in Evolution: I removed a filter from ...
Status: RESOLVED DUPLICATE of bug 359236
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-10-11 16:44 UTC by Burkay Genc
Modified: 2006-10-11 22:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Burkay Genc 2006-10-11 16:44:14 UTC
What were you doing when the application crashed?
I removed a filter from the filters list. Then I clicked on the Trash folder (I believe evolution froze at this point) and since the folder seemed to be empty I clicked on Junk folder. That also seemed to be empty (possibly because the application was already frozen and not displaying the contents of the folders anymore). And then this bug report dialogue showed up.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 352944128 vsize: 352944128 resident: 50737152 share: 22421504 rss: 50737152 rss_rlim: -1
CPU usage: start_time: 1160559700 rtime: 1548 utime: 1448 stime: 100 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47355248098592 (LWP 9838)]
[New Thread 1166326096 (LWP 20275)]
[New Thread 1115969872 (LWP 19928)]
[New Thread 1107577168 (LWP 9884)]
[New Thread 1098918224 (LWP 9880)]
[New Thread 1099184464 (LWP 9853)]
[New Thread 1090525520 (LWP 9851)]
[New Thread 1082132816 (LWP 9848)]
(no debugging symbols found)
0x00002b11bc71a5cf in waitpid () from /lib/libc.so.6

Thread 8 (Thread 1082132816 (LWP 9848))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 5 (Thread 1098918224 (LWP 9880))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 4 (Thread 1107577168 (LWP 9884))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 3 (Thread 1115969872 (LWP 19928))

  • #0 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #1 default_attr
    from /lib/libpthread.so.0
  • #2 ??
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??

Thread 2 (Thread 1166326096 (LWP 20275))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Comment 1 Karsten Bräckelmann 2006-10-11 17:12:03 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Can you reproduce this?
Comment 2 Burkay Genc 2006-10-11 20:40:44 UTC
I could reproduce the crash when I clicked on trash and then junk. Then, I installed the debug symbols and meanwhile I noticed that there is an update warning. So, I updated ubuntu and evolution was updated as well from (2.8.1-0ubuntu1) to 2.8.1-0ubuntu2. Now, I can't reproduce the crash anymore. It seems like whatever was fixed in the last update also fixed this bug.
Comment 3 Karsten Bräckelmann 2006-10-11 22:32:06 UTC
Thanks, Burkay. :)

The patch attached to bug 359236 is the only fix that went in into that Ubuntu point release.

Please feel free to report any further bugs you find.  Thanks!


*** This bug has been marked as a duplicate of 359236 ***