upgrade from 16.04 to 18.04, lock screen is stuck
Clash Royale CLAN TAG#URR8PPP up vote
5
down vote
favorite
Right now I'm upgrading a fairly clean install of 16.04 to 18.04 and it seems to be stuck.
I mean, after some time into the upgrade it went on screen lock and I typed my username and password and it seems to be stuck saying: 'unlocking...'
No idea if this is due to the update still running hogging system resourcing or something else is going on.
I can switch with CtrlAlt+Fkeys but that just gives me black screens and impossible to tell if the upgrade is still running/finished of something terrible happened...
Any idea's? (cant log in with ssh because I haven't installed ssh server on this laptop)
16.04 upgrade lock-screen 18.04
edited Apr 30 at 9:55
Eranda Peiris
661416
asked Apr 30 at 9:44
geegee
15615
 |Â
show 7 more comments
up vote
5
down vote
favorite
Right now I'm upgrading a fairly clean install of 16.04 to 18.04 and it seems to be stuck.
I mean, after some time into the upgrade it went on screen lock and I typed my username and password and it seems to be stuck saying: 'unlocking...'
No idea if this is due to the update still running hogging system resourcing or something else is going on.
I can switch with CtrlAlt+Fkeys but that just gives me black screens and impossible to tell if the upgrade is still running/finished of something terrible happened...
Any idea's? (cant log in with ssh because I haven't installed ssh server on this laptop)
16.04 upgrade lock-screen 18.04
edited Apr 30 at 9:55
Eranda Peiris
661416
asked Apr 30 at 9:44
geegee
15615
now also using alt ctrl + F keys is unresponsive.
– geegee
Apr 30 at 10:00
Have you tried switching to a terminal (ctrl+alt+f4 or your favorite fn key) and logging in there, looking at what's happening (top,iotopetc)
– guiverc
Apr 30 at 10:07
@guiverc as mentioned before, they give me a black screen instead of a login.
– geegee
Apr 30 at 10:08
sorry I didn't know what CTRL+ALT+F did or meant (actually tried the combination on my 18.04 and it did nothing) never realizing you meant Fn keys.
– guiverc
Apr 30 at 10:09
@guiverc i mean the F-keys (F1 - F12)
– geegee
Apr 30 at 10:11
 |Â
show 7 more comments
up vote
5
down vote
favorite
up vote
5
down vote
favorite
Right now I'm upgrading a fairly clean install of 16.04 to 18.04 and it seems to be stuck.
I mean, after some time into the upgrade it went on screen lock and I typed my username and password and it seems to be stuck saying: 'unlocking...'
No idea if this is due to the update still running hogging system resourcing or something else is going on.
I can switch with CtrlAlt+Fkeys but that just gives me black screens and impossible to tell if the upgrade is still running/finished of something terrible happened...
Any idea's? (cant log in with ssh because I haven't installed ssh server on this laptop)
16.04 upgrade lock-screen 18.04
edited Apr 30 at 9:55
Eranda Peiris
661416
asked Apr 30 at 9:44
geegee
15615
Right now I'm upgrading a fairly clean install of 16.04 to 18.04 and it seems to be stuck.
I mean, after some time into the upgrade it went on screen lock and I typed my username and password and it seems to be stuck saying: 'unlocking...'
No idea if this is due to the update still running hogging system resourcing or something else is going on.
I can switch with CtrlAlt+Fkeys but that just gives me black screens and impossible to tell if the upgrade is still running/finished of something terrible happened...
Any idea's? (cant log in with ssh because I haven't installed ssh server on this laptop)
16.04 upgrade lock-screen 18.04
edited Apr 30 at 9:55
Eranda Peiris
661416
asked Apr 30 at 9:44
geegee
15615
edited Apr 30 at 9:55
Eranda Peiris
661416
edited Apr 30 at 9:55
Eranda Peiris
661416
edited Apr 30 at 9:55
Eranda Peiris
661416
661416
asked Apr 30 at 9:44
geegee
15615
asked Apr 30 at 9:44
geegee
15615
asked Apr 30 at 9:44
geegee
15615
15615
now also using alt ctrl + F keys is unresponsive.
– geegee
Apr 30 at 10:00
Have you tried switching to a terminal (ctrl+alt+f4 or your favorite fn key) and logging in there, looking at what's happening (top,iotopetc)
– guiverc
Apr 30 at 10:07
@guiverc as mentioned before, they give me a black screen instead of a login.
– geegee
Apr 30 at 10:08
sorry I didn't know what CTRL+ALT+F did or meant (actually tried the combination on my 18.04 and it did nothing) never realizing you meant Fn keys.
– guiverc
Apr 30 at 10:09
@guiverc i mean the F-keys (F1 - F12)
– geegee
Apr 30 at 10:11
 |Â
show 7 more comments
now also using alt ctrl + F keys is unresponsive.
– geegee
Apr 30 at 10:00
Have you tried switching to a terminal (ctrl+alt+f4 or your favorite fn key) and logging in there, looking at what's happening (top,iotopetc)
– guiverc
Apr 30 at 10:07
@guiverc as mentioned before, they give me a black screen instead of a login.
– geegee
Apr 30 at 10:08
sorry I didn't know what CTRL+ALT+F did or meant (actually tried the combination on my 18.04 and it did nothing) never realizing you meant Fn keys.
– guiverc
Apr 30 at 10:09
@guiverc i mean the F-keys (F1 - F12)
– geegee
Apr 30 at 10:11
now also using alt ctrl + F keys is unresponsive.
– geegee
Apr 30 at 10:00
now also using alt ctrl + F keys is unresponsive.
– geegee
Apr 30 at 10:00
Have you tried switching to a terminal (ctrl+alt+f4 or your favorite fn key) and logging in there, looking at what's happening (
top, iotop etc)– guiverc
Apr 30 at 10:07
Have you tried switching to a terminal (ctrl+alt+f4 or your favorite fn key) and logging in there, looking at what's happening (
top, iotop etc)– guiverc
Apr 30 at 10:07
@guiverc as mentioned before, they give me a black screen instead of a login.
– geegee
Apr 30 at 10:08
@guiverc as mentioned before, they give me a black screen instead of a login.
– geegee
Apr 30 at 10:08
sorry I didn't know what CTRL+ALT+F did or meant (actually tried the combination on my 18.04 and it did nothing) never realizing you meant Fn keys.
– guiverc
Apr 30 at 10:09
sorry I didn't know what CTRL+ALT+F did or meant (actually tried the combination on my 18.04 and it did nothing) never realizing you meant Fn keys.
– guiverc
Apr 30 at 10:09
@guiverc i mean the F-keys (F1 - F12)
– geegee
Apr 30 at 10:11
@guiverc i mean the F-keys (F1 - F12)
– geegee
Apr 30 at 10:11
 |Â
show 7 more comments
3 Answers
3
active
oldest
votes
up vote
3
down vote
I am also still having this issue, but I found a workaround - Ctrl+Alt+F1 brings me to the normal login screen where I can enter my password and unlock the desktop. This method keeps the original session, so your browser, terminal and other apps are where you left them.
answered May 31 at 11:21
mtutty
1313
I installed 18.04 on my laptop on the 4th (2 days ago) and this started happening to me yesterday. I'd already discovered that I can do the same thing (i.e.: pop over to the "switch user" screen) however, that is a bad solution since it doesn't really fix the problem. It does work though! So, yeah, thanks for contributing a workaround. I'm going keep looking for a fix and publish it here as soon as I find it.
– Karl Wilbur
Jul 6 at 14:29
add a comment |Â
up vote
3
down vote
I stumbled into the same issue:
Upgrade from 16.04 to 18.04 (on Kubuntu). Screen automatically locked because I didn't use the PC. Entered password, screen is stuck. Switching to the text console - all screens dark. Switching back, mouse courser appears and is responsive, but everything else black.
I then realized:
switching to text console with Ctrl+Alt+F1, the text console was not empty but just very dark. So I increased screen brightness on the laptop with the function keys.
using
topI saw that the upgrade probably still running (heavy load on dpkg).With
sudo loginctl unlock-sessionsI could unlock the screen savers. I learned this from this answer (full quote for convenience, I used the ):
sudo loginctl unlock-sessionsif your system is usingsystemd. Note that the above will unlock ALL sessions no matter which user is running the screen saver.
If you only want to unlock your own session, just run
loginctl unlock-session(no root required because it's your own session).
After that, I changed with Ctrl+Alt+F7 back to KDE and found myself back to the still running session and upgrade process.
answered Aug 14 at 9:37
Joma
1313
I'd give you a thousand upvotes if I could. I absentmindedly locked my screen during my upgrade as I needed to walk away from the computer (at work). Was able to ssh to the machine from another and issue the unlock-sessions command. Thanks!!!
– Dashdrum
Aug 16 at 13:25
add a comment |Â
up vote
2
down vote
As mentioned in the comments, this problem can happen if your lockscreen is on a timeout.
So before upgrading make sure you unset a timeout for lockscreen.
To fix a stuck upgrade:
Powerdown the pc/laptop and reboot.
Most likely you will find yourself in a partially upgraded system.
You can fix it with:
sudo dpkg --configure --pending
sudo dpkg --configure -a
sudo apt -f install
sudo apt update
sudo apt upgrade
edited Jul 6 at 17:52
Karl Wilbur
6641614
answered May 1 at 13:35
geegee
15615
1
I think the last two commands should besudo apt-get updateandsudo apt-get upgradeRegardless, this had no effect for me.
– mtutty
May 31 at 11:17
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
I am also still having this issue, but I found a workaround - Ctrl+Alt+F1 brings me to the normal login screen where I can enter my password and unlock the desktop. This method keeps the original session, so your browser, terminal and other apps are where you left them.
answered May 31 at 11:21
mtutty
1313
I installed 18.04 on my laptop on the 4th (2 days ago) and this started happening to me yesterday. I'd already discovered that I can do the same thing (i.e.: pop over to the "switch user" screen) however, that is a bad solution since it doesn't really fix the problem. It does work though! So, yeah, thanks for contributing a workaround. I'm going keep looking for a fix and publish it here as soon as I find it.
– Karl Wilbur
Jul 6 at 14:29
add a comment |Â
up vote
3
down vote
I am also still having this issue, but I found a workaround - Ctrl+Alt+F1 brings me to the normal login screen where I can enter my password and unlock the desktop. This method keeps the original session, so your browser, terminal and other apps are where you left them.
answered May 31 at 11:21
mtutty
1313
I installed 18.04 on my laptop on the 4th (2 days ago) and this started happening to me yesterday. I'd already discovered that I can do the same thing (i.e.: pop over to the "switch user" screen) however, that is a bad solution since it doesn't really fix the problem. It does work though! So, yeah, thanks for contributing a workaround. I'm going keep looking for a fix and publish it here as soon as I find it.
– Karl Wilbur
Jul 6 at 14:29
add a comment |Â
up vote
3
down vote
up vote
3
down vote
I am also still having this issue, but I found a workaround - Ctrl+Alt+F1 brings me to the normal login screen where I can enter my password and unlock the desktop. This method keeps the original session, so your browser, terminal and other apps are where you left them.
answered May 31 at 11:21
mtutty
1313
I am also still having this issue, but I found a workaround - Ctrl+Alt+F1 brings me to the normal login screen where I can enter my password and unlock the desktop. This method keeps the original session, so your browser, terminal and other apps are where you left them.
answered May 31 at 11:21
mtutty
1313
answered May 31 at 11:21
mtutty
1313
answered May 31 at 11:21
mtutty
1313
answered May 31 at 11:21
mtutty
1313
1313
I installed 18.04 on my laptop on the 4th (2 days ago) and this started happening to me yesterday. I'd already discovered that I can do the same thing (i.e.: pop over to the "switch user" screen) however, that is a bad solution since it doesn't really fix the problem. It does work though! So, yeah, thanks for contributing a workaround. I'm going keep looking for a fix and publish it here as soon as I find it.
– Karl Wilbur
Jul 6 at 14:29
add a comment |Â
I installed 18.04 on my laptop on the 4th (2 days ago) and this started happening to me yesterday. I'd already discovered that I can do the same thing (i.e.: pop over to the "switch user" screen) however, that is a bad solution since it doesn't really fix the problem. It does work though! So, yeah, thanks for contributing a workaround. I'm going keep looking for a fix and publish it here as soon as I find it.
– Karl Wilbur
Jul 6 at 14:29
I installed 18.04 on my laptop on the 4th (2 days ago) and this started happening to me yesterday. I'd already discovered that I can do the same thing (i.e.: pop over to the "switch user" screen) however, that is a bad solution since it doesn't really fix the problem. It does work though! So, yeah, thanks for contributing a workaround. I'm going keep looking for a fix and publish it here as soon as I find it.
– Karl Wilbur
Jul 6 at 14:29
I installed 18.04 on my laptop on the 4th (2 days ago) and this started happening to me yesterday. I'd already discovered that I can do the same thing (i.e.: pop over to the "switch user" screen) however, that is a bad solution since it doesn't really fix the problem. It does work though! So, yeah, thanks for contributing a workaround. I'm going keep looking for a fix and publish it here as soon as I find it.
– Karl Wilbur
Jul 6 at 14:29
add a comment |Â
up vote
3
down vote
I stumbled into the same issue:
Upgrade from 16.04 to 18.04 (on Kubuntu). Screen automatically locked because I didn't use the PC. Entered password, screen is stuck. Switching to the text console - all screens dark. Switching back, mouse courser appears and is responsive, but everything else black.
I then realized:
switching to text console with Ctrl+Alt+F1, the text console was not empty but just very dark. So I increased screen brightness on the laptop with the function keys.
using
topI saw that the upgrade probably still running (heavy load on dpkg).With
sudo loginctl unlock-sessionsI could unlock the screen savers. I learned this from this answer (full quote for convenience, I used the ):
sudo loginctl unlock-sessionsif your system is usingsystemd. Note that the above will unlock ALL sessions no matter which user is running the screen saver.
If you only want to unlock your own session, just run
loginctl unlock-session(no root required because it's your own session).
After that, I changed with Ctrl+Alt+F7 back to KDE and found myself back to the still running session and upgrade process.
answered Aug 14 at 9:37
Joma
1313
I'd give you a thousand upvotes if I could. I absentmindedly locked my screen during my upgrade as I needed to walk away from the computer (at work). Was able to ssh to the machine from another and issue the unlock-sessions command. Thanks!!!
– Dashdrum
Aug 16 at 13:25
add a comment |Â
up vote
3
down vote
I stumbled into the same issue:
Upgrade from 16.04 to 18.04 (on Kubuntu). Screen automatically locked because I didn't use the PC. Entered password, screen is stuck. Switching to the text console - all screens dark. Switching back, mouse courser appears and is responsive, but everything else black.
I then realized:
switching to text console with Ctrl+Alt+F1, the text console was not empty but just very dark. So I increased screen brightness on the laptop with the function keys.
using
topI saw that the upgrade probably still running (heavy load on dpkg).With
sudo loginctl unlock-sessionsI could unlock the screen savers. I learned this from this answer (full quote for convenience, I used the ):
sudo loginctl unlock-sessionsif your system is usingsystemd. Note that the above will unlock ALL sessions no matter which user is running the screen saver.
If you only want to unlock your own session, just run
loginctl unlock-session(no root required because it's your own session).
After that, I changed with Ctrl+Alt+F7 back to KDE and found myself back to the still running session and upgrade process.
answered Aug 14 at 9:37
Joma
1313
I'd give you a thousand upvotes if I could. I absentmindedly locked my screen during my upgrade as I needed to walk away from the computer (at work). Was able to ssh to the machine from another and issue the unlock-sessions command. Thanks!!!
– Dashdrum
Aug 16 at 13:25
add a comment |Â
up vote
3
down vote
up vote
3
down vote
I stumbled into the same issue:
Upgrade from 16.04 to 18.04 (on Kubuntu). Screen automatically locked because I didn't use the PC. Entered password, screen is stuck. Switching to the text console - all screens dark. Switching back, mouse courser appears and is responsive, but everything else black.
I then realized:
switching to text console with Ctrl+Alt+F1, the text console was not empty but just very dark. So I increased screen brightness on the laptop with the function keys.
using
topI saw that the upgrade probably still running (heavy load on dpkg).With
sudo loginctl unlock-sessionsI could unlock the screen savers. I learned this from this answer (full quote for convenience, I used the ):
sudo loginctl unlock-sessionsif your system is usingsystemd. Note that the above will unlock ALL sessions no matter which user is running the screen saver.
If you only want to unlock your own session, just run
loginctl unlock-session(no root required because it's your own session).
After that, I changed with Ctrl+Alt+F7 back to KDE and found myself back to the still running session and upgrade process.
answered Aug 14 at 9:37
Joma
1313
I stumbled into the same issue:
Upgrade from 16.04 to 18.04 (on Kubuntu). Screen automatically locked because I didn't use the PC. Entered password, screen is stuck. Switching to the text console - all screens dark. Switching back, mouse courser appears and is responsive, but everything else black.
I then realized:
switching to text console with Ctrl+Alt+F1, the text console was not empty but just very dark. So I increased screen brightness on the laptop with the function keys.
using
topI saw that the upgrade probably still running (heavy load on dpkg).With
sudo loginctl unlock-sessionsI could unlock the screen savers. I learned this from this answer (full quote for convenience, I used the ):
sudo loginctl unlock-sessionsif your system is usingsystemd. Note that the above will unlock ALL sessions no matter which user is running the screen saver.
If you only want to unlock your own session, just run
loginctl unlock-session(no root required because it's your own session).
After that, I changed with Ctrl+Alt+F7 back to KDE and found myself back to the still running session and upgrade process.
answered Aug 14 at 9:37
Joma
1313
answered Aug 14 at 9:37
Joma
1313
answered Aug 14 at 9:37
Joma
1313
answered Aug 14 at 9:37
Joma
1313
1313
I'd give you a thousand upvotes if I could. I absentmindedly locked my screen during my upgrade as I needed to walk away from the computer (at work). Was able to ssh to the machine from another and issue the unlock-sessions command. Thanks!!!
– Dashdrum
Aug 16 at 13:25
add a comment |Â
I'd give you a thousand upvotes if I could. I absentmindedly locked my screen during my upgrade as I needed to walk away from the computer (at work). Was able to ssh to the machine from another and issue the unlock-sessions command. Thanks!!!
– Dashdrum
Aug 16 at 13:25
I'd give you a thousand upvotes if I could. I absentmindedly locked my screen during my upgrade as I needed to walk away from the computer (at work). Was able to ssh to the machine from another and issue the unlock-sessions command. Thanks!!!
– Dashdrum
Aug 16 at 13:25
I'd give you a thousand upvotes if I could. I absentmindedly locked my screen during my upgrade as I needed to walk away from the computer (at work). Was able to ssh to the machine from another and issue the unlock-sessions command. Thanks!!!
– Dashdrum
Aug 16 at 13:25
add a comment |Â
up vote
2
down vote
As mentioned in the comments, this problem can happen if your lockscreen is on a timeout.
So before upgrading make sure you unset a timeout for lockscreen.
To fix a stuck upgrade:
Powerdown the pc/laptop and reboot.
Most likely you will find yourself in a partially upgraded system.
You can fix it with:
sudo dpkg --configure --pending
sudo dpkg --configure -a
sudo apt -f install
sudo apt update
sudo apt upgrade
edited Jul 6 at 17:52
Karl Wilbur
6641614
answered May 1 at 13:35
geegee
15615
1
I think the last two commands should besudo apt-get updateandsudo apt-get upgradeRegardless, this had no effect for me.
– mtutty
May 31 at 11:17
add a comment |Â
up vote
2
down vote
As mentioned in the comments, this problem can happen if your lockscreen is on a timeout.
So before upgrading make sure you unset a timeout for lockscreen.
To fix a stuck upgrade:
Powerdown the pc/laptop and reboot.
Most likely you will find yourself in a partially upgraded system.
You can fix it with:
sudo dpkg --configure --pending
sudo dpkg --configure -a
sudo apt -f install
sudo apt update
sudo apt upgrade
edited Jul 6 at 17:52
Karl Wilbur
6641614
answered May 1 at 13:35
geegee
15615
1
I think the last two commands should besudo apt-get updateandsudo apt-get upgradeRegardless, this had no effect for me.
– mtutty
May 31 at 11:17
add a comment |Â
up vote
2
down vote
up vote
2
down vote
As mentioned in the comments, this problem can happen if your lockscreen is on a timeout.
So before upgrading make sure you unset a timeout for lockscreen.
To fix a stuck upgrade:
Powerdown the pc/laptop and reboot.
Most likely you will find yourself in a partially upgraded system.
You can fix it with:
sudo dpkg --configure --pending
sudo dpkg --configure -a
sudo apt -f install
sudo apt update
sudo apt upgrade
edited Jul 6 at 17:52
Karl Wilbur
6641614
answered May 1 at 13:35
geegee
15615
As mentioned in the comments, this problem can happen if your lockscreen is on a timeout.
So before upgrading make sure you unset a timeout for lockscreen.
To fix a stuck upgrade:
Powerdown the pc/laptop and reboot.
Most likely you will find yourself in a partially upgraded system.
You can fix it with:
sudo dpkg --configure --pending
sudo dpkg --configure -a
sudo apt -f install
sudo apt update
sudo apt upgrade
edited Jul 6 at 17:52
Karl Wilbur
6641614
answered May 1 at 13:35
geegee
15615
edited Jul 6 at 17:52
Karl Wilbur
6641614
edited Jul 6 at 17:52
Karl Wilbur
6641614
edited Jul 6 at 17:52
Karl Wilbur
6641614
6641614
answered May 1 at 13:35
geegee
15615
answered May 1 at 13:35
geegee
15615
answered May 1 at 13:35
geegee
15615
15615
1
I think the last two commands should besudo apt-get updateandsudo apt-get upgradeRegardless, this had no effect for me.
– mtutty
May 31 at 11:17
add a comment |Â
1
I think the last two commands should besudo apt-get updateandsudo apt-get upgradeRegardless, this had no effect for me.
– mtutty
May 31 at 11:17
1
1
I think the last two commands should be
sudo apt-get update and sudo apt-get upgrade Regardless, this had no effect for me.– mtutty
May 31 at 11:17
I think the last two commands should be
sudo apt-get update and sudo apt-get upgrade Regardless, this had no effect for me.– mtutty
May 31 at 11:17
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1030044%2fupgrade-from-16-04-to-18-04-lock-screen-is-stuck%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
now also using alt ctrl + F keys is unresponsive.
– geegee
Apr 30 at 10:00
Have you tried switching to a terminal (ctrl+alt+f4 or your favorite fn key) and logging in there, looking at what's happening (
top,iotopetc)– guiverc
Apr 30 at 10:07
@guiverc as mentioned before, they give me a black screen instead of a login.
– geegee
Apr 30 at 10:08
sorry I didn't know what CTRL+ALT+F did or meant (actually tried the combination on my 18.04 and it did nothing) never realizing you meant Fn keys.
– guiverc
Apr 30 at 10:09
@guiverc i mean the F-keys (F1 - F12)
– geegee
Apr 30 at 10:11