X11 crashes when opening LibreOffice

[rjasmin]

Ever since 14.04, X11 crashes when opening libreoffice, and the session is forced logged out.
---
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CasperVersion: 1.360
CurrentDesktop: KDE
DistroRelease: Ubuntu 15.04
LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
Package: xorg 1:7.7+7ubuntu4
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Tags: vivid
Uname: Linux 3.19.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Björn Michaelsen (bjoern-michaelsen)]

As this isnt reproduced elsewhere, needs reproduction step and hardware info.
Nothing LibreOffice does should be able to crash Xorg. As such, it is first and foremost a Xorg (or Xorg driver) bug, there is no clear evidence there is something illegal is requested from Xorg (and even if: it is still an Xorg bug, as nothing should crash Xorg).

[rjasmin (frazzledjazz)]

It has to do with the open sourced ATI driver. Im using an ATI HD7850, two of them. This is a problem for v14 as well. Ubuntu is the only distribution having this bug. Fedora and Debian do not have this issue. Gallium .4 works with this hardware.

This is a really odd bug because Fedora team have found a way to mimic the proprietary driver functions using open source ATI drivers.Im surprised they havent backported the changes so that debian based systems can benefit. Even OpenCL is supported this way. On other setups you need the fglrx packages installed for this to work correctly.

Also Im suprised that Debian has the lead lately with stretch. I thought ubuntu was based off of sid releases. You seem to be a tad behind.
I would have to try again with a live cd, as Im on debian. Will have to get back to yall.

[penalvch (penalvch)]

rjasmin, your crash report is missing.

Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this report since the process outlined above will deal with this issue more efficiently. Also, please do not attach your crash report manually to this report and reopen it. Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[rjasmin (frazzledjazz)]

apport information

[rjasmin (frazzledjazz)]

apport information

[rjasmin (frazzledjazz)]

apport information

[rjasmin (frazzledjazz)]

so then why the need for apport to handle it then? Kind of makes the whole bug reporting process useless, ya think? Besides Im getting a sigsev trying it. everything seems to be sigsev. Its all related to wiley, the bug is non-existant in tahir. So what to do about this mono bug that creeped in?