can one trust mirrors that claim to have fedora 20 ready for download right now?
as i remember it, new fedora releases typically become available mid to late morning of the release date, but i checked one of my common canadian mirrors and there it is (DVD image, checksum, netinst.iso), but the last modified date of all of that is back on dec 12. would that actually be the official release, or simply a misnamed beta? h ... it appears that mirrors.kernel.org has it up, with the same last modified dates. so i'm starting to be convinced. rday -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: can one trust mirrors that claim to have fedora 20 ready for download right now?
Robert P. J. Day rpjday at crashcourse.ca writes: as i remember it, new fedora releases typically become available mid to late morning of the release date, but i checked one of my common canadian mirrors and there it is (DVD image, checksum, netinst.iso), but the last modified date of all of that is back on dec 12. would that actually be the official release, or simply a misnamed beta? h ... it appears that mirrors.kernel.org has it up, with the same last modified dates. so i'm starting to be convinced. If there are signed checksum files, and they verify properly (see https://fedoraproject.org/en/verify ), then you can trust them, regardless of where you downloaded them from. The Gold Final version was RC1.1, which at the moment is still in https://dl.fedoraproject.org/pub/alt/stage/20-RC1.1/ (see the Go/No-Go meeting details from the links in https://lists.fedoraproject.org/pipermail/test-announce/2013-December/000838.html ). The checksums in your signed files should be identical to the ones in the unsigned files, and the signatures should be good. BTW, the reason the ISO times are from Dec. 12 is that that's when they were created - the Go/No-Go meeting was on that date and they were finished just in time. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
F20 Gnome-Documents
I just upgrade from a fresh install of F18 to 20 on my laptop(64bit) and would like to start using gnome-documents. (fedup worked great btw) My current setup seems to only be syncing one-way(local-Google). Is that the expected result or do I have to enable two-way somewhere? Thanks, Phil -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Warnings?
Hi Gang: For the last few upgrades / updates, I've been getting warnings such as are at the bottom of the output; what do they mean? Should I ignore them? setting up repos... adobe-linux-x86_64 | 951 B 00:00:00 default-installrepo/metalink | 22 kB 00:00:00 default-installrepo | 3.7 kB 00:00:00 default-installrepo/group_gz | 200 kB 00:00:00 default-installrepo/primary_db | 2.7 MB 00:00:06 google-chrome | 951 B 00:00:00 google-talkplugin | 951 B 00:00:00 updates/20/x86_64/metalink | 19 kB 00:00:00 getting boot images... .treeinfo | 1.1 kB 00:00:00 vmlinuz-fedup | 4.9 MB 00:00:08 initramfs-fedup.img | 29 MB 00:00:53 setting up update... default-installrepo/group | 864 kB 00:00:01 fedora/20/x86_64/group | 1.6 MB 00:00:03 updates/20/x86_64/group | 1.6 MB 00:00:02 repodata (google-talkplugin) 100% [==]Warning: group core does not exist. Warning: group gnome-desktop does not exist. Warning: group multimedia does not exist. Warning: group firefox does not exist. Warning: group guest-desktop-agents does not exist. Warning: group base-x does not exist. Warning: group anaconda-tools does not exist. Warning: group fonts does not exist. Warning: group hardware-support does not exist. Warning: group dial-up does not exist. Warning: group printing does not exist. Warning: group libreoffice does not exist. Warning: group input-methods does not exist. Warning: group standard does not exist. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Warnings?
Please see: https://fedoraproject.org/wiki/Common_F20_bugs#yum-group-errors kevin signature.asc Description: PGP signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
how to (properly) shut down a fedora 20 virtual machine?
not sure what list would be appropriate for this but i'll start here. currently running RHEL 6.5 on a 64-bit laptop, and installed a new fedora 20 VM using the Virtual Machine Manager -- seemed to work fine, f20 came up, looks good, but now i want to shut it down, so from the f20 console, i selected Virtual Machine - Shut Down - Shut Down, whereupon it *looks* like the VM shuts down, but the VMM window shows f20 Running should i expect a different result? i was expecting the VMM window to show that that VM was Stopped or something. i realize i could also select Force Off but i'd prefer not to be that brutal. am i doing something wrong? rday -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
[Fwd: Announcing the release of Fedora 20.]
FYI for those that don't know yet. Forwarded Message From: Robyn Bergeron rberg...@redhat.com To: annou...@lists.fedoraproject.org, devel-announce devel-annou...@lists.fedoraproject.org, test-announce test-annou...@lists.fedoraproject.org Subject: Announcing the release of Fedora 20. Date: Tue, 17 Dec 2013 10:02:30 -0500 (EST) Greetings! We can say with great certainty the Fedora Project is pleased to announce the release of Fedora 20 (Heisenbug), which coincides with the 10th anniversary of the creation of the Fedora Project. Download this leading-edge, free and open source operating system now: http://fedoraproject.org/get-fedora Detailed information about this release can be seen in the release notes: http://docs.fedoraproject.org/en-US/Fedora/20/html/Release_Notes/index.html *** Dedicated to Seth Vidal *** On July 8, the Fedora Project lost Seth Vidal, a dedicated, tireless, and brilliant contributor. Seth was a lead developer of Yum and the Fedora update repository system. He worked to ensure that the technical and community infrastructure of Fedora worked well and consistently for users and contributors around the world. Seth touched the lives of hundreds of Fedora contributors directly and millions of others indirectly by improving the experience of using and updating Fedora. The Fedora Project dedicates the Fedora 20 release to Seth and asks that you join us in remembering his generous spirit and incredible work that helped make Fedora what it is today. We miss you, Seth. *** 10 Years of Fedora *** The Fedora 20 release coincides with Fedora's tenth anniversary. The first Fedora release (then called Fedora Core 1) came out on November 6, 2003. The Fedora Project community has grown into an active and vibrant one that produces a new version of this leading-edge, free and open source operating system around every six months. *** Desktop Environments and Spins *** The Fedora Project strives to provide the best desktop experiences possible for users, from desktop environment to application selection. We also produce nearly a dozen spins tailor-made for desktop users, hardware design, gaming, musicians, artists, and early classroom environments. Spins are available for download here: https://fedoraproject.org/wiki/Releases/20/Spins == GNOME 3.10 == Fedora 20 comes with GNOME 3.10, which has several new applications and features that will please GNOME-lovers. This release includes a new music application (gnome-music), a new maps application (gnome-maps), a revamp for the system status menu, and Zimbra support in Evolution. == KDE Plasma Workspaces 4.11 == The Fedora KDE SIG has rebased to KDE 4.11 for Fedora 20. This release includes faster Nepomuk indexing, improvements to Kontact, KScreen integration in KWin, Metalink/HTTP support for KGet, and much more. == Spins == Spins are alternate versions of Fedora. In addition to various desktop environments for Fedora, spins are also available as tailored environments for various types of users via hand-picked application sets or customizations. See all of the Fedora 20 Release Spins here: https://fedoraproject.org/wiki/Releases/20/Spins *** ARM as a Primary Architecture *** While Fedora has supported a number of hardware architectures over the years, x86/x86_64 has been the default for the majority of Fedora users and for the Linux community in general. ARM, however, has been making massive strides. It already dominates the mobile market, is becoming a go-to platform for hobbyists and makers, and is showing enormous promise for the server market as well. In keeping with Fedora's commitment to innovation, the Fedora community has been pushing to make ARM a primary architecture to satisfy the needs of users and developers targeting the ARM platform. *** Cloud and Virtualization Improvements *** The Fedora 20 release continues the Fedora tradition of adopting and integrating leading edge technologies used in cloud computing. This release includes features that will make working with virtualization and cloud computing much easier. == First-Class Cloud Images == The Fedora Cloud SIG has been working hard to provide images that are well-suited for running as guests in public and private clouds like Amazon Web Services (AWS) and OpenStack. If you're using public or private cloud, you should grab one of the downloadable Cloud Images or find a supported EC2 image, here: http://fedoraproject.org/en/get-fedora-options#clouds == VM Snapshot UI with virt-manager == Taking VM snapshots is now much easier. Though qemu and libvirt have all the major pieces in place for performing safe VM snapshots/checkpoints, there isn't any simple, discoverable UI. This feature will track adding that UI to virt-manager and any other virt stack bits that need to be fixed/improved, including adding functionality to libvirt to support deleting and rebasing to external snapshots. == ARM
Fwd: Version upgrade from Fedora 17 to Fedora 20
I have been gradually updating my Fedora servers from a variety of releases ranging to F14 to F18 to more current versions. In order to do these as in-place updates rather than re-installs (which saves many headaches) I have had to do this gradually. Most are now running F19 with one pioneer at F20. But one that started at F14 seems to be stuck at F17, since F17 has been archived, and thus I cannot do yum install fedup since the links in /etc/yum.fedora.repo are now invalid. What is the best workaround? I know that once I have fedup installed, I can go to F19 with a minimum of hassle (mostly the apache config file restructuring, but that machine does not run apache anyway). Bu thow do I get there? - can I find the F17 fedup rpm in archive.fedoraproject.org and just install it manually? - can I update the /etc/yum.fedora.repo file to point to the archived set? (Can you send me a working file?) Lars Poulsen Afar Communications Inc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to (properly) shut down a fedora 20 virtual machine?
On Dec 17, 2013, at 8:43 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: not sure what list would be appropriate for this but i'll start here. currently running RHEL 6.5 on a 64-bit laptop, and installed a new fedora 20 VM using the Virtual Machine Manager -- seemed to work fine, f20 came up, looks good, but now i want to shut it down, so from the f20 console, i selected Virtual Machine - Shut Down - Shut Down, whereupon it *looks* like the VM shuts down, but the VMM window shows That command should be the same as 'virsh shutdown vmname'. I'm not sure how the message gets to the VM to shut it down cleanly but I'm guessing some sort of message gets to systemd in the VM. How long have you waited for it to shutdown? You might be running into this bug: slow shutdown unit user@0.service entered failed state https://bugzilla.redhat.com/show_bug.cgi?id=1023820 I'm running into that delayed reboot/shutdown bug a lot. Not every time, but maybe 1/3 of the time? It happens on baremetal and in VMs. New F20 installs, and updated ones. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Job opportunities at Lancaster University Library
With apologies for cross posting, these jobs may be of relevance to the audience on this list. -- Job opportunities at Lancaster University Library 2 new roles Digital developer (Library) Salary: £31,644 - £36,611 Closing date 6 January 2014 Join a fast paced-responsive team using agile methodologies to innovate in a rapidly evolving environment. Responsible for developing, enhancing and supporting library technologies and services to improve users' digital experience. Advanced technical skills especially in web-based applications essential. Research data and repository manager Salary: £31,644 - £36,611 Closing date 8 January 2014 Responsible for developing services, procedures, advice and training to support research data management and the institutional repository. You will have good background knowledge of these areas plus excellent analytical and organisational abilities and strong interpersonal skills to work with academic researchers and across teams. Further details from http://hr-jobs.lancs.ac.uk/Vacancies.aspx -- Thanks, Masud -- Masud Khokhar Head of Digital Innovation The Library, Lancaster University Bailrigg, Lancaster, LA1 4YH Tel: (01524) 5-94236 Email: masud.khok...@lancaster.ac.ukmailto:masud.khok...@lancaster.ac.uk -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On Dec 17, 2013, at 1:22 PM, Joe Zeff j...@zeff.us wrote: On 12/17/2013 11:57 AM, Bob Goodwin wrote: Joe, if I must justify my actions, and I question that, there's no big rush it's just another form of amusement for me. No, you don't need to justify your actions; if you find it amusing to be an early adopter and deal with all of the last-minute oopsies, that's all I need to know. My post was intended to explain why I prefer to wait, and ask why others rush in. Because it's fun to break things, and get irritated; irritation is motivation to fine causes, file bugs, and get things fixed. That's why I QA anyway. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to (properly) shut down a fedora 20 virtual machine?
Quoting Joe Zeff j...@zeff.us: On 12/17/2013 11:16 AM, Chris Murphy wrote: If you do it within the VM, what result do you get with 'poweroff'? systemd maps init 0 to poweroff, as of course there is no init with systemd, but it maintains compatibility with init scripts so I expect init 0 to work the same as poweroff. I don't know how the mapping is done, but if it were me, init would be a simple bash script with a case statement that made the requested system call depending on the argument. Just a thought. at this point, i'm not sure how much more helpful i can be. is anyone else seeing this behaviour? be annoying to find out it's just me. :-( rday -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On 17 December 2013 19:57, Bob Goodwin bobgood...@wildblue.net wrote: On 17/12/13 14:25, Joe Zeff wrote: Why be in such a hurry to upgrade? Is being an early adopter that important to you? On the first day or so of a new release, the repos are going to be slammed, just as the MS servers are on Patch Tuesday. And, of course, there's always the few (we hope) bugs and glitches that didn't get caught in beta-testing. I always wait at least a week, to see how things are going, and then I only upgrade my laptop. My desktop, and main work machine, can wait until I'm sure that the laptop's OK. And, if I see large numbers of threads here and on the various web fora about upgrade issues, I'll wait even longer, sometimes skipping a version if it seems buggier than normal. Of course, I'm only responsible for my own boxes at home, and being retired have no work boxes to consider, but I'd think that a little bit of patience might be a good thing here. YMMV, and clearly does, but I do wonder a tad about what's the big rush. (If you have a good reason, such as a need for the newest version of something, of course, that's different. It's just the change for the sake of change attitude that I don't quite understand.) Joe, if I must justify my actions, and I question that, there's no big rush it's just another form of amusement for me. I had been running F-20 in VMware and decided it worked well enough to use. The hard drive on which F-19 is installed was becoming too full. I installed a larger drive from an F-16 computer that failed several weeks ago and decided I would move my work into the larger drive, why not with F-20 beta which I already knew was good to go? So here I am. I still have F-19 available on this computer if I mess up anything as well as having a second F-19 computer configured to be like this one and can swap configuration files back and fourth as well as storing copies on an NFS server. The more I mess with this stuff the better my ability becomes at manipulating things and I solve most of the problems I create, only come here when I have to. In fact by definition it's people running pre-release for whatever reason who are doing the testing! And even if you don't want, or don't think you're wanted, to fill out test matrices, you can still provide feedback on individual packages. People with the time, resources and inclination are more than welcome to run beta. -- imalone http://ibmalone.blogspot.co.uk -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On 12/17/2013 11:57 AM, Bob Goodwin wrote: Joe, if I must justify my actions, and I question that, there's no big rush it's just another form of amusement for me. No, you don't need to justify your actions; if you find it amusing to be an early adopter and deal with all of the last-minute oopsies, that's all I need to know. My post was intended to explain why I prefer to wait, and ask why others rush in. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On 17/12/13 14:25, Joe Zeff wrote: Why be in such a hurry to upgrade? Is being an early adopter that important to you? On the first day or so of a new release, the repos are going to be slammed, just as the MS servers are on Patch Tuesday. And, of course, there's always the few (we hope) bugs and glitches that didn't get caught in beta-testing. I always wait at least a week, to see how things are going, and then I only upgrade my laptop. My desktop, and main work machine, can wait until I'm sure that the laptop's OK. And, if I see large numbers of threads here and on the various web fora about upgrade issues, I'll wait even longer, sometimes skipping a version if it seems buggier than normal. Of course, I'm only responsible for my own boxes at home, and being retired have no work boxes to consider, but I'd think that a little bit of patience might be a good thing here. YMMV, and clearly does, but I do wonder a tad about what's the big rush. (If you have a good reason, such as a need for the newest version of something, of course, that's different. It's just the change for the sake of change attitude that I don't quite understand.) Joe, if I must justify my actions, and I question that, there's no big rush it's just another form of amusement for me. I had been running F-20 in VMware and decided it worked well enough to use. The hard drive on which F-19 is installed was becoming too full. I installed a larger drive from an F-16 computer that failed several weeks ago and decided I would move my work into the larger drive, why not with F-20 beta which I already knew was good to go? So here I am. I still have F-19 available on this computer if I mess up anything as well as having a second F-19 computer configured to be like this one and can swap configuration files back and fourth as well as storing copies on an NFS server. The more I mess with this stuff the better my ability becomes at manipulating things and I solve most of the problems I create, only come here when I have to. Bob -- http://www.qrz.com/db/W2BOD Box 10 Fedora-20b/64 XFCE Linux -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to (properly) shut down a fedora 20 virtual machine?
On Dec 17, 2013, at 12:47 PM, Robert P. J. Day rpj...@crashcourse.ca wrote: Quoting Joe Zeff j...@zeff.us: On 12/17/2013 11:16 AM, Chris Murphy wrote: If you do it within the VM, what result do you get with 'poweroff'? systemd maps init 0 to poweroff, as of course there is no init with systemd, but it maintains compatibility with init scripts so I expect init 0 to work the same as poweroff. I don't know how the mapping is done, but if it were me, init would be a simple bash script with a case statement that made the requested system call depending on the argument. Just a thought. at this point, i'm not sure how much more helpful i can be. is anyone else seeing this behaviour? be annoying to find out it's just me. :-( I've seen it before, in the F18/19 time frame my recollection was it always was like this. But the last ~6 months I connect to the host computer via 'ssh blah@f20s.local -L 5900:127.0.0.1:5900' and use virsh to manipulate the VM from the outside, and TigerVNC pointed to 127.0.0.1 to control the VM from the inside, as well as ssh. Therefore I'm not regularly using virt-manager. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
strange warnings in .xsession-errors
I am running Mate (and Cinnamon) on Fedora 19...and lately noticed these errors in my .xsession-errors file when I am in Mate Does anyone know what's behind them ? mate-session[2557]: WARNING: Could not parse desktop file /home/frank/.config/autostart/sealertauto.desktop: Key file does not have key 'Type' mate-session[2557]: WARNING: could not read /home/frank/.config/autostart/sealertauto.desktop mate-session[2557]: WARNING: Could not parse desktop file /home/frank/.config/autostart/blueman.desktop: Key file does not have key 'Name' mate-session[2557]: WARNING: could not read /home/frank/.config/autostart/blueman.desktop mate-session[2557]: WARNING: Could not parse desktop file /home/frank/.config/autostart/print-applet.desktop: Key file does not have key 'Name' mate-session[2557]: WARNING: could not read /home/frank/.config/autostart/print-applet.desktop mate-session[2557]: WARNING: Could not parse desktop file /home/frank/.config/autostart/gdesklets.desktop: Key file does not have key 'Name' mate-session[2557]: WARNING: could not read /home/frank/.config/autostart/gdesklets.desktop mate-session[2557]: EggSMClient-WARNING: Invalid Version string '0.9.4' in /home/frank/.config/autostart/Compiz.desktop mate-session[2557]: WARNING: Could not parse desktop file /home/frank/.config/autostart/spice-vdagent.desktop: Key file does not have key 'Name' mate-session[2557]: WARNING: could not read /home/frank/.config/autostart/spice-vdagent.desktop mate-session[2557]: EggSMClient-WARNING: Invalid Version string '0.9.4' in /home/frank/.config/autostart/Window Manager.desktop mate-session[2557]: WARNING: Could not parse desktop file /home/frank/.config/autostart/xfce4-clipman-plugin-autostart.desktop: Key file does not have key 'Name' mate-session[2557]: WARNING: could not read /home/frank/.config/autostart/xfce4-clipman-plugin-autostart.desktop -- Your mail is being read by tight-lipped NSA agents who fail to see the humor in Doctor Strangelove. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to (properly) shut down a fedora 20 virtual machine?
Quoting Chris Murphy li...@colorremedies.com: On Dec 17, 2013, at 8:43 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: not sure what list would be appropriate for this but i'll start here. currently running RHEL 6.5 on a 64-bit laptop, and installed a new fedora 20 VM using the Virtual Machine Manager -- seemed to work fine, f20 came up, looks good, but now i want to shut it down, so from the f20 console, i selected Virtual Machine - Shut Down - Shut Down, whereupon it *looks* like the VM shuts down, but the VMM window shows That command should be the same as 'virsh shutdown vmname'. I'm not sure how the message gets to the VM to shut it down cleanly but I'm guessing some sort of message gets to systemd in the VM. How long have you waited for it to shutdown? You might be running into this bug: slow shutdown unit user@0.service entered failed state https://bugzilla.redhat.com/show_bug.cgi?id=1023820 I'm running into that delayed reboot/shutdown bug a lot. Not every time, but maybe 1/3 of the time? It happens on baremetal and in VMs. New F20 installs, and updated ones. ok, here's what i'm testing right now, and reporting on in real time. first, i noticed earlier that a fast way to shut down the f20 VM is to simply type: # init 0 if the VMM showed f20 Running, within seconds of typing that command, the console disconnected and the VMM showed f20 Shutoff, so that's the response time i'm looking for. so ... start the VM again, let it boot, log in, then return to VMM and Shut Down - Shut Down. As before, console goes black, but VMM continues to show f20 Running (even though CPU monitor in VMM seems to be totally quiet for that VM). ok, it's been over a minute and still f20 Running. i won't worry about it too much more since i know that init 0 works, but it's still kind of weird. rday -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On 12/17/2013 12:32 PM, Ian Malone wrote: In fact by definition it's people running pre-release for whatever reason who are doing the testing! And even if you don't want, or don't think you're wanted, to fill out test matrices, you can still provide feedback on individual packages. People with the time, resources and inclination are more than welcome to run beta. Of course. And, if you're running beta, you need to understand that the software you're using may not be ready for prime time yet. I've seen enough threads on various support fora from users running beta and expecting it to be as well polished and bug free (ha!) as production versions to know that there are an awful large number of people who think that beta means latest and greatest. And, as far as running beta goes, I have the time and the resources, but not the inclination. Cleaning up after an upgrade hung, or otherwise failed so that I don't have to do a complete re-install and figure out what packages I forgot to select is about the biggest job I'm willing to get involved in any more. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: qmake
On Tue, Dec 17, 2013 at 1:14 PM, Patrick Dupre pdu...@gmx.com wrote: Hello, Is there a qmake package for fedora? I found stuff for windows but nothing for linux! # repoquery --whatprovides /usr/bin/qmake-qt4 qt-devel-1:4.8.4-19.fc19.i686 qt-devel-1:4.8.4-19.fc19.x86_64 qt-devel-1:4.8.5-10.fc19.x86_64 qt-devel-1:4.8.5-10.fc19.i686 HTH, Richard -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On Dec 17, 2013, at 1:43 PM, Joe Zeff j...@zeff.us wrote: And, as far as running beta goes, I have the time and the resources, but not the inclination. Cleaning up after an upgrade hung, or otherwise failed so that I don't have to do a complete re-install and figure out what packages I forgot to select is about the biggest job I'm willing to get involved in any more. -- Fedora doesn't magically get more stable. It's due to testing, bug reporting, and triaging those bugs, much of which is done by volunteers. The more testers, the better the coverage, the more bugs are found before release. The stability depends in large part on the community's contribution into finding and properly reporting bugs (reproduce instructions, attaching the proper logs, etc.) The community gets out of Fedora what's put into it. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
fedup to F20 failed
I made a DVD and ran fedup --device --network 20 Everything went OK until I rebooted and selected the fedup upgrade. After thrashing around for a while, the system went into emergency mode, unable to find a file system. Rebooted and tried again with the same result. I was able to reboot back into F19 and here I am. So... Is there any way to capture the error messages from the fedup kernel to report here? Anyone else have a similar problem? -- -- Steve -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On 17/12/13 13:40, Frank Murphy wrote: On Tue, 17 Dec 2013 13:38:49 -0500 Bob Goodwin bobgood...@wildblue.net wrote: What do I do with a Fedora-20 beta install to update it? yum or dnf update it. [root@box10 bobg]# yum update Loaded plugins: langpacks, refresh-packagekit No packages marked for update So I can conclude all is well and it is what I want it to be? As I said I updated it around 04:00 this morning before the official release time so it would seem it whould be updated to the max. Thanks, Bob -- http://www.qrz.com/db/W2BOD Box 10 Fedora-20b/64 XFCE Linux -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Fedora-20 beta -
What do I do with a Fedora-20 beta install to update it? It was updated early this morning and I suspect it is now the equivalent of the new release. Will I have problems with yum updates? Presently it shows: [bobg@box10 ~]$ uname -a Linux box10 3.11.10-300.fc20.x86_64 #1 SMP Fri Nov 29 19:16:48 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [bobg@box10 ~]$ cat /etc/redhat-release Fedora release 20 (Heisenbug) Indications are it's Fedora-20 as it is ... I haven't found this mentioned in a Google search, perhaps I didn't use the right keyword/phrase. Suggestions please. Bob -- http://www.qrz.com/db/W2BOD Box 10 Fedora-20b/64 XFCE Linux -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to (properly) shut down a fedora 20 virtual machine?
On Dec 17, 2013, at 12:59 PM, Chris Murphy li...@colorremedies.com wrote: Urgh. I think this is a bug getting the external shutdown message passed into the VM. So this might mean setting up the VM with a serial device, and using virsh console so that even if it gets networking in the VM all shutdown, you can still control and see what's happening, or in this case what's not happening.. OK, I have a completely new F20 baremetal host installed (from DVD ISO, default desktop packageset without libreoffice and no other additions), with updates-testing enabled, all updates applied, and with group Virtualization installed. One non-stock thing I'm doing is running kernel 3.13.0-0.rc4.git0.1.fc21. This is not a debug kernel. Booting Fedora 20 Live Desktop with virt-manager, get to the desktop and immediate go to virt-manager's powerbutton icon pulldown menu and choose Shut Down. It takes a while but it down eventually shutdown the VM. If I retry this with virsh shutdown, it also works, eventually. However, I just tried yet again, using virsh console to see if it's the same bug as before, and I get the result you've got, black screen. But virsh list reports the VM as pmsuspended even though I clearly chose Shut Down. Serial console reports this: Trying to enqueue job suspend.target/start/replace-irreversibly Installed new job suspend.target/start as 1106 Installed new job systemd-suspend.service/start as 1107 Installed new job sleep.target/start as 1108 Enqueued job suspend.target/start as 1106 sleep.target changed dead - active Job sleep.target/start finished, result=done About to execute: /usr/lib/systemd/systemd-sleep suspend Forked /usr/lib/systemd/systemd-sleep as 1813 systemd-suspend.service changed dead - start Set up jobs progress timerfd. Set up idle_pipe watch. [ 98.381270] PM: Syncing filesystems ... done. [ 98.772061] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 98.833275] Freezing remaining freezable tasks ... (elapsed 0.007 seconds) done. [ 98.861637] Suspending console(s) (use no_console_suspend to debug) So that's consistent with what you're seeing I think. I got sick of the user@0.service bug causing delays and formed the habit of using virsh destroy. Looks like a totally separate bug here. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
System mail (Fedora 20)
Hi, I have a question. On Tue, Dec 17, 2013 at 10:02:30AM -0500, Robyn Bergeron wrote: == No Default Sendmail, Syslog == In the interests of paring down services that are generally not used on desktop systems, Fedora 20 removes and replaces some services that many users find unnecessary from the Live Desktop DVD. They will remain available as installable packages for users who might need them. The systemd journal now takes the place as the default logging solution for minimal and other selected installation methods, such as the Live Desktop DVD, having been tested and able to manage persistent logging in place of syslog. Also, Sendmail will no longer be installed by default, as most Fedora installs have no need of a Mail Transfer Agent (MTA). Does this mean there won't be any system mail (e.g. mail from root, cron jobs, etc)? I have never really used sendmail, but I always thought system mail was handled by the default MTA; hence my question. Thanks, -- Suvayu Open source is the future. It sets us free. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to (properly) shut down a fedora 20 virtual machine?
On Dec 17, 2013, at 11:42 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: Quoting Chris Murphy li...@colorremedies.com: On Dec 17, 2013, at 8:43 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: not sure what list would be appropriate for this but i'll start here. currently running RHEL 6.5 on a 64-bit laptop, and installed a new fedora 20 VM using the Virtual Machine Manager -- seemed to work fine, f20 came up, looks good, but now i want to shut it down, so from the f20 console, i selected Virtual Machine - Shut Down - Shut Down, whereupon it *looks* like the VM shuts down, but the VMM window shows That command should be the same as 'virsh shutdown vmname'. I'm not sure how the message gets to the VM to shut it down cleanly but I'm guessing some sort of message gets to systemd in the VM. How long have you waited for it to shutdown? You might be running into this bug: slow shutdown unit user@0.service entered failed state https://bugzilla.redhat.com/show_bug.cgi?id=1023820 I'm running into that delayed reboot/shutdown bug a lot. Not every time, but maybe 1/3 of the time? It happens on baremetal and in VMs. New F20 installs, and updated ones. ok, here's what i'm testing right now, and reporting on in real time. first, i noticed earlier that a fast way to shut down the f20 VM is to simply type: # init 0 if the VMM showed f20 Running, within seconds of typing that command, the console disconnected and the VMM showed f20 Shutoff, so that's the response time i'm looking for. so ... start the VM again, let it boot, log in, then return to VMM and Shut Down - Shut Down. As before, console goes black, but VMM continues to show f20 Running (even though CPU monitor in VMM seems to be totally quiet for that VM). ok, it's been over a minute and still f20 Running. i won't worry about it too much more since i know that init 0 works, but it's still kind of weird. If you do it within the VM, what result do you get with 'poweroff'? systemd maps init 0 to poweroff, as of course there is no init with systemd, but it maintains compatibility with init scripts so I expect init 0 to work the same as poweroff. I wonder if the GUI Shutdown option is mapped to halt rather than halt -p? That could be a bug. I'd expect Shutdown in the GUI to be the equivalent of power off within the VM, or of 'virsh shutdown' from the host. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: fedup to F20 failed
On Tue, 2013-12-17 at 15:04 -0600, Steven Stern wrote: I made a DVD and ran fedup --device --network 20 Everything went OK until I rebooted and selected the fedup upgrade. After thrashing around for a while, the system went into emergency mode, unable to find a file system. Rebooted and tried again with the same result. I was able to reboot back into F19 and here I am. So... Is there any way to capture the error messages from the fedup kernel to report here? Anyone else have a similar problem? -- -- Steve if you want to capture the boot info while it's in emergency mode do journalctl -xb ~/somefileorother Interestingly I've had a similar issue with --iso https://bugzilla.redhat.com/show_bug.cgi?id=1044128 Junk -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to (properly) shut down a fedora 20 virtual machine?
Quoting Chris Murphy li...@colorremedies.com: On Dec 17, 2013, at 11:42 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: Quoting Chris Murphy li...@colorremedies.com: On Dec 17, 2013, at 8:43 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: not sure what list would be appropriate for this but i'll start here. currently running RHEL 6.5 on a 64-bit laptop, and installed a new fedora 20 VM using the Virtual Machine Manager -- seemed to work fine, f20 came up, looks good, but now i want to shut it down, so from the f20 console, i selected Virtual Machine - Shut Down - Shut Down, whereupon it *looks* like the VM shuts down, but the VMM window shows That command should be the same as 'virsh shutdown vmname'. I'm not sure how the message gets to the VM to shut it down cleanly but I'm guessing some sort of message gets to systemd in the VM. How long have you waited for it to shutdown? You might be running into this bug: slow shutdown unit user@0.service entered failed state https://bugzilla.redhat.com/show_bug.cgi?id=1023820 I'm running into that delayed reboot/shutdown bug a lot. Not every time, but maybe 1/3 of the time? It happens on baremetal and in VMs. New F20 installs, and updated ones. ok, here's what i'm testing right now, and reporting on in real time. first, i noticed earlier that a fast way to shut down the f20 VM is to simply type: # init 0 if the VMM showed f20 Running, within seconds of typing that command, the console disconnected and the VMM showed f20 Shutoff, so that's the response time i'm looking for. so ... start the VM again, let it boot, log in, then return to VMM and Shut Down - Shut Down. As before, console goes black, but VMM continues to show f20 Running (even though CPU monitor in VMM seems to be totally quiet for that VM). ok, it's been over a minute and still f20 Running. i won't worry about it too much more since i know that init 0 works, but it's still kind of weird. If you do it within the VM, what result do you get with 'poweroff'? systemd maps init 0 to poweroff, as of course there is no init with systemd, but it maintains compatibility with init scripts so I expect init 0 to work the same as poweroff. unsurprisingly, poweroff was equivalent to init 0 in terms of how quickly the VMM moved to displaying f20 Shutoff. I wonder if the GUI Shutdown option is mapped to halt rather than halt -p? That could be a bug. I'd expect Shutdown in the GUI to be the equivalent of power off within the VM, or of 'virsh shutdown' from the host. ah, and doing virsh shutdown f20 blanks the console of the VM, but leaves the VMM displaying f20 Running. so virsh shutdown isn't even shutting down the VM properly. rday -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to (properly) shut down a fedora 20 virtual machine?
On 12/17/2013 11:16 AM, Chris Murphy wrote: If you do it within the VM, what result do you get with 'poweroff'? systemd maps init 0 to poweroff, as of course there is no init with systemd, but it maintains compatibility with init scripts so I expect init 0 to work the same as poweroff. I don't know how the mapping is done, but if it were me, init would be a simple bash script with a case statement that made the requested system call depending on the argument. Just a thought. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On Tue, 17 Dec 2013 13:38:49 -0500 Bob Goodwin bobgood...@wildblue.net wrote: What do I do with a Fedora-20 beta install to update it? It was updated early this morning and I suspect it is now the equivalent of the new release. Will I have problems with yum updates? Presently it shows: [bobg@box10 ~]$ uname -a Linux box10 3.11.10-300.fc20.x86_64 #1 SMP Fri Nov 29 19:16:48 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [bobg@box10 ~]$ cat /etc/redhat-release Fedora release 20 (Heisenbug) Indications are it's Fedora-20 as it is ... I haven't found this mentioned in a Google search, perhaps I didn't use the right keyword/phrase. Suggestions please. You will need to do a 'yum distro-sync' or re-enable the updates-testing repo if you wish to help test updates. See: http://www.scrye.com/wordpress/nirik/2013/12/01/updates-testing-and-final-freeze-time-again/ for more info. kevin signature.asc Description: PGP signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On 17/12/13 13:49, Kevin Fenzi wrote: On Tue, 17 Dec 2013 13:38:49 -0500 Bob Goodwin bobgood...@wildblue.net wrote: What do I do with a Fedora-20 beta install to update it? It was updated early this morning and I suspect it is now the equivalent of the new release. You will need to do a 'yum distro-sync' or re-enable the updates-testing repo if you wish to help test updates. See: http://www.scrye.com/wordpress/nirik/2013/12/01/updates-testing-and-final-freeze-time-again/ for more info. kevin It seems they insist testers use a straight Fedora 20 install and I prefer to use XFCE configured as I want things so I gave up on helping test. Ok, I ran yum distro-sync and that appeared to do what it should. Then yum update again: [root@box10 bobg]# yum update Loaded plugins: langpacks, refresh-packagekit Unable to send message to PackageKit No packages marked for update Thanks, Bob -- http://www.qrz.com/db/W2BOD Box 10 Fedora-20b/64 XFCE Linux -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to (properly) shut down a fedora 20 virtual machine?
On Dec 17, 2013, at 1:46 PM, Chris Murphy li...@colorremedies.com wrote: So that's consistent with what you're seeing I think. I got sick of the user@0.service bug causing delays and formed the habit of using virsh destroy. Looks like a totally separate bug here. https://bugzilla.redhat.com/show_bug.cgi?id=1044145 I think I figured it out. This is some GUI confusion. The option is Shut Down, but due to how the VM is launched, the -no-shutdown option is used by default, which makes the shut down command a pmsuspend command instead. This may end up turning into notabug. But I think it's sufficient confusing that at least the term used should be re-evaluated. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: how to (properly) shut down a fedora 20 virtual machine?
On Dec 17, 2013, at 12:29 PM, Robert P. J. Day rpj...@crashcourse.ca wrote: ah, and doing virsh shutdown f20 blanks the console of the VM, but leaves the VMM displaying f20 Running. so virsh shutdown isn't even shutting down the VM properly. Urgh. I think this is a bug getting the external shutdown message passed into the VM. So this might mean setting up the VM with a serial device, and using virsh console so that even if it gets networking in the VM all shutdown, you can still control and see what's happening, or in this case what's not happening.. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
qmake
Hello, Is there a qmake package for fedora? I found stuff for windows but nothing for linux! Thank. === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France === -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On 12/17/2013 10:48 AM, Bob Goodwin wrote: As I said I updated it around 04:00 this morning before the official release time so it would seem it whould be updated to the max. Why be in such a hurry to upgrade? Is being an early adopter that important to you? On the first day or so of a new release, the repos are going to be slammed, just as the MS servers are on Patch Tuesday. And, of course, there's always the few (we hope) bugs and glitches that didn't get caught in beta-testing. I always wait at least a week, to see how things are going, and then I only upgrade my laptop. My desktop, and main work machine, can wait until I'm sure that the laptop's OK. And, if I see large numbers of threads here and on the various web fora about upgrade issues, I'll wait even longer, sometimes skipping a version if it seems buggier than normal. Of course, I'm only responsible for my own boxes at home, and being retired have no work boxes to consider, but I'd think that a little bit of patience might be a good thing here. YMMV, and clearly does, but I do wonder a tad about what's the big rush. (If you have a good reason, such as a need for the newest version of something, of course, that's different. It's just the change for the sake of change attitude that I don't quite understand.) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On Dec 17, 2013, at 12:05 PM, Bob Goodwin bobgood...@wildblue.net wrote: On 17/12/13 13:49, Kevin Fenzi wrote: On Tue, 17 Dec 2013 13:38:49 -0500 Bob Goodwin bobgood...@wildblue.net wrote: What do I do with a Fedora-20 beta install to update it? It was updated early this morning and I suspect it is now the equivalent of the new release. You will need to do a 'yum distro-sync' or re-enable the updates-testing repo if you wish to help test updates. See: http://www.scrye.com/wordpress/nirik/2013/12/01/updates-testing-and-final-freeze-time-again/ for more info. kevin It seems they insist testers use a straight Fedora 20 install and I prefer to use XFCE configured as I want things so I gave up on helping test. Ok, I ran yum distro-sync and that appeared to do what it should. Then yum update again: [root@box10 bobg]# yum update Loaded plugins: langpacks, refresh-packagekit Unable to send message to PackageKit No packages marked for update Check commonbugs, in particular this one pertaining to pre-release installation /root permissions: https://fedoraproject.org/wiki/Common_F20_bugs#.2Froot_permissions_incorrect_on_pre-release_installations Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Cron vs. Whenjobs vs. Goaljobs
I'm interested in a replacement for cron which would allow me to run various cron jobs on demand, and mark them as having been run, so they won't be run again from the schedule. Looking through the Fedora repository, I noticed whenjobs, which looks like it may do the job (no pun intended). The documentation for whenjobs says that it is obsolete and has been replaced by goaljobs. Has anyone tried out whenjobs or goaljobs. Any problems? Will they do what I need done? Thanks - jon -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On Tue, 17 Dec 2013 13:38:49 -0500 Bob Goodwin bobgood...@wildblue.net wrote: What do I do with a Fedora-20 beta install to update it? yum or dnf update it. -- Regards, Frank www.frankly3d.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On 17/12/13 14:22, Chris Murphy wrote: Check commonbugs, in particular this one pertaining to pre-release installation /root permissions: https://fedoraproject.org/wiki/Common_F20_bugs#.2Froot_permissions_incorrect_on_pre-release_installations Chris Murphy Ok, I changed the permissions as suggested. Bob -- http://www.qrz.com/db/W2BOD Box 10 Fedora-20b/64 XFCE Linux -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
another FedUp issue
I wiped out the failed fedup (deleted stuff from grub.con and /var/tmp/) and tried again with fedup from updates-testing. This time, I got errors after fedup ran: WARNING: problems were encountered during transaction test: broken dependencies libreoffice-pdfimport-1:4.1.3.2-12.fc19.x86_64 requires poppler-0.22.1-5.fc19.x86_64 libreoffice-core-1:4.1.3.2-12.fc19.x86_64 requires boost-date-time-1.53.0-14.fc19.x86_64 ufraw-gimp-0.19.2-10.fc19.x86_64 requires cfitsio-3.340-1.fc19.x86_64 gnome-shell-extension-xrandr-indicator-3.8.4-1.fc19.noarch requires gnome-shell-extension-common-3.8.4-1.fc19.noarch Continue with the upgrade at your own risk. I think I'm going to put off a fedup to f20 for a while. -- -- Steve -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: another FedUp issue
Hi On Tue, Dec 17, 2013 at 5:07 PM, Steven Stern wrote: ufraw-gimp-0.19.2-10.fc19.x86_64 requires cfitsio-3.340-1.fc19.x86_64 gnome-shell-extension-xrandr-indicator-3.8.4-1.fc19.noarch requires gnome-shell-extension-common-3.8.4-1.fc19.noarch Continue with the upgrade at your own risk. I think I'm going to put off a fedup to f20 for a while. These are not fedup issues but packages that don't have a good upgrade path. You can easily remove these packages and install them post-upgrade Rahul -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On 12/17/2013 12:52 PM, Chris Murphy wrote: Fedora doesn't magically get more stable. It's due to testing, bug reporting, and triaging those bugs, much of which is done by volunteers. The more testers, the better the coverage, the more bugs are found before release. The stability depends in large part on the community's contribution into finding and properly reporting bugs (reproduce instructions, attaching the proper logs, etc.) The community gets out of Fedora what's put into it. Obviously, and that's what beta-testers are for. My comment was about people who install the beta and don't understand what the term beta means. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
F20 on iMac: plymouthd runs, clearing screen unexpectedly
Dear Folks, I have installed Fedora 20 on an iMac alongside Mac OS 10.5.8, and it works fine, except for the grub2 bugs 903937, 893179, 904668, and most problematic, the unexpected appearance of plymouthd clearing the screen, and putting a fedora booting-up image in the middle of the screen. This happens with either XFCE or gnome shell, and occurs some time after logging in and doing some work. I can get rid of it by killing plymouthd. Any ideas on how to investigate the cause, and to troubleshoot this? -- Nick Urbanik http://nicku.org 808-71011 nick.urba...@optusnet.com.au GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24 I disclaim, therefore I am. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fwd: Version upgrade from Fedora 17 to Fedora 20
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/17/2013 12:05 PM, Lars Poulsen wrote: I have been gradually updating my Fedora servers from a variety of releases ranging to F14 to F18 to more current versions. In order to do these as in-place updates rather than re-installs (which saves many headaches) I have had to do this gradually. Most are now running F19 with one pioneer at F20. But one that started at F14 seems to be stuck at F17, since F17 has been archived, and thus I cannot do yum install fedup since the links in /etc/yum.fedora.repo are now invalid. What is the best workaround? I know that once I have fedup installed, I can go to F19 with a minimum of hassle (mostly the apache config file restructuring, but that machine does not run apache anyway). Bu thow do I get there? - can I find the F17 fedup rpm in archive.fedoraproject.org and just install it manually? - can I update the /etc/yum.fedora.repo file to point to the archived set? (Can you send me a working file?) Lars Poulsen Afar Communications Inc I just successfully installed fedup on an F17 box from the updates repo, so you may not have a problem. [updates] name=Fedora $releasever - $basearch - Updates failovermethod=priority #baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/ mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releaseverarch=$basearch enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEAREIAAYFAlKw6MgACgkQ5LO5Iacp/hG8zQCePob5lIBan2KcCRwobVYSt4QV 10wAn1Kh4INJJLE3RJ/p6J4iJOSkVTiM =aSGz -END PGP SIGNATURE- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: qmake
On Tue, 17 Dec 2013 13:23:47 -0600, Richard Shaw wrote: On Tue, Dec 17, 2013 at 1:14 PM, Patrick Dupre pdu...@gmx.com wrote: Hello, Is there a qmake package for fedora? I found stuff for windows but nothing for linux! # repoquery --whatprovides /usr/bin/qmake-qt4 qt-devel-1:4.8.4-19.fc19.i686 qt-devel-1:4.8.4-19.fc19.x86_64 qt-devel-1:4.8.5-10.fc19.x86_64 qt-devel-1:4.8.5-10.fc19.i686 It's kinda hard to find if one expects it not to be shipped with Qt and not even yum search all qmake finds it. Similarly, if one did yum search moc, one would not find Qt's moc (and package moc is something else), and with yum search qt moc one would find automoc only. Indeed the queries such as # repoquery --whatprovides /usr/bin/qmake\* are more fruitful in such a case. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On 17 December 2013 20:28, Chris Murphy li...@colorremedies.com wrote: On Dec 17, 2013, at 1:22 PM, Joe Zeff j...@zeff.us wrote: On 12/17/2013 11:57 AM, Bob Goodwin wrote: Joe, if I must justify my actions, and I question that, there's no big rush it's just another form of amusement for me. No, you don't need to justify your actions; if you find it amusing to be an early adopter and deal with all of the last-minute oopsies, that's all I need to know. My post was intended to explain why I prefer to wait, and ask why others rush in. Because it's fun to break things, and get irritated; irritation is motivation to fine causes, file bugs, and get things fixed. That's why I QA anyway. Oddly the reason I do the (small amount) of pre-release testing I do is pretty much exactly the opposite. -- imalone http://ibmalone.blogspot.co.uk -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Cron vs. Whenjobs vs. Goaljobs
On Tue, Dec 17, 2013 at 7:23 PM, Jonathan Ryshpan jonr...@pacbell.netwrote: I'm interested in a replacement for cron which would allow me to run various cron jobs on demand, and mark them as having been run, so they won't be run again from the schedule. Looking through the Fedora repository, I noticed whenjobs, which looks like it may do the job (no pun intended). The documentation for whenjobs says that it is obsolete and has been replaced by goaljobs. Has anyone tried out whenjobs or goaljobs. Any problems? Will they do what I need done? Is there some reason 'at' won't do what you want? poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora-20 beta -
On 17 December 2013 20:43, Joe Zeff j...@zeff.us wrote: On 12/17/2013 12:32 PM, Ian Malone wrote: People with the time, resources and inclination are more than welcome to run beta. And, as far as running beta goes, I have the time and the resources, but not the inclination. Yes, I was trying to find a list that wouldn't put people off, but does set out what's required: 1. 'Time' it's a limited resource and testing does take time. 2. 'Resources' is a bit vague, but for instance if you're running test installations it's helpful to have another computer to download things or look them up, or a good install USB to hand. Can also mean the necessary knowledge to deal with the thing to test. 3. 'Inclination' you need to have a reason for wanting to do it. Mine comes mainly from the fact I think it's easier to deal with things earlier than later, I don't want to suddenly discover a problem when it lands on me. I think this is actually an advantage of open source rather than a disadvantage, end users get to see what's coming up and what problems might affect them rather than getting a new release dumped on them. -- imalone http://ibmalone.blogspot.co.uk -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Libre office
On 12/12/2013 11:59 PM, Richard Vickery wrote: Is there someone to email to for a suggestion for improving Libre office? It would sure be nice if the program did a grammar check and made suggestions on how to improve one's document. I haven't used MS Word for as long as I've used Linux, and I really miss the grammar-check that it did. There is a mail list: us...@global.libreoffice.org This is their signature line: To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Unit dbus-org.freedesktop.ModemManager1.service failed to load
Running f20. I see lots of these messages: Dec 17 20:40:56 nbecker1 dbus-daemon: dbus[562]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus- org.freedesktop.ModemManager1.service failed to load: No such file or directory. Dec 17 20:40:56 nbecker1 dbus[562]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus- org.freedesktop.ModemManager1.service failed to load: No such file or directory. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
What hath Gnome wrought?
OK, X was working well on my Samsung TV because at some point they introduced a quirk that informed the world that the idiots at Samsung set the size of the TV to 160x90 just to get the aspect ratio right in the EDID info, so Xorg.0.log says things like this: [ 4.694] (II) Quirked EDID physical size to 0x0 cm then later the intel video driver arbitrarily does this: [ 4.695] (==) intel(0): DPI set to (96, 96) Now, in Fedora 20, the Gnomes are apparently going to some vast amount of trouble to ignore the X DPI, and dig up the low level EDID provided display size in order to utterly screw everything up and make the characters on my screen be about the size of baseballs. Curse all helpful software to the uttermost depths of hades! Anyone know how to get latest gnome to believe the DPI setting and not blow up 12pt fonts to gigantic proportions? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Unit dbus-org.freedesktop.ModemManager1.service failed to load
On Tue, 17 Dec 2013 20:44:44 -0500 Neal Becker ndbeck...@gmail.com wrote: Running f20. I see lots of these messages: Dec 17 20:40:56 nbecker1 dbus-daemon: dbus[562]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus- org.freedesktop.ModemManager1.service failed to load: No such file or directory. Dec 17 20:40:56 nbecker1 dbus[562]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus- org.freedesktop.ModemManager1.service failed to load: No such file or directory. https://fedoraproject.org/wiki/Common_F20_bugs#modemmanager-dbus-spam kevin signature.asc Description: PGP signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Fedup Failure
I tried upgrading from Fedora 19 to 20. When the System Upgrade task starts I get a failure around /run/initramfs (it moves fast). Then it boots back to Fedora 19. Any thoughts on how to debug? -- Mark Bidewell http://www.linkedin.com/in/markbidewell -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedup Failure
On 12/17/2013 06:34 PM, Mark Bidewell wrote: I tried upgrading from Fedora 19 to 20. When the System Upgrade task starts I get a failure around /run/initramfs (it moves fast). Then it boots back to Fedora 19. Any thoughts on how to debug? There are several threads on this at fedoraforum.org. One suggestion is to update fedup to version 0.8 and try again. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
issues with upgrade from f19 - f20
Hi, I did an upgrade from F19 to F20 on three machines (2 laptops and 1 desktop). For one laptop and the desktop, things went smoothly -- no complaints: I used yum/fedora-upgrade. For the other, while upgrading, the X crashed and there were comments about journald, bluetooth etc (not sure if this has anything to do with anything or the upgrade) and so I am left with a bunch of F19 and F20 packages. I am able to run as if nothing has happened (though unclear whether I am running a F19 or a F20 system) but this is really a system which can not be updated. I tried doing the following, for want of knowing what to do: %sudo yum --releasever=20 distro-sync and I get the following: Loaded plugins: fastestmirror, langpacks, remove-with-leaves Loading mirror speeds from cached hostfile * fedora: kdeforge.unl.edu * rpmfusion-free-rawhide: mirrors.tummy.com * rpmfusion-nonfree: rpmfusion.famillecollet.com * rpmfusion-nonfree-updates: rpmfusion.famillecollet.com * updates: mirror.unl.edu Resolving Dependencies -- Running transaction check --- Package SDL.x86_64 0:1.2.15-11.fc20 will be updated --- Package SDL.x86_64 0:1.2.15-12.fc19 will be updated --- Package SDL.x86_64 0:1.2.15-12.fc20 will be an update --- Package autocorr-en.noarch 1:4.1.3.2-10.fc20 will be a downgrade --- Package autocorr-en.noarch 1:4.1.3.2-12.fc19 will be erased --- Package bluez.x86_64 0:5.12-1.fc20 will be obsoleting --- Package createrepo.noarch 0:0.9.9-22.fc20 will be a downgrade --- Package createrepo.noarch 0:0.10-1.fc19 will be erased --- Package dbus.x86_64 1:1.6.12-1.fc20 will be a downgrade --- Package dbus.x86_64 1:1.6.12-2.fc19 will be erased --- Package dbus-libs.x86_64 1:1.6.12-1.fc20 will be a downgrade --- Package dbus-libs.x86_64 1:1.6.12-2.fc19 will be erased --- Package dbus-x11.x86_64 1:1.6.12-1.fc20 will be a downgrade --- Package dbus-x11.x86_64 1:1.6.12-2.fc19 will be erased --- Package faad2-libs.x86_64 1:2.7-2.fc17 will be a downgrade --- Package faad2-libs.x86_64 1:2.7-4.fc19 will be erased --- Package fedora-upgrade.noarch 0:20.2-1.fc19 will be updated --- Package fedora-upgrade.noarch 0:20.2-1.fc20 will be an update --- Package firefox.x86_64 0:26.0-2.fc19 will be updated --- Package firefox.x86_64 0:26.0-3.fc20 will be an update --- Package gnutls.x86_64 0:3.1.16-1.fc20 will be updated --- Package gnutls.x86_64 0:3.1.17-2.fc19 will be updated --- Package gnutls.x86_64 0:3.1.17-3.fc20 will be an update --- Package google-crosextra-caladea-fonts.noarch 0:1.002-0.1.20130214.fc20 will be a downgrade --- Package google-crosextra-caladea-fonts.noarch 0:1.002-0.2.20130214.fc19 will be erased --- Package libreoffice-opensymbol-fonts.noarch 1:4.1.3.2-10.fc20 will be a downgrade --- Package libreoffice-opensymbol-fonts.noarch 1:4.1.3.2-12.fc19 will be erased --- Package libreoffice-ure.x86_64 1:4.1.3.2-10.fc20 will be a downgrade --- Package libreoffice-ure.x86_64 1:4.1.3.2-12.fc19 will be erased --- Package libreport-filesystem.x86_64 0:2.1.9-1.fc20 will be updated --- Package libreport-filesystem.x86_64 0:2.1.10-1.fc19 will be updated --- Package libreport-filesystem.x86_64 0:2.1.10-1.fc20 will be an update --- Package mesa-libGLU.x86_64 0:9.0.0-3.fc20 will be a downgrade --- Package mesa-libGLU.x86_64 0:9.0.0-4.fc19 will be erased --- Package obex-data-server.x86_64 1:0.4.6-5.fc19 will be obsoleted --- Package opus.x86_64 0:1.0.3-2.fc20 will be updated --- Package opus.x86_64 0:1.1-1.fc19 will be updated --- Package opus.x86_64 0:1.1-1.fc20 will be an update --- Package python-urlgrabber.noarch 0:3.9.1-32.fc20 will be a downgrade --- Package python-urlgrabber.noarch 0:3.10-0.fc19 will be erased --- Package rpmconf.noarch 0:0.3.4-1.fc19 will be updated --- Package rpmconf.noarch 0:0.3.5-1.fc20 will be an update -- Processing Dependency: rpmconf-base for package: rpmconf-0.3.5-1.fc20.noarch --- Package satyr.x86_64 0:0.11-1.fc20 will be updated --- Package satyr.x86_64 0:0.12-1.fc19 will be updated --- Package satyr.x86_64 0:0.12-1.fc20 will be an update --- Package ssmtp.x86_64 0:2.64-9.fc20 will be a downgrade --- Package ssmtp.x86_64 0:2.64-10.fc19 will be erased --- Package usb_modeswitch-data.noarch 0:20130807-1.fc20 will be a downgrade --- Package usb_modeswitch-data.noarch 0:20131113-1.fc19 will be erased --- Package vim-common.x86_64 2:7.4.027-2.fc19 will be updated --- Package vim-common.x86_64 2:7.4.027-2.fc20 will be an update --- Package vim-enhanced.x86_64 2:7.4.027-2.fc19 will be updated --- Package vim-enhanced.x86_64 2:7.4.027-2.fc20 will be an update --- Package vim-filesystem.x86_64 2:7.4.027-2.fc19 will be updated --- Package vim-filesystem.x86_64 2:7.4.027-2.fc20 will be an update --- Package xorg-x11-drv-modesetting.x86_64 0:0.8.0-2.fc20 will be a downgrade --- Package xorg-x11-drv-modesetting.x86_64 0:0.8.0-3.fc19 will be erased --- Package xulrunner.x86_64 0:26.0-1.fc19 will be updated --- Package xulrunner.x86_64 0:26.0-2.fc20 will be an update --- Package youtube-dl.noarch
Re: how to (properly) shut down a fedora 20 virtual machine?
On Dec 17, 2013, at 1:46 PM, Chris Murphy li...@colorremedies.com wrote: [ 118.522477] PM: Syncing filesystems ... done. [ 118.986063] Freezing user space processes ... (elapsed 0.005 seconds) done. [ 119.045554] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 119.689884] PM: suspend of devices complete after 636.182 msecs [ 119.693836] PM: late suspend of devices complete after 0.193 msecs [ 119.702168] PM: noirq suspend of devices complete after 5.163 msecs [ 119.704754] ACPI: Preparing to enter system sleep state S3 [ 119.706818] PM: Saving platform NVS memory [ 119.708309] Disabling non-boot CPUs ... [ 119.711815] Unregister pv shared memory for cpu 1 [ 119.717559] Broke affinity for irq 1 [ 119.718393] Broke affinity for irq 9 [ 119.718393] Broke affinity for irq 14 [ 119.836051] smpboot: CPU 1 is now offline Yet another pmsuspend on GUI shut down request. That's supposed to be the behavior if the host is shutdown, but that's not what I'm doing. And virsh dompmwakeup doesn't work. # virsh dompmwakeup fedora20 Domain fedora20 successfully woken up Yet serial console remains unresponsive, until I disconnect and reconnect, and then I get: [ 253.170908] ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20130517/evevent-286) [ 253.171840] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20130517/evevent-286) [ 253.171840] ACPI Error: Could not disable RealTimeClock events (20130517/evxfevnt-266) [ 253.199507] ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20130517/evevent-286) [ 253.200441] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20130517/evevent-286) [ 253.200441] ACPI Error: Could not disable RealTimeClock events (20130517/evxfevnt-266) [ 253.223361] ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20130517/evevent-286) [ 253.224296] ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20130517/evevent-286) [ 253.224296] ACPI Error: Could not disable RealTimeClock events (20130517/evxfevnt-266) So I'd say the VM is confused. I'm not sure where the problem is. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: fedup to F20 failed
On 12/17/2013 10:04 PM, Steven Stern wrote: I made a DVD and ran fedup --device --network 20 Anyone else have a similar problem? I am not having your problem but a similiar one. Here on one system, after having run fedup on f19, when rebooting for upgrade, the upgrade system starts, but after a couple of minute suddenly seems to stop and reboots into the old (f19) kernel without the upgrade actually having been performed. Except that I am observing selinux alerts and systemd-journald warnings/error during the upgrade, I don't know the cause. I guess, I'll resort to a traditional yum upgrade. Ralf -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: fedup to F20 failed
On Dec 18, 2013, at 12:13 AM, Ralf Corsepius rc040...@freenet.de wrote: On 12/17/2013 10:04 PM, Steven Stern wrote: I made a DVD and ran fedup --device --network 20 Anyone else have a similar problem? I am not having your problem but a similiar one. Here on one system, after having run fedup on f19, when rebooting for upgrade, the upgrade system starts, but after a couple of minute suddenly seems to stop and reboots into the old (f19) kernel without the upgrade actually having been performed. Except that I am observing selinux alerts and systemd-journald warnings/error during the upgrade, I don't know the cause. I guess, I'll resort to a traditional yum upgrade. Update to fedup 0.8 yum update fedup --enablerepo=updates-testing This contains the details including renaming the folders so that files already downloaded with fedup 0.7 won't be redownloaded with fedup 0.8: https://lists.fedoraproject.org/pipermail/test-announce/2013-December/000842.html Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedup Failure
On Dec 17, 2013, at 7:47 PM, Joe Zeff j...@zeff.us wrote: On 12/17/2013 06:34 PM, Mark Bidewell wrote: I tried upgrading from Fedora 19 to 20. When the System Upgrade task starts I get a failure around /run/initramfs (it moves fast). Then it boots back to Fedora 19. Any thoughts on how to debug? There are several threads on this at fedoraforum.org. One suggestion is to update fedup to version 0.8 and try again. Detail version is here: https://lists.fedoraproject.org/pipermail/test-announce/2013-December/000842.html It includes renaming two folders so that files downloaded with 0.7 don't have to be redownloaded by 0.8. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Fwd: [Test-Announce] PSA: Use fedup 0.8 for upgrades to Fedora 20! (was Re: Should a working fedup in Fedora N's stable repository be a release criterion for N+1?)
-- Forwarded message -- From: Adam Williamson awill...@redhat.com Date: Wed, Dec 18, 2013 at 1:57 AM Subject: [Test-Announce] PSA: Use fedup 0.8 for upgrades to Fedora 20! (was Re: Should a working fedup in Fedora N's stable repository be a release criterion for N+1?) To: test-annou...@lists.fedoraproject.org, users@lists.fedoraproject.org On Tue, 2013-12-17 at 21:47 -0800, Adam Williamson wrote: On Tue, 2013-12-17 at 15:16 -0800, Andrew Lutomirski wrote: I have a tendency to upgrade to a new Fedora release as soon as it's final, and I sometimes upgrade even sooner. ISTM that the official upgrade process is almost always broken, often for known reasons. Should one of the criteria for releasing Fedora N+1 be that a fully-updated Fedora N must be able to successfully complete 'fedup' or whatever the current preferred upgrade program is? (FWIW, the current bug is particularly nasty -- fedup 0.7.0 apparently can't actually update anything, and the sequence: - Install fedup 0.7.0 - Try it and watch it fail or hang - Update to fedup 0.8.0 from updates-testing - Run fedup ends up downloading all rpms *twice* a sucking up a correspondingly immense amount of disk space. Um, I'm fairly sure it doesn't. It only re-downloads stuff that's different from the previous run. We did test upgrades to F20 with 0.7, and they did work in testing, and quite a lot of people reported success with fedup in the last two weeks when at least some of them likely used 0.7. You have to bear in mind it's release day today, and there's always weirdness on release day, and people who have success generally don't report it while those who hit failure almost always do. I've been advising people to upgrade to 0.8 and retry just as a kind of generic piece of advice; for many of them, it'd probably work if they just retried with 0.7. 0.8 does fix several bugs compared to 0.7, but 0.7 wasn't entirely broken. Eh, that'll teach me to talk before thoroughly testing: these words are delicious! Om nom nom. I just poked it a bit and it sure seems like upgrades with fedup 0.7 to F20 are busted. They definitely worked when we tested shortly before release, though. I can only think that using fedup 0.7 against upgrade kernel/image built with fedup-dracut 0.8 doesn't work. FranciscoD also points out that the location of files downloaded by fedup changed between 0.7 and 0.8, so if you do a run with 0.7 then try with 0.8, it'll re-download all the updates, which is a waste of space and bandwidth. So, here's the news: do your upgrades to F20 with fedup 0.8, yo. It's in updates-testing for F18 and F19 at present, but will go to stable for F19 tomorrow. If you're upgrading from F18, you'll need to pass '--nogpgcheck' to fedup, because of https://bugzilla.redhat.com/show_bug.cgi?id=1040689 . If you did an unsuccessful run with fedup 0.7, then you can do: mv /var/tmp/fedora-upgrade /var/tmp/system-upgrade mv /var/lib/fedora-upgrade /var/lib/system-upgrade before running fedup 0.8, to save it downloading all the packages again, and make sure it cleans up nicely when it's done. I've just tested this, and it works. If you've already done an unsuccessful run with fedup 0.7 and then a successful run with 0.8, you may have files from the 0.7 run hanging around in /var/lib/fedora-upgrade and /var/tmp/fedora-upgrade. It is entirely safe and, indeed, advised to rm -rf these directories. Sorry for the mess, folks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
