|
Bugzilla – Full Text Bug Listing |
| Summary: | crash if I interact with empathy - no one specific action causes the crash | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 13.1 | Reporter: | fire bird <firebird209> |
| Component: | X.Org | Assignee: | E-mail List <xorg-maintainer-bugs> |
| Status: | RESOLVED NORESPONSE | QA Contact: | E-mail List <xorg-maintainer-bugs> |
| Severity: | Critical | ||
| Priority: | P3 - Medium | CC: | dimstar, forgotten_aK8dWmgD-F, forgotten_cvUOoXEf7z, forgotten_DV81ZEWZkN, hvogel |
| Version: | RC 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
fire bird
2013-11-01 23:20:44 UTC
The crash seems to be in X itself. CCing sndirsch, who might have some insight alreeady. Fire Bird: can you get a full stack trace of this crash? Likely by configuring your system to create core dumps in a spec. location (I use /cores; world-writable and /cores/%e-%t-%u.core in /proc/sys/kernel/core_pattern (In reply to comment #1) > The crash seems to be in X itself. > > CCing sndirsch, who might have some insight alreeady. > > Fire Bird: can you get a full stack trace of this crash? Likely by configuring > your system to create core dumps in a spec. location (I use /cores; > world-writable and /cores/%e-%t-%u.core in /proc/sys/kernel/core_pattern Hi Dominique, I have a .core file generated (thanks for your help on how to do that) but I cannot attach it here as I'm told it exceeds 10MB in size. I was playing around some more with this last night (November 3, 2013) and it seems the issue could be stemming from the Adwaita theme.... I had been customizing things a bit the other day and switched to a Zukitwo theme (gnome shell, window decorations, gtk, etc.) and empathy worked quite well, it didn't crash or have the same behavior as with Adwaita, so, I then switched things back to Adwaita, restarted empathy, and the crash occurred again.... I'm not sure how to track a theme bug down, but just throwing that out there as some new information I've discovered with regards to this bug. I'd like to say that I'm experiencing the same bug on openSUSE 13.1. fire bird, can't you host the core dump at an external website? Maybe Dropbox or something? If not, I'll gladly try to generate a core dump myself. I believe that I have pinpointed the source of the problem. It has to do with the Intel driver. Both I and firebird (I spoke with him on IRC) are using Intel GPUs. The current version of the driver defaults to the newer SNA acceleration. This acceleration is still a little big buggy, e.g., it introduces some artifacts on Firefox: https://bbs.archlinux.org/viewtopic.php?id=168823 I experienced these artifacts while using an Arch Linux install a few days ago, and they are also present on openSUSE. However, since they do not occur very often and kept everything as it was. Due to this empathy bug I started I thought that if X11 crashes it may well be caused by a driver problem. So I decided to override the default SNA and switch to UXA. And this change fixed the problem. Moreover, firebird also said to me that he has another computer with an NVIDIA GPU that doesn't present this issue. After some close inspection, it seems that openSUSE 13.1 is currently using a pre-release of the future 3.0 version of xf86-video-intel. The current version was released 10 days ago (https://build.opensuse.org/package/view_file/openSUSE:13.1/xf86-video-intel/xf86-video-intel.changes?expand=1). This version is actually newer than the one used by Arch Linux (https://www.archlinux.org/packages/extra/x86_64/xf86-video-intel/) and was made available "about a week ago" as firebird mentioned on his initial report. All of this indicates that the problem is related to the x86-video-intel driver, especially when using the default SNA mode. Also, considering that the problem seems the be confined to GNOME when using the Adwaita theme (according to what firebird said), it may be the case that Adwaita uses some function at the GPU level that causes the crash, where some other GTK themes do not. So, it seems that the bug manifests itself when using xf86-video-intel (SNA mode) + Adwaita. If the problem only happens with Adwaita, it may be fixed by patching it. But patching/downgrading xf86-video-intel seems to be a more future proof solution (since whatever Adwaita is doing "kind of wrong" can in fact be made by some other untested GTK theme/application combo that may crash X11, which is something really critical. (In reply to comment #2) > I have a .core file generated (thanks for your help on how to do that) but I > cannot attach it here as I'm told it exceeds 10MB in size. I was playing around > some more with this last night (November 3, 2013) and it seems the issue could > be stemming from the Adwaita theme.... I had been customizing things a bit the > other day and switched to a Zukitwo theme (gnome shell, window decorations, > gtk, etc.) and empathy worked quite well, it didn't crash or have the same > behavior as with Adwaita, so, I then switched things back to Adwaita, restarted > empathy, and the crash occurred again.... I'm not sure how to track a theme bug > down, but just throwing that out there as some new information I've discovered > with regards to this bug. Uploading the .core file would not help.. what we need is a stack trace. using gdb, you can load the core file as 'reference' and do a stack trace based on that crash (instead of trying to reproduce the crash while running gdb). Anyway.. intel driver seems to be a good pointer already... (the initial crash did show it being in X after all.. not gnome). changing component to Xorg for now.. I have pretty much the same problem. Please cross check with bug 847941 & bug 847762 (especially whether the newer version resolves the problem) Still anyone of the affected users available? Otherwise better close this bug ... I don't use Empathy anymore, so i'm not sure. Anyway, not for me. Seems we no longer can expect a response here ... |