beagle-search causes beagled to crash

Bug #33001 reported by Marc Nozell
28
Affects Status Importance Assigned to Milestone
beagle (Ubuntu)
Fix Released
Medium
Kevin Kubasik

Bug Description

I think it may be related to backspacing all the search text out of a search query in beagle-search, but beagled dies like this;

Debug: Starting queryables
Debug: Scanning addressbooks and calendars
Error: Unhandled exception thrown. Exiting immediately.
Error: System.TypeInitializationException: An exception was thrown by the type i nitializer for Evolution.SourceList ---> System.DllNotFoundException: libedatase rver-1.2.so.4
in (wrapper managed-to-native) Evolution.Source:e_source_get_type ()
in <0x00014> Evolution.Source:get_GType ()
in <0x00026> GtkSharp.EvolutionSharp.ObjectManager:Initialize ()
in <0x00007> Evolution.SourceList:.cctor ()--- End of inner exception stack trac e ---

in (unmanaged) 0xb7e624f1
in <0x00064> Beagle.Daemon.EvolutionDataServerQueryable.SourcesHandler:.ctor (st ring,System.Type,Beagle.Daemon.EvolutionDataServerQueryable.EvolutionDataServerQ ueryable,string)
in <0x000be> Beagle.Daemon.EvolutionDataServerQueryable.EvolutionDataServerQuery able:Start ()
in <0x00016> Beagle.Daemon.Queryable:Start ()
in <0x0008b> Beagle.Daemon.QueryDriver:StartQueryables ()
in <0x00047> (wrapper delegate-invoke) System.MulticastDelegate:invoke_bool ()
in <0x0002a> TimeoutProxy:Handler ()
in <0x00036> (wrapper native-to-managed) TimeoutProxy:Handler ()
in (unmanaged) 0xb7d3f3a7
in <0x00004> (wrapper managed-to-native) Gtk.Application:gtk_main ()
in <0x00007> Gtk.Application:Run ()
in <0x006b3> Beagle.Daemon.BeagleDaemon:DoMain (string[])
in <0x00014> Beagle.Daemon.BeagleDaemon:Main (string[])

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object
in <0x0002e> System.IO.StreamWriter:LowLevelWrite (System.String s)
in <0x0001d> System.IO.StreamWriter:Write (System.String value)
in <0x00010> System.IO.UnexceptionalStreamWriter:Write (System.String value)
in <0x0001e> System.IO.TextWriter:Write (System.Object value)
in <0x00028> System.IO.SynchronizedWriter:Write (System.Object value)
in <0x0009f> Beagle.Util.Log:WriteLine (LogLevel level, System.String format, Sy stem.Object[] args, System.Exception ex)
in <0x00011> Beagle.Util.Log:Warn (System.String message, System.Object[] args)
in <0x0000d> Beagle.Util.Logger:Warn (System.String message, System.Object[] arg s)
in <0x00222> Beagle.Util.ExceptionHandlingThread:ThreadStarted ()
in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()

Revision history for this message
Jorge Castro (jorge) wrote :

Confirming on 0.2.1-1ubuntu5

Changed in beagle:
status: Unconfirmed → Confirmed
Revision history for this message
Markus Matuszczak (konsumer) wrote :

confirm on beagle_0.2.1-1ubuntu5_amd64.deb

after removing of the beagle-backend-evolution_0.2.1-1ubuntu5_all it works.

Revision history for this message
Sebastian Dröge (slomo) wrote :

This is because evolution-sharp doesn't support our too new evolution-data-server yet... this will hopefully be fixed before release otherwise we probably have to disable evolution support completely :/

Revision history for this message
Sebastian Dröge (slomo) wrote :

Should be fixed with evolution-sharp / libevolution-cil 0.10.2-2ubuntu4.
Please reopen otherwise after updating.

Changed in beagle:
status: Confirmed → Fix Released
Revision history for this message
Chris Lee (chris-lee-gertner) wrote :

Latest evolution-sharp seems to do the trick for me! Thx.

Revision history for this message
Thomas Wolfe (tomwolfe) wrote :

Using Gutsy and I am getting this problem again, so I am opening it back up, using libevolution2.0-cil 0.13.1-0ubuntu1

Changed in beagle:
status: Fix Released → Confirmed
Revision history for this message
Kevin Kubasik (kkubasik) wrote :

I believe that a pending upstream version might have a fix for this, but I'm not sure.

Changed in beagle:
assignee: nobody → kkubasik
Kevin Kubasik (kkubasik)
Changed in beagle:
status: Confirmed → Fix Released
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.