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 445552 - crash in Tasks: Setup email account
crash in Tasks: Setup email account
Status: RESOLVED DUPLICATE of bug 373699
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-08 17:29 UTC by lenguyen_d
Modified: 2007-06-11 11:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description lenguyen_d 2007-06-08 17:29:29 UTC
What were you doing when the application crashed?
Setup email account


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 614346752 vsize: 614346752 resident: 35921920 share: 19898368 rss: 35921920 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181327151 rtime: 222 utime: 196 stime: 26 cutime:0 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496496224 (LWP 5316)]
[New Thread 1178638672 (LWP 5525)]
[New Thread 1157658960 (LWP 5522)]
(no debugging symbols found)
0x0000003cc180d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496496224 (LWP 5316))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #6 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #7 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/collisions": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/rx_packets": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/tx_packets": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/rx_bytes": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/tx_bytes": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/rx_errors": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/tx_errors": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/collisions": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/rx_packets": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/tx_packets": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/rx_bytes": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/tx_bytes": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/rx_errors": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/tx_errors": No such file or directory
glibtop: Failed to open "/sys/class/net/wmaster0/statistics/collisions": No such file or directory
--------------------------------------------------
Comment 1 André Klapper 2007-06-11 11:48:11 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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