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 473994 - crash in e_source_group_uid_from_xmldoc XML parsing errors
crash in e_source_group_uid_from_xmldoc XML parsing errors
Status: RESOLVED DUPLICATE of bug 552491
Product: evolution
Classification: Applications
Component: Calendar
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
aklapper[fc7]
: 474225 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-09-05 18:57 UTC by vivi
Modified: 2008-10-15 20:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description vivi 2007-09-05 18:57:26 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.20-2931.fc7xen #1 SMP Mon Aug 13 10:12:37 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 31096832 vsize: 31096832 resident: 8900608 share: 7614464 rss: 8900608 rss_rlim: 4294967295
CPU usage: start_time: 1189018497 rtime: 8 utime: 6 stime: 2 cutime:0 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208961312 (LWP 3767)]
(no debugging symbols found)
0x002f0402 in __kernel_vsyscall ()

Thread 1 (Thread -1208961312 (LWP 3767))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 e_source_group_uid_from_xmldoc
    from /usr/lib/libedataserver-1.2.so.9
  • #6 e_source_list_is_gconf_updated
    from /usr/lib/libedataserver-1.2.so.9
  • #7 e_source_list_sync
    from /usr/lib/libedataserver-1.2.so.9
  • #8 e_plugin_lib_enable
    from /usr/lib/evolution/2.10/plugins/liborg-gnome-evolution-caldav.so
  • #9 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #10 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #11 e_plugin_construct
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #12 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #13 e_plugin_load_plugins
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #14 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
Entity: line 1: parser error : parsing XML declaration: '?>' expected
<?xml version="1.0"
                   ^
Entity: line 1: parser error : Start tag expected, '<' not found
<?xml version="1.0"
                   ^
Entity: line 1: parser error : Blank needed here
<?xml version="1.0"
                   ^
Entity: line 1: parser error : parsing XML declaration: '?>' expected
<?xml version="1.0"
                   ^
Entity: line 1: parser error : Start tag expected, '<' not found
<?xml version="1.0"
                   ^
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-05 22:37:16 UTC
Unique according to sdf.

Dear reporter: Can you reproduce this issue?
Could you install debug packages for evolution, evolution-data-server and gtkthml as well in order to get a proper stacktrace?

Thanks in advance
Comment 2 Lucky Wankhede 2007-09-13 07:14:31 UTC
*** Bug 474225 has been marked as a duplicate of this bug. ***
Comment 3 Akhil Laddha 2008-06-23 11:29:26 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.
Could you please install some debugging packages [1], start the application as
normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, evolution-exchange, gtkhtml, gtk, glib, libsoup, gnome-vfs, libgnome, orbit2 and libgnomeui (as far as those packages are provided by your distribution). More details can be found here:
http://live.gnome.org/GettingTraces

If possible, please upgrade to current stable Evolution 2.22.2 (GNOME 2.22.2) version.
Comment 4 Akhil Laddha 2008-07-25 08:33:17 UTC
Closing this bug report as no further information has been provided. Please
feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 5 Philip Withnall 2008-10-15 20:35:58 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 552491 ***