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 474591 - (SamuraiCrow) crash in Tasks:
(SamuraiCrow)
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 460409
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-07 16:21 UTC by samuraileumas
Modified: 2007-09-22 20:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description samuraileumas 2007-09-07 16:21:54 UTC
What were you doing when the application crashed?



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: 618323968 vsize: 618323968 resident: 45154304 share: 21225472 rss: 45154304 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189181645 rtime: 880 utime: 801 stime: 79 cutime:2 cstime: 3 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 46912496406112 (LWP 6257)]
[New Thread 1136679248 (LWP 6328)]
[New Thread 1157658960 (LWP 6327)]
[New Thread 1084229968 (LWP 6275)]
(no debugging symbols found)
0x0000003a40c0d89f in waitpid () from /lib64/libpthread.so.0

Thread 3 (Thread 1157658960 (LWP 6327))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #3 <signal handler called>
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 ??
    from /lib64/libglib-2.0.so.0
  • #7 __nptl_deallocate_tsd
    from /lib64/libpthread.so.0
  • #8 start_thread
    from /lib64/libpthread.so.0
  • #9 clone
    from /lib64/libc.so.6


----------- .xsession-errors (24 sec old) ---------------------
(evolution:6257): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:6257): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:6257): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:6257): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:6257): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:6257): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:6257): camel-pop3-provider-WARNING **: Bad server response: Connection is closed. 21
(evolution:6257): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:6257): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x846800'
(evolution:6257): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x847c00'
--------------------------------------------------
Comment 1 samuraileumas 2007-09-08 02:16:54 UTC
I was editing the incorrect parts of the settings of a POP account and it crashed when I had entered one of the changes.  Specifically, I had to change the username to something other than the default setting.
Comment 2 Suman Manjunath 2007-09-22 20:03:47 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 460409 ***