Created attachment 407826 [details] gnome-session --debug output Description of problem: When I turn on my computer with GDM or when I start GNOME, I'm experiencing a really weird behaviour, for example when I start GNOME, when the screen is empty, without icons, the mouse pointer is very slow, and the computer is stuck there. In order to proceed with the GNOME startup, I have to move to a virtual terminal (tty3 for example) and then get back to X, then is when GNOME continue with the startup. Version-Release number of selected component (if applicable): gnome-session-xsession-2.28.0-2.fc12.x86_64 gnome-session-2.28.0-2.fc12.x86_64 How reproducible: Always Steps to Reproduce: 1. Install Fedora 12 (x86_64) 2. Try to start GNOME or GDM 3. Actual results: Computer is stuck with the mouse very slow until switching to a VT. It's very annoying Expected results: Computer starting without issues. Additional info:
I've another but too, that it has to do with this, apparently. Using GNOME after resuming from suspend I see a lot of notifications like: Could not switch the monitor configuration could not set the configuration to crtc 64 It repeats a lot of times, and the screen is completely slow and impossible to use, I had to restart X to solve the issue. These errors appears in GDM too, sometimes.
found a similar bug in launchpad
Created attachment 407856 [details] lspci output
Created attachment 407857 [details] xrandr output
Created attachment 407891 [details] Xorg.0.log when runing GDM and GNOME
Created attachment 407893 [details] dmesg output
Created attachment 407896 [details] gnome-session --debug output withoutvtswitching it was 5/10 minutes, it didn't start, I did ctrl+c to stop the gnome-session command, and then ctrl+alt+del to get back to KDM (I was using KDM because it has the failsafe option) gnome doesn't start if I don't switch to a VT and then I get back to X
From #fedora-bugzappers: ajax: that's not a bug. ajax: oh wait, it totally is. ajax: just seeing lots of edid reads on its own isn't though ajax: i know what that is though, and it's infuriating. ajax: we ask for hotplug interrupts on outputs you don't have and then the electronics to do that gets confused. ajax: and we can't just disable outputs you don't have because if we _do_ then some people's docks don't work. jraber: ajax: Is that Gnome specific? Is there a workaround? ajax: it's not, and there's not. ajax: it's gnome-specific in that listening for RANDR output status change events and actually doing something with them causes a busy loop - we rescan output status, this makes the kernel generate more "change" events, we get them and rescan... ajax: but any other DE doing that, would do that. Reassigning to xorg-x11 as that seems to be closer to the root cause than gnome-session
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
jraber - for the future, can you please avoid assigning bugs to the component xorg-x11 ? it's not a 'real' X component so neither Bugzappers nor X devel team monitor it very closely. It's best to use the xorg-x11-drv-* components or xorg-x11-server. Thanks!
fortunately this bug is *fixed* for me after upgrading to Fedora 13: [matias@flame ~]$ rpm -qa | grep gnome-session gnome-session-xsession-2.30.0-1.fc13.x86_64 gnome-session-2.30.0-1.fc13.x86_64 [matias@flame ~]$ rpm -qa | grep xorg-x11-server xorg-x11-server-utils-7.4-16.fc13.x86_64 xorg-x11-server-Xorg-1.8.0-12.fc13.x86_64 xorg-x11-server-common-1.8.0-12.fc13.x86_64
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Marking as CLOSED/CURRENTRELEASE per comment 11 -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers