Bug 911200

Summary: [abrt] libreoffice-core-3.6.5.2-2.fc18: gdk_x11_window_set_user_time: Process /usr/lib64/libreoffice/program/soffice.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Seb L. <D8F55524>
Component: libreofficeAssignee: Caolan McNamara <caolanm>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: caolanm, dtardon, erack, jvromans, ltinkl, mstahl, sbergman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5884ff82a93af11736ba121b5619cdc6ff0f1c8f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-28 14:47:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Seb L. 2013-02-14 15:05:33 UTC 
Description of problem:
1. Start ooimpress
2. Create a new, blank presentation
3. Press [F5]
4. Crash

100% reproducible on every dual-head machine I tried it on.

Note: using (nvidia) dual-head configuration, with Xinerama disabled.

Version-Release number of selected component:
libreoffice-core-3.6.5.2-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/lib64/libreoffice/program/soffice.bin --impress --splash-pipe=6
crash_function: gdk_x11_window_set_user_time
executable:     /usr/lib64/libreoffice/program/soffice.bin
kernel:         3.7.4-204.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (1 frames)
 #0 gdk_x11_window_set_user_time at gdkwindow-x11.c:3726
Comment 1 Seb L. 2013-02-14 15:05:36 UTC 
Created attachment 697244 [details]
File: backtrace
Comment 2 Seb L. 2013-02-14 15:05:38 UTC 
Created attachment 697245 [details]
File: build_ids
Comment 3 Seb L. 2013-02-14 15:05:41 UTC 
Created attachment 697246 [details]
File: cgroup
Comment 4 Seb L. 2013-02-14 15:05:43 UTC 
Created attachment 697247 [details]
File: core_backtrace
Comment 5 Seb L. 2013-02-14 15:05:45 UTC 
Created attachment 697248 [details]
File: dso_list
Comment 6 Seb L. 2013-02-14 15:05:47 UTC 
Created attachment 697249 [details]
File: limits
Comment 7 Seb L. 2013-02-14 15:05:50 UTC 
Created attachment 697250 [details]
File: maps
Comment 8 Seb L. 2013-02-14 15:05:56 UTC 
Created attachment 697251 [details]
File: open_fds
Comment 9 Seb L. 2013-02-14 15:05:58 UTC 
Created attachment 697252 [details]
File: proc_pid_status
Comment 10 Seb L. 2013-02-14 15:06:01 UTC 
Created attachment 697253 [details]
File: var_log_messages
Comment 11 Caolan McNamara 2013-02-15 12:52:54 UTC 
I've seen reports of the "gdk_x11_window_set_user_time" crash before (see upstream bug linked, which has a better backtrace than this one). How exactly are you "disabling Xinerama", i.e. what's the step by step to reproducing your setup.
Comment 12 Seb L. 2013-02-28 14:58:07 UTC 
Dear Caolan,

Sorry for this late reply: I meant by "disabling Xinerama" that I have the following option set in my "ServerLayout" section of my xorg.conf file:
    Option         "Xinerama" "0"
(meaning that I do not want my desktop to span across my two displays but use them independently)

This is identical setup as this one:
  https://bugs.freedesktop.org/attachment.cgi?id=69308

This bug is 100% reproducible on my three nvidia dual-head x86_64 Fedora 18 machines (one is using a Quadro 2000, another a GeForce GT 220 and finally a GeForce 8800 GTS).

I am using the nvidia proprietary drivers, but Johan Vromans (who reported https://bugs.freedesktop.org/show_bug.cgi?id=56583 ) is using the nouveau driver with identical results.

Please do not hesitate to contact me for any test or further information.

Best regards,

Sébastien
Comment 13 Johan Vromans 2013-06-03 08:08:09 UTC 
I'm really surprised to find this issue "resolved as INSUFFICIENT DATA".
Comment 14 David Tardon 2013-06-03 09:38:41 UTC 
fair point