Re: fedup failure
On 11/07/2014 05:34 PM, Adam Williamson wrote: On Fri, 2014-11-07 at 16:48 -0800, Per Bothner wrote: I wanted to try to updating to what will soon be Fedora 21. I tried using fedup, but failed miserably. Did I use the correct incantation? Well. Not according to the release information, which we've been waving all over the place lately: https://fedoraproject.org/wiki/Common_F21_bugs#no-fedup-beta There was no link here, where I looked https://fedoraproject.org/wiki/FedUp Important Changes in the Upgrade process to Fedora 21 https://fedoraproject.org/wiki/Releases/Rawhide suggests run fedup --network rawhide --nogpgcheck --instrepo http://download.fedoraproject.org/pub/fedora/linux/development/rawhide/$(uname -i)/os/ which I also considered but the initial command seemed to work, in the sense of downloading 2780/2780 packages. Can you get any more of a clue if you pass -v ? Not sure what fixed it, but I did: (1) Removed /var/cache/system-upgrade (2) Removed or disabled various repos in /etc/yum.repos.d Then when I tried: fedup --network 21 -v --product=workstation --debuglog=/var/log/fedupdebug4.log it worked. I'm using Fedora 21/rawhide now. No major problems or regressions so far. A trivial regression was that Gnome Terminal switched to white-on-black, which was easily fixed (unclick Use dark theme variant in Preferences). I'll be trying out Fedora 21 as long as it seems tolerable. Fedora 20 has some annoyances when it came to resuming after suspending or screen timeouts; Ill be curious to see if Fedora 21 does better. So far so good ... Btw before trying fedup I copied over my root partition to a spare partition, so I could have a fall-back. I got that working, after some grub and fstab tweaks, and disabling selinux. It might be useful to have a cookbook for that; however in the short term I ran this copy the Gnome environment died at least once (and I don't know why), so it may not be worthwhile trying to write up what I did. -- --Per Bothner p...@bothner.com http://per.bothner.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup failure
On Sat, 2014-11-08 at 00:13 -0800, Per Bothner wrote: Then when I tried: fedup --network 21 -v --product=workstation --debuglog=/var/log/fedupdebug4.log it worked. I'm using Fedora 21/rawhide now. These are not the same thing. Rawhide is now F22. See https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle and https://fedoraproject.org/wiki/Releases/Branched . The odd thing about your initial attempt is you somehow wound up with Rawhide packages being pulled in, even though I can't see any repo there that would contain them. All I can think is maybe releng fleetingly had the instrepo redirect pointing at Rawhide, and you happened to hit it while that was the case, but even that seems odd. Can you run 'rpm -qa | grep fc22' and verify you have no Fedora 22 packages installed? You should not. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20141108 changes
Compose started at Sat Nov 8 05:15:03 UTC 2014 Broken deps for i386 -- [3Depict] 3Depict-0.0.16-3.fc22.i686 requires libmgl.so.7.2.0 [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [audtty] audtty-0.1.12-9.fc20.i686 requires libaudclient.so.2 [authhub] authhub-0.1.2-3.fc19.i686 requires libjson.so.0 [cab] cab-0.1.9-12.fc22.i686 requires cabal-dev [condor] condor-plumage-8.1.4-7.a1a7df5.fc22.i686 requires libmongoclient.so [deltacloud-core] deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudservers) deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudfiles) [django-recaptcha] django-recaptcha-0.1-7.20091212svn6.fc21.noarch requires python-django14 [dnssec-check] dnssec-check-1.14.0.1-4.fc20.i686 requires libval-threads.so.14 dnssec-check-1.14.0.1-4.fc20.i686 requires libsres.so.14 [dragonegg] dragonegg-3.4-0.3.rc0.fc21.i686 requires libLLVM-3.4.so dragonegg-3.4-0.3.rc0.fc21.i686 requires gcc = 0:4.8.2-14.fc21 [edelib] edelib-2.1-5.fc22.i686 requires libedelib.so edelib-devel-2.1-5.fc22.i686 requires libedelib.so [fatrat] 1:fatrat-1.2.0-0.21.beta2.fc22.i686 requires libtorrent-rasterbar.so.7 [flush] flush-0.9.12-10.fc22.i686 requires libtorrent-rasterbar.so.7 [gdesklet-SlideShow] gdesklet-SlideShow-0.9-16.fc21.noarch requires gdesklets [gdesklets-citation] gdesklets-citation-2.0-3.20120702git355e2ee.fc19.noarch requires gdesklets [gedit-valencia] gedit-valencia-0.4.0-1.20131223git94442bf.fc21.i686 requires libvala-0.24.so.0 [ghc-hjsmin] ghc-hjsmin-0.1.4.7-3.fc22.i686 requires libHSoptparse-applicative-0.9.0-ghc7.6.3.so [glances] glances-2.1.2-2.fc22.noarch requires python-psutil = 0:2.0.0 [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) = 0:0.16.0 [iwhd] iwhd-1.6-11.fc22.i686 requires libmongoclient.so [juffed] juffed-plugin-terminal-0.10-10.fc22.i686 requires libqtermwidget.so.0 [kmid2] kmid2-2.4.0-7.fc22.i686 requires libdrumstick-file.so.0 kmid2-2.4.0-7.fc22.i686 requires libdrumstick-alsa.so.0 [leiningen] leiningen-1.7.1-7.fc20.noarch requires maven-ant-tasks leiningen-1.7.1-7.fc20.noarch requires classworlds [libghemical] libghemical-2.99.1-24.fc20.i686 requires libf77blas.so.3 libghemical-2.99.1-24.fc20.i686 requires libatlas.so.3 [libopensync-plugin-irmc] 1:libopensync-plugin-irmc-0.22-7.fc20.i686 requires libopenobex.so.1 [ltsp] ltsp-client-5.4.5-8.fc21.i686 requires fuse-unionfs ltsp-server-5.4.5-8.fc21.i686 requires cdialog [meshmagick] meshmagick-0.6.0-20.svn2898.fc21.i686 requires libOgreMain.so.1.8.1 meshmagick-libs-0.6.0-20.svn2898.fc21.i686 requires libOgreMain.so.1.8.1 [monodevelop-vala] monodevelop-vala-2.8.8.1-6.fc21.i686 requires vala 0:0.25.0 [netdisco] netdisco-1.1-7.fc21.noarch requires perl(SNMP::Info::Layer2::Bay) [nwchem] nwchem-openmpi-6.3.2-11.fc21.i686 requires libmpi_usempi.so.1 [openshift-origin-msg-node-mcollective] openshift-origin-msg-node-mcollective-1.18.0.1-2.fc21.noarch requires openshift-origin-msg-common [openslides] openslides-1.3.1-3.fc21.noarch requires python-django 0:1.5 [openvas-client] openvas-client-3.0.3-8.fc20.i686 requires libopenvas_omp.so.6 openvas-client-3.0.3-8.fc20.i686 requires libopenvas_nasl.so.6 openvas-client-3.0.3-8.fc20.i686 requires libopenvas_misc.so.6 openvas-client-3.0.3-8.fc20.i686 requires libopenvas_hg.so.6 openvas-client-3.0.3-8.fc20.i686 requires libopenvas_base.so.6 [perl-RT-Authen-ExternalAuth] perl-RT-Authen-ExternalAuth-0.11-5.fc21.noarch requires rt3 perl-RT-Authen-ExternalAuth-0.11-5.fc21.noarch requires perl(:MODULE_COMPAT_5.18.2) [perl-RT-Extension-CommandByMail] perl-RT-Extension-CommandByMail-0.07-10.fc21.noarch requires perl(RT::Interface::Email) perl-RT-Extension-CommandByMail-0.07-10.fc21.noarch requires perl(:MODULE_COMPAT_5.18.2) [pipelight-selinux] pipelight-selinux-0.2.1-2.fc22.noarch requires pipelight-common pipelight-selinux-0.2.1-2.fc22.noarch requires pipelight-common pipelight-selinux-0.2.1-2.fc22.noarch requires pipelight pipelight-selinux-0.2.1-2.fc22.noarch requires pipelight [pootle] pootle-2.1.6-8.fc21.noarch requires python-django14 [python-askbot-fedmsg] python-askbot-fedmsg-0.1.0-2.fc21.noarch requires askbot [python-coffin] python-coffin-0.3.7-3.fc21.noarch requires python-django14 [python-django-addons] python-django-addons-0.6.6-2.fc21.noarch requires python-django14 [python-django-longerusername] python-django-longerusername-0.4-5.20130204gite4e85d7d.fc21.noarch requires python-django14 [python-selenium]
F-21 Branched report: 20141108 changes
Compose started at Sat Nov 8 07:15:03 UTC 2014 Broken deps for armhfp -- [PyQuante] PyQuante-libint-1.6.4-11.fc21.1.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 [audtty] audtty-0.1.12-9.fc20.armv7hl requires libaudclient.so.2 [authhub] authhub-0.1.2-3.fc19.armv7hl requires libjson.so.0 [avro] avro-mapred-1.7.5-9.fc21.noarch requires hadoop-mapreduce avro-mapred-1.7.5-9.fc21.noarch requires hadoop-client [blender] 1:blender-2.72b-1.fc21.armv7hl requires libOpenCOLLADAStreamWriter.so.0.1 1:blender-2.72b-1.fc21.armv7hl requires libOpenCOLLADASaxFrameworkLoader.so.0.1 1:blender-2.72b-1.fc21.armv7hl requires libOpenCOLLADAFramework.so.0.1 1:blender-2.72b-1.fc21.armv7hl requires libOpenCOLLADABaseUtils.so.0.1 1:blender-2.72b-1.fc21.armv7hl requires libMathMLSolver.so.0.1 1:blender-2.72b-1.fc21.armv7hl requires libGeneratedSaxParser.so.0.1 1:blenderplayer-2.72b-1.fc21.armv7hl requires libOpenCOLLADAStreamWriter.so.0.1 1:blenderplayer-2.72b-1.fc21.armv7hl requires libOpenCOLLADASaxFrameworkLoader.so.0.1 1:blenderplayer-2.72b-1.fc21.armv7hl requires libOpenCOLLADAFramework.so.0.1 1:blenderplayer-2.72b-1.fc21.armv7hl requires libOpenCOLLADABaseUtils.so.0.1 1:blenderplayer-2.72b-1.fc21.armv7hl requires libMathMLSolver.so.0.1 1:blenderplayer-2.72b-1.fc21.armv7hl requires libGeneratedSaxParser.so.0.1 [cduce] cduce-0.5.5-9.fc21.armv7hl requires ocaml(Camlp4) = 0:ebd368022fd2bc7b305a42902efa4c90 [deltacloud-core] deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudservers) deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudfiles) [django-recaptcha] django-recaptcha-0.1-7.20091212svn6.fc21.noarch requires python-django14 [dragonegg] dragonegg-3.4-0.3.rc0.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 [edelib] edelib-2.1-5.fc21.armv7hl requires libedelib.so edelib-devel-2.1-5.fc21.armv7hl requires libedelib.so [fatrat] 1:fatrat-1.2.0-0.21.beta2.fc21.armv7hl requires libtorrent-rasterbar.so.7 [flush] flush-0.9.12-10.fc21.armv7hl requires libtorrent-rasterbar.so.7 [gdesklet-SlideShow] gdesklet-SlideShow-0.9-16.fc21.noarch requires gdesklets [gdesklets-citation] gdesklets-citation-2.0-3.20120702git355e2ee.fc19.noarch requires gdesklets [gedit-valencia] gedit-valencia-0.4.0-1.20131223git94442bf.fc21.armv7hl requires libvala-0.24.so.0 [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) = 0:0.16.0 [golang-github-influxdb-influxdb] golang-github-influxdb-influxdb-datastore-0.8.0-0.3.rc4.git67f9869.fc21.noarch requires golang(github.com/jmhodges/levigo) golang-github-influxdb-influxdb-datastore-0.8.0-0.3.rc4.git67f9869.fc21.noarch requires golang(code.google.com/p/log4go) golang-github-influxdb-influxdb-devel-0.8.0-0.3.rc4.git67f9869.fc21.noarch requires golang(github.com/jmhodges/levigo) golang-github-influxdb-influxdb-devel-0.8.0-0.3.rc4.git67f9869.fc21.noarch requires golang(github.com/influxdb/go-cache) golang-github-influxdb-influxdb-devel-0.8.0-0.3.rc4.git67f9869.fc21.noarch requires golang(github.com/bmizerany/pat) golang-github-influxdb-influxdb-devel-0.8.0-0.3.rc4.git67f9869.fc21.noarch requires golang(code.google.com/p/log4go) [gorm] gorm-1.2.18-5.fc20.armv7hl requires libgnustep-gui.so.0.23 [leiningen] leiningen-1.7.1-7.fc20.noarch requires maven-ant-tasks leiningen-1.7.1-7.fc20.noarch requires classworlds [libghemical] libghemical-2.99.1-24.fc20.armv7hl requires libf77blas.so.3 libghemical-2.99.1-24.fc20.armv7hl requires libatlas.so.3 [libopensync-plugin-irmc] 1:libopensync-plugin-irmc-0.22-7.fc20.armv7hl requires libopenobex.so.1 [ltsp] ltsp-client-5.4.5-8.fc21.armv7hl requires fuse-unionfs ltsp-server-5.4.5-8.fc21.armv7hl requires cdialog [meshmagick] meshmagick-0.6.0-20.svn2898.fc21.armv7hl requires libOgreMain.so.1.8.1 meshmagick-libs-0.6.0-20.svn2898.fc21.armv7hl requires libOgreMain.so.1.8.1 [monodevelop-vala] monodevelop-vala-2.8.8.1-6.fc21.armv7hl requires vala 0:0.25.0 [netdisco] netdisco-1.1-7.fc21.noarch requires perl(SNMP::Info::Layer2::Bay) [ocaml-pa-do] ocaml-pa-do-0.8.16-3.fc21.armv7hl requires ocaml(Camlp4) = 0:ebd368022fd2bc7b305a42902efa4c90 [openslides] openslides-1.3.1-3.fc21.noarch requires python-django 0:1.5 [openstack-nova] openstack-nova-compute-2014.1.2-1.fc21.noarch requires libvirt-daemon-xen [openvas-client] openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_omp.so.6 openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_nasl.so.6 openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_misc.so.6
Re: Linux multi-boot release criterion discussion, redux
On 11/07/2014 04:24 PM, Peter Jones wrote: On Fri, Nov 07, 2014 at 11:34:16AM -0800, Adam Williamson wrote: More criteria time, folks! So we managed to get the Windows multi-boot criterion revised and an OS X multi-boot criterion added, but we did not yet manage to come to a consensus on exactly what should be required for Linux multi-boot. I think Chris will re-propose his last idea and we can discuss it a bit more, but I'd like to suggest a more restricted criterion we can hopefully agree on immediately for the short term: === When installing to a system containing an existing installation of either the same Fedora release or either of the two previous releases, the installer must configure the new installation's bootloader such that it can successfully boot the existing installation. [Footnote] Typical configurations only: This criterion applies only to installations (both existing and new) using default or very common storage and bootloader configurations. [Footnote] Platforms: This criterion applies to all supported configurations described in [[Fedora_21_Alpha_Release_Criteria#Release-blocking_images_must_boot|the Alpha criteria]], but does not apply to mixed configurations, e.g. it does not require that a UEFI native installation of one Fedora release be able to configure its bootloader to boot a BIOS native installation of another Fedora release. === How does that look? I think we had at least a consensus that this much was reasonable, and we have two bugs currently that would likely violate the proposed criterion: https://bugzilla.redhat.com/show_bug.cgi?id=825236 https://bugzilla.redhat.com/show_bug.cgi?id=964828 I think it's reasonable to consider these blockers for F21, but we should justify it ASAP to give the devs sufficient time to fix them. I'm all for getting those bugs fixed, but making it an official criterion is basically adding an anaconda requirement and a new feature to the distro. Doing that at the end of a cycle isn't really okay, and doing it without any mention on anaconda-devel-list or fedora-devel-list for discussion isn't really that great, either. Also this criterion as written is going to bring in more than just those two bugs - for example, right now we don't /really/ support two UEFI Fedora installations on a single disk without the user making some fairly strange choices, and when you do that, some things such as fallback (which admittedly aren't in the criteria AFAIK) don't work. Fixing that would be a fairly substantial RFE, so either we need to have language in any potential new criterion to accept the current conditions (e.g. by requiring two separate disks to put an ESP on each), or we need to plan on adding support for that before we apply any new criteria. Before discussion any criteria for whatever release, perhaps there should be a discussion on how we would like things to work and what we really do not care about. Also, I believe that the appropriate place for this discussion is the anaconda-devel list and/or de...@lists.fedoraproject.org [or, perhaps both]. Also, is this just a grub2 issue or does it also apply to extlinux? Also, I would like to see the merits of directly booting other installations (linux/initrd) versus configfile chaining. Another point that would clarify things for me concerns linux16/initrd16. Other than it is the latest and greatest, just what features/capabilities does linux/initrd (32 bit) offer that is not available in linux16/initrd16? Once we know what goal we are aimed at and what we are ignoring, then we can establish some bounds and release criteria. And yes, it is far too late for Fedora 21 and will be too late for Fedora 22 if the discussion and decisions are not done soon. As Peter points out, some RFE things will involve a substantial amount of code and therefore need lots of lead time. Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: One Desktop and one Desktop ONLY.
On 11/05/2014 09:21 PM, Rahul Sundaram wrote: Hi On Wed, Nov 5, 2014 at 5:26 PM, Ed Greshko wrote: Sorry to start yet another thread on the same issue But I only just now discover that once you install Fedora Workstation you can't install another desktop Try, # yum swap fedora-release-workstation fedora-release-nonproduct # yum install @lxde-desktop I notice that dnf does not have swap. Is this intentional? Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: One Desktop and one Desktop ONLY.
On Sat, 2014-11-08 at 09:05 -0500, Gene Czarcinski wrote: I notice that dnf does not have swap. Is this intentional? Try: 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: One Desktop and one Desktop ONLY.
On Sat, 2014-11-08 at 14:46 +, Ankur Sinha wrote: On Sat, 2014-11-08 at 09:05 -0500, Gene Czarcinski wrote: I notice that dnf does not have swap. Is this intentional? Try: Gah, sent it early: http://dnf.readthedocs.org/en/latest/cli_vs_yum.html#packages-replacement-without-yum-shell-or-yum-swap as Tim pointed out already. :) -- Thanks, Regards, Ankur Sinha FranciscoD http://fedoraproject.org/wiki/User:Ankursinha 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: Linux multi-boot release criterion discussion, redux
On Sat, 2014-11-08 at 08:45 -0500, Gene Czarcinski wrote: Before discussion any criteria for whatever release, perhaps there should be a discussion on how we would like things to work and what we really do not care about. Also, I believe that the appropriate place for this discussion is the anaconda-devel list and/or de...@lists.fedoraproject.org [or, perhaps both]. We already did that, extensively. What I'm trying to do is propose a fairly minimum criterion that would be a *baseline* everyone can agree on, so we can at least get something added. As I wrote, I think cmurf is planning to re-propose his more extensive idea. I sent the proposal to a-d-l as well, but test@ is the 'official' place for criterion discussions. Also, is this just a grub2 issue or does it also apply to extlinux? My proposal does not. Also, I would like to see the merits of directly booting other installations (linux/initrd) versus configfile chaining. Release criteria are about functionality, not about implementation. That's an entirely separate discussion, which *would* make sense on a-d-l. Another point that would clarify things for me concerns linux16/initrd16. Other than it is the latest and greatest, just what features/capabilities does linux/initrd (32 bit) offer that is not available in linux16/initrd16? Again irrelevant to a criterion discussion. Once we know what goal we are aimed at and what we are ignoring, then we can establish some bounds and release criteria. I guess I don't quite see it that way. What goal we're aimed at is exactly what a criterion *is*: a functional requirement. What you're talking about above is not about 'goals', it's about technical/implementation details. These can have some impact on criteria - it's obviously absurd to write a requirement that is not technically achievable - but in general I don't see that we need to get into the nitty gritty of grub's alternative loader implementations in order to decide whether we want to set a release criterion for basic stock configuration multi-boot. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: One Desktop and one Desktop ONLY.
Hi On Sat, Nov 8, 2014 at 9:05 AM, Gene Czarcinski wrote: I notice that dnf does not have swap. Is this intentional? Yes https://bugzilla.redhat.com/show_bug.cgi?id=1110780 Rahul -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup failure
On 11/08/2014 12:46 AM, Adam Williamson wrote: Can you run 'rpm -qa | grep fc22' and verify you have no Fedora 22 packages installed? You should not. Thanks! Just one: $ sudo rpm -qa | grep fc22 shim-unsigned-0.8-1.fc22.x86_64 I'm afraid I don't know what that is. -- --Per Bothner p...@bothner.com http://per.bothner.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup failure
On Sat, 2014-11-08 at 10:06 -0800, Per Bothner wrote: On 11/08/2014 12:46 AM, Adam Williamson wrote: Can you run 'rpm -qa | grep fc22' and verify you have no Fedora 22 packages installed? You should not. Thanks! Just one: $ sudo rpm -qa | grep fc22 shim-unsigned-0.8-1.fc22.x86_64 I'm afraid I don't know what that is. Ah, that's actually fine. As a special case, the fc22 build of shim was sent to all supported releases as it cuts down on the Secure Boot signing/verification work - we don't have to verify four actually-the-same builds of shim. So, looks fine. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup failure
On 11/08/2014 11:14 AM, Adam Williamson wrote: Ah, that's actually fine. As a special case, the fc22 build of shim was sent to all supported releases as it cuts down on the Secure Boot signing/verification work - we don't have to verify four actually-the-same builds of shim. So, looks fine. Thanks for your help. So far looking good. A couple of minor but annoying bugs are still there (i.e. not regressions): (1) The default (Gnome) sound output device switches back to Speakers - Built-in Audio from HDMI / DisplayPort 2 - Built-in Audio each time the screensaver kicks in. (2) Some NetworkManager problems when the Ethernet cable is plugged in, leading me to just use WiFi even though I have a nice cable right there. (3) The Gnome Displays configuration applet works right after rebooting, but has problems disabling the external monitor or switching primary/secondary after suspend or screensaving. I'll check out KDE next time I reboot - on F20 it also had problems (only showing the upper-left quadrant of the 4k display after timeout-caused screen lock requiring unplugging and plugging back inthe HDMI cable). These could all be suspend or screensaver issues specific to my laptop (Toshiba Satellite P-50A with a connected Seiki 4k 50 display). I need to figure out where to report these bugs after I've used F21 a bit more. -- --Per Bothner p...@bothner.com http://per.bothner.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Resume still broken on Thinkpad X1 Carbon
On Tue, 4 Nov 2014 09:17:25 -0500 Jonathan Corbet corbet...@lwn.net wrote: I'm pretty well mystified, but, given my general lack of skills in this part of the system, that's not surprising. My next step, perhaps, is to start disabling boot-time unit files until I find the one that makes resume work, then try to see what's different under F21. Just in case anybody's curious, systemd-udev-trigger.service seems to be the one that makes the difference on F20. Something is happening there that isn't happening the same way under F21, but I've not had a chance to delve more deeply into it. My investigation would be aided if I could get into the emergency or rescue targets from the live image. But that wants the root password, and an empty password doesn't fly. Is there any way to boot the live image into one of those modes, or is that completely unsupported and out of scope? Thanks, jon -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Resume still broken on Thinkpad X1 Carbon
On Sat, 2014-11-08 at 16:50 -0500, Jonathan Corbet wrote: On Tue, 4 Nov 2014 09:17:25 -0500 Jonathan Corbet corbet...@lwn.net wrote: I'm pretty well mystified, but, given my general lack of skills in this part of the system, that's not surprising. My next step, perhaps, is to start disabling boot-time unit files until I find the one that makes resume work, then try to see what's different under F21. Just in case anybody's curious, systemd-udev-trigger.service seems to be the one that makes the difference on F20. Something is happening there that isn't happening the same way under F21, but I've not had a chance to delve more deeply into it. My investigation would be aided if I could get into the emergency or rescue targets from the live image. But that wants the root password, and an empty password doesn't fly. Is there any way to boot the live image into one of those modes, or is that completely unsupported and out of scope? One thing I've done before is build a live image with the systemd debug console enabled. To do that, add this to the %post of a ks: %post mkdir -p /etc/systemd/system/sysinit.target.wants ln -s /usr/lib/systemd/system/debug-shell.service /etc/systemd/system/sysinit.target.wants %end Here's the whole .ks I used: %include spin-kickstarts/fedora-live-workstation.ks repo --name=fedora --baseurl=http://dl.fedoraproject.org/pub/fedora/linux/development/$releasever/$basearch/os/ repo --name=side --baseurl=file:///home/adamw/local/repo2/$basearch repo --name=bleed --baseurl=http://kojipkgs.fedoraproject.org/mash/bleed/$basearch %post mkdir -p /etc/systemd/system/sysinit.target.wants ln -s /usr/lib/systemd/system/debug-shell.service /etc/systemd/system/sysinit.target.wants %end obviously, you'd have a checkout of the f21 branch of spin-kickstarts in the directory 'spin-kickstarts' below wherever that spec file is located, and you'd have your own side repo or just disable it. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F21 Installation Issues - Installation destination partitioning
I am trying to install F21 on my system. Unfortunately I am running in to some of issues. First issue is that I can not run the regular installer from the LiveUSB I created (this is likely to be due to my GeForce GTX 750TI graphics being not completely supported yet. Running the installer in low graphics mode seems work ok). The second issue is to do with create device partitions for the installation. Performing automatic partitioning will fail. The installer seems unable to detect the ~2TB of unallocated/free space on my hard drive. The installer will return to the main window and the Installation Destination button with first have some yellow/orange text saying Failed to save storage configuration, which will then turn to red text saying Error checking storage configuration. Performing manual partitioning will fail on two counts. First: Clicking the link that says Click here to create them automatically. fails A red box will appear at the bottom of the screen saying Automatic partitioning failed. Click for details.. Clicking there brings up a dialog will saying You have not defined a root partition (/), which is required for installation of Fedora to continue. No valid bootloader target device found. See below for details. For a UEFI installation, you must include an EFI System Partition on a GPT-formatted disk, mounted at /boot/efi.. Second: Creating manual partitions (specifying /, /boot, /home, and swap manually) I am able to add 1 of those 4 partitions (to be whatever size I desire), but trying to add a second partitions constantly fails despite having copious amounts of hard drive space available. A red box will appear at the bottom of the screen saying Failed to add new device. Click for details.. Clicking there brings up a dialog saying requested size exceeds maximum allowed. Some system specifications: Processor: Intel Core i7 4820K Motherboard: ASUS P9X79-LE (UEFI) Chipset: Intel X79 Memory: 64GB DDR3 HDD: 4TB Western Digital Caviar Green SATA 6GB/s (Windows 7 64-bit is installed in one half of this hard drive with a GPT partition table). Graphics: Gigabyte GeForce GTX 750TI Fedora 21 64-bit ISO was downloaded (via torrent) on 8th November and burnt on to a 8GB USB flash drive with 4GB of persistant storage. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F21 Installation Issues - Installation destination partitioning
On Sun, 2014-11-09 at 11:28 +1100, Bidski wrote: HDD: 4TB Western Digital Caviar Green SATA 6GB/s (Windows 7 64-bit is installed in one half of this hard drive with a GPT partition table). Well, the errors you're getting seem rather odd. Are you sure it *actually* has a GPT partition table? Can you post /tmp/storage.log , /tmp/program.log , and the output of 'fdisk' or 'parted' or something on the disk? Thanks. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F21 Installation Issues - Installation destination partitioning
My apologies. Apparently when you ask Windows to create a GPT it decides that what you really wanted was an MBR. I shall work on rectifying this now. I shall let you know the result. - Original Message - From: Bidski To:Adam Williamson Cc: Sent:Sun, 09 Nov 2014 13:52:21 +1100 Subject:Re: F21 Installation Issues - Installation destination partitioning My apologies. Apparently when you ask Windows to create a GPT it decides that what you really wanted was an MBR. I shall work on rectifying this now. I shall let you know the result. - Original Message - From: Adam Williamson To:Bidski , For testing and quality assurance of Fedora releases Cc: Sent:Sat, 08 Nov 2014 16:52:00 -0800 Subject:Re: F21 Installation Issues - Installation destination partitioning On Sun, 2014-11-09 at 11:28 +1100, Bidski wrote: HDD: 4TB Western Digital Caviar Green SATA 6GB/s (Windows 7 64-bit is installed in one half of this hard drive with a GPT partition table). Well, the errors you're getting seem rather odd. Are you sure it *actually* has a GPT partition table? Can you post /tmp/storage.log , /tmp/program.log , and the output of 'fdisk' or 'parted' or something on the disk? Thanks. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
