I remember that in previous Ubuntu releases, it was possible to restart/shutdown at the logon screen via the keyboard. I think it was via the F10 key. Can this function be brought back?
View 1 RepliesI am using Xubuntu 10.10 64bit . When I press the quit or logoff buttons on the desktop it takes me to the logon screen and then at the bottom right corner it allows me to shutdown or reboot. I would like to bypass this screen entirely,and just shutdown reboot from the desktop. Only I use this machine at home ,no none else needs to log on. Is there any way to do this?
View 3 Replies View RelatedA while ago, I was applying the new kernel updates (I guess 2.6.32-24, or the one after it.. well, the latest generic update) and accidentally powered off my laptop. And now it wont come up. It comes to the logon page, and neither the keyboard, nor the mouse work. Cant even switch to the TTYs. When I boot with the recovery mode, I just see a black screen (probably the TTYs dont work) but after "processing" some time, nothing happens. Not sure if the keyboard works, as I cannot turn on/off the capslock switch, but ctrl+alt+del works
View 3 Replies View RelatedI have Laptop sony VPCEA22EN. I have installed ubuntu 10.04. it was working fine. Then i installed kubuntu-desktop. it was working fine. i tried to some of bugs using kubuntu update manager. i restarted the laptop.
after that im not able to logon on kubuntu. on kubuntu logon screen i'm unable to enter username n password. Keyboard and mouse is not detected but, usb mouse works.
i tried ctrl+alt+esc, this combination doesnt work while booting. i can't use this combination on log-on screen because keyboard is not detected.
I have updated my 11.3x64 recently and after updateI cannot log into any X session.Keyboard is dead but mouse is moving fine.I tried to change kdm to gdm - no result!All I can do now is - select by mouse "Console Session"and log in to common terminal. In terminal session keyboard works.I can't understand What is it?The most interesting:If I run terminal as a root and run startx - kde desktop is started but the same way - without keyboard!Hardware manager (YAST) shows: /dev/input/event0and shows type of keyboard right: AT Keyboard bla-bla-bla. (Common Genius PS/2 keyboard for 6$ :-))I suspect something wrong with my X11 but can't get what!I did not find xorg.conf in it's standard place. I have found only /etc/X11/xorg.conf.install
View 1 Replies View Relatedi want to remove shutdown/restart/hibernate buttons from my gdm login screen on ubuntu 10.10. if i disable these buttons with ubuntu tweak or gdm2setup it is just ignored and all buttons are still there.
View 9 Replies View RelatedI have been using ubuntu 10.04 64 bits for about 3 month. Today I change my keyboard layout, so I want to test if everything is ok so I reboot my computer. When I try to reboot everything is as usual but the problem is that after grub. Nothing only a black screen no matter what i do. I doubt the keyboard layout change something but who knows. I run AMD phenom 940 X 4, 4 gig ram, Ati radeon HD 4870.
View 3 Replies View Relatedeverytime I try to shutdown/reboot, it gets to the screen where it has the green/bold status messages on the side, but then it simply stops. The cursor doesn't blink, nothing happens...you could wait 10 minutes, and it would still be at that same screen. I don't know if I've described this well enough for anyone to understand, but I hope so! I don't have a camera, but if I did...I'd post a picture of where I mean...
But like I said, after getting to a certain, without actually shutting down, it simply stops and does absolutely nothing. This is rather inconvenient, and I'd like to find a solution to this if possible. EDIT: I'm sorry I didn't provide any hardware info, but I'm using Gnome...This didn't happen 100% of the time KDE like it does now though. (But it DID happen in KDE as well) I'm using OpenSUSE 11.2... I'll be back in a moment with hardware info, assuming it may aid in a solution.
[Code]...
Further to this LQ thread which Tinkster solved by suggesting the last command (thanks Tinkster) I have been exploring last -x reboot and have found that the reported duration is incorrect for the last reboot and shutdown when a old wtmp file is used. Not having a record for the following shutdown, last assumes that the system has been up until the current time and similarly for the shutdown.
The output comes in time order, latest first, each line showing the time of the reboot and the uptime from then to shutdown. Using last -x reboot shutdown to show the shutdown time, here's an illustration
Code:
shutdown system down 2.6.29.6-smp Sun Mar 7 15:35 - 03:02 (11:27)
reboot system boot 2.6.29.6-smp Sun Mar 7 09:35 (05:59)
09:35 until 15:35 is 05:59.
When the uptime exceeds 24 hours it is shown as (<days>+<hours:minutes) like this
Code:
shutdown system down 2.6.29.6-smp Sun Feb 21 12:39 - 13:20 (00:40)
reboot system boot 2.6.29.6-smp Sat Feb 20 09:39 (1+02:59)
09:39 until 12:39 the next day is 1 day 02:59.
The time in parentheses at the end of the shutdown lines is normally the time until the next shutdown.
So far so good. The incorrect output is for the last reboot and shutdown of an old wtmp file. Here's the output of last /var/log/wtmp -x reboot shutdown; last -f /var/log/wtmp.1 -x reboot shutdown
Code:
[snip]
reboot system boot 2.6.29.6-smp Fri Mar 12 07:42 (01:54)
shutdown system down 2.6.29.6-smp Fri Mar 12 01:31 - 09:37 (08:05)
wtmp begins Thu Mar 11 08:25:26 2010
[snip]
reboot system boot 2.6.29.6-smp Wed Mar 10 14:12 (15+01:42)
shutdown system down 2.6.29.6-smp Wed Mar 10 12:41 - 15:54 (15+03:13)
[snip]
The boot started at "Wed Mar 10 14:12" which had an actual uptime of 1 day 11:20 is reported as 15 days 03:13 which is the time from then until the last -f /var/log/wtmp.1 -x reboot shutdown command was issued. The time from shutdown to shutdown is similarly affected.
When I log onto my 10.04 server via ssh, there is the /etc/motd displayed. This motd is made up each time by the files in /etc/update/motd.d/. There is this one file : update-motd-reboot-required The content is exec /usr/lib/update-notifier/update-mot-reboot-required and the content of this one is : if the file /var/run/reboot-required exists, print it.
But who is making this file and why ?we know who it is: it's pam_motd.. but why would I reboot ??!?
editt2 : nvmd [URL]
All of a sudden, My keyboards stopped working. It works for the login to enter password, but afterwards not.
Reboot and logout/login does not work.
A beep comes after pressing a key afterwards. I was only able to post this via links browser.
I'm trying to reboot the server (shutdown -r now).But it seems like nothing happened.
When I try "shutdown -c", the system prompts "shutdown: cannot find pid of running shutdown."
how to add text, or a picture to the initial logon screen in Ubuntu 10.04 alpha 2?
View 9 Replies View Relatedafter an update i cannot my pc remains in the log on screen. I insert my password then the screen goesn and of and after 4 secondit goes back in the logon screen. I run the following
sudo dpkg-reconfigure gnome-applets
sudo dpkg-reconfigure gnome-session
and i receive a message that both gnome and applets are not installed.
I have recently upgraded to the 10.04 Alpha and have been unable to reboot or shutdown. I know it's just an alpha and therefore problems are bound to exist, so I tried reinstalling from a live cd of Alpha 3. But I am still unable to reboot or shutdown.To clarify what happens, I click on shutdown or reboot, the pop-up appears, I click on the shutdown/reboot button and it seems to complete it. It says that processes have been killed and something has exited with 255. But my computer is still on. I am guessing that Ubuntu is shutting down, it's just not actually shutting my computer down or restarting it.
View 5 Replies View RelatedI have a remote server (Xubuntu 10.04) which suffered an electricity brownout yesterday. The server itself is backed with an ups, but it is connected to a external firewire disk, which is not, and this disk malfunctioned as a result of the brownout.
The problem: Now, any process trying to access the external disk freezes and ends up in eternal D state in the process list, including ls and umount. Even trying to ls a directory which contains a symbolic link to a file in that drive just causes ls to freeze. These processes cannot be killed even with SIGKILL, so I proceeded to reboot but...
None of the reboot commands work. Instead they just get added to the ever increasing list of D state processes. I tried (sudo) shutdown -r now, reboot -f now and finally plain shutdown -h now. Is there anything else to try other than ask somebody to actually go to the server and pull the plug (which is not at all trivial)? Some way to tell kernel not to worry about messing stuff up, and just reboot?
we've just bought 30 newest nettops ACER Aspire R3700 with ION 2. I've tried ubuntu, kubuntu, xubuntu. Everything works as expected, but... the first one freezes when trying to reboot, shutdown or enter sleep mode. Checked on several hardware units. The desktop just freezes and nothing happens (ubuntu 10.10, both x32 and amd64). Also no one installs the wi-fi drivers, only ethernet
View 4 Replies View RelatedNatty won't shutdown for me - the start up/shutting down graphic comes up and the 'light' go down from 5 to 3 then it just hangs there.
Is there a shutdown log? I've looked in /var/log/messages but there's nothing relevant there.
From a 11.04 Ubuntu, I installed the meta-package xfce4 (*). Now, in the xfce4 session, "suspend" and "logout" (from the xfce4-panel button) works, but "shutdowmn" and "reboot" not, they only lead to GDM. (the shutdowm option there works.)
I tried to solve that by installing the meta-package "xubuntu-desktop" (maybe there are some necessary settings included?), and in fact, the login-screen changed (it's still GDM, I suppose) and there is now a "xubuntu" session, but in that, the probem is just the same: shutdown only leads to the login screen.
In Gnome Classic or Unity, shutdowmn works as it shoulds, so it's not a general problem with my computer.
In Detail, in forst tried to install xfce4 with ubuntu-software-center, but although it seemed to succeed, there was no xfce session. In Synaptic, installing the xfce3 metapackage worked. In fact, software-center seemed to have overlooked some dependencies...
What I want to do is have a screensaver that will activate at the login screen, after a few mins lack of use.
This can obviously be set for individual accounts, but I cannot figure how this can be done for the login screen.
Installed ubuntu mobile 3 times, once off of a USB, second off of a burned ubuntu netbook cd, third off of a ubuntu 10.10 official cd. all three had the issue. as soon as i log on to ubuntu, all i see is my cursor and the background and nothing else.. tried searching and tried a few suggested things, but to no benefit.. What's next?
View 2 Replies View RelatedI recently migrated from Hardy 8.04 LTS (32) to Karmic 9.10 (32) so that the restricted ATI drivers and CCC would work correctly - that part is basically fine.
The problem for the past couple of weeks has been Karmic randomly shutting down, and rebooting the system after 1 or 2 hours up-time.
Why would this be happening, it was fine for the first few weeks after installing Karmic.
My system currently consists of the following;
Gigabyte MA790FX-DS5 mainboard - Jan '08
AMD 3.0Ghz Phenom II X4 945 CPU - Oct '09
4GB DDR2 Kingston HyperX RAM (1066 MHz) - Jul '09
Sapphire ATI HD5770 1GB GDDR5 video - Dec '09
Cooler Master Extreme Power Plus 640 watt power supply - Nov '09
Cooler Master Centurion 5 CAC-T05 case - Jan '08
1 pata 500 GB, 3 sata 500 GB & 1 sata 640 GB drives
2 DVD burners (Pioneer and LG)
2 x 19" (4:3) Samsung SyncMaster 943N LCD monitors
I used to have lmsensors working with the Athlon 2.8GHz dual core in Hardy, but they wouldn't work with the new Phenom 3.0 GHz 945 CPU in Hardy (and they still won't work in Karmic).
Th upshot is that I don't have cpu, system, or graphics temps; nor do I have any fan speeds, so I don't know what temps or fan speeds my system is running without rebooting into BIOS (which isn't much good as I really need to know what's happening when I'm using the OS itself).
Does anyone know what could be causing this random shut-down/reboot problem?
i was working on ubuntu when the machine suddenly shutdown. when i restarted it, i keep getting a sh:grub console instead of the logon screen. dunno what to do.
View 3 Replies View Related1. I can run the graphical installer at full resolution without using "nomodeset"
2. I can boot into the Gnome desktop using the option "Try without installing" without any problems
3. When I install to my HDD however, I can boot but just at the point where the logon screen should come(after the black screen,blinking cursor), the display reports no signal and goes to sleep. I can hit enter, type my password, hit enter again (blind, as there's no display) and the HDD spins up as if logging in, but I don't see anything.
4. Using "nomodeset" makes no difference whatsoever other than the graphical installer runs at a lower res.
5. using the alternate installer changes nothing
6. recovery mode has the same issues
It appears to me that booting into Gnome without installing uses some sort of generic driver, whereas installing uses a different driver which is sending my display to sleep. I'm using Ubuntu 10.10 64Bit. Have also tried using 10.04 64Bit and the alternate 10.10 .iso, but to no avail. My graphics card is an NVidia Quadro NVS 295 with a DisplayPort-DVI adapter. I've previously installed 10.04 64Bit on another system with an NVidia GT240 card with no problems whatsoever. I can't try that card in this machine as it's too big for the case chassis, let alone the case.
I have found a number of pages describing everything from how to match the splash screen to my desktop background to installing a feature length movie as a splash screen (something like that). These are NOT what I want to do. I simply want to disappear the ugly pink screen and be presented the logon dialog over a blank background.
I suppose I could change the run level, logon at a terminal and startx (if that works in 10.04 - I would not place any bets).
Our system is based on RH4 and is using pam_tally and faillog to record failed attempts and to lock users out after 5 attempts. We have a requirement to provide a normal (non-root) user logging onto our system, with information regarding the number of failed logon attempts made on their account before the current successful logon (similar to the functionality provided by HP Protect Tools on Windows). My first idea was to add 'faillog -u $USER' to the bashrc, however by the time the bashrc is run - the user has been successfully authenticated and the faillog has been reset back to zero.
View 5 Replies View Relatedi searched the forum about this subject, i found many post but nothing useful. i also wonder why a normal user is not prompted to authenticate as root to perform these tasks. i thought the file /etc/sudoers but i don't think this is the point. i tried the group "shutdown" but does not exist. i read that this is expected in ubuntu server so it should exist even in the desktop version, i guess.
View 3 Replies View Relatedubuntu with windows xp on my laptop. My problem is everytime I out of ubuntu, the vga driver seems to disappear. I can't start x server, and when go into windows xp, the screen is on very low resolution state. After go into win xp and reboot, I can boot either ubuntu or winxp normally, everything is okey again. In summary:- When go into XP and reboot, I can boot ubuntu and XP normally.- When go into ubuntu and reboot, I can only boot with very low resolution in XP and can not start x server if boot ubuntu
View 3 Replies View RelatedI recently updated my 10.04 (se remix,I guess it's only preinstalled language support and some other thinks like link to ubuntu se homepage; http://ubuntu.se/content.php/322-Ubu...it-uppdatering!) to 10.10.
I now I'm stuck with a quite annoying (but not sever) error. When I shut down the computer doesn't turn of it just restart?!
I know I had some similar issue with my old EEEPC but that was a GRUB 1 error and now I'm running the latest GRUB so ...
I have an mysql innodb ~ 20gigs. Normally shutting down mysql (service mysql stop) takes a few seconds. When I reboot Ubuntu with the reboot or shutdown command it just reboots it super fast without mysql logging (/usr/sbin/mysqld: Shutdown complete) Also during this shutdown the following is failed: umount2: device or resource busy /data: device is busy.
mysql is setup to read from /data . Why is ubuntu not waiting for mysql to properly shutdown before unmounting the filesystem and rebooting?