Rawhide Watch

Daily warnings for rawhide victims

Fedora 21 / 22: The Branchening

Posted by adamwill on July 10, 2014

So, today Fedora 21 branched from Rawhide, and Rawhide is now what will ultimately become Fedora 22.

For any puny weaklings who want to track Fedora 21 and not Fedora 22, I posted up a handy guide. For real men, real women, and real small furry creatures from Alpha Centauri who want to stick with Rawhide, no action is needed: just keep updating. Everyone else, your blog reading privileges are revoked.

Posted in Topical but Not Interesting Later | Comments Off

Nightly boot.iso fails to boot

Posted by adamwill on June 25, 2014

Recent nightly Rawhide boot.iso network install images are failing to boot due to a bug in util-linux. The fix has already been identified and pushed upstream, and should work its way downstream into Fedora soon. This doesn’t appear to be affecting the nightly live images.

Slightly older boot.iso images, if you have one lying around, may not suffer from that bug, but probably do suffer from this one, which is caused by metacity (the window manager used by non-live install images) failing to run due to excessive pruning of the anaconda environment. A fix for that bug was also pushed today. With any luck, once the util-linux fix comes downstream, we’ll get working nightlies again.

Posted in Topical but Not Interesting Later | Comments Off

3.16 kernels broken on i686 up until rc2 (affects installed systems and nightly images)

Posted by adamwill on June 23, 2014

There was a significant bug in all 3.16 kernels affecting the i686 architecture (32-bit Intel) only. This resulted in all sorts of breakage higher up the stack – dbus would not run, for a start, which causes many other problems. Installed systems might just limp to a console login; of nightly images, both lives and boot.iso images failed to boot fully.

The cause of this was recently identified and a fix submitted upstream. The fix has been pulled into Rawhide immediately, starting with kernel-3.16.0-0.rc2.git0.1.fc21. All 3.16 kernels prior to that should not be used on i686 machines, or you should pass the kernel parameter vdso=0 to work around the bug.

Nightly images should start working again (or, at least, not be broken by this particular bug…) starting from tomorrow, as the fixed kernel is pulled in.

Posted in Topical but Not Interesting Later | 1 Comment »

Wifi, direct ADSL, cellular or Bluetooth connections broken after upgrade to NetworkManager with dnf

Posted by adamwill on June 20, 2014

edit 2014-06-20: this also affects directly connected ADSL modems, cellular modems and Bluetooth connections.

Hey there, intrepid Rawhidenauts! If you use wifi edit: or an ADSL modem or cellular modem or Bluetooth connection/edit on your Rawhide system, and you did a Rawhide update with dnf which brought in NetworkManager- , you may find that your wifi stopped working after the update.

What happened is that NetworkManager’s support for these types of connection got split into subpackages. The NM maintainer followed the usual packaging protocols for when a new subpackage is introduced which should be automatically added to existing installs, and if you updated with yum then you would’ve got the new subpackages installed correctly, but it seems that people who upgraded with dnf did not get them installed. The issue’s been reported as bug #1107973.

If you’re affected by this, you should install the appropriate subpackage(s) manually. The packages are NetworkManager-wifi, NetworkManager-adsl, NetworkManager-wwan, and NetworkManager-bluetooth. Run, for example,

dnf install NetworkManager-wifi

to fix things up.

Posted in Uncategorized | Comments Off

Boot failures: systems / KVM guests with a single CPU core, current live installations

Posted by adamwill on May 13, 2014

There seem to be two interesting failure-to-boot bugs affecting Rawhide at present, intrepid Rawhide-nauts (yes, I totally just invented that).

#1096358 involves systems newly installed from any recent (seems to be since 2014-05-07) Rawhide-based live image. These installations seem to fail to boot – in fact, fail in the bootloader – with an “unaligned pointer” error message. The grub2 maintainer is currently investigating this one. If, for some strange reason, you have an urgent need to install Rawhide right now, non-live installs don’t seem to be affected by this issue.

#1095891 seems, so far, to be affecting virtual machines assigned a single CPU core (although it’s possible it affects real hardware systems with only a single CPU core, no-one’s confirmed that yet – I need to find someone with an old enough system to check it). Such systems fail to boot, this time early in the init process – the issue appears to be in udev. To work around this problem, assign more than one CPU core to the virtual guest, or downgrade to systemd 212-2 or earlier.

Posted in Uncategorized | Comments Off

Boot failures with kernels installed after grubby-8.31-1.fc21

Posted by adamwill on April 1, 2014

There was a bug in grubby-8.31-1.fc21 which caused it to write invalid grub config entries. This may only affect UEFI installations. If you installed any kernels after installing that version of grubby, they will likely be unbootable. When you try and boot them you’ll see an error like this:

error: file ‘/vmlinuz-3.14.0-0.rc8.git1.1.fc21.x86_64′ not found.
error: can’t find command ‘devicetree’.
error: you need to load the kernel first.

The bug in grubby is fixed with grubby-8.32-1.fc21, but that’s not the whole story. grubby works by using the top entry in the existing grub config file as a ‘template’ for the new entry, so as long as you have a ‘bad’ entry written by 8.31 as your top entry, even the new grubby will still write broken entries. To completely resolve this issue, you’ll need to manually edit your /etc/grub2.cfg and remove all broken entries. You should still have at least one working entry – the entry for whatever kernel is still bootable. Once you remove all broken entries, things should work OK again. You can reinstall kernel packages whose entries were lost, or use grub2-mkconfig to regenerate the grub2 config file entirely.

Posted in Uncategorized | Comments Off

GNOME start failure with new selinux-policy

Posted by adamwill on February 26, 2014

At least for the author, with selinux-policy-3.13.1-27.fc21 , GNOME fails to start correctly if SELinux is in Enforcing mode. If SELinux is in Permissive mode it starts correctly. This denial seems most likely to be the cause of the problem.

Posted in Uncategorized | Comments Off

Long-term users: check /var/run is a symlink to /run before updating to systemd 210

Posted by adamwill on February 26, 2014

If your Rawhide system has been around for a while, check that /var/run is a symlink to /run before you update to systemd 210. If it isn’t, the system will likely fail to boot.

Recent Fedora installations create /var/run as a symlink to /run, but older ones didn’t (I don’t know precisely when this was changed), and it seems systemd and dbus disagree about the location of dbus’ socket: dbus thinks it should be in /var/run , and systemd thinks it should be in /run. If one’s a symlink to the other this is fine; if it isn’t, things are very much not fine.

If /var/run isn’t a symlink to /run, you can move its contents into /run and make it into one. (Even if you mess up, this isn’t terribly important, as all this stuff is supposed to be transient anyway: /run is a tmpfs. Worst you can do is break one boot.)

Bug filed upstream for systemd dbus.

Posted in Uncategorized | Comments Off

Boot failures with recent Rawhide kernels

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 earlyprintk=vga.

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 »

GNOME fail (again) thanks to libevdev 0.6-1

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 »


Get every new post delivered to your Inbox.