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 500532 - crash in Tasks: Just closing the Applica...
crash in Tasks: Just closing the Applica...
Status: RESOLVED DUPLICATE of bug 445309
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-11-29 22:30 UTC by mhills
Modified: 2007-12-13 15:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mhills 2007-11-29 22:30:31 UTC
What were you doing when the application crashed?
Just closing the Application :-(


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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 113135616 vsize: 113135616 resident: 31555584 share: 18894848 rss: 31555584 rss_rlim: 4294967295
CPU usage: start_time: 1196370948 rtime: 734 utime: 692 stime: 42 cutime:0 cstime: 1 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 -1208195360 (LWP 24822)]
[New Thread -1244755056 (LWP 25143)]
[New Thread -1270916208 (LWP 24877)]
[New Thread -1212888176 (LWP 24857)]
(no debugging symbols found)
0x00c40402 in __kernel_vsyscall ()

Thread 2 (Thread -1244755056 (LWP 25143))

  • #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 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #7 PR_Lock
    from /usr/lib/libnspr4.so
  • #8 ??
    from /usr/lib/libnspr4.so
  • #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 (4002 sec old) ---------------------
** (evolution:23057): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
CalDAV Eplugin starting up ...
** (evolution:24822): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:24822): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
BBDB spinning up...
(evolution:24822): e-data-server-DEBUG: Loading categories from "/home/matt/.evolution/categories.xml"
(evolution:24822): e-data-server-DEBUG: Loaded 29 categories
(evolution:24822): gtkhtml-WARNING **: No such file or directory
(pidgin:19817): GStreamer-CRITICAL **: gst_object_unref: assertion `((GObject *) object)->ref_count > 0' failed
--------------------------------------------------
Comment 1 Susana 2007-11-30 20:22:18 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 André Klapper 2007-12-13 15:31:02 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 445309 ***