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 482988 - crash in Tasks:
crash in Tasks:
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-10-03 15:45 UTC by mugabenp
Modified: 2007-10-05 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mugabenp 2007-10-03 15:45:39 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: Crux

Memory status: size: 116850688 vsize: 116850688 resident: 37310464 share: 29569024 rss: 37310464 rss_rlim: 4294967295
CPU usage: start_time: 1191426388 rtime: 138 utime: 119 stime: 19 cutime:1 cstime: 3 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 -1208871200 (LWP 3890)]
[New Thread -1263445104 (LWP 3948)]
[New Thread -1252553840 (LWP 3947)]
[New Thread -1220179056 (LWP 3914)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208871200 (LWP 3890))

  • #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 (11 sec old) ---------------------
  VirtualChannelSelector: No progress for op 1: listener = class com.aelitis.azureus.core.clientmessageservice.impl.NonBlockingReadWriteService$2, count = 300, socket: open = true, connected = true
    VirtualChannelSelector::select::-1,NonBlockingReadWriteService$1::runSupport::-1,AEThread::run::-1
[alert] Alert:3:'Save to default data dir' [Use default data dir] needs to be enabled for auto-.torrent-import to work
[alert] Alert:3:'Save to default data dir' [Use default data dir] needs to be enabled for auto-.torrent-import to work
[alert] Alert:3:'Save to default data dir' [Use default data dir] needs to be enabled for auto-.torrent-import to work
[alert] Alert:3:'Save to default data dir' [Use default data dir] needs to be enabled for auto-.torrent-import to work
[alert] Alert:3:'Save to default data dir' [Use default data dir] needs to be enabled for auto-.torrent-import to work
[alert] Alert:3:'Save to default data dir' [Use default data dir] needs to be enabled for auto-.torrent-import to work
[alert] Alert:3:'Save to default data dir' [Use default data dir] needs to be enabled for auto-.torrent-import to work
CalDAV Eplugin starting up ...
** (evolution:3890): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3890): 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
[alert] Alert:3:'Save to default data dir' [Use default data dir] needs to be enabled for auto-.torrent-import to work
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-05 10:03:56 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 ***