For 12.10, we really should add a 'primary-graphics-card' event alias or
abstract job that abstracts the udev complexities since that confusing
condition ("drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1 or
stopped udev-fallback-graphics") is also semi-duplicated in other jobs:
- plymouth-splash.conf
- udev-fallback-graphics.conf
I think the "definitive" condition that becomes true when the first
graphics device becomes available is:
(graphics-device-added PRIMARY_DEVICE_FOR_DISPLAY=1
or drm-device-added PRIMARY_DEVICE_FOR_DISPLAY=1
or stopped udev-fallback-graphics)
I agree that 'card0' seems bogus - looks like it's trying to match
DEVPATH but that will never match since there is no wildcard in the
expression. It should be something like the following (note the asterisk
after the equals!!):
drm-device-added DEVPATH=*card0 PRIMARY_DEVICE_FOR_DISPLAY=1
Using named variables ('name=value' as opposed to positional ones where
only a *value* is given) as I've done above is *much* safer in this
scenario since to use positional variables, you need to know the exact
content of the corresponding udev message that the upstart-udev-bridge
converts into an Upstart event.
File /lib/udev/rules.d/78-graphics-card.rules is what is modifying the
udev message to add PRIMARY_DEVICE_FOR_DISPLAY=1 so I'm wondering if we
can simplify the logic to be simply:
drm-device-added PRIMARY_DEVICE_FOR_DISPLAY=1
... since udev will tag both KMS and non-KMS devices correctly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/969489
Title:
lightdm tries (and fails) to start too early?
Status in Upstart:
New
Status in “lightdm” package in Ubuntu:
Confirmed
Bug description:
Sometimes lightdm comes up fine. Other times it appears to fail.
x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is
what actually exists). When I then log into console and 'start
lightdm', it comes up fine (on :1).
I've not had it come up ok today, so I don't know if, when it comes up
fine, it starts on :0. No idea if the lightdm.conf needs a change to
'start on'clause, or if this is just a case of a bad shipped config
file (for module 'nv').
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lightdm 1.1.9-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0-0ubuntu1
Architecture: amd64
Date: Fri Mar 30 13:40:27 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64
(20120323)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
