I hoping someone can point me in a direction. I installed F13 KDE from the live cd and now when I Shutdown or Reboot, it takes 2 minutes and 8 seconds for the machine to power off. Yes, I timed it.Happens everytime like that. Even when booting from both "mainstream" live cd and the KDE spin live cd. When I hit the Shutdown or Reboot, it goes through the daemons/services shutdown the flashes up the Halting System or Please wait while the system reboots messages (respectivley), turns off the LCD and then just... sits with the power light on and hard drive activity light on. I should mention this is on a Toshiba Laptop about 2 years old now. Intel Chipsets. (Satellite Pro S300M-S2142 if anyone is really curious). The hard drive light stays on for about 1:03 minutes and then it turns off, at 2:08 minutes - the Power light finally turns off and the thing finally shuts down or reboots. If this sounds familiar, it's because it is and I've posted about it with F12 and it's still there with F13. Running kernel-2.6.33.3-85.fc13.x86_64
I installed F12 KDE from the live cd and now when I Shutdown or Reboot, it takes 2 minutes and 8 seconds for the machine to power off. Yes, I timed it. Happens everytime like that. Even when booting from both "mainstream" live cd and the KDE spin live cd. When I hit the Shutdown or Reboot, it goes through the daemons/services shutdown the flashes up the Halting System or Please wait while the system reboots messages (respectivley), turns off the LCD and then just... sits with the power light on and hard drive activity light on. I should mention this is on a Toshiba Laptop about a year old. Intel Chipsets. (Satellite Pro S300M-S2142 if anyone is really curious).
The hard drive light stays on for about 1:03 minutes and then it turns off, at 2:08 minutes - the Power light finally turns off and the thing finally shuts down. I've tried adding acpi=off, but that just gets me a kernel panic on startup and acpi=debug all I seem to notice is "Malformed early option 'acpi'" in messages and dmesg. How consistant the power off time is makes me think there's a timeout of sorts going on, but I have no idea on how to track that down.
I am using Fedora 15 KDE 32-bit. I am facing a problem while shutdown. It takes unusually long to shut down. It reaches the blue screen with the fedora logo within a few seconds, but it stays on the blue logo screen for 2-3 minutes before shutting down. However, I am facing no problems during startup.
About suspending F15 KDE. It goes into suspend successfully but after switching on after suspend, it just shows an unresponsive black screen.
Is anyone else facing the same problem and has it been solved before? Because I haven't come across many posts regarding F15 KDE.
I wanted to edit the Selinux policies using a GUI and i read that there's seedit. The problem was the selinux-policy-targeted package. It was conflicting every time i wanted seedit. I uninstalled the selinux-policy targeted and was able to install seedit. After that, I did ./seedit-init, after that i just entered reboot. Was there supposed to be a button or anything popping up after the seedit-init?
So it reboots, and during the first reboot, a bunch of words flashed, and i see some words like Green [OK]. It was very quick so i have no idea what it said. It then reboots again and it loads but now after the fedora loading bar and word turns grey, it just stops. Nothing else happens. I can type things in, but just that, nothing else. Ctrl+Alt+Delete restarts it though.
So my problem is, is it still relabeling? Because that's what I'm told seedit is doing; relabeling all the policies. If so, how long does it take?And if it's not relabeling, then did something happen a long the way?I started the seedit around 3ish and it's almost 8 already. I'm currently using Fedora 14 with a 500gb HDD. However, i partitioned 11gig for the fedora, and the rest is for Windows 7. So basically it is a dual-boot.okay, after much waiting, it was an error =/. I just don't know why though. I did a restart, made the kernal disable selinux and went and uninstalled seedit. I reapplid the selinux-policy-target. I did a restart and there it was, telling me it had to relabel.
After installation of Fedora 11, I click reboot, it ejects out the disk, but is stuck at the screen for a long time and doesn't reboot so I manually had to reboot it. Today, surfing on firefox, it got frozen, and the touchpad worked, but everything was frozen nothing moved so I had to manually shut the laptop down. On bootup everything was ok. Im worried about corrupted files.Should I just reinstall Fedora 11? m using a dell studio 1555 laptop
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.
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?
After a couple of days, some commands related to the disk (df) or files (ls) or killing process (kill -9) doesn't respond. Even I can't reboot or shutdown my server. After an hard reboot, some files are not here anymore or the log files are not filled anymore until I restart.My disk are behind the RAID controller i6 and are configure in RAID 1. The disks are two HP SCSI 72,8GB 10k RPM.Maybe I am totally wrong to check the disk access side, so I am open to other explanation.I can also add that my CPU is running under 1% et my RAM under 10%.
I don't follow why the Suspend option is there and the Reboot and Shutdown is not. Can anyone guide me to the code needed to add the selections. I know I can use a Terminal to shutdown or reboot but a simpler solution would be nice. I expect there are methods to fix most of what I don't like about Gnome 3 but I haven't found them yet. Is there a central place for the solutions needed to deminimalize Gnome 3? I really prefer one click control.
I need to know how to configure automate sending sms if server reboot and shutdown? Now i just set sms notification once my server it's UP by create scripts in /etc/rc.d/rc.local while booting then from server sending sms notification. SMS - using gnokii attached mobibe phone. Server - Fedora 10
Running Opensuse 11.4 (but had same problem on 11.3). During startup and shutdown, the text messages are displayed using a very large font (characters are > 1 cm high). How can I specify the font and font size it uses ? Presumably it is doing a bad job of detecting the monitor (its a Samsung SyncMaster P2250). Which config file contains a suitable entry, and what is the entry ?
So as the title says shutdown time takes unusually long. Upwards of 4-6 minutes. I'm used to my linux systems taking about 10 seconds to shutdown, 20 tops. In fact this problem seemed to stem from the natty release because I didn't have this issue with the betas or 10.10....
It seems the longer I use my laptop the longer it takes to shutdown. When I do a quick task like a file backup the shutdown takes 10seconds or so, but if I open up a browser and start surfing for a few hours it takes more like 5 minutes.
Shutting down my machine takes a very long time! Not convenient when one want to pack his laptop (I don't dare to when the fan is still blowing).
Upon shutdown, I press 'esc' and see what's happening. The last commands seem to hang. First, shutting down the network interfaces seem to last long than needed (eth0, pan0, wlan0). Sometimes, it stalls also on "networkmanager disconnecting from DBUS" (or something like this ) (which is the very last command executed). Hmm, I will write the exact command down.
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...
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.
A couple of little niggles seen with KDE4.6. On 32bit install, (openSUSE11.3 was clean install)
-- reboot and shut down do nothing but hibernate and sleep are ok, can only powerdown with su privileges, -- order of applications in plasma bar change after reboot.
On 64bit install, (openSUSE11.3 was update of openSUSE11.2)
-- slow poweroff overcome with new user profile, (no longer a problem with latest update) -- inconsistent mouse curser theme, over desktop theme is Oxygen White, over application windows its DMZ (resolved mouse cursor theme issue on 64bit install. -- /etc/sysconfig, parameter X_MOUSE_CURSOR="DMZ" -- and -- /usr/share/icons/default was a link to DMZ -- /usr/share/icons/default.kde4 was a link to oxygen -- changed so that both were linked to DMZ -- mouse cursor now consistent within windows and across desktop.
On one of my computers that I upgraded from 11.3 to 11.4 with a SSD HDD, it no longer umounts any disks on reboot or shutdown, there are no errors shown, it goes from sending TERM and KILL to rebooting.here is my fstab:
I 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'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.
I want to do a shutdown -rF 3:00 to reboot my RHEL server at 3am tomorrow and force an e2fsck on each volume. But I want the e2fsck to run with the -y switch so it automatically answers yes so it will fix any problems it find automatically.
I can't find anywhere where it says if it will do this or not. does anyone know or have proof? Or is there a better way to do what I'm trying to accomplish?
I have recently installed 11.04 natty on Intel Core i3-2100 3.1 GHZ using its own graphic accelerator. When the screen is idle for a long time, more than 1 hour, I get a black screen with the mouse arrow but nothing else. the mouse moves the cursor and Ctl+Alt+F1 does work. How to fix this problem?
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.
