Re: F21 Installation Issues - Installation destination partitioning
Hi, Can you instruct me in how you installed the nVidia drivers? - Original Message - From: "Joerg Lechner" To:, Cc: Sent:Tue, 11 Nov 2014 02:18:35 -0500 Subject:Re: F21 Installation Issues - Installation destination partitioning Hi, on my laptop there is a Nvidia Geforce 840M (Acer Aspire E15, E5 571G). I didn't have any problems with the grafics drivers so far. Currently running F21 Final TC1. Kind Regards -Ursprüngliche Mitteilung- Von: Bidski An: test Verschickt: Mo, 10 Nov 2014 10:05 pm Betreff: Re: F21 Installation Issues - Installation destination partitioning Has anyone had success installing the nVidia drivers in F21 yet? I am meeting some strange issues following the instructions for installing them in F20. Including this page (https://www.dropbox.com/s/9de7q9llhlamf32/IMG_20141110_192627.jpg?dl=0 [1]) displaying while booting after installing the drivers. I will generate some better diagnostics tonight. - Original Message - From: "Adam Williamson" To: "Bidski" , "For testing and quality assurance of Fedora releases" Cc: Sent: Sun, 09 Nov 2014 23:38:19 -0800 Subject: Re: F21 Installation Issues - Installation destination partitioning On Mon, 2014-11-10 at 18:28 +1100, Bidski wrote: > > After shifting the partitions on my HDD up by about 200 MiB and then > using gdisk to convert the disk to GPT (did it this way to try and > preserve the existing Windows partitions), the Fedora installer now > only recognises my HDD as a multipath device. > I also looked at the F21 Common Bugs page on the wiki. There is a > section there talking about multipath device issue. I created edited > the /etc/multipath.conf file to have the contents specified but the > installer still treats all devices as multipaths. > > Any suggestions here? I wrote the CommonBugs note blind - I couldn't test that the proposed workaround would actually work as I haven't reproduced the bug. However, it shouldn't happen if you use a non-live install image, so I'd suggest that. You can use the 'Server' network install image to install any package set, not just Server, so try using that. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net [5] -- test mailing list test@lists.fedoraproject.org [6] To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test [7] Links: -- [1] https://www.dropbox.com/s/9de7q9llhlamf32/IMG_20141110_192627.jpg?dl=0 [2] mailto:adamw...@fedoraproject.org [3] mailto:bid...@iinet.net.au [4] mailto:test@lists.fedoraproject.org [5] http://www.happyassassin.net [6] mailto:test@lists.fedoraproject.org [7] https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F21 Installation Issues - Installation destination partitioning
Hi, on my laptop there is a Nvidia Geforce 840M (Acer Aspire E15, E5 571G). I didn't have any problems with the grafics drivers so far. Currently running F21 Final TC1. Kind Regards -Ursprüngliche Mitteilung- Von: Bidski An: test Verschickt: Mo, 10 Nov 2014 10:05 pm Betreff: Re: F21 Installation Issues - Installation destination partitioning Has anyone had success installing the nVidia drivers in F21 yet? I am meeting some strange issues following the instructions for installing them in F20. Including this page (https://www.dropbox.com/s/9de7q9llhlamf32/IMG_20141110_192627.jpg?dl=0) displaying while booting after installing the drivers. I will generate some better diagnostics tonight. - Original Message - From: "Adam Williamson" To: "Bidski" , "For testing and quality assurance of Fedora releases" Cc: Sent: Sun, 09 Nov 2014 23:38:19 -0800 Subject: Re: F21 Installation Issues - Installation destination partitioning On Mon, 2014-11-10 at 18:28 +1100, Bidski wrote: > > After shifting the partitions on my HDD up by about 200 MiB and then > using gdisk to convert the disk to GPT (did it this way to try and > preserve the existing Windows partitions), the Fedora installer now > only recognises my HDD as a multipath device. > I also looked at the F21 Common Bugs page on the wiki. There is a > section there talking about multipath device issue. I created edited > the /etc/multipath.conf file to have the contents specified but the > installer still treats all devices as multipaths. > > Any suggestions here? I wrote the CommonBugs note blind - I couldn't test that the proposed workaround would actually work as I haven't reproduced the bug. However, it shouldn't happen if you use a non-live install image, so I'd suggest that. You can use the 'Server' network install image to install any package set, not just Server, so try using that. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: wrong resolution in Fedora 21 beta
On 11/10/2014 10:42 PM, Samuel Sieb wrote: On 11/10/2014 06:06 PM, Frank wrote: I installed 21 beta today from the live cd and ran into a couple of (minor) problems. I guess because I had booted the live cd in safe mode (trying to solve another problem) when I installed it from the desktop I ended up with 1280x1024 resolution. My monitor is capable of 1650x900 but I can't figure out how to change it. Look in your grub config file and remove the "nomodeset" options. Also, remove it from /etc/default/grub. That did it ! Thanks. Removed it from /etc/default/grub and rebuilt grub.cfg. But now I have lockup problems on the desktop and to some extent at the CLI. I have disabled composting in Marco ( I'm running the Mate desktop) and nothing else I could see that might affect video is on. It's real tight lockups...nothing works except the power button. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: wrong resolution in Fedora 21 beta
On Mon, 2014-11-10 at 21:06 -0500, Frank wrote: > I installed 21 beta today from the live cd and ran into a couple of > (minor) problems. I guess because I had booted the live cd in safe mode > (trying to solve another problem) when I installed it from the desktop I > ended up with 1280x1024 resolution. My monitor is capable of 1650x900 > but I can't figure out how to change it. Drop the 'nomodeset' from the kernel parameters in /boot/grub2/grub.cfg (or /boot/efi/EFI/fedora/grub.cfg if you're on UEFI). Just remove all occurrences of that word. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Linux multi-boot release criterion discussion, redux
On Mon, 2014-11-10 at 05:29 -0500, Kamil Paral wrote: > I was about to mention the same, Fedora UEFI dual-boot requires a lot > of manual tweaking at the moment, and I guess it's not something that > can be changed and properly tested in a few weeks. For me it actually works OK in a smoke test with the latest os-prober and grub2, if the first-installed release doesn't use LVM. The grub menu for the second-installed release gets entries for the first, and they work. As they wind up sharing /boot/efi they actually override each other's configurations constantly, but this doesn't seem to break much in practice. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: installation matrix environment adjustments
On Mon, 2014-11-10 at 05:13 -0500, Kamil Paral wrote:
> > It makes sense for Graphical and Text to not be split between i686,
> > x86_64 and UEFI, for sure. And it makes sense for Basic Video Driver to
> > have probably x86 BIOS / x86 UEFI split, indeed. We should consider the
> > other tests in deciding the right thing to do - what's the appropriate
> > split for VNC and serial console?
>
> For VNC, we require the vnc binary (and networking) to work correctly.
> Of course there can be arch-specific bugs. But that's true for almost
> anything, we're working with likelihood-to-break-in-just-a-single-arch
> estimates here. From that POV, I think the test case is very similar
> to NFS/NFSISO repo testcase - again, you need the NFS binaries to work
> correctly. And we have just a single Result column for that.
> As I said, I don't feel well acquainted with ARM to guess which areas
> are more or less likely to work differently than on x86, and thus
> likely to contain arch-specific bugs. But I'd either keep current x86
> & ARM separation, or unify that into a single test result, as with
> NFS.
>
> Serial console is likely to be more different between x86 and ARM than
> VNC (I seem to remember some ARM specific serial console bugs from
> this cycle), so the current separation seems reasonably there.
>
> Another question is whether we should keep the same approach for Text
> interface test case, or whether that can be united into a single
> result. Not sure here.
If you want my guess, I guess I'd suggest we make VNC non-arch-specific,
keep serial console split ARM/x86, and make text non-interface-specific,
it seems like as long as you get a console at all, that ought to work.
> > ACK. Honestly I think this is just because they used to be in the
> > miscellaneous tests table (some of them still are, I think) and that
> > thing was freaking huge, and I kinda ran out of steam when I was doing
> > the revision and just left some of 'em alone).
>
> All of them are from Miscellaneous section. Do you have a good idea
> how to make then x86 generic without making the tables too complex?
>
> I can add a fourth 'x86' column, and gray out BIOS and UEFI columns
> for these discussed test cases. Which is usable, but not completely
> nice (the table source code grows a lot).
> Or I can create a separate table in this section. I think this is
> nicer and we'll end up doing this in some sections in the future
> anyway. Do you see some disadvantage in it?
No, I agree, I was kinda working to split the misc section up. It fits
the design most nicely if you can come up with some sort of 'topic'
connection between the cases that live together in a table, but the
*functional* reason to have split tables is indeed to group tests with
similar result environments, and I don't like having too much greying
out of the rows either.
We should really limit the greying-out hack and use it only when a test
case is *clearly* part of a set with a lot of others but the
environments that otherwise apply to them all don't apply to it - i.e.
it should be a 'rare exception' case, we shouldn't be building complex
sets of result columns where each one might have only one or two white
boxes.
> Yes, this is exactly the reason why I try to reduce the number of
> boxes. Because even though in theory it would be nice to have fields
> for every possible combination and people would fill them according to
> the real priority (e.g. it's better to test 2 different test cases on
> a single arch, than a single test case on 2 arches), in practice often
> the opposite happens. We don't have this priority specified anywhere
> ("is it really important to test run test case on all arches or
> not?"), and even if we did, it would probably make the matrix horribly
> complicated. So people tend to do the opposite approach - I have read
> this test case, I remember it now, so let's run it for all
> architectures available, and only then continue to the next one. I do
> that often as well, even though it's not efficient from test coverage
> POV, because it's much easier especially when you're juggling with
> several tasks at the same time. And it's also easier than to try to
> decide which white boxes are mandatory and which ones are optional.
>
> The second thing is that we don't usually have too much spare time for
> running extra test cases anyway, so it's better to optimize the
> required path as much as possible, and if people end up with spare
> time, usually they find more bugs when they're just playing with
> software and experimenting, than testing the same stuff on a bit
> different hardware.
Yeah, I more or less agree entirely with all of this. You can count me
generally in favour of any change which rationalizes the tables on the
basis of moving more towards 'white boxes express required testing'.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
--
t
Re: wrong resolution in Fedora 21 beta
On 11/10/2014 06:06 PM, Frank wrote: I installed 21 beta today from the live cd and ran into a couple of (minor) problems. I guess because I had booted the live cd in safe mode (trying to solve another problem) when I installed it from the desktop I ended up with 1280x1024 resolution. My monitor is capable of 1650x900 but I can't figure out how to change it. Look in your grub config file and remove the "nomodeset" options. Also, remove it from /etc/default/grub. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Problem with Display configuration
On Fedora 21, Gnome desktop, the Display configuration tool has regressed: I'm unable to switch my external monitor to be Primary, and the laptop monitor to be Secondary. I also can't disable the external monitor as long as it is plugged in via HDMI. I.e. when I try to change those settings, and Apply then, nothing changes. This is with a freshly-rebooted system, so it's not suspend/lock-related, as I though before. My laptop is a Toshiba Satellite P-50A, and the connected display is a Seiki 4k 50" display. If I should report a bug, which Component would this be? -- --Per Bothner p...@bothner.com http://per.bothner.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
wrong resolution in Fedora 21 beta
I installed 21 beta today from the live cd and ran into a couple of (minor) problems. I guess because I had booted the live cd in safe mode (trying to solve another problem) when I installed it from the desktop I ended up with 1280x1024 resolution. My monitor is capable of 1650x900 but I can't figure out how to change it. The other minor problems was a blank white screen on the first reboot after install..but that was resolved somehow when I updated 21 from a console. I still need to figure out how to allow Thunderbird access to my mail on the other partition (Debian Sid). I was using a mount of the .thunderbird directory using bind when I was running Fedora 19 and 20 but that doesn't seem to work anymore. All suggestions are welcome. Thanks -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Resume still broken on Thinkpad X1 Carbon
On 10.11.2014 21:33, Jared K. Smith wrote: > On Tue, Nov 4, 2014 at 9:17 AM, Jonathan Corbet wrote: > >> - Under F21, suspend seems to work fine, but there is no response to the >>power button (or any other input). One has to hold the power button >>until the firmware gets fed up and powers things down hard. >> > > > I had the same problem with mine (X1 Carbon second generation) until I > updated the UEFI firmware on it. Since updating that, I haven't had any > problems with suspend or resume. > These are usually three components that affect the functionality of the suspension, and hibernation. \ - STORAGE - once are solved the specificities of the new device, no problemos - BIOS/EFI - poorly customized original firmware, once this is resolved, no problemos - VGA - most annoying, is repeated in cycles, with new features come new bugs poma -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F21 Installation Issues - Installation destination partitioning
Has anyone had success installing the nVidia drivers in F21 yet? I am meeting some strange issues following the instructions for installing them in F20. Including this page (https://www.dropbox.com/s/9de7q9llhlamf32/IMG_20141110_192627.jpg?dl=0) displaying while booting after installing the drivers. I will generate some better diagnostics tonight. - Original Message - From: "Adam Williamson" To:"Bidski" , "For testing and quality assurance of Fedora releases" Cc: Sent:Sun, 09 Nov 2014 23:38:19 -0800 Subject:Re: F21 Installation Issues - Installation destination partitioning On Mon, 2014-11-10 at 18:28 +1100, Bidski wrote: > > After shifting the partitions on my HDD up by about 200 MiB and then > using gdisk to convert the disk to GPT (did it this way to try and > preserve the existing Windows partitions), the Fedora installer now > only recognises my HDD as a multipath device. > I also looked at the F21 Common Bugs page on the wiki. There is a > section there talking about multipath device issue. I created edited > the /etc/multipath.conf file to have the contents specified but the > installer still treats all devices as multipaths. > > Any suggestions here? I wrote the CommonBugs note blind - I couldn't test that the proposed workaround would actually work as I haven't reproduced the bug. However, it shouldn't happen if you use a non-live install image, so I'd suggest that. You can use the 'Server' network install image to install any package set, not just Server, so try using that. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Resume still broken on Thinkpad X1 Carbon
On Tue, Nov 4, 2014 at 9:17 AM, Jonathan Corbet wrote: > - Under F21, suspend seems to work fine, but there is no response to the >power button (or any other input). One has to hold the power button >until the firmware gets fed up and powers things down hard. > I had the same problem with mine (X1 Carbon second generation) until I updated the UEFI firmware on it. Since updating that, I haven't had any problems with suspend or resume. -- Jared Smith -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 21 updates-testing report
The following Fedora 21 Security updates need testing: Age URL 4 https://admin.fedoraproject.org/updates/FEDORA-2014-13837/konversation-1.5.1-1.fc21 3 https://admin.fedoraproject.org/updates/FEDORA-2014-14461/python-requests-kerberos-0.6-1.fc21 0 https://admin.fedoraproject.org/updates/FEDORA-2014-14617/GraphicsMagick-1.3.20-3.fc21 0 https://admin.fedoraproject.org/updates/FEDORA-2014-14697/drupal7-ckeditor-1.16-2.fc21 0 https://admin.fedoraproject.org/updates/FEDORA-2014-14546/oath-toolkit-2.4.1-6.fc21 The following Fedora 21 Critical Path updates have yet to be approved: Age URL 4 https://admin.fedoraproject.org/updates/FEDORA-2014-14342/cdrkit-1.1.11-25.fc21 3 https://admin.fedoraproject.org/updates/FEDORA-2014-14476/pulseaudio-5.0-24.20141103gitaec81.fc21 3 https://admin.fedoraproject.org/updates/FEDORA-2014-14433/libteam-1.14-1.fc21 0 https://admin.fedoraproject.org/updates/FEDORA-2014-14639/pcre-8.35-7.fc21 0 https://admin.fedoraproject.org/updates/FEDORA-2014-14298/openssh-6.6.1p1-7.fc21 The following builds have been pushed to Fedora 21 updates-testing abcde-2.6-1.fc21 anki-2.0.31-1.fc21 bluebird-1.2-2.fc21 drupal7-ckeditor-1.16-2.fc21 drupal7-ds-2.7-1.fc21 drupal7-link-1.3-1.fc21 gimp-paint-studio-2.0-8.fc21 greybird-1.4-3.fc21 mate-themes-1.9.2-0.1.git20141108.66e3797.fc21 mesa-10.3.3-1.20141110.fc21 mintmenu-5.6.0-1.fc21 perl-Devel-Timer-0.06-1.fc21 php-Monolog-1.11.0-1.fc21 php-aws-sdk-2.7.3-1.fc21 php-egulias-email-validator-1.2.5-1.fc21 python-structlog-0.4.2-3.fc21 recoll-1.19.14p2-1.fc21 sazanami-fonts-0.20040629-23.fc21 xpa-2.1.15-2.fc21 Details about builds: abcde-2.6-1.fc21 (FEDORA-2014-14680) A Better CD Encoder Update Information: Update to version 2.6. http://git.einval.com/cgi-bin/gitweb.cgi?p=abcde.git;a=blob;f=changelog;hb=HEAD ChangeLog: * Sun Nov 9 2014 Ville Skyttä - 2.6-1 - Update to 2.6 - Mark COPYING as %license where applicable anki-2.0.31-1.fc21 (FEDORA-2014-14685) Flashcard program for using space repetition learning Update Information: Update to new bugfix upstream release 2.0.28. Please see http://www.ankisrs.net/docs/changes.html for details. ChangeLog: * Mon Nov 3 2014 Christian Krause - 2.0.31-1 - Update to new upstream version 2.0.31 (BZ 1144973) References: [ 1 ] Bug #1144973 - anki-2.0.31 is available https://bugzilla.redhat.com/show_bug.cgi?id=1144973 bluebird-1.2-2.fc21 (FEDORA-2014-14679) A clean minimalistic theme for Xfce, GTK+ 2 and 3 Update Information: Upstream fix for checkboxes and radios in gtk3.14 ChangeLog: * Sat Nov 8 2014 poma 1.2-2 - Upstream fix for checkboxes and radios in gtk3.14 - The "shadow" is re-enabled, the full size of the app menu in the system tray is resolved upstream - gtkmenu: fix unnecessary scroll buttons gtk-3-14 https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-14&id=695ff38 - The same applies to the Shimmer Project Desktop Suites for Xfce as a whole, i.e. Greybird, Bluebird and Albatross. - With these two corrections bugs #1114161, #1139190 and #1139187 are solved completely. References: [ 1 ] Bug #1139190 - Update to 1.2 & catch up gtk3 https://bugzilla.redhat.com/show_bug.cgi?id=1139190 drupal7-ckeditor-1.16-2.fc21 (FEDORA-2014-14697) Enables the usage of CKEditor (WYSIWYG) instead of plain text fields Update Information: ## [7.x-1.16](https://www.drupal.org/node/2356563) * [SA-CONTRIB-2014-098 - CKEditor - Cross Site Scripting (XSS)](https://www.drupal.org/node/2357029) ChangeLog:
Fedora 19 updates-testing report
The following Fedora 19 Security updates need testing: Age URL 380 https://admin.fedoraproject.org/updates/FEDORA-2013-19963/openstack-glance-2013.1.4-1.fc19 192 https://admin.fedoraproject.org/updates/FEDORA-2014-5896/nrpe-2.15-2.fc19 143 https://admin.fedoraproject.org/updates/FEDORA-2014-7496/readline-6.2-8.fc19 61 https://admin.fedoraproject.org/updates/FEDORA-2014-10366/icecream-1.0.1-8.20140822git.fc19 60 https://admin.fedoraproject.org/updates/FEDORA-2014-10640/libreoffice-4.1.6.2-8.fc19 45 https://admin.fedoraproject.org/updates/FEDORA-2014-11544/drupal6-6.33-1.fc19 38 https://admin.fedoraproject.org/updates/FEDORA-2014-12057/krb5-1.11.3-29.fc19 31 https://admin.fedoraproject.org/updates/FEDORA-2014-12407/sddm-0.9.0-2.20141007git6a28c29b.fc19 24 https://admin.fedoraproject.org/updates/FEDORA-2014-13047/libxml2-2.9.1-2.fc19 24 https://admin.fedoraproject.org/updates/FEDORA-2014-13018/deluge-1.3.10-1.fc19 14 https://admin.fedoraproject.org/updates/FEDORA-2014-13551/wpa_supplicant-2.0-12.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-14066/php-sabredav-Sabre_VObject-2.1.4-1.fc19,php-sabredav-Sabre_HTTP-1.7.11-1.fc19,php-sabredav-Sabre_CalDAV-1.7.9-1.fc19,php-sabredav-Sabre_DAVACL-1.7.9-1.fc19,php-sabredav-Sabre_CardDAV-1.7.9-2.fc19,php-sabredav-Sabre_DAV-1.7.13-1.fc19,owncloud-5.0.17-2.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-14068/kernel-3.14.23-100.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-14266/python-2.7.5-15.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-14237/claws-mail-plugins-3.11.1-1.fc19,claws-mail-3.11.1-2.fc19,libetpan-1.6-1.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-14257/python3-3.3.2-10.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-14233/aircrack-ng-1.2-0.3.rc1.fc19 3 https://admin.fedoraproject.org/updates/FEDORA-2014-13702/konversation-1.5.1-1.fc19 3 https://admin.fedoraproject.org/updates/FEDORA-2014-14359/curl-7.29.0-25.fc19 1 https://admin.fedoraproject.org/updates/FEDORA-2014-14498/python-requests-kerberos-0.6-1.fc19 0 https://admin.fedoraproject.org/updates/FEDORA-2014-14699/drupal7-ckeditor-1.16-2.fc19 0 https://admin.fedoraproject.org/updates/FEDORA-2014-14564/qpid-cpp-0.26-12.fc19 The following Fedora 19 Critical Path updates have yet to be approved: Age URL 328 https://admin.fedoraproject.org/updates/FEDORA-2013-22326/fedora-bookmarks-15-5.fc19 254 https://admin.fedoraproject.org/updates/FEDORA-2014-3245/testdisk-6.14-2.fc19.1,ntfs-3g-2014.2.15-1.fc19 12 https://admin.fedoraproject.org/updates/FEDORA-2014-13880/device-mapper-persistent-data-0.4.1-1.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-14068/kernel-3.14.23-100.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-14047/qtwebkit-2.3.4-1.fc19 5 https://admin.fedoraproject.org/updates/FEDORA-2014-14266/python-2.7.5-15.fc19 3 https://admin.fedoraproject.org/updates/FEDORA-2014-14359/curl-7.29.0-25.fc19 1 https://admin.fedoraproject.org/updates/FEDORA-2014-14516/pcre-8.32-11.fc19 1 https://admin.fedoraproject.org/updates/FEDORA-2014-14505/unzip-6.0-12.fc19 The following builds have been pushed to Fedora 19 updates-testing anki-2.0.31-1.fc19 drupal7-ckeditor-1.16-2.fc19 drupal7-ds-2.7-1.fc19 drupal7-link-1.3-1.fc19 gimp-paint-studio-2.0-8.fc19 mintmenu-5.6.0-1.fc19 php-Monolog-1.11.0-1.fc19 recoll-1.19.14p2-1.fc19 Details about builds: anki-2.0.31-1.fc19 (FEDORA-2014-14681) Flashcard program for using space repetition learning Update Information: Update to new bugfix upstream release 2.0.28. Please see http://www.ankisrs.net/docs/changes.html for details. ChangeLog: * Mon Nov 3 2014 Christian Krause - 2.0.31-1 - Update to new upstream version 2.0.31 (BZ 1144973) References: [ 1 ] Bug #1144973 - anki-2.0.31 is available https://bugzilla.redhat.com/show_bug.cgi?id=1144973 drupal7-ckeditor-1.16-2.fc19 (FEDORA-2014-14699) Enables the usage of CKEditor (WYSIWYG) instead of plain text fields Update Information: ## [7.x-1.16](https://www.drupal.org/node/2356563) * [SA-CONTRIB-2014-098 - CKEditor - Cross Site Scripting (XSS)](https://www.drupal.org/node/2357029) ChangeLog: * Mon Nov 10 2014 S
Fedora 20 updates-testing report
The following Fedora 20 Security updates need testing: Age URL 192 https://admin.fedoraproject.org/updates/FEDORA-2014-5897/nrpe-2.15-2.fc20 61 https://admin.fedoraproject.org/updates/FEDORA-2014-10451/geary-0.6.3-1.fc20 61 https://admin.fedoraproject.org/updates/FEDORA-2014-10468/icecream-1.0.1-8.20140822git.fc20 46 https://admin.fedoraproject.org/updates/FEDORA-2014-11430/ca-certificates-2014.2.1-1.1.fc20 38 https://admin.fedoraproject.org/updates/FEDORA-2014-11969/krb5-1.11.5-16.fc20 29 https://admin.fedoraproject.org/updates/FEDORA-2014-12699/facter-1.7.6-1.fc20 5 https://admin.fedoraproject.org/updates/FEDORA-2014-14247/aircrack-ng-1.2-0.3.rc1.fc20 3 https://admin.fedoraproject.org/updates/FEDORA-2014-13791/konversation-1.5.1-1.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2014-14506/oath-toolkit-2.4.1-6.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2014-14493/python-requests-kerberos-0.6-1.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2014-14674/drupal7-ckeditor-1.16-2.fc20 The following Fedora 20 Critical Path updates have yet to be approved: Age URL 13 https://admin.fedoraproject.org/updates/FEDORA-2014-13756/sddm-0.10.0-2.fc20 3 https://admin.fedoraproject.org/updates/FEDORA-2014-14389/colord-1.1.8-1.fc20 1 https://admin.fedoraproject.org/updates/FEDORA-2014-14526/pcre-8.33-7.fc20 The following builds have been pushed to Fedora 20 updates-testing anki-2.0.31-1.fc20 drupal7-ckeditor-1.16-2.fc20 drupal7-ds-2.7-1.fc20 drupal7-link-1.3-1.fc20 gimp-paint-studio-2.0-8.fc20 mate-themes-1.9.2-0.1.git20141108.98cd09d.fc20 mintmenu-5.6.0-1.fc20 perl-Devel-Timer-0.06-1.fc20 php-Monolog-1.11.0-1.fc20 php-aws-sdk-2.7.3-1.fc20 php-egulias-email-validator-1.2.5-1.fc20 recoll-1.19.14p2-1.fc20 Details about builds: anki-2.0.31-1.fc20 (FEDORA-2014-14689) Flashcard program for using space repetition learning Update Information: Update to new bugfix upstream release 2.0.28. Please see http://www.ankisrs.net/docs/changes.html for details. ChangeLog: * Mon Nov 3 2014 Christian Krause - 2.0.31-1 - Update to new upstream version 2.0.31 (BZ 1144973) References: [ 1 ] Bug #1144973 - anki-2.0.31 is available https://bugzilla.redhat.com/show_bug.cgi?id=1144973 drupal7-ckeditor-1.16-2.fc20 (FEDORA-2014-14674) Enables the usage of CKEditor (WYSIWYG) instead of plain text fields Update Information: ## [7.x-1.16](https://www.drupal.org/node/2356563) * [SA-CONTRIB-2014-098 - CKEditor - Cross Site Scripting (XSS)](https://www.drupal.org/node/2357029) ChangeLog: * Mon Nov 10 2014 Shawn Iwinski - 1.16-2 - Removed EPEL 5 bits * Sun Nov 9 2014 Shawn Iwinski - 1.16-1 - Updated to 1.16 (BZ #1153938) - Removed RPM README b/c it only explained common Drupal workflow - Spec cleanup References: [ 1 ] Bug #1153938 - drupal7-ckeditor-1.16 is available https://bugzilla.redhat.com/show_bug.cgi?id=1153938 drupal7-ds-2.7-1.fc20 (FEDORA-2014-14671) Extend the display options for every entity type Update Information: ## [7.x-2.7](https://www.drupal.org/node/2364627) * Issue #2345543 by lorenx: Fixed undefined variable. * Issue #2288345 by axe312: Added token support for region classes. * Issue #2324537 by mitrpaka: Fixed Odd/even classes for field items. * Issue #2284575 by stefan.r: Fixed Node display test fails if site is installed in a subdirectory. * Issue #2289845 by thirdender: Added ds_render_user_picture should use format_username. * Issue #2291887 by MXT: Added FIGURE to custom wrappers. * Added odd/even classes to grouped elements * Issue #1927752 by yannickoo: Token support for outer wrapper's, field items' and field item's classes and attributes. * Issue #2226083 by samhassell: PHP 5.5 'undefined index' notice in ds_extras.registry.inc. * Issue #2111707 by aspilicious | robertstaddon: Display Suite Search + PHP 5.4 = "Notice: Array to string conversion in node_ds_search_execute()". * Prevent f
2014-11-12 @ 1600 UTC ** Fedora Blocker Review Meeting
# F21 Blocker Review meeting # Date: 2014-11-12 # Time: 16:00 UTC (11:00 EST, 08:00 PST) # Location: #fedora-blocker-review on irc.freenode.net It's that time of the week again! Last week we had 15 proposed blockers, which we managed to get down to 4 or so. This week we have 11 to go through. Also, we're keeping the meeting time locked into UTC so make sure to check your local time (for those of us who had a time change recently). If you want to take a look at the accepted blockers, the full list can be found here: https://qa.fedoraproject.org/blockerbugs/milestone/21/final/buglist We'll be evaluating these bugs to see if they violate the Final Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F21 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you Wednesday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 updates-testing report
On Mon, 10 Nov 2014 08:28:14 -0600 Michael Cronenworth wrote: > 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. The builds are all gone and bodhi won't let me unpush it (likely because the builds are all gone). Will see if I can get lmacken to look at it. kevin pgpDqFJFbCdS2.pgp Description: OpenPGP digital signature -- 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: Can't install from Fedora-Server-netinst-x86_64-21_Beta.iso
On Thu, 06 Nov 2014 04:19:17 -0800, Chuck Forsberg WA7KGX wrote: > I tried installing from a flash drive of > Fedora-Server-netinst-x86_64-21_Beta.iso. > I tried a number of package selections based on either Creative and > Development > or Xfce. All failed with software dependencies. > > Is there a way to get Anaconda to reveal which packages provoke dependency > problems? Did it display anything on the virtual consoles? > ILIA PROBE: It is illogical to withhold the required information. Well, a properly prepared and tested product would be free of unresolvable dependencies and unsolvable conflicts in RPM packages. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20141110 changes
Compose started at Mon Nov 10 05:15:04 UTC 2014 Broken deps for i386 -- [3Depict] 3Depict-0.0.16-3.fc22.i686 requires libmgl.so.7.2.0 [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [audtty] audtty-0.1.12-9.fc20.i686 requires libaudclient.so.2 [authhub] authhub-0.1.2-3.fc19.i686 requires libjson.so.0 [cab] cab-0.1.9-12.fc22.i686 requires cabal-dev [condor] condor-plumage-8.1.4-7.a1a7df5.fc22.i686 requires libmongoclient.so [deltacloud-core] deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudservers) deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudfiles) [django-recaptcha] django-recaptcha-0.1-7.20091212svn6.fc21.noarch requires python-django14 [dnssec-check] dnssec-check-1.14.0.1-4.fc20.i686 requires libval-threads.so.14 dnssec-check-1.14.0.1-4.fc20.i686 requires libsres.so.14 [dragonegg] dragonegg-3.4-0.3.rc0.fc21.i686 requires libLLVM-3.4.so dragonegg-3.4-0.3.rc0.fc21.i686 requires gcc = 0:4.8.2-14.fc21 [edelib] edelib-2.1-5.fc22.i686 requires libedelib.so edelib-devel-2.1-5.fc22.i686 requires libedelib.so [fatrat] 1:fatrat-1.2.0-0.21.beta2.fc22.i686 requires libtorrent-rasterbar.so.7 [flush] flush-0.9.12-10.fc22.i686 requires libtorrent-rasterbar.so.7 [gdesklet-SlideShow] gdesklet-SlideShow-0.9-16.fc21.noarch requires gdesklets [gdesklets-citation] gdesklets-citation-2.0-3.20120702git355e2ee.fc19.noarch requires gdesklets [gedit-valencia] gedit-valencia-0.4.0-1.20131223git94442bf.fc21.i686 requires libvala-0.24.so.0 [ghc-hjsmin] ghc-hjsmin-0.1.4.7-3.fc22.i686 requires libHSoptparse-applicative-0.9.0-ghc7.6.3.so [glances] glances-2.1.2-2.fc22.noarch requires python-psutil >= 0:2.0.0 [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) >= 0:0.16.0 [iwhd] iwhd-1.6-11.fc22.i686 requires libmongoclient.so [juffed] juffed-plugin-terminal-0.10-10.fc22.i686 requires libqtermwidget.so.0 [kdegraphics] 7:kdegraphics-4.14.3-1.fc22.noarch requires gwenview >= 0:4.14.3 [kmid2] kmid2-2.4.0-7.fc22.i686 requires libdrumstick-file.so.0 kmid2-2.4.0-7.fc22.i686 requires libdrumstick-alsa.so.0 [leiningen] leiningen-1.7.1-7.fc20.noarch requires maven-ant-tasks leiningen-1.7.1-7.fc20.noarch requires classworlds [libghemical] libghemical-2.99.1-24.fc20.i686 requires libf77blas.so.3 libghemical-2.99.1-24.fc20.i686 requires libatlas.so.3 [libopensync-plugin-irmc] 1:libopensync-plugin-irmc-0.22-7.fc20.i686 requires libopenobex.so.1 [ltsp] ltsp-client-5.4.5-8.fc21.i686 requires fuse-unionfs ltsp-server-5.4.5-8.fc21.i686 requires cdialog [meshmagick] meshmagick-0.6.0-20.svn2898.fc21.i686 requires libOgreMain.so.1.8.1 meshmagick-libs-0.6.0-20.svn2898.fc21.i686 requires libOgreMain.so.1.8.1 [monodevelop-vala] monodevelop-vala-2.8.8.1-6.fc21.i686 requires vala < 0:0.25.0 [netdisco] netdisco-1.1-7.fc21.noarch requires perl(SNMP::Info::Layer2::Bay) [nwchem] nwchem-openmpi-6.3.2-11.fc21.i686 requires libmpi_usempi.so.1 [openshift-origin-msg-node-mcollective] openshift-origin-msg-node-mcollective-1.18.0.1-2.fc21.noarch requires openshift-origin-msg-common [openslides] openslides-1.3.1-3.fc21.noarch requires python-django < 0:1.5 [openvas-client] openvas-client-3.0.3-8.fc20.i686 requires libopenvas_omp.so.6 openvas-client-3.0.3-8.fc20.i686 requires libopenvas_nasl.so.6 openvas-client-3.0.3-8.fc20.i686 requires libopenvas_misc.so.6 openvas-client-3.0.3-8.fc20.i686 requires libopenvas_hg.so.6 openvas-client-3.0.3-8.fc20.i686 requires libopenvas_base.so.6 [perl-RT-Authen-ExternalAuth] perl-RT-Authen-ExternalAuth-0.11-5.fc21.noarch requires rt3 perl-RT-Authen-ExternalAuth-0.11-5.fc21.noarch requires perl(:MODULE_COMPAT_5.18.2) [perl-RT-Extension-CommandByMail] perl-RT-Extension-CommandByMail-0.07-10.fc21.noarch requires perl(RT::Interface::Email) perl-RT-Extension-CommandByMail-0.07-10.fc21.noarch requires perl(:MODULE_COMPAT_5.18.2) [pipelight-selinux] pipelight-selinux-0.2.1-2.fc22.noarch requires pipelight-common pipelight-selinux-0.2.1-2.fc22.noarch requires pipelight-common pipelight-selinux-0.2.1-2.fc22.noarch requires pipelight pipelight-selinux-0.2.1-2.fc22.noarch requires pipelight [pootle] pootle-2.1.6-8.fc21.noarch requires python-django14 [python-askbot-fedmsg] python-askbot-fedmsg-0.1.0-2.fc21.noarch requires askbot [python-coffin] python-coffin-0.3.7-3.fc21.noarch requires python-django14 [python-django-addons] python-django-addons-0.6.6-2.fc21.noarch requires python-django14 [python-django-longerusername] python-django-longer
Re: Linux multi-boot release criterion discussion, redux
> > === > > > > When installing to a system containing an existing installation of > > either the same Fedora release or either of the two previous releases, > > the installer must configure the new installation's bootloader such that > > it can successfully boot the existing installation. > > > > [Footnote] Typical configurations only: This criterion applies only to > > installations (both existing and new) using default or very common > > storage and bootloader configurations. > > > > [Footnote] Platforms: This criterion applies to all supported > > configurations described in > > [[Fedora_21_Alpha_Release_Criteria#Release-blocking_images_must_boot|the > > Alpha criteria]], but does not apply to mixed configurations, e.g. it > > does not require that a UEFI native installation of one Fedora release > > be able to configure its bootloader to boot a BIOS native installation > > of another Fedora release. > > > > === > > > > How does that look? I think we had at least a consensus that this much > > was reasonable, and we have two bugs currently that would likely violate > > the proposed criterion: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=825236 > > https://bugzilla.redhat.com/show_bug.cgi?id=964828 > > > > I think it's reasonable to consider these blockers for F21, but we > > should justify it ASAP to give the devs sufficient time to fix them. > > I'm all for getting those bugs fixed, but making it an official > criterion is basically adding an anaconda requirement and a new feature > to the distro. Doing that at the end of a cycle isn't really okay, and > doing it without any mention on anaconda-devel-list or fedora-devel-list > for discussion isn't really that great, either. I'm in favor of adding such a criterion. And I agree it's too late for F21, so it should target F22. Of course, that doesn't preclude anaconda devs from best-effort to fix those bugs, if they have spare time. > > Also this criterion as written is going to bring in more than just those > two bugs - for example, right now we don't /really/ support two UEFI > Fedora installations on a single disk without the user making some > fairly strange choices, and when you do that, some things such as > fallback (which admittedly aren't in the criteria AFAIK) don't work. > > Fixing that would be a fairly substantial RFE, so either we need to have > language in any potential new criterion to accept the current conditions > (e.g. by requiring two separate disks to put an ESP on each), or we need > to plan on adding support for that before we apply any new criteria. I was about to mention the same, Fedora UEFI dual-boot requires a lot of manual tweaking at the moment, and I guess it's not something that can be changed and properly tested in a few weeks. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: installation matrix environment adjustments
> > 1. Testcase_Anaconda_User_Interface_Basic_Video_Driver was changed to > > a generic x86 test. In this case, it is problematic, because BIOS and > > UEFI fallback video driver are completely different code paths. I have > > a personal experience from that past when one of those worked and the > > other didn't. We should distinguish BIOS and UEFI in this case. To fix > > this, I see two viable options: > > > a) move the test case to Miscellaneous section, so that the table in > > User interface section doesn't get more complicated > > > b) keep the test case in User interface section, but create a separate > > table for it (right under the first table). This new table would have > > x86 BIOS and x86 UEFI columns. Again, the purpose is to keep the > > original table simple (avoid adding columns which are not required for > > anything else). > > The tests in that table are really covering somewhat different things, > now I look at them. Graphical, and Text actually exercise two of > anaconda's UIs (we seem to be missing a test for cmdline, unless one of > the other test cases hits it in passing). The others are different ways > of accessing those same UIs: the VNC tests are different ways to get at > graphical, and serial_console is another way to get at text. > > It makes sense for Graphical and Text to not be split between i686, > x86_64 and UEFI, for sure. And it makes sense for Basic Video Driver to > have probably x86 BIOS / x86 UEFI split, indeed. We should consider the > other tests in deciding the right thing to do - what's the appropriate > split for VNC and serial console? For VNC, we require the vnc binary (and networking) to work correctly. Of course there can be arch-specific bugs. But that's true for almost anything, we're working with likelihood-to-break-in-just-a-single-arch estimates here. From that POV, I think the test case is very similar to NFS/NFSISO repo testcase - again, you need the NFS binaries to work correctly. And we have just a single Result column for that. As I said, I don't feel well acquainted with ARM to guess which areas are more or less likely to work differently than on x86, and thus likely to contain arch-specific bugs. But I'd either keep current x86 & ARM separation, or unify that into a single test result, as with NFS. Serial console is likely to be more different between x86 and ARM than VNC (I seem to remember some ARM specific serial console bugs from this cycle), so the current separation seems reasonably there. Another question is whether we should keep the same approach for Text interface test case, or whether that can be united into a single result. Not sure here. > > > 2. Testcase_Install_to_Previous_KVM and > > Testcase_Install_to_Current_KVM differentiate BIOS and UEFI. I always > > forget whether this is about the host or the guest (or both, or which > > combination). But I think host differentiation doesn't make any > > difference - libvirt should work the same, I assume. It makes sense to > > differentiate the guests. Unfortunately I believe the UEFI mode for > > libvirt/kvm [2] is not available under an open source license, > > therefore it's not packaged and not trivial to use. Which means not > > that many people probably use it. I wonder whether we really need to > > keep this separated. I would gladly merge this together to a single > > x86 column and split up once OVMF is available under a better license. > > If we keep it separate, we should provide better instructions for the > > UEFI part. > > Well, the licensing issue is a bit subtle. OVMF itself is freely > licensed (BSD or MIT IIRC). The bit that has a license issue is the FAT > driver used by EDK II, on which OVMF is built. It has this extra term in > its license: > > Additional terms: In addition to the forgoing, redistribution and use > of the code is conditioned upon the FAT 32 File System Driver and all > derivative works thereof being used for and designed only to read > and/or write to a file system that is directly managed by Intel's > Extensible Firmware Initiative (EFI) Specification v. 1.0 and later > and/or the Unified Extensible Firmware Interface (UEFI) Forum's UEFI > Specifications v.2.0 and later (together the "UEFI Specifications"); > only as necessary to emulate an implementation of the UEFI > Specifications; > and to create firmware, applications, utilities and/or drivers. > > which obviously makes it non-free. I believe the *reason* is something > to do with Microsoft patent(s) believed to be related to FAT, and I > don't think it's prudent to say anything more specific than that. > > There therefore isn't a legal issue with redistributing OVMF builds, and > there is a commonly-used repository which contains them, updated daily: > > https://www.kraxel.org/repos/ > > they just can't go into Fedora, because of Fedora's policies about > non-freely-licensed software. It's pretty easy to set up a UEFI KVM > using the packages from that repo, I have o
Re: Resume still broken on Thinkpad X1 Carbon
I guess that there are lots and lots people at Red Hat with Lenovo laptops (few or them must be X1 and T440) so this is trivial for them to test. Guys/galls please help us out. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Resume still broken on Thinkpad X1 Carbon
Instead of opening a new thread I'll just jump in here because I have Lenovo T440s and same or at least similar issue. I tried doing suspend/resume on both Fedora 21 Alpha and now on Beta and it is not working on T440s. When I read Jonathans comment I immediately recognised same issue that I have: " - Under F21, suspend seems to work fine, but there is no response to the power button (or any other input). One has to hold the power button until the firmware gets fed up and powers things down hard." But after a bit closer inspection this is not true, actually I get some reaction when pressing power button - I can hear that cpu fan starts to work, but machine is still in suspend state - power button is blinking, monitor is off, only cpu fan is working. Jonathan can you check if your fan also starts up? I have installed all updates, what else can I do? On Mon, Nov 10, 2014 at 7:14 AM, Igor Gnatenko wrote: > After one of updates resume was broken. Now it's working for me > > On Tue, Nov 4, 2014 at 5:17 PM, Jonathan Corbet wrote: >> Just FYI, I tried out the F21 beta image in the vain hope that my resume >> problems would have magically gone away. No such luck. In case anybody >> is interested, here is what (little) I know... >> >> - Resume works great under F20. >> >> - Under F21, suspend seems to work fine, but there is no response to the >>power button (or any other input). One has to hold the power button >>until the firmware gets fed up and powers things down hard. >> >> - The kernel doesn't seem to matter; running an F20 kernel with F21 user >>space still fails. >> >> - Booting with init=/bin/bash produces a system that will not resume >>under either release; it fails in pretty much the same way. >>Single-user mode, instead, resumes properly under F20. So some sort >>of setup is happening that enables proper resume, but only on F20. >> >> - Running the F21 udev configuration on an F20 system still resumes >>properly. >> >> - As far as I can tell, the configuration of wakeup events, as found in >>sysfs, is the same on both systems. >> >> I'm pretty well mystified, but, given my general lack of skills in this >> part of the system, that's not surprising. My next step, perhaps, is to >> start disabling boot-time unit files until I find the one that makes >> resume work, then try to see what's different under F21. But if anybody >> has a better idea, I'm all ears. >> >> Thanks, >> >> jon >> -- >> test mailing list >> test@lists.fedoraproject.org >> To unsubscribe: >> https://admin.fedoraproject.org/mailman/listinfo/test > > > > -- > -Igor Gnatenko > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
