| Summary: | OOimpress2 crashes after Slideshow | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Santiago Gala <sgala> |
| Component: | New packages | Assignee: | Gentoo Office Team <office> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | crashfix | ||
|
Description
Santiago Gala
2007-04-19 18:36:03 UTC
I meant Alt-F C, but X works for me too :) I can reproduce that. Still: Could you file that upstream? where is upstream? Novell? if so URL Sun? ditto I spend hours looking for the diverse and moving locations of openoffice.org bugzillas, just to be told that I used the wrong one after that. I read recently in some bug that we were not using "official" sources, but the old-ximian-now-i-don't-know-how-is-called build. (In reply to comment #3) > where is upstream? > > Novell? if so URL https://bugzilla.novell.com/index.cgi > Sun? ditto http://qa.openoffice.org/ > I spend hours looking for the diverse and moving locations of openoffice.org > bugzillas, just to be told that I used the wrong one after that. It's actually not THAT complicated, if the bug is reproducable in openoffice-bin > OOo issuezilla, if not: Novell (and ours for both, so that we know). Normaly I point people directly to the right URL, in this case I just thought you would know, as I remembered you from earlier bug reports. > I read recently in some bug that we were not using "official" sources, but the > old-ximian-now-i-don't-know-how-is-called build. > That's not quite true. It's more like: We use the official source, plus a bunch of patches from ooo-build. But yes: It's not an unmodified OpenOffice.org, which complicates the bug reporting process a fair bit. openoffice-bin is not amd64, but runs in 32-bits compat mode, so I dont think the crash will be there. I have not installed it so I can't test (openoffice and openoffice-bin block each other). Anybody can test with a binary build? or a native build on a 32 bit platform. I think there is no official amd64/x86_64 build at oo.o, so this leaves us with novell. Their bugzilla does not allow me to login with the password they gave me. See? it is not that simple :( It is known to ooo-build devs, see thread: http://lists.ximian.com/pipermail/openoffice/2007-April/002252.html Though, there is no solution. Just known to be caused by system components. http://lists.ximian.com/pipermail/openoffice/2007-April/002257.html Created attachment 116844 [details, diff]
crashfix
Well, no real fix. Rather a hack to hide the segfault.
Upstream should decide what has to be done to fix this.
The 2.2.0-ebuild is now using a newer ooo-build snapshot, which incorporates the fix by Hanno (which also corrects the problem for me), great catch, thanks. Closing. |
