Mir

Mir servers crash when using the Nvidia driver

Bug #1628478 reported by Paul
72
This bug affects 11 people
Affects Status Importance Assigned to Milestone
Mir
Triaged
Medium
Unassigned
mir (Ubuntu)
Triaged
High
Unassigned

Bug Description

I select Unity8 from the log in screen, type in my credentials and it just hangs.

Intel® Core™ i7-4710HQ CPU @ 2.50GHz × 8
GeForce GTX 860M/PCIe/SSE2

Related branches

Revision history for this message
Stephen M. Webb (bregma) wrote :

Are you using the proprietary nVidia drivers?

Changed in unity8-desktop-session (Ubuntu):
status: New → Incomplete
Revision history for this message
Paul (sabret00the) wrote :

I am indeed, version 364.44

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Hi... Mir and Unity8 do not yet support the Nvidia driver. Although we're making good progress and will do in future.

Changed in qtmir (Ubuntu):
status: New → Invalid
summary: - Cannot log into Unity8 desktop
+ Cannot log into Unity8 desktop with the Nvidia driver
affects: unity8-desktop-session (Ubuntu) → mir
Changed in mir:
assignee: nobody → Mir development team (mir-team)
importance: Undecided → High
status: Incomplete → In Progress
milestone: none → 0.25.0
milestone: 0.25.0 → none
milestone: none → 0.26.0
affects: qtmir (Ubuntu) → mir (Ubuntu)
Changed in mir (Ubuntu):
status: Invalid → Triaged
importance: Undecided → High
tags: added: enhancement nvidia
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug is actually the #1 cause of unity-system-compositor crashes too:

https://errors.ubuntu.com/problem/960c15c9c1de479829969c91769dac8ee4cb9afc

summary: - Cannot log into Unity8 desktop with the Nvidia driver
+ Mir servers crash when using the Nvidia driver
Changed in mir:
milestone: 0.26.0 → 0.25.0
Revision history for this message
Alex Kon (alkon) wrote :

It seems the next version of mir (v0.25) will support nvidia.

See bug #1628478 at https://launchpad.net/mir/+milestone/0.25.0.

The bug milestone was changed to 0.25 from 0.26 a few days ago which makes me think that much progress was made and hopefully an 0.25 release is imminent.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I'm glad you're paying attention, but that's probably an incorrect conclusion.

I only moved that bug from 0.26 to 0.25 because it was alone in a hidden future milestone and wanted it to be more visible with all our other current work. That does not mean it will all be done in time for 0.25. Some of the items in 0.25 right now will (again) move to 0.26.

Revision history for this message
Alex Kon (alkon) wrote :

Ah ok, thanks for clarifying. I actually posted the comment here by mistake - I was meaning to post it in one of the forums. I guess a lot of users are waiting for nvidia support since 16.10 shipped with unity 8.

Changed in mir:
assignee: Mir development team (mir-team) → Alberto Aguirre (albaguirre)
Changed in mir:
milestone: 0.25.0 → 0.26.0
Revision history for this message
Ivan D. Sanders (vandelsand) wrote :

This is indeed a duplicate of my new bug: https://bugs.launchpad.net/bugs/1643420

Please close one of them, I believe the one I linked is newer.

Confirmed again today with newest updates and proprietary driver 375...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

We always try to keep the oldest bug open unless for some reason there is dramatically better information in the newer duplicate. So this one stays the main bug. Bug 1643420 is 'closed' by simply being a duplicate of this one.

Changed in mir:
milestone: 0.26.0 → 1.0.0
Revision history for this message
Ivan D. Sanders (vandelsand) wrote :

I can confirm that this big still exists with Nvidia 378.13 and Unity 8 in Ubuntu 16.10 as of today.

Changed in mir:
milestone: 0.27.0 → 0.28.0
Changed in mir:
milestone: 0.28.0 → none
status: In Progress → Triaged
Changed in mir:
assignee: Alberto Aguirre (albaguirre) → nobody
Changed in mir:
importance: High → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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