Re: F37 Beta Cannot Install KODI
On 9/26/22 9:38 AM, stan via test wrote: I don't use kodi, but I think that in this case the fedora firewalld should have precedence. Thus, I would suggest you open a bug against kodi at rpmfusion. Please don't. This was already done and closed. https://bugzilla.rpmfusion.org/show_bug.cgi?id=6405 The correct bug report has now been opened. https://bugzilla.redhat.com/show_bug.cgi?id=2129946 ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F37 Beta Cannot Install KODI
On 9/23/22 3:46 PM, Earnest Henderson wrote: Apparently that has not made it into Fedora 37 yet? Upstream has removed it, but they have also not released a new version that includes the change. The Fedora firewalld package maintainer needs to either remove the file or apply the patch that removes the file in the mean time. I have requested that from the package maintainer. https://bugzilla.redhat.com/show_bug.cgi?id=2129946 Thanks, Michael ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Warning: gnome evolution drop old TLS protocol and you get "Error performing TLS handshake: A packet with illegal or unsupported version was received."
On 4/7/20 12:30 PM, Dario Lesca wrote: I use Fedora 32 ... and the TLS 1.0/1.1 are already disabled by default Please file a bug. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Warning: gnome evolution drop old TLS protocol and you get "Error performing TLS handshake: A packet with illegal or unsupported version was received."
On 4/7/20 11:28 AM, Dario Lesca wrote: On evolution ML Milan say that: the protocols are disabled system-wide. Read (and edit) the /etc/crypto-policies/config file to change the settings. I do not know whether it has any user- level setting, apart of the environment variable you found. Someone know how to configure this file for change the default system-wide ? Since you are posting to the test list I am assuming you are using Fedora Rawhide (33). You would be affected by the upcoming Change[1] that disables TLS 1.0/1.1 by default. Instead of looking for ways to enable TLS 1.0/1.1 you should engage with your provider to offer TLS 1.2 or 1.3. [1] https://fedoraproject.org/wiki/Changes/StrongCryptoSettings2 ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Call for testers: lzo update
Hello, The following update needs some karma so it can be released sooner than 12 days from now. https://bodhi.fedoraproject.org/updates/FEDORA-2020-25291e492f The lzo package was updated last month from 2.08 (dated 2014) to 2.10 (dated 2017). Part of the code in the new version is not properly written to work with gcc aliasing and the resulting binary does not work. I've applied a workaround (disabling gcc strict aliasing) until the maintainer or upstream fixes it. Bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1807737 Thanks, Michael ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: How to approve a review request ?
On 11/15/19 12:05 AM, J. Scheurich wrote: I want to approve the review request of vimvi-qt https://bugzilla.redhat.com/show_bug.cgi?id=1770278 but i can't find the right page to do that. Can someone help me ? https://fedoraproject.org/wiki/Package_Review_Process ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: btrfs
On 8/28/19 3:13 PM, pmkel...@frontier.com wrote: I've probably misunderstood some of this. Please feel free to let me know where my mistakes are. The btrfs filesystem has been in development for years. It entered into the kernel in 2009. Red Hat even had an engineer working on it, but he left to go work at other large tech firms. Red Hat has not replaced him. As far as the technical side of things btrfs sounds better, but in reality it still has teething issues. I've been bit by data loss by it and haven't used it since. There are other, more interesting filesystems that should be given attention to instead. The f2fs file system comes to mind. At the end of the day any of the top choices (ext4, xfs, f2fs, btrfs) are indistinguishable for desktop users with the advent of SSD / NVME drives. Pick a widely supported one (ext4, xfs) and forget about it. Anyways, welcome to Fedora. Large discussion threads are a once a quarter type of adventure so do not feel too overwhelmed. Regards, Michael ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Call for Deluge 2.0 testing
Hi all, Deluge[1] has just reached a major milestone in releasing version 2.0 with Python 3 support. I have pushed the 2.0.3 update (previous version being 1.3.15) to Fedora Rawhide. In my light testing everything appears to be working, but I would like more eyes on it. https://koji.fedoraproject.org/koji/buildinfo?buildID=1307635 Please either grab the update in the next compose or pull the packages from Koji. You may leave feedback in this thread or in Bugzilla. FYI, I have seen a few bugs reported by other users so far so a 2.0.4 update is possible soon. One reported issue is the loss of all seeding info for 1.3.x torrents, but in my upgrade I did not see any data loss. Thank you, Michael [1] https://deluge-torrent.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: proposal: drop optical media from release criteria
On 9/20/18 3:23 PM, pmkel...@frontier.com wrote: We buy used, manufacturer refurbished PCs for the most part to keep costs down. They are generally 5 years old when purchased and they get used for another 5 or more years. They run Fedora and the applications we use just fine. So now it sounds like your telling me I need to buy newer PCs. What age limit do you propose for PCs before Fedora will no longer support them? Use PXE. I bet your systems support it. Setup Cobbler and never touch physical media again. Oh I forgot to add in my prior replies on this subject that we used DVDs for long term backups too. Yikes. I would suggest you invest in other options. Thumb drives, especially the low cost ones, have not demonstrated good enough characteristics, to be good candidates for long term back ups. ESD is a particularly important issue in that regard. I'm not sure what FUD you've read to believe that, but flash drives from reputable brands are very hard and last more than a few times writing to them. It's time to move on. Technology eventually advances. You have options. There is no doomsday scenario here. :) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Security problem with firefox-57.0-0.8.fc26.x86_64
On 10/31/2017 04:17 AM, Joachim Backes wrote: I'm having a problem with thw wikipedia.de website: If I try to open it, I get some warning issue: - Your connection is not secure The website tried to negotiate an inadequate level of security. wiki2.wikimedia.de uses security technology that is outdated and vulnerable to attack. An attacker could easily reveal information which you thought to be safe. The website administrator will need to fix the server first before you can visit the site. Error code: NS_ERROR_NET_INADEQUATE_SECURITY - Anybody sees this too for the German wikipedia website wikipedia.de? The site uses RC4 in its cipher offering. https://www.ssllabs.com/ssltest/analyze.html?d=wiki2.wikimedia.de=46.252.27.114 You should contact the site admin for the German wikipedia site and get them to remove the RC4 cipher. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Strange situation with Wine on Fedora 27
On 07/12/2017 10:39 AM, Michael Schwendt wrote: Installing wine.x86_64 pulls in dozens of i686 packages by default through implicit or explicit dependencies. Working as intended or else my inbox would be swamped with "I can't start app $XYZ!" ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Strange situation with Wine on Fedora 27
On 07/12/2017 05:12 AM, Michael Schwendt wrote: The x86_64 and i686 build of a package are published at the same time. If you get a conflict like this, where the version of the two packages is not the same, you need to examine your installation and the repository contents to figure out why you don't get the very latest version for both the x86_64 and i686 packages. It could be due to broken dependencies somewhere or due to duplicate installed packages. IMO, we need to stop allowing arch to be specified in dnf by default. Users think they need to add them and get into constant trouble by it. I've closed a handful of bugs against Wine for this reason. A command argument could be added to dnf to allow an arch to be specified. dnf --enablearchtagbecauseiknowwhatimdoing foo.i686 Yes, I'm being extreme, but it is a pain point for users and to put it bluntly their ignorance gets them into trouble. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: missing thunderbird-lightning in f24
On 05/05/2016 11:55 AM, Joachim Backes wrote: But with the installed thunderbird, I get no lightning functionality, only with installing the addon lightning-4.7-sm+tb-linunx.xpi (I think, starting with thunderbird-45.0-4.fc24). With previous F24 TB versions, no flaw! The way they designed the "bundling" makes it only show up for new Thunderbird profiles. Thunderbird copies the extension into your profile on new profiles. Since you have an existing profile you can must install it from the website. Either way you get the same addon. I forgot that uninstalling it makes it really go away so you don't need to uninstall. -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: missing thunderbird-lightning in f24
On 05/05/2016 10:24 AM, Joachim Backes wrote: Anybody sees this too: no more thunderbird-lightning for f24, I have to install the xpi file from the thunderbird extension download site (as in earlier times)! The Lightning extension is shipped with Thunderbird itself. It has been since Thunderbird version 38, which was about a year ago. You may uninstall your local copy and use the built-in copy. Regards, Michael -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Fedora 21 updates-testing report
On 10/19/2015 12:20 AM, upda...@fedoraproject.org wrote: The following Fedora 21 Security updates need testing: Could we remove these notices? It's been obvious for years that no one cares about them. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F23 on PATA or SATA ext. disk?
On 08/06/2015 02:13 PM, Joerg Lechner wrote: Hi, thank You for the advices. I will buy another Pata disk by ebay and then start testing F23. Kind Regards Please don't. Please test with SATA or newer hardware. External or internal. If you don't have a SATA external enclosure then also pick one of those up. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel 4.0.2+ ext4 corruption
On 05/20/2015 05:22 AM, Matthew Miller wrote: Michael, are you able to reproduce this reliably, by any chance, so we have a test case for any potential fix? I upgraded to 4.0.4 from a 4.0.0 build I was running. Initially everything seemed fine. The corruption occurred several hours later after I started an update run and during the run ldconfig was spitting out bad ELF errors. I corrected those that were reported, but upon a reboot it had corrupted even more files and the system was no longer bootable due to corruption to libXfont and a few other libraries. I was able to salvage the system after downgrading to 4.0.1 and re-installing rpm, yum, and a couple dozen other packages. The problem may only be related to 4.0.2 and mdadm RAID. I won't have time right this minute, but if no one else can easily reproduce it I will setup a VM with two drives and see if that's enough. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
kernel 4.0.2+ ext4 corruption
Hi testers, Beware: Kernel 4.0.2 and up have an ext4 corruption bug that has not yet been fixed. I was just hit by it on my RAID0 SSD setup on a laptop. http://news.softpedia.com/news/Linux-Kernel-Plagued-by-an-EXT4-Data-Corruption-Issue-481699.shtml Regards, Michael -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [ASUS] Laptop issue with hotkeys
On 05/10/2015 03:27 AM, Luya Tshimbalanga wrote: The problem is mostly related to ASUS laptop. i would like if any user have their hotkeys work out of box. Mine somehow refuses to work even though the drivers correctly detected it as asus-nb-wmi. See https://bugzilla.redhat.com/show_bug.cgi?id=1206862 Try adding acpi_osi= to your kernel boot command arguments. Example: linuxefi /vmlinuz-foo ... acpi_osi= -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: AKmods not properly building with rc4 kenel
On 04/15/2015 06:48 AM, Justyn Temme wrote: Running on 2014MBA with braodcom wifi chipset. When trying to build akmods it freaks out halfway through. will post a bug report when i have time. RPMFusion package bugs need to be reported to the RPMFusion package maintainer[1] or RPMFusion mailing list[2]. This is the Fedora (rawhide) mailing list. Thanks, Michael [1] https://bugzilla.rpmfusion.org/ [2] http://lists.rpmfusion.org/mailman/listinfo/rpmfusion-users -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
On 04/08/2015 09:31 AM, Russel Winder wrote: My Lenovo X1 has the 2560 x 1440 screen. When running Debian Sid/GNOME, the displays settings dialogue shows all the possible resolutions with the 16:10, 16:9, 5:4 and 4:3 aspect rations. When running Fedora Rawhide/GNOME the same dialogue shows only the native resolution and 4:3 aspect ration resolutions. As far as I am aware this is both of them out of the box in that I have not knowingly fiddled with anything. Is this to be expected (I hope not as I want 16:9 and 16:10 resolutions available), or have I failed to do something during Fedora Rawhide/GNOME setup that has led to this? I see the same problem with my ASUS ultrabook that has the same resolution screen. I haven't debugged it but either the i915 module (kernel) or Xorg driver is not providing the correct modes. This issue has been around for a while. You won't want 16:10 modes as 2560x1440 is a 16:9 resolution. Please open a bug report. I'll CC on it. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Silly bodhi karma games
On 03/19/2015 04:14 PM, Michael Schwendt wrote: And obviously, for those packagers who don't mind the timeout, Bodhi could improve and offer an option to push an update to stable automatically after the timeout. Or after a customizable timeout, so e.g. the maintainer could request 21 days instead of 7 days. Meanwhile, a sufficient number of karma changes could still speed up the release or veto it, too. +1 The updates-testing email has plenty of proof that maintainers dump updates and forget about them. EOL comes around and bug fix / security fixes that were sitting in testing for 100+ days are left to die. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 22 updates-testing report
On 03/05/2015 01:25 PM, Chuck Forsberg WA7KGX wrote: Wine still can not load any windows programs I tried, including: caf omen 1110776 Jun 20 2012 LadyHeather310.exe Known issue. https://bugzilla.redhat.com/show_bug.cgi?id=1192725 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Mounting XFS with discard option only works for /boot but not /
On 11/23/2014 05:23 PM, Chris Murphy wrote: What's odd is that I'm certain discard worked for root on Btrfs, so I wonder if this remount limitation is XFS only or if it applies to any filesystem? In which case, how is anyone getting trim to work on the root device? Limitation of xfs only. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 updates-testing report
On 11/10/2014 12:54 AM, upda...@fedoraproject.org wrote: 86https://admin.fedoraproject.org/updates/FEDORA-2014-9474/pipelight-0.2.7.3-3.fc20 Could someone remove this from testing? The package has been removed from Fedora. There is also an F19 build. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: ?howto?: find needed package in not configured repository - intel video driver
On 10/16/2014 01:52 PM, Felix Miata wrote: This is even more confusing, since I thought I made explicit that the upstream fix is in git3.0.0, not 2.99.9##. There is no 3.0.0 yet. Anyone versioning it that way is wrong. -- 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: Mozilla Firefox
poma wrote: xulrunner i686 29.0-1.fc21rawhide 25 M Protip: You can remove xulrunner from your system now. Firefox no longer requires the standalone package. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: golang-godoc dependencies broken on f19
Dennis Jacobfeuerborn wrote: Hi Dennis, First off I'll have to point out that this is a test list for Fedora Rawhide and not Fedora 19 (a stable release). Point your e-mail client to us...@lists.fedoraproject.org in the future. Any ideas where to get godoc from? You have encountered a packaging bug. Please file a bug against golang so that the maintainer can fix it. They need to add a Provides line in the golang RPM spec so that your yum command will work correctly. https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: '10 Years of Fedora' t-shirt
On 01/10/2014 07:05 PM, Adam Williamson wrote: There is a project currently underway to distribute a commemorative t-shirt for Fedora's 10th anniversary to significant contributors: https://fedoraproject.org/wiki/F20_anniversary_tshirt My shirt arrived yesterday. Thanks! I know your list is QA, but I checked the wiki page and see that a major MinGW contributor is missing - Erik van Pienbroek. Could you pass along word to get him on a list? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 18 updates-testing report
Adam Williamson wrote: The submitter has just submitted it for stable, so it should make it on the next push. Thanks, Adam. People are usually responsive to my e-mails and the ball starts rolling. Wireshark is the last update that needs attention. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 18 updates-testing report
upda...@fedoraproject.org wrote: The following Fedora 18 Security updates need testing: Age URL 241 https://admin.fedoraproject.org/updates/FEDORA-2013-6117/eucalyptus-3.2.2-1.fc18 88 https://admin.fedoraproject.org/updates/FEDORA-2013-17195/spice-gtk-0.18-3.fc18 82 https://admin.fedoraproject.org/updates/FEDORA-2013-17635/wireshark-1.10.2-4.fc18 80 https://admin.fedoraproject.org/updates/FEDORA-2013-17853/davfs2-1.4.7-3.fc18 Just a friendly reminder that these updates are still waiting for Fedora 18, which will be EOL soon. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Is yum groups broken in f20 ?
Adam Pribyl wrote: There is much more problems with groups in bugzilla, it affects F19 too. You can fix this by using yum mark remove group on all groups you get a warning they are missing (you have to have the latest yum - so yum update yum). You don't need to bother with this. If you read the bug link you'll find an easier solution. rm -rf /var/lib/yum/groups -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Is yum groups broken in f20 ?
Adam Pribyl wrote: What happens if yum downloads again the groups info? BTW: I only have two 4bytes long file in this directory, and have the same problem. The files in the directory are created by yum and are not downloaded from a repository. Removing the files will stop yum from using the group marking code that we're seeing these warnings from. I'm not sure why some systems have these files and some do not, which is what needs more investigation, but removing them will not have any negative side effects. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Is yum groups broken in f20 ?
On 12/08/2013 08:37 AM, Mateusz Marzantowicz wrote: Curious, why it blew up right now, just before F20 is released. It should have happened in alpha and not now. Workaround is to yum group mark remove group name here for every group on the list. What a waste of time. Whatever you do - do not run yum group mark convert. Now one of my systems wants to install every Fedora package with yum update. This affects all Fedoras with yum -120. Here's the parent bug: https://bugzilla.redhat.com/show_bug.cgi?id=1014202 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Package not fedup'd
Adam Williamson wrote: Well, F20 is frozen, so so they may have built and submitted an update but it can't go stable because of the freeze... I checked Bodhi before sending my email. There was no update submitted, but there is one now thanks to Ed's bug report. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 20 Final Test Compose 5 (TC5) Available Now!
On 12/05/2013 03:30 PM, Andre Robatino wrote: NOTE: The 64-bit Desktop Live is over its size limit. As per the Fedora 20 schedule [1], Fedora 20 Final Test Compose 5 (TC5) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/5808#comment:13 . Please see the following pages for download links (including delta ISOs) and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace dl with download-ib01 in the download URL. The installer art contains the Fedora 17 mascot. http://i.imgur.com/vKLioXB.png Otherwise, installation and general usage work without a problem including 3D acceleration in VBox. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Package not fedup'd
Ed Greshko wrote: Never mind. Eyes going bad. Just noticed the version of apper in current f18 is greater than apper in f20. This is a bug that the maintainer needs to fix by pushing an F20 update. Can you file a bug for this? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 packages on F20
Mateusz Marzantowicz wrote: atlas.x86_64 3.8.4-8.fc19 @fedora The package maintainer has not pushed any Fedora 20 updates. Please file a bug against this package requesting an F20 update so that upgrades work properly. I see he has pushed a F19 update today but with no matching F20 update. gstreamer-plugins-espeak.x86_640.4.0-2.fc19 @fedora This package FTBFS. A bug has been created for this. https://bugzilla.redhat.com/show_bug.cgi?id=992441 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 32bit guest on 64bit host, should it work?
Eric Blake wrote: No support for running a 64-bit guest on a 32-bit host (hardware just doesn't expose enough memory). Your competitors software supports this configuration as long as virtualization extensions are available on the host CPU. Not that I'm requesting it, but a little FYI for Chris (as you probably know this). -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: The bodhi nss bundle to rebase to nss-3.15.2 could use some karma
Elio Maldonado wrote: https://admin.fedoraproject.org/updates/FEDORA-2013-18382/nss-3.15.2-1.fc19,nss-util-3.15.2-1.fc19,nss-softokn-3.15.2-1.fc19,nspr-4.10.1-1.fc19 Thank you in advance, Thanks for sending out the email and fixing this problem. Karma left! Michael -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Intel SRT,
Chris Murphy wrote: Does anyone know the prevalence of computers shipping with Intel Smart Response Technology (binds SSD and HDD, using SSD as a cache) enabled? And should there be an RFE for anaconda to identify such configurations? The computers I have seen with ISRT have it disabled by default. I'd recommend posting to the linux-raid list or anaconda list to see who needs to do what. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Nvidia installation problems
On 08/02/2013 05:31 PM, Sandro Mani wrote: This is not really the right list for the issue, but I suggest you consulted the log file as indicated. Problem might be as simple as not having kernel-headers or gcc installed. The problem is that the NVIDIA binary driver does not currently support the kernel 3.10.x series. ... and yes, this is not the correct list to ask this question. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 17 updates-testing report
On 07/06/2013 08:41 PM, upda...@fedoraproject.org wrote: The following Fedora 17 Security updates need testing: Age URL 366https://admin.fedoraproject.org/updates/FEDORA-2012-10269/revelation-0.4.14-1.fc17 178https://admin.fedoraproject.org/updates/FEDORA-2013-0455/fedora-business-cards-1-0.1.beta1.fc17 106https://admin.fedoraproject.org/updates/FEDORA-2013-4234/stunnel-4.55-1.fc17 101https://admin.fedoraproject.org/updates/FEDORA-2013-4501/libxslt-1.1.28-1.fc17 98https://admin.fedoraproject.org/updates/FEDORA-2013-4581/libuser-0.57.6-2.fc17 31https://admin.fedoraproject.org/updates/FEDORA-2013-10121/subversion-1.7.10-1.fc17 20https://admin.fedoraproject.org/updates/FEDORA-2013-10940/tomcat6-6.0.37-1.fc17 15https://admin.fedoraproject.org/updates/FEDORA-2013-11397/python-bugzilla-0.9.0-1.fc17 12https://admin.fedoraproject.org/updates/FEDORA-2013-11568/curl-7.24.0-10.fc17 The following Fedora 17 Critical Path updates have yet to be approved: Age URL 318https://admin.fedoraproject.org/updates/FEDORA-2012-12509/PackageKit-0.7.6-1.fc17 126https://admin.fedoraproject.org/updates/FEDORA-2013-3304/libvpx-1.2.0-1.fc17 12https://admin.fedoraproject.org/updates/FEDORA-2013-11568/curl-7.24.0-10.fc17 F17 is EOL soon. 12 updates that will miss being pushed. Perhaps Bodhi needs a warning sent to maintainers about EOL. The bugzilla message doesn't motivate maintainers. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Bug 499836: It's back
On 06/22/2013 11:05 AM, Chuck Forsberg WA7KGX wrote: The p8z77-vle plus BIOS does not seem to have a problem with this keyboard. Once Fedora finishes booting the keyboard is recognized. The grub2 boot however does not read keyboard presses, preventing selection of anything but the latest Fedora installation. Are you using UEFI mode or BIOS mode? If UEFI, make sure that USB initialization for keyboards is enabled. ASUS calls this partial USB initialization. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gnome-shell cpu usage during installation
On 06/18/2013 01:27 PM, Chris Murphy wrote: With the system installed, dragging e.g. a Firefox window, around the screen approximates the same behavior. gnome-shell is pegged. This doesn't seem right. The system I am typing from has the NVIDIA binary driver and experiences the same pegged behavior. Gnome Shell has always worked this way. But this is what profilers are for. OK? You are free to profile gnome-shell and see exactly why so much CPU is used to move a window around. Maybe you could provide a patch to Gnome to reduce it. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 18 updates-testing report
On 05/29/2013 10:11 PM, upda...@fedoraproject.org wrote: mesa-9.2-0.7.20130528.fc18 (FEDORA-2013-9611) Mesa graphics libraries Update Information: Massive graphics update for F18, including: - Mesa resync with F19 (GL 3, vdpau drivers, etc) [snip] - Enable hardware floating-point texture support Hurrah... pigs are flying. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: p7zip-plugins and rar extraction.
On 04/27/2013 04:36 PM, Igor Gnatenko wrote: Can you show me? $ rpm -qa unrar Igor, The point of the file-roller update is to not require the non-free RAR binary. The unrar package should no longer be required. The unar package takes its place. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: my impressions of F19A, from Radeon testing day
On 04/25/2013 11:51 PM, DJ Delorie wrote: I did hit Esc, it didn't work. You want the Enter key. :) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 alpha and VirtualBox
On 04/17/2013 10:50 PM, Ed Greshko wrote: FWIW, I didn't do any debugging. I did experience slowness but my goal was to install since my DVD download got corrupted (my fault). Once installed and Guest Additions installed all works fine. I cannot run any application, including anaconda. Perhaps if I let it sit overnight anaconda might display, but then I'd have to wait a week for it to install at this pace. I managed to get SSH running by starting in 3 and then switching to 5. The process doing all the nothing is the loop device. The host system is reporting very small I/O through iotop. Roughly 200kbyte/sec reads of the ISO file every couple of seconds. I have tried switching the CD device from IDE to SATA to no avail. I have no issues with my Fedora 18 or Windows VMs. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 alpha and VirtualBox
On 04/18/2013 01:49 AM, Michael Cronenworth wrote: I cannot run any application, including anaconda. Perhaps if I let it sit overnight anaconda might display, but then I'd have to wait a week for it to install at this pace. I managed to get SSH running by starting in 3 and then switching to 5. The process doing all the nothing is the loop device. The host system is reporting very small I/O through iotop. Roughly 200kbyte/sec reads of the ISO file every couple of seconds. I have tried switching the CD device from IDE to SATA to no avail. The problem is RAM. I allocated 1 GB of RAM as my usual amount for any new VM. This works until X is started then it is bumping the 1GB limit. Any new app that is started is being OOM killed. Just sitting at a Gnome desktop consumes 950MB. I'm not happy about this increase in usage, but I'll save the complaining for another thread. After bumping the RAM to 2GB I can get things rolling. The VM is still very slow, but the UI responds within about a minute after clicking on widgets. Anaconda is using about 500MB by itself, so 2GB may not be enough if this trend continues. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 alpha and VirtualBox
On 04/18/2013 08:07 AM, Sérgio Basto wrote: Are using vbox from rpmfusion ? Please see my previous email: http://lists.fedoraproject.org/pipermail/test/2013-April/114890.html In answer to your question: No, I am using the official package. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 alpha and VirtualBox
On 04/18/2013 12:29 PM, Chuck Forsberg WA7KGX N2469R wrote: What is the official version and how does it differ from the Rpmfusion version? https://www.virtualbox.org/wiki/Linux_Downloads It doesn't differ from the RPMFusion version. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 19 Alpha Release Candidate 4 (RC4) Available Now!
On 04/18/2013 06:59 PM, Adam Williamson wrote: For the tenth time this week :), debug kernel. Try a nodebug kernel, or 'slub_debug=-'. It helps when running the installer as well as on installed systems. When you want the mass public to test the image you produced, it doesn't help when it is as slow as Christmas. You will have to eat the fruit you produce and learn to like it. :) Or post disclaimers that Alphas now use a slow, debug kernel and has high memory requirements. I believe F18 was the first to have a debug kernel/high RAM, correct? That's 17 previous releases that people were used to a normal speed system to test with. Expect bitching. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 19 Alpha Release Candidate 4 (RC4) Available Now!
On 04/18/2013 08:20 PM, Adam Williamson wrote: No, they've had debug kernels for ages, but debug kernels got quite a lot slower with the 2.6.40 release (IIRC). Before that the difference wasn't so great. Ah, time has flown. It seems just yesterday I read the discussions about when to enable/ship debug kernels. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F19 alpha and VirtualBox
Is there a trick to getting F19 and VirtualBox to play nice? Host: Fedora 18 x86_64 VBox 4.2.12 3ghz quad core When I load the latest F19 Alpha LiveCD ISO it takes about 5 minutes just to get to the desktop. Once there, the CD access never stops, and a CPU core is always 100%. My clicks take about 30 seconds to register. I got ALT-F2 to pop-up to enter a command, but typing in gnome-terminal and waiting 5 minutes didn't result in anything. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F19 alpha and VirtualBox
On 04/17/2013 09:31 PM, Adam Williamson wrote: Try 4.2.10. I saw someone somewhere mention that 4.2.12 was crazy slow but 4.2.10 worked fine. Same behavior with 4.2.10. I can boot into the console (3 on kernel cmdline) and CD access stops and nothing uses any CPU. It seems X related, but I cannot open any programs to debug it. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup network download
On 03/19/2013 05:30 PM, Michael Cronenworth wrote: Which component should I file the bug against? Fedup? Bug created: https://bugzilla.redhat.com/show_bug.cgi?id=923807 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Missing python-imaging
On 03/18/2013 11:18 AM, Chuck Forsberg WA7KGX N2469R wrote: Python-imaging seems to be missing from Fedora 19 and rawhide. Pillow is installed but WSPR won't run because it can't import the stuff that used to be in python-imaging. Chuck, You will find it helpful to read the FeatureList wiki page[1] when you are testing Fedora N+1 or Rawhide releases. The relevant page regarding your issue is here: http://fedoraproject.org/wiki/Features/Pillow Michael [1] http://fedoraproject.org/wiki/FeatureList -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 18 updates-testing report
On 03/10/2013 08:27 PM, upda...@fedoraproject.org wrote: The following Fedora 18 Security updates need testing: Age URL 121https://admin.fedoraproject.org/updates/FEDORA-2012-17834/cumin-0.1.5522-4.fc18 61https://admin.fedoraproject.org/updates/FEDORA-2013-0416/fedora-business-cards-1-0.1.beta1.fc18 30https://admin.fedoraproject.org/updates/FEDORA-2013-2131/rubygem-rdoc-3.12-6.fc18 26https://admin.fedoraproject.org/updates/FEDORA-2013-2306/rubygem-rack-1.4.0-5.fc18 Maintainers: Did you forget about your updates? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Mesa 9.0.3 update
Adam Jackson wrote: The smiley does not make this less condescending. We will be updating Mesa aggressively. I said as much on the phone to Valve last week. I asked this on the legal list but did not receive a response. What's the status of enabling the floating-point features in Mesa? It prevents OpenGL 3+ from being advertised. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: rawhide report: 20130304 changes
On 03/04/2013 08:42 AM, Fedora Rawhide Report wrote: [mediawiki119-HTTP302Found] mediawiki119-HTTP302Found-2.0.1-3.fc19.noarch requires mediawiki119 [mediawiki119-RSS] mediawiki119-RSS-2.16-4.fc19.noarch requires mediawiki119 [mediawiki119-intersection] mediawiki119-intersection-37906-3.fc19.noarch requires mediawiki119 Since mediawiki119 was blocked these need to be blocked, too. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18 beta experience under VM
Michael Cronenworth wrote: https://bugzilla.redhat.com/show_bug.cgi?id=883182 I wasn't sure on the component. Feel free to correct. Thanks! Apparently lorax was incorrect. Does anyone have any input on what component this should be filed against? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18 beta experience under VM
Chris Murphy wrote: I'm not understanding the problem in the bug. The Date/Time setting is required by anaconda before package installation may begin. I wanted to make this an optional setting. In order for it to be optional the date/time must be set to something reasonable from a trusted source. Chronyd should, and as far as I know does, update both the system clock and hardware clock once (on startup), when it has internet access to get a time sync from a server. If chronyd doesn't have network access, then simply it's up to the user to set the date/time. If there isn't a trusted time source, the hardware clock shouldn't be touched by software via assumption. If there is no network access, then yes, the hardware clock doesn't have to be modified. If the user's BIOS is set to 1/1/1970 some package install features may not work. We should be able to use a burned in date/time in the ISO as a trusted source if there is no network access. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18: when closing the lid, pm/sleep.d hooks not being run
Michal Jaegermann wrote: You are not authorized to access bug #690713. Well, that does not help very much unless you happen to be authorized. I can see the bug just fine. Have you tried logging in? Maybe you are banned? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
fedup network download
I have a few boxes that use a local repository that is rsync'd for both fedora and updates. When I tried out fedup --network the tool showed the names of my local repos. However, when it started package downloads I noticed the speed to be 100k to 500k per second range. This would indicate that fedup is downloading from an Internet mirror (6mbit Internet) instead of my local mirror (gigabit network). I found, through ss, that fedup is indeed connected to an FTP server on the Internet (ftp-chi.osuosl.org). Is fedup hardcoded to use the default fedora and updates repos even if they are disabled? Thanks, Michael -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18 beta experience under VM
On 12/03/2012 01:19 AM, Adam Williamson wrote: That's an equally confusing bug report.:) Could you please state precisely what steps you took and what results you saw? This is more useful and reliable than just saying what you think happened, because part of the agreed-upon problem here is that not everyone is clear on exactly what is actually happening in custom part. -I checked I don't need help; let me customize disk partitioning. -Clicked on Reclaim space button. -Clicked on plus button on existing F18 installation. -Clicked on the Boot 500MB partition. -Clicked on Customize... -Clicked on Reformat -Clicked on Apply Changes At this point my Boot partition disappears. -Click on plus button on new F18 installation. -Click on ext4 500MB partition. -Type in /boot into Mount Point. -Click Apply Changes At this point a Boot 500MB partition is added, but the old ext4 500MB partition line is still displayed. 1) The logic behind the steps required to entire custom partitioning is wordy. It should be a simple step of asking the user Do it for me! or Let me do it! and not a couple paragraphs of text no one will read. 2) The Customize... expander is frivolous. There is an extensive amount of empty UI space. There is no need to have an expander for the Customize... area. It should always be displayed as we are in Custom Partitioning to begin with. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18 beta experience under VM
On 12/03/2012 01:19 AM, Adam Williamson wrote: This kind of change is very disruptive and won't happen post-Beta. Also, we can't do that anyway: the reason there's a date/time spoke during anaconda at all is because on some systems the clock is completely wrong - like 30 years wrong - and that can affect some package scripts. So the spoke exists to make sure you have an opportunity to set the correct date/time prior to package install beginning. Moving the spoke to during package installation would defeat its purpose. If we didn't need to be sure date/time could be set prior to package install on some systems, there would be no such spoke in anaconda at all, and it'd be done at firstboot instead. There's a solution to this. Hard code the date in the installer when the ISO is created. We know today's date and it could be set in the installer before the UI starts. Then it doesn't matter what the person's system is set to. It doesn't need to be accurate to the exact second, but the year would be accurate and that should be more than enough to pass package script checks. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18 beta experience under VM
On 12/03/2012 08:44 AM, Michael Cronenworth wrote: 1) The logic behind the steps required to entire custom partitioning is wordy. It should be a simple step of asking the user Do it for me! or Let me do it! and not a couple paragraphs of text no one will read. s/entire/enter -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18 beta experience under VM
On 12/03/2012 02:40 AM, Adam Williamson wrote: Yeah, I seem to recall we've been round that merry-go-round before, and somehow it's happening again. The first entry should indeed be the default, so we should re-jig the order, I think. Should a new bug be created for this or does one already exist? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18 beta experience under VM
On 12/03/2012 08:47 AM, Michael Cronenworth wrote: There's a solution to this. Hard code the date in the installer when the ISO is created. We know today's date and it could be set in the installer before the UI starts. Then it doesn't matter what the person's system is set to. It doesn't need to be accurate to the exact second, but the year would be accurate and that should be more than enough to pass package script checks. ... and for extra brownie points: If we detect a network connection: Use chrony to update the date! (in the case of user's using updates repos during install) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18 beta experience under VM
On 12/03/2012 10:44 AM, Adam Williamson wrote: At no point in all that did you actually assign a mount point to it. I think you may be hitting the label/mount point confusion here. 'Boot' is not a mount point: it is the label of that partition. If I'm reading this correctly, at this point in the process, you have nothing set to be mounted at /boot. All you've done is say you'd like to format the partition called Boot in your existing F18 install, but you haven't said you'd actually like to use it in the new install in any way. Boot is not a label on the file system, it is a label of the UI widget. I do not use labels on my file systems and there is not one on my existing F18 install. At this point a Boot 500MB partition is added, but the old ext4 500MB partition line is still displayed. Well yes, you didn't say that partition should be removed. Why would it disappear? Instead of adding an additional UI widget item for a partition, I expect the existing partition UI widget to be updated. In fact, when you navigate back to the old partition setup, and then back to the new partition setup, the duplicate UI widget is gone. https://bugzilla.redhat.com/show_bug.cgi?id=883076 1) The logic behind the steps required to entire custom partitioning is wordy. It should be a simple step of asking the user Do it for me! or Let me do it! and not a couple paragraphs of text no one will read. So, wait, we have a couple of people in the thread suggesting that what the installer needs is more explanatory text, and now you're suggesting that explanatory text is wordy paragraphs no one will read?:) I deal with end users of all backgrounds every day. People don't read *anything* you give them. People that say otherwise have been programming in basements for too long. I've actually suggested that to dlehman myself, but apparently Mo wasn't keen on it, but I haven't discussed it directly with her. A compromise I suggested was to name the expander more clearly. 'Customize' gives you no idea what's behind it. That is unfortunate. What's the purpose of having 50% of the screen be blank? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18 beta experience under VM
On 12/03/2012 10:35 AM, David Lehman wrote: Apparently you are the first one to attempt this particular workflow. Please open a bug report. https://bugzilla.redhat.com/show_bug.cgi?id=883076 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18 beta experience under VM
On 12/03/2012 10:41 AM, Adam Williamson wrote: Probably file a new one. What component should it be filed under? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18 beta experience under VM
On 12/03/2012 12:08 PM, Andre Robatino wrote: The current defaults are mediacheck for install images and no mediacheck for lives, so to keep that, the choice is to either make the order of menu entries different on installs vs. lives, or keep them the same, and have the default not be the first entry on one of them. Media checks have always been optional. Why are they the default now? Bug filed: https://bugzilla.redhat.com/show_bug.cgi?id=883086 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F18 beta experience under VM
On 12/03/2012 05:50 PM, Matthew Miller wrote: That's a good idea. Have you filed an RFE in bugzilla? https://bugzilla.redhat.com/show_bug.cgi?id=883182 I wasn't sure on the component. Feel free to correct. Thanks! -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F18 beta experience under VM
Getting to the first anaconda UI screen took a good 1-2 minutes. I wasn't sure if the VM had locked up as I had no indication of work being done. I can see people being frustrated with the wait and rebooting a few times and then posting on @test or @users that F18 won't install. The custom partitioning manager, as mentioned on other threads, is confusing and buggy. The VM I tested with was already F18 alpha. Anaconda saw F18 already installed, and when I offered to reformat the existing partitions they disappeared from the F18 alpha list (not expecting that) and I found them under the F18 beta partitioning without a mount point. When I added a mount point the partition was duplicated so for example I had a 500MB ext4 partition and gave it a /boot mount point, which created a 500MB Boot ext4 partition leaving the original partition still on my screen. Overall I think the NewUI is a step in the right direction even if it is a very rough, if not still in carbon form, diamond. May I suggest that the Date/Time setting be moved to the User Settings page, which is during package installation? The root password setting looks lonely. Michael -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Notes on testing F18 in an EFI environment
G.Wolfe Woodbury wrote: I need to file a BZ for the update EFI incompatibility but have not quite figured out which component to file against yet. Bare in mind that VBox EFI is not fully functional. I just loaded F17 (install ISO, not live) on a brand-new UEFI-only motherboard with full graphical anaconda. I did not have to manually adjust or configure any* part of Fedora and the system booted fine once installed. * I did have to format the new SSD to GPT before installing as anaconda wanted MBR. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Notes on testing F18 in an EFI environment
On 11/14/2012 07:17 PM, Adam Williamson wrote: anaconda will use the existing partition label format unless you direct it to reformat the entire drive, in which case it'll use the preferred format for the install you're doing. It's not possible to re-label a drive without reformatting it. So if the drive was already MS-DOS labelled and you picked partitioning options that didn't involve reformatting the whole thing, that'd be expected. The SSD was fresh from the factory. No bits were written to it prior to my first attempt at F17 install. The first F17 install attempt told me it needed to initialize the drive. I said OK and continued with install. When it was going to format (the entire drive, as no data was on it prior) anaconda said it was going to use MSDOS labeling. I exited the installer before this occured, loaded a Live image, and formatted the drive to GPT (palimpset showed no prior data or formatting). -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Notes on testing F18 in an EFI environment
On 11/14/2012 07:47 PM, Adam Williamson wrote: That sounds odd. Are you double-extra-plus sure it was booting UEFI? It should never attempt to format to MS-DOS for a UEFI install. I suppose it might just be that the*message* was incorrect. -- I'm a UEFI noob. My EFI does not have any BIOS/EFI boot option even though the manual shows one. There is a Compatibility Support Module that is set to Auto and this seems to have smarts to boot a system in BIOS or EFI automatically. It default boots in BIOS mode and anaconda saw this. I do not have a /sys/firmware/efi currently. When I turned off CSM and reinstalled (with a EFI USB stick...) everything is now EFI. Now this tangent can come to an end. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Selinux in development releases
drago01 wrote: This would just mean we test something different then we actually ship. If there are selinux bugs they are supposed to be cough during testing and reported like any other bugs. +1 There are instances of SELinux rules (bug or intentional) that only occur under Enforcing. The SELinux team is very speedy IMHO. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Selinux in development releases
Jóhann B. Guðmundsson wrote: Do you have any reference for such bugs that only happen when selinux is in enforcing mode but not when it is in enforcing mode? Yes, here is one bug[1] to get you started. [1] https://bugzilla.redhat.com/show_bug.cgi?id=638511 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Selinux in development releases
Jóhann B. Guðmundsson wrote: This bug is filed against RHEL in any case just have it in permissive mode up to beta should suffice and prevent any RC_N surprises Jóhann, I didn't blindly post the first bug I found. I ran into this bug on a Fedora system, which is the only reason I knew about it in the first place. If you read the bug comments you will find: * With Enforcing: No AVC messages were output, but dirsrv-admin could not be started * With Permissive: No AVC messages where output, but dirsrv-admin started If you default to Permissive then you *will* miss possible policy bugs. Some of these are hidden in dontaudit messages such as the bug I linked. It would be good to get feed back from Dan what's his taken on this Good. I know I'm Mr. Nobody here, but his answer would be definitive. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: New BugZapper Introduction
Adam Williamson wrote: Michael - this is just what Chris is doing. He's clearly been to the Bugzappers Join page: https://fedoraproject.org/wiki/BugZappers/Joining which asks people to send a self-introduction mail. This is why we get such mails, it's not just dozens of people deciding on their own to write one. :) I knew full well that that page existed and why the emails reach this list. I also knew that the Bugzappers group was not active and wanted to point him in a positive direction. I'm tired of seeing the emails hit this list and go no where. We should encourage contributors and not ignore them. I'm sick and tired of the down talking you give me day in and day out, Adam. Please stop. Chris, and other recent bugzapper applicants - thanks a lot for volunteering to help out. At present the Bugzappers group is fairly dormant, though we will certainly handle your application and there's nothing to stop people working on bug triage. You might want to look at the other participation options on the QA Join page too, though: Thanks for regurgitating my e-mail in your own words. You're as much a narcissist as I am but we don't need to clash with each other. Thanks, Michael -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: New BugZapper Introduction
On Sat Sep 8 2012 11:14:48 PM CDT, Chris Hyndman chynd...@zoho.com wrote: Hi Bug Zappers, I'm hoping that you will consider me as a potential new member for the Fedora Bug Zapper team. I started installing, using and embracing Linux distros about four years ago and it would be great for me to be able to return the favor. (Snip) Hi Chris, The best way to give back is to package software. Other ways include QA work or user support. You don't need to apply to a group to start giving back. Just Do It. Regards, Michael -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Gnutls 3??
Richard Shaw wrote: nettle was easy enough to package[1]... Took about 10 minutes, but I don't have any real interest in maintaining it... Someone want to pick it up? Nettle contains many pieces so I've taken an alternative approach to packaging it. https://bugzilla.redhat.com/show_bug.cgi?id=833573 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Gnutls 3??
Richard Shaw wrote: I wonder, is the package name libnettle acceptable? Generally the main package name needs to be the same as the upstream name, which is just nettle. You're right. Fixed. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: gtk3-3.5.2-1 ???
Rob Healey wrote: The only reason why, would be to use it now rather than having to wait for FC18 to stabilize a little more first. If this is such a bad idea, then I will wait for rawhide? GTK 3.5 is an unstable branch. There's a reason why the package maintainer does what he does. I would recommend that you stick with the F17 packages unless you have a legitimate reason (and judging from your two e-mails you do not) not to. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: f17 should I be using updates-testing?
Neal Becker wrote: After doing preupgrade f16-f17, I see yum update does nothing. Maybe I should be using updates-testing for now? That's the beauty of preupgrade. It brings your system up to now. An ISO file can only bring your system up to then (when the ISO was generated). If you want to help QA, then yes, enable updates-testing. Otherwise it is not really necessary. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Testing of f17 TC2 in USB
On 05/03/2012 06:20 AM, Adam Williamson wrote: That would be my guess too. Do you have another you can test with? Once TC3 lands I'll try again and get back with you. I'll also try with the latest livecd-tools. I was using the F16 package the first time. I saw an update land into testing today that mentioned some F17 fixes. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Testing of f17 TC2 in USB
On 05/02/2012 03:24 PM, Adam Williamson wrote: It's good of you to do this, but it would be even_better_ if you'd follow the test cases at https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test#USB_Stick , file bugs on any failures, and enter your results into the matrix, with bugzilla links to the failures. The whole point of the validation matrices is to co-ordinate this kind of testing so the results are not lost and bugs found are given appropriate priority. thanks! I'm having a hard time figuring out how people passed the USB install in your matrix. I can't get it to work. I used the DVD ISO and the livecd-iso-to-disk script (--format, --reset-mbr) to format a 8GB USB stick. The image boots and installation (with *defaults*) begins. It gets to 160 packages of 1212 and errors on perl. A unpack error occurred when installing the perl package... The image checksummed properly. I have tried installation twice. Same error at same point each time. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Testing of f17 TC2 in USB
On 05/02/2012 06:57 PM, Michael Cronenworth wrote: The image boots and installation (with *defaults*) begins. It gets to 160 packages of 1212 and errors on perl. A unpack error occurred when installing the perl package... I burned the image to a real DVD and installation succeeded. My guess is that my USB stick is bad. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: block on name
On 04/27/2012 01:55 PM, george2 wrote: The banking crises was in part formed by many individuals sensing something wasn't right but did not take any personal responsibility to act. If you really meant the words you typed then you would be responding to the replies to your message. It is obvious you wrote a one-off rant that alleviates your ignorance about what the F17 name means. A.K.A. A spam mail to the test list. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: FC17 and btrfs
On 04/12/2012 09:00 PM, Rob Healey wrote: Is there a step by step document explaining how to change my local filesystem from ext4 to btrfs after my computer has already been installed??? Google works really well for these sorts of questions. https://btrfs.wiki.kernel.org/articles/c/o/n/Conversion_from_Ext3_6e03.html I would not recommend using btrfs if you did not know how to do the conversion. There is still no fsck tool. Well, there is one now (1 month old!) but it is highly experimental. Be prepared to lose data or experience bugs. Michael -btrfs user -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Install Fedora Button for LiveCD
Kamil Paral wrote: http://kparal.fedorapeople.org/misc/InstallFedoraButton.png What do you think? Better than default? I like it. Good work. Would it be better to have the text say Install Fedora instead of .. to Hard Drive? Hard Drive is becoming an obsolete term. You have flash drives, SSDs, or whatever else people install Fedora to. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F17 vs. Pentium 4
Michael Hennebry wrote: How do I find the most recent image? I'd previously thought that that was the most recent image. Official images are made one time only. You will need to make a new install image yourself or try a Fedora 17 beta image. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: New BugZapper Introduction
Ted Hornsby wrote: My name is Ted Hornsby. I'm 27 and reside in the North Texas area. I've been using Linux for quite a while, but have only just recently started using Fedora, but I'm liking it more and more everyday. I wanted to give something back to the community, so I thought joining the BugZappers would be a good way to start. Hey Ted, how wacky is this. We're the same age and live in the same area. Welcome. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: X.Org 1.12-compatible VBoxGuestAdditions_4.1.9-76737.iso available (works with F17 and Rawhide)
Andre Robatino wrote: VirtualBox 4.1.10 has just been released, and X.Org 1.12 is supported. I wish the Linux guest 3D driver was fixed. It still hangs due to some threading issue. The Windows guest 3D driver seems to be much more stable though. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
mdraid with encrypted fs
I installed a system fresh with Fedora 15 when it was released. I configured the file system to have root on a software RAID 1 and then encrypted the ext4 file system inside of the raid. I tried to upgrade to F16 a few days ago and ran into an Anaconda bug[1]. Is my particular use-case supported and then does it need a QA test case? I see a test case for encrypted root but not for RAID+encrypted root. In regards to the bug, am I stuck doing a yum upgrade or is there a possible workaround to use preupgrade? [1] https://bugzilla.redhat.com/show_bug.cgi?id=753421 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: mdraid with encrypted fs
On 02/13/2012 08:35 PM, Adam Williamson wrote: I'd suggest that this is 'supported' in terms of the release criteria, under the Final criterion The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above: we don't explicitly list encryption there, but we probably should, and I'd read the intent of the criterion as being that encryption should be covered. So, I'd say you could propose your bug as a Final blocker. It looks like it has just been marked as a Beta blocker. As far as 'should there be a test case' - well, it's kind of a tricky question: there are essentially unlimited permutations when it comes to filesystem layout, and we can't have a test case for*every single one*, especially not a test case that must be done for the release to proceed. There'd be no harm at all in you drawing up a test case for this scenario, but whether we should add it to the matrices and especially whether we should mark it as Final (indicating it has to be completed for the release to ship) is a more difficult question. Your test matrix already includes RAID and encryption but not together. The problem post-release is that how do I upgrade? Wait for F17 for a fix? Roll my own installer ISO? Use yum? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
