Joined
·
23 Posts
Screw it I'm pushing the power button.
How to turn off linux stuck on command line?
Qubes:
1 - 16 of 16 Posts
Joined
·
1,722 Posts
Code:
shutdown now
Joined
·
23 Posts
The problem was I could not enter any command.
That or the text could of been transparent.
Hell, I'm might of been entering the command on the wrong screen.
Joined
·
331 Posts
Other than losing data, why wouldn't you push the power button?
I mean, you're obviously a smart guy on a tech forum, seems like common sense?
Legitimately confused.
I mean, you're obviously a smart guy on a tech forum, seems like common sense?
Legitimately confused.
Joined
·
23 Posts
My mistake, I thought that command prompts in Linux were command lines.
So to get access to the command line next time I just press ctrl+alt+T?
Ctrl+Alt with function keys F3 to F6 to access TTY. You can have 4 different sessions opened which you can switch between with F3-F6.
Ctrl+Alt with function key F1/F2 will bring you back to the GUI this case boot screen.
Joined
·
23 Posts
The problem was pressing Ctrl + Alt + F3 to F6 did not allow me to enter any commands.
When you pressed Ctrl + Alt + F3 to F6 did it take you to TTY where it would ask you for your username and password?
Joined
·
23 Posts
No just a textless screen with a blinking cursor.
Now I understand, the blinking cursor is the "GUI" when you press Ctrl + Alt + F3 to F6 it takes you to the boot screen and shows that your OS can't boot properly.
What was the last thing you did before this occurred?
Joined
·
23 Posts
Sadly, now the Qubes won't even boot to the initial install screen. However, this is likely just the result of a corrupted USB stick.
Joined
·
23 Posts
@Scharfschutzen
The reason is that a graceful shutdown did not work.
I also feel that a hard shutdown might result in damaged hardware.
Essentially, I would rather shutdown the computer safely when given a chance.
The reason is that a graceful shutdown did not work.
I also feel that a hard shutdown might result in damaged hardware.
Essentially, I would rather shutdown the computer safely when given a chance.
Joined
·
23 Posts
I was installing Qubes and Qubes was installing the VM for Fedora.
Granted, the simple error above has been solved.
It was resulting from my bad habit of using words that are protected as usernames.
In this case it contained the word user.
Error codes (for others):
g_str_has_prefix: assertion 'prefix !=null'
The property '/general/double_click_distance' of type int is not supported.
Another compositing manager is running on screen 0.
Failed to connect to session manager.
Problem and fix:
The g_str_has_prefix function expects a string but receives a null object since it cannot set the user or password to a reserved word.
Change the password or username to a non-reserved word.
Notes:
I realise failed to connect to session manager is a generic error message.
Granted, the simple error above has been solved.
It was resulting from my bad habit of using words that are protected as usernames.
In this case it contained the word user.
Error codes (for others):
g_str_has_prefix: assertion 'prefix !=null'
The property '/general/double_click_distance' of type int is not supported.
Another compositing manager is running on screen 0.
Failed to connect to session manager.
Problem and fix:
The g_str_has_prefix function expects a string but receives a null object since it cannot set the user or password to a reserved word.
Change the password or username to a non-reserved word.
Notes:
I realise failed to connect to session manager is a generic error message.
1 - 16 of 16 Posts
