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 517883 - crash in Tasks: looking at properties of...
crash in Tasks: looking at properties of...
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
Depends on:
Blocks:
 
 
Reported: 2008-02-21 14:52 UTC by dchesley
Modified: 2008-02-21 16:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description dchesley 2008-02-21 14:52:26 UTC
What were you doing when the application crashed?
looking at properties of "sent" folder


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 114307072 vsize: 114307072 resident: 24621056 share: 17309696 rss: 24621056 rss_rlim: 4294967295
CPU usage: start_time: 1203605280 rtime: 63 utime: 58 stime: 5 cutime:0 cstime: 0 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 -1208658208 (LWP 2943)]
[New Thread -1263535216 (LWP 2997)]
[New Thread -1219163248 (LWP 2965)]
(no debugging symbols found)
0x0036b402 in __kernel_vsyscall ()

Thread 1 (Thread -1208658208 (LWP 2943))

  • #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 ---------------------
localuser:jko being added to access control list
SESSION_MANAGER=local/jee:/tmp/.ICE-unix/2729
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
CalDAV Eplugin starting up ...
** (evolution:2943): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2943): 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
(evolution:2943): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 dchesley 2008-02-21 15:28:32 UTC
The evolution account was originally set up for a user whose home directory was on an nfs mount on /home2. We had to move to a different network, so the user's home directory path was changed from /home2/jko to /home/jko. This led to an error from Evolution when the user sent mail (/home2/jko/.evolution/mail/local/Sent could no longer be found). While looking at the properties of the Sent folder, the system suddenly rebooted itself. Office lights didn't flicker, so power interrupt not likely.

A subsequent workaround to avoid repeate of Evolution's complaints was to greate a local file /home2/jko/.evolution/mail/local/Sent (matching what Evolution used under the original setup) - error msg has ceased, function seems OK, we're watching for another reboot or other pathology, will report such if and when it happens.
Comment 2 Tobias Mueller 2008-02-21 16:37:11 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 431459 ***