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
Created attachment 697244 [details] File: backtrace
Created attachment 697245 [details] File: build_ids
Created attachment 697246 [details] File: cgroup
Created attachment 697247 [details] File: core_backtrace
Created attachment 697248 [details] File: dso_list
Created attachment 697249 [details] File: limits
Created attachment 697250 [details] File: maps
Created attachment 697251 [details] File: open_fds
Created attachment 697252 [details] File: proc_pid_status
Created attachment 697253 [details] File: var_log_messages
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.
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
I'm really surprised to find this issue "resolved as INSUFFICIENT DATA".
fair point