Trying to run on a Samsung 700T tablet I see a huge number (5000) of messages in session.log: (gnome-settings-daemon:686): wacom-plugin-WARNING **: Automatically mapping tablet to heuristically-found display. (gnome-settings-daemon:686): wacom-plugin-WARNING **: Automatically mapping tablet to heuristically-found display. (gnome-settings-daemon:686): wacom-plugin-WARNING **: Automatically mapping tablet to heuristically-found display. Gnome fails to start and I get "Oh no". Whatever the reason is it shouldn't spew that many error messages. gnome-settings-daemon-3.6.3-1.fc18.i686 libwacom-0.6.1-1.fc18.i686 libwacom-data-0.6.1-1.fc18.noarch xorg-x11-drv-wacom-0.16.1-2.fc18.i686
Created attachment 645914 [details] session.log with 5000 errors
Created attachment 645915 [details] Xorg.1.log
Created attachment 645918 [details] dmesg
Might be caused by Bug 877191 - [abrt] gnome-settings-daemon-3.6.3-1.fc18: g_variant_serialised_check: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Created attachment 646393 [details] g-s-d --debug Reproduced on plain "f18 base" testday image with gnome-settings-daemon-3.6.1-3.fc18.i686. X could be started after removing /usr/libexec/gnome-settings-daemon through a console - and then GNOME worked just fine. (It seems to me like it would be a big win for testing, stability and workaroundability if a failing g-s-d didn't halt GNOME completely.) Running g-s-d --debug gave the attached output before it crashed. A couple of possibly related messages: (gnome-settings-daemon-:3214): color-plugin-WARNING **: failed to get edid: unable to get EDID for output (gnome-settings-daemon-:3214): color-plugin-DEBUG: no edid for LVDS1 [unable to get EDID for output], falling back to connection name and then (gnome-settings-daemon-:3214): wacom-plugin-DEBUG: Creating fallback driver for wacom tablet 'Wacom ISDv4 EC Pen eraser' ('/dev/input/event7') (gnome-settings-daemon-:3214): wacom-plugin-DEBUG: Adding device 'Wacom ISDv4 EC Pen eraser' (type: 'Eraser') to known devices list (gnome-settings-daemon-:3214): wacom-plugin-DEBUG: Applying settings for device 'Wacom ISDv4 EC Pen eraser' (type: Eraser) (gnome-settings-daemon-:3214): wacom-plugin-DEBUG: Did not find a matching output for EDID 'WAC,(null),(null)' g-s-d worked fine after removing wacom.gnome-settings-plugin . My conclusion: 1. the root cause might be bad hardware or a kernel bug ... or the kernel bug that it doesn't know how to handle the bad hardware 2. g-s-d should handle such errors somehow, perhaps by using default values or falling back 3. even in the worst case it shouldn't loop and segfault
X agree that LVDS1 doesn't have any EDID info that it wants to use - it will apparently just use the existing "KMS" mode: [ 12.048] (II) intel(0): Output LVDS1 has no monitor section [ 12.048] (--) intel(0): found backlight control interface /sys/class/backlight/acpi_video0 [ 12.064] (II) intel(0): Output VGA1 has no monitor section [ 12.064] (II) intel(0): Output HDMI1 has no monitor section [ 12.089] (II) intel(0): Output DP1 has no monitor section [ 12.089] (II) intel(0): EDID for output LVDS1 [ 12.089] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported) [ 12.089] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported) [ 12.089] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported) [ 12.089] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported) [ 12.089] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported) [ 12.089] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported) [ 12.089] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported) [ 12.089] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported) [ 12.089] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported) [ 12.089] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported) [ 12.089] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported) [ 12.089] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported) [ 12.089] (II) intel(0): Printing probed modes for output LVDS1 [ 12.089] (II) intel(0): Modeline "1366x768"x60.1 70.61 1366 1414 1446 1488 768 770 775 790 -hsync -vsync (47.5 kHz P) [ 12.089] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d) [ 12.089] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d) [ 12.089] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d) [ 12.089] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d) [ 12.105] (II) intel(0): EDID for output VGA1 [ 12.105] (II) intel(0): EDID for output HDMI1 [ 12.130] (II) intel(0): EDID for output DP1 [ 12.130] (II) intel(0): Output LVDS1 connected [ 12.130] (II) intel(0): Output VGA1 disconnected [ 12.130] (II) intel(0): Output HDMI1 disconnected [ 12.130] (II) intel(0): Output DP1 disconnected [ 12.130] (II) intel(0): Using exact sizes for initial modes [ 12.130] (II) intel(0): Output LVDS1 using initial mode 1366x768 +0+0
No hardware issue here, this is definitely related to bug 877191, g-s-d enters a recursion loop when matching the tablet with the monitor.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.