Bug 1046461 - kernel-3.12.6-300
Summary: kernel-3.12.6-300
Keywords:
Status: CLOSED DUPLICATE of bug 1046426
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-25 12:43 UTC by flashl
Modified: 2014-01-06 13:46 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-06 13:46:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description flashl 2013-12-25 12:43:08 UTC
Description of problem: xorg multi-display will not start


Version-Release number of selected component (if applicable): kernel-3.12.6-300


How reproducible: yum update packages:
kernel-3.12.6-300.fc20.x86_64
kernel-modules-extra-3.12.6-300.fc20.x86_64
kexec-tools-2.0.4-18.fc20.x86_64
libevdev-0.6-1.fc20.x86_64
kernel-headers-3.12.6-300.fc20.x86_64
kernel-debug-devel-3.12.6-300.fc20.x86_64

Steps to Reproduce:
1.
2.
3.

Actual results:
xorg multi-display will not start

Expected results: multi-display, multi-monitor output


Additional info:

Comment 1 Michele Baldessari 2013-12-25 22:12:21 UTC
There is zero information in this BZ to be able to help.

What graphic cards? What is the output of /var/log/Xorg.0.log and /var/log/messages

Did this work before? Is this a new setup?

Comment 2 flashl 2013-12-25 23:54:38 UTC
Configuration works with prior kernel versions. Solved problem by using yum history undo. Currently using  3.11.10-301.fc20.x86_64. Cards Intel i915 and Nvidia 9500GT.  No complaints found in Xorg.0.log or messages.  Do not reach greeting or login screen.

I can reinstall and capture any info you find helpful.

Comment 3 domgross 2013-12-26 01:11:57 UTC
This is not caused by the kernel update. I ran into the same issue earlier today, namely:

1) update using yum update -y, here is what was updated 

Packages Altered:
    Install kernel-3.12.6-300.fc20.x86_64         @updates-testing
    Install kernel-debug-3.12.6-300.fc20.x86_64   @updates-testing
    Install kernel-devel-3.12.6-300.fc20.x86_64   @updates-testing
    Updated kernel-headers-3.12.5-302.fc21.x86_64 @fedora-rawhide-kernel-nodebug
    Update                 3.12.6-300.fc20.x86_64 @updates-testing
    Updated kexec-tools-2.0.4-14.fc20.x86_64      @updates
    Update              2.0.4-18.fc20.x86_64      @updates-testing
    Updated libevdev-0.5-1.fc20.x86_64            @updates
    Update           0.6-1.fc20.x86_64            @updates-testing
    Updated wireshark-1.10.4-2.fc20.x86_64        @updates-testing
    Update            1.10.5-1.fc20.x86_64        @updates-testing


2) reboot
3) gnome will not start, no error message is printed to the console

The most likely culprit seemed to be libevdev, so I rolled back the update and updated everything except libevdev and voila everyting works. After an update of libevdev gnome is broken again. I will check logfiles now.

Comment 4 domgross 2013-12-26 01:43:23 UTC
$ journalctl -b -1 /usr/bin/gnome-session

-- Logs begin at Wed 2013-07-24 13:58:35 CEST, end at Thu 2013-12-26 02:31:51 CET. --
Dec 26 02:02:34 pressanykey gnome-session[1320]: Entering running state
Dec 26 02:02:34 pressanykey gnome-session[1320]: gnome-shell: symbol lookup error: /lib64/libclutter-1.0.so.0: undefined symbol: LIBEVDEV_READ_NORMAL
Dec 26 02:03:44 pressanykey gnome-session[1320]: (gnome-settings-daemon:1372): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

see:

http://cgit.freedesktop.org/libevdev/commit/libevdev/libevdev.h?id=661602fe3bd247a7a151f8d24f8b40e97c0c5402

Comment 5 domgross 2013-12-26 02:03:04 UTC
this seems to be a duplicate of #1046426

Comment 6 flashl 2013-12-26 13:41:53 UTC
(In reply to domgross from comment #3)
> This is not caused by the kernel update. I ran into the same issue earlier
> today, namely:
> 
> 1) update using yum update -y, here is what was updated 
> 
> Packages Altered:
>     Install kernel-3.12.6-300.fc20.x86_64         @updates-testing
>     Install kernel-debug-3.12.6-300.fc20.x86_64   @updates-testing
>     Install kernel-devel-3.12.6-300.fc20.x86_64   @updates-testing
>     Updated kernel-headers-3.12.5-302.fc21.x86_64
> @fedora-rawhide-kernel-nodebug
>     Update                 3.12.6-300.fc20.x86_64 @updates-testing
>     Updated kexec-tools-2.0.4-14.fc20.x86_64      @updates
>     Update              2.0.4-18.fc20.x86_64      @updates-testing
>     Updated libevdev-0.5-1.fc20.x86_64            @updates
>     Update           0.6-1.fc20.x86_64            @updates-testing
>     Updated wireshark-1.10.4-2.fc20.x86_64        @updates-testing
>     Update            1.10.5-1.fc20.x86_64        @updates-testing
> 
> 
> 2) reboot
> 3) gnome will not start, no error message is printed to the console
> 
> The most likely culprit seemed to be libevdev, so I rolled back the update
> and updated everything except libevdev and voila everyting works. After an
> update of libevdev gnome is broken again. I will check logfiles now.

I can confirm libevdev is culprit, however, messages from gnome in /var/log/messages is different: "Dec 26 07:31:53 blackheart gnome-session[2287]: WARNING: App 'gnome-shell.desktop' exited with code 127
Dec 26 07:31:53 blackheart gnome-session[2287]: WARNING: App 'gnome-shell.desktop' exited with code 127
Dec 26 07:31:53 blackheart gnome-session[2287]: WARNING: App 'gnome-shell.desktop' respawning too quickly"

Comment 7 Michele Baldessari 2013-12-26 17:41:15 UTC
If downgrading libevdev to 0.5-1.fc20 fixes it can you close this BZ as duplicate of 1046426 please?

Thanks,
Michele

Comment 8 Nemanja Andrejevic 2013-12-26 18:21:48 UTC
(In reply to domgross from comment #4)
> $ journalctl -b -1 /usr/bin/gnome-session
> 
> -- Logs begin at Wed 2013-07-24 13:58:35 CEST, end at Thu 2013-12-26
> 02:31:51 CET. --
> Dec 26 02:02:34 pressanykey gnome-session[1320]: Entering running state
> Dec 26 02:02:34 pressanykey gnome-session[1320]: gnome-shell: symbol lookup
> error: /lib64/libclutter-1.0.so.0: undefined symbol: LIBEVDEV_READ_NORMAL
> Dec 26 02:03:44 pressanykey gnome-session[1320]:
> (gnome-settings-daemon:1372): Gdk-WARNING **: gnome-settings-daemon: Fatal
> IO error 11 (Resource temporarily unavailable) on X server :0.
> 
> see:
> 
> http://cgit.freedesktop.org/libevdev/commit/libevdev/libevdev.
> h?id=661602fe3bd247a7a151f8d24f8b40e97c0c5402

I had exactly the same problem and i can confirm that downgrading libevdev to 0.5.1.fc20 helped me and now everything is ok.

Comment 9 Josh Boyer 2014-01-06 13:46:40 UTC

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


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