impress hangs when opening Canonical template presentation [regression from edgy]

[James Troup]

Binary package hint: openoffice.org

Whenever I try to open the Canonical template presentation impress starts up enough to open a(n empty) window, but then gets stuck and just sits there chewing CPU. Impress was happy to open the same document in Edgy.

[Matthias Klose (doko)]

unable to reproduce on feisty 20070228, i386 and amd64, both fresh installations

[Tollef Fog Heen (tfheen)]

Milestoning as this is important to get fixed. James, can you see if there's any information you can give Matthias to be able to reproduce it?

[James Troup (elmo)]

I've reproduced this with a newly added user (to rule out my dotfiles) with openoffice 2.1-4ubuntu1. I've uploaded the file in question to chinstrap:~james/Canonical.otp .

[Matthias Klose (doko)]

still unreproducible with a live CD (2.1) or 2.2

[Tollef Fog Heen (tfheen)]

I can't reproduce it either (i386 and amd64). James, can you please try with a version that has OOo 2.2 (current feisty) to see if the problem is fixed there?

[James Troup (elmo)]

Ok, this is weird. I can't reproduce this either with a live CD. But I've upgraded to latest feisty and the problem persists on the installed system. I tried purging openoffice* and reinstalling it. I moved ~/.openoffice* out of the way. I tried purging my environment of everything except the essentials (PATH, DISPLAY, XAUTHORITY). None of it helps, it still fails 100% reliably for me on this installed system. I'd welcome any suggestions on anything else I can do to try and narrow this down.

[Henrik Nilsen Omma (henrik)]

I cannot reproduce this either. I've tried on an i386 system (my daily machine) and an amd64 fresh install. Tried turning on AT-SPI as that has caused weird OOo hangs in the past, but it works as normal.

[Tollef Fog Heen (tfheen)]

Bringing milestone forward

[Tollef Fog Heen (tfheen)]

What language packs and such do you have installed? Is this i386 or amd64?

[Matthias Klose (doko)]

removing the milestone; unreproducible on new installations.

[James Troup (elmo)]

Thankfully, this appears to have been fixed now.

[Of course, 'unreproducible on new installations' is a terrible reason to remove the milestone unless it's become official Ubuntu policy to not support upgrades ...]