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
Before i wiped windows (and the dual-booted slackware on it to make a slackware only hdd) i (sort of) backed up my files. I put something into my /etc/fstab that wiped /tmp/ when i shutdown/rebooted.
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.
Running 13.37. If I am in xfce, I have the option to shutdown or restart in addition to log off. In KDE I don't. how to get them to show up.
View 5 Replies View RelatedI 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.
I just happen to have a glitch with my newly rebuild slackware server. This morning everything was working fine. Then having recently setup raid arrays, I decided to try MrGoblin's rc.mdadm script to monitor the raid arrays.
I copied the rc script to rc.d & added lines in rc.local to start the script, and a line in rc.6 to stop the script when shutdown or reboot.
Now, I cant reboot neither I can shutdown...
If I issue the command "shutdown -r now", Slack execute the normal shutdown or reboot steps, unmount the local FS, turn off swap, remount the rootdev as readonly, and then I see:
Code:
Mdadm monitor not running:INIT: no more processes left in this runlevel & it stalls at this point forever...
Before the machine would have rebooted after this line. What could explain this? Now I have to hard power down or reset the machine, and of course, upon rebooting I get a REISERFS warning of unclean shutdown...
Content of the rc.local:
Code:
#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local startup commands in here. Also, if you have
code....
I have included a "start" (slackware logo) button and an exit button. The problem is, neither of these buttons work. The start button should bring up the fluxbox menu but I have found to bring up this menu is by right clicking on the screen.the only way to logout and go back to the login screen seems to be via the fluxbox menu. Running "exit" from the command line only exits the terminal of course.
View 14 Replies View RelatedTo an empty disk I installed:
1) Windows XP & then shrank it's partition to make room for OpenSuse) 2) OpenSuse with grub installed on the MBR (& then shrank the home partition & created a new root and home partition for Slackware 13.1). These two OSes dual-booted properly 3) Slackware 13.1 with LiLo installed to the superblock of the Slackware root partition (sda8). How do I get Slackware to be a 'working' selection on the boot menu?
I've recently found out about "lilo -R" (I've always hated waiting for Lilo after reboot but never thought that a solution could exist :-) ), but I would like to avoid typing it in a shell windows. It would be easier if I just had a "Reboot to Windows" option in the KDE logout menu.The question is: do I have to recompile KDE or there is a simpler way (i.e. scripts)?
View 2 Replies View RelatedI want to disable Reboot and Shutdown options from the drop down menu in Ubuntu 9.10. I tried this:[URL] I also tried to modify the gdm.conf file, but the changes I made, made no difference.
View 2 Replies View RelatedI know that there is a nice little launcher that will run the script for Grub to select a menu option upon shutdown for a reboot [URL]
I however would like to use this from Windows XP and have grub select menu item 2 during a reboot. Does anyone know if there is any way to set Grub commands from within Windows?
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?
View 12 Replies View RelatedIt 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?
View 1 Replies View Related1) 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'm using Slackware 13.1.
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.
View 10 Replies View RelatedFurther 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.
I've install Slackware 13.1 and i cannot shutdown my PC. The shut down process stop while trying to run PCMCIA module.
This is the first time that happens.
From Hardware point of view , i didn't do anything at all (if that helps).
I just recently installed slackware 13.37 as a fresh install. In firefox, I currently only have the flashplayer plugin installed, no themes, no other add-ons. Firefox will open fine the first time, however after I close it and try to open it again, I get a message saying that firefox is already running and the process must be closed before another session can be opened. Looking through the open processes, firefox-bin still shows open. I can kill -9 firefox-bin and restart firefox, but then I have the same problem after close. I have deleted my .mozilla folder, which did not help and I have deleted the libflashplayer.
View 13 Replies View RelatedUsing slack 13 this started happening after my last 'upgrade-all' with slackpkg where I think it updated ssl and sea monkey. When I shutdown (fluxbox) it hangs at "starting up x11 manager" I have to ctrl alt del to get it moving again.
View 3 Replies View RelatedOS = Slackware 13.1
I'm normally a KDE user but tried xfce4 and found that it works nicely. I wanted to switch to it for a while. I did find one particular problem: When you try and end the session, you can Log Out but can not Restart or Shutdown. If you click on Restart or Shutdown it asks for password Even after entering a valid password, it will not allow the action.
(I tried user and root's passwords.) It says "Please enter your password." After entering the password it says, "Either the password you entered is invalid, or the system administrator disallows shutting down this computer with your user account." (Before you ask; my user is in power group.)
I tinkered with it for a while and decided it must have something to do with KDM and so I switched my default runlevel to 3 and started xfce4 [via startx] and it worked as expected. Next I tried using xdm instead of kdm and YES, it works as expected. I was able to Restart or Shutdown (no asking for password, it just does it.) What is it about KDM that does not allow xfce4 to restart or shutdown?
My home computer is (of course) a multi-user system with my wife and I each having separate non-root accounts. Usually at the end of the day I exit X, drop down to the terminal, su to root and type
Code:
shutdown -h now
to turn the computer off for the night.
However, my wife doesn't know (or care to know) the root password, but she would like to be able to shutdown the computer.I tried making a /etc/shutdown.allow file, and typing
Code:
/sbin/shutdown -a -h now from her account, but it didn't work. I got an error that one has to be root to do that.
So, how do I allow regular users to shutdown?
Basically what is happening is i installed slackware 13 and then madwifi following these instructions [URL] and it works great, then i shutdown or restart and when i come back to linux i dont have the internet anymore. This happened twice already and i dont know how to fix it. by the way i have 2 hard drives, one with windows xp and one with linux. i dont think this would affect anything but i put it just in case.
i will try to install it again from scratch following those instructions exactly because i just went to the configure and make part, i will take the post down if it works after that but if this is up then it didnt work. i know i didnt provide any info on things like the output of iwconfig or the model of my network card (atheros something) but all i can say right now is that i use the latest version of madwifi, 0.9.4, the fixed one that works for the latest models of atheros.
I've got a minor problem with my GPU: I replaced the OEM GeForce 6200 with a 9600 GT, but I believe the shutdown temperature is still set to the 6200's; causing annoyance with graphically intensive programs/games. It was a fairly small card, and has a low shutdown temp. BIOS revealed no settings, is there a setting for this in slack?
View 3 Replies View RelatedI just realized that my /tmp directory is not being cleared at shutdown time. How to enable this? I'm running -current.
View 8 Replies View RelatedI'm using Slackware 13.1 on my laptop, and sometime ago it make some beeps on shutdown, and when I don't find any word on a page on Firefox(using the find tool on Firefox).
View 2 Replies View RelatedWhat if I want to install Slackware for my parents so then I no longer have to get rid of virus and malware for them. Is there way so they never have to log on as root? Any way to access CD's and to shutdown computer? I only know how to do those things as root.
View 7 Replies View RelatedI have been looking for a lightweight bandwidth monitoring app and came across bmon. It does what I need. However it has an interesting way of exiting.
when it is running and you close it down it ask you 'Really quit (y/n)' and does not shut down. I am used to just right clicking on my desktop and selecting 'leave' when it comes to shutdown time.
A few times now the laptop hangs on shutdown if bmon is open. I guess it is due to the app asking if it should shutdown. Is there a way to disable the app asking or alternatively nuke it for sure with some script on shutdown.
I could search the relevant konsole running the app and go thru the steps to shut it down but sometimes I am in a hurry and it doesn't feel like the way to go anyhow?
