Closed pixelr0 closed 5 years ago
/var/log/syslog
Oct 3 09:53:40 pixel-desktop unity8-session[4255]: [2018-10-03:09:53:40.030] qtmir.screens: ScreensModel::ScreensModel
Oct 3 09:53:40 pixel-desktop unity8-session[4255]: [2018-10-03:09:53:40.032] QSocketNotifier: Can only be used with threads started with QThread
Oct 3 09:53:40 pixel-desktop unity8-session[4255]: [2018-10-03 09:53:40.036349] mirserver: Starting
Oct 3 09:53:40 pixel-desktop unity8-session[4255]: [2018-10-03 09:53:40.036418]
Could you do dpkg -l | grep mir
?
$ dpkg -l | grep mir ii libertine-xmir-tools 1.7.2+ubports+0~20180214124619.3~1.gbp4ae89b amd64 helper apps for using and interacting with Xmir ii libmiral2:amd64 1.5.0.0.31.0.1+0ubports2+0~20180310134906.6~1.gbpa17c3e amd64 Display server for Ubuntu - ABI preserving abstraction layer ii libmiral3:amd64 2.4.0.1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - ABI preserving abstraction layer ii libmirclient-dev:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - development headers ii libmirclient9:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - client library ii libmircommon-dev:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - development headers ii libmircommon7:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - shared library ii libmircookie-dev:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Produce and verify spoof-resistant timestamps - development headers ii libmircookie2:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Produce and verify spoof-resistant timestamps - runtime library ii libmircore-dev:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - development headers ii libmircore1:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - shared library ii libmirplatform16:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - platform library ii libmirprotobuf3:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - RPC definitions ii libmirserver45:amd64 0.28.1+18.04.20171030-ubuntu0~1309~ubuntu17.10.1 amd64 Display server for Ubuntu - server library ii libmirserver46:amd64 0.30.0-0ubuntu17.10 amd64 Display server for Ubuntu - server library ii libmirserver47:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - server library ii mir-client-platform-mesa5:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - client platform library for Mesa ii mir-demos 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - demonstration programs ii mir-graphics-drivers-desktop:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - desktop driver metapackage ii mir-platform-graphics-mesa-kms13:amd64 0.31.2-0ubuntu17.10 amd64 Display server for Ubuntu - platform library for KMS Mesa ii mir-platform-graphics-mesa-kms15:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - platform library for KMS Mesa ii mir-platform-graphics-mesa-x13:amd64 0.31.2-0ubuntu17.10 amd64 Display server for Ubuntu - platform library for X11 Mesa ii mir-platform-graphics-mesa-x15:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - platform library for X11 Mesa ii mir-platform-input-evdev7:amd64 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - input platform library ii mir-utils 1.0.0+0~20181002215523.10~1.gbpdede9b amd64 Display server for Ubuntu - utility programs ii qtdeclarative5-qtmir-plugin:amd64 0.5.3+ubports1+0~20180918223824.20~1.gbpb37293 amd64 Qt plugin for Unity specific Mir APIs ii qtmir-desktop:amd64 0.5.3+ubports1+0~20180918223824.20~1.gbpb37293 amd64 Qt platform abstraction (QPA) plugin for a Mir server (desktop) ii xmir 2:1.19.7+ubports1+0~20180221013947.2~1.gbp98d4ca amd64 Xmir X server
ummm... after the last update i can now login, yay (second try)
So we can close this now? Seems to be on par with behavior when using lightdm at least.
yep, closed
just bounces back to the login screen sddm
where can i see the logs?