[Bug 1315464] Re: Cannot login if ~/.cache is dead symlink

[Dimitri John Ledkov]

I believe this could be due to dbus job failing to start, which i have
recently fixed in unicorn. I will SRU that change into trusty as well.

** Package changed: upstart (Ubuntu) => dbus (Ubuntu)

** Also affects: dbus (Ubuntu Utopic)
   Importance: Undecided
       Status: New

** Also affects: dbus (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Changed in: dbus (Ubuntu Trusty)
       Status: New => Confirmed

** Changed in: dbus (Ubuntu Utopic)
       Status: New => Fix Released

** Changed in: dbus (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: dbus (Ubuntu Trusty)
     Assignee: (unassigned) => Dimitri John Ledkov (xnox)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1315464

Title:
  Cannot login if ~/.cache is dead symlink

Status in “dbus” package in Ubuntu:
  Fix Released
Status in “dbus” source package in Trusty:
  Confirmed
Status in “dbus” source package in Utopic:
  Fix Released

Bug description:
  On Ubuntu 14.04, graphical logins fail if ~/.cache is a dead symlink.
  Only the background picture and the mouse cursor is shown during
  login, and nothing else is started. Console logins still work.

  This happens independently of the login manager (tested lightdm, gdm,
  and kdm) and the session (tested unity, gnome-shell, kde, and xfce).
  Therefore I guess upstart (the "init --user" process) is the problem,
  as it tries to log in to ~/.cache/upstart/.

  My version of upstart is 1.12.1-0ubuntu4.

  Steps to reproduce:

  mv .cache cache.bak
  ln -s /non-existent .cache
  Try logging in.

  I would expect that logging in just works without using the .cache
  directory in this case (e.g., not logging to .cache/upstart), or that
  the dead symlink would be silently removed and the directory created,
  or that an error message would appear and login would be aborted. The
  current situation is bad because it is very hard to find the cause of
  the login problem (I just stumbled upon it by accident).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 19:42:54 2014
  InstallationDate: Installed on 2012-05-31 (700 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (6 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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