Bug 1046533 - gdm doesn't start after updating fedora 20 (updates-testing) on an AMD/ATI FirePro M4000 card
Summary: gdm doesn't start after updating fedora 20 (updates-testing) on an AMD/ATI Fi...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 20
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-26 03:14 UTC by Rodrigo Paz
Modified: 2014-06-12 16:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-16 01:48:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rodrigo Paz 2013-12-26 03:14:35 UTC
Description of problem:
Today, after updating F20 using updates-testing repo I cannot have X working. After booting I just have the screen with the boot log messages. 

Version-Release number of selected component (if applicable):
kernel-3.12.6-300.fc20.x86_64
xorg-x11-drv-ati-7.2.0-3.20131101git3b38701.fc20.x86_64

How reproducible:
deterministic

Steps to Reproduce:
1. update fedora 20 using uppdates-testing
2. reboot

Actual results:
no gdm screen, just boot log messages

Expected results:
gdm login screen

Comment 1 Jussi Eloranta 2013-12-26 06:19:28 UTC
Same problem here. Happens also on intel graphics so probably not ati related.

Comment 2 Jussi Eloranta 2013-12-26 06:22:15 UTC
Forgot to mention: tried also to boot with older kernels, the same issue. I also tried to downgrade xorg* and mesa* but that did not help either.

Comment 3 Jussi Eloranta 2013-12-26 07:32:12 UTC
OK, I found the update that caused this. If I downgrade libevdev from 0.6 back to 0.5, I get the login screen again.

Comment 4 Rodrigo Paz 2013-12-26 07:53:22 UTC
Thanks Jussi for the hint. I tried downgrading libevdec (and also xorg* and mesa*) and It didn't work for me.
Also, I tried installing ATI propietary drivers having the same result.

Comment 5 Jussi Eloranta 2013-12-26 07:58:53 UTC
I have everything updated (from updates-testing) except left libevdev at 0.5. I am not sure if it matters but I have also selinux disabled in /etc/grub2.cfg (i.e., kernel parameter selinux=0). By the way, I have an ATI card on this computer (not the same model as yours though):

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550]

Comment 6 Todd Mokros 2013-12-26 08:06:01 UTC
Same issue here with nvidia graphics, with both nouveau and nvidia binary drivers.

Comment 7 Rodrigo Paz 2013-12-26 08:10:16 UTC
Jussi, I have tried everything up-to-date against updates-testing, except libevdev and selinux off, with same result.

Comment 8 Jussi Eloranta 2013-12-26 08:12:17 UTC
These must be then two separate issues... :-(

Comment 9 Todd Mokros 2013-12-26 08:27:52 UTC
After downgrading to libevdev-0.5-1.fc20.x86_64 I am able to start X here.

Comment 10 Rodrigo Paz 2013-12-27 03:45:21 UTC
After 2 days trying different approaches with this bug/crash, Fedora 20 is unusable for me. I cannot work on my laptop and I am flying abroad tomorrow. I used RH & Fedora since 1997 without major problems but this time this issue  (and other bugs I posted) is so annoying and frustrating to me. I do not want to migrate to another distribution, but today I seriously think about it.

Comment 11 Jussi Eloranta 2013-12-27 04:04:53 UTC
Did your system work before going to updates-testing (i.e., just with regular updates)? Things break from time to time with updates-testing. But I agree, F20 seems to be rather buggy at least for now and my production systems will stay at F19 for the moment.

Comment 12 Rodrigo Paz 2013-12-27 05:20:30 UTC
Yes Jussi,
it worked OK until yesterday changes in updates-testing. Before that, it was working OK enabling/disabling updates-testing repo.
You are right, I always run one-previous fedora release on production machines, but this time I had confidence. Thanks :-)

Comment 13 Rodrigo Paz 2013-12-27 05:23:16 UTC
I forgot to mention that previous kernels I have suffer the same problems.

Comment 14 Rodrigo Paz 2013-12-31 18:56:03 UTC
Yesterday, there was an update in libselinux (libselinux-2.2.1-6.fc20.x86_64) that seems to fix my problem with ati drivers.
Thanks guys for the hints


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