LightDM won't load: Stopping startpar bridge for notification of upstart job start/stop

Bug #1244989 reported by Ads20000
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
Fix Released
Undecided
Unassigned
sysvinit (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Installed the Ubuntu 14.04 "Trusty Tahr" daily image (21-Oct-2013 13:57) into Virtualbox 4.2.18 r88780 and it won't load LightDM, I switched to tty1 and I see the following message:

    Stopping startpar bridge for notification of upstart job start/stop

On several lines alternating between `[start]` and `[stop]` messages at the end. If I use `sudo lightdm restart` it just brings up a blank screen. I didn't have this specific problem when I was running the Saucy development branch.

When I try to use `sudo lightdm restart` I get the error:

    Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?

and I get a blank screen again.

Guest:
lightdm 1.8.2
1851 MB of RAM

Host:
Pentium Dual-Core CPU E5200 @ 2.50GHz
4GB (3.7GiB) DDR2 RAM + 1.8GiB Swap
nVidia GeForce 7100 (512MB GRAM)

Ads20000 (ads20000)
information type: Public → Private
Ads20000 (ads20000)
information type: Private → Public
Ads20000 (ads20000)
description: updated
Ads20000 (ads20000)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lightdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Olaf (exoyds) wrote :

Same problem

Revision history for this message
Daniel Cordeiro (dcordeiro) wrote :

I'm having the same issue on a clean install of Ubuntu server 13.10 :

# grep startpar /var/log/boot.log
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]
 * Starting startpar bridge for notification of upstart job start/stop [ OK ]
 * Stopping startpar bridge for notification of upstart job start/stop [ OK ]

Revision history for this message
Steve Langasek (vorlon) wrote :

these startpar bridge messages have nothing to do with a lightdm failure to start.

Changed in sysvinit (Ubuntu):
status: New → Invalid
Revision history for this message
Ads20000 (ads20000) wrote :

However I don't get the problem in the description when I use GDM by default (or I use `gdm start`).

Revision history for this message
Sylvain Cardine (maxwello) wrote :

samedi problem since yesterday. ubuntu 14.04 Sony vaio vpcz21c5e

Revision history for this message
Sylvain Cardine (maxwello) wrote :

idem with gdm. i remember a similar prob at work with 12.04 and gnome-settings... i try it ...

Revision history for this message
Francesco Randi (francesco-randi) wrote :

Same problem since yesterday:
I have an integrated (intel) and a discrete (radeon) graphic card, and it seems that the update "broke" just the integrated one. I'm running fine on the radeon one now..

Below an extract of /var/log/dpkg.log, regarding the updated packages that could be related to the problem:

2014-02-23 16:36:58 upgrade xserver-common:all 2:1.14.3-3ubuntu2 2:1.14.5-1ubuntu2~saucy1
2014-02-23 16:36:59 upgrade xserver-xephyr:amd64 2:1.14.3-3ubuntu2 2:1.14.5-1ubuntu2~saucy1
2014-02-23 16:37:00 upgrade xserver-xorg-core:amd64 2:1.14.3-3ubuntu2 2:1.14.5-1ubuntu2~saucy1
2014-02-23 16:37:01 upgrade xserver-xorg-glamoregl:amd64 0.5.1-0ubuntu4 0.5.1-0ubuntu4.2

Revision history for this message
Sylvain Cardine (maxwello) wrote :

ok ; i've a vaio with amd dock and intel in primary. i'll test another install because i've crashed grub etc. even trying opensuse :/
thx for help francesco!

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Closing assumed fixed.

Changed in lightdm (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
nequx (nequx-deactivatedaccount) wrote :

I can not understand how to solve this problem! Will you help me? I have one vidoeokarta computer.

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

Other bug subscribers

Remote bug watches

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