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 473210 - crash in Tasks: looking at a map of new ...
crash in Tasks: looking at a map of new ...
Status: RESOLVED DUPLICATE of bug 364700
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-09-03 15:25 UTC by ali
Modified: 2007-09-24 17:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ali 2007-09-03 15:25:53 UTC
Version: 2.10

What were you doing when the application crashed?
looking at a map of new york manhattan


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 106528768 vsize: 106528768 resident: 37134336 share: 28962816 rss: 37134336 rss_rlim: 4294967295
CPU usage: start_time: 1188833360 rtime: 116 utime: 102 stime: 14 cutime:2 cstime: 7 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 -1209129248 (LWP 22795)]
[New Thread -1230705776 (LWP 22855)]
[New Thread -1219806320 (LWP 22829)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209129248 (LWP 22795))

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


----------- .xsession-errors (28 sec old) ---------------------
(evolution:21241): gtkhtml-WARNING **: No such file or directory
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30000b4 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30000b4 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3001ef1 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3001ef1 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:22795): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:22795): 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
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-24 17:59:29 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, 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.


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