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 468755 - crash in Tasks: reception du courrier
crash in Tasks: reception du courrier
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-21 06:43 UTC by ericsalon
Modified: 2007-11-30 18:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ericsalon 2007-08-21 06:43:16 UTC
Version: 2.10

What were you doing when the application crashed?
reception du courrier


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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 118448128 vsize: 118448128 resident: 48807936 share: 33280000 rss: 48807936 rss_rlim: 4294967295
CPU usage: start_time: 1187677764 rtime: 1530 utime: 1411 stime: 119 cutime:829 cstime: 81 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 -1208378640 (LWP 3021)]
[New Thread -1295000688 (LWP 3292)]
[New Thread -1305490544 (LWP 3291)]
[New Thread -1239299184 (LWP 3105)]
[New Thread -1251558512 (LWP 3092)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

Thread 3 (Thread -1305490544 (LWP 3291))

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


----------- .xsession-errors (60 sec old) ---------------------
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:3021): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3021): DEBUG: mailto URL program: evolution
(evolution:3021): e-data-server-ui-WARNING **: Le fichier de clés n'a pas de groupe « Passwords-Mail »
report junk?? Plus d'1 million de virus détectés... avec le nouveau Panda Internet Security 2008
(evolution:3021): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:3021): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x982f000'
(evolution:3021): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x982f120'
--------------------------------------------------
Comment 1 Suman Manjunath 2007-11-30 18:05:19 UTC
(evolution:3133): GLib-GObject-WARNING **: gsignal.c:1669: signal
`source_selected' is invalid for instance `0xaa6c008'
(evolution:3133): GLib-GObject-WARNING **: gsignal.c:1669: signal
`source_selected' is invalid for instance `0xaa6c128'

This is bug #447591, which is fixed now.

*** This bug has been marked as a duplicate of 447591 ***
Comment 2 Milan Crha 2007-11-30 18:13:07 UTC
Suman, I think this is other bug, not that you marked as duplicate of. The bug you mention is not crashing, and same text could be on console even in non-Fedora Evolutions, see bug #417999