F-21 Branched report: 20141006 changes
Compose started at Mon Oct 6 07:15:02 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 [cduce] cduce-0.5.5-9.fc21.armv7hl requires ocaml(Camlp4) = 0:ebd368022fd2bc7b305a42902efa4c90 [cp2k] cp2k-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 cp2k-mpich-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 cp2k-openmpi-2.5.1-8.fc21.armv7hl requires libmpi_usempi.so.1 cp2k-openmpi-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 [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 [elpa] elpa-openmpi-2013.11-4.008.fc21.armv7hl requires libmpi_usempi.so.1 [eucalyptus] eucalyptus-common-java-3.3.0-0.5.20130408git32052445.fc20.armv7hl requires hibernate3-jbosscache = 0:3.6.10-7 [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 [freesteam] freesteam-ascend-2.1-6.20140724svn753.fc21.armv7hl requires libascend.so.1 [gcc-python-plugin] gcc-python2-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 gcc-python2-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires libpython3.3dm.so.1.0 gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 gcc-python3-plugin-0.12-18.fc21.armv7hl requires libpython3.3m.so.1.0 gcc-python3-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 [gdb-heap] gdb-heap-0.5-18.fc21.armv7hl requires glibc(armv7hl-32) = 0:2.19.90 [gedit-valencia] gedit-valencia-0.4.0-1.20131223git94442bf.fc21.armv7hl requires libvala-0.24.so.0 [gnome-python2-desktop] gnome-python2-metacity-2.32.0-18.fc21.armv7hl requires libmetacity-private.so.0 [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) = 0:0.16.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.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 openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_hg.so.6 openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_base.so.6 [perl-RT-Authen-ExternalAuth] perl-RT-Authen-ExternalAuth-0.11-5.fc21.noarch requires rt3 [perl-RT-Extension-CommandByMail] perl-RT-Extension-CommandByMail-0.07-10.fc21.noarch requires perl(RT::Interface::Email) [pipelight-selinux] pipelight-selinux-0.2.1-2.fc21.noarch requires pipelight-common pipelight-selinux-0.2.1-2.fc21.noarch requires pipelight-common pipelight-selinux-0.2.1-2.fc21.noarch requires pipelight pipelight-selinux-0.2.1-2.fc21.noarch requires pipelight [pootle] pootle-2.1.6-8.fc21.noarch requires python-django14
rawhide report: 20141006 changes
Compose started at Mon Oct 6 05:15:04 UTC 2014 Broken deps for i386 -- [Agda] ghc-Agda-2.3.2.2-5.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so ghc-Agda-2.3.2.2-5.fc22.i686 requires libHShaskeline-0.7.0.3-ghc7.6.3.so ghc-Agda-2.3.2.2-5.fc22.i686 requires ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5) ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires libHShaskeline-0.7.0.3-ghc7.6.3.so ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires ghc-devel(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5) ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires ghc(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3) ghc-Agda-devel-2.3.2.2-5.fc22.i686 requires ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5) [PyQuante] PyQuante-libint-1.6.4-11.fc22.1.i686 requires libint(x86-32) = 0:1.1.6-2.fc21 [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 [aws] aws-devel-3.1.0-6.fc21.i686 requires libgrypt-devel [blender] 1:blender-2.71-3.fc22.i686 requires libOpenCOLLADAStreamWriter.so.0.1 1:blender-2.71-3.fc22.i686 requires libOpenCOLLADASaxFrameworkLoader.so.0.1 1:blender-2.71-3.fc22.i686 requires libOpenCOLLADAFramework.so.0.1 1:blender-2.71-3.fc22.i686 requires libOpenCOLLADABaseUtils.so.0.1 1:blender-2.71-3.fc22.i686 requires libMathMLSolver.so.0.1 1:blender-2.71-3.fc22.i686 requires libGeneratedSaxParser.so.0.1 1:blenderplayer-2.71-3.fc22.i686 requires libOpenCOLLADAStreamWriter.so.0.1 1:blenderplayer-2.71-3.fc22.i686 requires libOpenCOLLADASaxFrameworkLoader.so.0.1 1:blenderplayer-2.71-3.fc22.i686 requires libOpenCOLLADAFramework.so.0.1 1:blenderplayer-2.71-3.fc22.i686 requires libOpenCOLLADABaseUtils.so.0.1 1:blenderplayer-2.71-3.fc22.i686 requires libMathMLSolver.so.0.1 1:blenderplayer-2.71-3.fc22.i686 requires libGeneratedSaxParser.so.0.1 [cab] cab-0.1.9-12.fc22.i686 requires cabal-dev [darcs] darcs-2.8.4-5.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so darcs-2.8.4-5.fc22.i686 requires libHShaskeline-0.7.0.3-ghc7.6.3.so darcs-2.8.4-5.fc22.i686 requires ghc(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3) darcs-2.8.4-5.fc22.i686 requires ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5) ghc-darcs-2.8.4-5.fc22.i686 requires libHSterminfo-0.3.2.5-ghc7.6.3.so ghc-darcs-2.8.4-5.fc22.i686 requires libHShaskeline-0.7.0.3-ghc7.6.3.so ghc-darcs-2.8.4-5.fc22.i686 requires ghc(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3) ghc-darcs-2.8.4-5.fc22.i686 requires ghc(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5) ghc-darcs-devel-2.8.4-5.fc22.i686 requires ghc-devel(terminfo-0.3.2.5-61e0dc43a1465e327dacd9ab37bbe1a3) ghc-darcs-devel-2.8.4-5.fc22.i686 requires ghc-devel(haskeline-0.7.0.3-775b029f16a4b58f3cc6b4cb4f7e7ac5) [debconf] debconf-1.5.53-1.fc22.noarch requires perl(:MODULE_COMPAT_5.18.2) [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 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 [eucalyptus] eucalyptus-common-java-3.3.0-0.5.20130408git32052445.fc20.i686 requires hibernate3-jbosscache = 0:3.6.10-7 [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 [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 [gnome-python2-desktop] gnome-python2-metacity-2.32.0-18.fc21.i686 requires libmetacity-private.so.0 [gnustep-back] gnustep-back-0.23.0-5.fc21.i686 requires libgnustep-gui.so.0.23 [gnustep-examples] gnustep-examples-1.3.0-19.fc20.i686 requires libgnustep-gui.so.0.23 [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) = 0:0.16.0 [gorm] gorm-1.2.18-5.fc20.i686 requires libgnustep-gui.so.0.23 [hledger] ghc-hledger-0.19.3-5.fc22.i686 requires
Password not recognized -
I have an updated Fedora 21 alpha that has worked perfectly until this morning's update. I rebooted and it no longer recognizes my password at the GUI loin screen. I does recognize me from this F-20 computer as bobg or root via ssh. I thought perhaps caps lock was on but no? Is it just me ? Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-20/64bit Linux/XFCE -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Fwd: Updated Beta Upgrade Requirements]
---BeginMessage---
Today, we worked out how we will be handling upgrades from F20-F21.
Please see below as a proposed edit to
https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria#Upgrade_requirements
=== span style=text-decoration:underlineUpgrade requirements/span
===
For each one of the release-blocking package sets, it must be possible
to successfully complete an upgrade from a fully updated installation of
the previous stable Fedora release with that package set installed. The
user must be made to specify which Product (or none) they wish to have
running when upgrade is complete.
{{hidden|header=Release-blocking package sets|content=The
release-blocking package sets are the minimal set, and the sets for each
one of the release-blocking desktops.|headerstyle=background:#e5e5e5|
fw1=normal|ta1=left}}
{{hidden|header=Recommended upgrade mechanisms|content=This criterion
applies to the [[Upgrading|recommended upgrade mechanisms]] only.|
headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Upgraded system requirements|content=
* The upgraded system must meet all release criteria.
* The upgraded system must include all packages that would be present
on the system after a default installation from install media, plus any
packages the user previously had (minus any obsolete content).
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* Initial upgrade criterion was part of initial Fedora 13 criteria
revision
* Adjusted to require upgraded system to work
[https://lists.fedoraproject.org/pipermail/test/2011-March/098288.html
2011-03-28]
* Adjusted to refer to 'officially supported upgrade mechanisms' rather
than specifying particular methods:
[https://lists.fedoraproject.org/pipermail/test/2012-September/110296.html
proposed 2012-09-24],
[https://lists.fedoraproject.org/pipermail/test/2012-October/110575.html
implemented 2012-10-03]
* Wording slightly re-organized as part of the major Fedora 19 criteria
revision
* Interpreted to require all fedup methods to work (or at least both
repository and ISO file) in
[http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-02/f20-blocker-review-%234.2013-12-02-17.02.log.txt
2013-12-02 blocker review meeting]
* Test cases:
** [[QA:Testcase_upgrade_fedup_cli_previous_desktop]]
** [[QA:Testcase_upgrade_fedup_cli_previous_kde]]
** [[QA:Testcase_upgrade_fedup_cli_previous_minimal]]
** [[QA:Testcase_upgrade_fedup_cli_previous_desktop_encrypted]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{anchor|virtualization-requirements}}
signature.asc
Description: This is a digitally signed message part
---End Message---
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: Password not recognized -
On Mon, 2014-10-06 at 10:47 -0400, Bob Goodwin - Zuni, Virginia, USA wrote: I have an updated Fedora 21 alpha that has worked perfectly until this morning's update. I rebooted and it no longer recognizes my password at the GUI loin screen. I does recognize me from this F-20 computer as bobg or root via ssh. I thought perhaps caps lock was on but no? Is it just me ? Does logging in at a console (ctrl-alt-f2) work? I haven't seen this, but then I haven't rebooted for a couple of days... -- 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: Password not recognized -
On 10/06/14 10:47, Bob Goodwin - Zuni, Virginia, USA wrote: I have an updated Fedora 21 alpha that has worked perfectly until this morning's update. I rebooted and it no longer recognizes my password at the GUI loin screen. I does recognize me from this F-20 computer as bobg or root via ssh. I thought perhaps caps lock was on but no? Is it just me ? Bob I've fixed the problem by eliminating the login gui and reverting to a runlevel 3 type text boot screen. I prefer that anyway. This morning's update also wiped out my preferred copy/paste by highlightinh the text to be copied, that had to be restored too. Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-20/64bit Linux/XFCE -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Password not recognized -
On 10/06/14 12:43, Adam Williamson wrote: Does logging in at a console (ctrl-alt-f2) work? I haven't seen this, but then I haven't rebooted for a couple of days... Yes that did work but it protested about starting xfce, it required startxfce -- :1 From there on I could do what needed to be done. Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-20/64bit Linux/XFCE -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Password not recognized -
On 10/06/2014 11:53 AM, Bob Goodwin - Zuni, Virginia, USA wrote: Yes that did work but it protested about starting xfce, it required startxfce -- :1 From there on I could do what needed to be done. You should not have to start X or start DEs by hand. You need to fix your environment... or report bugs if this is only effecting you. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Password not recognized -
On 10/06/14 12:55, Michael Cronenworth wrote: You should not have to start X or start DEs by hand. Yes I know that. I am trying to determine if I am a unique case. It may be that no one has booted since this morning's update? I reboot after every one. Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-20/64bit Linux/XFCE -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Some F21 Alpha impressions
On Sat, 2014-10-04 at 10:08 -0400, Jonathan Corbet wrote: Hey Jonathan, thanks for the feedback. - The main thing is that resume does not work in F21. Things appear to suspend just fine, but there is no response to pressing the blinking power button. I simply have to hold it until it powers down hard and start over. On my own Carbon with F21, suspend/resume seems to work fine, with lid close, power button or systemctl suspend. Given that you seem to have ruled out a kernel problem, I would point at systemd as the best starting point for further investigation. Is your system using EFI for booting ? - Emacs is *totally* confused about its window size. Any new window comes up essentially full screen, but the sizes it shows when one resizes indicates that it thinks its window is quite small - even though text display works just fine. F20 shows this too, it's not an F21 specific thing. Emacs is using GTK+ in 'interesting' way, things could certainly go wrong here. My system is not hidpi, but if I manually force a scale with GDK_SCALE=2 emacs, it seems to mostly work as I would expect it - everything is twice as big (except for the content font - thats the area where emacs is most special). - The huge onscreen keyboard seems to be easy to provoke and hard to make go away; this does seem to be new with F21. Is there any way to just turn that off? I like my touchscreen, but it's permanently attached to a physical keyboard a few cm away; I will *never* want the onscreen one. To make it go away, use the keyboard button in the lower right corner. Of course, having it come up unexpectedly is not great, and we need to improve this. Sadly hardware is very variable, and there are flip-over laptops where the keyboard might be physically hidden from you (by the flipped-over touchscreen), but still be very much present as a usb device. As a workaround in the short term, disabling the gnome-settings-daemon cursor plugin will prevent the OSK from being shown: gsettings set org.gnome.settings-daemon.plugins.cursor active false - Whatever happened to the ability to associate actions with mouse button events? That seems to be gone in F20 too? Is that another one of those things we're not supposed to worry our pretty little heads about anymore? What actions do you mean here ? I could imagine at least 2 things you might mean here - first, the modifier-click to trigger wm actions on the content of windows or second, various titlebar click actions. For the first, the modifier we use changed from Alt to Super (that was a while ago, though, might have already been in F20. The rationale for this change is to establish Super as the sole modifier used for 'system actions', and leave Alt/Ctrl/Shift to applications. To change things back, you can use the tweak tool. In the Windows tab, there is a Window Action Key control that lets you switch back to Alt. For the second, the same tweak-tool tab has a 'Titlebar Actions' section which can configure clicks in the titlebar. In F21 final, these settings will apply in the same way to CSD windows and traditional titlebars (this change is probably not yet in the alpha image you tried). -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Some F21 Alpha impressions
On Mon, Oct 6, 2014 at 7:58 PM, Jonathan Corbet corbet...@lwn.net wrote: The HiDPI pixel scaling stuff seems to be full of surprises, though. I've been exploring the intersection with external monitors, which is...not fully pleasing. Yeah this is a major limitation which is pretty much impossible to fix under X11. We can do better on wayland (we currently don't but hopefully will for gnome 3.16). -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Password not recognized -
On Mon, 2014-10-06 at 12:48 -0400, Bob Goodwin - Zuni, Virginia, USA wrote: I've fixed the problem by eliminating the login gui and reverting to a runlevel 3 type text boot screen. I prefer that anyway. This morning's update also wiped out my preferred copy/paste by highlightinh the text to be copied, that had to be restored too. Bob I updated today and haven't seen the password issue. Can you login using the console and check your journal? Can you also create a new user and see if the issue persists. Last question - upgrade from F20 or a fresh install? Can you check the yum logs to see what packages are updated? -- Thanks, Warm regards, Ankur (FranciscoD) http://fedoraproject.org/wiki/User:Ankursinha Join Fedora! Come talk to us! http://fedoraproject.org/wiki/Fedora_Join_SIG 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: Password not recognized -
On Mon, 2014-10-06 at 15:51 -0400, Bob Goodwin wrote: On 10/06/14 14:05, Ankur Sinha wrote: On Mon, 2014-10-06 at 12:48 -0400, Bob Goodwin - Zuni, Virginia, USA wrote: I've fixed the problem by eliminating the login gui and reverting to a runlevel 3 type text boot screen. I prefer that anyway. This morning's update also wiped out my preferred copy/paste by highlightinh the text to be copied, that had to be restored too. Bob I updated today and haven't seen the password issue. Can you login using the console and check your journal? Can you also create a new user and see if the issue persists. Last question - upgrade from F20 or a fresh install? Can you check the yum logs to see what packages are updated? [root@box7 bobg]# less /var/log/yum.log shows the following for this morning. The computer was idle until the reboot about six hours later. I always check to avoid discovering problems when later when it may be inconvenient. Oct 06 04:31:47 Updated: lightdm-gobject-1.10.2-1.fc21.x86_64 Oct 06 04:31:48 Updated: p11-kit-0.22.0-1.fc21.x86_64 Oct 06 04:31:48 Installed: lightdm-gtk-common-1.8.5-6.fc21.noarch Oct 06 04:31:49 Updated: lightdm-gtk-1.8.5-6.fc21.x86_64 Oct 06 04:31:49 Updated: lightdm-1.10.2-1.fc21.x86_64 Oct 06 04:31:50 Updated: p11-kit-trust-0.22.0-1.fc21.x86_64 Oct 06 04:31:50 Updated: albatross-gtk3-theme-1.7.3-1.fc21.noarch Oct 06 04:31:51 Updated: at-3.1.16-1.fc21.x86_64 Oct 06 04:31:51 Updated: bluebird-gtk3-theme-1.2-1.fc21.noarch Oct 06 04:31:52 Updated: btrfs-progs-3.16.2-1.fc21.x86_64 Oct 06 04:31:53 Updated: albatross-xfwm4-theme-1.7.3-1.fc21.noarch Oct 06 04:31:53 Updated: bluebird-xfwm4-theme-1.2-1.fc21.noarch Oct 06 04:31:54 Updated: dnf-0.6.2-1.fc21.noarch Oct 06 04:31:54 Updated: albatross-gtk2-theme-1.7.3-1.fc21.noarch Oct 06 04:31:55 Updated: iproute-3.16.0-3.fc21.x86_64 Oct 06 04:31:55 Updated: bluebird-gtk2-theme-1.2-1.fc21.noarch Oct 06 04:31:56 Updated: gdb-7.8-24.fc21.x86_64 Oct 06 04:31:57 Updated: yumex-3.0.16-1.fc21.noarch This was a new install from the XFCE Live Spin. It does not look like a password issue to me since I could login via ssh from another computer and by using another console. Ok, now I have restored the graphical.default so it logs in from the GUI again. Log in from bobg and root fails, as well as a new user I just added rfg. I had to start xfce from another console to complete this which I am writing from the Fedora 21a computer, a Dell 755 with 6 gigs of ram, all the DDR@ strips I had. But this has always been a good computer ... Look at the logs from the current boot around the time you tried to log in graphically. You should see some kind of error indicating what's going wrong with the graphical login. -- 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: Proposing new dual booting release criteria
On Wed, 2014-10-01 at 21:48 -0700, Adam Williamson wrote: On Wed, 2014-10-01 at 22:42 -0500, Michael Catanzaro wrote: On Wed, 2014-10-01 at 17:40 -0700, Adam Williamson wrote: I have now updated this in the Fedora 21 Final Release Criteria: https://fedoraproject.org/w/index.php?title=Fedora_21_Final_Release_Criteriadiff=390099oldid=374841 I think the proposed OS X criterion is also uncontroversial: The installer must be able to install into free space alongside an existing OS X installation, install and configure a bootloader that will boot Fedora; if the boot menu presents OS X entries, they should boot OS X. I was just giving a day more for feedback on my proposed addition of 'can't break the firmware boot menu'. I am now placing the following criterion into the 21 Final criteria: The installer must be able to install into free space alongside an existing OS X installation, install and configure a bootloader that will boot Fedora; if the boot menu presents OS X entries, they must boot OS X. Installing Fedora must not inhibit the system's ability to boot OS X from the UEFI boot manager. as no-one seemed to object to my proposal to ensure we don't break the bootability of OS X from the UEFI boot manager. Thanks folks! If we're not currently meeting this requirement, please do propose the relevant bug(s) as Final blocker(s). -- 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: Proposing new dual booting release criteria
On Mon, 2014-10-06 at 16:38 -0700, Adam Williamson wrote: On Wed, 2014-10-01 at 21:48 -0700, Adam Williamson wrote: On Wed, 2014-10-01 at 22:42 -0500, Michael Catanzaro wrote: On Wed, 2014-10-01 at 17:40 -0700, Adam Williamson wrote: I have now updated this in the Fedora 21 Final Release Criteria: https://fedoraproject.org/w/index.php?title=Fedora_21_Final_Release_Criteriadiff=390099oldid=374841 I think the proposed OS X criterion is also uncontroversial: The installer must be able to install into free space alongside an existing OS X installation, install and configure a bootloader that will boot Fedora; if the boot menu presents OS X entries, they should boot OS X. I was just giving a day more for feedback on my proposed addition of 'can't break the firmware boot menu'. I am now placing the following criterion into the 21 Final criteria: The installer must be able to install into free space alongside an existing OS X installation, install and configure a bootloader that will boot Fedora; if the boot menu presents OS X entries, they must boot OS X. Installing Fedora must not inhibit the system's ability to boot OS X from the UEFI boot manager. as no-one seemed to object to my proposal to ensure we don't break the bootability of OS X from the UEFI boot manager. Thanks folks! If we're not currently meeting this requirement, please do propose the relevant bug(s) as Final blocker(s). We have a test case for this lying around already. I've renamed it to follow the Windows test case name: https://fedoraproject.org/wiki/QA:Testcase_dualboot_with_OSX and I'll add it to the Installation matrix. Can someone with OS X experience please check it over and update/correct it if necessary? 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: [Fwd: Updated Beta Upgrade Requirements]
On Mon, 2014-10-06 at 11:21 -0400, Stephen Gallagher wrote: This is somewhat hard to read as it doesn't diff against the previous text. A mail which just specified what you actually intend to change, or a sandbox wiki page with a revision history that provides the diff, would be most useful. -- 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
