Bug 54383 - : About dialog causing immediate crash
Summary: : About dialog causing immediate crash
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected) release
Hardware: Other All
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2012-09-02 11:02 UTC by Ondrej Machulda
Modified: 2013-10-25 15:16 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

backtrace gdb.log (12.02 KB, text/plain)
2012-09-02 11:02 UTC, Ondrej Machulda

Note You need to log in before you can comment on or make changes to this bug.
Description Ondrej Machulda 2012-09-02 11:02:13 UTC
Created attachment 66488 [details]
backtrace gdb.log

Problem description: 
Starting LO 3.6, the about dialog is not being shown but LO crashes instead.

Steps to reproduce:
1. Open any Libreoffice component
2. Menu: Help > About

Current behavior: LO crashes

Expected behavior: About dialog is shown

Platform (if different from the browser): 
X11; Gentoo Linux i686, KDE 4
Comment 1 Julien Nabet 2012-09-04 20:49:33 UTC
On pc Debian x86-64 with 3.6 sources updated today (so more equivalent 3.6.2 than, I don't reproduce the problem.
Comment 2 Julien Nabet 2012-10-19 22:51:05 UTC
Extra info are needed here:
- what Java version do you have?
- did you install any specific extensions?
- did you test after having renamed your LO profile (see http://wiki.documentfoundation.org/UserProfile)?
- do you reproduce this with LO 3.6.2?
Comment 3 Robert Nagy 2012-10-29 08:57:39 UTC
I've managed to reproduce this issue on OpenBSD as well, where LO has been installed on a virgin system.
The issue happens with java and without java as well. (as in disabled java at compile time).
According to my debugging there are no libraries missing.
The user profile has also been cleaned up each time I tried and there are no specific extensions installed at all.
Comment 4 Robert Nagy 2012-10-29 18:36:21 UTC
invokeComponentFactory envDcp:gcc3 implName:vcl::rsvg::Rasterizer modPath:file:///usr/local/lib/libreoffice/program/../program/libvcllo.so
### cannot activate factory: 
file:///usr/local/lib/libreoffice/program/../program/libvcllo.so: cannot get factory of demanded implementation: vcl::rsvg::Rasterizer
terminate called after throwing an instance of 'com::sun::star::loader::CannotActivateFactoryException'
Comment 5 Julien Nabet 2012-10-29 22:45:15 UTC
Just wondered if it could be linked with fdo#51694 (https://bugs.freedesktop.org/show_bug.cgi?id=51694).

Ondrej, Robert: Do you have Galaxy theme enabled? If yes, could you change the theme to something else and try again?
Comment 6 QA Administrators 2013-09-24 01:59:07 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team
Comment 7 QA Administrators 2013-10-25 15:16:54 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO