Bug#633929:

[Rene Engelhard <rene@debian.org>]

On Sun, Jul 01, 2012 at 09:57:48PM +0200, Rene Engelhard wrote:
> Hi,
> 
> On Thu, Jun 21, 2012 at 04:14:55PM +0800, Henk Metselaar wrote:
> > Op Thu, 21 Jun 2012 15:41:08 +0800 schreef Rene Engelhard
> > <rene@debian.org>:
> > 
> > >On Thu, Jun 21, 2012 at 02:42:33PM +0800, Henk Metselaar wrote:
> > >>I had the same problem and (nearly) the same versions installed as
> > >>Joey Hess in post #19. The problem cleared up after downgrading
> > >
> > >Sure? 3.4.5-5 != 3.5.4-5. Either you used a totally ancient system (which
> > >you shouldn't) or... ;)
> > 
> > I installed LO from backports. For some reason some individual
> > packages have been pulled from testing at some time. Some other were
> > slightly outdated (3.4.6-2 instead of 3.4.6-2~bpo60+2).
> > 
> > I see in #19: LO-filter-mobiledev 3.5.2~rc2-1, I had 3.5.4.4-4.
> 
> Yeah, I can reproduce this. LO from bpo (1:3.4.6-2~bpo60+2) +
> filter-mobiledev 3.5.4.4-5 -> RuntimeError. Will add a Breaks:

Sorry, sent to early.

I wanted to add:

as we see this gave me a RuntimeError on console, not a "unable to access central
configuration", though..

Did you verify that a -filter-mobiledev dowgrade fixes your problem?

Regards,
 
Rene