Re: System.Xml.XmlException: Document element did not appear. Line 1, position 1.
- From: Debajyoti Bera <dbera web gmail com>
- To: dashboard-hackers gnome org
- Subject: Re: System.Xml.XmlException: Document element did not appear. Line 1, position 1.
- Date: Sat, 12 Jan 2008 11:36:34 -0500
> 20080111 10:38:30.0808 27307 Beagle WARN EX: Caught exception in
> DoTaskReal 20080111 10:38:30.0808 27307 Beagle WARN EX: Tag:
> Crawling Nautilus Metadata 20080111 10:38:30.0808 27307 Beagle WARN EX:
> Creator:
> 20080111 10:38:30.0808 27307 Beagle WARN EX: Description:
> 20080111 10:38:30.0808 27307 Beagle WARN EX: Priority: Delayed (0)
> 20080111 10:38:30.0808 27307 Beagle WARN EX: System.Xml.XmlException:
> Document element did not appear. Line 1, position 1. 20080111
You are probably facing http://bugzilla.gnome.org/show_bug.cgi?id=504192 . It
was fixed shortly after 0.3.1 and is available in 0.3.2
> This error aside, I think it's some for some intelligence in the beagle
> log handling. Too many times beagle has filled my ~ with a single error
I have thought about this over and over again ... one option is to disable
verbose debug logging by default, but people are against it. The argument
given is, such verbose logging leads us to the errors - without them, we
would not be able to know of certain errors. This argument is kind of valid,
though it can be quite taxing on the users. Btw, most of the distros lower
the loglevel so users installing from packages would not face this problem.
The other options like "last message repeated" work against the above
argument. Are there reasons to believe that reporting "last message repeated"
is better than disabling debug output ?
- dBera
--
-----------------------------------------------------
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]