Bug 561465

Summary: [abrt] crash in osl_systemPathRemoveSeparator
Product: [Fedora] Fedora Reporter: niemcu <michal.deszcz>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: caolanm, dtardon, jpate22
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:b5e218e3c46db086930053bd927e6182f0fecd58
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-09 14:17:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description niemcu 2010-02-03 17:38:12 UTC 
abrt 1.0.4 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/soffice.bin -nologo -norestore -view /tmp/plugtmp-3/plugin-7453191,zalacznik.html
comment: Selinux wykrył błąd przy zamknięciu OOo, kiedy zostały zapisane dany dokumentu.
component: openoffice.org
executable: /usr/lib/openoffice.org3/program/soffice.bin
kernel: 2.6.31.12-174.2.3.fc12.i686
package: openoffice.org-brand-1:3.1.1-19.14.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)
Comment 1 niemcu 2010-02-03 17:38:18 UTC 
Created attachment 388571 [details]
File: backtrace
Comment 2 David Tardon 2010-02-03 18:13:51 UTC 
Translated comment (google translate): Selinux detected an error when you close OOo, you have saved the document.

dtardon->michal.deszcz: This bug was already reported once, but we couldn't get any clue about what caused it from the reporter at that time. Could you reproduce it? If yes, how? The automatically translated comment is not too clear...
Comment 3 David Tardon 2010-02-03 18:17:02 UTC 
dtardon->michal.deszcz: It should have been 'Can you reproduce it?', of course... And another question: what is the output of sestatus?
Comment 4 Caolan McNamara 2010-02-04 09:39:07 UTC 
*** Bug 556627 has been marked as a duplicate of this bug. ***
Comment 5 Caolan McNamara 2010-02-09 14:17:41 UTC 
There's a number of people on CC here, someone must be able to show us how to reproduce this. If you know how to reproduce this then feel free to reopen and add that information.
Comment 6 niemcu 2010-02-10 16:41:58 UTC 
I'm sorry, but I don't know how to reproduce this bug.
Output of sestatus is:

[m@krainaozz ~]$ sestatus
SELinux status:                 enabled
SELinuxfs mount:                /selinux
Current mode:                   enforcing
Mode from config file:          enforcing
Policy version:                 24
Policy from config file:        targeted
Comment 7 Caolan McNamara 2010-04-09 13:30:11 UTC 

*** This bug has been marked as a duplicate of bug 580596 ***