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 475945 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 431459
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
aklapper[fc7]
Depends on:
Blocks:
 
 
Reported: 2007-09-11 18:16 UTC by vaeduus
Modified: 2007-09-20 16:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description vaeduus 2007-09-11 18:16:03 UTC
Version: 2.10

What were you doing when the application crashed?



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: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks_Cairo-Olive2
Icon Theme: nuoveXT-1.6

Memory status: size: 131592192 vsize: 131592192 resident: 33443840 share: 27193344 rss: 33443840 rss_rlim: 4294967295
CPU usage: start_time: 1189534436 rtime: 78 utime: 63 stime: 15 cutime:1 cstime: 6 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 -1208994080 (LWP 24400)]
[New Thread -1229980784 (LWP 24450)]
[New Thread -1250960496 (LWP 24425)]
[New Thread -1240470640 (LWP 24422)]
[New Thread -1217537136 (LWP 24420)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208994080 (LWP 24400))

  • #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 ---------------------
/usr/share/themes/Clearlooks_Cairo-Olive2/gtk-2.0/gtkrc:52: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive2/gtk-2.0/gtkrc:53: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive2/gtk-2.0/gtkrc:54: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:24400): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:24400): 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
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
/usr/share/themes/Clearlooks_Cairo-Olive2/gtk-2.0/gtkrc:52: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive2/gtk-2.0/gtkrc:53: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Olive2/gtk-2.0/gtkrc:54: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-20 16:47:36 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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