To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=109682
                 Issue #|109682
                 Summary|Launching OO 3.2 crashes on sigsegv (QSettings::sync: 
                        |filename is null/empty warnings)
               Component|framework
                 Version|OOO320m12
                Platform|PC
                     URL|
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|ui
             Assigned to|tm
             Reported by|bloody95





------- Additional comments from [email protected] Sun Feb 28 13:59:54 
+0000 2010 -------
I have just installed on FC12 OpenOffice 3.2 from openoffice.org. Version
3.1.1 installed in the same way was working fine.

When running version 3.2, I get the following lines and nothing more than
the splash screen :
/opt/openoffice.org3/program/soffice
QSettings::sync: filename is null/empty
QSettings::sync: filename is null/empty
QSettings::sync: filename is null/empty
QSettings::sync: filename is null/empty
QSettings::sync: filename is null/empty
QSettings::sync: filename is null/empty
/opt/openoffice.org3/program/soffice: line 131: 10510 Erreur de segmentation 
"$sd_prog/$sd_binary" "$@"

This happens with my regular account, running a simple window manager and
not the full gnome or kde desktop.

However, the crash does not happen when logged in with a user running under
gnome. It also does not happen if I 'su - <my account>' from this gnomed
user and start then soffice.

Seems like an error code has not been properly checked.

Regards,
-- 
    Thierry

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to