[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#678532: libreoffice: crash on startup: 'com::sun::star::uno::RuntimeException'



Hi,

On Sat, Jun 23, 2012 at 08:51:36AM +0800, Clayton wrote:
> > What did you run before? 1:3.5.4-4?
> 
> Not sure right off-hand, I normally follow testing, and upgrade a
> couple times a week. So it would have been a really fresh version in
> testing, as of yesterday.

Hrm, OK. 3.5.4-4 migrated to testing last Sunday (2012-06-17), so you probably
has it. Weird that it still happens.

Maybe some other (external from LO) extension still has the same bug because it
copied LO stuff over?. Can you give me the output of dpkg -l | grep libreoffice
so see what LO and LO extensions you have installed in exact versions?

> That was it, ~/.config/libreoffice, and as far as I can tell only
> ~/.config/libreoffice, was root:root. Not sure how that could have
> happened on my end. Note that although I do not start libreoffice

Well, as said, there was #619263, so upgrades with sudo can run into it
when it does stuff with $HOME...

> Like I said, I do an apt-get upgrade on testing a couple times a week,
> so I get those packages when you send them. ;-)

Nah, you get them later. (Testing is not managed by maintainers but by
the release team.) :-)

(And no, you shouldn't do "upgrade" but "dist-upgrade" for updated/changes
dependencies, etc ;-))

> The sequence was:
> * libreoffice in whatever state it was from my last apt-get upgrade to
>   testing
> * I see the bug reported here
> * attempt to file a bug report, informed a newer version in unstable
> * uncommented unstable in sources.list, and did an
>   apt-get update && apt-get install -f unstable libreoffice
> 
> Is there a better way to do this? I don't want to take my whole machine
> to unstable with an apt-get upgrade.

Nah, that scenario is understandable but I still don't like it ;-/

Regards,

Rene



Reply to: