Debian :: Login Window Pops Up On Reboot/shutdown?
Jul 5, 2011
Every time I reboot or shutdown my PC, the login window shortly pops up. The PC does shutdown or reboot normally afterwards. When I use the terminal to shutdown/reboot (sudo shutdown -h now or sudo reboot) all goes well. The PC is running Debian Squeeze with the GNOME desktop environment.
i 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.
I am facing the issue that the PC not capable to shutdown or reboot; In order to debug that, htop tells me the running processes but all seems normal, I killed few but still cold reset is needed.There is certainly a problem somewhere. the best would be to know which process are weirdly hanging. It could make this testing debian bit better to know which package has these issues.
i have fresh installed debian wheezy xfce4, and using slim to start it but i can't get reboot, shutdown and thunar can't open flash and others volumes. i using .xinitrc (exec ck-launch-session startxfce4)
I've added entries to my Openbox menu labeled Reboot and Shutdown. Problem is, reboot and shutdown h only work as root, and I never login as root. I've tried su-to-root -c reboot, but the menu entries remain unresponsive. I do not have sudo installed because I feel it is a security issue. However, I found that sudo reboot works with the menu entry, but only if my account is set to use sudo without a password in /etc/sudoers. I use tint2 as my panel, but have had no luck with finding a shutdown/reboot button.
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.
Code: Select allshutdown -h now reboot shutdown -r now halt init 0 init 6
And all hang on the same line. This is 100% reproducible. I am not actually running a virtual machine. I don't have qemu-kvm installed. I do have separate partitions on my system. I have a /boot, /, swap, and /home partition.
From looking at other posts: [URL] .....
Solutions tend to be across the board: not unmounting properly, acpi settings in grub, using a different shutdown command.
My fstab file is:
Code: Select all# /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda2 during installation
[Code] ....
and the result of Code: Select allmount is
Code: Select allsysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=498135,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,relatime,size=800408k,mode=755)
I set the file as executable. sudo chmod +x /etc/init.d/myshutdown.sh
I inserted a symlink in the rc0.d directory with the process order K04. sudo ln -s /etc/init.d/myshutdown.sh /etc/rc0.d/K04myshutdown.sh
I also inserted a symlink in the rc6.d directory with the process order K04. sudo ln -s /etc/init.d/myshutdown.sh /etc/rc6.d/K04myshutdown.sh
Apparently rc0.d is for shutdown and rc6.d if for reboot
After reboot it appears that rtorrent does not run (I cannot connect to rtorrent via rutorrent) but really what is going on. I am trying to do this because rtorrent does a hash check on all files if it is not shutdown properly. I just want it to shutdown automatically and safely, before the system shuts down.
Come across with a situation where all methods of shutdown result in a restart/reboot? I've tried commands:
- shutdown - halt - poweroff
.. with various parameters, nothing works. The laptop seems to power off, but after a sec it restarts/reboots. I've Googled high and low, but there's very little on this topic. Maybe it is specific to the current kernel in Wheezy? I'm not suspecting a harware failure, since this was not happening with Windows installed.
This happens on me with Wheezy on a HP Elitebook 8530w.
I have two external monitors connected to my laptop, one with DVI port and one with displayport port.
Now when I run something a new window always pops up in the monitor on the left. I guess it is set so a net window always pops up at 0, 0 pixel or something. I want it to pop up in the monitor on the right.
I've recently installed Kubuntu 10.10 on my Acer Aspire One ZG5 netbook. Everything works pretty well and I'm enjoying it so far. One problem - I have a Lexmark S405 inkjet printer - for which I installed drivers the other day. The install goes fine and the printer does work - but upon next boot, there is an error loading Kate - and then some sort of script editor pops up. Uninstalling the driver package seems to fix the error message but it's back upon re-install. Didn't have this with my Ubuntu VM on my desktop. The printer does still work.
I recently installed the newest version of Songbird, it worked for two days. Now when I click Songbird, it tells me it's starting down in the Window List, but it never pops up. I've tried all three methods from here to install it afterwards... none of them I got to work. Anyone have a clue what could possibly going on? This is on Ubuntu 9.10(32bit)
I'm having problem getting my Edimax EW-7711UTn to work (I'm stuck with using the ethernet cable for now). The light flashes on it and it picks up wireless networks, but when I'm connecting to them, I put in the key, it tries to connect, but the wireless key window pops up again and again and again. I've looked up other threads about this, but none of the suggested methods have worked for me (I've checked to see if it's compatible, apparently it isn't, but people seem to have got it working before...) I'm using a Toshiba Satellite M40 laptop. $lspci:
Just during the last three days, when running Update Manager, clicking Check, downloading all available updates, then Clicking Install Updates, the Downloading Files window pops up but it is blank. and it stays blank. The little rotating icon indicates something's going on but, NO. Nothing has happened, even after a couple of hours. Trying to close Downloading Files brings up a window to Force Quit. Then trying to close Update Manager has no effect. to shorten the story, finally a window pops up saying that the "AT SPI Registry" is not responding. I'm sure trying the same thing will not yield different results. I'm running 10.04.
I just updated my netbook remix 9.10 to 10.04 and every time I boot up it freezes as soon as the login screen pops up. Before this said screen pops up I have the ability to move the cursor around freely, and if I mash the life out of enter I can get it to select my username, but freezes before the password entry bar has the chance to come up under it.
I installed new version of Choqok 1.0 Beta3 (0.9.90). It works nice, but the notifications for new posts bothers me. With every timeline refresh, system tray notification window pops up informing me for new posts.
How to disable notifications for Choqok? I cannot find option in Choqok. However, I can disable application notifications in system tray options, but in this case some ugly little window pops on the top of the screen informing me for new posts.
After a lot of headache and time I was finally able to get Ubuntu 11.04 64bit installed along side my Windows 7 64bit installation. The whole process was hindered by the screen resolution being really off, looked like this LINK (aspect ratio of (16:10) I believe it was). After much fiddling i was able to get the installation started hoping that in the end it would let me set the res. correctly once it was installed. About 75% of the way done it threw an error saying there was either a problem with the HDD or the CD, I know my HDD is fine, so I booted up windows and set up my USB thumb drive as the installation device, Unbootable.
My next attempt i hooked the laptop to my internet via cable and started the installation again, this time i found that I could set the res of the LiveCD (which was a pain in the neck) and this time Ubuntu installed and upgraded and seemed all sorts of happy! Once the PC rebooted and i selected to boot into Ubuntu, the(what i suppose is) login screen pops up but the resolution is messed up again and this time I can't navigate at all. I've tried just typing in my password and hitting enter as i can see that it is by default selecting my user name to login with.
If I start my Lenny with Gnome I get the login window. The strange problem is, I have us keyboard there, but after login I have german keyboard. Under System -> Preferences -> Keyboard I have only german keyboard layout setuped. Howto change keyboard layout at the login window?
I just installed successfully Wheezy, but I can't change my Login Window Theme.I put the three files (.desktop .xml and.jpg) in/usr/share/gdm/autostart/LoginWindow/),I think that my mistake is here but I don't know where to put the .xml file and the .jpg files.And the I edited the file/etc/gdm3/greeter.gconf-defaults.The background is well-displayed but the "theme" is still the same.
I'm fairly new to Debian/GNOME, and I'm running Squeeze and GNOME 2 and I have some questions. How exactly do I change the background image for the login window? I've looked up various suggestions but none of them seem to work - the appearances window does not ever seem to change the background image for the login screen. Also, whenever I log out or when I close the lid on my laptop and it suspends, I am unable to log back in - all I see is a black screen and my cursor, which I can move.
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.
I 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
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...
Recently I installed Fedora 12 64bit in my HP Compaq 6720s. Among many other problems that I had and I solved with your help, I have the following problem:When I restart or shut-down Fedora 12 it crushes and hangs and only thing that I can do is to stop and restart my laptop by means of ON/OFF button.My question is:Is there any way to see this error (maybe some log file or something) so I can send this message or log file here in this forum and get some help?