It looks like I just ran into this issue with Ubuntu 16.10 so the
upstart reference may be wrong here.
Is any more data needed or would it be useless anyway?
PS: It seems that some of the "fixes" made it to /etc/init/lightdm.conf
already but nothing helps?
--
You received this bug notification
This bug hit me after an upgrade from 14.04 to 16.04.1. Strangely I was not
affected earlier. Maybe a reinstall might fix this issue? Two out of three
reboots leads to failsafe X. Sleep command improved the situation but still
50%... Other solutions like restart in rc.local somehow did not
FWIW, I'm also on 14.04 LTS and the workaround from comment #127 did not
work for me. (nor any of the other lightdm work-arounds.)
The "fix" to switch to GDM worked for me
--BUT--
If you set your screen to shut off and require a password (in the
Brightness & Lock settings), you'll get this bug
I run Ubuntu 14.04 and the workaround in #127 seems to have fixed it for
me, thanks Ciprian.
The fact that this is still happening on Ubuntu 14.04 is pretty shocking
- I know LightDM and Upstart are effectively deprecated in favour of
SDDM and systemd in the newer versions, but since this is such
It's me, again.
The N54L works now, but I don't remember the changes.
But today I failed to add SSD based EnhanceIO to several iSCSI based
Ubuntu desktops (Intel G530 and G1610). They hung up with a blank screen
and a mouse cursor in the middle. The kernel hung up, I cannot ping it.
But when I
avius, the same behavior sudo service lightdm restart for my at an HP
N54L. I'm not sure which parameter counts, the times I tried to restart
or the duration since booting.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in
Avius: When lightdm fails to start, do you get sometimes X started up in
safe mode as per Comment 2 from Serge ?
Your problem seems different as your your logs show that lightdm can
successfully start and connect to the X server, and something happens during
your login. Relevant extract from
I forgot to mention: sometimes it takes two or three sudo service
lightdm restart attempts before the system proceeds normally. In other
words, it will bootup, go to the blinking cursor, I'll restart lightdm,
and it will go to the blinking cursor again. Sometimes if I'm fast, I
can catch it
When X fails to start, I don't get the safe mode screen; I just have a
blinking cursor in the top left corner. This occurs during random
bootups, and without any interaction; the failure is before the
username/password textbox is presented. I'm not sure what the something
happening during login
I have applied Ciprian's fix from #127 to no avail.
Here are my new logs, with the change applied. I didn't spot any
difference.
** Attachment added: new-logs.tar
https://bugs.launchpad.net/upstart/+bug/969489/+attachment/4051131/+files/new-logs.tar
--
You received this bug notification
This bug affects me also. I have not tried Ciprian's one line fix. My
logs are attached.
** Attachment added: logs.tar
https://bugs.launchpad.net/upstart/+bug/969489/+attachment/4047432/+files/logs.tar
--
You received this bug notification because you are a member of Desktop
Packages, which
Currently I've been running without issues with the following
configuration in /etc/init/lightdm.conf since September 2013.
[...]
start on ((filesystem
and runlevel [!06]
and started dbus
and plymouth-ready
and stopped udevtrigger) # - one line fix
Something has happened again. The scenario described in #116 has
disappeared, that is now - for some reason, which I do not know - I am
not experiencing any of the problems described in #116. Goes without
saying, I haven't changed anything, just used the computer.
--
You received this bug
Relax, the bug is only sporadic and the slowdown on boot may be overcome with
inode updates and defrags which may or may not occur automatically with the
BTRFS file system. While it may happen with one system, it may not with
another. While it may happen at one time with a system, it may not
I concur!
Though, I think the problem is more-so that there is a race in the first place
instead of a march which is what I'm hoping we can fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Yep. It's a bug with the ligthgm setup. Replacing it with gdm solves the
problem
--
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
Excerpts from walec51's message of 2014-03-01 23:53:04 UTC:
Yep. It's a bug with the ligthgm setup. Replacing it with gdm solves the
problem
Thanks for the data, that should help a bit.
However, all that proves is that gdm does not have the symptom. It does
not indicate that the problem is
Seven months have passed with no fix in place. I have removed the
assigned user so that another may step-up in their place to resolve the
issue.
** Changed in: lightdm (Ubuntu)
Assignee: Dalmer Vieira (dalmer-vieira) = (unassigned)
--
You received this bug notification because you are a
We need to apply a fix in the startup which performs a while statement to check
if dependencies are not yet loaded. This will mitigate against problems with
varying sleep times which may or may not work for users.
Alternatively, having a list of dependencies to run inline may be a better
This is still an issue in ubuntu 14.04.
--
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:
Confirmed
The same what 323232 wrote happened to me - had to replace lightdm with
gdm.
--
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
Seems that the bug occurs more often after an update and reboot (with
new profiling) although it also occurs less often without any
updates..
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Now something has changed since as I took more disk to use. As the
system is a dual-boot, I mounted the Windows system disk (SSD) as read-
only and another disk as shared read-write for both systems to use.
What happens now, and actually started happening a couple of days after
the changes
Commented to early, The workaround #95 did not resolve the blackscreen
issues (although the frequency seems to be lower)
--
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:
Also tried the workaround #95;
quote
On the kernel i turned removed: splash quiet and noticed that the events
proceeding starting lightdm were quite a bit shorter for the failed machines.
When I turned on more debugging features, all the machines boot-up fine with no
errors! So my
I have a fresh Ubuntu 12.04.3 LTS installation and at first everything
worked fine. 2 days and approximately 10-15 reboots after the initial
installation I started experiencing this blank screen, blinking cursor
in upper left corner problem with increasing density. After another 2-3
days and a
Despite the sleep command (up to 12 at this moment) before exec lightdm in
/etc/init/lightdm.conf
still the ocasionally startup with a black screen and blincking cursir.
Also tried the lightdm-gtk-greeter and GDB. The same error remains!
--
You received this bug notification because you are a
In 13.10 on an Aspire laptop with an HDMI attached 1920x1280 monitor the
background on one or the other comes up blank depending upon how I set
the monitor positions. When side by side with the laptop to the right,
it is the laptop screen that comes up blank. Gkrellm is supposed to come
up on the
Same problem, 13.04 fresh install. I have been trying to solve this bug
for ages, the only workaround that has worked for me is to use GDM, not
ideal, I have tried #39, since the set up is similar to mine, nvidia
graphics and SSD, will report back with findings. At least we can work
around it, but
same problem with 13.10 on a samsung series 5 notebook with a ssd
set sleep to 5 (with lower seconds the bug still persist in a lower
frequency...)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
I recommend that Canonical moves over to using GDM or another display
manager if they can't get this fixed for LightDM.
If they're looking to make a good impression, resolving this critical
issue should be at the absolute top of the list (and back-ported).
--
You received this bug notification
I should also mention that after the screen locks and blanks while
unattended, it often comes back only on the external monitor while
leaving the laptop monitor blank. Pulling the monitor cable brings it
back on the main screen.
--
You received this bug notification because you are a member of
I might have some news for this bug:
First is, if i remove quiet splash from boot, the bug disappears as
well.
More importantly though, if I have the blank login screen, and I connect an
external monitor, the screen shows up.
If I go to a tty (Alt-Ctrl-F1) and back to X (Alt-Ctrl-F7), the
By the way I encountered this bug on an old laptop with ATI Mobility
Radeon X1300 using radeon module on 13.10 (/ on btrfs fs, /home on ext4
fs ; using SSD drive).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
I got better result using default lightdm greeter instead of ubuntu's one.
Maybe this can help others.
sudo apt-get purge lightdm
sudo apt-get install ubuntu-desktop
sudo apt-get install lightdm-gtk-greeter
If lightdm-gtk-greeter is installed, you will not be able to start neither
thanks for looking into this bug. I tried switching the display manager
to gdm but pc kept rebooting. How would I restore old version of
lightdm?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
I managed to downgrade lightdm to version 1.2.1-0buntu1-amd64 but I
still do not get GUI when I boot up
--
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
plum7500, in the log you just reported, the relevant lines are these:
[+0.03s] DEBUG: Registering seat with bus path
/org/freedesktop/DisplayManager/Seat0
[+1.62s] DEBUG: Process 1470 exited with return value 127
[+1.62s] DEBUG: X server stopped
What means the X Window System Server wasn't
I am running kernel 3.2.0-54 in Ubuntu 12.04. After the last update,
lightdm does not start so no gui. I tried editing the config for lightdm
by adding some delay and the respawn but it did not work. Can anybody
here tell me what is wrong by looking at the log?
** Attachment added: lightdm log
I'm experimenting this bug since 12.10 on all my systems, amd and
nvidia.
Attached the lightdm.log from a filed startup.
I think it's time to fix this bug.
** Attachment added: lightdm.log
https://bugs.launchpad.net/upstart/+bug/969489/+attachment/3853936/+files/lightdm.log-fail
--
You
** Changed in: lightdm (Ubuntu)
Status: Confirmed = Triaged
** Changed in: lightdm (Ubuntu)
Importance: Undecided = High
--
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
Adding some lines to /etc/init/lightdm.conf fixed the problem on my PC
(Ubuntu 12.04):
start on ((filesystem
and runlevel [!06]
and started dbus
and plymouth-ready
and (graphics-device-added PRIMARY_DEVICE_FOR_DISPLAY=1 #added
or
This happens sometimes on my machine:
Ubuntu 12.04 64bit
Intel SSD 335
Nvidia GTS 650 with NVIDIA drivers.
lightdm version 1.2.3-0ubuntu2.3
Tracked it to a race issue - if NVRM module is loaded before lightdm
starts, all is OK. (see logs in Post Scriptum)
My current configuration in
Same problem with my X230 since I installed a SSD drive. Previously ran
the same device with a normal drive without these issues.
Lenovo X230
Ubuntu 12.10/13.04 64bit
Samsung SSD 840
i5-3320M
using the processors HD4000 graphics.
Definitely checks the boxes for a race issue. Often I can boot
With our particular setup of school labs. 2-3 out of 30 stations would
always fail - the display manager would not start.
On the kernel i turned removed: splash quiet and noticed that the
events proceeding starting lightdm were quite a bit shorter for the
failed machines.
When I turned on more
Ubuntu 13.04
Intel SSD
i7 4770S
Using the processor graphics with the default driver.
I got the black screen with a white mouse cursor about a quarter the
time on boot and finally discovered the machine wasn't broken/crappy by
pressing CTRL-ALT-F1 to see if tty1 would work (previously I would
If the bug is actually what I think it is (not that sure reading some
comments), ie black screen with white cursor in the top left corner instead of
lightdm from time time, but still working when typing your password and Enter
in the dark.
Then I have it on my Dell xps 13, SSD and only Intel HD
I had the opposite problem. By commenting out the line : sleep 5
after the line: post-start script
in /etc/init/lightdm.conf
my lightdm bug is fixed in Ubuntu 13.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Dell XPS 13 + Fresh 13.04:
Black screen almost every time ... for month.
1) Log in to the console.
2) sudo /etc/init.d/lightdm restart logout
3) Enter the password for the third time. I did it!
I guess I have to remove lightdm and fire up 'startx' from the console
instead for more comfort. ;)
Excerpts from Clint Byrum (clint-fewbar) message:
Second, I'm pretty sure this is a hardware specific problem caused
by drivers lying to the system about the state of the hardware, and
subsequently dying when actually asked to function. This is only exposed
on systems that boot extremely
I've not seen this bug on my SSD based vaio in a long time. Originally
I fixed it with the 'and stopped udevtrigger' workaround, but that has
been gone for awhile. I assume this is because I'm not running the
nvidia drivers any more. (Long ago it had been posited that the problem
was that the
I had this with fglrx, so either both amd and nvidia suffer from the same bug,
or it is elsewhere.
It's just a pity that this is treated as such low priority.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Also affected here.
Ubuntu 13.04
SSD
Radeon HD4250
Phenon X4
Seems to work making lightdm.conf as:
start on ((filesystem
and runlevel [!06]
and started dbus
and stopped udevtrigger ### line added
and (drm-device-added card0
Same problem here with Ubuntu 12.10 running kernel 3.5.0-37-generic.
Acer Apire Timeline U
SSD 20GB with Btrfs - /
HDD 500 with Ext4 - /home
6GB Ram
Then the sudo /etc/init.d/lightdm restart helps me.
Intel(R) Core(TM) i5
** Changed in: lightdm (Ubuntu)
Assignee: (unassigned) = Dalmer
Since I reinstalled my system (13.10) in UEFI mode, this bug even occurs
more often. Before it only occured about every second start.
I've got a SATA II SSD, and a Haswell i5 CPU which also handles the
graphics.
The special thing about the bug for me is that I am never able to start
or restart
I only see a black console with a blinking cursor.. lightdm process is still
running, so failsafe-x doesn´t take over i guess...
Experiencing this bug with latest 13.10 Saucy Salamander...
Would be nice if someone can fix this! Its a problem that effects a lot
of users and people who don´t know
I have not seen data that proves it has 0 bad effects. I'd suspect that
it would have a minor impact on time between power-on and login for
those users who are not affected, but I also have no data on that either.
Sorry... say what!? I will just quote it for you, from canonical's upstart
Excerpts from Ivo Anjo's message of 2013-07-22 16:39:16 UTC:
I have not seen data that proves it has 0 bad effects. I'd suspect that
it would have a minor impact on time between power-on and login for
those users who are not affected, but I also have no data on that either.
Sorry... say
Excerpts from Ivo Anjo's message of 2013-07-17 08:32:54 UTC:
@Clint: But honestly, why not deploy the workaround by default?
It has 0 bad effects when you don't have the issue, and is the difference
between some strange flickering and most people not being able to get a
working system at
lightdm does not use respawn because the failsafe-x job catches lightdm
failures and launches its own fallback X server for troubleshooting
purposes. Adding 'respawn' doesn't fix the ordering issue, and would
break other things besides.
--
You received this bug notification because you are a
Is this both a lightdm bug and a failsafe-x bug?
Because I don't get failsafe-x when lightdm fails, I just get a tty.
--
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:
** Tags added: i386 saucy
--
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”
@Clint: But honestly, why not deploy the workaround by default?
It has 0 bad effects when you don't have the issue, and is the difference
between some strange flickering and most people not being able to get a working
system at all.
--
You received this bug notification because you are a
respawn workaround works fine here, but frankly I find it troubling that
such a severe issue has gone unfixed for so long... Will we ever get an
official update that fixes this? New users shouldn't be expected to edit
config files just to get their system to boot correctly. This type of
bug should
Excerpts from bwat47's message of 2013-07-16 22:02:03 UTC:
respawn workaround works fine here, but frankly I find it troubling that
such a severe issue has gone unfixed for so long... Will we ever get an
official update that fixes this? New users shouldn't be expected to edit
config files just
I run Ubuntu 13.04 on Thinkpad W530 with 256GB SSD. After upgrading to
kernel 3.8.0-26 I have a black screen with cursor in place of lightdm.
Lightdm works well if I boot with elder kernels.
The solutions of posts #5 (sleep 10) and #48 (respawn) are useless, the
solution of post #12 (and stopped
I have same problem.
On 12.04 it was even acceptable - freezing from time to time. But after
upgrading to 13.04 I have 3 to 4 freezes before successfull lightdm load.
Patching /etc/init/lightdm.conf helped me for now - but slowing down fastboot
is a little pity.
Let me know if I could help
I just added respawn to /etc/init/lightdm.conf as suggested in comment
#48 - did /not/ fix the problem for me.
--
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
VirtualBox - fresh install. No SSD :)
+1 for #48
That's a catch-all workaround, that does not rely on an outcome in some race
condition.
If it does not work for you, I believe you have a different bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is
#5 Seems to do the job for me
On an silentmaxx Tower with
- Mainboard GIGABYTE GA-Z77X-UP4 Thunderbolt
- Radeon ATI Radeon 7750 1GB
- SSD Samsung SATA3 128GB
It's a bit annoying, that this bug is over a year old, and still not fixed.
Ubuntu is made for 'working out of the box' especially for
+1 for #48
Sleep only helped occacionally.
--
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
+1 for #48
On an Lenovo Thinkpad X200s with ext4 SSD (256GB Crucial V4) and some
integrated Intel graphics, it is reproducible even when just
/etc/init.d/lightdm restart -ing it from console, doing so happens every
15th time or so. Sleep 5 does not help, and stopped udevtrigger does
not work
#64 provides a work-around that does the trick for me too. I'm on the
same kernel as jmac939 there, and about 50% of the time my system boots
properly into the lightdm login screen. But the rest of the time the
system fails to do so but shows only the black screen + mouse pointer.
When that
I switched to GDM for the moment.
--
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
In my computer, bumblebee started causing this problem.
A suggested fix, given in https://github.com/Bumblebee-
Project/Bumblebee/issues/205#issuecomment-8022153 did not solve the
problem, and added a delay. However the and stopped udevtrigger seems
to be working with a fresh bumblebee install
Bug still persist in 13.04. GDM works fine.
--
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
I'm on 12.10 kernel 3.5.0-25 and I'm booting off an SSD (which seems to
be a common symptom).
When the blanks screen occurs, I know it wants the FS crypt password.
So I type it in blind on this black screen. Then the rest of boot
occurs normally. I never see the Grub screen.
I tried adding a 5
I upgraded to Ubuntu Linux kernel 3.5.0-25 and the fix I described in
comment #55 now fails as well. So does the work-around suggested in
comment #48 (as I previously described, again in comment #55). I have
switched back to kernel 3.5.0-23. I'm still looking forward to a
genuine fix.
--
You
isn't it upstart issue? I removed it and it's booting and working good.
--
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?
Excerpts from maxim's message of 2013-03-05 09:02:15 UTC:
isn't it upstart issue? I removed it and it's booting and working good.
You removed what?
The issue is that something in the system is not ready when lightdm
tries to start, so either the upstart job needs more start on conditions
Marked #1142044 as a duplicate of this one as I believe it is the same
bug.
I'm on a Samsung Series 9 notebook with an Intel Core i7. In my bug
report I've added some additional information and logs which aren't
available here.
I'm on 13.04 though.
--
You received this bug notification because
For me this bug appears on a (slow) BTRFS partition on hard disk mounted
as root. Apperantly lightdm has timing proplems and there is no fix for
it. As a workaround, respawing as of #48 worked for me as well.
--
You received this bug notification because you are a member of Desktop
Packages,
Interesting, I too use btrfs for root and home.
--
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
Comment #48 seems to have remedied the problem for me. It's a bit of a
hack, but it does the trick. A terminal prompt showed up first for a few
seconds (the same thing that often happened before), then Light DM fired
up the login screen.
--
You received this bug notification because you are a
I also have this problem, I think!
Occasionally my computer will hang at boot showing only a black screen.
Running Ubuntu 12.10 on the following hardware:
CPU: Intel Core i7-2700K@3.5 Ghz (Sandy Bridge)
GPU: Nvidia GeForce GTX660Ti 2Gb
HDD: Corsair Force 3 SSD 240GB (mounted as / )
Motherboard:
I'm on a Dell XPS 15z. I detail below other attempts (all pretty much
taken from this thread but unsuccessful for my setup); instead, what
works for me is to (1) change in /etc/default/grub the variable
GRUB_CMDLINE_LINUX_DEFAULT to acpi_backlight=vendor
dell_laptop.backlight=0 quiet splash, i.e.,
I'm affected by this bug and have nvidia gpu with the binary nvdia
drivers enabled (12.10). Comment #12 provides a solution for me.
--
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
Found this post here:
http://askubuntu.com/questions/215842/ubuntu-12-10-sometimes-a-black-
screen-after-boot:
I had almost the same problem, black screen at login :( I had to
Ctrl+Alt+F1 and restart lightdm and then it worked perfectly, but it
sucked a bit to do that all the time so this is what
I believe this bug is featured on Web Upd8:
http://www.webupd8.org/2013/01/ubuntu-lightdm-black-screen-when-
using.html
--
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:
Also I found this an interesting comment:
xf86-video-modesetting 0.6.0 driver has been released fixing the crash with a
udev race condition.
http://www.phoronix.com/scan.php?page=news_itempx=MTI3MDc
--
You received this bug notification because you are a member of Desktop
Packages, which is
It may have something to do with the powersaving modes of some graphic cards,
too.
On the same laptop, booting with the power plugged in causes this problem, but
everyting's fine when the power is plugged off.
--
You received this bug notification because you are a member of Desktop
Packages,
With respawn is working consistently well here so far.
--
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:
Bug 1080082 has been marked as a duplicate of this one, although I'm not
sure it is (I use fglrx).
Anyway, my workaround for 1.5 months with no issues and no need for
arbitrary sleep has been to modify /etc/init/lightdm.conf and adding
respawn like this:
...
stop on runlevel [016]
respawn # --
This is quite bad when running ubuntu on VMWare WorkStation 9
I tried editing the lines:
and stopped udevtrigger #this line I added
and (drm-device-added DEVPATH=*card0 PRIMARY_DEVICE_FOR_DISPLAY=1
But that didn't work.
--
You received this bug notification because you
Excerpts from Gavin Graham's message of 2012-12-19 02:25:34 UTC:
@Pieter
I agree, it is not a fix (well, a permanent and proper one anyway) but
it does suggest that it's a race condition and that it is in the Binary
itself and not the /etc/init/lightdm script as some of the other
potential
@Clint
I'm happy to participate in collecting the data on a quiet day over the
Christmas break when I don't really need to use my computer for any real
activity. Are you talking about a debug-level log of X or something
similar?
Tell me what you would like to see and I'll strip the '-d' from the
I thought I'd try stripping the config back to the original without the
'-d' in the 'exec lightdm -d' line and after six reboots, not one
failure. I'll leave the config in its original state now and if/when the
symptoms reappear, I'll grab all the logs and post them up here.
--
You received this
Ideally lightdm should wait until soundcards are ready as well, waiting for the
udev event with SOUND_INITIALIZED=1.
See udev script 78-sound-card.rules.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
That's not a fix, that's just slowing down the exec by enabling
debugging so that it's not causing the race issue.
--
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:
@Pieter
I agree, it is not a fix (well, a permanent and proper one anyway) but
it does suggest that it's a race condition and that it is in the Binary
itself and not the /etc/init/lightdm script as some of the other
potential fixes have tried to remedy.
--
You received this bug notification
1 - 100 of 141 matches
Mail list logo
