When I click logout or shut down I get a countdown saying I will be logged out or shut down in 60 seconds, then it counts down. I can click the "shut down now" button, but I find this behavior incredibly irritating. When I click logout I would like to logout NOW.
View 6 RepliesWhen I log into my ubuntu 10.04 after booting my computer, I receive a 30-40 second lag before I can actually log in. During this lag, I can move the cursor and the login background is shown, but the computer seems to be doing nothing. It is as if there is a sleep command before I even log in. I am using a Sager 2096 computer but I got this computer for free and it did not come with the specs. I had installed a 64-bit version of Ubuntu because this computer has a 64-bit architecture. However, whenever I install software, it always has to install the x86 version because the x64 is "not supported." Perhaps I have a mix of 32 and 64 bit programs and that is what is screwing it up?
View 3 Replies View Relatedi'm running ubuntu (32bit) on a quad core compaq presario with 3.9gb of ram and a 500gb HDD.sometimes when i have few windows open (nautilus, firefox) and i'm watching a movie the hard drive will spin up for no reason and everything on screen will hang for a few seconds.i did a hard drive check and everything seems to be ok there. i have a geforce 8600 gt with the recommended 185 driver installed.i'm wondering what the problem is? could it be hardware?
i've noticed this is happening from time to time, no matter what i'm doing. First the computer beeps then the hard drive speeds up and everything lags.
I would like to watch a baseball game on TV, but listen to the radio broadcast. The TV is about 10 seconds behind the radio, though.Does anyone know a way to delay the input from my radio by 10 seconds and output it again to the speakers? I can do this on Mac OS X or Linux (or even Windows). I have Audio Hijack Pro, but there is no such effect.
View 2 Replies View RelatedI added a Netspeed applet to my top panel. It screwed up my Me Menu and Logout menu, so I removed it, rebooted. However after the reboot my menu's are still screwed up. See the attached screen shot. The Me Menu works however if I click where the logout menu is supposed to be I don't get anything.
View 9 Replies View RelatedOn two of my machines that have Ubuntu 10.10 on them, I cannot shut down, restart or log out by pressing the "power button" on Gnome panel. I can not even do "Alt + Ctl + Backspace" either. However, I can shutdown or restart by: Quote: sudo shutdown -h now sudo shutdown -r now
View 4 Replies View RelatedMy normal day to day user can't shutdown, restart, logout, etc...It just doesn't do anything at all when I try. This wasn't the case three days ago, just fresh installed and seeing the same problem (so it must be some setting saved in my home folder which wasn't wiped).
View 5 Replies View RelatedI just installed debian unstable with kde 4.4.5 on a new hp desktop. Just about everything is working fine except when I try to logout or shutdown by right clicking on the desktop. No matter which option I choose--logout, shutdown, or restart--the screen goes black and nothing happens. I'm forced to do a hard shutdown or use alt-SysRq-B to reboot. I can reboot or shutdown using the command line when logged into kde.
View 4 Replies View RelatedIs there a way to run a prompt at logout or shutdown? I added the following code to .bash_logout, but apparently the �read� command doesn't work from there.
Code:
echo "Make a backup now? (y)"
read answer
if [ "$answer" != "y" ]
then
echo "Backup aborted."
fi
I am using Ubuntu 9.10
I installed a few media servers to stream something to my PS3 over the weekend, but now when trying to shutdown the computer, I'm asked to authenticate with a password since other users are still logged in. I installed quite a few programs over the weekend trying to get it to work, so I can't remove a specific one. Is there a way to see which daemons are logged in under a different session? Found it. It turned out to be mythtv.
View 3 Replies View RelatedLenovo X200 notebook, 64bit maverick, external monitor connected through DisplayPort, fast SSD drive, encrypted homeI'm almost positive these issues were non existent after installing 10.10RC, but I'm not 100% sure. Maybe I will install it again to check it outAnyway, when I try to suspend/restart/shutdown/logout the system often freezes, showing the console with the similar output:I know this guy is running Ubuntu in VM, but I have very similar ouput, except the last usplash line.But the first line I always have in the output is the infamousQuote:GLIb-WARNING **: getpwid_r(): failed due to unknown user id (0)On a very rare occassion, the system hanged while booting (showing the above glib line as well. But that's quite rare, so I'm not that concerned.
Now, sometimes it does respond to ctrl+alt+delete after freezing, and after I hit this combination, another line appears (from memory):Quote:Init: rc main process killed by TERM signalChecking for running unattended-upgradesBut that's it, I cannot do anything else, only hard reset, which is especially painful when I suspend in the middle of work...There is no interesting information in the logs - a few messages in the kern.log, but nothing I think would show the culpritEDIT: other than that, the machine is very stable and I have no issues with it. It also worked perfectly on lucid 32bit.
working on KDE, I cannot shutdown, reset, logout or switch users through graphical interface (you know, bit blue button, 'leave' tab and all these buttons).I've googled the problem, and here's what I have found:[URL]Guys on the Arch forum related the problem to the OGG files and phonon-xine - indeed, I cannot play OGG files anymore.I tried to install phonon-vlc, but the package is not in any of my repositories. I tried to remove libqt4-phonon, but it would also remove half of the system, which isn't the best idea. Someone else suggested to install speex, but it's already installed on my Kubuntu.I'm out of ideas, and I'm not really sure how to reinstall xine and phonon without deleting half of the system like this:
Code:
The following packages will be REMOVED:
akregator amarok apport-kde apport-qt apturl-kde ark calibre digikam dolphin dragonplayer
[code]....
For some reason in the last few days I can no longer logout of KDE, nor will it let me shutdown the system. The only way out is to Ctrl+Alt+Backspace and then shutdown from there. Weird thing is other users can. For me the logout box just disappears and I carry on working or if effects are enabled, the screen blurs and I carry on working. After this the logout box doesn't come back up until I have restarted X (logged out).
I have tried disabling the desktop effects to no availe and I have looked in the messages / kdm logs. So far the only thing I can find is in KDM.log
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86TouchpadOn
> Internal error: Could not resolve keysym XF86TouchpadOff
I have no idea if this is at all relevant but there are several threads from Google relating to this and GDM, although no cures as far as I can tell.
I would rather not delete my ~/.kde folder again if at all possible as it takes ages to reset everything back to normal.
For some reason the shutdown/hibernate/logout options has disappeared from the Indicator session. I can still set my status in EmpathyI have tried reverting to gnome panel defaults (gconftool --recursive-unset /apps/panel && killall gnome-panel), removing and readding and I've checked synaptics and it seems I have everything indicator-related installed.
View 2 Replies View RelatedI have Linux debian 7.7.0 i386-amd64 under VBox 4.3.20 and here is the problem:::
When I open the menu from Linux's top-right corner and click SHUT DOWN..., it shows the dialog with choices, and that Linux guest will automatically shutdown after 60 seconds and I need to change that delay value to 3 seconds. Of course I could just re-click Shut Down -button again, but I don't want to do it. Period.
By Googling I found these "instructions" for UBUNTU:
None of this worked on my 13.04 system. In the end I re-compiled gnome-session.
In gsm_shell.c and gsm_logout_dialog.c change #define AUTOMATIC_ACTION_TIMEOUT from 60 to 5
I am using Fedora 10 .Generally to update I open a virtual console by pressing Ctrl-Alt-F2,login as root and give the "yum update" command.Then I continue using my graphical terminal for other tasks from the 'non-root' account..Now my room-mate comes uses my 'non-root' account to browse web for few minutes and then opens a terminal types "halt", ENTER and viola...! My root account seems to be insulted by a 'non-root' user!.When I am doing updates or other important work as root any silly user can just 'halt' my computer. Can somebody tell me how to set up my computer so that when root is logged in no other user can simply halt the computer.
View 3 Replies View RelatedIf there is a simple way to prevent accidental shutdown when the following situation occurs:
Sometimes, I log in on my father's computer to run some administrations' tasks (updates...). For that, I use SSH since I'm frequently far from my parents and what I want is to prevent a shutdown run by my father. Of course, he should be able to turn off by himself if nobody else is connected.
Molly-Guard allows to prevent distant shutdown, my request is a kind of complementary software.
Does anyone know a project which could fit with this request? Do you have simple ideas to write a short code I know bash, perl, python...
I've installed F13 on a DELL computer. Everything works fine except that under KDE menu if I click on 'shutdown', I have the confirmation windows but the computer never shutdown. Same issue with the the logout button. If I want to stop my commuter I have to open a terminal and type " shutdown now" or "halt".
View 1 Replies View RelatedI'm using Debian 8.2 from a very recent download of the latest NetInst (less than 2 weeks). I'm sort of new to Linux - More accurately, I've used Unix and Linux extensively in the past, so most of my knowledge is dated. In particular, the whole systemd / systemctl paradigm is completely new to me.
Problem: I've added an entry to /etc/fstab to mount a NAS drive as CIFS. When I do a system shutdown or reboot, the system hangs for 90 seconds trying to unmount the NAS. If I manually umount the NAS prior to shutdown / reboot everything works fine.
I've done a fair amount of investigation and web searches, but haven't found a fix yet. Apparently several people were encountering similar problems about a year back, and it seems pretty clear that the root cause what ordering of steps in the shutdown process, e.g., WLAN being turned off before unmounting filesystems. This seems to have been resolved for most users (no one is discussing it any more), but I'm now running into the same issue. Ugh.
I tried to add a shell script to /etc/rc0.d to umount the NAS first in the shutdown process. This had no effect. I assume this is because the new systemd / systemctl paradigm supplants the old /etc/rc model of runlevel control, though it is rather baffling (to me, at least) as to why /etc/rc* still exists if the system is no longer using it...?
Here's some things I'd like to try, but how to proceed:
1. In the new systemd / systemctl paradigm, how do I examine and change the ordering of steps in the shutdown process? I've seen a lot of documentation on systemd, but nothing tells me how to do what I used to be able to do with /etc/rc with a simple rename of a symlink. If I knew how to look at the order of shutdown and change that ordering, I'm fairly certain I could identify and resolve this issue.
2. Is there some other way to mount my CIFS NAS other than editing /etc/fstab? Is it possible that my manual edit to /etc/fstab is the cause of this issue? My research into systemd indicates that it IS supposed to be compatible with /etc/fstab. I have not yet found documentation describing how to mount a filesystem at boot WITHOUT editing /etc/fstab ...
on my netbook I've tried to make possible for my user to shutdown without needing a password. battery could run low when I'm not in front of it. Editing sudoers has allowed my user to shutdown the system, but Gnome still prompts me for the root password whenever root is logged in too. That's usually the case, because to avoid entering the root password multiple times whenever I need elevated privileges and not wanting to cache the root password, I keep a Root Terminal always open.
View 6 Replies View RelatedWhen I'm logged into my account, I can't shut down the computer if someone else is also logged in unless I supply the root password. However, if I log out, I can shut down from GDM without being challenged, even though another person is logged in, which could cause problems if that person is in the middle of some work. Is there a way to password-protect the gdm shutdown function if people are logged in?
View 2 Replies View RelatedI am running Fedora 12 with KDE on an Acer Aspire One netbook.
A recent update has caused the KDE shutdown/restart/logout buttons (found for example through the Fedora -> Leave menu or by pressing the power off switch)to stop working. I am having to shutdown using shutdown -P now command.
So I have the following questions:
a) Has anyone else had this issue and knows a workaround/fix?
b) Does anyone know what package these belong to so I can try an older version?
c) Does anyone know where this package writes its logs, or if I need to install anything for it to do so so I can have a look?
d) Does anyone know the command-line interface to these commands - that may give me either a more gentle workaround than shutdown -P now, or some insight into why the command is no longer working.
how to record/save logout/shutdown messages for OpenSuse 11.2.
View 9 Replies View Relatedas a normal user when I click logout from a KDE session nothing happens and I can't re-launch logout again, shutdown is doing the same.I have just upgraded to fc14 from fc13 yesterday tried to delete .kde folder and it has not been succesful tried to create another user and log to kde session and the new user also failed to logout or shutdown Root user is able to logout and shutdown I have no probs on GNOME for root or users.
View 1 Replies View RelatedWhen trying to "Leave" the system (either via the small button on the lower right of the taskbar or by right clicking on the Desktop and selecting "Leave") the logout / shutdown / restart screen comes up. I have the "Logout" desktop effect activated, which is supposed to desaturated the background when the Leave screen appears. However, instead of simply greying out the background, the image on the desktop and the rest of the screen also gets slightly distorted, with seemingly random distortion effects cropping up all over the place (e.g. horizontal lines or large blurs).
These distortions are different every time the Leave screen comes up. The Leave screen itself is displayed fine, and apart from the dodgy background I have no other issues with the whole process (the system shuts down or restarts properly according to my choice). I am using the Radeon drivers, and all other desktop effects I have on (Magic lamb, cover switch, present windows, etc) work fine and without a hitch. It's only the Logout effect that seems to glitch. Are the distortions intentionally created by the effect in order to emphasize the focus on the Leave screen?
I have lost my ability in KDE Menus to do a shutdown or restart. My only option is to logoff or cancel. This started occurring about 2 weeks ago, possibly 2 KDE workspace updates ago. I have been assuming it would get fixed with an update but so far it has not.
I am running Fedora 10 x86_64, kernel = 2.6.27.7-134.fc10.x86_64, and the KDE version is:
kde-filesystem.noarch 4-20.fc10 installed
kde-settings.noarch 4.1-4.20081031svn.fc10 installed
kde-settings-kdm.noarch 4.1-4.20081031svn.fc10 installed
code....
I have 3 different systems all running the same OS and KDE versions and it is happening on all 3 systems. All systems have the "Offer Shutdown Options" selected in Session Manager. I have even turned this option off, rebooted, and then back on to try to jumpstart it but that did not work.
Additionally, I have tried deleting the contents of the /tmp directory while in single-user mode and also the .kde under my home directory. This made no difference.
Another symptom I am noticing is that any desktop widgets that I create all get moved to the upper left-hand corner of the display whenever I reboot and log back in. Any extra shortcut widgets that I add to the panel are also gone the next time I log in.
Again, these same symptoms are occurring on 3 different machines.
These symptom do not occur after a fresh install of FC 10. It is breaking during one of the yum updates but I have not narrowed it down yet as to which update is causing this to happen.
Simple question: what parameters can be used to shutdown a computer running Linux/OSX in 30 seconds? I've always run Windows, where I would go shutdown -s -t 30 but the parameters are different. I've looked it up here but it will only let you shut a computer down at a specific time (like 8:00) rather than in a specific amount of seconds.
View 4 Replies View RelatedI have just installed Slackware 13.1 32bit. My hardware is a P-4 3Ghz with a gig of ram. Intel on board graphic and sound.
This is the best implementation of Kde I have used so far. Slack 13.1 is amazing. The install went very well and everything we configured properly.
My problem is when I start Kde or try to shut dowm or logout I get the same error for knotify: Unable to use the Xine Multimedia Backend:Could not find plugin 'Xine' for application 'Knotify'
I get this same error with the application name at the end of it. If I open amarok I get the same error message with amarok at the end. If I try to click a misic file in dolphin same error message.
When I try to shut down or log out from menu I get the xine error and nothing happens. The only way I can log out is Ctrl+Alt+Backspace to get to the KDM log in screen and then I am able to shut down from the menu.
I have been looking on the forum and using google but have found nothing useful.
The error pops up when I try to play a cd or music on the hard drive.
I have done 3 clean installs for this problem and it remains, i don't want to do it from the terminal..(Buttons exists but they won't work...)
View 3 Replies View RelatedAfter GRUB 2 comes up (I'm running Ubuntu 10.10) and I choose the OS to boot, there is about a 5 second delay where nothing appears to happen after I make the selection -- no disk activity. It happens consistently every time I boot. Again, this is after I choose the OS to boot, so it shouldn't have anything to do with the standard delay to allow me to choose the appropriate OS.Is there a good way to troubleshoot this and determine what is causing the delay?
View 4 Replies View Related