Bug 755684 - gnome-shell segfault with kmod-catalyst
Summary: gnome-shell segfault with kmod-catalyst
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 16
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-21 19:03 UTC by Gwendal
Modified: 2013-02-13 20:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 20:04:13 UTC
Type: ---


Attachments (Terms of Use)

Description Gwendal 2011-11-21 19:03:30 UTC
Description of problem:

After installing kmod-catalyst (on a fresh Fedora 16 install, updated), the wallpaper shows up with the cursor, but right before the login application pops, an error screen appears (fullscreen) that says something like "Something went wrong. Please contact your system admin." with a sad computer face (my screen is in french).

When i'm stuck there, if I do alt+F2, login as root and enters 'dmesg', one of the last messages is :

Nov 21 18:06:58 goudurix kernel: [   37.887192] gnome-shell[1496]: segfault at 0 ip 04a6ced6 sp bf923140 error 4 in libc-2.14.90.so[49ed000+1a5000]


How reproducible:

Steps to Reproduce:
1. Install Fedora 16 + set rpmfusion repos
2. yum update
3. yum install kmod-catalyst
4. Reboot - the crash fullcreen appears at startup
  

Additional info:

I tried to disable gnome-shell by doing this :

dbus-launch gsettings set org.gnome.desktop.session session-name 'gnome-fallback'

But it did not change anything.

Comment 1 Gwendal 2011-11-28 21:01:54 UTC
I did a yum update, which updated ... a lot of things. But the problem wasn't solved.

One more thing to add to the report : I could boot and do whatever I wanted with gnome shell before trying to use the proprietary catalyst drivers (and I need those =( ).

Comment 2 Gwendal 2011-12-13 10:59:28 UTC
Yum update today, removal of kmod-catalyst and installation of akmod-catalyst (because new kernel version and no kmod-catalyst available).

And no changes, same segfault with gnome-shell + crash screen.

Comment 3 Gwendal 2011-12-17 17:30:04 UTC
Updated today (because new kernel and many updates available), and still crashing with the same segfault in the logs.

Comment 4 Gwendal 2011-12-18 18:23:59 UTC
Today I did a 'yum remove gnome-shell', and I have access to the login screen at last after rebooting.

If you want me to try anything to solve the bug, or if you need additionnal information, I can re-install gnome-shell.

Comment 5 Fedora End Of Life 2013-01-16 16:25:19 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Fedora End Of Life 2013-02-13 20:04:17 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.