Failure initializing radeon (as /dev/card1) renderer: unexpectedly disconnected from boot status daemon

Bug #1386781 reported by Dariusz Gadomski on 2014-10-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Plymouth
Confirmed
High
plymouth (Ubuntu)
Undecided
Dariusz Gadomski

Bug Description

Log from a failed run.

In a setup as follows:

1. Ubuntu 14.04 booting from a live CD with updated plymouth (0.9.0 from https://launchpad.net/~xnox/+archive/ubuntu/backports)
2. Hardware is an iMac 12,1 with an integrated intel (/dev/card0) and a discrete radeon (/dev/card1). The display is connected to the radeon and a prompt for an disk encryption password is needed.

Expected results:
A password prompt should be displayed on each display (including the main display connected to the radeon).

Actual result:
On the only display connected to radeon right after leaving GRUB all what may be seen is:
error: unexpectedly disconnected from boot status daemon
/dev/loop0: UUID="<the device UUID>" TYPE="crypto_LUKS"

According to the plymouth changelog it should have been fixed by https://bugs.freedesktop.org/show_bug.cgi?id=25943 (http://cgit.freedesktop.org/plymouth/commit/?id=e982dc255c0f471e67eb7bd0858c170d103d39ce)
but according to the plymouth debug log (attached) radeon fails to open.

Tags: cts Edit Tag help

Created attachment 108522
Log from a failed run.

In a setup as follows:

1. Ubuntu 14.04 booting from a live CD with updated plymouth (0.9.0 from https://launchpad.net/~xnox/+archive/ubuntu/backports)
2. Hardware is an iMac 12,1 with an integrated intel (/dev/card0) and a discrete radeon (/dev/card1). The display is connected to the radeon and a prompt for an disk encryption password is needed.

Expected results:
A password prompt should be displayed on each display (including the main display connected to the radeon).

Actual result:
On the only display connected to radeon right after leaving GRUB all what may be seen is:
error: unexpectedly disconnected from boot status daemon
/dev/loop0: UUID="<the device UUID>" TYPE="crypto_LUKS"

According to the plymouth changelog it should have been fixed by https://bugs.freedesktop.org/show_bug.cgi?id=25943 (http://cgit.freedesktop.org/plymouth/commit/?id=e982dc255c0f471e67eb7bd0858c170d103d39ce)
but according to the plymouth debug log (attached) radeon fails to open.

Dariusz Gadomski (dgadomski) wrote :
affects: linux → plymouth
affects: linux (Ubuntu) → plymouth (Ubuntu)
Changed in plymouth (Ubuntu):
assignee: nobody → Dariusz Gadomski (dgadomski)
Changed in plymouth:
importance: Unknown → High
status: Unknown → Confirmed
Steve Langasek (vorlon) wrote :

Is this reproducible with either 14.10 or vivid? This is not an actionable bug in Ubuntu if it's only reproducible with a ppa-sourced plymouth package.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.