Bug 1224440 - Regression after F22_Beta_RC3. Live Workstation image boots to "Oh no!" error.
Summary: Regression after F22_Beta_RC3. Live Workstation image boots to "Oh no!" error.
Keywords:
Status: CLOSED DUPLICATE of bug 1228011
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-libinput
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-23 02:04 UTC by Luke Macken
Modified: 2016-09-20 02:46 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-28 15:57:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journal output of the gdm/gnome session (51.51 KB, text/plain)
2015-05-23 02:04 UTC, Luke Macken
no flags Details

Description Luke Macken 2015-05-23 02:04:16 UTC
Created attachment 1028974 [details]
journal output of the gdm/gnome session

Description of problem:


I'm hitting a regression on my Thinkpad X300 that was created between 22_Beta_RC3 and 22_RC1, and is still an issue with 22_RC3. I am unable to reproduce it on my newer Thinkpad.

Starting with RC1 the live Workstation boots to the "Oh no! Something has gnone wrong" gnome-shell error. On some attempts the Try/Install dialog pops up on top of it, but on some it doesn't.

This is the error:

gnome-session[1471]: X Error of failed request:  BadValue (integer parameter out of range for operation)    
gnome-session[1471]: Major opcode of failed request:  131 (XInputExtension)                                 
gnome-session[1471]: Minor opcode of failed request:  57 ()                                                 
gnome-session[1471]: Value in failed request:  0x113                                                        
gnome-session[1471]: Serial number of failed request:  267                                                  
gnome-session[1471]: Current serial number in output stream:  268                                           
gnome-session[1471]: gnome-session[1471]: WARNING: App 'gnome-shell.desktop' exited with code 1             


Version-Release number of selected component:

22_Beta_RC3 (works)
 - kernel-4.0.0-0.rc5.git4.1.fc22.x86_64
 - gnome-shell-3.16.0-1.fc22.x86_64
 - xorg-x11-server-Xorg-1.17.1-9.fc22.x86_64

22_RC1 (doesn't work)
 - kernel-4.0.0-1.fc22.x86_64
 - gnome-shell-3.16.1-1.fc22.x86_64
 - xorg-x11-server-Xorg-1.17.1-9.f22.x86_64

22_RC3 (doesn't work)
 - kernel-4.0.4-301
 - gnome-shell-3.16.2-1.fc22.x86_64
 - xorg-x11-server-Xorg-1.17.1-11.fc22.x86_64

Comment 1 Luke Macken 2015-05-23 19:23:49 UTC
CC'ing ajax, as this might be an X issue?

Comment 2 darrell pfeifer 2015-06-16 20:29:40 UTC
I have a similar problem (though no sure the minor opcode means it is different).

Using rawhide from today, so latest of everything.

Jun 16 11:09:55 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:
Jun 16 11:09:55 localhost.localdomain gnome-session[3774]: X Error of failed request:  BadValue (integer parameter out 
Jun 16 11:09:55 localhost.localdomain gnome-session[3774]: Major opcode of failed request:  131 (XInputExtension)
Jun 16 11:09:55 localhost.localdomain gnome-session[3774]: Minor opcode of failed request:  57 ()
Jun 16 11:09:55 localhost.localdomain gnome-session[3774]: Value in failed request:  0x11c
Jun 16 11:09:55 localhost.localdomain gnome-session[3774]: Serial number of failed request:  266
Jun 16 11:09:55 localhost.localdomain gnome-session[3774]: Current serial number in output stream:  267
Jun 16 11:09:55 localhost.localdomain gnome-session[3774]: gnome-session[3774]: WARNING: App 'gnome-shell.desktop' exit
Jun 16 11:09:55 localhost.localdomain gnome-session[3774]: WARNING: App 'gnome-shell.desktop' exited with code 1

Comment 3 Milan Bouchet-Valat 2015-06-28 15:49:52 UTC
Seeing the same here on up-to-date F22. Removing xorg-x11-drv-libinput fixes it.

Comment 4 Milan Bouchet-Valat 2015-06-28 15:57:20 UTC
I think this is probably a duplicate of Bug 1228011, which was just fixed in updates-testing, and fixes the error for me.

*** This bug has been marked as a duplicate of bug 1228011 ***


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