Can not start Flashback session in 18.04 (Bionic) after update from 16.04 (Xenial)

Bug #1802094 reported by Chrescht
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-flashback (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Users authenticate against LDAP. Was fine until I upgraded to Ubuntu 18.04. /home is nfs mounted.

I've checked all logs I can find, syslog, auth, kern, lightdm, Xorg, .xsession-errors. My main suspect from auth.log is:
lightdm: pam_systemd(lightdm:session): Failed to create session: Connection timed out

There seems to be a 25 second timeout and if the session isn't ready it goes back to the login screen (here lightdm-greeter).

Something else is bugging me: when a given session DOES let me login, after restarting lightdm for whatever reason, I won't be able to log back in. It's like the lightdm restart doesn't properly terminate, and some bad clues are left in the user's home folder so that the next try will end in a login loop.

Reinstalling flashback with apt-get install --reinstall gnome-session-flashback didn't help.
~/.Xauthority is owned and writable by the owner. This has never been a problem.

No login problem for an old local account.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: GNOME-Flashback:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2016-12-18 (693 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Package: gnome-flashback 3.28.0-1ubuntu1.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Tags: bionic package-from-proposed
Uname: Linux 4.15.0-39-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-11-03 (7 days ago)
UserGroups: adm adm cdrom cdrom dip dip lpadmin lpadmin plugdev plugdev sambashare sambashare sudo sudo
_MarkForUpload: True

Revision history for this message
Alberts Muktupāvels (muktupavels) wrote :

Well this starts sound like problem is somewhere else... Do I understand correctly that you can not login only in LDAP?

Revision history for this message
Chrescht (sekateur) wrote :

A newly created local user with command adduser was also unable to login.

Revision history for this message
Dmitry Shachnev (mitya57) wrote :

Can you please run “apport-collect 1802094” on the affected machine? This command will attach some logs to this bug.

Also can you try GDM instead of LightDM? Use “sudo dpkg-reconfigure gdm3” to select the default display manager.

Or maybe even log in directly, without any DM, by entering these commands in a tty:

# systemctl stop lightdm.service
# update-alternatives --set x-session-manager /usr/lib/gnome-flashback/gnome-flashback-metacity
# startx

Then check whether it works and what it prints, and use this command to undo update-alternatives changes:

# update-alternatives --auto /usr/lib/gnome-flashback/gnome-flashback-metacity

Revision history for this message
Chrescht (sekateur) wrote : Dependencies.txt

apport information

tags: added: apport-collected bionic package-from-proposed
description: updated
Revision history for this message
Chrescht (sekateur) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Chrescht (sekateur) wrote : ProcEnviron.txt

apport information

Revision history for this message
Dmitry Shachnev (mitya57) wrote :

Unfortunately apport-collect did not attach any logs, only some information about versions.

Can you please attach the output of journalctl after unsuccessful login attempt, as suggested by Alberts in https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1753807/comments/7 ?

Revision history for this message
Chrescht (sekateur) wrote :

gdm3: didn't work when I tried a couple of days ago, wanted to test again now, but unable to do so, x11vnc doesn't want to play nice with gdm3.

no DM: flashback session seems ok. I used "update-alternatives --config x-session-manager" to undo the changes, your command with --auto didn't work.

Revision history for this message
Chrescht (sekateur) wrote :
Download full text (5.1 KiB)

journalctl _COMM=gnome-flashback
-- Logs begin at Fri 2018-11-02 19:04:45 CET, end at Sun 2018-11-11 21:43:50 CET. --
Nov 06 17:47:31 R1 gnome-flashback[11436]: failed to commit changes to dconf: The connection is closed
Nov 06 17:47:31 R1 gnome-flashback[11436]: Error unregistering authentication agent: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: T
Nov 06 17:47:31 R1 gnome-flashback[11436]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/vo
Nov 06 17:47:31 R1 gnome-flashback[11436]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/vo
-- Reboot --
Nov 06 21:06:39 R1 gnome-flashback[7089]: g_object_notify: object class 'UpClient' has no property named 'g-name-owner'
Nov 06 21:06:39 R1 gnome-flashback[7089]: gnome-flashback: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.
-- Reboot --
Nov 09 01:50:04 R1 gnome-flashback[3592]: g_object_notify: object class 'UpClient' has no property named 'g-name-owner'
Nov 09 01:50:04 R1 gnome-flashback[3592]: Couldn't upload new XKB keyboard description
Nov 09 01:50:04 R1 gnome-flashback[3592]: failed to commit changes to dconf: The connection is closed
Nov 09 01:50:04 R1 gnome-flashback[3592]: Error unregistering authentication agent: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: Th
Nov 09 01:50:04 R1 gnome-flashback[3592]: gnome-flashback: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.
-- Reboot --
Nov 11 20:58:24 R1 gnome-flashback[30233]: The owner of /home/christian/.config/ibus/bus is not root!

journalctl _COMM=gnome-panel
-- Reboot --
Nov 08 07:38:46 R1 gnome-panel[3012]: Binding '<Super>S' failed!
Nov 08 07:49:54 R1 gnome-panel.desktop[3012]: (/usr/lib/firefox/firefox:3552): dconf-WARNING **: 07:49:54.295: Unable to open /var/lib/snapd/desktop/dc
Nov 08 17:41:11 R1 gnome-panel[3012]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mount
-- Reboot --
Nov 09 01:49:35 R1 gnome-panel[3572]: Binding '<Super>S' failed!
-- Reboot --
Nov 09 07:41:39 R1 gnome-panel[1899]: Binding '<Super>S' failed!
Nov 09 10:58:59 R1 gnome-panel.desktop[1899]: (/usr/lib/firefox/firefox:3492): dconf-WARNING **: 10:58:59.943: Unable to open /var/lib/snapd/desktop/dc
-- Reboot --
Nov 11 12:35:14 R1 gnome-panel[18932]: Binding '<Super>S' failed!
Nov 11 20:28:14 R1 gnome-panel.desktop[18932]: (/usr/lib/firefox/firefox:19614): dconf-WARNING **: 20:28:14.846: Unable to open /var/lib/snapd/desktop/
Nov 11 20:30:34 R1 gnome-panel.desktop[18932]: (/usr/lib/firefox/firefox:24404): dconf-WARNING **: 20:30:34.597: Unable to open /var/lib/snapd/desktop/
Nov 11 20:31:44 R1 gnome-panel.desktop[18932]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
Nov 11 20:41:34 R1 gnome-panel.desktop[18932]: Sandbox: Unexpected EOF, op 2 flags 00 path /etc/localtime
Nov 11 20:41:34 R1 gnome-panel.desktop[18932]: Gdk-Message: 19:41:34.029: /usr/lib/firefox/firefox: Fatal IO error 11 (Ressource temporairement non dis
Nov 11 20:41:33 R1 gnome-panel[18932]: gnome-panel: Fatal IO erro...

Read more...

Revision history for this message
Alberts Muktupāvels (muktupavels) wrote :

LDAP, x11vnc... !?

Can you explain how are you using your pc? Are you accessing it only remotely?

I am not sure if that is problem, but could you check if you have correct permissions for ~./config/dconf/user? Are your user owner of that file?

Can you attach also log file for Xorg?

Revision history for this message
Chrescht (sekateur) wrote :

Accessing the pc: remotely only if I have no other choice. LDAP always though, unless there are LDAP issues, then a local account.

~./config/dconf/user: you meant ~/.config/dconf/user: yes it's owned by me

Revision history for this message
Alberts Muktupāvels (muktupavels) wrote :

Have you upgraded to 20.04? Do you have same problems?

Changed in gnome-flashback (Ubuntu):
status: New → Incomplete
Revision history for this message
Chrescht (sekateur) wrote :

Yes I have most probably already upgraded to 20.04 some time ago.
I guess this bug can be closed.

Changed in gnome-flashback (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Jesse Stone (feelthat) wrote (last edit ):
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.