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 502168 - crash in Tasks: after recieving Error me...
crash in Tasks: after recieving Error me...
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-12-06 18:59 UTC by etolkacheva
Modified: 2007-12-10 00:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description etolkacheva 2007-12-06 18:59:40 UTC
Version: 2.10

What were you doing when the application crashed?
after recieving Error message "Failed to connect to SMTP server.. STARTTLS not supported" tried to change encryption in the Account settings, didn't change anything, closed the menu and went to administrator to ask which encryption to use... When was back Evolution crashed.


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

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 722571264 vsize: 722571264 resident: 77971456 share: 40816640 rss: 77971456 rss_rlim: 18446744073709551615
CPU usage: start_time: 1196963880 rtime: 818 utime: 720 stime: 98 cutime:644 cstime: 54 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 46912496362864 (LWP 3228)]
[New Thread 1178904912 (LWP 3645)]
[New Thread 1189394768 (LWP 3643)]
[New Thread 1147435344 (LWP 3308)]
[New Thread 1115965776 (LWP 3262)]
[New Thread 1094719824 (LWP 3258)]
(no debugging symbols found)
0x00000037a6e0d97f in waitpid () from /lib64/libpthread.so.0

Thread 3 (Thread 1189394768 (LWP 3643))

  • #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 ---------------------
(evolution:3228): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x895260'
(evolution:3228): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x895460'
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff35dfd000
--------------------------------------------------
Comment 1 Tobias Mueller 2007-12-10 00:27:50 UTC
Thanks for taking the time to report this bug.
It's most likely that this particular bug is the fedora specific bug 447591:
   GLib-GObject-WARNING **: gsignal.c:1669: signal
   `source_selected' is invalid for instance

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.
As debug symbols are missing, it's just a guess anyway since we can't determine the issue without debug information. Feel free to install debug information and open a new bug. See http://live.gnome.org/GettingTraces for details

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