Issue 70450 - Crash OOo start on Fedora Core 5
Summary: Crash OOo start on Fedora Core 5
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Native-Lang
Classification: NLC
Component: www (show other issues)
Version: OOo 2.0
Hardware: All Linux, all
: P1 (highest) Trivial
Target Milestone: ---
Assignee: caolanm
QA Contact: issues@es
URL:
Keywords: crash, needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2006-10-15 15:23 UTC by diablo70
Modified: 2012-01-31 01:21 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description diablo70 2006-10-15 15:23:21 UTC
Video Driver is probably: nv
Desktop is: not GNOME
libgcj version is: libgcj-4.1.1-1.fc5
kernel is: Linux 2.6.17-1.2187_FC5 #1 Mon Sep 11 01:17:06 EDT 2006 i686 athlon i386
OpenOffice.org core rpm version is: openoffice.org-core-2.0.2-5.19.2
accessibility is: false
...start sestatus details ...
SELinux status:                 enabled
SELinuxfs mount:                /selinux
Current mode:                   enforcing
Mode from config file:          enforcing
Policy version:                 20
Policy from config file:        targeted
...end sestatus details ...
0x5607640: /usr/lib/openoffice.org2.0/program/libuno_sal.so.3 + 0x1e640
0x5607e80: /usr/lib/openoffice.org2.0/program/libuno_sal.so.3 + 0x1ee80
0x981420:  + 0x420 (__kernel_sigreturn + 0x0)
0x3f11aa: /usr/lib/openoffice.org2.0/program/libucbhelper3gcc3.so + 0x461aa
(ucbhelper::cancelCommandExecution(com::sun::star::ucb::IOErrorCode,
com::sun::star::uno::Sequence<com::sun::star::uno::Any> const&,
com::sun::star::uno::Reference<com::sun::star::ucb::XCommandEnvironment> const&,
rtl::OUString const&,
com::sun::star::uno::Reference<com::sun::star::ucb::XCommandProcessor> const&) +
0x174)
0xa56f2f: /usr/lib/openoffice.org2.0/program/libucpfile1.so + 0x2df2f
0xa4830a: /usr/lib/openoffice.org2.0/program/libucpfile1.so + 0x1f30a
0xa353c7: /usr/lib/openoffice.org2.0/program/libucpfile1.so + 0xc3c7
0xa37a2f: /usr/lib/openoffice.org2.0/program/libucpfile1.so + 0xea2f
0x3c5411: /usr/lib/openoffice.org2.0/program/libucbhelper3gcc3.so + 0x1a411
0x3c5d7f: /usr/lib/openoffice.org2.0/program/libucbhelper3gcc3.so + 0x1ad7f
(ucb::Content::executeCommand(rtl::OUString const&, com::sun::star::uno::Any
const&) + 0x4b)
0x6be65c: /usr/lib/openoffice.org2.0/program/libutl680li.so + 0x4465c
(utl::UCBContentHelper::Kill(String const&) + 0xde)
0x88ae9f: /usr/lib/openoffice.org2.0/program/libsoffice.so + 0x2fe9f
(desktop::Desktop::CreateTemporaryDirectory() + 0x243)
0x88bb3a: /usr/lib/openoffice.org2.0/program/libsoffice.so + 0x30b3a
(desktop::Desktop::RegisterServices(com::sun::star::uno::Reference<com::sun::star::lang::XMultiServiceFactory>&)
+ 0x6f4)
0x87db6c: /usr/lib/openoffice.org2.0/program/libsoffice.so + 0x22b6c
(desktop::Desktop::Main() + 0x1a8)
0x49f84a: /usr/lib/openoffice.org2.0/program/libvcl680li.so + 0x8684a
0x49f8fd: /usr/lib/openoffice.org2.0/program/libvcl680li.so + 0x868fd (SVMain()
+ 0x2b)
0x878e53: /usr/lib/openoffice.org2.0/program/libsoffice.so + 0x1de53 (sal_main +
0x57)
0x878e9f: /usr/lib/openoffice.org2.0/program/libsoffice.so + 0x1de9f (main + 0x27)
0x1574e4: /lib/libc.so.6 + 0x154e4 (__libc_start_main + 0xdc)
0x80484d1: /usr/lib/openoffice.org2.0/program/simpress.bin + 0x4d1
Comment 1 aziem 2006-10-15 18:51:57 UTC
diablo70: Since Fedora Core modifies their OpenOffice.org, could you test
whether the crash also happens with the latest official version from
http://download.openoffice.org ?

I am on Fedora Core 5 and haven't had problem with any version including OOo 2.0.4.
Comment 2 Olaf Felka 2006-11-01 08:11:07 UTC
@ cmc: Any idea about this? That's not a problem with native OOo builds.
Comment 3 caolanm 2006-11-01 08:27:36 UTC
looks like the first UNO exception, which goes through the bridge code. FC-5 is
selinux enabled, so a default upstream build will die around here as well. The
FC-5/FC-6 one should not, so...

can you strace /usr/lib/openoffice.org2.0/program/soffice.bin > /tmp/ooorun.log
2.&1 and attach the output here.

It's possible that you have /home mounted in such a way that a file created on
it cannot be mmaped read/write, i.e. this *might* be
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=212988
it depends on the output of the strace what the problem is.
Comment 4 caolanm 2006-11-09 13:00:36 UTC
I'd say it's https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=212988, and
"invalid" for upstream, though upstream won't start on enforcing selinux so it's
not the case of a fedora change for the sake of it. 

Fix will be in next fedora update
Comment 5 caolanm 2006-11-09 13:11:54 UTC
closing