Confirmed.

The problem is unity8 crashes/exits for the second user, right after:

[2017-03-16:09:39:09.588] QStandardPaths: XDG_RUNTIME_DIR not set, defaulting 
to '/tmp/runtime-testuser'
[2017-03-16:09:39:09.588] qtmir.screens: ScreensModel::ScreensModel
[2017-03-16:09:39:09.589] QSocketNotifier: Can only be used with threads 
started with QThread
[2017-03-16 09:39:09.592597] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.1)
[2017-03-16 09:39:09.592630] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.1)
[2017-03-16 09:39:09.592766] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.26.1)
[2017-03-16 09:39:09.592775] mirplatform: Found graphics driver: 
throw-on-creation (version 0.26.1)
[2017-03-16 09:39:09.593183] mirserver: Starting
[2017-03-16 09:39:09.607913] mirserver: Using nested cursor
[2017-03-16:09:39:09.608] qtmir.mir: 
PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x7fe14c16bc50)
[2017-03-16:09:39:09.608] qtmir.mir: 
PromptSessionListener::~PromptSessionListener - this= 
PromptSessionListener(0x7fe14c16bc50)
[2017-03-16:09:39:09.610] bind: Permission denied

Also confirmed the high CPU usage that follows. That's unity8-dash for
the second user continuously restarting (because there is no server for
it to connect to) -> bug 1578469

** Changed in: mir
       Status: New => Incomplete

** Changed in: mir (Ubuntu)
       Status: Confirmed => Incomplete

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => High

** Changed in: mir (Ubuntu)
   Importance: Undecided => High

** Changed in: mir
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1673215

Title:
  Second unity8 user session hangs with a black screen

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Login to user1 using u8 as the session
  login to a second session and select u8 as the session

  The screen goes black and the fan comes on indicating something is in a tight 
loop
  Waited for several minutes and it stays in that state. A hard power cycle is 
needed.

  This is with the Zesty as of 3/15, no extra packages installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673215/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to