@Michal Sawicz, as far as I understand the problem in bug #1526658, my
problem is not due to wrong/old packages.

LC_ALL=C apt-cache policy libmirclient9
libmirclient9:
  Installed: 0.19.2+16.04.20160210-0ubuntu1
  Candidate: 0.19.3+16.04.20160212-0ubuntu1
  Version table:
     0.19.3+16.04.20160212-0ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
 *** 0.19.2+16.04.20160210-0ubuntu1 100
        100 /var/lib/dpkg/status

C_ALL=C apt-cache policy libmirserver37
libmirserver37:
  Installed: 0.19.2+16.04.20160210-0ubuntu1
  Candidate: 0.19.3+16.04.20160212-0ubuntu1
  Version table:
     0.19.3+16.04.20160212-0ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
 *** 0.19.2+16.04.20160210-0ubuntu1 100
        100 /var/lib/dpkg/status

dpkg -l | grep mir
ii  libmirclient9:amd64                                  
0.19.2+16.04.20160210-0ubuntu1              amd64        
ii  libmircommon5:amd64                                  
0.19.2+16.04.20160210-0ubuntu1              amd64       
ii  libmircookie2:amd64                                  
0.19.2+16.04.20160210-0ubuntu1              amd64       
ii  libmirplatform11:amd64                               
0.19.2+16.04.20160210-0ubuntu1              amd64        
ii  libmirprotobuf3:amd64                                
0.19.2+16.04.20160210-0ubuntu1              amd64        
ii  libmirserver37:amd64                                 
0.19.2+16.04.20160210-0ubuntu1              amd64        
ii  mir-client-platform-mesa4:amd64                      
0.19.2+16.04.20160210-0ubuntu1              amd64        
ii  mir-graphics-drivers-desktop:amd64                   
0.19.2+16.04.20160210-0ubuntu1              amd64        
ii  mir-platform-graphics-mesa-kms7:amd64                
0.19.2+16.04.20160210-0ubuntu1              amd64        
ii  mir-platform-graphics-mesa-x7:amd64                  
0.19.2+16.04.20160210-0ubuntu1              amd64        
ii  mir-platform-input-evdev5:amd64                      
0.19.2+16.04.20160210-0ubuntu1              amd64        
ii  qtdeclarative5-qtmir-plugin:amd64                    
0.4.7+16.04.20160208-0ubuntu1               amd64        
ii  qtmir-desktop:amd64                                  
0.4.7+16.04.20160208-0ubuntu1               amd64        
ii  unity8-desktop-session-mir                           
1.0.12+15.10.20150609-0ubuntu1              all 

I have some updates for mir-client-platform-mesa4, mir-graphics-drivers-
desktop, mir-platform-graphics-mesa-kms7, mir-platform-graphics-mesa-x7,
mir-platform-input-evdev5 and unity8. I am going to update system and
try to see if these updates fiz the issue.

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

Title:
  Unity8 crashes with Intel Sandybridge on 16.04

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I can not log in to Unity8 session on Ubuntu 16.04. When I try to log in to 
Unity8 session, only a black screen is shown. And when I return to Unity7 
session, I get a crash report from apport.
  --- 
  ApportVersion: 2.20-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160208-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Tags:  xenial
  Uname: Linux 4.4.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1545784/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to