This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours

Bug 682034

Summary: LibreOffice Base Doesn't Launch
Product: [Fedora] Fedora Reporter: David Le Sage <dlesage>
Component: libreofficeAssignee: Caolan McNamara <caolanm>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: caolanm, dtardon, ItSANgo, ltinkl
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-04 04:05:29 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Attachments:
Description Flags
Error message that appears when I try to run Base. none

Description David Le Sage 2011-03-03 19:09:24 EST
Created attachment 482181 [details]
Error message that appears when I try to run Base.

Description of problem:
Base fails to launch. An error dialogue appears.

Version-Release number of selected component (if applicable):
libreoffice-base-3.3.1.2-1.fc15.x86_64


How reproducible:
Every time.

Steps to Reproduce:
1. Log into GNOME Shell
2. yum install libreoffice-base
3. Go into the GNOME Shell overlay's applications tab and launch Base.
  
Actual results:
Error message (see attached screenshot.)

Expected results:
Base moduel should launch.

Additional info:
Comment 1 David Le Sage 2011-03-03 19:14:11 EST
Actually, this is more complicated than I first though.  When I tried to run it and received that error, Calc was already running.

Now that I have exited Calc, Base launches.  I just shut down Base and loaded Calc again.  Base now starts every time so I cannot reproduce the error I was receiving consistently before.
Comment 2 Caolan McNamara 2011-03-04 04:05:29 EST
If calc was running, then base installed, and then an attempt to launch base that would probably explain it, given the single process nature of LibO the new process asks the old process to open a base window and the old process doesn't know about base seeing as it wasn't installed when it was launched.

Would be nice to fix this edge-case, but its not as critical as the gazillion other bugs we have, so I guess we can live with it.