[Bug 1185592] Re: No logind session after upgrade

[Diego Andres]

diego at sdra: ~ $ loginctl
   SESSION        UID USER             SEAT            

0 sessions listed.


diego at sdra: ~ $ loginctl show-session
ControlGroupHierarchy=/user
NAutoVTs=6
KillExcludeUsers=root
KillUserProcesses=no
IdleHint=yes
IdleSinceHint=0
IdleSinceHintMonotonic=0
InhibitDelayMaxUSec=5s
HandlePowerKey=poweroff
HandleSuspendKey=suspend
HandleHibernateKey=hibernate
HandleLidSwitch=suspend
IdleAction=ignore
IdleActionUSec=30min
PreparingForShutdown=no
PreparingForSleep=no


diego at sdra: ~ $ cat /etc/pam.d/common-session
#
# /etc/pam.d/common-session - session-related modules common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of modules that define tasks to be performed
# at the start and end of sessions of *any* kind (both interactive and
# non-interactive).
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules.  See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
session	[default=1]			pam_permit.so
# here's the fallback if no module succeeds
session	requisite			pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
session	required			pam_permit.so
# The pam_umask module will set the umask according to the system default in
# /etc/login.defs and user settings, solving the problem of different
# umask settings with different shells, display managers, remote sessions etc.
# See "man pam_umask".
session optional			pam_umask.so
# and here are more per-package modules (the "Additional" block)
session	required	pam_unix.so 
session	optional			pam_winbind.so 
session	optional			pam_xdg_support.so 
session	optional	pam_ecryptfs.so unwrap
session	optional			pam_ck_connector.so nox11
# end of pam-auth-update config

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

Title:
  No logind session after upgrade

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  dist-upgraded by accident to 13.10... no permissions for audio...
  after adding user diego to audio group in /etc/group, audio works
  again, but still does not mount devices (and internal disks)... also
  does not show shutdown/restart buttons but logout/lock instead...
  after latest aptitude upgrade network manager does not have
  permissions to connect (I need to sudo dhclient eth0)...

  probably related to lack of permissions for dbus

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: udev 202-0ubuntu10
  ProcVersionSignature: Ubuntu 3.9.0-1.5-generic 3.9.1
  Uname: Linux 3.9.0-1-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: i386
  CustomUdevRuleFiles: z80_user.rules 51-android.rules 10-vboxdrv.rules
  Date: Wed May 29 23:47:17 2013
  HotplugNewDevices: /dev/sdd /dev/sdd1
  HotplugNewMounts:

  InstallationDate: Installed on 2010-01-14 (1231 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-1-generic root=UUID=5d1c6d4a-087c-4274-9161-724bdde1248c ro quiet splash
  SourcePackage: systemd
  Symptom: storage
  Title: Does not detect hotplugged storage device
  UpgradeStatus: Upgraded to saucy on 2013-05-12 (17 days ago)
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd11/23/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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