Slackware :: Hal Daemon Stalls And Logout Shuts Down Computer
May 22, 2010
1) When my computer boots up it stalls when HAL daemon loads. This did not happen until I plugged in a defective hard drive. Anyone have any idea of how to go about fixing this?
2) If I open the session manager system setting, and untick "confirm logout" my system will shutdown instead of logging out. With the option enabled my computer logs out normally. I don't need the confirmation and find it redundant and feel like Linux is holding my hand and that's why I use linux because generally speaking I don't like an OS that wants to hold my hand, metaphorically, I mean.
I am new to linux and WAS a window user. boy am i glad i switched, but still have lots to learn. Any who, currently i am working on a server for some residents at my current job. I have DNS and everything setup right and it is working. Samba on the other hand is configured right but it keeps shutting down after about a minute. it says "Dead". Ill restart the service(rcsmb start), and keep checking the status, and after about a minute it shuts down again. I have done a restart, double checked my configurations and still cant find why this is happening. (config file somewhere?)
Now since im new, im not sure what info any of you would need to help me out, so please chime in, if there is a specific file or info you need to know, please let me know and ill try my best to get it.
Since when I installed Squeeze I'm having this problem. You know how disturbing it is. I don't know if this is related in any way, but when I play music or watch video and do other things at the same time it looks like this happens more.
I installed ubuntu 10 yesterday and I have a real frustrating problem. It shuts down for no reason at all, at first I thought it was because I was not using it (power management or maybe because of the screensaver) so configured it to never put it to sleep or shut down, and disabled the screensaver but it keeps happening. This is actually the second time I'm writing this post, because it suddenly shut down again while I was writing this before submitting it. I used to never have this problem before when I was using windows, so the problem must be something with Ubuntu.
Could it be something with my gfx driver? I tried configuring Fluxbox to use my second screen as an extended desktop but couldn't get it to work except with Gnome. If I do "fglrxinfo" I get a segmentation fault, so I messed that up but I'm okay with that because everything is working like I want it with Gnome. One weird thing I've noticed is that ubuntu once said (when booting) that it couldn't find /dev/null...? Should I just try a reinstall? I'm on a quad core with 2GB ram and an ATI HD 4870 2gb graphics card.
I've been using Ubuntu for about one year. Recently upgraded to 10.04. The PC tries to boot, comes to the "Booting from device hd..." screen and then shuts down. It shuts down or halts but doesn't power off. The CPU is still powered. This happens for about 2 in 4 boots. The recovery mode runs just fine. It says no damaged partitions. Only the 'booting from device' is the problem point.
After using Ubuntu 10.4 for months, my computer has started turning itself on without my pressing the on button. Sometimes it gets halfway through the boot process and shuts itself down. Sometimes it gets all the way to the desktop and a window pops up saying shutdown in 60 seconds however it never waits but shuts down immediately. Probably the second time this happened, I had time enough to get to the Power Manager and made sure it was set to 'never' power down. Currently the on/off cycling is happening so quickly I can't check the BIOS or grup. My only control is the master power switch on the back
I upgraded to 10.04 and it is sooooo annoying. The computer will just randomly shut off. Sometimes it will be 10 minutes after turning the computer on, sometimes 10 hours!
Sometimes, when I leave my Ubuntu's X Server on, I'll come back after several minutes and see that my machine is powered off. Sometimes this happens, sometimes it doesn't, but I don't think it's because of hardware failure rather than my lack of measurement.
It used to power off in terminal mode (CTRL+ALT+F1) but then I added this to ~/.bashrc and it went away:
Code: if [ "${USER}" == "root" ] then export TMOUT = 3600 fi
Also, I checked my logs and I see this:
Code: Feb 2 00:00:09 l1nux AptDaemon: INFO: Quiting due to inactivity Feb 2 00:00:09 l1nux AptDaemon: INFO: Shutdown was requested
Since it's not a CRITICAL message, but an INFO, it seems like its a planned shutdown.
I installed Ubuntu 10.10 last night by USB Drive, It worked for about 10 minutes, then shut down. After I rebooted, it stays on for somewhere near 3 minutes.
My computer randomly shuts off sometimes and I'm not sure what causes it. It doesn't always happen when I'm doing the same thing.I know this is hardly any info, but if someone could let me know where I can go to find logs and Also, if this means anything, to restart my computer I need to physically turn it off (the I/O switch on my PS) and let the capacitors on my board empty out before starting it up again.
today i started getting this on my laptop:when starting synaptic package manager or software sources from system administration, neither app do launches and the computer shuts down.i have been using ubuntu on this toshiba laptop for about three years now.
UPDATE2: As of 2 weeks ago, it won't boot at all. UPDATE1: HDD booted OK, but I don't know how to copy the GRUB file. Could this be a hardware temperature problem? I have just replaced a Hard Drive, & had to reinstall XP & 10.04.2LTS from scratch, (it was a TOTAL failure) The system now will not boot into XP, or either of the 2 Linux kernels or the recovery modes, without several attempts. ( I'm using a LiveCD now.)
POST is good. GRUB loads, but when I select an OS, it powers off. Windows shows the splash for a few seconds, then shuts down. Yesterday, I was able to boot into Linux after booting into Windows, but today Windows won't boot either. On examining the GRUB menu (e) the first line in the Linux records is 'recordfail' I will attempt to boot from HDD now, & post the GRUB output here. EDIT: If I run MEMTEST first, up to Test6, it boots normally.
I want to create an unprivileged user account, say 'shutdown', which can be used only to shutdown the system. I followed the instructions in ut when I login into the system, I get this error 'Cannot execute /usr/bin/sudo /sbin/shutdown -h now: No such file or directory'.These are the configurations that I did
/etc/sudoers: Code: shutdown localhost=/sbin/shutdown -h now
after a successful installation of the latest debian testing amd64 kde CD-1 iso, the monitor shuts off about 2 seconds after passing the grub2 menu while computer remains powered.
After updating my Slackware-Current (there was kernel and glibc package updates), I just get a black screen with a blinking "_" in the top-left corner when I logout.
I checked /var/log/kdm.log and found these errors:
Code:
I've found a workaround: uncommenting "TerminateServer=true" in kdmrc.
I'm trying to run Slackware 13.37 64-bit in a VirtualBox virtual machine. My VirtualBox version is 3.2.12. I had to disable compositing to keep the X-Server from reporting a segfault.Now the problem is that on logout from KDE I get a completely black screen. I can switch to a console session and type commands to get the login screen again.
telinit 3 telinit 4
I tried editing "kdmrc" to add the line "TerminateServer=true" but it had no effect on the problem.I had this working with Slackware 13.1 at one time, but I can't seem to get it working properly now even without desktop effects.I'm trying to avoid changing my VirtualBox software since each version seems to just introduce new and different bugs. The 4.X versions are not yet very stable.
I use Slack 13-32 with kde-431, but when in kde logout actually get out of the X-KDE ...I have that after leaving the kde, type "logout" at the command line ...How to make a real logout when exiting KDE in Slack?
It seems like 1 out of every 3 times I try to log out of xfce it stalls. I can continue to work but if I want to leave I have to ctrl>alt>backspace. Has anyone else had a problem like this?
Whenever I logout of KDE and go back into console mode, the characters at the console screen become unreadable gibberish. Is anyone else having this problem?
I can ctl+alt+F? to work at another console screen, but the ctl+alt+F1 screen remains unreadable until I reboot.
If, as root, I 'Leave' --> 'Logout', I get the KDE login screen.If, as user rob, I 'Leave' --> 'Logout', I get a black screen from which I must power off to recover, and I use the term very loosely. User rob is a member of the 'power' group.
As a normal user I have activated the functions of the Quit applet, i.e. Logout, Shutdown and Restart are active buttons. I am able to restart or shutdown, no problems. But when I use the Logout button I don't get logged out, just returned to the login shell & I am still logged in as my user. I don't have a display manager installed and I do NOT want to use a display manager such as XDM or GDM. How do I get the Logout button to actually logout the user? It appears I am only getting logged out of the x-session, but I want complete logout.
I recently installed a software package that needs a command called 'daemon' to be able to start up. Slackware doesn't seem to have this command and I'm unable to find it. Where can I get it and what exactly is it that it does?
I have slackware 64 13.37 Kernel 2.6.37.6 I am trying to install notifcation daemon so I can use notify-send. I am trying to install the package notification-daemon, via sbopkg using the 13.37 repository. I have installed dependencies: ORBit2, GConf, libsexy.I hit this error during installation of notification-daemon.
/usr/lib/libdbus-glib-1.so: could not read symbols: File in wrong format collect2: ld returned 1 exit status
I did previously have gsb gnome 3 installed, but removed that and then lost notify-send.
I 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.
