** Changed in: lightdm
Status: Incomplete => New
** Changed in: unity-system-compositor
Status: Incomplete => New
** Changed in: lightdm (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here is a copy of my unity-system-compositor.sleep.
A failed upgrade is possible: before I upgraded to 16.10, I tried
purging a few PPAs because they are often problematic and purging the
overlay-ppa proved very difficult (ended up chasing the word "overlay"
in Synaptic to completely remove any t
Also, I don't know if there is an overlay-ppa for 16.10, but if there
is, I did not install it on my machine, so I should be using pure 16.10
repos.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/163441
Note that --on-fatal-error-abort is not a valid option, and just causes
a warning to be emitted.
And if you specify a valid option twice, it should tell you explicitly:
$ /usr/sbin/unity-system-compositor --vt 8 --vt 8
[2016-10-27 13:29:27.409922] mirplatform: Found graphics driver: mir:mesa-x11
Most likely this is an upgrade and/or upgrade+PPA problem. Please try
pure Ubuntu 16.10.
** Changed in: lightdm
Status: New => Incomplete
** Changed in: unity-system-compositor
Status: New => Incomplete
** Changed in: lightdm (Ubuntu)
Status: New => Incomplete
--
You recei
Please attach a copy of /usr/sbin/unity-system-compositor.sleep from the
affected machine.
I'm surprised boost::program_options doesn't provide more information
but we can investigate that separately...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
If your copy of /usr/sbin/unity-system-compositor.sleep is the same as mine
then the full command is:
/usr/sbin/unity-system-compositor --disable-inactivity-policy=true
--on-fatal-error-abort --file '/run/mir_socket' --from-dm-fd 12 --to-dm-fd 21
--vt 8
--
You received this bug notification be
The lightdm log shows the following being called:
/usr/sbin/unity-system-compositor.sleep --file '/run/mir_socket' --from-
dm-fd 12 --to-dm-fd 21 --vt 8
There's no duplicate entries there...
** Changed in: lightdm
Assignee: Robert Ancell (robert-ancell) => (unassigned)
--
You received thi
** Changed in: lightdm
Assignee: (unassigned) => Robert Ancell (robert-ancell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634412
Title:
Unity8 session fails to start due to unity-system-com
Is there any more log I can provide that could shed a light on this?
This bug is very easily reproducible on my computer, so I should be able
to provide relevant logs!
My computer is not a fresh install and has been upgraded every step of
the way since 14.10. I'll try a LiveUSB of 16.10 to see if
I can't reproduce any such problem on a pure 16.10 install. The error:
what(): option cannot be specified more than once
implies that your lightdm is passing an extra option when it executes
the unity-system-compositor command.
** Also affects: lightdm
Importance: Undecided
Status:
11 matches
Mail list logo
