I have tested a few installs on my idle test PC.
Overall, a nice new release with exciting news and a few blockers. Beautiful theme (as always).
Fedora 12 x86_64 live CD
Comes up nicely with 1920x1200 resolution using nouveau driver. I must have pressed enter to wake up the display, as I found myself logged in without selecting keyboard layout. The default was USA layout. Easy enough to correct. Installed to hard drive Installed on entire drives Selected Review and modify Deleted all lvm stuff, built a raid1 device for /home and rebuilt the lvm vg for swap and / Creating filesystems took a long time. I would prefer to answer all questions first so I could leave the PC. The reboot button on the last screen didn't reboot. Just terminated the installer. Rebooted and left. When I came back the CD tray was ejected and the screen black. Nothing would wake the screen, so I removed the CD and forcefully rebooted. See the i686 install below for more info. Booted nicely, went through firstboot, setting up my local NTP servers, etc. Set up a local user. Logged in, and the default keyboard was still USA... Logged out and selected correct keyboard at login. Still USA layout after login! Went to system->preferences->Keyboard. USA was the only layout listed. Added Norwegian and removed USA. Logged out and selected my user. The keyboard selector at the login screen still says USA. Ignored it and entered my password. Got correct keyboard layout. Login screen keyboard layout selector seems to not work at all. Keyboard selection at install doesn't have any effect on the default after install. No 'desktop effects'. Hope nouveau gets there soon... Did a yum update and rebooted. Got the superblock in the future error. Yes, I am east of Greenwich. A lot of us are. Make it part of your testing of all packages, please. The evolution-mapi connector is full of such time zone errors as well. I didn't work around this issue, as I was ready to reinstall.
Fedora 12 i686 live CD
This time I selected Norwegian layout while logging into the live session. This actually worked. Installed just like the x86_64 install above. This time I was present while the system supposedly rebooted. After I typed reboot, the screen went black, the tray ejected, and then nothing. The system never rebooted. I assume this was the same with the x86_64 install. Everything proceeded just like the x86_64 install. They seemed completely bug-compatible, including the keyboard layout selector at login not doing much good. upgraded and rebooted to verify that the file system got updated in the future. It didn't! The system actually rebooted, but NetworkManager failed during login. Couldn't find some required resource. The network is up and running, but no icon.
If this kind of report is interesting, I was planning to do a basic install tomorrow from the x86_64 DVD, and then a network install. Just testing the basic installation. I have not been asked to submit smolt profiles during these installs from the live cd's. I'll do so tomorrow.
On Thu, 2009-10-22 at 16:01 +0200, Birger Wathne wrote:
I have tested a few installs on my idle test PC.
Overall, a nice new release with exciting news and a few blockers. Beautiful theme (as always).
Fedora 12 x86_64 live CD
Comes up nicely with 1920x1200 resolution using nouveau driver. I must have pressed enter to wake up the display, as I found myself logged in without selecting keyboard layout. The default was USA layout. Easy enough to correct.
There's a time-out on the login - if you leave it sitting at GDM long enough, it just logs itself in with default options.
Installed to hard drive Installed on entire drives Selected Review and modify Deleted all lvm stuff, built a raid1 device for /home and rebuilt the lvm vg for swap and / Creating filesystems took a long time. I would prefer to answer all questions first so I could leave the PC. The reboot button on the last screen didn't reboot. Just terminated the installer. Rebooted and left. When I came back the CD tray was ejected and the screen black. Nothing would wake the screen, so I removed the CD and forcefully rebooted. See the i686 install below for more info. Booted nicely, went through firstboot, setting up my local NTP servers, etc. Set up a local user. Logged in, and the default keyboard was still USA... Logged out and selected correct keyboard at login. Still USA layout after login! Went to system->preferences->Keyboard. USA was the only layout listed. Added Norwegian and removed USA. Logged out and selected my user. The keyboard selector at the login screen still says USA. Ignored it and entered my password. Got correct keyboard layout. Login screen keyboard layout selector seems to not work at all. Keyboard selection at install doesn't have any effect on the default after install.
I believe it's only meant to set the keyboard layout *for GDM* (if you set your username and password with, oh, a Russian keyboard layout, trying to enter them with an English one is unlikely to work spectacularly well :>). I could be wrong here, though.
No 'desktop effects'. Hope nouveau gets there soon...
3D is Hard, unfortunately. Especially when you have to reverse-engineer everything (there's no specs for NVIDIA hardware). We are getting there, though. Ben has somewhat-working compiz with a few artifacts on a few NVIDIA chipsets, at this point in time. Give it a year or so, is my guess, depending on your chipset.
Did a yum update and rebooted. Got the superblock in the future error. Yes, I am east of Greenwich. A lot of us are. Make it part of your testing of all packages, please. The evolution-mapi connector is full of such time zone errors as well. I didn't work around this issue, as I was ready to reinstall.
It's been fixed already.
upgraded and rebooted to verify that the file system got updated in the future. It didn't!
See above :)
The system actually rebooted, but NetworkManager failed during login. Couldn't find some required resource. The network is up and running, but no icon.
Also known and fixed already, as long as you have NetworkManager and NetworkManager-gnome 0.7.996-5.git20091021.fc12 or higher you won't see this again.
If this kind of report is interesting, I was planning to do a basic install tomorrow from the x86_64 DVD, and then a network install. Just testing the basic installation. I have not been asked to submit smolt profiles during these installs from the live cd's. I'll do so tomorrow.
Certainly! Thanks a lot.
Sitat Adam Williamson awilliam@redhat.com:
I believe it's only meant to set the keyboard layout *for GDM* (if you set your username and password with, oh, a Russian keyboard layout, trying to enter them with an English one is unlikely to work spectacularly well :>). I could be wrong here, though.
You would quickly run into the same problem with a Norwegian keyboard if your password contained anyting outside a-z0-9.
From a user perspective I would expect that the keyboard I selected during
install also was the default at the login screen (Isn't it a valid assumption for a desktop OS that the keyboard used during install will be permanently attached), and what I used to log in would be the default for that session. Wouldn't that be far more user friendly?
No 'desktop effects'. Hope nouveau gets there soon...
3D is Hard, unfortunately. Especially when you have to reverse-engineer everything (there's no specs for NVIDIA hardware). We are getting there, though. Ben has somewhat-working compiz with a few artifacts on a few NVIDIA chipsets, at this point in time. Give it a year or so, is my guess, depending on your chipset.
It must be a wonderful challenge... It would have been very fun to have the spare time for that kind of project. From my user perspective I would rather have nvidia turn around and learn from Intel and lately ATI/AMD. Even those are big challenges but at least documentation exists. The Nouveau developers have chosen a real 'mission impossible' and are actually getting there. I am very, very impressed.
Did a yum update and rebooted. Got the superblock in the future error.
Yes,
I am east of Greenwich. A lot of us are. Make it part of your testing
of
all packages, please. The evolution-mapi connector is full of such time
zone errors as well. I didn't work around this issue, as I was ready to
reinstall.
Is it possible to search the source of all packages for constructs that assume GMT offset is positive? Or perhaps add testing with negative time zones to some list of recommended test procedures?
On 10/22/2009 06:28 PM, Adam Williamson wrote:
On Thu, 2009-10-22 at 16:01 +0200, Birger Wathne wrote:
I have tested a few installs on my idle test PC.
Overall, a nice new release with exciting news and a few blockers. Beautiful theme (as always).
Fedora 12 x86_64 live CD
Comes up nicely with 1920x1200 resolution using nouveau driver. I must have pressed enter to wake up the display, as I found myself logged in without selecting keyboard layout. The default was USA layout. Easy enough to correct.
There's a time-out on the login - if you leave it sitting at GDM long enough, it just logs itself in with default options.
Installed to hard drive Installed on entire drives Selected Review and modify Deleted all lvm stuff, built a raid1 device for /home and rebuilt the lvm vg for swap and / Creating filesystems took a long time. I would prefer to answer all questions first so I could leave the PC. The reboot button on the last screen didn't reboot. Just terminated the installer. Rebooted and left. When I came back the CD tray was ejected and the screen black. Nothing would wake the screen, so I removed the CD and forcefully rebooted. See the i686 install below for more info. Booted nicely, went through firstboot, setting up my local NTP servers, etc. Set up a local user. Logged in, and the default keyboard was still USA... Logged out and selected correct keyboard at login. Still USA layout after login! Went to system->preferences->Keyboard. USA was the only layout listed. Added Norwegian and removed USA. Logged out and selected my user. The keyboard selector at the login screen still says USA. Ignored it and entered my password. Got correct keyboard layout. Login screen keyboard layout selector seems to not work at all. Keyboard selection at install doesn't have any effect on the default after install.
I believe it's only meant to set the keyboard layout *for GDM* (if you set your username and password with, oh, a Russian keyboard layout, trying to enter them with an English one is unlikely to work spectacularly well :>). I could be wrong here, though.
No this is a regression..
In a perfect pony world after the install you should have the keyboard layout you select during install. ( thou I cant recalling that to ever work since F8 or to be precise the removal of xorg.conf ).
X/Gnome seems not only be adding the USA keyboard layout back to the users account after he removes it but defaulting to it as well.
We need to add locale or at least an none USA keyboard layout to autoqa's test queue.
JBG
On Thu, 2009-10-22 at 16:01 +0200, Birger Wathne wrote:
Set up a local user. Logged in, and the default keyboard was still USA... Logged out and selected correct keyboard at login. Still USA layout after login! Went to system->preferences->Keyboard. USA was the only layout listed. Added Norwegian and removed USA. Logged out and selected my user. The keyboard selector at the login screen still says USA. Ignored it and entered my password. Got correct keyboard layout. Login screen keyboard layout selector seems to not work at all. Keyboard selection at install doesn't have any effect on the default after install.
This time I selected Norwegian layout while logging into the live session. This actually worked. Installed just like the x86_64 install above. This time I was present while the system supposedly rebooted. After I typed reboot, the screen went black, the tray ejected, and then nothing. The system never rebooted. I assume this was the same with the x86_64 install. Everything proceeded just like the x86_64 install. They seemed completely bug-compatible, including the keyboard layout selector at login not doing much good.
There's been a bug filed about the keyboard layout problems; could you follow up on https://bugzilla.redhat.com/show_bug.cgi?id=530452 with your experiences? Thanks.