Bug 46965 - CTRL+F or Choosing FIND from the MENU causes Libre Office to Crash
Summary: CTRL+F or Choosing FIND from the MENU causes Libre Office to Crash
Status: RESOLVED DUPLICATE of bug 46687
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: x86 (IA32) Linux (All)
: medium blocker
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-04 12:01 UTC by vermontpoet
Modified: 2012-03-05 09:06 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vermontpoet 2012-03-04 12:01:16 UTC
As per the summary, choosing CTRL+F or FIND from the MENU causes Libre Office to crash - as if the app had been "killed". Am using Xubuntu 11.04 32 bit. 

LibreOffice 3.5.0 
Build ID: 350m1(Build:13)

This bug is reproducible at will, on my system, and in any document. The bug kills all instances of Libre Office.

I have not tried logging off and back in.
Comment 1 vitriol 2012-03-04 12:06:33 UTC
Related/duplicate of Bug 46687?
Comment 2 vermontpoet 2012-03-04 12:09:46 UTC
I may have solved the problem.

I had been using Cairo Dock to start Libre Office. After the upgrade to 3.5, I continued to use the same launcher that I had used with the previous version. Once I deleted the launcher and called on LibreOffice from the main menu (recreating the launcher with the new instance) I haven't been able to reproduce the bug.

The issue appears to have been a version conflict?
Comment 3 vermontpoet 2012-03-04 12:12:50 UTC
Oh, never mind. The bug is back. CTRL+F is like sending a killall command.
Comment 4 vermontpoet 2012-03-04 12:17:12 UTC
OK, running Libre Office in Terminal resulted in the following:

The program 'soffice' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 33499 error_code 8 request_code 42 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


This is beginning to get above my pay grade. I noticed after restarting Libre Office after the last crash, the FIND dialogue window was opened on restart. So... No more messages from me unless I really have something new or helpful to add.
Comment 5 reporter_of_bugs 2012-03-04 22:04:26 UTC
LibreOffice 3.5.1.1 
Build ID: 45a2874-aa8c38d-dff3b9c-def3dbd-62463c8 downloaded from libreoffice.org 
4GB RAM AMD Phenom II 4x925
Xorg 11.0  1.10.4 (11004000)
GeForce GTS 450 NVIDIA Driver Version:280.13
Ubuntu 11.10 Gnome Shell 

This happens to me also. With a blank new document or existing.
Run from the terminal:

The program 'soffice' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 18955 error_code 8 request_code 42 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Comment 6 reporter_of_bugs 2012-03-04 22:35:31 UTC
Launching from terminal with:

 /opt/libreoffice3.5/program/soffice --sync &

seems to solve the problem. Ctrl + F and Find from the menu work as expected.
Comment 7 vermontpoet 2012-03-05 05:38:50 UTC
So far, running Libreoffice with the --sync command also works for me. I added the command to my launcher. And for those, like me, who have no clue as to what --sync does, I found this:

"What the X client code by default does is keep throwing requests as your code
generates them, but *NOT* waiting for replies.  This allows for much faster
operation, but has the drawback that if an X error is reported by the server, it
will come back later and be reported against some OTHER X call.

--sync disables the pipelining by calling XSync(), so each request waits for its
matching reply.  Performance drops considerably, but errors are reported on the
actual call that caused the problem."
Comment 8 Petr Mladek 2012-03-05 09:06:22 UTC
It seems to be duplicate of the bug #46687.

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