Mir graphics drivers don't automatically upgrade when libmir* is manually upgraded, resulting in broken system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Triaged
|
Medium
|
Unassigned | ||
mir (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
While investigating bug #1528279 I've noticed there's some missing dependency somewhere, I'm able to get a broken device by upgrading unity-system-
Excerpt from apt history.log:
Start-Date: 2015-12-21 17:59:29
Commandline: apt install unity-system-
Install: libmirserver36:
Upgrade: libmircookie1:armhf (0.17.1+
End-Date: 2015-12-21 17:59:34
→ Broken
Start-Date: 2015-12-21 18:28:00
Commandline: apt install mir-graphics-
Install: libinput10:armhf (1.1.0-
Upgrade: mir-graphics-
End-Date: 2015-12-21 18:28:02
→ Fixed
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: mir-graphics-
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.17.2-
Architecture: armhf
Date: Mon Dec 21 18:30:50 2015
InstallationDate: Installed on 2015-12-18 (3 days ago)
InstallationMedia: Ubuntu 15.04 - armhf (20151218-161516)
SourcePackage: mir
UpgradeStatus: No upgrade log present (probably fresh install)
IIRC, this is by design. Mir can't possibly know which driver package is the right one for you at build time. And although we do have probing, installing all driver packages bloats the dependency tree unnecessarily. So our solution (IIRC) was to put a seed in the phone image such that the android drivers package was always included.
I'm not sure if there's something in our packaging that might have made it easier for your system to become broken...?