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 494670 - crash in Tasks: switching between mailbo...
crash in Tasks: switching between mailbo...
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-11-07 17:03 UTC by kbreheny
Modified: 2007-11-07 21:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description kbreheny 2007-11-07 17:03:42 UTC 
Version: 2.10

What were you doing when the application crashed?
switching between mailboxes - (both on the same scalix server)


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 191606784 vsize: 191606784 resident: 106147840 share: 52084736 rss: 106147840 rss_rlim: 4294967295
CPU usage: start_time: 1194444991 rtime: 10861 utime: 10211 stime: 650 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1208867104 (LWP 2921)]
[New Thread -1228293232 (LWP 3039)]
[New Thread -1241322608 (LWP 3008)]
[New Thread -1300243568 (LWP 2996)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 176097

Thread 1 (Thread -1208867104 (LWP 2921))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #6 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #7 e_tree_table_adapter_save_expanded_state
    from /usr/lib/evolution/2.10/libetable.so.0
  • #8 e_tree_save_expanded_state
    from /usr/lib/evolution/2.10/libetable.so.0
  • #9 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #10 message_list_set_folder
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #11 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #12 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #13 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #20 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #21 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (38 sec old) ---------------------
console-kit-daemon (pid 2206) is running...
chargen-dgram
xinetd (pid 2163) is running...
ConsoleKit
console-kit-daemon (pid 2206) is running...
ConsoleKit
console-kit-daemon (pid 2206) is running...
chargen-dgram
xinetd (pid 2163) is running...
NetworkManager
NetworkManager is stopped
NetworkManager
NetworkManager is stopped
NetworkManager
NetworkManager (pid 4564) is running...
--------------------------------------------------
Comment 1 Tobias Mueller 2007-11-07 21:53:54 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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