Re: Boot issue, probably with grub and maybe mdraid
On Wed, Jan 18, 2023 at 12:18:30 -0600, Bruno Wolff III wrote: On Tue, Jan 17, 2023 at 18:37:20 -0600, Bruno Wolff III wrote: Today one of three machines failed to boot 6.2.0-0.rc4. The machine that failed had not been rebooted in a week and now won't boot any kernel and it appears grub is aborting with a pointer out of range error. All three machines use ext4 and luks, but only the failing I filed bug 2162113 about this issue, though I'm good for now after running grub2-install. ___ 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: Boot issue, probably with grub and maybe mdraid
On Tue, Jan 17, 2023 at 18:37:20 -0600, Bruno Wolff III wrote: Today one of three machines failed to boot 6.2.0-0.rc4. The machine that failed had not been rebooted in a week and now won't boot any kernel and it appears grub is aborting with a pointer out of range error. All three machines use ext4 and luks, but only the failing machine uses mdraid. I haven't recovered the failing machine yet, but plan to downgrade grub tomorrow and hope that confirms a grub bug by allowing it to boot. If so, I'll file a bug report. Running grub2-install in a live image fixed this. I'm not sure if this is a bug or if people are expected to do this themselves (before rebooting) because there are issues trying to automate this for legacy systems. It might be that the scripts to do updates don't pull the correct devices when /boot is on raid. It is very annoying though when this happens. ___ 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: Boot issue, probably with grub and maybe mdraid
On Tue, Jan 17, 2023 at 18:37:20 -0600, Bruno Wolff III wrote: Today one of three machines failed to boot 6.2.0-0.rc4. The machine that failed had not been rebooted in a week and now won't boot any kernel and it appears grub is aborting with a pointer out of range error. All three machines use ext4 and luks, but only the failing machine uses mdraid. I haven't recovered the failing machine yet, but plan to downgrade grub tomorrow and hope that confirms a grub bug by allowing it to boot. If so, I'll file a bug report. I'm wondering if anyone else saw this and/or if they think there might be a different issue I should be looking for? On these machines /boot is not encrypted, so likely luks isn't a factor in the issue. ___ 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
Boot issue, probably with grub and maybe mdraid
Today one of three machines failed to boot 6.2.0-0.rc4. The machine that failed had not been rebooted in a week and now won't boot any kernel and it appears grub is aborting with a pointer out of range error. All three machines use ext4 and luks, but only the failing machine uses mdraid. I haven't recovered the failing machine yet, but plan to downgrade grub tomorrow and hope that confirms a grub bug by allowing it to boot. If so, I'll file a bug report. I'm wondering if anyone else saw this and/or if they think there might be a different issue I should be looking for? ___ 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: [Test-Announce] Fedora 37 Rawhide 20220517.n.0 nightly compose nominated for testing
On Tue, May 17, 2022 at 09:41:26 +, rawh...@fedoraproject.org wrote: Announcing the creation of a new nightly release validation test event for Fedora 37 Rawhide 20220517.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan I had a problem booting with the latest systemd. It looks like the problem might be related to luks support. I have filed a bug report for it. (https://bugzilla.redhat.com/show_bug.cgi?id=2087225) I ended up using a live image to downgrade systemd to fix things. Since / was mounted despite the problems mounting other encrypted file systems, it probably could have been recovered in the emergency mode if I hadn't made things a bit worse while testing things. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
IRC link for kernel test day uses freenode
Currently the irc link on https://fedoraproject.org/wiki/Test_Day:2021-07-11_Kernel_5.13_Test_Week points to irc://irc.freenode.net/#fedora-test-day . I think that it should probably be updated to point to librechat, but I'm not sure enough to make the change myself. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Can dxvk be turned on/off per app?
On Fri, Aug 14, 2020 at 10:54:50 +0200, Frantisek Zatloukal wrote: I pushed the 1.7.1 into F34-F31 just moments ago. You can grab the rpms from koji or wait till tomorrow (or whenever we get another F33/34 compose). I tried it and Sins still doesn't start and Heroes of Might and Magic III and Empire Earth seem to still work normally, but I didn't try much out in the games. I made a couple of scripts to use alternatives to set and unset whether dxvk is used so I can quickly switch. ___ 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: Can dxvk be turned on/off per app?
On Fri, Aug 14, 2020 at 09:31:57 +0200, Frantisek Zatloukal wrote: On Fri, Aug 14, 2020 at 4:50 AM Bruno Wolff III wrote: The next dxvk enhancement for wine broke Sin of the Solar Empire - Rebellion (GoG's version) for me, but works for some other games. Right now I've turned it off for everything, but I'd like to only turn it off for games that have a problem. Can you please go ahead and report the issue to DXVK developers? https://github.com/doitsujin/dxvk/issues I'm not interested in creating a github account and it looks like one is required to report problems. Unfortunately, enabling/disabling dxvk from default installation per application is not possible. Thanks for that answer as it keeps me from spending time trying to make dll overrides work when it isn't possible in this case. In these cases, the only option would be to uninstall dxvk and then install/enable it from official sources. Or, if you're having problems with only few applications/games, you can use lutris to launch them with different (dxvk-less) versions of wine. I ended up using alternatives to disable dxvk as I was worried about the packages getting pulled in again later. I'm running rawhide and I had this get pulled in during a routine update so I wasn't sure if it would get pulled in another update later. Sins is the heaviest graphics game that I play, so I don't think I'll need it for performance reasons for other games at this time. I would have been interested in trying it out on a couple of more games. If I end up wanting to do that, it looks like writing a couple of scripts that use alternatvies to turn it on and off wouldn't be hard. And would be faster than installing and uninstalling the dxvk packages and simpler than keeping multiple versions of wine around. I'll be keeping an eye on it though, as Sins does slow down in the end game. I think this has more to do with tracking objects than rendering them, but if it does help, I'll want to use it. I expect I'll test 1.7.1 as soon as it is convenient, as that is supposed to have a lot of fixes. Thanks for getting dxvk into Fedora. ___ 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
Can dxvk be turned on/off per app?
The next dxvk enhancement for wine broke Sin of the Solar Empire - Rebellion (GoG's version) for me, but works for some other games. Right now I've turned it off for everything, but I'd like to only turn it off for games that have a problem. I looked at the feature page and there doesn't seem to be much help there for people who have problems other than uninstalling it. Alternatives was mentioned without examples, which was enough to help me turn it off with that so that it didn't get reinstalled later and break things. But I'm hoping there is a way to do overrides using winecfg, but I'm not sure how to specify the overrides. ___ 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: some Rawhide feedback
On Fri, Apr 10, 2020 at 21:30:41 -0500, David wrote: Today's update seemed to go smoothly. I think I would call this a typical minor update that happens about twice a week, or maybe three times per week ? Normally there is a new compose daily. You can look at the recent ones at: https://kojipkgs.fedoraproject.org/compose/rawhide/ If you look at the status file, the ones that say 'DOOMED' failed to complete and were not made available to update from. ___ 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: system upgrade problems
On Sun, Feb 09, 2020 at 20:46:06 +, George R Goffe via test wrote: Stan, Thank you very much for your response... AND the information. I guess I'll just wait and see what happens. I have seen some of these problems for several months though I haven't been tracking them. What I do is use dnf distro-sync -b --allowerasing. I also keep track of which packages get removed and try to add them back the next time I update stuff. I could use some better scripts for doing this, than I have right now. But the general process works well. ___ 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
CI Wrapper tests
I am trying to get a wrapped test script to work for squashfs-tools and the artifacts don't appear to be properly saved. I think I might be misunderstanding the wrapper example. Is the idea really that the test should run ansible with the basic role referring to the wrapper? I have been trying to run the wrapper as the test and it runs the shell script, but the test results don't end up where the CI can find them and the test fails. I also don't see a way for the wrapper to ask for extra packages other than to run dnf in the script. There is stuff to look at in the pipeline pages if you want to see what I tried to do. ___ 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
Heads up, systemd-240-4 might cause problems
I went from 240-2 to 240-4 on one machine today (I have another that doesn't work with 240 at all with different symptons.) and it looks like dbus probably was broken. I couldn't use Xfce or Gnome after rebooting, but Lxde still was usable. Downgrading systemd fixed things. Bug 1666083. ___ 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
Rawhide dnf issue recovery
In case anyone else had dnf segflaulting on update recently. The current (in rawhide) set of dnf packages fixes the problem. You can use the distro-sync command to do the update instead of the update command. It is quite possible no one else saw this as it only happened on one machine and I never tracked things back to the update / plugin that caused the issue. Since the recovery is easy, but might not occur to someone to try, I wanted to mention it. ___ 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: Cairo 1.15.12-1.fc29 has a serious regression
On Sun, Apr 15, 2018 at 08:21:51 -0500, Bruno Wolff III wrote: Cairo 1.15.12-1.fc29 has broken bino and gmplayer at least and likely other things. 1.15.10-5.fc29 still works fine. Bug 1567611: https://bugzilla.redhat.com/show_bug.cgi?id=1567611 It turns out this also blocks graphical boots. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Cairo 1.15.12-1.fc29 has a serious regression
On Sun, Apr 15, 2018 at 18:07:41 +0200, Kalev Lember wrote: On 04/15/2018 03:21 PM, Bruno Wolff III wrote: Cairo 1.15.12-1.fc29 has broken bino and gmplayer at least and likely other things. 1.15.10-5.fc29 still works fine. Bug 1567611: https://bugzilla.redhat.com/show_bug.cgi?id=1567611 I can't seem to reproduce this with the cairo 1.15.12 build that's in fc28. I just use rawhide for my machines. It is certainly possible that the actual bug isn't in cairo, but rather one of the font packages, and the fresh cairo build picked up the problem from them. Possibly there was an API change. FT_Done_MM_Var has something to do with freetype. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Cairo 1.15.12-1.fc29 has a serious regression
Cairo 1.15.12-1.fc29 has broken bino and gmplayer at least and likely other things. 1.15.10-5.fc29 still works fine. Bug 1567611: https://bugzilla.redhat.com/show_bug.cgi?id=1567611 ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Packages that are failing dependencies or blocked by other packages in rawhide / F28
On Wed, Feb 28, 2018 at 11:49:59 -0700, stan wrote: When I run dnf update the follow problems show up before it tells me that there is nothing to do. I've only been able to run 1 update since Feb 4. It was huge, 11 GB, and took forever. I'm not even sure if I'm on rawhide or F28. Yet I see that milestones are being passed, and everything is on course for release of F28. Is it just that my repos are lagging? Composes are not suceeding very often. The latest was on the 20th. You can use: dnf distro-sync --best --allowerasing to try to update your system. This will remove some packages that you might not want to remove right now, so review the list before telling the command to continue. Otherwise an update will update as much as can be now without removing things and eventually the conflicts should be resolved. If you really need for something in particular to get updated there may be other options, but generally you don't want to go down those paths. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Kernel 4.15 Test Day 2018-02-22
On Wed, Feb 21, 2018 at 13:22:27 -0500, Sumantro Mukherjee wrote: Hey All, This is a gentle reminder.We have the Kernel 4.15 Test Day[1] coming up. As discussed at Flock 2017, we will start hosting test days for each major kernel rebase (approximately every 10 weeks). As the Kernel 4.15 has just released, we would like to get a test day done before we push the rebase to stable releases. [1]https://fedoraproject.org/wiki/Test_Day:2018-02-22_Kernel_4.15_Test_Day The performance test isn't running on rawhide. (But the kernel there is already 4.16-rc2. (Maybe there is an unlisted package dependency.) ./runtests.sh -t performance No .config file found. You can cp config.example .config and edit as needed for easier log submission Test suite called with performance In file included from lib_tcp.c:9: bench.h:38:10: fatal error: rpc/rpc.h: No such file or directory #include ^~~ compilation terminated. gmake[2]: *** [Makefile:244: ../bin/x86_64-linux-gnu/lib_tcp.o] Error 1 make[1]: *** [Makefile:114: lmbench] Error 2 make: *** [Makefile:20: build] Error 2 In file included from lib_tcp.c:9: bench.h:38:10: fatal error: rpc/rpc.h: No such file or directory #include ^~~ compilation terminated. gmake[2]: *** [Makefile:244: ../bin/x86_64-linux-gnu/lib_tcp.o] Error 1 make[1]: *** [Makefile:114: lmbench] Error 2 make: *** [Makefile:23: results] Error 2 ./performance/lmbench3 PASS Test suite complete PASS ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Is the 28 rawhide repo broken?
On Thu, Feb 15, 2018 at 18:54:43 +, George R Goffe wrote: Hi, I haven't seen updates from the rawhide repo in over a week. Is it that the "freeipa" situation clogging things up? Thanks, George... There hasn't been a fully successful compose since the 4th. The tentative ones almost always produce a repo suitable for updates. Right now there are some conflicts from what looks like a poppler upgrade. There were also more failures than usual for the gcc 8 mass rebuild. The rawhide composes are accessible at: https://kojipkgs.fedoraproject.org/compose/rawhide/ I'm using the following for using the one from this morning: (You might not want to disable gpgcheck or sslverify though.) [compose] name=Compose - Specific compose repo failovermethod=priority #baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/$basearch/os/ #mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=rawhide&arch=$basearch baseurl=https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20180215.n.0/compose/Everything/x86_64/os/ enabled=1 gpgcheck=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch sslverify=False ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Rawhide XFCE problems?
On Wed, Jan 17, 2018 at 14:03:02 -0800, Adam Williamson wrote: On Wed, 2018-01-17 at 15:53 -0600, Bruno Wolff III wrote: On Fri, Jan 12, 2018 at 14:25:36 -0600, Bruno Wolff III wrote: > > I was able to recreate the problem while upgrading and am in the > middle of doing a sort of bisect to get identify the problem package. > Once I do, I'll file a real bug report. I isolated this to m17n-db and filed bug 1535672. https://bugzilla.redhat.com/show_bug.cgi?id=1535672 Nice debugging work, Bruno! It hasn't been enough for other people to reproduce yet. I still don't know why it affects only one of the two machines I use with desktops. They are both x86_64. I may need to play with this on an older laptop that is currently using i686, but that I have been meaning to move to x86_64. I can at least get it up to date and do a quick check to see if it is affected using i686. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Rawhide XFCE problems?
On Fri, Jan 12, 2018 at 14:25:36 -0600, Bruno Wolff III wrote: I was able to recreate the problem while upgrading and am in the middle of doing a sort of bisect to get identify the problem package. Once I do, I'll file a real bug report. I isolated this to m17n-db and filed bug 1535672. https://bugzilla.redhat.com/show_bug.cgi?id=1535672 ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Rawhide XFCE problems?
On Thu, Jan 11, 2018 at 13:55:40 -0600, Bruno Wolff III wrote: Rolling back to Fedora-Rawhide-20171230.n.1 fixed the problem. I downgraded a bit over 1000 packages in that process. I'll work on slowly moving forward see if I can narrow things down, but it probably won't be quick. I was able to recreate the problem while upgrading and am in the middle of doing a sort of bisect to get identify the problem package. Once I do, I'll file a real bug report. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Rawhide XFCE problems?
Rolling back to Fedora-Rawhide-20171230.n.1 fixed the problem. I downgraded a bit over 1000 packages in that process. I'll work on slowly moving forward see if I can narrow things down, but it probably won't be quick. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Rawhide XFCE problems?
On Fri, Jan 05, 2018 at 10:30:17 -0600, This problem didn't happen on my home laptop, so it isn't a general XFCE issue. I need to look into this more on my end. I'm seeing random crashes of applications when using a few different desktops, but not with gnome and not in VTs. The crashes don't always happen, just most of the time. If I keep starting the terminal app, eventually it will start. Once started it keeps running. Selinux status (enforcing, permissive or disabled) doesn't apper to matter. This happens on a Intel(R) Xeon(R) CPU E5-1603 v3 @ 2.80GHz, but not on an Intel(R) Core(TM) i7-2677M CPU @ 1.80GHz. I don't really know if this is a hardware difference or if some cache didn't properly get rebuilt during an update. I did try reinstalling all of the packages on the machine having problems and that didn't fix things. So far I haven't identified any obvious package updates that could be linked to the problem. I did see the problem on an rc4 kernel that didn't have the problem earlier, so I don't think it is do to a recent kernel update. Running firefox or seamonkey from a terminal window (once I get one) results in crashes, though core files aren't currently being saved. (At least not in my home directory.) As an example I get this from firefox: [bruno@cerberus ~]$ firefox ExceptionHandler::GenerateDump cloned child 7260 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... And for seamonkey: [bruno@cerberus ~]$ seamonkey Segmentation fault (core dumped) lynx and mutt work in the terminal window, so there seems to be some connection to graphics. I have a radeon video card: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland GL [FirePro W2100] 03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Rawhide XFCE problems?
On Thu, Jan 04, 2018 at 11:56:31 -0600, Bruno Wolff III wrote: Is anyone having problems running stuff in XFCE on Rawhide, probably starting within the last two days, maybe after a reboot? Gnome seems to work normally. I'm trying to guess what to revert and it's a pain to just do the whole lot on rawhide since old packages drop out of the repo right away. I was hoping someone else had already figured out what needed to be reverted. This problem didn't happen on my home laptop, so it isn't a general XFCE issue. I need to look into this more on my end. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Rawhide XFCE problems?
On Thu, Jan 04, 2018 at 13:20:07 -0500, Matthew Miller wrote: On Thu, Jan 04, 2018 at 11:56:31AM -0600, Bruno Wolff III wrote: Is anyone having problems running stuff in XFCE on Rawhide, probably starting within the last two days, maybe after a reboot? Gnome seems to work normally. I'm trying to guess what to revert and it's a pain to just do the whole lot on rawhide since old packages drop out of the repo right away. I was hoping someone else had already figured out what needed to be reverted. Can you be more specific about "problems running stuff"? Several programs that are in my session start list (firefox, thunderbird, pidgin, rhythmbox, xfce terminal) don't get started. Manually starting stuff doesn't work either. I get an error message: Failed to execute default Terminal Emulator. Input/outout error. Logging out works. Switching to VTs works. SELinux status doesn't appear to matter. I haven't had a chance to test it at home yet. Things were working when I left, but I didn't do a reboot after updating to today's rawhide. I didn't see it at work until after I rebooted (though I didn't test logging out and back in before the reboot). I rebooted Tuesday, so it was probably an update for something in today's or yesterday's rawhide updates. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Rawhide XFCE problems?
Is anyone having problems running stuff in XFCE on Rawhide, probably starting within the last two days, maybe after a reboot? Gnome seems to work normally. I'm trying to guess what to revert and it's a pain to just do the whole lot on rawhide since old packages drop out of the repo right away. I was hoping someone else had already figured out what needed to be reverted. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Fedora crash reports: up in f24 over f23 when normalized to number of installed systems
On Thu, Sep 22, 2016 at 16:50:43 -0400, Matthew Miller wrote: We probably _can_ -- the data is there. Just need to find a way to show it that brings out that answer. Maybe instead of counting number of reports, count number of packages with reports each day and compare; that'd show if it's general or specific crashyness. I know Festival is a problem and I am probably not going to have time to fix it. Given the machine with my digium card has died, my incentive for wanting Festival has dropped. It also really needs to get updated, which will be a significant amount of work. Given its current state we should probably retire it before f25 beta unless someone wants to try to work on it. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: only installing F24 release sets sytem time to USA eastern time
On Wed, Jun 22, 2016 at 14:42:43 +0200, David Novák wrote: Hi, will there be release of updated images of F24? Sometimes third parties make them, but not official ones (except I think for atomic). You can make your own fairly easily using livemedia-creator. You'll need to manually apply the fix to the live base kickstart file. (Even in rawhide, the package hasn't been updated yet, only the repo used for official builds.) I do sometimes do an update of the spin-kickstarts after a release, but usually only if there is an important bug or multiple bugs being fixed. Currently, I think this one is more in the annoying category, than important category, but I could be convinced otherwise. I also don't like to rush a build right away, but rather wait for multiple fixes to accumulate. With agure in the mix now, people might be less likely to do updates to the f24 branch after release than we used to see if the past. Not much has changed since I did the last rawhide build either. The only other change so far are some tweaks to the games on the games spin. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: only installing F24 release sets sytem time to USA eastern time
On Tue, Jun 21, 2016 at 14:07:09 -0400, Joerg Lechner wrote: Hi, there is an -I think- open bug " [Bug 1018162] only testing LIVE CD, changes system time in BIOS ", in this error system time was set to UTC. Just installed the release version Workstation (6.2) after a fresh download according to the release link. I installed F24, shut down the Live Media on usb and started immediately Windows 8.1. My system time in UEFI or BIOS is now set 6 hours back, in my case from MEZ (middle European Time) to eastern North American Time. This effect is new. Shall I file another bug, or comment Bug 1018162? What's best? This got fixed in rawhide, not f24, because I fixed it too late. If you are building your own images you can look at the fix in the master branch and apply it yourself. For released images it is too late. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Propose for onbaording session for new contributors
On Mon, Jun 20, 2016 at 18:17:11 +0200, moon wrote: https://openmeetings.apache.org/ I never used it so I don't know how it is, but it can hardly be any worse than hangouts I think for very the short term, doing what is easist to get something to actually happen, is what is most important. Right now there are a lot of new people and there is already momentum, which we don't want to kill. Also having experience with a real intro meeting will help us make good decisions about what we should do longer term. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: F24 - ncsvc VPN doesn't work any more
On Tue, May 10, 2016 at 09:53:10 +0100, Ankur Sinha wrote: Any tips on how to debug this? The ncsvc thing is the same - the change here is F24. To start, I think you want to try to narrow down the issue. You want to see if the routing is working correctly. If the routing appers to be working, then you want to check dns resolution. -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: F24 Beta status
On Wed, Apr 27, 2016 at 09:13:36 -0700, Adam Williamson wrote: So please expect the RC to arrive in the next several hours, if all goes well, and be ready to test :) It won't be super different from the current nightly, but we'll at least need to do sanity testing and make sure we cover the few Beta tests which have not been run recently. How are the semi-random livemedia compose failures (https://bugzilla.redhat.com/show_bug.cgi?id=1315541) going to be handled? -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Hardware clock being set again by live images
We have an old bug https://bugzilla.redhat.com/show_bug.cgi?id=297421, which was never closed, but looks like it should have been, for the hardware clock being set by live images on shutdown. This problem is happening again. Some things have changed for what happens for ntp support and I suspect this broken the live image hack we put in, way back when. I'm not sure if we want to ressurect the old bug or file a new one (and close the old one)? -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Did luks get broken in f24?
On Tue, Mar 01, 2016 at 16:44:51 -0600, Bruno Wolff III wrote: Thanks. I re-try tonight, as maybe I got really unlucky with bad typing with the latest kernel and the got it right on the first try with the older kernel. I can also rebuild the initramfs image and see if that helps. I retried this and things worked, so it looks like I was just unlucky. -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Did luks get broken in f24?
On Tue, Mar 01, 2016 at 17:21:17 -0500, Chuck Anderson wrote: On Tue, Mar 01, 2016 at 01:41:22PM -0600, Bruno Wolff III wrote: I updated my kernel this morning and my disk password doesn't seem to work when booting with that kernel (multiple tries), but did work with the previous kernel. Is this perhaps glibc fallout with dracut? FWIW, on F25 (rawhide, not branched) I updated/rebooted kernel/glibc/etc. this morning and my laptop with LUKS still works. I didn't have to jump through hoops with dracut, but I did have to install glibc-langpack-en in order for gnome-terminal to work. Thanks. I re-try tonight, as maybe I got really unlucky with bad typing with the latest kernel and the got it right on the first try with the older kernel. I can also rebuild the initramfs image and see if that helps. -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Did luks get broken in f24?
I updated my kernel this morning and my disk password doesn't seem to work when booting with that kernel (multiple tries), but did work with the previous kernel. Is this perhaps glibc fallout with dracut? -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Postgres and glibc change heads up
The recent glibc change resulted in language packs being seperated and by default none of them were intsalled. This breaks the postgres server in you used anything but the C locale for a database. You can fix things by installing the appropriate language pack (e.g. glibc-langpack-en) or all language packs (glibc-all-langpacks) and restarting postgres (systemctl restart postgresql). -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Fedora Rawhide 20160212 compose check report
On Fri, Feb 12, 2016 at 21:25:56 +0100, Adam Williamson wrote: On Fri, 2016-02-12 at 19:44 +, Fedora compose checker wrote: Failed openQA tests: 16 of 63 32-bit tests are still failing to boot, still kernel issue there. I suspect the real issue is with binutils rather than the kernel. -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Did bugzilla's redirect checking get more strict in the last few days?
On Fri, Nov 06, 2015 at 15:18:29 -0600, Bruno Wolff III wrote: I am unable to login to bugzilla today and I think it is because the redirect test has gotten stricter but I am not sure. I saw this happen months ago with a direct bookmark, but I only had to try a second time. Now I keep getting sent back to unable to trust my login attempt page, so I think some new test got added. This appears to have been a change in Firefox's whitelisting for cookies. In the past you just gave a domain name, but now it also seems to track connection type or perhaps port. While some of my entries ended up being associated with https connections, my bugzilla one got associated only with http connections, which is what broke authentication. White listing https://bugzilla.redhat.com got things working again. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Did bugzilla's redirect checking get more strict in the last few days?
I am unable to login to bugzilla today and I think it is because the redirect test has gotten stricter but I am not sure. I saw this happen months ago with a direct bookmark, but I only had to try a second time. Now I keep getting sent back to unable to trust my login attempt page, so I think some new test got added. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Odd changes in compose sizes
This release I have been seeing a lot of bouncing around in games spin sizes, even when there aren't changes that would seem to explain things. Other than one image being over the target size eariler in the process, this hasn't broken things, but it still seems odd. For example for RC6 the i686 image was roughly 130 MB bigger than the x86_64 image, but for RC9 things flip flopped and the x86_64 image was roughly 130 MB bigger than the i686 image. I wouldn't have expected any significant size change for the games spin between RC6 and RC9. So I think something weird is going on. I don't have a lot of time right now to figure out the root cause of this, but I'll keep a lookout for it in F24. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 23 Final Release Compose 2 (RC2) Available Now!
On Wed, Oct 21, 2015 at 18:30:02 -0700, Adam Williamson wrote: valuable, but there's no need to go all out. At present I'm expecting we'll build an RC3 tomorrow and focus on testing that really thoroughly over the next 7 days (and any further RCs that turn out to be necessary). Is the new build going to use the same spin-kickstarts commit? There has been an arm related commit since the commit used for rc2. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Call for testing: 32-bit AMD CPU owners
On Wed, Sep 16, 2015 at 14:17:13 -0500, Bruno Wolff III wrote: I have a dual MP system as my main desktop at home. I rebooted it a couple of times this week with rawhide nodebug kernels (the base system is rawhide) and haven't had a problem. It won't boot from flash drives and I was unable to burn a good DVD tonight. I'll try burning on another machine tomorrow and see if I can at least read a DVD still late tomorrow night. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Call for testing: 32-bit AMD CPU owners
On Wed, Sep 16, 2015 at 12:08:15 -0700, Adam Williamson wrote: If anyone reading this has an old 32-bit AMD system - the last range of 32-bit AMD CPUs was the Athlon XPs from early 2003, anything 'Athlon 64' or later is 64-bit - and it's not too much trouble, could you please grab a 23 Beta RC1 32-bit image and try booting it? Here's how you can do it, assuming you want to write to a USB stick '/dev/sdc' (adjust for your USB stick's device node): I have a dual MP system as my main desktop at home. I rebooted it a couple of times this week with rawhide nodebug kernels (the base system is rawhide) and haven't had a problem. wget https://dl.fedoraproject.org/pub/alt/stage/23_Alpha_RC1/Server/x86 _64/iso/Fedora-Server-netinst-x86_64-23_Alpha.iso Didn't you want i686 tested instead of X86_64 tested? Presumably you also want beta rc1 tested rather than alpha rc1? su dd if=Fedora-Server-netinst-x86_64-23_Alpha.iso of=/dev/sdc I'll try this tonight. I don't remember if it boots off of USB devices. If not I'll burn a DVD and test that. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: dl.fedoraproject.org rsync broken most of the day
On Tue, Aug 18, 2015 at 21:36:11 -0500, Bruno Wolff III wrote: I have been getting rsync errors from dl.fedoraproject.org since this morning. Things are working again this morning. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
dl.fedoraproject.org rsync broken most of the day
I have been getting rsync errors from dl.fedoraproject.org since this morning. rawhide-nodebug hasn't been updated and I was able to grab other stuff from mirrors that may have gotten today's updates before the problems started. The error I am seeing is: rsync: safe_read failed to read 1 bytes [Receiver]: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(276) [Receiver=3.1.1] Accessing the files via http seems normal. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 23 Alpha Test Compose 2 (TC2) Available Now!
On Sat, Jul 25, 2015 at 21:48:36 -0700, Adam Williamson wrote: The games spin doesn't show up in either list, so it seems the compose wasn't even attempted for some reason; Dennis should be able to say what the deal is. My guess is that it was because when the ks renanes were done, it broke the games spin and I just fixed that a few days ago. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 23 Alpha Test Compose 2 (TC2) Available Now!
On Sat, Jul 25, 2015 at 20:30:25 -0700, Adam Williamson wrote: Somewhat later than scheduled [1], Fedora 23 Alpha Test Compose 2 (TC2) is now available for testing. Please help us complete as much of the validation testing as we can! Did the games spin not build or is it missing for some other reason? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Possibly problem with 4.2.0 kernel
On Sun, Jul 19, 2015 at 11:41:59 +0100, Russel Winder wrote: I should also note that it only affects the Intel video. If I force using the ATI Radeon video everything is fine. So the question is what have they done wrong with the Intel drivers? There have been fixes going in for the i915 driver. I have switched back to the 4.1 kernel on the affected machine, but will be trying rc3 kernel when a build is available. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Should generic-release issues block releases?
This is being post to remixes, test and devel since people on test and devel may not ordinarily be involved with remixes, but might want to comment. Replies have been pointed back to the remixes list (hopefully won't be munged) and you probably should join remixes temporarily if you want to follow this thread. In yesterday's QA meeting bug https://bugzilla.redhat.com/show_bug.cgi?id=1224561 was nominated as an f23 final blocker. The group wasn't sure of the impact this would have on remixes if it wasn't fixed before the release, so it was resolved to reject blocker status for now (and the bug was fixed today, so this is moot) and start a discussion with remix representatives. In this particular bug, it wouldn't have been possible to install anaconda and generic-release together on the same image. That might not actually effect many remixes. The other big question is, would fixing generic-release after the f23 release instead of blocking the release work for remixes. Do remixes generally use just the release versions of packages or do they pick up updates as well? The release criteria that was proposed that the bug violated the spirit of, but not the letter of is: Release identification A fedora-release package containing the correct names, information and repository configuration for a final Fedora release must be present on release-blocking images and the appropriately versioned generic-release package must be available in the release repository. It was thought that for bug 1224561 to be considered a release blocker, the above criteria would need to have been expanded to include some functional criteria for generic-release beyond it just be present, So what we are looking for is feedback from people doing remixes about what they really need and when they need it? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: conflict between latest fedora-release and systemd (rawhide)
On Thu, Jun 11, 2015 at 13:38:31 -0400, Stephen Gallagher wrote: It really *can't* be included in the same source RPM, because remixes wouldn't be able to ship the source, then. Has that been checked by legal? Having a trademarked image in a source file is different from displaying the trademarked image on a desktop or splash screen by default. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: conflict between latest fedora-release and systemd (rawhide)
On Thu, Jun 11, 2015 at 09:27:18 -0600, Kevin Fenzi wrote: On Thu, 11 Jun 2015 10:01:04 -0500 Bruno Wolff III wrote: That change also caused problems installing stuff with generic release that depend on lvm2. For example you can't build a generic live image that will have anaconda on it for live installs. Is there a bug? I'm not sure how that happened from this change... https://bugzilla.redhat.com/show_bug.cgi?id=1224561 I think the idea was to have product (edition) dependent presets, but I don't think the implementation was done well. No, the idea was to move presets from systemd that didn't want to have to change them to fedora-release that makes more sense and is controlled by more Fedoray folks who can make changes as needed. fedora-release seems to be getting more complicated. This makes it hard for generic-release to stay caught up as a separate package. I would like to see generic-release merged into the fedora-release source rpm so that it is easier to keep in sync, if that is possible to do while still solving the trademark problem it is meant to solve. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: conflict between latest fedora-release and systemd (rawhide)
Looks like somebody decided to move the 90-default.preset from systemd to the fedora-release package without changing the systemd package to reflect that and pushing out a new package (as discussed about a year ago). That change also caused problems installing stuff with generic release that depend on lvm2. For example you can't build a generic live image that will have anaconda on it for live installs. I think the idea was to have product (edition) dependent presets, but I don't think the implementation was done well. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 23 Rawhide 20150607 nightly compose nominated for testing
On Tue, Jun 09, 2015 at 23:50:55 -0700, adamw...@fedoraproject.org wrote: Announcing the creation of a new nightly release validation test event for Fedora 23 Rawhide 20150607. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: Some people will find https://bugzilla.redhat.com/show_bug.cgi?id=1212224 (SIGWINCH kills httpd) annoying. I have been having to run httpd manually for a couple of months now, to work around this. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Update FC22 - doesn't find root fs and doesn't boot
And already we have fought for this user's side simplification, but it seems developers are very persistent when they do not need to be. In the past changes with this effect were reverted. This time they were not. This generally just affects people upgrading, as anaconda has been adding the needed stuff on the kernel command line for a while now. You can also hostonly_cmdline=yes to the dracut config or set hostonly=no if you are willing to have a larger initramfs file. The latter will also help if you switch out hardware. I am not sure why hostonly_cmdline=yes is not the default when hostonly=yes. That would seem to be a better default. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Live media changes systemtime to UTC
On Sat, May 30, 2015 at 08:27:43 +1200, Gavin Flower wrote: On 30/05/15 04:59, Joerg Lechner wrote: Hi, I add this comment about F22 here, even when F22 is now distributed as final, because I think this problem will also occur in F23. When I load the F22 Final Live Medium (Workstation x86_64) via USB stick to the laptop the system time is permanently changed to UTC. The Live medium is produced via the F22 liveUSB Creator. There was a similar problem in F20 or F21, I don't remember exactly. Kind Regards The system should ALWAYS be in UTC (also known as GMT)! Arguably it should be TAI or GPS as leap seconds cause problems similar to DST changes in that it is hard to tell if the clock has been adjusted already after a change. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F22 Final testing - I'm away
On Fri, May 15, 2015 at 22:43:31 -0700, Adam Williamson wrote: On Fri, 2015-05-15 at 20:57 -0500, Bruno Wolff III wrote: Do we need a bug for getting a matching spin kickstart build into the release after the gold build but before release day? (I don't believe that any of the kickstart packages end up on media, but I haven't checked that.) Yes, we should have such a bug, it is a criterion requirement that a matching spin-kickstarts package be in the frozen package set for reproducibility reasons. Please file one and make sure dennis is CC'ed on it. roshi, make sure a spin-kickstarts package matching the git commit used for the final RC is pushed stable as part of the frozen final release tree - Dennis knows about this. I have created https://bugzilla.redhat.com/show_bug.cgi?id=148 for this. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F22 Final testing - I'm away
Do we need a bug for getting a matching spin kickstart build into the release after the gold build but before release day? (I don't believe that any of the kickstart packages end up on media, but I haven't checked that.) My memory is that that is what the process was last release. The build process is simple, but we need to know what commit was used by rel-eng to build the media. I don't remember if we used a freeze exception or a blocker, though the freeze exception seems more appropriate. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F22 Final: karma requests
On Mon, May 11, 2015 at 17:44:51 -0700, Adam Williamson wrote: * https://admin.fedoraproject.org/updates/FEDORA-2015-7721 (something for the Games spin, karma it if it runs - Note something odd happen with this one, probably because I edited it to add a second build. Bohdi said it was in testing, but the two packages weren't in the testing repo. I did an unpush and push to testing to get the rpms in testing, but you might need to grab the builds from koji. I'd like fish fillets (fillets-ng) to be one of the featured on the games spin web page. However, I found that the lua 5.2 fix for it didn't work and the program wouldn't start. Fortunately recebtly some made a lua 5.1 compat library and I was able to switch it to using that and it seems to work OK now. I need some independent confirmations that the change really works so I can get the fixed version on the games spin media. Thanks. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Rawhide not mashing?
Is there an estimate when rawhide composes will get fixed? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Yum SIGSEGV
On Sun, Mar 29, 2015 at 23:53:57 -0700, Adam Williamson wrote: On Sun, 2015-03-29 at 17:31 -0500, Dan Mossor wrote: Rawhide should be using DNF exclusively. Please try again using dnf and let us know the results from that. Not really. yum is still present and expected to be used, no-one's expecting the world to stop using yum overnight. If segfaults are happening, it's a problem. That being said, it's hard to tell much from just 'it segfaulted' - an abrt report would be better, if we can get one? This was actually an rpm bug and it has been fixed. Not all updates triggered the problem, so try updating or downgrading rpm* and then you should be OK. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] 2015-03-09 @ ** 15:00 ** UTC - Fedora QA Meeting
On Sat, Mar 07, 2015 at 00:10:31 -0800, Chuck Forsberg WA7KGX wrote: On 03/06/2015 11:16 PM, Adam Williamson wrote: Wine 1.7.38 reportedly fixes the ability to install Windows apps on 64 bit systems. The inability to load windows apps into wine is a profound defect. Fedora should ship with a wine that has useful functionality. There is a work around listed in https://bugzilla.redhat.com/show_bug.cgi?id=1192725#c7 that might help you. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
live image rebuilding linker cache
I was testing the games spin and saw that the boot was significantly slowed down because the dynamic linker cache was being rebuilt. It seemed odd that this would happen on a live image (why isn't it prebuilt) and that it would block the boot process. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 22 Branched 20150218 nightly compose nominated for testing
On Wed, Feb 18, 2015 at 12:46:31 -0800, Chuck Forsberg WA7KGX wrote: Wine seems to have been broken about the same time the kernel was bumped to 3.20. I was unable to load any of the usual apps with yesterday's snapshot. It may be just the latest wine update. I filed the following a few days ago: https://bugzilla.redhat.com/show_bug.cgi?id=1192725 Downgrading worked around the problem. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Heads up - Anaconda 22.17 will enforce 'good' passwords
On Wed, Jan 28, 2015 at 22:20:54 +, Andre Robatino wrote: down, they could forget it after the install, and be locked out. I was also wondering about ways to get around the password - for example if the disk isn't encrypted, or there's no bootloader password. Wouldn't anaconda need to enforce some of that as well, to be consistent? That depends on the threat model they are attemping to defend against. It may be that attacks requiring physical access are out of scope for their model. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Heads up - Anaconda 22.17 will enforce 'good' passwords
On Wed, Jan 28, 2015 at 08:53:42 -0800, "Brian C. Lane" wrote: I *know* this is going to be a bit of a pain to get used to. But the increased security is worth it. Super simple passwords will no longer be allowed, but it is still easy to come up with one that passes the checks. pwgen has lots of suggestions. As I mentioned in a related tgread, for people who need to do this a lot, a yubikey might be helpful. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Alpha criterion and major language related breakage?
On Wed, Jan 07, 2015 at 10:32:16 -0800, Adam Williamson wrote: Sure, it might be an idea to draft an Alpha criterion based on the Final one in that case... I'll do that. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Alpha criterion and major language related breakage?
We had a ticket come up in the blocker meeting today, where I got the feeling that people felt that any major breakage that was language dependent should be a blocker. We sort of fudged this into a blocker using a different criterion, but I think if that is the intent we should note that being able to use English as a work around isn't good enough. I don't know if we'd want to require all languages to work like in the final criterion, but it did seem that multiple languages not working for installation was considered to be a blocker issue for alpha. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: rawhide report: 20150104 changes
On Sun, Jan 04, 2015 at 10:08:05 -0800, Chuck Forsberg WA7KGX wrote: I tried today's install and still no graphics. Perhaps someone could figure out why rawhide hasn't come up in X for the last week or so (on real hardware). They have been testing mesa 10.5 for about about a week. That might be a good candidate to try to downgrade. (There are multiple mesa packages you'd want to downgrade as a group.) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What's with Rawhide?
On Mon, Dec 29, 2014 at 12:27:23 -0800, Rpmfusion has a rawhide repo but rawhide wants to see a Fedora 22 repo. Currently rpmfusion's rawhide repo is just a pointer to their f21 repo. This caused some problems a couple of weeks ago when ffmpeg couldn't work for both rawhide and f21 at the same time because of soname bump in a dependency. But thinmgs seem fine currently. Probably on new installs you are getting the default repos for an f21 install instead of rawhide. The repo files for both get installed and you can enable the rawhide ones and disable the others. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup f20->f21 kde broken deps
On Sat, Dec 13, 2014 at 11:48:00 +0100, Michael Schwendt wrote: But I claim that the ordinary user doesn't upgrade to updates-testing and doesn't want to upgrade to updates-testing due to some of the stuff that's dumped in there. Too many updates, too many packages updated too frequently. We could mitigate some of this by recommending that more updates (particularly the ones that aren't an upstream update) add to the release string after the distribution instead of before it. Doing it this way it doesn't matter if fixes for the older releases go to stable first. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 21 updates-testing question
On Fri, Dec 05, 2014 at 11:51:41 -0500, Gene Czarcinski wrote: I realize that once Fedora 21 is released, that some of the packages in the "current" updates-testing will be moved to updates, others will be discarded as OBE and the rest left in updates-testing for further testing. I realize that, at this point, nothing will change the Fedora 21 base but this could help with day-zero and day-one fixes. Now that RC5 is gold, the updates repository will be updated with packages pushed to stable. I am not sure how often there will be a push, but I would expect at least one today and one on Monday. (This is assuming there is stuff waiting to go to stable.) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: karma wanted: https://admin.fedoraproject.org/updates/xfdesktop-4.10.3-1.fc21
On Tue, Nov 18, 2014 at 19:17:15 +0100, poma wrote: On 18.11.2014 18:48, Kevin Fenzi wrote: Yeah I see you are stuck with the "4.12" mantra. Listen to Justin, perhaps you succeed to unshackle the mind ;) I think Kevin is correct. If people think it would be nice to have 4.12 available early, then I think using a copr is the appropriate way to do it. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Note on 'systemd-216-9'
On Tue, Nov 04, 2014 at 08:30:32 -0800, Adam Williamson wrote: systemd-216-8 (and 216-1 through 216-5) and earlier) was more or less identical to upstream systemd-stable 216: http://cgit.freedesktop.org/systemd/systemd-stable/log/?h=v216-stable . systemd "216-9" is not built from 216 at all, it is in fact systemd-217 with some particular changes (presumably intended to be the most There is a definite problem with 217 I have been seeing in rawhide. I am seeing an intermittent (very roughly 50% of boots) problem where copying logs to persistent storage hangs for a long time. This is described in: https://bugzilla.redhat.com/show_bug.cgi?id=1159641 Though I actually filed that bug because the debug-shell was shutting the system down. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 21 Beta Test Compose 4 (TC4) Available Now!
On Mon, Oct 20, 2014 at 10:28:02 -0500, Bruno Wolff III wrote: The way this was working was that if you did an excludes in a kickstart file (such as -generic-*) the excluded packages were not available to satisfy dependencies. However this is a relatively recent change and maybe something undid it. In the past packages that absolutely were not to be available to satisfy dependencies were excluded on the repo commands. I went back and looked at the ks files from f19 and it looks like we did carry forward the excludes for the install ks files and the live ks files didn't use them. The reason that the install ks files had the excludes and the live images didn't is that the install images were built with pungi which would bring in all packages that satisfied a dependency, whereas livecd-creator would only bring in what was necessary. So as long as the right packages were getting picked, the excludes weren't needed for composing live images. It is also possible that the repo commands were being overridden and some packages excluded in the overrides. It might just be with the next fedora-release-product packages being added, that the generic-release versions are getting preferred now, when they weren't previously. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 21 Beta Test Compose 4 (TC4) Available Now!
On Mon, Oct 20, 2014 at 10:01:32 -0400, Stephen Gallagher wrote: So, why does the depsolver suddenly start giving us generic-release instead of fedora-release? I'm not sure yet, but I have a theory - I believe fedora-release's dependency chain got longer, and that affects the depsolver's choice. In fedora-release-21-0.16, a requirement was added to fedora-release for 'system-release-product', which is provided by fedora-release-server, fedora-release-nonproduct etc. But 'generic-release' has no such matching requirement (nor do we in fact have a generic-release-server, generic-release-workstation, generic-release-nonproduct etc). So basically you get generic-release because it can satisfy the 'system-release' requirement with a shorter dep chain, because it doesn't also have to pull in a 'product' package to satisfy the 'system-release-product' dep. The way this was working was that if you did an excludes in a kickstart file (such as -generic-*) the excluded packages were not available to satisfy dependencies. However this is a relatively recent change and maybe something undid it. In the past packages that absolutely were not to be available to satisfy dependencies were excluded on the repo commands. And I think your analysis is spot-on. We haven't been keeping the generic-release-* stuff up to date (I think because it's maintained separately from the fedora-release-* stuff). Dennis, do you have any insight here? I know when we talked a few months ago, you were planning to try to bring these two upstreams together so we could avoid this sort of thing. Any word on that? I tried to take a stab at this when we needed a generic-release update for F20 (there was a change in how provides were handled that required changing generic-release to allow it to be used) and there was no source for some of the included files. generic-release is now significantly different from fedora-release and I think it would be better if they had some common upstream. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 21 Alpha karma requests
On Wed, Sep 10, 2014 at 18:45:05 -0700, Adam Williamson wrote: https://admin.fedoraproject.org/updates/FEDORA-2014-10190/python-blivet-0.61.1-1.fc21 - this one was in TC6, so if TC6 partitioning works for you (at least no worse than previous TCs), +1 it Would any successful install to hard drive from a live iamge be a good enough test, or would it need to involve custom partitioning? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Back to Fedora 20
On Sun, Aug 24, 2014 at 19:42:12 -0700, Chuck Forsberg WA7KGX wrote: I could not get httpd to run. It failed, complaining about not being able to identify its hostname and/or domainname. I started seeing this a few days ago but on omen.com it is a show stopper. I am seeing something that may be related for ssl. When I just ran non-ssl http daemons, things work. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Proposing new dual booting release criteria
On Sun, Aug 24, 2014 at 12:23:55 -0500, Michael Catanzaro wrote: I therefore propose some new release criteria, based on the consensus from the desktop list. It's possible that these new criteria will directly result in further significant delays to the release of F21, since there are four open bugs that would fall under these criteria, but harming the user's previous OS is so severe that we should block on them anyway. Fedora will not become widely popular if it remains dangerous to install. Is this criteria intended for final (as opposed to alpha or beta)? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: default kernel
On Mon, Aug 18, 2014 at 15:04:53 -0400, Tom Horsley wrote: On Mon, 18 Aug 2014 07:59:53 -0500 Bruno Wolff III wrote: Normally whether to use the lastest or previous kernel by default is set in /etc/sysconfig/kernel. Well, I finally got a chance to check that file and it says: UPDATEDEFAULT=yes DEFAULTKERNEL=kernel-core Not sure what the kernel-core setting means, but it definitely looks as if UPDATEDEFAULT=yes was ignored. If you were using a PAE kernel, it would have had kernel-PAE-core (or kernel-PAE). This matters if you have both PAE and non-PAE kernels installed. (Previously SMP kernels used to be available as well.) It says which varient should be used for the default boot. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: default kernel
On Mon, Aug 18, 2014 at 08:28:39 -0400, Tom Horsley wrote: There is all kinds of cryptic gibberish in grub.cfg dealing with the environment file and saved entries so I can't even tell exactly where the heck the default is coming from, but the default selected in the menu when I boot is the older kernel, so where ever it is coming from, it is the wrong choice :-). Normally whether to use the lastest or previous kernel by default is set in /etc/sysconfig/kernel. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Is anyone else seeing a problem with glibc 2.19.90-29.fc22 ?
On Mon, Jul 21, 2014 at 17:11:51 +0200, poma wrote: On 21.07.2014 14:03, Bruno Wolff III wrote: On Mon, Jul 21, 2014 at 11:27:35 +0200, poma wrote: Withd thisd breakaged ofd d logind byd d glibcd, d Rawhided i686d isd d literallyd busted! We'll fresh installs and live images are not really usable. If you already have rawhide installed and a root shell you can downgrade glibc. I do wish they'd untag that build if it isn't going to be fixed right away. Resolved. ;) https://bugzilla.redhat.com/show_bug.cgi?id=1121419#c6 Note that that copy of the bug is closed "Work's for me". The comment might be better in an open bug, or maybe that one should be reopened. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: rawhide report: 20140721 changes
On Mon, Jul 21, 2014 at 10:36:47 +, Fedora Rawhide Report wrote: This is pretty minor, but for some reason the devel list copy of the rawhide report arrives significantly after (over an hour later) the test list copy. This didn't used to happen. The branched reports both arrive around the same time. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Is anyone else seeing a problem with glibc 2.19.90-29.fc22 ?
On Mon, Jul 21, 2014 at 11:27:35 +0200, poma wrote: Withd thisd breakaged ofd d logind byd d glibcd, d Rawhided i686d isd d literallyd busted! We'll fresh installs and live images are not really usable. If you already have rawhide installed and a root shell you can downgrade glibc. I do wish they'd untag that build if it isn't going to be fixed right away. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Is anyone else seeing a problem with glibc 2.19.90-29.fc22 ?
On Thu, Jul 17, 2014 at 12:59:45 +0800, Christopher Meng wrote: $ fedpkg switch-branch f21 Could not execute switch_branch: len([]) != len(['PRIV_END: seteuid: Function not implemented', '', '', 'and the repository exists.']) ERROR:rpkg:Could not execute switch_branch: len([]) != len(['PRIV_END: seteuid: Function not implemented', '', '', 'and the repository exists.']) That's a similar message to what I was getting thanks. I'll file a bug later today if no one beats me to it. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Is anyone else seeing a problem with glibc 2.19.90-29.fc22 ?
After updating glibc this morning setuid stuff broken (openssh and cron were affected). Downgrading made it work again. I might have needed to reboot (though that would be unusual), but I didn't want to risk it as I am testing some other stuff and didn't want to have to do a recovery before getting to finish the other stuff. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Wither Fedora 21 boot.iso?
On Tue, Jul 15, 2014 at 19:50:59 +0200, poma wrote: After 21 gets released, due to the use of 'updates-testing', do we need to yum --releasever=21 distro-sync after yum-config-manager --disable updates-testing yum-config-manager --enable updates You can enable updates now if you want. There is an empty repo there so things will work, but slightly slower. You don't have to disable updates-testing after the release. If you are running with it enabled now, it's reasonable to keep it enabled after the release. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Rawhide users: ceph packaging issues
On Thu, Jul 10, 2014 at 15:36:41 -0700, Adam Williamson wrote: On Thu, 2014-07-10 at 15:34 -0700, Adam Williamson wrote: so, yeah, bit of a mess. You can probably get onto the 0.81.0-5 packages manually with a bit of judicious --nodeps use or 'yum shell' use, but it'd be best if the packages were fixed up, and I figured I'd let folks know about the problem for now. Sigh, just realized I forgot to mention that I have reported this issue as a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1118510 I also filed bug, though mine was originally for a file conflict between ceph and python-ceph. I figured out that an obsolete would have fixed things later. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: (Rawhide users) Fedora 22 branching: What You Need To Know
On Wed, Jul 09, 2014 at 23:37:39 -0700, Adam Williamson wrote: sudo yum-config-manager --enable fedora and, optionally, enable updates-testing: sudo yum-config-manager --enable updates-testing The updates-testing repo isn't there yet. I am hoping we get empty repos created for both updates and updates-testing now. (updates-testing will be getting used soon, and having an empty updates repo is useful for avoiding configuration changes between switching to branched and the release.) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 2014-07-09 @ **17:00 UTC** - F21 Blocker Review #1
On Wed, Jul 09, 2014 at 23:07:12 +0400, Igor Gnatenko wrote: Hi, On Wed, Jul 9, 2014 at 4:20 AM, Mike Ruckman wrote: # F21 Blocker Review meeting #1 # Date: 2014-07-09 # Time: 17:00 UTC (13:00 EST, 10:00 PST) # Location: #fedora-blocker-review on irc.freenode.neteria ... == // Mike Fedora QA irc: roshi | twitter: roshi_fedora blog: roshi.fedorapeople.org Why this msg not going to the test-announce@? :P I don't think the meeting log needs to go to test-announce. If the complaint is really about the meeting notice, then that is arguably a reasonable suggestion. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Rawhide heads up: cryptsetup update breaks rebooting if using luks
On Tue, Jul 01, 2014 at 08:03:13 -0500, Bruno Wolff III wrote: I don't have all the details yet, but the update of cryptsetup in yesterday's rawhide breaks rebooting if your are using at least some patterns of luks partitions. Early boot works, but mounting /home after the root pivot fails. I confirmed that downgrading to the previous version fixes the problem. I'll be filing a bug for this later today. It would be prudent for people with luks partitions to downgrade in case they need or want to reboot before there is a fix. I have filed a bug for this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1115120 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Rawhide heads up: cryptsetup update breaks rebooting if using luks
I don't have all the details yet, but the update of cryptsetup in yesterday's rawhide breaks rebooting if your are using at least some patterns of luks partitions. Early boot works, but mounting /home after the root pivot fails. I confirmed that downgrading to the previous version fixes the problem. I'll be filing a bug for this later today. It would be prudent for people with luks partitions to downgrade in case they need or want to reboot before there is a fix. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 3.16.x on i686
On Wed, Jun 25, 2014 at 14:10:31 -0700, Adam Williamson wrote: On Wed, 2014-06-25 at 15:09 -0500, Bruno Wolff III wrote: On Wed, Jun 25, 2014 at 12:56:41 -0700, Adam Williamson wrote: > >http://koji.fedoraproject.org/koji/taskinfo?taskID=7076318 > >assuming it builds successfully (AdamW Patching C: Take Cover!), if you >could test with that it'd be good. I'm installing it now. Should be about 30 minutes before I get back to you with results. Hum, you can probably skip it - the patch isn't exactly wrong, but it's also not exactly right and also not exactly sufficient. as you can probably tell, this is getting complicated... https://bugs.freedesktop.org/show_bug.cgi?id=80537 Well it made things better. The several services that were erroneously being started are no getting started. However on the first reboot after installation the shutdown hung. I powered off rather than wait for a timeout, since this happens relatively often with systemd updates. However the two times the system has come up, the network service (I use that in preference to NM) did not come up properly and I had to manually start it to have working network access. systemctl status network ● network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: inactive (dead) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 3.16.x on i686
On Wed, Jun 25, 2014 at 12:56:41 -0700, Adam Williamson wrote: http://koji.fedoraproject.org/koji/taskinfo?taskID=7076318 assuming it builds successfully (AdamW Patching C: Take Cover!), if you could test with that it'd be good. I'm installing it now. Should be about 30 minutes before I get back to you with results. sysv-generator actually landed in systemd-214 (not 209 as I'd thought), so it makes sense that we're only just now seeing this bug crop up. Do we want a bug for the dangling symlink handling? It would be nice if they got cleaned up automatically. Barring that, a different message that made it clear you should remove them as the current message wasn't all that obvious about what was going on. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 3.16.x on i686
On Tue, Jun 24, 2014 at 19:22:05 -0700, Adam Williamson wrote: The most obvious thing is whether you have a SXXservice symlink in /etc/rc*.d; that constitutes the service being 'enabled' so far as SysV is concerned, and so in that case it seems correct for systemd to enable the runtime-generated systemd service. But there may be other reasons why this might happen, I think we'd best look at them case by case. I filed a bug (https://bugzilla.redhat.com/show_bug.cgi?id=1112908) for plague. Plague has both a systemd entry and an init.d file (but not files for any run levels) for the plague-server service. That seems odd, but I don't know if that is the cause of the problem. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 3.16.x on i686
On Mon, Jun 23, 2014 at 13:52:10 -0500, Bruno Wolff III wrote: On Mon, Jun 23, 2014 at 11:34:53 -0700, Adam Williamson wrote: All 3.16 kernels before 3.16.0-0.rc2.git0.1 are just fundamentally broken on i686, I think, unless you pass 'vdso=0'. I wouldn't bother messing with anything unless you're using the rc2 kernel, or passing vdso=0. I'll be testing that shortly on x86_64 and on i686 tonight. But I am seeing two different problems and I'd be surprised if either was that problem. I suspect I am not getting far enough into the boot to see that problem. 3.16.0-0.rc2.git0.1 is pretty broken too. I am definitely seeing two other issues. The one affecting raid has been filed. The other one is a crash early It looks like this one might be elsewhere in the I/O stack. When I got a live image to boot, dd reported /dev/sda3 as zero size which would explain why the superblock was bad. blkid returned info about the device so this seems really odd. And it only seems to happen on this one partition. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 3.16.x on i686
On Tue, Jun 24, 2014 at 16:30:59 -0700, Adam Williamson wrote: I think the "Could not find init script" errors are probably due to this 'dangling symlink' problem, and the fact that .service files are being generated is intentional - just the way systemd is handling remaining sysv services - and not a bug. That's my reading on the situation anyway. You should find the generated .service files match the remaining sysv services you have in /etc/init.d ; that's the case for me: Thanks, that helped me get rid of extraneous boot output. I used: rm -vf `find -L /etc/rc.d -lname '*'` to remove these sym links. However this didn't solve my concern about some services attempting to start that shouldn't. But now I'm thinking there might be some other old config around that I should look for. I'm going to start with plague-server since I never actually used that, but might have had to disable it in the past. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 3.16.x on i686
On Mon, Jun 23, 2014 at 11:34:53 -0700, Adam Williamson wrote: systemd doesn't just 'create init files', I don't think. It *does* have a concept of dependencies, which could account for this effect. Something is creating ones during boot since about a month ago. They are in a scratch location that gets recreated each boot. What services exactly are you talking about? Plague is one example. I also seem to have a selinux problem blocking consolekit so that sound doesn't work in enforcing mode. What desktop are you using? It'd be good if you could file the bug for this, filing SELinux denials via sealert is pretty fast. XFCE. So far I am just working on the kernel change that seems to have md being more picky about md raid1 superblocks and just doing workarounds for the rest. All 3.16 kernels before 3.16.0-0.rc2.git0.1 are just fundamentally broken on i686, I think, unless you pass 'vdso=0'. I wouldn't bother messing with anything unless you're using the rc2 kernel, or passing vdso=0. I'll be testing that shortly on x86_64 and on i686 tonight. But I am seeing two different problems and I'd be surprised if either was that problem. I suspect I am not getting far enough into the boot to see that problem. The one affecting raid has been filed. The other one is a crash early in boot, and I thought I had heard there were some nouveau regressions and that could affect that machine. I need to get netconsole setup again to capture the crash dump, but have given it lower priority because it seems like something others are likely to run into. The raid thing is weird in that it affects only one of my raid devices. And there may be something odd about the superblock, that gets checked more carefully in 3.16, than 3.15. Though I didn't see any commits that indicated a change in md raid superblock checking recently. I have an upstream bug filed for that as well. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
