Ubuntu
ubuntu-system-settings package

image 185 --wipe causes unity 8 not to show up on first boot (after welcome wizard)

Bug #1355726 reported by Zygmunt Krynicki
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mir (Ubuntu)
Invalid
Undecided
Unassigned
ubuntu-system-settings (Ubuntu)
Fix Released
Critical
Michael Terry
unity8 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Do a 185 --wipe upgrade. Pass the initial boot wizard. Go to unity 8 and see black screen. Gave it 5 minutes then rebooted (using the phone UI to do it). The problem goes away after that reboot.

Related branches

lp:~mterry/ubuntu-system-settings/careful-sockets
PS Jenkins bot: Approve (continuous-integration)
Ken VanDine: Approve
Michał Sawicz (community): Approve
Diff: 12 lines (+1/-3)
1 file modified
wizard/ubuntu-system-settings-wizard.conf (+1/-3)
Zygmunt Krynicki (zyga)
Changed in ubuntu-system-settings (Ubuntu):
assignee: nobody → Michael Terry (mterry)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubuntu-system-settings (Ubuntu):
status: New → Confirmed
Revision history for this message
Michał Sawicz (saviq) wrote :

There's a suspicion env isn't set up properly after the wizard.

Revision history for this message
Michał Sawicz (saviq) wrote :

Although:
phablet@ubuntu-phablet:~$ initctl list-env -g | grep MIR
MIR_SERVER_NAME=session-0
MIR_SERVER_PROMPT_FILE=1
MIR_SOCKET=/run/user/32011/mir_socket
UNITY_MIR_SOCKET=/run/mir_socket
WIZARD_ORIG_MIR_SOCKET=/run/mir_socket

phablet@ubuntu-phablet:~$ initctl list-env unity8-dash | grep MIR
MIR_SERVER_NAME=session-0
MIR_SERVER_PROMPT_FILE=1
MIR_SOCKET=/run/user/32011/mir_socket
UNITY_MIR_SOCKET=/run/mir_socket
WIZARD_ORIG_MIR_SOCKET=/run/mir_socket

Revision history for this message
Michał Sawicz (saviq) wrote :

But still, unity8-dash.log:

UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is running, and the correct socket is being used and is accessible. The shell may have rejected the incoming connection, so check its log file

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity8 (Ubuntu):
status: New → Confirmed
Revision history for this message
Dave Morley (davmor2) wrote :

After some digging this isn't the Wizzard causing the issue, If you do a reboot then remove the ~/.config/ubuntu-system-settings/wizard-has-run the wizzard runs and is closed correctly and the unity8-dash appears as expected.

tags: added: mako qa-daily-testing rtn14 u185
tags: added: rtm14
removed: rtn14
Revision history for this message
Michael Terry (mterry) wrote :

That error could also be due to a bad QT_QPA_PLATFORM value...

Revision history for this message
Michael Terry (mterry) wrote :

I just tried this on a non-mako machine with r185 and it worked fine. Will try with mako next.

Revision history for this message
Michael Terry (mterry) wrote :

Nor on mako. How reproducable is this for folks?

Changed in ubuntu-system-settings (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Zygmunt Krynicki (zyga) wrote : Re: [Bug 1355726] Re: image 185 --wipe causes unity 8 not to show up on first boot (after welcome wizard)

I don't want to --wipe again but I tried this on both mako and
non-mako. Not sure what else I can do.

On Tue, Aug 12, 2014 at 6:42 PM, Michael Terry
<email address hidden> wrote:
> Nor on mako. How reproducable is this for folks?
>
> ** Changed in: ubuntu-system-settings (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1355726
>
> Title:
> image 185 --wipe causes unity 8 not to show up on first boot (after
> welcome wizard)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1355726/+subscriptions

Revision history for this message
Dave Morley (davmor2) wrote :

It was happening for me very reliably but now I'm trying to confirm some things of course it isn't :)

Łukasz Zemczak (sil2100)
tags: added: lt-blocker lt-category-visible lt-prio-high
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Reproduced with build 187 on mako

Changed in ubuntu-system-settings (Ubuntu):
importance: Undecided → Critical
status: Incomplete → Confirmed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

And this is what I see when it happens.
No greeter, no spinner, no dash and no wizard.

Revision history for this message
Michał Sawicz (saviq) wrote :

Thanks to mterry we tracked this down to:
- changing language in wizard causes this
- results from the mir server socket being absent (even though the trusted one is)

Changed in unity8 (Ubuntu):
status: Confirmed → In Progress
Michał Sawicz (saviq)
Changed in ubuntu-system-settings (Ubuntu):
status: Confirmed → In Progress
Changed in unity8 (Ubuntu):
status: In Progress → Invalid
Changed in mir (Ubuntu):
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-system-settings - 0.3+14.10.20140814-0ubuntu1

---------------
ubuntu-system-settings (0.3+14.10.20140814-0ubuntu1) utopic; urgency=low

  [ Michael Terry ]
  * Avoid a race condition when cleaning up the wizard's Mir socket.
    This way we won't delete unity8's Mir socket out from under it. (LP:
    #1355726)
 -- Ubuntu daily release <email address hidden> Thu, 14 Aug 2014 00:37:03 +0000

Changed in ubuntu-system-settings (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

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