f20 beta tc1, live desktop, text install?
Is text install expected to work for live media? If not, disregard. If yes, the problem I'm having is installation source errors when set to CD/DVD, making it not possible to install without resorting to network as a source. See screenshot, item 6 is presumably hung up due to 1. https://dl.dropboxusercontent.com/u/3253801/anacondatextinstall1.png Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20 Beta TC1 strange naming
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 03 Oct 2013 10:47:35 -0400 Gene Czarcinski wrote: > Shouldn't the Fedora ISOs be named: > Fedora-20-Beta-TC1-x86_64-DVD.iso > rather than: > Fedora-20-Beta-x86_64-DVD.iso > > I notice that the spin and live ISOs are all named "Beta-TC1" rather > than just "Beta" > > Yes, I know, a nit. > > Gene > > Its a side effect of redoing the compose processes, i need to fix it so it has -TC2 etc Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.21 (GNU/Linux) iEYEARECAAYFAlJNl6sACgkQkSxm47BaWfdGYwCgjPXTJg8txiD2rQ7SV/47R8m1 SEEAn0C9dWav6wbzBxPhgmuRl77Ed9HZ =q+7V -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] Fedora 20 Virt Test Day is October 8th!
Hey all, The Fedora 20 Virt Test Day is this coming Tuesday, October 8th. Check out the test day landing page: https://fedoraproject.org/wiki/Test_Day:2013-10-08_Virtualization If you're interested in trying out some new virt functionality, there's step by step instructions for: * Snapshot UI in virt-manager * Running ARM VMs on x86 with libvirt/virt-manager * Libvirt ACLs for granting a user access to only a single VM Even if you aren't interested in testing new features, we still need you! The test day is the perfect time to make sure your virt workflow is working fine on Fedora 20, as there will be several developers on hand to answer any questions, help with debugging, provide patches, etc. No requirement to run through test cases on the wiki, just show up and let us know what works (or breaks). If you can't make the date of the test day, adding test case results to the wiki anytime next week is fine as well. Though if you do plan on showing up to the test day, add your name to the participant list on the wiki, and when the day arrives, pop into #fedora-test-day on freenode and give us a shout! Thanks, Cole ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Heisenbug: Xfce vs MATE
I have been running Heisenbug on omen.com since about Sep. 22. Omen.com and my office machine are running 3.11.3-301.fc20.x86_64. I have been running the MATE desktop as well as Xfce. (BTW MATE is pronounced "mah-teigh".) Xfce has the annoying habit of moving apps between panes. For example, I normally have Thunderbird in the leftmost panes, Firefox in the next, and Pan newsreader in the third. If I click on a URL from Thunderbird or Pan Xfce moves Firefox on top of the other pane. When finished looking at the web site I have to move Firefox back to its pane. I have not figured out how to disable this most annoying feature. On the other hand, MATE does not gnerate a wine group in the applications menu the way Xfce does. My work around is to create the desktop icon in Xfce, which then appears in MATE. Heisenbug has been running smoothly on omen.com once I got it installed. On my office machine networking has died a few times in the last week or so. -- Chuck Forsberg WA7KGX 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: Gnome 3.10: Network UI missing from new system status area
On Oct 3, 2013, at 11:48 PM, John Morris wrote: > On Thu, 2013-10-03 at 20:59 +0200, drago01 wrote: >> You should get an icon indicating failure just no success one. Which >> is even very unixy ;) > > Well GNU is Not Unix and these days Fedora isn't even following that > star. How does Apple do it? OS X does not have a wired network icon for the persistent menu bar at all. Not by default or as an option. User needs to go to the Network panel to see the state which is one of three: not connected (red), connected but no IP (yellow), connect with IP (green). OS X does have a wireless network icon on the menu bar. It can optionally be removed. It's completely gray when there is no connection, otherwise it indicates signal strength. An X is never used to indicate state. If the signal weakens or vanishes, the menu bar icon simply goes gray. No dialog, no text. A dialog appears with a connection failure only when actively connecting to a discrete access point and the connection attempt fails (wrong login or password, or error establishing connection). > > Screen space is valuable so removing an icon that is 'always' there and > isn't typically displaying useful information is sensible enough. But > as the bug commenters noted, some people DO move between wired > connections and such so an option to put it back really needs a bit of > thought. A wired state icon in the menu bar is not needed if it's available upon making a physical connection, by default, for all users. For Gnome 3.8, I regularly encountered no network connection upon successful install, despite a working wire in the singular ethernet port, because by default "Connect Automatically" is not enabled for wired connections. So if I have to give the system A Captain Obvious Clue, yes I really do need an otherwise useless wired network state icon in the menubar. But better would be no wired network icon, but any user by default has access to the network connection automatically if the wired is in the port. (As a Mac user the idea that a network isn't connected to automatically by default upon physical access to both computer and wire is not merely surprising, it is considered broken.) Chris Murphy -- 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 04.10.2013 16:38, Matthew Miller wrote: On Fri, Oct 04, 2013 at 07:54:54AM +0200, moshe nahmias wrote: I think that it must be possible to make the icon visible as an option. I This seems like a very useful place for a Gnome Shell Extension. Or rather a gsettings option accessible via tweak tool. Having extensions for every small detail is a bit excessive IMO. -- 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 07:54:54AM +0200, moshe nahmias wrote: > I think that it must be possible to make the icon visible as an option. I This seems like a very useful place for a Gnome Shell Extension. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ -- 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 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
Re: Gnome 3.10: Network UI missing from new system status area
On Fri, Oct 4, 2013 at 3:05 PM, Chuck Anderson 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. -- 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: First impressions with F20-Beta
On Fri, Oct 4, 2013 at 2:52 PM, Adam Williamson wrote: > On Fri, 2013-10-04 at 00:47 +0200, drago01 wrote: >> >> >> On Thursday, October 3, 2013, Chuck Forsberg WA7KGX >> wrote: >> > TC1 netinst installation, booting, and initial operation nominal >> > on a hardware E6550. Gnuradio compiled in normal time and >> > passed all but one self test (the usual). >> > >> > The TC1 USB stick netinst UEFI booted on an Asus P8z77v LE Plus was >> > unable to modify the hard drive partitions. >> > >> > Is UEFI boot a requirement for Heisenbug? >> >> No. > > I think you misread Chuck's mail (I did at first). Just to be sure, here > are answers to both of the possible questions: > > 1. Do you have to be using UEFI to install Fedora 20? > Answer: No. Yeah that's the question I answered. -- 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, 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. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin DOT net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: First impressions with F20-Beta
On Fri, 2013-10-04 at 00:47 +0200, drago01 wrote: > > > On Thursday, October 3, 2013, Chuck Forsberg WA7KGX > wrote: > > TC1 netinst installation, booting, and initial operation nominal > > on a hardware E6550. Gnuradio compiled in normal time and > > passed all but one self test (the usual). > > > > The TC1 USB stick netinst UEFI booted on an Asus P8z77v LE Plus was > > unable to modify the hard drive partitions. > > > > Is UEFI boot a requirement for Heisenbug? > > No. I think you misread Chuck's mail (I did at first). Just to be sure, here are answers to both of the possible questions: 1. Do you have to be using UEFI to install Fedora 20? Answer: No. 2. Is it a QA requirement that a normal UEFI install of Fedora 20 work? Answer: Yes. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin DOT net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-20 Branched report: 20131004 changes
Compose started at Fri Oct 4 09:15:02 UTC 2013 Broken deps for armhfp -- [blueman] blueman-1.23-7.fc20.armv7hl requires obex-data-server >= 0:0.4.3 blueman-1.23-7.fc20.armv7hl requires gvfs-obexftp [bwm-ng] bwm-ng-0.6-11.1.fc20.armv7hl requires libstatgrab.so.9 [cloud-init] cloud-init-0.7.2-4.fc20.noarch requires dmidecode [cobbler] cobbler-2.4.0-2.fc20.noarch requires syslinux [fawkes] fawkes-doc-0.5.0-9.fc20.noarch requires fawkes = 0:0.5.0-9.fc20 [fts] fts-server-3.1.1-1.fc20.armv7hl requires libactivemq-cpp.so.14 [glusterfs] glusterfs-ufo-3.4.0-8.fc20.noarch requires openstack-swift-proxy = 0:1.8.0 glusterfs-ufo-3.4.0-8.fc20.noarch requires openstack-swift-object = 0:1.8.0 glusterfs-ufo-3.4.0-8.fc20.noarch requires openstack-swift-container = 0:1.8.0 glusterfs-ufo-3.4.0-8.fc20.noarch requires openstack-swift-account = 0:1.8.0 glusterfs-ufo-3.4.0-8.fc20.noarch requires openstack-swift = 0:1.8.0 [gnome-do-plugins] gnome-do-plugins-thunderbird-0.8.4-14.fc20.armv7hl requires thunderbird [gofer] ruby-gofer-0.75-4.fc20.noarch requires rubygem(qpid) >= 0:0.16.0 [gradle] gradle-1.0-18.fc20.noarch requires plexus-container-default [grass] grass-6.4.2-11.fc20.armv7hl requires libgeos-3.3.8.so grass-libs-6.4.2-11.fc20.armv7hl requires libgeos-3.3.8.so [gtkd] gtkd-geany-tags-2.0.0-29.20120815git9ae9181.fc18.noarch requires gtkd = 0:2.0.0-29.20120815git9ae9181.fc18 [kawa] 1:kawa-1.11-5.fc19.armv7hl requires servlet25 [koji] koji-vm-1.8.0-2.fc20.noarch requires python-virtinst [kyua-cli] kyua-cli-0.5-3.fc19.armv7hl requires liblutok.so.0 kyua-cli-tests-0.5-3.fc19.armv7hl requires liblutok.so.0 [monotone] monotone-1.0-11.fc19.armv7hl requires libbotan-1.8.2.so perl-Monotone-1.0-11.fc19.armv7hl requires perl(:MODULE_COMPAT_5.16.2) [mozilla-firetray] mozilla-firetray-thunderbird-0.3.6-0.5.143svn.fc18.1.armv7hl requires thunderbird >= 0:11 [msp430-libc] msp430-libc-20120224-2.fc19.noarch requires msp430-gcc >= 0:4.6.3 [nifti2dicom] nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtksys.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkWidgets.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkVolumeRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkViews.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkTextAnalysis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkParallel.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkInfovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkImaging.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkIO.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkHybrid.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGraphics.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGeovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGenericFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCommon.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCharts.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libQVTK.so.5.10 [nocpulse-common] nocpulse-common-2.2.7-2.fc20.noarch requires perl(RHN::DBI) [openbox] gdm-control-3.5.2-2.fc20.armv7hl requires gnome-panel gnome-panel-control-3.5.2-2.fc20.armv7hl requires gnome-panel [openpts] openpts-0.2.6-7.fc20.armv7hl requires tboot [osm2pgsql] osm2pgsql-0.82.0-1.fc20.armv7hl requires libgeos-3.3.8.so [ovirt-engine] ovirt-engine-notification-service-3.1.0-1.fc19.noarch requires classpathx-mail [oyranos] oyranos-libs-0.4.0-7.fc19.armv7hl requires libraw.so.5 [perl-Language-Expr] perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) [perl-MIME-Lite-HTML] perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) [perl-MooseX-TrackDirty-Attributes] perl-MooseX-TrackDirty-Attributes-2.002-2.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) [perl-Padre] perl-Padre-0.90-6.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0) [player] player-3.0.2-32.fc20.armv7hl requires libstatgrab.so.9 player-3.0.2-32.fc20.armv7hl requires libgeos-3.3.8.so [pure] pure-doc-0.57-4.fc20.noarch requires pure = 0:0.57-4.fc20 [python-basemap] python-basemap-1.0.6-4.fc20.armv7hl requires libgeos-3.3.8.so [python-tag] python-tag-2013.1-1.fc20.armv7hl requires libboost_python.so.1.53.0 [rootplot] rootplot-2.2.1-7.fc19.noarch requires root-python [rubygem-audited-activerecord]
Re: Gnome 3.10: Network UI missing from new system status area
On 04.10.2013 07:54, 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. Also when ohne has multiple wired-networking profiles configured, you have to go to the system settings in order to switch between them. I think users would expect to be able to do that from the system status area. And my opinion: I find this to be unnecessarily confusing. The system status area should show in what state the computer/device is, and in my opinion the ethernet cable status should definitely be part of the state (unless the device has no LAN adapter). Sandro -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
