Re: F15 BETA.TC1 experiences
When installing over the network and providing IP address through boot options I noticed in the log a message saying it couldn't find updates.img with the reason "name resolution error". As I did not expect to load a updates.img this didn't effect me. But further on in the installation I saw no networking problem and all the packages were fetched as expected. Could it be that networking is activated after anaconda tries to load updates.img or am I looking at an artefact. Koos. Op 30-3-2011 19:36, Gregory Woodbury schreef: Downloaded BETA.TC1 x86_64 DVD.iso and did an install on a VBox guest. No glitches encountered during the install. One nit: NetworkManager isn't activated during the install so firstboot isn't network connected for the NTP setup dialogue. Looks good to me. -- G.Wolfe Woodbury aka redwolfe (proventesters) smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: TC1
This is already filed: Bug #692196 Koos Op 30-3-2011 21:47, Adam Williamson schreef: On Wed, 2011-03-30 at 12:35 -0700, Chuck Forsberg WA7KGX N2469R wrote: Manual disk setup with basic video was nominal except that I was unable to enter a static IP during install as the address field went blank as soon as I entered an address. Is there a reason you chose basic video? Did you try without it to see if it would work? Please file the static networking issue, thanks. smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On Thu, Mar 31, 2011 at 07:27:24AM +0530, Rahul Sundaram wrote: > On 03/31/2011 03:20 AM, Jared K. Smith wrote: > > On Wed, Mar 30, 2011 at 3:46 PM, Scott Robbins wrote: > >> It looks as if, from this one test install, as if adding the user to > >> admin users automatically adds them to wheel, and that in /etc/sudoers, > >> wheel is already able to execute all commands (whereas in the past, that > >> line was commented out.) Was that just an oddity, or is it by design? > > >From what (little?) I understand, it's by design. > > I can confirm it is, It should really should have gone through the > feature process but noone bothered to do one and it is going to take > some extra time to get it documented in the release notes as a result of > this but I fully intend to followup when I can. Thanks for the confirmation. Actually, I think many Fedora users are people who come from Ubuntu and its offshoots, so this will probably avoid some confusion. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Buffy: Well, that works out great. You won't tell anyone that I'm the Slayer, and I won't tell anyone you're a moron. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On Thu, Mar 31, 2011 at 09:00:03AM +0800, bsfmig wrote: > On Thu, Mar 31, 2011 at 02:14, Scott Robbins wrote: > > As it was a virtual machine (I guess that's the reason) Gnome 3 failed > to load. I then enabled 3D acceleration in VBox and gave it the > maximum allowable memory (128MB), and tried again. (This doesn't > affect me in real life, where I do minimal installations and use > openbox, but I was curious.) However, still no Gnome 3. I seem to > remember this being a known issue--or perhaps not even considered an > issue, that it won't work in many VMs. > > > > About the graphics, I accidentally got a VirtualBox Guest Additions 4.0.5 > (yes, > it's a development build) ISO which supports Fedora 15 by fully supporting > gold > release of xorg-server 1.10. It was originally posted in vbox-users mailing > list some a week ago. > http://www.virtualbox.org/download/testcase/VBoxGuestAdditions-r70636.iso Interesting. Thank you. I'll probably be lazy and wait till VirtualBox tells me it has a newer version available. :) -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Kendra: I call it Mr. Pointy. Buffy: You named your stake? Kendra: Yes. Buffy: Remind me to get you a stuffed animal. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On 03/31/2011 03:20 AM, Jared K. Smith wrote: > On Wed, Mar 30, 2011 at 3:46 PM, Scott Robbins wrote: >> It looks as if, from this one test install, as if adding the user to >> admin users automatically adds them to wheel, and that in /etc/sudoers, >> wheel is already able to execute all commands (whereas in the past, that >> line was commented out.) Was that just an oddity, or is it by design? > >From what (little?) I understand, it's by design. I can confirm it is, It should really should have gone through the feature process but noone bothered to do one and it is going to take some extra time to get it documented in the release notes as a result of this but I fully intend to followup when I can. Rahul -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On Thu, Mar 31, 2011 at 02:14, Scott Robbins wrote: > On Wed, Mar 30, 2011 at 10:50:56AM -0700, Adam Williamson wrote: > > On Wed, 2011-03-30 at 13:44 -0400, James Laska wrote: > > > On Wed, 2011-03-30 at 13:36 -0400, Gregory Woodbury wrote: > > > > Downloaded BETA.TC1 x86_64 DVD.iso and did an install on a VBox > guest. > > > > > > > > No glitches encountered during the install. > > > > > > > > One nit: NetworkManager isn't activated during the install so > firstboot > > > > isn't > > > > network connected for the NTP setup dialogue. > > > > > > When performing a media-based (non-network) installation, networking is > > > not enabled by default. If you perform an installation that uses a > > > network-based package repository, networking will be enabled by > default. > > I just did a default installation in Virtual Box, using the netboot.iso. > One thing--I don't remember if this is a new improvement or not, but I > find it automatically finds the server and gets the packages--I seem to > remember I used to have to manually enter the url. > > Using network, as per what Adam says below, had my network running at > boot. I like the default wallpaper too, nice choices. > > As it was a virtual machine (I guess that's the reason) Gnome 3 failed > to load. I then enabled 3D acceleration in VBox and gave it the > maximum allowable memory (128MB), and tried again. (This doesn't > affect me in real life, where I do minimal installations and use > openbox, but I was curious.) However, still no Gnome 3. I seem to > remember this being a known issue--or perhaps not even considered an > issue, that it won't work in many VMs. > About the graphics, I accidentally got a VirtualBox Guest Additions 4.0.5 (yes, it's a development build) ISO which supports Fedora 15 by fully supporting gold release of xorg-server 1.10. It was originally posted in vbox-users mailing list some a week ago. http://www.virtualbox.org/download/testcase/VBoxGuestAdditions-r70636.iso -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
Just did a new install on a netbook--this time I went for my usual minimal installation. It failed on bind-libs. This strikes me as ood for two reasons--why would bind-libs be included in a minimal installation, and why would it cause the installation to fail? I thought I had seen, somewhere along the line, that anaconda had been made more robust and wouldn't die on a failed package, especially when the package is non-essential. Is that simply my imagination playing tricks? (Googling doesn't bring me any sign of it.) Even if it is the case, from what I see on CentOS with whatrequires bind-libs, it's really not necessary for a minimal installation. (Ironically, trying a complete install earlier worked perfectly.) Would someone be able to tell me if I am imagining things about Anaconda being so fragile? Seems that most other installers are able to recover from something like that, so it should be doable. The bind-libs being included in a minimal install sounds like a possible bug, but the same argument could probably be made for anything not essential to boot into a shell. I'm guessing that it was just a glitch in the image downloaded on this install, or a network burp, but the bigger concern, IMHO, is anaconda being so fragile. (Especially if it's not supposed to be, but as mentioned above, I can't find anything to support that, so am beginning to think I misunderstood, or perhaps scanned over, something in the past.) I think I'm most annoyed over my failing memory. Running the install a second time, everything was fine. Thanks for any feedback, (especially on whether there was or wasn't an anaconda fix). -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Xander: So, we Bronzin' it tonight? Willow: Wednesdays, kinda beat... Xander: Well, we could grind our enemies into talcum powder with a sledgehammer, but, gosh, we did that last night. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On Wed, Mar 30, 2011 at 3:46 PM, Scott Robbins wrote: > It looks as if, from this one test install, as if adding the user to > admin users automatically adds them to wheel, and that in /etc/sudoers, > wheel is already able to execute all commands (whereas in the past, that > line was commented out.) Was that just an oddity, or is it by design? >From what (little?) I understand, it's by design. -- Jared Smith Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: TC1
On 03/30/2011 07:35 PM, Chuck Forsberg WA7KGX N2469R wrote: > No wonder > OpenSuse and Ubuntu are looking for something else. Do you got some referrense backing that up with regards to OpenSuse? Just a bit curios given that the upstream Gnome3 releases are OpenSuse and hosted [1] @ OpenSuse JBG 1.http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/GNOME_3.x86_64-0.3.1-Build1.1.iso -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 13 updates-testing report
The following Fedora 13 Security updates need testing: https://admin.fedoraproject.org/updates/libvirt-0.8.2-3.fc13 https://admin.fedoraproject.org/updates/dbus-1.2.24-2.fc13 https://admin.fedoraproject.org/updates/openldap-2.4.21-12.fc13 https://admin.fedoraproject.org/updates/tor-0.2.1.29-1300.fc13 https://admin.fedoraproject.org/updates/libxml2-2.7.7-2.fc13 https://admin.fedoraproject.org/updates/loggerhead-1.18.1-1.fc13 https://admin.fedoraproject.org/updates/php-5.3.6-1.fc13,maniadrive-1.2-27.fc13,php-eaccelerator-0.9.6.1-6.fc13 https://admin.fedoraproject.org/updates/rsync-3.0.8-1.fc13 https://admin.fedoraproject.org/updates/nss-3.12.9-9.fc13 https://admin.fedoraproject.org/updates/gdm-2.30.2-2.fc13 https://admin.fedoraproject.org/updates/libcgroup-0.35.1-5.fc13 https://admin.fedoraproject.org/updates/feh-1.10.1-1.fc13 https://admin.fedoraproject.org/updates/libtiff-3.9.4-4.fc13 https://admin.fedoraproject.org/updates/quagga-0.99.18-1.fc13 https://admin.fedoraproject.org/updates/dhcp-4.1.2-2.ESV.R1.fc13 https://admin.fedoraproject.org/updates/asterisk-1.6.2.17.2-1.fc13 The following Fedora 13 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/policycoreutils-2.0.83-33.8.fc13 https://admin.fedoraproject.org/updates/tzdata-2011d-2.fc13 https://admin.fedoraproject.org/updates/gdm-2.30.2-2.fc13 https://admin.fedoraproject.org/updates/nss-3.12.9-9.fc13 https://admin.fedoraproject.org/updates/libimobiledevice-1.0.6-1.fc13 https://admin.fedoraproject.org/updates/PackageKit-0.6.6-3.fc13 https://admin.fedoraproject.org/updates/NetworkManager-0.8.3.998-2.fc13 https://admin.fedoraproject.org/updates/usbmuxd-1.0.7-1.fc13 https://admin.fedoraproject.org/updates/libtiff-3.9.4-4.fc13 https://admin.fedoraproject.org/updates/libnl-1.1-14.fc13 https://admin.fedoraproject.org/updates/selinux-policy-3.7.19-101.fc13 https://admin.fedoraproject.org/updates/perl-ExtUtils-XSpp-0.15-2.fc13,perl-5.10.1-122.fc13,perl-Wx-0.98-5.fc13 https://admin.fedoraproject.org/updates/libxml2-2.7.7-2.fc13 https://admin.fedoraproject.org/updates/fuse-2.8.5-5.fc13 https://admin.fedoraproject.org/updates/libcgroup-0.35.1-5.fc13 https://admin.fedoraproject.org/updates/openldap-2.4.21-12.fc13 https://admin.fedoraproject.org/updates/livecd-tools-13.2-1.fc13 https://admin.fedoraproject.org/updates/lua-5.1.4-7.fc13 https://admin.fedoraproject.org/updates/librsvg2-2.26.3-3.fc13 https://admin.fedoraproject.org/updates/mobile-broadband-provider-info-1.20110218-1.fc13 https://admin.fedoraproject.org/updates/dosfstools-3.0.9-4.fc13 https://admin.fedoraproject.org/updates/file-5.04-7.fc13 https://admin.fedoraproject.org/updates/system-config-users-1.2.107-1.fc13 https://admin.fedoraproject.org/updates/python-ethtool-0.6-1.fc13 https://admin.fedoraproject.org/updates/libical-0.46-2.fc13 https://admin.fedoraproject.org/updates/mash-0.5.20-1.fc13 https://admin.fedoraproject.org/updates/libfprint-0.3.0-1.fc13 https://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.904-7.fc13 https://admin.fedoraproject.org/updates/lldpad-0.9.26-2.fc13 The following builds have been pushed to Fedora 13 updates-testing 389-admin-1.1.16-1.fc13 389-admin-console-1.1.7-1.fc13 389-ds-base-1.2.8-0.8.rc4.fc13 389-ds-console-1.2.5-1.fc13 digikam-1.9.0-1.fc13 gnome-chemistry-utils-0.12.7-2.fc13 gnumeric-1.10.14-1.fc13 goffice-0.8.14-1.fc13 groonga-1.2.0-1.fc13 idm-console-framework-1.1.7-1.fc13 kadu-0.9.0-1.fc13 kipi-plugins-1.9.0-1.fc13 pam_shield-0.9.5-2.fc13 perl-Module-Mask-0.03-1.fc13 policycoreutils-2.0.83-33.8.fc13 rsync-3.0.8-1.fc13 ruby-augeas-0.4.1-1.fc13 texmaker-2.3-1.fc13 texworks-0.4.0-1.fc13 Details about builds: 389-admin-1.1.16-1.fc13 (FEDORA-2011-4400) 389 Administration Server (admin) Update Information: This is the 1.1.16 release 1.1.15 release - git tag 389-admin-1.1.15 see Bugs for the list of bugs fixed start-ds-admin.in -- replaced "return 1" with "exit 1" ChangeLog: * Tue Mar 29 2011 Rich Megginson - 1.1.16-1 - 389-admin-1.1.16 - Bug 476925 - Admin Server: Do not allow 8-bit passwords for the admin user - Bug 614690 - Don't use exec to call genrb - Bug 158926 - Unable to install CA certificate when using - hardware token ( LunaSA ) - Bug 211296 - Clean up all HTML pages (Admin Express, Repl Monitor, etc) * Wed Feb 23 2011 Rich Megginson - 1.1.15-1 - 1.1.15 release - git tag 389-admin-1.1.15 - Bug 493424 - remove unneeded modules for admin server apache config - Bug 618897 - Wrong permissions when cre
Re: F15 BETA.TC1 experiences
On Wed, Mar 30, 2011 at 12:26:13PM -0700, Adam Williamson wrote: > > > > I've seen quite a few comparison reviews and so on, so I'm not sure we'd > be providing anything new by doing another evaluation. To side with Adam on this, most reviews are dated within 3 months anyway. Seriously, evil though Oracle is, they update VB regularly, KVM is always being updated, and so is VMware, to the point where any comparison quickly becomes inaccurate. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Xander: So, do we have to speak Spanish when we see him?' Cause I don't know anything much besides 'Doritos' and 'chihuahua.' -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: TC1
On Wed, 2011-03-30 at 12:35 -0700, Chuck Forsberg WA7KGX N2469R wrote: > Manual disk setup with basic video was nominal except that > I was unable to enter a static IP during install as the address > field went blank as soon as I entered an address. Is there a reason you chose basic video? Did you try without it to see if it would work? Please file the static networking issue, thanks. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On Wed, Mar 30, 2011 at 08:44:00PM +0200, Johan Scheepers wrote: > On 30/03/2011 19:50, Adam Williamson wrote: > > Selecting the NTP checkbox during firstboot should probably bring up a > > network connection if one isn't already up, though. > Kindly please provide me with the web address where I may find this Blah, I realized I gave bogus information before--I didn't mean that NTP brought up the network, only that the network was up. I misread what Adam had written, interpreting it as If the network is up, NTP will work. Apologies to any who were confused. It looks as if, from this one test install, as if adding the user to admin users automatically adds them to wheel, and that in /etc/sudoers, wheel is already able to execute all commands (whereas in the past, that line was commented out.) Was that just an oddity, or is it by design? (I can see it being a good idea to stop confusing Ubuntu migrants, but it's one of those bikeshed things that will probably cause 100 post threads.) :) To pick a nit, I think xterm should be in the default install. Anyway, again, (I think I said this), it basically looks pretty smooth. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Buffy: Besides, it's kind of my job. Spike: For now. Buffy: What, you want me to stop working? Spike: Well, let's see - do I want you to give up killing my friends? Yeah, I've given it some thought. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
TC1
Manual disk setup with basic video was nominal except that I was unable to enter a static IP during install as the address field went blank as soon as I entered an address. Once installed, Gnome failed on login and logged me out immediately. XFCE did work but the icons in the upper right were jumbled together. This resolved after I installed the Nvidia driver for my GT 460 SE. Gnome was much happier running under Nvidia. I think Gnome is working as intended, but it either half done or on the wrong track based on what I see. No wonder OpenSuse and Ubuntu are looking for something else. Maybe Gnome 4 will be more to peoples' liking. -- Chuck Forsberg WA7KGX N2469R c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On Wed, 2011-03-30 at 19:04 +, "Jóhann B. Guðmundsson" wrote: > On 03/30/2011 06:51 PM, Adam Williamson wrote: > > The differences between various virt suites are pretty well known, > > really... > > Well I was personally thinking about graphical application usage > comparison against virt-manager but since you mentioned that the > differences is well know then there is no point in doing that. I've seen quite a few comparison reviews and so on, so I'm not sure we'd be providing anything new by doing another evaluation. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] 2011-04-01 @ 17:00 UTC - F-15-Beta blocker bug review #4
# F15-Beta Blocker Review meeting #3 # Date: 2011-03-25 # Time: 17:00 UTC [1] (13:00 EDT, 10:00 PDT, 10:00 MST) # Location: #fedora-bugzappers on irc.freenode.net Greetings, This Friday is April 1st. I was trying to cook up something clever for the blocker meeting, without causing too much heartache. I'm sure we can do better than ... * Today only, all bugs are file one, get one free! * All previously approved blocker bugs have been CLOSED WONTFIX * The first 50 bugs filed will be fixed immediately (limit 1 per user, offer not valid in Arizona) Good, glad I got that over with. Now, back to our regularly scheduled programming... The fourth Beta blocker review meeting will be this Friday at 17:00 UTC in #fedora-bugzappers. We'll spend time reviewing proposed and accepted F-15-Beta blocker bugs. Please note that recent daylight savings changes may result in a different local time [1]. An updated list of blocker bugs is available at https://fedoraproject.org/wiki/Current_Release_Blockers. The list of bugs is also attached to this mail. We'll be reviewing the bugs to determine ... 1. whether they meet the Beta release criteria [2] and should stay on the list 2. are getting the attention they need For guidance on Blocker and Nice-to-have (NTH) bugs, checkout ... https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_nth_bug_process == Suggested Meeting Preparation == Maintainers ... * If your bug is *not* MODIFIED ... this issue is at risk of slipping the F15 Beta release date * If your bug is in MODIFIED ... please make sure a build with the fix exists, and is available as a bodhi update. Testers ... * If you REPORT a bug ... please be responsive to any requests for additional information. * If a bug is in ON_QA ... please take a moment to apply the update, and post karma feedback [1] https://fedoraproject.org/wiki/Infrastructure/UTCHowto [2] https://fedoraproject.org/wiki/Fedora_15_Beta_Release_Criteria Thanks, James == Approved Blockers == The following list of bugs are approved blockers that must be resolved. There are 16 bug(s) affecting 5 component(s). === anaconda === * 676821 (VERIFIED) - Couldn't resolve host name when installing packages over NFS * 676968 (ASSIGNED) - system halts after first reboot during kickstart installation * 677131 (VERIFIED) - How to skip update disk prompt * 678150 (ON_QA) - VNC install w/ password, fails to establish password for VNC session * 678201 (ON_QA) - F14->F15 upgrade halted due to package conflicts * 678414 (ON_QA) - NFS ISO install fails during repo setup - umount.nfs4: /mnt/source: device is busy * 678689 (ON_QA) - Disks sda, sdb contain BIOS RAID metadata, but are not part of any recognized BIOS RAID sets. Ignoring disks sda, sdb. * 680474 (ON_QA) - Anaconda doesn't recognize my LVM on RAID1 setup * 681267 (ON_QA) - AttributeError: 'module' object has no attribute 'findExistingRoots' * 681608 (ON_QA) - KeyError: '/dev/md126' * 683574 (ON_QA) - Logical volume resize causes corrupted filesystem * 683956 (ON_QA) - raid creation doesn't do the right thing with --spares during kickstart === desktop-backgrounds === * 683179 (MODIFIED) - desktop- backgrounds package no longer sets the default Fedora background, due to changes in Gnome === openbios === * 679179 (ON_QA) - openbios-ppc subpackage, which qemu depends on, disappeared === preupgrade === * 646843 (MODIFIED) - images/install.img will no longer exist in F-15 and newer === xorg-x11-xauth === * 679486 (ASSIGNED) - Unable to start graphical installer on RC1 KDE live image == Proposed Blockers == The following list of bugs are not yet approved to block the release. There are 10 bug(s) affecting 6 component(s). For guidance on reviewing the following bugs, refer to [[QA:SOP_blocker_bug_process]]. === NetworkManager === * 678553 (ON_QA) - NetworkManager doesn't start successfully on bootup after upgrade from F14 -> F15 * 684246 (NEW) - Accounts don't activate on startup * 689291 (NEW) - activation_source_schedule(): activation stage already scheduled * 691139 (NEW) - NetworkManager 0.8.997 doesn't connect to hidden wireless network === fife === * 677800 (NEW) - Broken dependency: 1:fife-0.3.2-1.fc15.i686 requires libboost_regex.so.1.44.0 === gnome-icon-theme === * 692029 (MODIFIED) - package conflict between fedora-logos and gnome-logos on 15 Beta TC1 DVD === isomd5sum === * 692135 (NEW) - Image failed media check === spin-kickstarts === * 297421 (ASSIGNED) - LiveCD handles timezones inconsistently === systemd === * 678927 (ASSIGNED) - Password prompt for unlocking encrypted /home partition sometimes does not appear * 692097 (NEW) - run directory in root with latest update == Approved NICE-TO-HAVE == The following list of bugs are approved nths that must be resolved. There are 9 bug(s) affecting 5 component(s). === anaconda
Re: F15 BETA.TC1 experiences
On 03/30/2011 06:51 PM, Adam Williamson wrote: > The differences between various virt suites are pretty well known, > really... Well I was personally thinking about graphical application usage comparison against virt-manager but since you mentioned that the differences is well know then there is no point in doing that. JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On 03/30/2011 06:44 PM, Johan Scheepers wrote: > Kindly please provide me with the web address where I may find this http://alt.fedoraproject.org/pub/alt/stage/15-Beta.TC1/ JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On Wed, 2011-03-30 at 18:40 +, "Jóhann B. Guðmundsson" wrote: > On 03/30/2011 06:29 PM, Adam Williamson wrote: > > On Wed, 2011-03-30 at 12:20 -0600, Eric Blake wrote: > >> On 03/30/2011 12:14 PM, Scott Robbins wrote: > >>> I just did a default installation in Virtual Box, using the netboot.iso. > >> Since Fedora ships qemu-kvm and not VirtualBox, I would be more > >> interested in people trying out kvm virtualization to give our own > >> products better testing. > > Don't worry, a lot of people test that config too (it's actually in our > > validation test suite). > > Perhaps it would be a nice idea to gather feed back from reporters using > other virtualsation solutions as in what they like and dislike with ours > and what they like and dislike in the other one as well? The differences between various virt suites are pretty well known, really... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On 30/03/2011 19:50, Adam Williamson wrote: > On Wed, 2011-03-30 at 13:44 -0400, James Laska wrote: >> On Wed, 2011-03-30 at 13:36 -0400, Gregory Woodbury wrote: >>> Downloaded BETA.TC1 x86_64 DVD.iso and did an install on a VBox guest. >>> >>> No glitches encountered during the install. >>> >>> One nit: NetworkManager isn't activated during the install so firstboot >>> isn't >>>network connected for the NTP setup dialogue. >> When performing a media-based (non-network) installation, networking is >> not enabled by default. If you perform an installation that uses a >> network-based package repository, networking will be enabled by default. >> >> For the media-based (non-network) use case, you can manually enable >> networking by selecting 'Start automatically' for the appropriate device >> from the network configuration dialog. >> >> http://docs.fedoraproject.org/en-US/Fedora/14/html/Installation_Guide/sn-Netconfig-x86.html#sn-Netconfig-x86-edit > Selecting the NTP checkbox during firstboot should probably bring up a > network connection if one isn't already up, though. Kindly please provide me with the web address where I may find this BETA.TC1 x86_64 to download Thanks Johan -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On 03/30/2011 06:29 PM, Adam Williamson wrote: > On Wed, 2011-03-30 at 12:20 -0600, Eric Blake wrote: >> On 03/30/2011 12:14 PM, Scott Robbins wrote: >>> I just did a default installation in Virtual Box, using the netboot.iso. >> Since Fedora ships qemu-kvm and not VirtualBox, I would be more >> interested in people trying out kvm virtualization to give our own >> products better testing. > Don't worry, a lot of people test that config too (it's actually in our > validation test suite). Perhaps it would be a nice idea to gather feed back from reporters using other virtualsation solutions as in what they like and dislike with ours and what they like and dislike in the other one as well? JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On 03/30/2011 05:50 PM, Adam Williamson wrote: > Selecting the NTP checkbox during firstboot should probably bring up a > network connection if one isn't already up, though. Hum not sure that would be something we wanted as in application to have the control start and stop over network connections. I'm not even sure if NTP should be configurable in Firstboot in graphical installations since the novice end user has absolutely no idea what that it is. But then again I've always thought Firstboot existence be a bit odd from end users perspective you simply should just be able to create a non root user account in Anaconda and configure the rest within the *DE. JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On Wed, 2011-03-30 at 12:20 -0600, Eric Blake wrote: > On 03/30/2011 12:14 PM, Scott Robbins wrote: > > I just did a default installation in Virtual Box, using the netboot.iso. > > Since Fedora ships qemu-kvm and not VirtualBox, I would be more > interested in people trying out kvm virtualization to give our own > products better testing. Don't worry, a lot of people test that config too (it's actually in our validation test suite). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On Wed, 2011-03-30 at 14:14 -0400, Scott Robbins wrote: > As it was a virtual machine (I guess that's the reason) Gnome 3 failed > to load. I then enabled 3D acceleration in VBox and gave it the > maximum allowable memory (128MB), and tried again. (This doesn't > affect me in real life, where I do minimal installations and use > openbox, but I was curious.) However, still no Gnome 3. I seem to > remember this being a known issue--or perhaps not even considered an > issue, that it won't work in many VMs. Yeah, it's a known issue. In theory we should be able to make it work with VBox's acceleration passthrough, in practice it doesn't, yet. It's mentioned in Common Bugs. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On 03/30/2011 12:14 PM, Scott Robbins wrote: > I just did a default installation in Virtual Box, using the netboot.iso. Since Fedora ships qemu-kvm and not VirtualBox, I would be more interested in people trying out kvm virtualization to give our own products better testing. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On Wed, Mar 30, 2011 at 10:50:56AM -0700, Adam Williamson wrote: > On Wed, 2011-03-30 at 13:44 -0400, James Laska wrote: > > On Wed, 2011-03-30 at 13:36 -0400, Gregory Woodbury wrote: > > > Downloaded BETA.TC1 x86_64 DVD.iso and did an install on a VBox guest. > > > > > > No glitches encountered during the install. > > > > > > One nit: NetworkManager isn't activated during the install so firstboot > > > isn't > > > network connected for the NTP setup dialogue. > > > > When performing a media-based (non-network) installation, networking is > > not enabled by default. If you perform an installation that uses a > > network-based package repository, networking will be enabled by default. I just did a default installation in Virtual Box, using the netboot.iso. One thing--I don't remember if this is a new improvement or not, but I find it automatically finds the server and gets the packages--I seem to remember I used to have to manually enter the url. Using network, as per what Adam says below, had my network running at boot. I like the default wallpaper too, nice choices. As it was a virtual machine (I guess that's the reason) Gnome 3 failed to load. I then enabled 3D acceleration in VBox and gave it the maximum allowable memory (128MB), and tried again. (This doesn't affect me in real life, where I do minimal installations and use openbox, but I was curious.) However, still no Gnome 3. I seem to remember this being a known issue--or perhaps not even considered an issue, that it won't work in many VMs. I see that if one adds the user to adminstrative groups, they are added to wheel, and that sudo now works. (In one of the earlier alphas, it didn't). All in all, seems to be running rather well at least in this cursory test installation. > > Selecting the NTP checkbox during firstboot should probably bring up a > network connection if one isn't already up, though. Correct in my case at least, see above. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Willow: I just talked to Buffy, and yeah, I think she's feeling a little... insane. No, not bitchy crazy, more like homicidal maniac crazy. So I told her to come see you, 'kay? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On Wed, 2011-03-30 at 13:44 -0400, James Laska wrote: > On Wed, 2011-03-30 at 13:36 -0400, Gregory Woodbury wrote: > > Downloaded BETA.TC1 x86_64 DVD.iso and did an install on a VBox guest. > > > > No glitches encountered during the install. > > > > One nit: NetworkManager isn't activated during the install so firstboot > > isn't > > network connected for the NTP setup dialogue. > > When performing a media-based (non-network) installation, networking is > not enabled by default. If you perform an installation that uses a > network-based package repository, networking will be enabled by default. > > For the media-based (non-network) use case, you can manually enable > networking by selecting 'Start automatically' for the appropriate device > from the network configuration dialog. > > http://docs.fedoraproject.org/en-US/Fedora/14/html/Installation_Guide/sn-Netconfig-x86.html#sn-Netconfig-x86-edit Selecting the NTP checkbox during firstboot should probably bring up a network connection if one isn't already up, though. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F15 BETA.TC1 experiences
On Wed, 2011-03-30 at 13:36 -0400, Gregory Woodbury wrote: > Downloaded BETA.TC1 x86_64 DVD.iso and did an install on a VBox guest. > > No glitches encountered during the install. > > One nit: NetworkManager isn't activated during the install so firstboot > isn't > network connected for the NTP setup dialogue. When performing a media-based (non-network) installation, networking is not enabled by default. If you perform an installation that uses a network-based package repository, networking will be enabled by default. For the media-based (non-network) use case, you can manually enable networking by selecting 'Start automatically' for the appropriate device from the network configuration dialog. http://docs.fedoraproject.org/en-US/Fedora/14/html/Installation_Guide/sn-Netconfig-x86.html#sn-Netconfig-x86-edit Thanks, James signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F15 BETA.TC1 experiences
Downloaded BETA.TC1 x86_64 DVD.iso and did an install on a VBox guest. No glitches encountered during the install. One nit: NetworkManager isn't activated during the install so firstboot isn't network connected for the NTP setup dialogue. Looks good to me. -- G.Wolfe Woodbury aka redwolfe (proventesters) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 15 Beta TC1 Available Now!
On Wed, 2011-03-30 at 09:46 -0700, Adam Williamson wrote: > Well, that's not exactly right. We don't expect everyone to be able to > reinstall all the time. To help with the formal validation testing > linked in the announcement mail you need to do a fresh install, but if > you just want to follow along with F15 development and catch bugs in > normal use, it's perfectly fine to just keep updating. ...updating F15, that is. As others have pointed out, Rawhide is something different. But if you just install an F15 pre-release and update as usual, you will get F15, not Rawhide. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 15 Beta TC1 Available Now!
On Wed, 2011-03-30 at 04:56 -0500, Mike Chambers wrote: > On Wed, 2011-03-30 at 13:12 +0530, Frederic Muller wrote: > > On 03/30/2011 09:24 AM, Adam Williamson wrote: > > > On Tue, 2011-03-29 at 23:29 -0400, Andre Robatino wrote: > > > > Fedora 15 Beta TC1 is now available [1]. Please refer to the following > > > > pages for download links and testing instructions. > > > Live images are not ready yet, there's a problem composing them which > > > we're currently looking into. We'll send out another announcement once > > > they're done. > > Hi! > > > > Are we supposed to simply upgrade rawhide, or should we make a fresh > > install from the live image? What do you prefer and what is required? > > Biggest test is either doing a fresh install or trying an upgrade from > F14 itself. > > Upgrading from rawhide or even F15 current isn't really helping and not > sure supported. Well, that's not exactly right. We don't expect everyone to be able to reinstall all the time. To help with the formal validation testing linked in the announcement mail you need to do a fresh install, but if you just want to follow along with F15 development and catch bugs in normal use, it's perfectly fine to just keep updating. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Updated boot.iso available for anaconda-15.25-1 karma feedback
Filed this bug as bug #692196 on bugzilla. Koos. Op 30-3-2011 15:02, A.J. Werkman schreef: Radek came up with a solution to the ipv6 boot option problem. This solution however rose another question: Why is there a prefix field in the UI but in the boot options the ipv6 parameter does not want a prefix? I would think that either - the prefix is relevant and then ipv6 boot option should accept a prefix or - it is not relevant and than the UI should not ask for the prefix. But probably this is a different issue. I initially thought the "bug" with the boot option could be related to the problem of the NM network UI to accept an ipv6 address. But I now think this relation isn't there. I wil retest this when I am back home again and report back my findings later. Koos. Op 30-3-2011 15:44, James Laska schreef: On Wed, 2011-03-30 at 08:55 +0200, A.J. Werkman wrote: I filled this bug in another setting, but I think the undelying problem is the same. Bug number is 691664. Are there screenshots that you want in particular? As I recall the information on the screen wasn't that exciting. Appears that won't be needed. It seems Radek responded already, can you retest with his suggestion? https://bugzilla.redhat.com/show_bug.cgi?id=691664#c5 Thanks, James smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Today's GNOME pathologies
Last build of gnome-shell (2.91.93-3) from koji solved dependencies problems around libtelepathy-logger. Le lundi 28 mars 2011 à 20:29 +0200, Pierre Jaury a écrit : > I also lost some icons and my background on rawhide, plus got errors > about glib schemas (which actualy make me grumpy too). > > Last update even broke dependencies around nm and libnm, getting yum > complaining about instant messaging, from empathy to gnome-shell, which > requires telepathy-logger. > > Since mutter won't start either, I'm still mining for interesting data > to report. > > Le lundi 28 mars 2011 à 11:22 -0600, Jonathan Corbet a écrit : > > So I just updated my Rawhide system. Items noticed in the first few > > minutes: > > > > - Blinking cursors are on everything and cannot be turned off. I *hate* > >blinking cursors. They make me Grumpy. > > > > - Lots of icons are missing. The "system settings" dialog is now mostly > >text. > > > > - Setting the background no longer works; it is pure black. > > > > Obviously something has gone a little funky somewhere; or is it only me? > > > > Thanks, > > > > jon > -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Extremly long login time in F15?
On 03/30/2011 03:01 PM, Panu Matilainen wrote: On 03/30/2011 11:05 AM, Joachim Backes wrote: On 03/30/2011 10:02 AM, Panu Matilainen wrote: On 03/30/2011 10:22 AM, Joachim Backes wrote: On 03/30/2011 09:14 AM, Panu Matilainen wrote: On 03/30/2011 08:07 AM, Joachim Backes wrote: Hi, I'm running F15 with gnome-shell. Having the following effect: after having entered the login password, it takes about 10-15 secs until the session is running and the gnome-shell panel appears at the desktop's top. For me, that extreme long: I have a dual core Intel CPU, both with 1.8 Ghz, and 2 Gigs of mem. Somebody can explain this effect? I'm seeing this too, both in Gnome 3 and XFCE sessions (where especially the latter should fire up in a blink of an eye), so it's something else than gnome-shell as such. Haven't got around to look into it (yet) though. Oh and no network filesystems involved here either. - Panu - Hi Panu, I took a look in /var/log/messages, and there is a time leap of 30 secs between Mar 30 08:57:03 . gdm-simple-greeter[6636]: DEBUG(+): GdmGreeterSession: Disposing greeter_session and Mar 30 08:57:33 . gdm-simple-slave[6573]: DEBUG(+): GdmCommon: process (pid:6597) done (status:0) Do you see similar things? Yes, very much the same, there's a 30 sec pause in the log: [...] Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: Stopping welcome_session Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: sending signal 15 to process 2184 Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: Waiting on process 2184 Mar 30 10:45:48 turre gnome-session[2184]: WARNING: Invalid method call: Argument 0 is specified to be of type "boolean", but is actually of type "uint32"#012 Mar 30 10:45:50 turre gnome-session[2184]: WARNING: Client '/org/gnome/SessionManager/Client2' failed to reply before timeout Mar 30 10:45:50 turre gnome-session[2184]: WARNING: Invalid method call: Argument 0 is specified to be of type "boolean", but is actually of type "uint32"#012 Mar 30 10:45:50 turre gdm-simple-greeter[2219]: DEBUG(+): GdmGreeterSession: Disposing greeter_session Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: process (pid:2184) done (status:0) Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: WelcomeSession died Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: De-registering session from ConsoleKit Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: Stopping D-Bus daemon Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: sending signal 15 to process -2182 Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GreeterServer: Stopping greeter server... [...] So quite apparently something is misfiring and there's a 30sec timeout on something, somewhere... Also I /think/ this didn't happen in F15-alpha originally when I installed it, Hi Panu, I can confirm this. This behaviour appeared after some updates. I don't know what updates are the culprit :-( Turns out the bug is in at-spi2-core, exposed by a change in the way gdm runs its login-screen gnome-session. Was fun to dig up :) For the impatient, 'yum remove "at-spi2*"' should do the trick until an update is built for https://bugzilla.redhat.com/show_bug.cgi?id=691995. Hi Panu, your trick was very helpful. (Re-) logging in now needs 1-2 seconds. Many thanks. -- Joachim Backes http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Updated boot.iso available for anaconda-15.25-1 karma feedback
Radek came up with a solution to the ipv6 boot option problem. This solution however rose another question: Why is there a prefix field in the UI but in the boot options the ipv6 parameter does not want a prefix? I would think that either - the prefix is relevant and then ipv6 boot option should accept a prefix or - it is not relevant and than the UI should not ask for the prefix. But probably this is a different issue. I initially thought the "bug" with the boot option could be related to the problem of the NM network UI to accept an ipv6 address. But I now think this relation isn't there. I wil retest this when I am back home again and report back my findings later. Koos. Op 30-3-2011 15:44, James Laska schreef: On Wed, 2011-03-30 at 08:55 +0200, A.J. Werkman wrote: I filled this bug in another setting, but I think the undelying problem is the same. Bug number is 691664. Are there screenshots that you want in particular? As I recall the information on the screen wasn't that exciting. Appears that won't be needed. It seems Radek responded already, can you retest with his suggestion? https://bugzilla.redhat.com/show_bug.cgi?id=691664#c5 Thanks, James smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Extremly long login time in F15?
Hi, When I boot up in runlevel 3 I see a delay of about 30 seconds in the kernel boot messages. I was wondering if this could correlate to the issue you discussed here. Koos. Op 30-3-2011 15:01, Panu Matilainen schreef: On 03/30/2011 11:05 AM, Joachim Backes wrote: On 03/30/2011 10:02 AM, Panu Matilainen wrote: On 03/30/2011 10:22 AM, Joachim Backes wrote: On 03/30/2011 09:14 AM, Panu Matilainen wrote: On 03/30/2011 08:07 AM, Joachim Backes wrote: Hi, I'm running F15 with gnome-shell. Having the following effect: after having entered the login password, it takes about 10-15 secs until the session is running and the gnome-shell panel appears at the desktop's top. For me, that extreme long: I have a dual core Intel CPU, both with 1.8 Ghz, and 2 Gigs of mem. Somebody can explain this effect? I'm seeing this too, both in Gnome 3 and XFCE sessions (where especially the latter should fire up in a blink of an eye), so it's something else than gnome-shell as such. Haven't got around to look into it (yet) though. Oh and no network filesystems involved here either. - Panu - Hi Panu, I took a look in /var/log/messages, and there is a time leap of 30 secs between Mar 30 08:57:03 . gdm-simple-greeter[6636]: DEBUG(+): GdmGreeterSession: Disposing greeter_session and Mar 30 08:57:33 . gdm-simple-slave[6573]: DEBUG(+): GdmCommon: process (pid:6597) done (status:0) Do you see similar things? Yes, very much the same, there's a 30 sec pause in the log: [...] Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: Stopping welcome_session Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: sending signal 15 to process 2184 Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: Waiting on process 2184 Mar 30 10:45:48 turre gnome-session[2184]: WARNING: Invalid method call: Argument 0 is specified to be of type "boolean", but is actually of type "uint32"#012 Mar 30 10:45:50 turre gnome-session[2184]: WARNING: Client '/org/gnome/SessionManager/Client2' failed to reply before timeout Mar 30 10:45:50 turre gnome-session[2184]: WARNING: Invalid method call: Argument 0 is specified to be of type "boolean", but is actually of type "uint32"#012 Mar 30 10:45:50 turre gdm-simple-greeter[2219]: DEBUG(+): GdmGreeterSession: Disposing greeter_session Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: process (pid:2184) done (status:0) Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: WelcomeSession died Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: De-registering session from ConsoleKit Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: Stopping D-Bus daemon Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: sending signal 15 to process -2182 Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GreeterServer: Stopping greeter server... [...] So quite apparently something is misfiring and there's a 30sec timeout on something, somewhere... Also I /think/ this didn't happen in F15-alpha originally when I installed it, Hi Panu, I can confirm this. This behaviour appeared after some updates. I don't know what updates are the culprit :-( Turns out the bug is in at-spi2-core, exposed by a change in the way gdm runs its login-screen gnome-session. Was fun to dig up :) For the impatient, 'yum remove "at-spi2*"' should do the trick until an update is built for https://bugzilla.redhat.com/show_bug.cgi?id=691995. - Panu - smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Updated boot.iso available for anaconda-15.25-1 karma feedback
On Wed, 2011-03-30 at 08:55 +0200, A.J. Werkman wrote: > I filled this bug in another setting, but I think the undelying problem > is the same. Bug number is 691664. > > Are there screenshots that you want in particular? As I recall the > information on the screen wasn't that exciting. Appears that won't be needed. It seems Radek responded already, can you retest with his suggestion? https://bugzilla.redhat.com/show_bug.cgi?id=691664#c5 Thanks, James signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 15 Beta TC1 Available Now!
On Wed, 30 Mar 2011 13:12:12 +0530, Frederic wrote: > On 03/30/2011 09:24 AM, Adam Williamson wrote:On Tue, 2011-03-29 at 23:29 > -0400, Andre Robatino wrote: > Fedora 15 Beta TC1 is now available [1]. Please refer to the following > pages for download links and testing instructions. > > Live images are not ready yet, there's a problem composing them which > we're currently looking into. We'll send out another announcement once > they're done. > Hi! > > Are we supposed to simply upgrade rawhide, or should we make a fresh install > from the live image? What do you prefer and what is required? > Rawhide is latest and currently is "Fedora 16 development", so don't try to "upgrade rawhide" with F-15 Beta. Try a fresh install or an upgrade of F-14. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Long systemd pauses mounting local filesystem/swap
On 03/30/2011 12:45 PM, Ian Pilcher wrote: > I just spent a long and frustrating night trying to recover my system > from what I believed was a complete hang on startup. It turns out that > it was just pausing for several minutes. > > I was finally able to track it down to these two lines in my /etc/fstab: > >UUID=67a74931-48ac-4bdd-91d2-3e788398d472 /boot ext4 defaults 1 2 >/dev/mapper/root_vg-swap_lv swap swap defaults 0 0 > > Commenting out these two lines enables the system to come up at its > usual speed. > > I tried using the filesystem LABEL for my /boot filesystem, but that > also caused the delay. > > Interestingly, this *does* work: > >/dev/md0 /boot ext4 defaults 1 2 >/dev/root_vg/swap_lv swap swap defaults 0 0 > > I'm way too tired to file a decent bug report now, but definitely > wondering if anyone else has seen anything like this. There is a default time out of 3 minutes in systemd for everything It would be good if you try the latest systemd release [1] along with the latest selinux-policy [2] and follow [3] and provide /etc/fstab when filing the report JBG 1. http://koji.fedoraproject.org/koji/packageinfo?packageID=10477 2. http://koji.fedoraproject.org/koji/packageinfo?packageID=32 3. http://fedoraproject.org/wiki/How_to_debug_Systemd_problems -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Extremly long login time in F15?
On 03/30/2011 11:05 AM, Joachim Backes wrote: > On 03/30/2011 10:02 AM, Panu Matilainen wrote: >> On 03/30/2011 10:22 AM, Joachim Backes wrote: >>> On 03/30/2011 09:14 AM, Panu Matilainen wrote: On 03/30/2011 08:07 AM, Joachim Backes wrote: > Hi, > > I'm running F15 with gnome-shell. > > Having the following effect: after having entered the login > password, it > takes about 10-15 secs until the session is running and the > gnome-shell > panel appears at the desktop's top. For me, that extreme long: I > have a > dual core Intel CPU, both with 1.8 Ghz, and 2 Gigs of mem. > > Somebody can explain this effect? I'm seeing this too, both in Gnome 3 and XFCE sessions (where especially the latter should fire up in a blink of an eye), so it's something else than gnome-shell as such. Haven't got around to look into it (yet) though. Oh and no network filesystems involved here either. - Panu - >>> >>> Hi Panu, >>> >>> I took a look in /var/log/messages, and there is a time leap of 30 secs >>> between >>> >>> Mar 30 08:57:03 . gdm-simple-greeter[6636]: DEBUG(+): >>> GdmGreeterSession: Disposing greeter_session >>> >>> and >>> >>> Mar 30 08:57:33 . gdm-simple-slave[6573]: DEBUG(+): GdmCommon: >>> process (pid:6597) done (status:0) >>> >>> Do you see similar things? >> >> Yes, very much the same, there's a 30 sec pause in the log: >> >> [...] >> Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): >> GdmWelcomeSession: Stopping welcome_session >> Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: >> sending signal 15 to process 2184 >> Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): >> GdmWelcomeSession: Waiting on process 2184 >> Mar 30 10:45:48 turre gnome-session[2184]: WARNING: Invalid method call: >> Argument 0 is specified to be of type "boolean", but is actually of type >> "uint32"#012 >> Mar 30 10:45:50 turre gnome-session[2184]: WARNING: Client >> '/org/gnome/SessionManager/Client2' failed to reply before timeout >> Mar 30 10:45:50 turre gnome-session[2184]: WARNING: Invalid method call: >> Argument 0 is specified to be of type "boolean", but is actually of type >> "uint32"#012 >> Mar 30 10:45:50 turre gdm-simple-greeter[2219]: DEBUG(+): >> GdmGreeterSession: Disposing greeter_session >> Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: >> process (pid:2184) done (status:0) >> Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): >> GdmWelcomeSession: WelcomeSession died >> Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): >> GdmWelcomeSession: De-registering session from ConsoleKit >> Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): >> GdmWelcomeSession: Stopping D-Bus daemon >> Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: >> sending signal 15 to process -2182 >> Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GreeterServer: >> Stopping greeter server... >> [...] >> >> So quite apparently something is misfiring and there's a 30sec timeout >> on something, somewhere... >> >> Also I /think/ this didn't happen in F15-alpha originally when I >> installed it, > > Hi Panu, > > I can confirm this. This behaviour appeared after some updates. I don't > know what updates are the culprit :-( Turns out the bug is in at-spi2-core, exposed by a change in the way gdm runs its login-screen gnome-session. Was fun to dig up :) For the impatient, 'yum remove "at-spi2*"' should do the trick until an update is built for https://bugzilla.redhat.com/show_bug.cgi?id=691995. - Panu - -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Long systemd pauses mounting local filesystem/swap
I just spent a long and frustrating night trying to recover my system from what I believed was a complete hang on startup. It turns out that it was just pausing for several minutes. I was finally able to track it down to these two lines in my /etc/fstab: UUID=67a74931-48ac-4bdd-91d2-3e788398d472 /boot ext4 defaults 1 2 /dev/mapper/root_vg-swap_lv swap swap defaults 0 0 Commenting out these two lines enables the system to come up at its usual speed. I tried using the filesystem LABEL for my /boot filesystem, but that also caused the delay. Interestingly, this *does* work: /dev/md0 /boot ext4 defaults 1 2 /dev/root_vg/swap_lv swap swap defaults 0 0 I'm way too tired to file a decent bug report now, but definitely wondering if anyone else has seen anything like this. TIA -- Ian Pilcher arequip...@gmail.com "If you're going to shift my paradigm ... at least buy me dinner first." -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: How do I add startup programs in Gnome 3? (Solved), ... (autologin SOLVED)
--- On Tue, 3/29/11, Mike Chambers wrote: > From: Mike Chambers > Subject: Re: How do I add startup programs in Gnome 3? (Solved), ... > (autologin SOLVED) > To: "For testing and quality assurance of Fedora releases" > > Date: Tuesday, March 29, 2011, 6:34 PM > On Tue, 2011-03-29 at 18:17 -0700, > Antonio Olivares wrote: > > > > --- On Tue, 3/29/11, Rahul Sundaram > wrote: > > > > Have you tried: > > > > > > /etc/gdm/custom.conf > > > > > > [daemon] > > > AutomaticLoginEnable=True > > > AutomaticLogin= > > > > > > --- > > > > Must have been a typo, or the other line > > TimedLoginDelay=0, Now it is working like a > champ! :) > > > > [students@localhost ~]$ cat /etc/gdm/custom.conf > > # GDM configuration storage > > > > [daemon] > > TimedLoginEnable=true > > TimedLogin=students > > Was neither, your using *timed* login and what Rahul posted > above is > *Automatic*. > > Might try what he has posted above again, using Automatic > and not timed > and see what happens. > > > AutomaticLoginEnable=True > AutomaticLogin= > > -- I did have it correct on the machine that I first tried it. Here's the output of the file: [students@maddog ~]$ cat /etc/gdm/custom.conf # GDM configuration storage [daemon] AutomaticLoginEnable=true AutomaticLogin=students #TimedLoginDelay=0 [security] [xdmcp] [greeter] [chooser] [debug] [students@maddog ~]$ It had TimedLoginDelay=0, and it was causing the problems. On the other two machines, I did have the other version: TimedLoginEnable=true TimedLogin=students Does it make sense now? I had the delay=0 and it was causing the trouble :( Thanks to all who have helped me get this working. My students are appreciative as they do not have to type a password to get to use the computers. Regards, Antonio [students@maddog ~]$ cat /etc/fedora-release Fedora release 15 (Lovelock) [students@maddog ~]$ uname -r 2.6.38.2-8.fc15.x86_64 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 15 Beta TC1 Available Now!
On Wed, 2011-03-30 at 13:12 +0530, Frederic Muller wrote: > On 03/30/2011 09:24 AM, Adam Williamson wrote: > > On Tue, 2011-03-29 at 23:29 -0400, Andre Robatino wrote: > > > Fedora 15 Beta TC1 is now available [1]. Please refer to the following > > > pages for download links and testing instructions. > > Live images are not ready yet, there's a problem composing them which > > we're currently looking into. We'll send out another announcement once > > they're done. > Hi! > > Are we supposed to simply upgrade rawhide, or should we make a fresh > install from the live image? What do you prefer and what is required? Biggest test is either doing a fresh install or trying an upgrade from F14 itself. Upgrading from rawhide or even F15 current isn't really helping and not sure supported. -- Mike Chambers Madisonville, KY "The best town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Extremly long login time in F15?
On 03/30/2011 10:02 AM, Panu Matilainen wrote: On 03/30/2011 10:22 AM, Joachim Backes wrote: On 03/30/2011 09:14 AM, Panu Matilainen wrote: On 03/30/2011 08:07 AM, Joachim Backes wrote: Hi, I'm running F15 with gnome-shell. Having the following effect: after having entered the login password, it takes about 10-15 secs until the session is running and the gnome-shell panel appears at the desktop's top. For me, that extreme long: I have a dual core Intel CPU, both with 1.8 Ghz, and 2 Gigs of mem. Somebody can explain this effect? I'm seeing this too, both in Gnome 3 and XFCE sessions (where especially the latter should fire up in a blink of an eye), so it's something else than gnome-shell as such. Haven't got around to look into it (yet) though. Oh and no network filesystems involved here either. - Panu - Hi Panu, I took a look in /var/log/messages, and there is a time leap of 30 secs between Mar 30 08:57:03 . gdm-simple-greeter[6636]: DEBUG(+): GdmGreeterSession: Disposing greeter_session and Mar 30 08:57:33 . gdm-simple-slave[6573]: DEBUG(+): GdmCommon: process (pid:6597) done (status:0) Do you see similar things? Yes, very much the same, there's a 30 sec pause in the log: [...] Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: Stopping welcome_session Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: sending signal 15 to process 2184 Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: Waiting on process 2184 Mar 30 10:45:48 turre gnome-session[2184]: WARNING: Invalid method call: Argument 0 is specified to be of type "boolean", but is actually of type "uint32"#012 Mar 30 10:45:50 turre gnome-session[2184]: WARNING: Client '/org/gnome/SessionManager/Client2' failed to reply before timeout Mar 30 10:45:50 turre gnome-session[2184]: WARNING: Invalid method call: Argument 0 is specified to be of type "boolean", but is actually of type "uint32"#012 Mar 30 10:45:50 turre gdm-simple-greeter[2219]: DEBUG(+): GdmGreeterSession: Disposing greeter_session Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: process (pid:2184) done (status:0) Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: WelcomeSession died Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: De-registering session from ConsoleKit Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: Stopping D-Bus daemon Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: sending signal 15 to process -2182 Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GreeterServer: Stopping greeter server... [...] So quite apparently something is misfiring and there's a 30sec timeout on something, somewhere... Also I /think/ this didn't happen in F15-alpha originally when I installed it, Hi Panu, I can confirm this. This behaviour appeared after some updates. I don't know what updates are the culprit :-( Kind regards -- Joachim Backes http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Extremly long login time in F15?
On 03/30/2011 10:22 AM, Joachim Backes wrote: > On 03/30/2011 09:14 AM, Panu Matilainen wrote: >> On 03/30/2011 08:07 AM, Joachim Backes wrote: >>> Hi, >>> >>> I'm running F15 with gnome-shell. >>> >>> Having the following effect: after having entered the login password, it >>> takes about 10-15 secs until the session is running and the gnome-shell >>> panel appears at the desktop's top. For me, that extreme long: I have a >>> dual core Intel CPU, both with 1.8 Ghz, and 2 Gigs of mem. >>> >>> Somebody can explain this effect? >> >> I'm seeing this too, both in Gnome 3 and XFCE sessions (where especially >> the latter should fire up in a blink of an eye), so it's something else >> than gnome-shell as such. Haven't got around to look into it (yet) >> though. Oh and no network filesystems involved here either. >> >> - Panu - > > Hi Panu, > > I took a look in /var/log/messages, and there is a time leap of 30 secs > between > > Mar 30 08:57:03 . gdm-simple-greeter[6636]: DEBUG(+): > GdmGreeterSession: Disposing greeter_session > > and > > Mar 30 08:57:33 . gdm-simple-slave[6573]: DEBUG(+): GdmCommon: > process (pid:6597) done (status:0) > > Do you see similar things? Yes, very much the same, there's a 30 sec pause in the log: [...] Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: Stopping welcome_session Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: sending signal 15 to process 2184 Mar 30 10:45:48 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: Waiting on process 2184 Mar 30 10:45:48 turre gnome-session[2184]: WARNING: Invalid method call: Argument 0 is specified to be of type "boolean", but is actually of type "uint32"#012 Mar 30 10:45:50 turre gnome-session[2184]: WARNING: Client '/org/gnome/SessionManager/Client2' failed to reply before timeout Mar 30 10:45:50 turre gnome-session[2184]: WARNING: Invalid method call: Argument 0 is specified to be of type "boolean", but is actually of type "uint32"#012 Mar 30 10:45:50 turre gdm-simple-greeter[2219]: DEBUG(+): GdmGreeterSession: Disposing greeter_session Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: process (pid:2184) done (status:0) Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: WelcomeSession died Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: De-registering session from ConsoleKit Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmWelcomeSession: Stopping D-Bus daemon Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GdmCommon: sending signal 15 to process -2182 Mar 30 10:46:20 turre gdm-simple-slave[2160]: DEBUG(+): GreeterServer: Stopping greeter server... [...] So quite apparently something is misfiring and there's a 30sec timeout on something, somewhere... Also I /think/ this didn't happen in F15-alpha originally when I installed it, but I could easily be wrong on that (too many things going on for the poor mind to keep up :) - Panu - -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 15 Beta TC1 Available Now!
On 03/30/2011 09:24 AM, Adam Williamson wrote: On Tue, 2011-03-29 at 23:29 -0400, Andre Robatino wrote: Fedora 15 Beta TC1 is now available [1]. Please refer to the following pages for download links and testing instructions. Live images are not ready yet, there's a problem composing them which we're currently looking into. We'll send out another announcement once they're done. Hi! Are we supposed to simply upgrade rawhide, or should we make a fresh install from the live image? What do you prefer and what is required? Thanks Fred -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Extremly long login time in F15?
On 03/30/2011 09:14 AM, Panu Matilainen wrote: On 03/30/2011 08:07 AM, Joachim Backes wrote: Hi, I'm running F15 with gnome-shell. Having the following effect: after having entered the login password, it takes about 10-15 secs until the session is running and the gnome-shell panel appears at the desktop's top. For me, that extreme long: I have a dual core Intel CPU, both with 1.8 Ghz, and 2 Gigs of mem. Somebody can explain this effect? I'm seeing this too, both in Gnome 3 and XFCE sessions (where especially the latter should fire up in a blink of an eye), so it's something else than gnome-shell as such. Haven't got around to look into it (yet) though. Oh and no network filesystems involved here either. - Panu - Hi Panu, I took a look in /var/log/messages, and there is a time leap of 30 secs between Mar 30 08:57:03 . gdm-simple-greeter[6636]: DEBUG(+): GdmGreeterSession: Disposing greeter_session and Mar 30 08:57:33 . gdm-simple-slave[6573]: DEBUG(+): GdmCommon: process (pid:6597) done (status:0) Do you see similar things? Kind regards -- Joachim Backes http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Extremly long login time in F15?
On 03/30/2011 08:07 AM, Joachim Backes wrote: > Hi, > > I'm running F15 with gnome-shell. > > Having the following effect: after having entered the login password, it > takes about 10-15 secs until the session is running and the gnome-shell > panel appears at the desktop's top. For me, that extreme long: I have a > dual core Intel CPU, both with 1.8 Ghz, and 2 Gigs of mem. > > Somebody can explain this effect? I'm seeing this too, both in Gnome 3 and XFCE sessions (where especially the latter should fire up in a blink of an eye), so it's something else than gnome-shell as such. Haven't got around to look into it (yet) though. Oh and no network filesystems involved here either. - Panu - -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
