You are not logged in.

#1 2016-04-19 05:22:16

becker_11
Member
From: Perth, Western Australia
Registered: 2015-12-30
Posts: 66

[Solved] Can't log in to a system I'm already logged into (seriously)

So I have an unusual problem.

Today I fired up my BL virtual machine but instead of logging in to the desktop as I normally do I just connected through ssh, ran a few updates, installed a few packages and thought everything was going just fine.
Then I decided I wanted to do some web browsing so went to log in as normal to the desktop and uh-oh I can't login.

Now obviously I haven't forgotten the password because I've just used it a bunch of times to ssh in and run updates and installs. The user name is right there in the ssh terminal so I can see I haven't got that wrong. Tried it a bunch of times with no success so now I'm wondering if there is some way given I have full terminal access the  system of unlocking, bypassing etc the lock screen and getting into the system.

The upgrade I did was 10 packages all prefixed with bl- any chance something there could have caused a glitch?

Last edited by becker_11 (2016-04-19 08:21:46)

Offline

#2 2016-04-19 05:24:48

damo
....moderator....
Registered: 2015-08-20
Posts: 6,734

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

Did you accept the change to lightdm? Perhaps that may have caused an issue.


Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#3 2016-04-19 05:52:12

becker_11
Member
From: Perth, Western Australia
Registered: 2015-12-30
Posts: 66

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

my alias for sudo apt-get update && sudo apt-get upgrade has the -y flag so it may well have done.

Offline

#4 2016-04-19 06:27:04

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,073
Website

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

becker_11 wrote:

I'm wondering if there is some way given I have full terminal access the  system of unlocking, bypassing etc the lock screen and getting into the system.

You can use this to disable LightDM:

sudo systemctl set-default multi-user.target

You can then reboot, log in at the console and use `startx` to start the desktop.

EDIT: to re-enable LightDM, use:

sudo systemctl set-default graphical.target

Have you added any new repositories or PPAs to your system?

Last edited by Head_on_a_Stick (2016-04-20 06:27:44)

Offline

#5 2016-04-19 06:57:56

becker_11
Member
From: Perth, Western Australia
Registered: 2015-12-30
Posts: 66

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

No new PPA's nor repo's. Just installed moc, moc-ffmpeg-plugin and youtube-dl plus doing a regular update/upgrade.

madoromi there was a file path update I believe to the new location for the background files if that's what they're referring to.

Offline

#6 2016-04-19 06:59:00

becker_11
Member
From: Perth, Western Australia
Registered: 2015-12-30
Posts: 66

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

Thanks HoaS I'm in. I'll just pdf up this thread in case of a repeat performance and add it to my dropbox/backups directory.

Offline

#7 2016-04-19 07:12:54

Horizon_Brave
Operating System: Linux-Nettrix
Registered: 2015-10-18
Posts: 1,473

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

huh...so is it that lightdm doesn't allow for an open ssh connection along with a local login?


"I have not failed, I have found 10,000 ways that will not work" -Edison

Offline

#8 2016-04-19 07:26:49

becker_11
Member
From: Perth, Western Australia
Registered: 2015-12-30
Posts: 66

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

@madoromi Here is the auth.log up until I restarted after running HoaS snippet that got me back in.

Apr 19 13:02:44 bunsenlabs sudo: pam_unix(sudo:session): session closed for user root
Apr 19 13:02:44 bunsenlabs sudo:   becker : TTY=pts/0 ; PWD=/home/becker ; USER=root ; COMMAND=/usr/bin/apt-get autoremove
Apr 19 13:02:44 bunsenlabs sudo: pam_unix(sudo:session): session opened for user root by becker(uid=0)
Apr 19 13:02:44 bunsenlabs sudo: pam_unix(sudo:session): session closed for user root
Apr 19 13:12:30 bunsenlabs sudo:   becker : TTY=pts/0 ; PWD=/home/becker ; USER=root ; COMMAND=/usr/bin/apt-get install moc moc
-ffmpeg-plugin ffmpeg youtube-dl
Apr 19 13:12:30 bunsenlabs sudo: pam_unix(sudo:session): session opened for user root by becker(uid=0)
Apr 19 13:13:36 bunsenlabs sudo: pam_unix(sudo:session): session closed for user root
Apr 19 13:14:13 bunsenlabs lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
Apr 19 13:14:13 bunsenlabs lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Apr 19 13:14:13 bunsenlabs systemd-logind[441]: New session c2 of user lightdm.
Apr 19 13:14:21 bunsenlabs lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
Apr 19 13:14:21 bunsenlabs systemd-logind[441]: Removed session c2.
Apr 19 13:14:21 bunsenlabs lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Apr 19 13:14:21 bunsenlabs systemd-logind[441]: New session c3 of user lightdm.
Apr 19 13:14:36 bunsenlabs lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
Apr 19 13:14:36 bunsenlabs systemd-logind[441]: Removed session c3.
Apr 19 13:14:36 bunsenlabs lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Apr 19 13:14:36 bunsenlabs systemd-logind[441]: New session c4 of user lightdm.
Apr 19 13:15:18 bunsenlabs lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
Apr 19 13:15:18 bunsenlabs systemd-logind[441]: Removed session c4.
Apr 19 13:15:18 bunsenlabs lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Apr 19 13:15:18 bunsenlabs systemd-logind[441]: New session c5 of user lightdm.
Apr 19 13:17:01 bunsenlabs CRON[4528]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 19 13:17:01 bunsenlabs CRON[4528]: pam_unix(cron:session): session closed for user root
Apr 19 14:17:01 bunsenlabs CRON[4547]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 19 14:17:01 bunsenlabs CRON[4547]: pam_unix(cron:session): session closed for user root
Apr 19 14:53:05 bunsenlabs sudo:   becker : TTY=pts/0 ; PWD=/home/becker ; USER=root ; COMMAND=/bin/systemctl set-default multi-user.target
Apr 19 14:53:05 bunsenlabs sudo: pam_unix(sudo:session): session opened for user root by becker(uid=0)
Apr 19 14:53:05 bunsenlabs sudo: pam_unix(sudo:session): session closed for user root
Apr 19 14:53:15 bunsenlabs sudo:   becker : TTY=pts/0 ; PWD=/home/becker ; USER=root ; COMMAND=/sbin/shutdown -r now

Here's the lightdm.log sorry for posting the whole thing but I wasn't able to reliably break it down and be confident I hadn't missed something.

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=552
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Registered seat module surfaceflinger
[+0.01s] DEBUG: Adding default seat
[+0.01s] DEBUG: Seat: Starting
[+0.01s] DEBUG: Seat: Creating greeter session
[+0.01s] DEBUG: Seat: Creating display server of type x
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat: Starting local X display on VT 7
[+0.01s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.01s] DEBUG: DisplayServer x-0: Launching X Server
[+0.01s] DEBUG: Launching process 559: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.02s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+0.02s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.05s] DEBUG: User becker added
[+1.27s] DEBUG: Got signal 10 from process 559
[+1.27s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+1.27s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+1.29s] DEBUG: Seat: Display server ready, starting session authentication
[+1.29s] DEBUG: Session pid=848: Started with service 'lightdm-greeter', username 'lightdm'
[+1.35s] DEBUG: Session pid=848: Authentication complete with return value 0: Success
[+1.35s] DEBUG: Seat: Session authenticated, running command
[+1.35s] DEBUG: Session pid=848: Running command /usr/sbin/lightdm-gtk-greeter
[+1.35s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+1.35s] DEBUG: Session pid=848: Logging to /var/log/lightdm/x-0-greeter.log
[+1.41s] DEBUG: Activating VT 7
[+1.41s] DEBUG: Activating login1 session c1
[+1.67s] DEBUG: Session pid=848: Greeter connected version=1.10.3
[+2.17s] DEBUG: Session pid=848: Greeter start authentication
[+2.17s] DEBUG: Session pid=872: Started with service 'lightdm', username '(null)'
[+2.19s] DEBUG: Session pid=872: Got 1 message(s) from PAM
[+2.19s] DEBUG: Session pid=848: Prompt greeter with 1 message(s)
[+1005.87s] DEBUG: Session pid=848: Greeter start authentication for becker
[+1005.87s] DEBUG: Session pid=872: Sending SIGTERM
[+1005.87s] DEBUG: Session pid=4472: Started with service 'lightdm', username 'becker'
[+1005.87s] DEBUG: Session pid=872: Terminated with signal 15
[+1005.87s] DEBUG: Session: Failed during authentication
[+1005.87s] DEBUG: Seat: Session stopped
[+1005.88s] DEBUG: Session pid=4472: Got 1 message(s) from PAM
[+1005.88s] DEBUG: Session pid=848: Prompt greeter with 1 message(s)
[+1010.31s] DEBUG: Session pid=848: Continue authentication
[+1010.33s] DEBUG: Session pid=4472: Authentication complete with return value 0: Success
[+1010.33s] DEBUG: Session pid=848: Authenticate result for user becker: Success
[+1010.33s] DEBUG: Session pid=848: User becker authorized
[+1010.33s] DEBUG: Session pid=848: Greeter sets language en_AU.utf8
[+1010.34s] DEBUG: Session pid=848: Greeter requests session lightdm-xsession
[+1010.34s] DEBUG: Seat: Stopping greeter; display server will be re-used for user session
[+1010.34s] DEBUG: Session pid=848: Sending SIGTERM
[+1010.35s] DEBUG: Session pid=848: Greeter closed communication channel
[+1010.35s] DEBUG: Session pid=848: Exited with return value 0
[+1010.35s] DEBUG: Seat: Session stopped
[+1010.35s] DEBUG: Seat: Greeter stopped, running session
[+1010.35s] DEBUG: Launching process 4475: /usr/lib/bunsen/bunsen-configs/bl-user-setup
[+1010.36s] DEBUG: Process 4475 exited with return value 1
[+1010.36s] DEBUG: Seat: Exit status of /usr/lib/bunsen/bunsen-configs/bl-user-setup: 1
[+1010.36s] DEBUG: Seat: Switching to greeter due to failed setup script
[+1010.36s] DEBUG: Seat: Creating greeter session
[+1010.36s] DEBUG: Session pid=4476: Started with service 'lightdm-greeter', username 'lightdm'
[+1010.36s] DEBUG: Session pid=4472: Exited with return value 0
[+1010.36s] DEBUG: Seat: Session stopped
[+1010.37s] DEBUG: Session pid=4476: Authentication complete with return value 0: Success
[+1010.37s] DEBUG: Seat: Session authenticated, running command
[+1010.37s] DEBUG: Session pid=4476: Running command /usr/sbin/lightdm-gtk-greeter
[+1010.37s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+1010.37s] DEBUG: Session pid=4476: Logging to /var/log/lightdm/x-0-greeter.log
[+1010.38s] DEBUG: Activating VT 7
[+1010.38s] DEBUG: Activating login1 session c2
[+1010.40s] DEBUG: Session pid=4476: Greeter connected version=1.10.3
[+1010.54s] DEBUG: Session pid=4476: Greeter start authentication
[+1010.54s] DEBUG: Session pid=4483: Started with service 'lightdm', username '(null)'
[+1010.55s] DEBUG: Session pid=4483: Got 1 message(s) from PAM
[+1010.55s] DEBUG: Session pid=4476: Prompt greeter with 1 message(s)
[+1013.40s] DEBUG: Session pid=4476: Greeter start authentication for becker
[+1013.40s] DEBUG: Session pid=4483: Sending SIGTERM
[+1013.40s] DEBUG: Session pid=4485: Started with service 'lightdm', username 'becker'
[+1013.40s] DEBUG: Session pid=4483: Terminated with signal 15
[+1013.40s] DEBUG: Session: Failed during authentication
[+1013.40s] DEBUG: Seat: Session stopped
[+1013.41s] DEBUG: Session pid=4485: Got 1 message(s) from PAM
[+1013.41s] DEBUG: Session pid=4476: Prompt greeter with 1 message(s)
[+1018.28s] DEBUG: Session pid=4476: Continue authentication
[+1018.31s] DEBUG: Session pid=4485: Authentication complete with return value 0: Success
[+1018.31s] DEBUG: Session pid=4476: Authenticate result for user becker: Success
[+1018.31s] DEBUG: Session pid=4476: User becker authorized
[+1018.31s] DEBUG: Session pid=4476: Greeter sets language en_AU.utf8
[+1018.31s] DEBUG: Session pid=4476: Greeter requests session lightdm-xsession
[+1018.31s] DEBUG: Seat: Stopping greeter; display server will be re-used for user session
[+1018.31s] DEBUG: Session pid=4476: Sending SIGTERM
[+1018.33s] DEBUG: Session pid=4476: Greeter closed communication channel
[+1018.33s] DEBUG: Session pid=4476: Exited with return value 0
[+1018.33s] DEBUG: Seat: Session stopped
[+1018.33s] DEBUG: Seat: Greeter stopped, running session
[+1018.33s] DEBUG: Launching process 4489: /usr/lib/bunsen/bunsen-configs/bl-user-setup
[+1018.33s] DEBUG: Process 4489 exited with return value 1
[+1018.33s] DEBUG: Seat: Exit status of /usr/lib/bunsen/bunsen-configs/bl-user-setup: 1
[+1018.33s] DEBUG: Seat: Switching to greeter due to failed setup script
[+1018.33s] DEBUG: Seat: Creating greeter session
[+1018.33s] DEBUG: Session pid=4490: Started with service 'lightdm-greeter', username 'lightdm'
[+1018.33s] DEBUG: Session pid=4485: Exited with return value 0
[+1018.33s] DEBUG: Seat: Session stopped
[+1018.35s] DEBUG: Session pid=4490: Authentication complete with return value 0: Success
[+1018.35s] DEBUG: Seat: Session authenticated, running command
[+1018.35s] DEBUG: Session pid=4490: Running command /usr/sbin/lightdm-gtk-greeter
[+1018.35s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+1018.35s] DEBUG: Session pid=4490: Logging to /var/log/lightdm/x-0-greeter.log
[+1018.36s] DEBUG: Activating VT 7
[+1018.36s] DEBUG: Activating login1 session c3
[+1018.38s] DEBUG: Session pid=4490: Greeter connected version=1.10.3
[+1018.51s] DEBUG: Session pid=4490: Greeter start authentication
[+1018.51s] DEBUG: Session pid=4497: Started with service 'lightdm', username '(null)'
[+1018.52s] DEBUG: Session pid=4497: Got 1 message(s) from PAM
[+1018.52s] DEBUG: Session pid=4490: Prompt greeter with 1 message(s)
[+1025.98s] DEBUG: Session pid=4490: Greeter start authentication for becker
[+1025.98s] DEBUG: Session pid=4497: Sending SIGTERM
[+1025.98s] DEBUG: Session pid=4499: Started with service 'lightdm', username 'becker'
[+1025.98s] DEBUG: Session pid=4497: Terminated with signal 15
[+1025.98s] DEBUG: Session: Failed during authentication
[+1025.98s] DEBUG: Seat: Session stopped
[+1025.99s] DEBUG: Session pid=4499: Got 1 message(s) from PAM
[+1025.99s] DEBUG: Session pid=4490: Prompt greeter with 1 message(s)
[+1033.07s] DEBUG: Session pid=4490: Continue authentication
[+1033.09s] DEBUG: Session pid=4499: Authentication complete with return value 0: Success
[+1033.09s] DEBUG: Session pid=4490: Authenticate result for user becker: Success
[+1033.09s] DEBUG: Session pid=4490: User becker authorized
[+1033.09s] DEBUG: Session pid=4490: Greeter sets language en_AU.utf8
[+1033.09s] DEBUG: Session pid=4490: Greeter requests session lightdm-xsession
[+1033.09s] DEBUG: Seat: Stopping greeter; display server will be re-used for user session
[+1033.09s] DEBUG: Session pid=4490: Sending SIGTERM
[+1033.11s] DEBUG: Session pid=4490: Greeter closed communication channel
[+1033.11s] DEBUG: Session pid=4490: Exited with return value 0
[+1033.11s] DEBUG: Seat: Session stopped
[+1033.11s] DEBUG: Seat: Greeter stopped, running session
[+1033.11s] DEBUG: Launching process 4503: /usr/lib/bunsen/bunsen-configs/bl-user-setup
[+1033.11s] DEBUG: Process 4503 exited with return value 1
[+1033.11s] DEBUG: Seat: Exit status of /usr/lib/bunsen/bunsen-configs/bl-user-setup: 1
[+1033.11s] DEBUG: Seat: Switching to greeter due to failed setup script
[+1033.11s] DEBUG: Seat: Creating greeter session
[+1033.11s] DEBUG: Session pid=4504: Started with service 'lightdm-greeter', username 'lightdm'
[+1033.11s] DEBUG: Session pid=4499: Exited with return value 0
[+1033.11s] DEBUG: Seat: Session stopped
[+1033.13s] DEBUG: Session pid=4504: Authentication complete with return value 0: Success
[+1033.13s] DEBUG: Seat: Session authenticated, running command
[+1033.13s] DEBUG: Session pid=4504: Running command /usr/sbin/lightdm-gtk-greeter
[+1033.13s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+1033.13s] DEBUG: Session pid=4504: Logging to /var/log/lightdm/x-0-greeter.log
[+1033.13s] DEBUG: Activating VT 7
[+1033.13s] DEBUG: Activating login1 session c4
[+1033.16s] DEBUG: Session pid=4504: Greeter connected version=1.10.3
[+1033.30s] DEBUG: Session pid=4504: Greeter start authentication
[+1033.30s] DEBUG: Session pid=4511: Started with service 'lightdm', username '(null)'
[+1033.32s] DEBUG: Session pid=4511: Got 1 message(s) from PAM
[+1033.32s] DEBUG: Session pid=4504: Prompt greeter with 1 message(s)
[+1036.39s] DEBUG: Session pid=4504: Cancel authentication
[+1036.39s] DEBUG: Session pid=4511: Sending SIGTERM
[+1036.39s] DEBUG: Session pid=4511: Terminated with signal 15
[+1036.39s] DEBUG: Session: Failed during authentication
[+1036.39s] DEBUG: Seat: Session stopped
[+1036.39s] DEBUG: Session pid=4504: Greeter start authentication
[+1036.39s] DEBUG: Session pid=4512: Started with service 'lightdm', username '(null)'
[+1036.40s] DEBUG: Session pid=4512: Got 1 message(s) from PAM
[+1036.40s] DEBUG: Session pid=4504: Prompt greeter with 1 message(s)
[+1037.06s] DEBUG: Session pid=4504: Cancel authentication
[+1037.06s] DEBUG: Session pid=4512: Sending SIGTERM
[+1037.06s] DEBUG: Session pid=4512: Terminated with signal 15
[+1037.06s] DEBUG: Session: Failed during authentication
[+1037.06s] DEBUG: Seat: Session stopped
[+1037.06s] DEBUG: Session pid=4504: Greeter start authentication
[+1037.06s] DEBUG: Session pid=4513: Started with service 'lightdm', username '(null)'
[+1037.07s] DEBUG: Session pid=4513: Got 1 message(s) from PAM
[+1037.07s] DEBUG: Session pid=4504: Prompt greeter with 1 message(s)
[+1068.32s] DEBUG: Session pid=4504: Greeter start authentication for becker
[+1068.32s] DEBUG: Session pid=4513: Sending SIGTERM
[+1068.32s] DEBUG: Session pid=4515: Started with service 'lightdm', username 'becker'
[+1068.32s] DEBUG: Session pid=4513: Terminated with signal 15
[+1068.32s] DEBUG: Session: Failed during authentication
[+1068.32s] DEBUG: Seat: Session stopped
[+1068.33s] DEBUG: Session pid=4515: Got 1 message(s) from PAM
[+1068.33s] DEBUG: Session pid=4504: Prompt greeter with 1 message(s)
[+1075.05s] DEBUG: Session pid=4504: Continue authentication
[+1075.07s] DEBUG: Session pid=4515: Authentication complete with return value 0: Success
[+1075.07s] DEBUG: Session pid=4504: Authenticate result for user becker: Success
[+1075.07s] DEBUG: Session pid=4504: User becker authorized
[+1075.07s] DEBUG: Session pid=4504: Greeter sets language en_AU.utf8
[+1075.07s] DEBUG: Session pid=4504: Greeter requests session lightdm-xsession
[+1075.07s] DEBUG: Seat: Stopping greeter; display server will be re-used for user session
[+1075.07s] DEBUG: Session pid=4504: Sending SIGTERM
[+1075.09s] DEBUG: Session pid=4504: Greeter closed communication channel
[+1075.09s] DEBUG: Session pid=4504: Exited with return value 0
[+1075.09s] DEBUG: Seat: Session stopped
[+1075.09s] DEBUG: Seat: Greeter stopped, running session
[+1075.09s] DEBUG: Launching process 4519: /usr/lib/bunsen/bunsen-configs/bl-user-setup
[+1075.10s] DEBUG: Process 4519 exited with return value 1
[+1075.10s] DEBUG: Seat: Exit status of /usr/lib/bunsen/bunsen-configs/bl-user-setup: 1
[+1075.10s] DEBUG: Seat: Switching to greeter due to failed setup script
[+1075.10s] DEBUG: Seat: Creating greeter session
[+1075.10s] DEBUG: Session pid=4520: Started with service 'lightdm-greeter', username 'lightdm'
[+1075.10s] DEBUG: Session pid=4515: Exited with return value 0
[+1075.10s] DEBUG: Seat: Session stopped
[+1075.11s] DEBUG: Session pid=4520: Authentication complete with return value 0: Success
[+1075.11s] DEBUG: Seat: Session authenticated, running command
[+1075.11s] DEBUG: Session pid=4520: Running command /usr/sbin/lightdm-gtk-greeter
[+1075.11s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+1075.11s] DEBUG: Session pid=4520: Logging to /var/log/lightdm/x-0-greeter.log
[+1075.12s] DEBUG: Activating VT 7
[+1075.12s] DEBUG: Activating login1 session c5
[+1075.15s] DEBUG: Session pid=4520: Greeter connected version=1.10.3
[+1075.29s] DEBUG: Session pid=4520: Greeter start authentication
[+1075.29s] DEBUG: Session pid=4527: Started with service 'lightdm', username '(null)'
[+1075.31s] DEBUG: Session pid=4527: Got 1 message(s) from PAM
[+1075.31s] DEBUG: Session pid=4520: Prompt greeter with 1 message(s)
[+6952.04s] DEBUG: Session pid=4520: Greeter closed communication channel
[+6952.04s] DEBUG: Session pid=4520: Terminated with signal 1
[+6952.04s] DEBUG: Seat: Session stopped
[+6952.04s] DEBUG: Seat: Stopping; failed to start a greeter
[+6952.04s] DEBUG: Seat: Stopping
[+6952.04s] DEBUG: Seat: Stopping display server
[+6952.04s] DEBUG: Sending signal 15 to process 559
[+6952.04s] DEBUG: Seat: Stopping session
[+6952.04s] DEBUG: Session pid=4527: Sending SIGTERM
[+6952.04s] DEBUG: Session pid=4527: Terminated with signal 15
[+6952.04s] DEBUG: Session: Failed during authentication
[+6952.04s] DEBUG: Seat: Session stopped
[+6952.07s] DEBUG: Got signal 15 from process 1
[+6952.07s] DEBUG: Caught Terminated signal, shutting down
[+6952.07s] DEBUG: Stopping display manager

Last edited by becker_11 (2016-04-19 09:08:22)

Offline

#9 2016-04-19 15:47:52

damo
....moderator....
Registered: 2015-08-20
Posts: 6,734

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

madoromi wrote:
damo wrote:

Did you accept the change to lightdm? Perhaps that may have caused an issue.

What change "to lightdm"? Changing from some other dm to lightdm or modifying something about lightdm?

Configuration file '/etc/lightdm/lightdm.conf.bunsen'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** lightdm.conf.bunsen (Y/I/N/O/D/Z) [default=N] ? 

Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#10 2016-04-19 19:14:53

username
Member
Registered: 2016-02-13
Posts: 8

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

I accepted the default but couldn't login

short version. lightdm.conf line 114:
  session-setup-script=/usr/lib/bunsen/bunsen-configs/bl-user-setup

changed to:
  session-setup-script=/usr/lib/bunsen/configs/bl-user-setup

solved the login problem for  me in case it helps anyone.

Offline

#11 2016-04-19 23:33:04

exe
Member
Registered: 2015-09-29
Posts: 123

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

Head_on_a_Stick wrote:
becker_11 wrote:

I'm wondering if there is some way given I have full terminal access the  system of unlocking, bypassing etc the lock screen and getting into the system.

You can use this to disable LightDM:

sudo systemctl set-default multi-user.target

You can then reboot, log in at the console and use `startx` to start the desktop.

Have you added any new repositories or PPAs to your system?



hi..



How i can activate LighDM again ??

Offline

#12 2016-04-19 23:49:40

damo
....moderator....
Registered: 2015-08-20
Posts: 6,734

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

exe wrote:

...
How i can activate LighDM again ??

sudo systemctl enable lightdm.service

Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#13 2016-04-20 00:30:45

Horizon_Brave
Operating System: Linux-Nettrix
Registered: 2015-10-18
Posts: 1,473

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

Head_on_a_Stick wrote:
becker_11 wrote:

I'm wondering if there is some way given I have full terminal access the  system of unlocking, bypassing etc the lock screen and getting into the system.

You can use this to disable LightDM:

sudo systemctl set-default multi-user.target

You can then reboot, log in at the console and use `startx` to start the desktop.

Do you really need to switch targets for this? shouldn't startx run just from him being logged in via ssh to whatever user he's logged into?


"I have not failed, I have found 10,000 ways that will not work" -Edison

Offline

#14 2016-04-20 06:26:12

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,073
Website

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

exe wrote:

How i can activate LighDM again ??

Ah yes, sorry  :8

sudo systemctl set-default graphical.target

Offline

#15 2016-04-20 14:31:52

exe
Member
Registered: 2015-09-29
Posts: 123

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

Head_on_a_Stick wrote:
exe wrote:

How i can activate LighDM again ??

Ah yes, sorry  :8

sudo systemctl set-default graphical.target


OK.. thanks !!

Offline

#16 2016-04-20 19:41:41

Horizon_Brave
Operating System: Linux-Nettrix
Registered: 2015-10-18
Posts: 1,473

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

Just to be clear about this everyone...The few login issues, and wallpaper /nitrogen issues that we've seen recently, are all tied to a slight hiccup with the file path change correct?


"I have not failed, I have found 10,000 ways that will not work" -Edison

Offline

#17 2016-04-20 20:02:43

damo
....moderator....
Registered: 2015-08-20
Posts: 6,734

Re: [Solved] Can't log in to a system I'm already logged into (seriously)

Horizon_Brave wrote:

Just to be clear about this everyone...The few login issues, and wallpaper /nitrogen issues that we've seen recently, are all tied to a slight hiccup with the file path change correct?

The login hiccup is when someone has edited lightdm.conf, and not chosen "Y" to accept the changes, in the question during the upgrade. The wallpaper issues generally go away if the symlink(s) is/are made correctly.


Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

Board footer

Powered by FluxBB