Posted by adamwill on February 4, 2014
Several people have reported that recent kernels sometimes, often or always completely fail to boot, very early in the boot process (right after the boot menu). We’re still looking into this at present, but we have a possible indication of what the problem might be right now. You may see a trace in numa stuff if you boot with
We’d advise Rawhide users to make sure you still have a 3.13 kernel installed, just in case you run into trouble booting 3.14 kernels.
Edit: kernel-3.14.0-0.rc1.git0.2.fc21 may well fix this. Please test it out, if you’re affected, and let us know if it doesn’t.
Posted in Uncategorized | 2 Comments »
Posted by adamwill on December 27, 2013
A couple of days ago, a new libevdev build, 0.6-1, was sent to Rawhide. It changed the ABI of libevdev.so.1 by dropping some ‘deprecated’ functions, without bumping the library version (soname). Unfortunately, clutter was still using these ‘deprecated’ functions: upstream clutter git had been updated to use the replacement functions, but no release had yet been cut with this change, and it had not been backported to Fedora.
This meant that if you installed libevdev-0.6-1.fc21, GNOME would fail to start up, with gnome-shell reporting a failure in clutter:
gnome-shell: symbol lookup error: /lib64/libclutter-1.0.so.0: undefined symbol: LIBEVDEV_READ_NORMAL
We’ve now sent out a libevdev-0.6-2.fc21 build which restores the dropped functions, and also a clutter-1.16.2-4.fc21 build which backports the fix to use the replacement functions, thus fixing the bug from both ends for extra safety. If you’re currently suffering from this bug, updating libevdev, clutter or both should resolve it.
Posted in Topical but Not Interesting Later | 1 Comment »
Posted by adamwill on December 23, 2013
So hey, this blog still exists!
For this author (AdamW), there are two major issues in Rawhide currently. SELinux appears to be denying ‘execmem’ and ‘execstack’ access to all sorts of stuff – this is affecting dhclient (stopping networking working), sshd, sssd (for those of us who use FreeIPA authentication), cups and several other things. I haven’t looked into what caused this exactly yet, but booting with enforcing=0 is likely to be a requirement for Rawhide users until it gets figured out. Bugs filed so far are #1046112 and #1045682.
Also for this author, GNOME currently fails to run at all. GDM doesn’t start, and if I boot to runlevel 3 and run startx I get an extremely broken GNOME session with Shell not running and windows all over the shop. For now, I’ve switched to Xfce. I suspect this is because about half of GNOME 3.11.3 got built before most of the desktop team left for the holidays, but again don’t have precise details yet. We may be able to get it fixed up with the help of any desktop folks who are still around.
Update on GNOME: turns out it just needs a new gsettings-desktop-schemas build. That is now in progress – grab that when it’s done, and GNOME should work again, with all other components at their latest Rawhide level.
Posted in Topical but Not Interesting Later, Uncategorized | 4 Comments »
Posted by adamwill on January 28, 2010
When booting Rawhide of 2010-01-28, you may hit a tricky situation: absolutely no input at all. In some (possibly all) cases this affects runlevel 3 as well as runlevel 5. This is due to bug #559679: it’s an SELinux problem which prevents HAL starting up (so can cause problems for anything else that still uses HAL, as well).
To fix this problem, you need to install selinux-policy 3.7.8-5 or later (update all selinux-policy packages you have installed, of course). To install them, boot to runlevel 3: add ‘3’ to your kernel parameters in grub. If you get no input even at runlevel 3, try deleting ‘rhgb quiet’ from the grub parameters as well. Install the selinux-policy updates, reboot, and input should be working again.
Obviously, if you did not yet update your Rawhide (or you updated but didn’t reboot), make sure when you do update that if you get an older selinux-policy, then install the newer one from Koji before you reboot! That way you’ll avoid hitting the problem.
Posted in Topical but Not Interesting Later | 2 Comments »
Posted by adamwill on September 22, 2009
Some people are now aware of (and using) the nightly Rawhide live builds. To save time and bandwidth, it should be noted that all nightly builds since 2009-09-18 fail to boot at all, on any hardware, and are hence essentially unusable. We are currently looking into the cause of this problem and hope to have the nightly builds working again soon.
Update 2009-09-24: The initial problem was resolved, but 2009-09-22 and 2009-09-23 nightly builds were affected by a second problem with the same result. We hope that 2009-09-24 builds will finally fix all issues and boot correctly, once they are available (which depends on when the main Rawhide compose is completed).
In the mean time, the latest available working live build is Snap3, which is available at the pre-release download page. This was built from the 2009-09-17 Rawhide tree.
Posted in Topical but Not Interesting Later | 1 Comment »
Posted by rawhidewatch on August 20, 2009
If you were running the restorecond service and upgraded to policycoreutils-2.0.71-6.fc12 then things went horribly wrong. restorecond goes nuts and screws up labels across your filesystem. Logins via ssh or local console breaks among other problems.
Here is how to recover:
- Boot into single user mode.
- Turn off restorecond service with chkconfig restorecond off
- fixfiles restore will fix labels across your entire filesystem.
- Reboot into the normal system.
- Upgrade to policycoreutils-2.0.71-7.fc12 or later.
- chkconfig restorecond on
In related news, you might be having problems with the restorecon command. In the past commands like restorecon -Rv . would relabel the current directory, but now it fails silently. dwalsh says this is a bug he intends to fix. Until it is fixed, you must specify an absolute pathname to the restorecon command.
Posted in Uncategorized | Comments Off on restorecond in policycoreutils-2.0.71-6 breaks the world, how to recover
Posted by rawhidewatch on August 6, 2009
xorg-x11-server-1.6.99-25* is broken. Upgrade to -27 to fix this problem. This is should be pushed to rawhide before Saturday.
Posted in Topical but Not Interesting Later | Comments Off on Rawhide X crashes on startup
Posted by adamwill on August 5, 2009
There are two problems in today’s Rawhide. First, xulrunner has been updated, but Firefox (and other Gecko-based applications) have not been rebuilt. If you update to today’s Rawhide and include the updated xulrunner, Firefox (and other Gecko-based applications applications) will not work. If you haven’t updated yet, you can avoid this problem by excluding xulrunner from your update: ‘yum update -x *xulrunner*’. Remember to take this out again once rebuilt Firefox and other packages have gone into Rawhide. If you already got hit by this problem, you need update to the rebuilt Firefox package, but as of the time of this writing, the build has not got through. You can attempt to manually revert xulrunner to its old version, as an alternative.
Secondly, you might find that yum seems unable to download packages properly, getting partway through, failing with a HTTP Error 200 message, trying the next mirror, and failing again. To fix this, update the python-urlgrabber package: ‘yum upgrade python-urlgrabber’.
Posted in Topical but Not Interesting Later | Comments Off on Rawhide 2009/08/05: xulrunner and python-urlgrabber
Posted by rawhidewatch on August 3, 2009
Many are experiencing a problem where the notification area (a.k.a. systray, or that place icons like nm-applet appear) being blank in rawhide. The current workaround is to restart notification-area-applet a few times. There is a bug report for this issue. Hopefully this will be fixed soon. Thanks to mclasen for this tip.
Posted in Uncategorized | Comments Off on Blank notification area (systray) workaround
Posted by rawhidewatch on July 31, 2009
Trying to update your Fedora 11 (or older) system to the latest rawhide content? You might notice a failure similar to below when attempting to upgrade using yum:
rpmlib(PayloadIsXz) <= 5.2-1 is needed by kernel-PAE-2.6.31-0.107.rc4.git3.fc12.i686
rpmlib(PayloadIsXz) <= 5.2-1 is needed by kernel-firmware-2.6.31-0.107.rc4.git3.fc12.noarch
Turns out that rawhide packages now use XZ (the new LZMA format) as the default payload compression format. The details of this new feature can be found on the XZRpmPayloads feature page. Testers that install directly from Fedora 12 or rawhide should not experience problems. However, folks upgrading from Fedora 11 or from an older rawhide may need to manually workaround this issue using the following commands:
yum --enablerepo=updates-testing update rpm
Once completed, you may continue with the rawhide upgrade:
yum --disablerepo=* --enablerepo=rawhide update
More information on upgrading to rawhide can be found on the wiki.
Posted in Uncategorized | Comments Off on Unable to update to rawhide – rpmlib(PayloadIsXz)