Summary: | Segfault in nouveau_dri.so | ||
---|---|---|---|
Product: | Mesa | Reporter: | sune |
Component: | Drivers/DRI/nouveau | Assignee: | Nouveau Project <nouveau> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | high | CC: | kristian, ungift-ed |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | backtrace |
Description
sune
2013-03-14 19:17:59 UTC
Same on Gentoo and mesa-9999 (~ 2-3 weeks) Created attachment 76541 [details]
backtrace
gdb /usr/bin/gnome-shell
run
bt full
I've been rather conservative in specifying the importance, but since it precludes, and apparently Ungifted, from using any form of 3D-accelerated desktop environment, I don't feel wrong in bumping it up a few notches... I can also confirm this bug, same error. Nvidia GeForce 8600 GT on Arch Linux tested with mesa from git today (22/3) and 11/3. [ 21.613812] gnome-shell[431]: segfault at 1 ip 00007fb252ea8465 sp 00007fff9e19bc00 error 4 in nouveau_dri.so[7fb252968000+121b000] (In reply to comment #1) > Same on Gentoo and mesa-9999 (~ 2-3 weeks) Today: I'm on kernel 3.9-rc5 (was 3.8) / gnome 3.8 (was 3.6) / mesa and nouveau (current git). Seems works fine now. I can also confirm i dont have this "bug" more.. Therefor i set it as Fixed Just wanted to chime in with support for "RESOLVED FIXED" status. Incidentally, as the reporter, I specified where I got my packages from. What seems to have effected the fixing for me, was a new (package) release of the libdrm-nouveau(2?) package. (In reply to comment #7) > Just wanted to chime in with support for "RESOLVED FIXED" status. > > Incidentally, as the reporter, I specified where I got my packages from. > What seems to have effected the fixing for me, was a new (package) release > of the libdrm-nouveau(2?) package. I have not updated libdrm just "mesa"/"nouveau" from git. So for me it seems like it have been fixed in mesa. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.