Public bug reported:

After an upgrade of the system not possible anymore to login using 
lightdm-greeter.
Tried dpkg-reconfigure on all major DM package - no success
Looking for errors in PAM - no authentication errors
Looking for errors in syslog ;
org.gtk.vfs.Daemon[7528]: A connection to the bus can't be made

seems same problem that Bug #1571206 reported by dino99 on 2016-04-16
but with different symptoms.

Workaround ; put the system boot into text mode then "startx" works everytime
(and doesn't trigger gvfs error)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gvfs 1.28.2-1ubuntu1~16.04.1
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: MATE
Date: Wed Sep 28 11:28:04 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-06-01 (118 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gvfs (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug xenial

** Attachment added: "This file describe the upgrade of the system - before 
apply it works, after it fails"
   https://bugs.launchpad.net/bugs/1628439/+attachment/4750058/+files/fuck4

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1628439

Title:
  login loop on lightdm-greeter

Status in gvfs package in Ubuntu:
  New

Bug description:
  After an upgrade of the system not possible anymore to login using 
lightdm-greeter.
  Tried dpkg-reconfigure on all major DM package - no success
  Looking for errors in PAM - no authentication errors
  Looking for errors in syslog ;
  org.gtk.vfs.Daemon[7528]: A connection to the bus can't be made

  seems same problem that Bug #1571206 reported by dino99 on 2016-04-16
  but with different symptoms.

  Workaround ; put the system boot into text mode then "startx" works everytime
  (and doesn't trigger gvfs error)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs 1.28.2-1ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Sep 28 11:28:04 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-06-01 (118 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Reply via email to