On Sun, 2011-02-27 at 23:06 -0600, Jason D. Clinton wrote: > , running 'startx' > from a vt just gives me a blank background. I'm posting this > from Xfce. > > Don't know the root cause but using the fallback force method posted > by mclasen will get you in to fallback mode until it's fixed. The root cause turned out to be at-spi2 breakage. Again. I don't want this to come across the wrong way, but this: https://admin.fedoraproject.org/updates/notification-daemon-0.7.1-1.fc15,abattis-cantarell-fonts-0.0.3-1.fc15,accountsservice-0.6.3-3.fc15,at-spi2-atk-1.91.90-1.fc15,at-spi2-core-1.91.90-1.fc15,brasero-2.91.90-1.fc15,control-center-2.91.90-1.fc15,devhelp-2.91.90-1.fc15,empathy-2.91.90-1.fc15,eog-2.91.90-1.fc15,epiphany-2.91.90-1.fc15,evince-2.91.90-1.fc15,file-roller-2.91.90-1.fc15,folks-0.3.6-1.fc15,gcalctool-5.91.90-1.fc15,gedit-2.91.7-1.fc15,gedit-plugins-2.91.0-1.fc15,gjs-0.7.11-1.fc15,glib-networking-2.28.0-1.fc15,gnome-color-manager-2.91.90-1.fc15,gnome-desktop3-2.91.90-1.fc15,gnome-games-2.91.90-1.fc15,gnome-icon-theme-2.91.7-4.fc15,gnome-icon-theme-extras-2.90.7-1.fc15,gnome-icon-theme-symbolic-2.91.7-1.fc15,gnome-packagekit-2.91.90-1.fc15,gnome-panel-2.91.90-1.fc15,gnome-phone-manager-0.66-1.fc15,gnome-power-manager-2.91.90-1.fc15,gnome-screensaver-2.91.90-1.fc15,gnome-session-2.91.90-2.fc15,gnome-settings-daemon-2.91.90-3.fc15,gnome-shell-2.91.90-2.fc15,gnome-system -monitor-2.99.0-1.fc15,gnome-terminal-2.33.90-1.fc15,gnome-themes-standard-2.91.90-2.fc15,gnome-utils-2.91.90-1.fc15,gnome-web-photo-0.10-1.fc15,gsettings-desktop-schemas-0.1.7-1.fc15,gtksourceview3-2.91.6-1.fc15,libgnomekbd-2.91.90-1.fc15,libpeas-0.7.3-1.fc15,libsoup-2.33.90-1.fc15,libwnck3-2.91.90-1.fc15,libxklavier-5.1-1.fc15,mousetweaks-2.91.90-1.fc15,mutter-2.91.90-1.fc15,nautilus-2.91.90.1-1.fc15,nautilus-open-terminal-0.19-1.fc15,orca-2.91.90-1.fc15,polkit-0.100-1.fc15,polkit-gnome-0.100-1.fc15,pyatspi-1.91.90-1.fc15,pyclutter-gtk-0.10.0-7.fc15,python-xklavier-0.2-7.fc15,seed-2.91.90-1.fc15,totem-2.91.7-1.fc15,totem-pl-parser-2.32.3-1.fc15,vino-2.99.0-2.fc15,vte-0.27.90-1.fc15,vte3-0.27.90-1.fc15,yelp-2.91.10-4.fc15,zenity-2.91.90-1.fc15,gdm-2.91.91-1.fc15 really doesn't make me happy. See caillon's comment starting "Note that in order to get things working, one needs to disable a11y" - which makes it clear that he knows, unless you manually disable a feature by using an arcane command or by removing a package, GNOME will fail to run at all...yet he gives the update +1 karma? This really isn't how the update approval system is supposed to work. If you (corporate 'you', Fedora desktop team) know about such a critical bug, you should fix it and edit the update. Unless this gets fixed soon, we are in a state where anyone who installs the Alpha and does an update will find their system apparently utterly broken (it boots to a crashing gdm and if you boot to 'runlevel 3' and do startx, GNOME fails to run). I know we're in early pre-release state and we don't guarantee anything, but it doesn't really excuse submitting and then pushing to 'stable' code you know to be badly broken. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
