Beagle doesn't handle coma in mail folder name

Bug #108957 reported by Anders Magnusson
12
Affects Status Importance Assigned to Milestone
Beagle
Fix Released
High
beagle (Ubuntu)
Fix Released
Undecided
Kevin Kubasik

Bug Description

I have a couple of mail folder with a coma (",") in them, ,and it looks like beagle has some kind of problem with these folder. It throws an exception saying:

20070422 17:23:59.4449 10026 Beagle WARN EX: System.InvalidOperationException: Invalid connection string
20070422 17:23:59.4449 10026 Beagle WARN EX: at Mono.Data.SqliteClient.SqliteConnection.SetConnectionString (System.String connstring) [0x00000]
20070422 17:23:59.4449 10026 Beagle WARN EX: at Mono.Data.SqliteClient.SqliteConnection.set_ConnectionString (System.String value) [0x00000]
20070422 17:23:59.4449 10026 Beagle WARN EX: at Beagle.Daemon.EvolutionMailQueryable.EvolutionSummaryTracker.GetConnection (System.String filename) [0x00000]
20070422 17:23:59.4449 10026 Beagle WARN EX: at Beagle.Daemon.EvolutionMailQueryable.EvolutionSummaryTracker..ctor (System.String directory, System.String account_name, System.String folder_name) [0x00000]
20070422 17:23:59.4449 10026 Beagle WARN EX: at Beagle.Daemon.EvolutionMailQueryable.EvolutionMailIndexableGeneratorImap.HasNextIndexable () [0x00000]
20070422 17:23:59.4449 10026 Beagle WARN EX: at Beagle.Daemon.LuceneQueryable+AddGeneratorTask.DoTaskReal () [0x00000]
20070422 17:23:59.4449 10026 Beagle WARN EX: at Beagle.Util.Scheduler+Task.DoTask () [0x00000]

It also looks like it tries to crawl these folder over and over again, so if I do a 'beagle-index-info' it always says that it is crawling the EvolutionMail backend.

Revision history for this message
Kevin Kubasik (kkubasik) wrote :

Ok, looks like some imporoper escaping in the evo summary code, Joe did most of this, so I'll point him this way at some point, but it should be easy enough to fix, its just a question of if we can get a well-tested patch out into fesity.

Changed in beagle:
assignee: nobody → kkubasik
status: Unconfirmed → Confirmed
Changed in beagle:
status: Unknown → Unconfirmed
Revision history for this message
Joe Shaw (joeshaw) wrote :

I presume this affects feisty? (There doesn't appear to be a way to see what version of a package a bug in LP affects?)

Revision history for this message
Anders Magnusson (d98.ama) wrote :

Correct. This is in Feisty.

Revision history for this message
Joe Shaw (joeshaw) wrote :

I just checked in a fix for this upstream, I will attach updated assemblies with the fix.

Revision history for this message
Joe Shaw (joeshaw) wrote :

Drop this (and the .mdb file) over top of your previous file, probably in /usr/lib/beagle/Backends/

Revision history for this message
Joe Shaw (joeshaw) wrote :
Revision history for this message
Anders Magnusson (d98.ama) wrote :

Thank you very much for the quick fix!!

Changed in beagle:
status: Unconfirmed → Fix Released
Revision history for this message
dBera (dbera-web) wrote :

Upstream release 0.2.17 fixes the problem.

Revision history for this message
Kevin Kubasik (kkubasik) wrote :

This has been fixed.

Changed in beagle:
status: Confirmed → Fix Released
Changed in beagle:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.