login loop on lightdm-greeter

Bug #1628439 reported by GB
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Critical
Unassigned

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)

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

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

Changed in gvfs (Ubuntu):
status: New → Confirmed
Changed in gvfs (Ubuntu):
importance: Undecided → Critical
Changed in gvfs (Ubuntu):
status: Confirmed → Incomplete
status: Incomplete → Fix Committed
dino99 (9d9)
Changed in gvfs (Ubuntu):
status: Fix Committed → Confirmed
Revision history for this message
GB (querty) wrote :

I realized that .xinputrc was corrupted due to the fact that im-config was using an non official md5sum build!
For that reason, the bus couldn't sucessfully complete its initialization and gvfs couldn't launch itself.
With the use the official md5sum (from coreutils), the .xinputrc was corrected and I could launch the graphical environment automaticaly again without issue (sudo systemctl set-default graphical.target --force)
The gvfs error was gone away from syslog.

Guillaume

Revision history for this message
dino99 (9d9) wrote :

So closing that report per comment above.

Changed in gvfs (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
GB (querty) wrote :

Not a bug. corrupted xinputrc

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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