Apache OpenOffice (AOO) Bugzilla – Issue 75421
Crash when changing to fullscreen/windowed mode
Last modified: 2008-06-13 15:43:17 UTC
The crash I describe is frequent, and it is present in ubuntu where I reported it originally. This crash is seriously mining openoffice popularity, since ubuntu users are now a huge part of the gnu/linux users, and what you often hear from them is that "openoffice crashes too often". The crash description follows follows, and it is definitely the most frequent for me in impress. It is also reported at https://launchpad.net/ubuntu/+source/openoffice.org/+bug/69244 I open a presentation that I have, and keep pressing "F5-ESC-PGDOWN" at random until I make impress crash with the following backtrace. This does not happen with an empty presentation so I can provide mine if needed. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1246775104 (LWP 13432)] 0xb7c93efd in MapMode::MapMode () from /usr/lib/openoffice/program/libvcl680li.so (gdb) bt #0 0xb7c93efd in MapMode::MapMode () from /usr/lib/openoffice/program/libvcl680li.so #1 0xadeed9dc in SvxTextEditSource::getRanges () from /usr/lib/openoffice/program/libsvx680li.so #2 0xadeeda6c in SvxTextEditSource::GetVisArea () from /usr/lib/openoffice/program/libsvx680li.so #3 0xadf79b80 in accessibility::AccessibleTextHelper::GetAt () from /usr/lib/openoffice/program/libsvx680li.so #4 0xadf7a885 in accessibility::AccessibleTextHelper::UpdateChildren () from /usr/lib/openoffice/program/libsvx680li.so #5 0xadf7b430 in accessibility::AccessibleTextHelper::UpdateChildren () from /usr/lib/openoffice/program/libsvx680li.so #6 0xb7b6e9e8 in SfxBroadcaster::Broadcast () from /usr/lib/openoffice/program/libsvl680li.so #7 0xadeee77b in SvxTextEditSource::removeRange () from /usr/lib/openoffice/program/libsvx680li.so #8 0xb7b6e9e8 in SfxBroadcaster::Broadcast () from /usr/lib/openoffice/program/libsvl680li.so #9 0xae00cee6 in SdrObject::BroadcastObjectChange () from /usr/lib/openoffice/program/libsvx680li.so #10 0xae00d270 in SdrObject::SetOutlinerParaObject () from /usr/lib/openoffice/program/libsvx680li.so #11 0xac5d9c03 in SdDrawDocument::GetDefaultWritingMode () from /usr/lib/openoffice/program/libsd680li.so #12 0xac5db70d in SdDrawDocument::GetDefaultWritingMode () from /usr/lib/openoffice/program/libsd680li.so #13 0xac5db758 in SdDrawDocument::GetDefaultWritingMode () from /usr/lib/openoffice/program/libsd680li.so #14 0xb7c2d01c in Timer::Timeout () from /usr/lib/openoffice/program/libvcl680li.so #15 0xb7c2d209 in Timer::ImplTimerCallbackProc () from /usr/lib/openoffice/program/libvcl680li.so #16 0xb569484a in X11SalData::Timeout () from /usr/lib/openoffice/program/libvclplug_gen680li.so #17 0xb5a884c6 in GtkXLib::timeoutFn () from /usr/lib/openoffice/program/libvclplug_gtk680li.so #18 0xb5a88501 in call_timeoutFn () from /usr/lib/openoffice/program/libvclplug_gtk680li.so #19 0xb5cb9dd6 in g_source_get_current_time () from /usr/lib/libglib-2.0.so.0 #20 0xb5cb9802 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #21 0xb5cbc7df in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #22 0xb5cbcd45 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #23 0xb5a8a201 in GtkXLib::Yield () from /usr/lib/openoffice/program/libvclplug_gtk680li.so #24 0xb569e037 in X11SalInstance::Yield () from /usr/lib/openoffice/program/libvclplug_gen680li.so #25 0xb7c26f08 in Application::Yield () from /usr/lib/openoffice/program/libvcl680li.so #26 0xb7c26fdc in Application::Execute () from /usr/lib/openoffice/program/libvcl680li.so #27 0x0806d8c7 in desktop::Desktop::Main () #28 0xb7c2cc2c in InitVCL () from /usr/lib/openoffice/program/libvcl680li.so #29 0xb7c2cd35 in SVMain () from /usr/lib/openoffice/program/libvcl680li.so #30 0x0805fdc3 in sal_main () #31 0x0805fe46 in main ()
Created attachment 43721 [details] Presentation where the bug manifests
I forgot to mention that 'keep pressing "F5-ESC-PGDOWN"' is obviously not the bug circumstance, but only a recipe to reproduce it.
Is this happening in the OOo version delivered by Ubuntu? In this case we cannot do anything about it. Ubuntu is the right place to write the bug to. In your link I saw a comment that this only happens under GNOME, not KDE. Is that right? This is a very important piece of information.
Reassigned.
Using 2.2RC3 I have stepped throughout FUSE.odt twice - no crash. Using Novell's 2.04 on Suse 10.2 I got crash on first F5-Esc. Resolving as fixed.
And closing. BTW, I have tested on Gnome.
Sorry for delaying my reply, I am very busy these days. Something has changed, you're right, but the bug is perhaps still manifesting: if I open FUSE.odt and then close ooo, (version 2.2 gnome, on ubuntu), everything is fine, while if I open it, then press F5, then press ESC, then close the window, the program crashes. I don't have time to test under kde and to install dbg packages and report a backtrace today, I am leaving for a conference. If you can't reproduce it yourself, I will provide more information when I'll be back (in the first week of april). If you think this should be reported as a different issue close this, but I would get a backtrace before, because it seems to me that it might be the same problem.
As far as I know Ubuntu build the office by their own therefore I think that's a bug in the Ubuntu build of OOo. Please tell me if the bug also occurs in the 'official' OOo build from Openoffice.org.
I can't find neutral linux binaries (e.g. tgz binary archives), only rpms that I can't install it seems. However, I realize that you already closed the report with "worksforme" but can you please confirm that just opening fuse.odp under gnome, then pressing F5, then ESC, then closing the window does NOT make openoffice crash on your machine? Moreover, I can't find instructions on how to get a backtrace of ooimpress, I installed the relevant debug package but need to know how to run gdb on the real binary.
The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew
These crashes almost certainly with accessibility enabled, which might be the magic trigger
found it, reopening to set as duplicate
set as duplicate *** This issue has been marked as a duplicate of 90697 ***
close as duplicate