Bug 48049 - BASIC: Arch Linux error_code 5 request_code 17 minor_code 0
Summary: BASIC: Arch Linux error_code 5 request_code 17 minor_code 0
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
(earliest affected)
3.5.1 RC1
Hardware: Other All
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2012-03-29 07:14 UTC by ninquitassar
Modified: 2012-10-27 11:08 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description ninquitassar 2012-03-29 07:14:28 UTC
Problem description: In my Arch Linux System "libreoffice", "libreoffice --sync" or "libreoffice --nologo" commands run the splash and immediatly the program crashes. Then it returns the following error:

The program 'soffice' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 191 error_code 5 request_code 17 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.)

NOTE: 3.4 version works perfectly on my system

Steps to reproduce:
1. Open the terminal
2. Launch "libreoffice"

Current behavior: the program doesn't work and crash immediatly

Expected behavior: the program works

System: Arch Linux with WMFS window manager on X
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0
Comment 1 sasha.libreoffice 2012-06-22 03:36:04 UTC
Thanks for bugreport
Please, verify if in last version of LibreOffice still reproducible

Try also on one of this if possible: Ubuntu, Fedora, OpenSUSE.
Comment 2 Julien Nabet 2012-10-27 11:08:01 UTC
Since there has been no feedback and I don't reproduce it with 3.5 sources updated today (on pc Debian x86-64), I put it as WFM.

ninquitassar: if you still reproduce the crash with a newer version, don't hesitate to reopen this tracker.
If so, a backtrace with symbols could be very useful (see