Search results
Search results 1-13 of 13.
Can't you use sudo for this?
I think this problem is the same as I had, see my bug report at http://qa.mandriva.com/show_bug.cgi?id=36408 (I'm using Mandriva) for my findings and a workaround on this problem.
I don't know such a script or place, but there might indeed Point is that you cannot lock the KDE way because that way becomes available seconds after the desktop has appeared.
I suspect your script is run last in the KDE start process and I'm afraid there is not much you can do about this fact. If you really want a full proof system, you could look into Xscreensaver. It surely starts during or before KDE starts and also is capable of locking the screen via a command (xscreensaver-command -lock).
Hi again! You should put that command in a .sh and save that file to ~/.kde/Autostart (chmod it executable for your user off course). I believe that works. One thing of concern would be that you don't know when KScreensaverIface becomes available in the starting process and that you don't know when the programs/links in that directory are being executed. So maybe you have to incorporate a pause, but that can easily be done with sleep Hope this helps, I'm curious to see if it works.
I found this: http://blog.vrplumber.com/1408
I believe it is in ~/.kde/share/config/kmixrc.
Thanks, I hereby forward your credits to the makers of krandrtray and the inventors of the X11 Randr extension.
Assuming you're used to Windows, you can think of a shell as a command prompt. Start it with Alt+F2, typing in konsole. A black screen then appears with a promt at which you can enter commands or run programs. Now type in krandrtray followed by enter and you should get a new system tray icon. You can now exit this shell with exit. You could also have done it by starting krandrtray directly from the Run Command screen, but now you also know how to start and use a shell
You can fix the problem of a MTU that is too large by using ifconfig. Set it lower for the interface your ADSL modem is connected to on the other end, something like ifconfig eth0 mtu 1464. The best value for this would be the largest ping packet without the 'Frag needed and DF set'-message. However, I can't see why your high MTU is causing packet loss, this must be a completely different problem I don't know what truncated means, sorry. Maybe someone else has a clue on this?
Clearly an issue with your MTU, it's indeed too large. Packets that are too large cannot get out or in. You can use ping (e.g. ping -s 1000 -M do host.on.internet) to find your ideal MTU.
Try running it from a shell.
I have the somewhat the same problem. Some shortcuts only work on 0:0, some only on 0:1 and there might be some that work on both. Killing one of the khotkeys-processes doesn't work. Isn't there some way to configure the second window manager instance of KDE in a way it doesn't start a second khotkeys-process?