Hi. I'm trying to create an application to make a login screen launch at boot. This application will *(hopefully)* force users to login using an username and a password before they are able to use the home, back, menu and search buttons. So far, I have done *MOST* of the coding and as far as I can see, the login app works.
when I reboot my Linux machine Linux version 5.5 red hat
I get the following warning on the console screen ,
Linux cant startup and I can't login
please advice , how to login as single user mode and how to bypass the following problem ?
umounting old /dev
umounting old /proc
umounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: attempted to kill init
New install of 12.04.1 and the user established during install cannot login.
I was able to create an new user by entering the system as guest. Ubuntu accepted the sudo password of the first user to establish the new user; but I cannot login as the user established during install. The newly created user does have admin permission and I can login using that user and do sudo stuff.
On my app I see having multiple activities...
Main
|
--------------------
Login |
| |
--------------- Dashboard
|
-----------------------------------------
| | |
Activity1 Activity2 Activity3
If a user is logged in, it will by
I've upgraded a machine from 12.04 to 12.10 and now can't log in to my user account.
When I type in the password, the screen goes black and I get dumped back at the login screen.
T-Mobile instituted a hotspot plan in 2010, but many users were never charged because of technical limitations with the software. Recently T-Mo has been blocking users, after receiving Ice Cream Sandwich upgrades, and redirecting them to a sales page telling them that they can purchase the feature for an additional $14.95 per month.
I get into this endless login-cycle if I attempt logging with my main user - I tried Gnome Classic and regular Gnome, but after I login it sends me back to the login.
The only way I can login is through another user.
This means that there's some hidden setting file in the home directory that messes things up.
How can I debug this further?
Hi I have an App which has a strict requirement of staying "logged in" even when the app is destroyed.
This is certainly not game-changing or life-altering, but a question about Ubuntu has been nagging at me.
Why is it that when a user locks the screen (or the screen is locked due to inactivity), the machine doesn't simply go straight to the login screen. The little dialogue that is shown has nothing to offer that the login screen doesn't have.
Email this page