lock screen phantom typing
More Gnome problems: For the second time, I came back to my F24 Gnome workstation at the lock screen this morning, and I was unable to type my password to unlock the screen because some phantom keyboard input was continuously entering characters into the password field. If I typed backspace, it deleted the characters, but more characters continued to appear. Anyone else seeing this problem? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: window manager/focus problems
On Thu, Jul 21, 2016 at 09:47:15AM -0600, Chris Murphy wrote: > On Thu, Jul 21, 2016 at 9:08 AM, Chuck Anderson <c...@wpi.edu> wrote: > > I just upgraded to Fedora 24 and the Gnome window manager sometimes > > gets stuck such that I can't move windows anymore. Focus also seems > > to get stuck in virt-manager/virt-viewer. Anyone else having this > > problem? > > Maybe. The problem I've had is when I'm in Activities view, where > application windows are zoomed out and tiled so I can see all of them > - I'm using the command key to do this, which I think is the > "windows" key on some keyboards, I guess sometimes it's called the > magic key. > > Anyway, when I hit that, it usually works but sometimes I can't get > out of that by clicking with the mouse. Escape key works, but that was > the only key that worked. Nothing else on the keyboard or mouse click > did anything. I'm not experiencing that particular problem. I just tried hitting the "windows" key to open the Activities view and was able to exit using either the "windows" key, a mouse click on a window, a mouse click on the Activities menu in the upper left, moving the mouse into the Activities "hot corner", or using the Escape key. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
window manager/focus problems
I just upgraded to Fedora 24 and the Gnome window manager sometimes gets stuck such that I can't move windows anymore. Focus also seems to get stuck in virt-manager/virt-viewer. Anyone else having this problem? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Did luks get broken in f24?
On Tue, Mar 01, 2016 at 01:41:22PM -0600, Bruno Wolff III wrote: > I updated my kernel this morning and my disk password doesn't seem > to work when booting with that kernel (multiple tries), but did work > with the previous kernel. Is this perhaps glibc fallout with dracut? FWIW, on F25 (rawhide, not branched) I updated/rebooted kernel/glibc/etc. this morning and my laptop with LUKS still works. I didn't have to jump through hoops with dracut, but I did have to install glibc-langpack-en in order for gnome-terminal to work. -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Weird effect of mount command in F23
On Tue, Oct 20, 2015 at 07:12:36PM +0200, Joachim Backes wrote: > On 20.10.2015 17:41, Richard Ryniker wrote: > >I suspect you suffer from software that wants to help you and "Do the > >right thing." > > > > Exactly. When mounting HD's, *one* mount command is enough for > achieving this, but for removable optical media (like CD's), I need > at least 2 commands, if the media is not loaded. That's what I don't > understand. Accessing the device node is apparently causing the tray to close. Why do you not close the tray first with the button on the drive before trying the mount? > >If you try to mount a device with no media, mount might simply fail (no > >media present). Instead, at least for optical drives, it presumes the > >desired media might be available in the tray and requests the device to > >load media, then tries again to mount a file system from this device. > > This is exactly my question: why mount is able to load the media, > but doesn't include it correctly into the filesystem? It seems like it doesn't wait long enough for the tray to close before giving up. You can try closing the tray first with this command: eject -t From man eject: -t, --trayclose With this option the drive is given a CD-ROM tray close command. Not all devices support this command. and then do the mount, perhaps with a "sleep" in there: eject -t sleep 5 mount ... -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F21 Beta TC3 refused to mount NTFS partition
Windows 8 does not shutdown when you tell it to shutdown. Instead it partially hibernates. To be sure that Windows 8 really shuts down, either turn off the Fast Startup (aka hybrid boot, aka hybrid shutdown) option in Windows 8 (not in the BIOS/UEFI), or do a Restart in Windows 8 but then choose to boot Fedora before Windows starts. http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html On Mon, Oct 13, 2014 at 10:53:30AM -0400, Joerg Lechner wrote: Hi, I don't find a fast restart button in the BIOS. Windows 8.1 I have to run in UEFI Mode. For F21 I have to switch to Legacy Mode. There is in UEFI Mode a button Secure Boot Mode which is on standard. Anyway I did several Boots of Windows, switched to Legacy F21 and back to Windows etc. In one of my trials I could access in F21 Beta TC3 the Windows disk, but currently there is this Error Message again. Possibly there is an influence of the UEFI mode sometimes, in this case I would think it's a BIOS problem and not F21. But I didn't have a problem like that previously in F21 Alpha and Beta TC2. Kind Regards -Ursprüngliche Mitteilung- Von: Kamil Paral kpa...@redhat.com An: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Verschickt: Mo, 13 Okt 2014 2:21 pm Betreff: Re: F21 Beta TC3 refused to mount NTFS partition Error mounting /dev/sda4 at /run/media/joerg/Acer: Command-line `mount -t ntfs -o uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177 /dev/sda4 /run/media/joerg/Acer' exited with non-zero exit status 14: Windows is hibernated, refused to mount. Failed to mount '/dev/sda4': Die Operation ist nicht erlaubt The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option. Is this a ok for F21 Beta TC3? Is the partition check in TC3 more detailed now and my Windows (currently shut down) really is in an unsafe state? Most likely your Windows is not shut down, because you have not disabled 'fast restart' feature, as the error message suggests. Or have you? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: can someone suggest why firefox is so $*^%*#^%* slow?
On Fri, Sep 26, 2014 at 07:36:19PM -0700, Adam Williamson wrote: On Wed, 2014-09-24 at 10:44 -0400, Robert P. J. Day wrote: i am at my wit's end with firefox on my fedora rawhide system -- to say it's nad-grindingly slow would be charitable. just now, i tried clicking on another tab ... some 30 seconds later, i am still waiting for the tab to change, oh, wait, there it is. watching any sort of youtube video is excruciating ... while audio is typically, i will frequently get *maybe* one frame change a second, i kid you not. i frequently get javascripts that are not responding, and i'm asked whether i want to wait for them. is there *something* i can do to debug this? what firefox configuration settings should i be looking at? i'm willing to try anything because, at this point, firefox is utterly unusable. even something as simple as scrolling in a window is painfully slow. oh, and i'm on a quad core i7, so i'm pretty sure horsepower isn't the problem. FWIW, I've been seeing some odd 'laggy' behaviour in F21 on my desktop lately, which does mostly seem to be in Firefox. I do have sixteen zillion tabs open, but I do that a lot and it's not happened before, and RAM isn't exhausted (I have 16GB, using about 8GB). I don't have Flash installed. Not had time to look into it in more detail yet, but it does seem like something squiffy is going on. The symptoms are basically that things like switching tabs, highlighting text, copy/pasting, or input appearing after I start to type lag by 1-3 seconds, and sometimes presses/characters that occur within the lag time are lost. I'm having problems with FF on Fedora 19 that just started recently, maybe related, maybe not. In my case, the entire desktop is freezing--even the mouse cursor won't move for 5-10 seconds. It always seems to happen when opening a new blank tab in FF. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: new f19/f20 images
On Wed, Apr 16, 2014 at 11:23:15PM +0200, drago01 wrote: On Wed, Apr 16, 2014 at 9:11 PM, Kevin Fenzi ke...@scrye.com wrote: Greetings. We have new f19/f20 images with openssl updated, and they appear to be default/live already. Were we waiting for some testing runs on them before announcing? (Which we should have done before making them live, imho) Or did that already happen? Did we want to do a full test cycle on them? Or just openssl related actions? Huh? Since when do we do something like this? Sounds like an over reaction to me. Installing (security) updates is the first thing you should do after installing anyway and besides who decided this and when? What are the criteria for doing updated images? Live images can't be updated... -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: new f19/f20 images
On Thu, Apr 17, 2014 at 02:52:41PM +0200, drago01 wrote: On Thu, Apr 17, 2014 at 2:51 PM, Chuck Anderson c...@wpi.edu wrote: On Wed, Apr 16, 2014 at 11:23:15PM +0200, drago01 wrote: On Wed, Apr 16, 2014 at 9:11 PM, Kevin Fenzi ke...@scrye.com wrote: Greetings. We have new f19/f20 images with openssl updated, and they appear to be default/live already. Were we waiting for some testing runs on them before announcing? (Which we should have done before making them live, imho) Or did that already happen? Did we want to do a full test cycle on them? Or just openssl related actions? Huh? Since when do we do something like this? Sounds like an over reaction to me. Installing (security) updates is the first thing you should do after installing anyway and besides who decided this and when? What are the criteria for doing updated images? Live images can't be updated... 1) They can 2) Live images are not supposed be used for production .. 1) Sure if you have a persistent live image on a USB I suppose. But with CD/DVD media, you cannot update and then reboot as is necessary to fix the issue. You can manually restart all processes/services that were linked against the old openssl I suppose, but you would have to go through this dance after every single boot to remove this vulnerability. 2) Live images could be used to rescue/repair a production environment, or could be used as a client to access a production environment. For example one could be using curl which is linked against the bad openssl. We shouldn't leave our users exposed if they decide to use a live image, especially since I don't think it is documented anywhere that these images are unsuitable for use in a production environment. Additionally, I believe we should somehow clearly mark all the new images so that we can easily tell if they are the updated ones or not. Maybe call them Fedora releases 19.1 and 20.1. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: new f19/f20 images
On Thu, Apr 17, 2014 at 03:11:38PM +0200, drago01 wrote: On Thu, Apr 17, 2014 at 3:02 PM, Chuck Anderson c...@wpi.edu wrote: On Thu, Apr 17, 2014 at 02:52:41PM +0200, drago01 wrote: On Thu, Apr 17, 2014 at 2:51 PM, Chuck Anderson c...@wpi.edu wrote: On Wed, Apr 16, 2014 at 11:23:15PM +0200, drago01 wrote: On Wed, Apr 16, 2014 at 9:11 PM, Kevin Fenzi ke...@scrye.com wrote: Greetings. We have new f19/f20 images with openssl updated, and they appear to be default/live already. Were we waiting for some testing runs on them before announcing? (Which we should have done before making them live, imho) Or did that already happen? Did we want to do a full test cycle on them? Or just openssl related actions? Huh? Since when do we do something like this? Sounds like an over reaction to me. Installing (security) updates is the first thing you should do after installing anyway and besides who decided this and when? What are the criteria for doing updated images? Live images can't be updated... 1) They can 2) Live images are not supposed be used for production .. 1) Sure if you have a persistent live image on a USB I suppose. But with CD/DVD media, you cannot update and then reboot as is necessary to fix the issue. You can manually restart all processes/services that were linked against the old openssl I suppose, but you would have to go through this dance after every single boot to remove this vulnerability. Which service do we install and run by default that uses OpenSSL and is configured to use SSL on the live media? - Answer is none. 2) Live images could be used to rescue/repair a production environment, See above. or could be used as a client to access a production environment. For example one could be using curl which is linked against the bad openssl. curl is a client. Clients ARE affected: http://security.stackexchange.com/questions/55119/does-the-heartbleed-vulnerability-affect-clients-as-severely Does anaconda or yum use OpenSSL? Because then yum updates and liveinst are potentially affected. Does libvirt/virt-manager/virt-viewer use OpenSSL? Because I could certainly see a sysadmin using a Live image to run virt-manager/virt-viewer to connect over the network via SSL to a hypervisor. Do VNC/RDP clients use OpenSSL? rdesktop is linked against an OpenSSL library. It may be possible to exploit it. We shouldn't leave our users exposed if they decide to use a live image, especially since I don't think it is documented anywhere that these images are unsuitable for use in a production environment. There are unsuitable by their very nature of being live images. Why are we shipping unsuitable software then? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Gnome 3.10: Network UI missing from new system status area
On Fri, Oct 04, 2013 at 01:54:17PM +0100, Adam Williamson wrote: On Fri, 2013-10-04 at 07:54 +0200, moshe nahmias wrote: I think that it must be possible to make the icon visible as an option. I use a cellular modem on my laptop and the easiest way to connect with it to the net is by clicking that icon... I guess that it's possible to connect from other places, but it won't be as easy. GNOME 3.10 has a combined system tray. Your cellular connection will be visible in it. (In other words, don't worry, it will work exactly how you expect it to). The change we're discussing applies only to boring plain wired ethernet connections. Use Case #1 for having the wired connection icon show at all times is to know when your network connection isn't working locally, as opposed to some remote problem. If you are connected to your LAN, the icon would show connected, but if your WAN/Internet connection is down, google.com will fail to connect. This is the first question any tech support person would ask the end user--does your computer show that it is connected (do you have a link light on the NIC)? We should be making this determination easier, not harder. Use Case #2 is for switching between different wired network configuration profiles and turning multiple NICs on or off. Why are we adding more and more functionality to NetworkManager, just to take it away from the user interface? I guess we'll need yet another GNOME Shell extension to fix this too. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Gnome 3.10: Network UI missing from new system status area
On Fri, Oct 04, 2013 at 03:17:03PM +0200, drago01 wrote: On Fri, Oct 4, 2013 at 3:05 PM, Chuck Anderson c...@wpi.edu wrote: On Fri, Oct 04, 2013 at 01:54:17PM +0100, Adam Williamson wrote: On Fri, 2013-10-04 at 07:54 +0200, moshe nahmias wrote: I think that it must be possible to make the icon visible as an option. I use a cellular modem on my laptop and the easiest way to connect with it to the net is by clicking that icon... I guess that it's possible to connect from other places, but it won't be as easy. GNOME 3.10 has a combined system tray. Your cellular connection will be visible in it. (In other words, don't worry, it will work exactly how you expect it to). The change we're discussing applies only to boring plain wired ethernet connections. Use Case #1 for having the wired connection icon show at all times is to know when your network connection isn't working locally, as opposed to some remote problem. If you are connected to your LAN, the icon would show connected, but if your WAN/Internet connection is down, google.com will fail to connect. This is the first question any tech support person would ask the end user--does your computer show that it is connected (do you have a link light on the NIC)? We should be making this determination easier, not harder. Use Case #2 is for switching between different wired network configuration profiles and turning multiple NICs on or off. Why are we adding more and more functionality to NetworkManager, just to take it away from the user interface? https://bugzilla.gnome.org/show_bug.cgi?id=708966 is the upstream bug ... if you have anything useful (i.e no flamebait) to add ad it there. Thanks, done. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
can't login to rawhide nightly live images
Are the nightly rawhide live images supposed to be login-able? I tried XFCE from the 7th and Desktop from the 4th, and cannot login using root or liveuser on either, so they are unusable (unless someone can tell me a secret way to break in--systemd.unit=rescue.target and systemd.unit=emergency.target both require sulogin). Fedora-20-Nightly-i686-Live-desktop-20130804.15-1.iso Fedora-20-Nightly-i686-Live-xfce-20130807.10-1.iso Fedora-20-Nightly-x86_64-Live-xfce-20130807.10-1.iso -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F17 yum/rpm not running groupadd in %pre scripts
I ran into a comedy of errors today after I did a new F17 installation yesterday. Here are a couple: https://bugzilla.redhat.com/show_bug.cgi?id=848148 Error in PREIN scriptlet in rpm package wireshark-1.6.9-1.fc17.x86_64 (and why does yum still let the transaction succeed, creating problems in the RPMDB, broken dependencies?) https://bugzilla.redhat.com/show_bug.cgi?id=845671 Directory '/var/run/screen' must have mode 777. when opening screen (and why does systemd-tmpfiles completely fail to start when there is a missing group--it should fail gracefully, allowing the other tmpfiles stuff to run and the service as a whole to run) Both of these are traceable to missing entries in /etc/group. In the former cae, there is an explicit Error in PREIN script during instalation. In the latter case, there is only a warning and installation proceeds: Running Transaction Installing : screen-4.1.0-0.9.20120314git3c2946.fc17.x86_64 1/1 warning: group screen does not exist - using root warning: group screen does not exist - using root So what is going on with %pre not running groupadd properly? Are there any known issues in this area? Thanks. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17 yum/rpm not running groupadd in %pre scripts
On Tue, Aug 14, 2012 at 09:33:36PM -0500, Rex Dieter wrote: Chuck Anderson wrote: I ran into a comedy of errors today after I did a new F17 installation yesterday. Here are a couple: https://bugzilla.redhat.com/show_bug.cgi?id=848148 Error in PREIN scriptlet in rpm package wireshark-1.6.9-1.fc17.x86_64 (and why does yum still let the transaction succeed, creating problems in the RPMDB, broken dependencies?) Still need to file a bug on yum for this one. yum should have failed the transaction rather than allow a package to be installed with missing deps. I believe your suspicions are correct. ... So what is going on with %pre not running groupadd properly? Are there any known issues in this area? Maybe try running the scriptlet by hand? %pre /usr/sbin/groupadd -g 84 -r -f screen and and try to figure out why it fails on your box. Already found the problem in selinux-policy: https://bugzilla.redhat.com/show_bug.cgi?id=844167 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 17 Final Release Candidate 4 (RC4) Available Now!
On Wed, May 23, 2012 at 09:14:21AM -0400, Andre Robatino wrote: Bruno Wolff III wrote: Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test It looks like this page needs to be updated for RC4. (I remember that most RC3 results were supposed to be transferred so I didn't want to go change things from RC3 to RC4, but at list the download link should get updated.) I don't know why people are seeing outdated links. I updated all four redirect links, including this one (see the history on https://fedoraproject.org/w/index.php?title=Test_Results:Current_Installation_Testredirect=no ) just before the announcement, it currently points to the RC4 page, and the download link on that is correct as well. The same was true the earlier time when someone said the link was wrong. P.S. Sorry for replying out of thread, but this message doesn't appear on Gmane. I often see a cached copy of the test result pages, and need to do a Ctrl-R to reload them before the new version shows up. Is there a way we can set a No-Cache header or something on them? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: abrt backtrace failures
This is: https://bugzilla.redhat.com/show_bug.cgi?id=750616 On Wed, May 23, 2012 at 12:06:20AM -0400, Chuck Anderson wrote: During F17 RC testing, twice now [1][2] I've been unable to submit bugs using abrt because the backtrace was considered unusable by abrt. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 16 Final Release Candidate 3 (RC3) Available Now!
On Mon, Oct 31, 2011 at 11:03:12PM -0700, Adam Williamson wrote: On Tue, 2011-11-01 at 01:09 -0400, Andre Robatino wrote: As per the Fedora 16 schedule [1], Fedora 16 Final Release Candidate 3 (RC3) is now available for testing. Please see the following pages for download links (including delta ISOs) and testing instructions. Serverbeach1 is still available as a mirror (but with approximately a 1 hour lag behind dl), so if you are getting a slow download, try replacing dl with serverbeach1 in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Security Lab: https://fedoraproject.org/wiki/Test_Results:Current_Security_Lab_Test Ideally, all Alpha, Beta, and Final priority test cases for Installation [2], Base [3], Desktop [4], and Security Lab [5] should pass in order to meet the Final Release Criteria [6]. Help is available on #fedora-qa on irc.freenode.net [7], or on the test list [8]. As mentioned before, we don't really need to re-do the whole set of tests, but it'd be good to get a few done just to make sure the RC3 image hasn't gone horribly wrong somehow. The only things that should have changed are KDE and Xfce bug fixes. To check the KDE issue, install F15 from the KDE live spin then try upgrading with the F16 RC3 DVD; it should work. Whether by luck-of-the-draw or not, efidisk.img appears correct (i.e. non-zeroed content) in this release! -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Pre RC4 install testing
On Tue, Nov 01, 2011 at 04:08:19PM -0600, Tim Flink wrote: I keep saying this but this will hopfully be the last test boot.iso for Fedora 16. http://tflink.fedorapeople.org/iso/2001_preRc4.x64.boot.iso http://tflink.fedorapeople.org/iso/2001_preRc4.x64.boot.iso.sha256 The only thing in these isos that has an update at the moment is dracut: - https://admin.fedoraproject.org/updates/dracut-013-18.fc16 The new kernel build that I used (3.1.0-7.fc16) doesn't have an update yet but should have one soon. The bugs that can be tested with this iso are: - https://bugzilla.redhat.com/show_bug.cgi?id=748516 * This iso has the new kernel build on it, should boot on EFI machines that were affected. - https://bugzilla.redhat.com/show_bug.cgi?id=750228 * I have no EFI machines to test with, let me know if the test iso has issues with the efidisk.img - https://bugzilla.redhat.com/show_bug.cgi?id=750603 * Kickstart File Path Ks Cfg [1] If you have the time, please give the image a whirl so that we can catch any issues (if there are any) before RC4 get spun up. All looks good. EFI USB w/efidisk.img, Legacy BIOS dd ISO to USB, new kernel update. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC status update - please pull livecd-tools-16.8 into buildroot
On Sun, Oct 30, 2011 at 03:56:37PM -0500, Dennis Gilmore wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 El Sun, 30 Oct 2011 11:26:45 -0700 Adam Williamson awill...@redhat.com escribió: On Sun, 2011-10-30 at 10:50 -0700, Adam Williamson wrote: On Sun, 2011-10-30 at 11:58 -0400, Chuck Anderson wrote: On Sun, Oct 30, 2011 at 10:11:07AM -0400, Chuck Anderson wrote: On Sat, Oct 29, 2011 at 05:53:10PM -0700, Adam Williamson wrote: Hey folks, just to let you know - I've requested an RC2 build: https://fedorahosted.org/rel-eng/ticket/4967#comment:6 Will this build be done with livecd-tools-16.8 so the livecd images pick up the fix for efi boot rd.* kernel args? RC1 didn't have it. I see in the koji task that 16.6 was still in the buildroot (root.log) despite 16.8 being in stable. Can you please be sure to pull 16.8 into the buildroot for future RC's? Thanks. There won't necessarily *be* any future RCs, but I'll talk to dennis about it. We're going to a silent re-spin (so don't tell anyone!) of the RC2 lives, using livecd-tools-16.8. It's a single pretty well-tested change so should be fine. Only impact is on the kernel parameters used when booting live via EFI. Should be up in 3hrs or so, will simply silently replace the existing RC2 live images. and its done. new images in place. please test. Thanks for the re-spin! Tested Live Desktop x86_64 both EFI and non-EFI, works fine and fixes the kernel args. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC status update
On Sat, Oct 29, 2011 at 05:53:10PM -0700, Adam Williamson wrote: Hey folks, just to let you know - I've requested an RC2 build: https://fedorahosted.org/rel-eng/ticket/4967#comment:6 Will this build be done with livecd-tools-16.8 so the livecd images pick up the fix for efi boot rd.* kernel args? RC1 didn't have it. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC status update - please pull livecd-tools-16.8 into buildroot
On Sun, Oct 30, 2011 at 10:11:07AM -0400, Chuck Anderson wrote: On Sat, Oct 29, 2011 at 05:53:10PM -0700, Adam Williamson wrote: Hey folks, just to let you know - I've requested an RC2 build: https://fedorahosted.org/rel-eng/ticket/4967#comment:6 Will this build be done with livecd-tools-16.8 so the livecd images pick up the fix for efi boot rd.* kernel args? RC1 didn't have it. I see in the koji task that 16.6 was still in the buildroot (root.log) despite 16.8 being in stable. Can you please be sure to pull 16.8 into the buildroot for future RC's? Thanks. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: workspace background overlay
On Fri, Oct 14, 2011 at 06:46:57PM +0800, Frederic Muller wrote: I'm using the Gallium 0.4 on ATI RV515 and when using multiple workspaces I am getting workspace 2 under workspace 1 in the overview view. Switching between workspaces seems ok so apparently it's only happening on workspace 1 view. Sometimes it's all workspaces stacked up, sometimes only 1 over 2. and then I also get bits of application windows at the top of the screen not disappearing. Look at the screenshot for more details (you can see pidgin in the background, which is from workspace 2). Am I the only one getting this (seems the artifacts I had in F15 are gone though)? No, I was seeing it as well on Intel graphics, although I'm not seeing it at the moment... -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Can't login via GDM anyomre: Re: Fedora 16 updates-testing report
On Sun, Sep 25, 2011 at 05:21:56PM -0400, Matthias Clasen wrote: On Sat, 2011-09-24 at 19:11 -0400, Janina Sajka wrote: Matthias Clasen writes: On Thu, 2011-09-22 at 14:05 -0400, Matthias Clasen wrote: On Thu, 2011-09-22 at 09:12 -0400, Chuck Anderson wrote: Beware the gigantic gnome 3.1.92 update. Something in this transaction broke the ability for me to log in at all via GDM. You type your password, and hit enter, nothing happens. Click Sign In button, nothing happens. You are likely hitting a race in the a11y key event handling at session end (the session being the login screen here). I've been seeing that myself with .92. We're working on it. This should be fixed in at-spi2-atk-2.1.92-2.fc16. I now have at-spi2-atk-2.1.92-2 (from Koji), but no joy--sorry to say. I need some information on what is hanging where, then. On my system, -2 100% fixed a very reproducible hang after hitting Enter in the password entry. You may be seeing something else that I cannot reproduce. How can we help track this down? Is the problem happening before or after gnome-session is launched? Would it help to trace /etc/gdm/Xsession? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Can't login via GDM anyomre: Re: Fedora 16 updates-testing report
Beware the gigantic gnome 3.1.92 update. Something in this transaction broke the ability for me to log in at all via GDM. You type your password, and hit enter, nothing happens. Click Sign In button, nothing happens. On Wed, Sep 21, 2011 at 10:15:47PM +, upda...@fedoraproject.org wrote: The following Fedora 16 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/glib2-2.29.92-1.fc16,gnome-color-manager-3.1.92-2.fc16,gnome-packagekit-3.1.92-2.fc16,gnome-power-manager-3.1.92-1.fc16,glib-networking-2.29.92-1.fc16,gtk3-3.1.92-1.fc16,libsoup-2.35.92-1.fc16,dconf-0.9.1-1.fc16,gtk-doc-1.18-1.fc16,polkit-gnome-0.103-1.fc16,gnome-desktop3-3.1.92-1.fc16,json-glib-0.14.0-1.fc16,atk-2.1.92-1.fc16,gnome-themes-standard-3.1.92-1.fc16,gnome-menus-3.1.92-1.fc16,libwnck3-3.1.92-1.fc16,libgnome-keyring-3.1.92-1.fc16,libgdata-0.10.1-1.fc16,yelp-xsl-3.1.6-1.fc16,p11-kit-0.6-1.fc16,at-spi2-atk-2.1.92-1.fc16,at-spi2-core-2.1.92-1.fc16,gnome-keyring-3.1.92-1.fc16,gnome-online-accounts-3.1.91-1.fc16,gnome-screensaver-3.1.92-1.fc16,gnome-utils-3.1.92-1.fc16,gucharmap-3.1.92-1.fc16,pyatspi-2.1.91-1.fc16,sushi-0.1.92-2.fc16,aisleriot-3.1.92-1.fc16,file-roller-3.1.92-1.fc16,gnome-settings-daemon-3.1.92-1.fc16,nautilus-3.1.92-1.fc16,gdm-3.1.92-1.fc16,GConf2-3.1.92-1.fc16,seahorse-3.1.92-1.fc16,eog-3.1.92-1.fc16,clutt er-1.8.0-1.fc16,clutter-gtk-1.0.2-4.fc16,cogl-1.8.0-1.fc16,libchamplain-0.12.0-1.fc16,yelp-3.1.4-1.fc16,gnome-session-3.1.92-1.fc16,gnome-documents-0.1.92-2.fc16,vinagre-3.1.92-1.fc16,vino-3.1.92-1.fc16,gnome-panel-3.1.92-1.fc16,orca-3.1.92-1.fc16,clutter-gst-1.3.14-2.fc16,libmx-1.3.1-2.fc16,gnome-games-3.1.92-1.fc16,gnome-applets-3.1.92-1.fc16,rygel-0.12.2-1.fc16,gnome-contacts-0.1.5.2-1.fc16,mutter-3.1.92-1.fc16,cheese-3.1.92-1.fc16,gobject-introspection-1.30.0-1.fc16,control-center-3.1.92-1.fc16,totem-3.1.92-1.fc16,simple-scan-3.1.91-1.fc16,rhythmbox-2.90.1-16.git20110829.fc16,gjs-1.29.18-1.fc16,gnome-user-docs-3.1.1-1.fc16,gnome-shell-3.1.92-1.fc16,caribou-0.3.92-1.fc16 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Can't login via GDM anyomre: Re: Fedora 16 updates-testing report
On Thu, Sep 22, 2011 at 09:39:20AM -0400, Clyde E. Kunkel wrote: On 09/22/2011 09:12 AM, Chuck Anderson wrote: Beware the gigantic gnome 3.1.92 update. Something in this transaction broke the ability for me to log in at all via GDM. You type your password, and hit enter, nothing happens. Click Sign In button, nothing happens. BZ? https://bugzilla.redhat.com/show_bug.cgi?id=740625 Working great here with radeon graphics (RV630). What happens if you revert GDM? I tried reverting a couple things (one at a time) but so far no luck: gdm gnome-session -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Can't login via GDM anyomre: Re: Fedora 16 updates-testing report
On Thu, Sep 22, 2011 at 02:05:20PM -0400, Matthias Clasen wrote: On Thu, 2011-09-22 at 09:12 -0400, Chuck Anderson wrote: Beware the gigantic gnome 3.1.92 update. Something in this transaction broke the ability for me to log in at all via GDM. You type your password, and hit enter, nothing happens. Click Sign In button, nothing happens. You are likely hitting a race in the a11y key event handling at session end (the session being the login screen here). I've been seeing that myself with .92. We're working on it. Latest update to my bug report: Choosing Not listed? and then typing my username/password works. So at least there is a workaround :-) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
gnome network applet not showing multiple wireless networks
I've noticed in Fedora 16 the Gnome network applet sometimes doesn't show the other available wireless networks once you are associated to one. I've also noticed that the wireless on/off switch sometimes doesn't appear. Have other people seen this? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: security update process failure
On Tue, Sep 06, 2011 at 08:57:01AM -0400, Genes MailLists wrote: libcap provides posix capabilities support - fair question would be how to get a list of applications which use libcap stuff it provides. rpm -q -l libcap shows these are provided: /lib64/libcap.so.2 /lib64/libcap.so.2.17 /lib64/security/pam_cap.so /usr/sbin/capsh /usr/sbin/getcap /usr/sbin/getpcaps /usr/sbin/setcap One could troll all binaries on the system asking which ones employ libcap.so.2 using ldd - and perhaps egrep for calls to getcap and the like ... I suspect someone has or has written a tool to catalog these things - anyone? repoquery --whatrequires libcap To verify this update, I just ran the setcap and getcap commands and checked their results. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: security update process failure
On Mon, Sep 05, 2011 at 08:48:07AM +0530, Rahul Sundaram wrote: On 09/05/2011 08:44 AM, Chuck Anderson wrote: So, I guess what I'm asking is, is it ok to give +1 to any/all packages if they work at all/we don't notice any regressions, or do we have to actually test what they are supposed to fix? Thanks. It is ok to +1 if you don't notice any regressions. It would be very helpful to explicitly mention what you tested however. Thanks. I just did a fedora-easy-karma run through most of the F14 critical-path updates and many non-critical ones as well. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: security update process failure
On Sun, Sep 04, 2011 at 05:34:43PM -0700, Adam Williamson wrote: On Sun, 2011-09-04 at 23:01 +0200, Karsten Hopp wrote: Hi ! I'd call it a failure when a security update for a critical path package gets stuck in -updates-testing for 6 weeks. I'm talking about the F14 libcap update, where only one proventester cared to test the updated package and commented on it. Sure, it is only a minor security issue, but shouldn't security updates have priority in testing over any pet packages you have ? Security updates certainly take preference for me as I'm trying to get them submitted as early as possible. But when a package sits in -testing for such a long time I need to ask myself why I should bother with doing timely security updates at all. The problem is really that not enough people test old releases. Barely any proventesters are on F14. If you look it's hardly just your update that's waiting on karma, there are quite a few waiting for F14. I've had 'do f14 karma' on my todo list for about a week and a half, but f16 keeps eating the time. I've mentioned this several times and floated a few ideas to fix it (as have others), but they haven't really gone anywhere. I haven't seen any indication that FESCo (which defined the update requirements - it's not a QA thing) considers it a big problem. I need guidance. I've installed the F14 libcap from updates-testing. I have no idea if it works or how to test it--it doesn't appear to break anything as far as normal operation of my system. Is that good enough to give +1 karma to the package? If not, it would be helpful for the maintainer would put instructions in the update text saying how to test the update. So, I guess what I'm asking is, is it ok to give +1 to any/all packages if they work at all/we don't notice any regressions, or do we have to actually test what they are supposed to fix? Thanks. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: no recent F16 pushes
On Sun, Sep 04, 2011 at 10:57:12PM +, Andre Robatino wrote: Tom Horsley horsley1953 at gmail.com writes: I also note that I still have to use --skip-broken due to a load of stuff involving gnome control panel and evolution-data-server and wot-not. Seems like those problems have been there forever as well. kiilerix on #fedora-qa pointed out that you can work around some of the broken dependencies by disabling the updates-testing repo. By doing this I was able to install some updates from the fedora repo, then doing a regular update managed to pull in a few more from updates-testing. So now for me yum check-update just lists empathy.x86_64 3.1.90.1-1.fc16 updates-testing evolution.x86_643.1.90-1.fc16 updates-testing evolution-NetworkManager.x86_64 3.1.90-1.fc16 updates-testing evolution-data-server.x86_643.1.90-1.fc16 updates-testing evolution-help.noarch 3.1.90-1.fc16 updates-testing gnome-keyring.x86_643.1.90-1.fc16 updates-testing gnome-keyring-pam.x86_643.1.90-1.fc16 updates-testing gnome-shell.x86_64 3.1.90.1-1.fc16 updates-testing seahorse.x86_64 3.1.90-1.fc16 updates-testing I just grabbed the few missing packages directly from koji: folks-0.6.1-2.fc16.x86_64.rpm gnome-panel-3.1.5-5.fc16.x86_64.rpm gnome-panel-libs-3.1.5-5.fc16.x86_64.rpm nautilus-sendto-3.0.0-11.fc16.x86_64.rpm and did: yum update folks-0.6.1-2.fc16.x86_64.rpm gnome-panel-3.1.5-5.fc16.x86_64.rpm gnome-panel-libs-3.1.5-5.fc16.x86_64.rpm nautilus-sendto-3.0.0-11.fc16.x86_64.rpm \* These last few packages will hopfully appear on mirrors soon. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: lldpad consuming up to 65% of cpu
On Fri, Sep 02, 2011 at 02:10:49PM -0700, Adam Williamson wrote: On Fri, 2011-09-02 at 11:06 -0600, Peter Gueckel wrote: Adam Williamson wrote: so if you have anaconda installed, you can probably just remove it, remove fcoe-utils and lldpad, and be happy. I installed from alive CD, so I think that is why anaconda is installed, and hence, with it, as you said, all of the other stuff. I will uninstall as per your advice. Thanks Looks like there's a couple of bugs for this too: https://bugzilla.redhat.com/show_bug.cgi?id=701943 https://bugzilla.redhat.com/show_bug.cgi?id=701999 And: https://bugzilla.redhat.com/show_bug.cgi?id=720080 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
btrfs-progs signed with F-15 GPG key [was F-16 Branched report: 20110831 changes]
On Wed, Aug 31, 2011 at 04:23:32PM +, Branched Report wrote: btrfs-progs-0.19-16.fc15 * Fri Aug 05 2011 Josef Bacik jo...@toxicpanda.com 0.19-16 - fix a typo * Fri Aug 05 2011 Josef Bacik jo...@toxicpanda.com 0.19-15 - actually build btrfs-zero-log * Thu Aug 04 2011 Josef Bacik jo...@toxicpanda.com 0.19-14 - bring btrfs-progs uptodate with upstream Somehow this got built as a F-15 package but ended up in the F-16 Branched repo, signed by the F-15 GPG key which makes yum not happy since it can't find the F-15 key. Is there some reason why F-16 packages aren't being built for this package, and instead you are only building F-15 and F-17 packages? I think F-16 is inheriting the F-15 build and breaking the F-16 repo. Downloading Packages: warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 069c8460: NOKEY Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64 The GPG keys listed for the Fedora 16 - x86_64 repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository. Name: btrfs-progs Version : 0.19 Release : 16.fc15 Architecture: x86_64 Install Date: (not installed) Group : System Environment/Base Size: 1655725 License : GPLv2 Signature : RSA/SHA256, Fri 05 Aug 2011 10:14:55 AM EDT, Key ID b4ebf579069c8460 Source RPM : btrfs-progs-0.19-16.fc15.src.rpm Build Date : Fri 05 Aug 2011 02:12:59 PM EDT Build Host : x86-05.phx2.fedoraproject.org Relocations : (not relocatable) Packager: Fedora Project Vendor : Fedora Project URL : http://btrfs.wiki.kernel.org/index.php/Main_Page Summary : Userspace programs for btrfs Description : The btrfs-progs package provides all the userpsace programs needed to create, check, modify and correct any inconsistencies in the btrfs filesystem. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
which repos should be enabled in F16 Alpha?
It seems the Fedora repo and the Updates Testing repo, but not the Updates repo, are enabled for F16 Alpha. What is strange is that I enabled Updates (and disabled Updates-Testing) and got a bunch of different updates from what is in Updates-Testing (which currently has broken deps). /etc/yum.repos.d/fedora.repo:enabled=1 /etc/yum.repos.d/fedora.repo:enabled=0 /etc/yum.repos.d/fedora.repo:enabled=0 /etc/yum.repos.d/fedora-updates.repo:enabled=0 /etc/yum.repos.d/fedora-updates.repo:enabled=0 /etc/yum.repos.d/fedora-updates.repo:enabled=0 /etc/yum.repos.d/fedora-updates-testing.repo:enabled=1 /etc/yum.repos.d/fedora-updates-testing.repo:enabled=0 /etc/yum.repos.d/fedora-updates-testing.repo:enabled=0 I had to do this to get any Updates-Testing to install at all on x86_64: yum --skip-broken update \*.x86_64 The remaining updates that won't install are: Packages skipped because of dependency problems: 1:control-center-3.1.5-1.fc16.x86_64 from updates-testing 1:control-center-filesystem-3.1.5-1.fc16.x86_64 from updates-testing empathy-3.1.5-1.fc16.x86_64 from updates-testing evolution-3.1.5-1.fc16.x86_64 from updates-testing evolution-NetworkManager-3.1.5-1.fc16.x86_64 from updates-testing evolution-data-server-3.1.5-1.fc16.x86_64 from updates-testing 1:folks-0.6.0-2.fc16.x86_64 from updates-testing gnome-contacts-0.1.2-1.fc16.x86_64 from updates-testing gnome-keyring-3.1.4-1.fc16.x86_64 from updates-testing gnome-keyring-pam-3.1.4-1.fc16.x86_64 from updates-testing gnome-panel-3.1.5-2.fc16.x86_64 from updates-testing libsocialweb-0.25.19-1.fc16.x86_64 from fedora libsocialweb-keys-0.25.19-1.fc16.noarch from fedora 1:nautilus-sendto-3.0.0-7.fc16.x86_64 from updates-testing p11-kit-0.3-2.fc16.x86_64 from fedora Error: Protected multilib versions: gnome-panel-libs-3.1.5-2.fc16.x86_64 != gnome-panel-libs-3.0.2-3.fc16.i686 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 16 Alpha Release Candidate 3 (RC3) Available Now!
On Tue, Aug 09, 2011 at 10:05:54AM -0700, Adam Williamson wrote: On Tue, 2011-08-09 at 12:46 -0400, Andre Robatino wrote: As per the Fedora 16 schedule [1], Fedora 16 Alpha Release Candidate 3 (RC3) is now available for testing. Please see the following pages for download links and testing instructions. In general, official live images arrive a few hours after the install images: see the links below for updates. When they appear, the download directory should be the same as that for install images, except with the trailing /Fedora/ replaced by /Live/. The only difference between RC2 and RC3 is that RC3 includes the libreport update which fixes https://bugzilla.redhat.com/show_bug.cgi?id=692433 - reporting anaconda failures. Given the tight time before go/no-go tomorrow, I suggest we combine RC2 and RC3 test results: for RC3, please focus on testing things that haven't yet been filled in in the RC2 matrices, so between RC2 and RC3 we have all Alpha tests covered. And, of course, re-do the tests which hit 692433 in RC2 - most importantly, QA:Testcase_Anaconda_save_traceback_to_bugzilla . Thanks everyone! I don't see how it can be a go if Live doesn't work without enforcing=0: https://bugzilla.redhat.com/show_bug.cgi?id=728863 I'm surprised RC3 was rushed so quickly with no resoution to this. I expect an RC4 will be necessary. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Heads up: impending IPv6 Test Day
On Thu, Jun 02, 2011 at 04:40:10PM +0100, Richard W.M. Jones wrote: Is there an easy way I can set up IPv6 and a handful of machines on my LAN for testing, without requiring any IPv6 internet connection or an IPv6 assigned prefix? Yes, every system automatically chooses a link-local address. The Linux machines on my LAN appear to have acquired IPv6 addresses, eg: $ ip addr show eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:e0:81:74:02:28 brd ff:ff:ff:ff:ff:ff inet 192.168.0.128/24 brd 192.168.0.255 scope global eth0 inet6 fe80::2e0:81ff:fe74:228/64 scope link valid_lft forever preferred_lft forever fe80:: are link local. The hint is scope link. but pinging them gives me strange errors: $ ping6 fe80::2e0:81ff:fe74:228/64 unknown host $ ping6 fe80::2e0:81ff:fe74:228 connect: Invalid argument $ ping6 fe80::2e0:81ff:fe74 connect: Invalid argument For using link local addresses, you need to specify the outgoing network interface, because the addresses are global to the host, not local to any one interface. Otherwise, it would have no way of knowing which interface to send the packets out of. Also, don't put the /nn, because that is the prefix length (equivalent to the IPv4 subnetwork mask). There are two ways typically to specify outgoing interface for link local: ping6 -I eth0 fe80::2e0:81ff:fe74:228 or: ping6 fe80::2e0:81ff:fe74:228%eth0 Some apps work with one vs. the other. Another tidbit: for IPv6 literals like above, some applications require you to put them in square brackets. For example, web browsers need this syntax: http://[fe80::2e0:81ff:fe74:228%eth0]/ Support for %iface or [] syntax may not be universal, unfortunately. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RFE nm-connection-editor put back into nm-applet
On Fri, Apr 08, 2011 at 10:02:47AM -0500, Brian Millett wrote: With the new NetworkManager, to edit connections, I need to launch nm-connection-editor. It would be nice to have that as an option in the nm-applet (like it used to be) -- Brian Millett - [ Delenn (re: Japanese stone garden), The Gathering] On my world, there are books, thousands of pages, about the power of one mind to change the Universe. But none say it as clearly as this. Right, I noticed on the F15 Live Beta TC1 that I cannot easily connect to WPA2-Enterprise networks. Clicking on the network in the network icon doesn't do anything at all--no attempt to connect, no connection editor dialog pops up, nothing. Also, clicking Network Settings doesn't have any way to edit the WPA2-Enterprise connection either. The Options... button stays greyed out. I had to go to overview mode to launch nm-connection-editor manually just to be able to connect to the wireless network. I think if a network requires more credentials to connect, the Gnome Shell applet should pop up the connection editor, and/or the Options... button on the network control panel should be active and also launch nm-connection-editor. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: since last update system does not boot any more
On Fri, Apr 01, 2011 at 09:44:03PM +0100, mike cloaked wrote: It is also useful to know how to rescue a failed X session after booting and in the middle of a graphical problem once logged in. On the old (current!) days you could switch also to a non-graphical VT and enter telinit 3 to go into runlevel 3 during a normal session or if X broke, and then reenable runlevel 5 by telinit 5. Is there going to remain an equivalent after f15 release - i.e. will switching to say VT 3 using the standard shortcut still be possible - and then I guess login as root and do systemctl stop prefdm.service and then systemctl start prefdm.service to reenable the graphical screen? This is all documented here: http://fedoraproject.org/wiki/Systemd systemctl isolate multi-user.target (or) systemctl isolate runlevel3.target -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 15 Alpha TC2 Available Now!
On Wed, Feb 16, 2011 at 07:32:07AM +0100, Michał Piotrowski wrote: 2011/2/16 Adam Williamson awill...@redhat.com: That is a, ahem, policy decision. What? 8-| What's next? Shutdown option? sarcasm Excellent idea. Who needs to shutdown when you can just suspend/hibernate? /sarcasm Actually though, I highly recommend reading the GNOME 3 Design documents before accusing the GNOME team of not doing their homework. http://gnome3.org/ http://gnome3.org/faq.html http://live.gnome.org/GnomeShell/Design/FAQ http://live.gnome.org/GnomeShell/Design/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 15 Alpha TC2 Available Now!
On Wed, Feb 16, 2011 at 03:45:30PM +, Jóhann B. Guðmundsson wrote: On 02/16/2011 02:26 PM, Chuck Anderson wrote: On Wed, Feb 16, 2011 at 07:32:07AM +0100, Michał Piotrowski wrote: 2011/2/16 Adam Williamsonawill...@redhat.com: That is a, ahem, policy decision. What? 8-| What's next? Shutdown option? sarcasm Excellent idea. Who needs to shutdown when you can just suspend/hibernate? /sarcasm Actually though, I highly recommend reading the GNOME 3 Design documents before accusing the GNOME team of not doing their homework. http://gnome3.org/ http://gnome3.org/faq.html http://live.gnome.org/GnomeShell/Design/FAQ http://live.gnome.org/GnomeShell/Design I think it would be more meaningful to provide links to their actual usability study/research then a links to their design/mockups and FAQ for novice end users. How about this: http://www.gnome.org/~mccann/shell/design/GNOME_Shell-20090705.pdf http://cgwalters.livejournal.com/25818.html -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Gnome busted today?
On Thu, Feb 03, 2011 at 06:01:31PM -0500, Andy Lawrence wrote: On Thu, Feb 3, 2011 at 5:38 PM, Andy Lawrence dr.die...@gmail.com wrote: Updated to today's rawhide, just 10 minutes ago. GDM comes up (without an option to boot into XFCE which worked yesterday), enter my pass the screen just goes black, nothing after. Mouse works/moves, VT switch works. Don't see anything interesting in the logs, any help or suggestions on what to log or how to help ID? Thanks Andy Downgrading to: gdm-2.91.4-6.fc15.x86_64 gdm-plugin-fingerprint-2.91.4-6.fc15.x86_64 Restored proper operation. I will BZ it. Working here fine with 2.91.6-1.fc15.x86_65. I am running with koji updates enabled, though. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: NetworkManager connection priority - a question
On Sat, Jan 08, 2011 at 02:18:19PM -0430, Patrick O'Callaghan wrote: In principle this is about f14 (and all versions prior!) where I have tested this - but I suspect that these issues are also relevant to f15/rawhide unless changes have been made to the NM and/or wpa+supplicant code between f14 release and now - which I expect has not happened. Hence this is likely to be relevant to f15 and to rawhide I expect? Maybe, maybe not. If you aren't testing it, how would you know? If you want to bring up a long-standing issue with NM's functionality, which affects users of current versions as well as (possibly) future ones, the appropriate place would seem to be the Users list. Since the Users list is also more populous than this one, you may also get more response. Or the upstream NetworkManager list: http://mail.gnome.org/mailman/listinfo/networkmanager-list -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Specifying an IPv6 suffix
On Thu, Nov 04, 2010 at 10:22:03AM -0400, Robert Moskowitz wrote: I want to control the IPv6 suffix for my interfaces and let the prefix be set with RA. Currently I can either have the RA prefix with the MAC address for the suffix, or I can specify a complete IPv6 address (and gateway) and ignore RA. The first approach causes problems with DNS if I change the interface. The second approach causes problems if I change the network prefix. Or I could implement DHCPv6, but would still have to change its content if I change the MAC address. And I don't want to ge the DHCPv6 approach anyway. The way I want would be better :) but I don't see that it is supported. My current systems are Centos 5.5 and FC12, so I am stuck, probably with the world as it is, but at least with FC14, it would be nice The best place to bring this up would be with the NetworkManager folks: http://mail.gnome.org/mailman/listinfo/networkmanager-list -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: SOLVED: Re: firefox always starts offline
On Thu, Sep 02, 2010 at 09:12:32AM +0300, cornel panceac wrote: it remains a mistery why this is the first pc where i see this behaviour even if i installed fedora 14 on other computers and everywhere i had to enable network and disable NetworkManager to connect to the network and firefox worked ok. Why did you have to enable network and disable NetworkManager to connect to the network? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
