how to not lock the screen

[Michael Hennebry]

I recently installed FC8 and  haven't been able to find
the incantation to tell FC8 and KDE not to lock my screen.

How do I tell them not to lock my screen?

-- 
Michael   hennebry(a)web.cs.ndsu.NoDak.edu
"Those parts of the system that you can hit with a hammer (not advised)
are called Hardware;  those program instructions that you can only
curse at are called Software."

[g]

Michael Hennebry wrote:
>  Thanks. 
you are welcome. glad you got things to work for you.

>  I'd found the spot before, but coudn't get it to work.
>  'Require password to stop' wasn't xed, but it was grayed out.
>  xing 'Start automatically' eliminated the need for a password. 
interesting. "xing 'Start automatically'" is among 1st in my initial
setup
of kde. i like to blank crt. was not aware of effect if password not xed.

live and learn, die and forget.

thanks for info.

later.

--

tc,hago.

g
.

in a free world without fences, who needs gates.

[g]

Michael Hennebry wrote:
>  I'm at work now and can't test any theories. 
i just sent you a message off list.

have a look at it and reply back thru it.


-- 

tc,hago.

g
.

in a free world without fences, who needs gates.

[Michael Hennebry]

On Tue, 24 Jun 2008, g wrote:

>  Michael Hennebry wrote:
>  > More data:
>  > The problem went away for a while for no apparent reason.
>  > Hence, I haven't posted in a while.
>  > I turned off my computer when I went away for a weekend.
>
>  you should have stayed home or left computer on.
>
>  > I turned it on yesterday and today the problem is back.
>
>  or, left it off. :o)
>
>  > Any ideas?
>
>  previous post are on other system. will have to login on it to see
>  what all has been gone thru. back later after i check. 
Thanks.
Assuming that I can get to anothe virtual terminal,
is there a way to ask which processes are using the X display?
Better yet, is there a way to find out which process has a lock
or created the top window?

I'm at work now and can't test any theories.

-- 
Michael   hennebry(a)web.cs.ndsu.NoDak.edu
"Those parts of the system that you can hit with a hammer (not advised)
are called Hardware;  those program instructions that you can only
curse at are called Software."

[g]

Michael Hennebry wrote:
>  More data:
>  The problem went away for a while for no apparent reason.
>  Hence, I haven't posted in a while.
>  I turned off my computer when I went away for a weekend. 
you should have stayed home or left computer on.

>  I turned it on yesterday and today the problem is back. 
or, left it off. :o)

>  Any ideas? 
previous post are on other system. will have to login on it to see
what all has been gone thru. back later after i check.


-- 

tc,hago.

g
.

in a free world without fences, who needs gates.

[Michael Hennebry]

More data:
The problem went away for a while for no apparent reason.
Hence, I haven't posted in a while.
I turned off my computer when I went away for a weekend.
I turned it on yesterday and today the problem is back.

Any ideas?
The problem is rather annoying.

On Sun, 15 Jun 2008, Michael Hennebry wrote:

>  On Mon, 9 Jun 2008, g wrote:
>
>  > Michael Hennebry wrote:
>  > > I did an experiment.
>  > <snip>
>  > > Eventually something else blanked the screen and wanted my password.
>  >
>  > 2 good reasons for what i have 4 suggestions.
>  >
>  > 1a) if not already level 3, change '/etc/inittab' to *id:3:initdefault:*,
> reboot.
>  > 1b) in 'level 3';
>  >
>  >   >$ mv .kde .kde.old
>  >   >$ startx
>  >
>  > if still,
>  > 2) add another user, login as, if continues, #3.
>
>  I got around to trying 1 and 2, but no joy.
>  After exiting X, I did notice window manager complaints.
>  I kind of fuzzy on what they were.
>  Possibly they were the result of trying to run a gnome desktop without gnome.
>  IIRC I didn't clickon gnome during install.
>  I tried grepping /var/log/* , but didn't find the complaints. 
-- 
Michael   hennebry(a)web.cs.ndsu.NoDak.edu
"Those parts of the system that you can hit with a hammer (not advised)
are called Hardware;  those program instructions that you can only
curse at are called Software."

[Michael Hennebry]

On Sat, 7 Jun 2008, g wrote:

>   > Michael Hennebry wrote:
>  > What is an sel level?
>
>  SELinux 
Apparently not enforcing.
A .so file compiled without -pic ran.

>  > hennebry as usual.
>  > yes, no, no.
>
>  was if you had any type of 'file recovery' running'.
>
>  > [hennebry@localhost ~]$ find . -newer tstamp.fn -print -exec ls -ld \; >
> hold.list 
I forgot the "{}"

>  > [hennebry@localhost ~]$ cat hold.list
>
>   > drwx------ 55 hennebry hennebry 4096 2008-06-07 09:31 .
>   > ./.kde/share/config/kdesktoprc
>
>  strange way 'kdesktoprc' is shown, being i have it as a file, not a directory.
I forgot the "{}"

>  anyway, my 'kdesktoprc', sleep enabled and lock disabled
> shows;
>
>     [ScreenSaver]
>     Lock=false
>     Saver=KSlideshow.desktop
>     Timeout=480
>
>  w/ lock enabled;
>
>     [ScreenSaver]
>     Saver=KSlideshow.desktop
>     Timeout=480
>
>  where 'lock=' went, do not know. may be else where with 'display power
> off'.
>  not sure of where it would be tied in, and need 'find /'. being that it is thru
>  'control center', setup file could be among /etc or /usr. 
I have:
>  [ScreenSaver]
>  Lock=false
>  LockGrace=300000
>  Saver=KPolygon.desktop
>  Timeout=1200
>
>  [Version] 
300000 ms=5 min.
Getting rid of LockGrace didn't help.

>  > I think something else is demanding a password.
>
>  maybe. 'ps -el|less' to see what else is running. 
Lots there.  Little that I recognize.
I've appended the result of ps -el > /tmp/ps.txt
I removed some stuff that I did recognize: bash, xterm, vim.
Is gnome-screensav supposed to be there?

>  > Whatever it is is taking more than 5 minutes to blank the
> screen.
>  > The screensaver is set for an animation.
>
>  nft. 
Not for tourists?

>  if no one comes up with solution, you could always 'mv .kde
> .kde.bad'
>  and run 'startx' again.
>
>  yes, i know, re-config kde. but what the heck, it might cure things.
>  at least you will still have desktop icons. scattered, but there.  :o)
>
>  there is always loading source and reading a bunch c files.  :o( 
My previous such efforts did not go well rewarded.

>  loads of luck and perseverance. 
interesting times.


F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTY          TIME CMD
4 S     0     1     0  0  80   0 -   528 -      ?        00:00:13 init
1 S     0     2     0  0  75  -5 -     0 -      ?        00:00:00 kthreadd
1 S     0     3     2  0 -40   - -     0 -      ?        00:00:01 migration/0
1 S     0     4     2  0  75  -5 -     0 -      ?        00:00:00 ksoftirqd/0
5 S     0     5     2  0 -40   - -     0 -      ?        00:00:00 watchdog/0
1 S     0     6     2  0 -40   - -     0 -      ?        00:00:01 migration/1
1 S     0     7     2  0  75  -5 -     0 -      ?        00:00:00 ksoftirqd/1
5 S     0     8     2  0 -40   - -     0 -      ?        00:00:00 watchdog/1
1 S     0     9     2  0  75  -5 -     0 -      ?        00:00:05 events/0
1 S     0    10     2  0  75  -5 -     0 -      ?        00:00:06 events/1
1 S     0    11     2  0  75  -5 -     0 -      ?        00:00:00 khelper
1 S     0    64     2  0  75  -5 -     0 -      ?        00:00:00 kblockd/0
1 S     0    65     2  0  75  -5 -     0 -      ?        00:00:00 kblockd/1
1 S     0    68     2  0  75  -5 -     0 -      ?        00:00:00 kacpid
1 S     0    69     2  0  75  -5 -     0 -      ?        00:00:00 kacpi_notify
1 S     0   143     2  0  75  -5 -     0 -      ?        00:00:00 cqueue/0
1 S     0   144     2  0  75  -5 -     0 -      ?        00:00:00 cqueue/1
1 S     0   146     2  0  75  -5 -     0 -      ?        00:00:00 ksuspend_usbd
1 S     0   151     2  0  75  -5 -     0 -      ?        00:00:00 khubd
1 S     0   154     2  0  75  -5 -     0 -      ?        00:00:00 kseriod
1 S     0   189     2  0  75  -5 -     0 -      ?        00:00:07 kswapd0
1 S     0   229     2  0  75  -5 -     0 -      ?        00:00:00 aio/0
1 S     0   230     2  0  75  -5 -     0 -      ?        00:00:00 aio/1
1 S     0   377     2  0  75  -5 -     0 -      ?        00:00:00 kpsmoused
1 S     0   414     2  0  75  -5 -     0 -      ?        00:01:48 ata/0
1 S     0   415     2  0  75  -5 -     0 -      ?        00:02:17 ata/1
1 S     0   416     2  0  75  -5 -     0 -      ?        00:00:00 ata_aux
1 S     0   423     2  0  75  -5 -     0 -      ?        00:00:00 scsi_eh_0
1 S     0   424     2  0  75  -5 -     0 -      ?        00:06:02 scsi_eh_1
1 S     0   425     2  0  75  -5 -     0 -      ?        00:00:00 scsi_eh_2
1 S     0   426     2  0  75  -5 -     0 -      ?        00:00:00 scsi_eh_3
1 S     0   438     2  0  75  -5 -     0 -      ?        00:00:03 kjournald
1 S     0   470     2  0  75  -5 -     0 -      ?        00:00:00 kauditd
5 S     0   502     1  0  76  -4 -   906 -      ?        00:00:00 udevd
0 S   500   673  2726  0  80   0 - 12013 -      ?        00:00:03 gvim
1 S     0  1263     2  0  75  -5 -     0 -      ?        00:00:00 kmpathd/0
1 S     0  1264     2  0  75  -5 -     0 -      ?        00:00:00 kmpathd/1
1 S     0  1295     2  0  75  -5 -     0 -      ?        00:00:00 kjournald
1 S     0  1296     2  0  75  -5 -     0 -      ?        00:00:02 kjournald
1 S     0  1297     2  0  75  -5 -     0 -      ?        00:01:08 kjournald
1 S     0  1298     2  0  75  -5 -     0 -      ?        00:00:00 kjournald
1 S     0  1771     1  0  80   0 -   596 -      ?        00:00:01 dhclient
1 S     0  1858     1  0  80   0 -  2919 -      ?        00:00:00 restorecond
1 S     0  1868     1  0  80   0 -   642 -      ?        00:00:20 irqbalance
5 S    32  1878     1  0  80   0 -   564 -      ?        00:00:00 rpcbind
5 S    29  1898     1  0  80   0 -   488 -      ?        00:00:00 rpc.statd
1 S     0  1926     2  0  75  -5 -     0 -      ?        00:00:00 rpciod/0
1 S     0  1927     2  0  75  -5 -     0 -      ?        00:00:00 rpciod/1
1 S     0  1936     1  0  80   0 -  1335 -      ?        00:00:00 rpc.idmapd
1 S     0  1993     1  0  80   0 -  3206 -      ?        00:00:12 pcscd
1 S     0  2003     1  0  80   0 -  3356 -      ?        00:00:39 rsyslogd
5 S     0  2007     1  0  80   0 -   440 -      ?        00:00:00 rklogd
5 S    81  2022     1  0  80   0 -  3269 -      ?        00:00:02 dbus-daemon
5 S     0  2034     1  0  80   0 - 10811 -      ?        00:01:40 setroubleshootd
1 S     0  2048     1  0  80   0 -  2169 -      ?        00:00:14 automount
1 S     0  2066     1  0  80   0 -   439 -      ?        00:00:00 acpid
5 S     0  2075     1  0  80   0 -   787 -      ?        00:00:00 hcid
1 S     0  2084     2  0  75  -5 -     0 -      ?        00:00:00 btaddconn
1 S     0  2085     2  0  75  -5 -     0 -      ?        00:00:00 btdelconn
5 S     0  2100     2  0  70 -10 -     0 -      ?        00:00:00 krfcommd
4 S     0  2105  2075  0  80   0 -   740 -      ?        00:00:00 bluetoothd-serv
5 S     0  2113     1  0  80   0 -  1520 -      ?        00:00:10 sshd
5 S    38  2128     1  0  80   0 -  1068 -      ?        00:00:04 ntpd
5 S     0  2151     1  0  80   0 -  2379 -      ?        00:00:28 sendmail
1 S    51  2160     1  0  80   0 -  2055 -      ?        00:00:00 sendmail
1 S     0  2171     1  0  80   0 -   465 -      ?        00:00:00 nasd
5 S     0  2180     1  0  80   0 -  2204 -      ?        00:00:00 console-kit-dae
1 S     0  2250     1  0  80   0 -  1276 -      ?        00:00:00 crond
5 S     0  2258     1  0  80   0 -   522 -      ?        00:00:00 atd
5 S   498  2268     1  0  80   0 -   676 -      ?        00:00:00 avahi-daemon
1 S   498  2269  2268  0  80   0 -   676 -      ?        00:00:00 avahi-daemon
5 S     0  2286     1  0  80   0 -  2481 -      ?        00:00:00 cupsd
5 S    68  2295     1  0  80   0 -  1469 -      ?        00:00:08 hald
0 S     0  2296  2295  0  80   0 -   824 -      ?        00:00:00 hald-runner
1 S     0  2310     1  0  99  19 -  5430 -      ?        00:00:02 yum-updatesd
0 S     0  2311  2296  0  80   0 -   849 -      ?        00:00:00 hald-addon-inpu
0 S     0  2314     1  0  99  19 -   708 -      ?        00:00:02 gam_server
4 S    68  2332  2296  0  80   0 -   539 -      ?        00:00:00 hald-addon-acpi
0 S     0  2366  2296  0  80   0 -   849 -      ?        00:01:54 hald-addon-stor
0 S     0  2369  2296  0  80   0 -   849 -      ?        00:01:36 hald-addon-stor
4 S     0  2436     1  0  80   0 -   436 -      tty1     00:00:00 mingetty
4 S     0  2437     1  0  80   0 -   436 -      tty2     00:00:00 mingetty
4 S     0  2438     1  0  80   0 -   436 -      tty3     00:00:00 mingetty
4 S     0  2439     1  0  80   0 -   436 -      tty4     00:00:00 mingetty
4 S     0  2440     1  0  80   0 -   436 -      tty5     00:00:00 mingetty
4 S     0  2441     1  0  80   0 -   436 -      tty6     00:00:00 mingetty
4 S     0  2442     1  0  80   0 -  4561 -      ?        00:00:00 gdm-binary
5 S     0  2520  2442  0  80   0 -  4248 -      ?        00:00:00 gdm-binary
1 S     0  2524     1  0  80   0 -  4561 -      ?        00:00:22 gdm-binary
4 S     0  2525  2520  0  80   0 - 43273 -      tty7     00:43:55 X
1 S   500  2610     1  0  80   0 -  3585 -      ?        00:00:00 gnome-keyring-d
4 S   500  2611  2520  0  80   0 -  1164 -      ?        00:00:00 startkde
1 S   500  2641  2611  0  80   0 -  1384 -      ?        00:00:02 ssh-agent
1 S   500  2676     1  0  80   0 -   738 -      ?        00:00:00 dbus-launch
1 S   500  2677     1  0  80   0 -  3235 -      ?        00:00:00 dbus-daemon
1 S   500  2697     1  0  80   0 -  1513 -      ?        00:00:00 gnome-keyring-d
1 S   500  2700     1  0  80   0 -  1154 -      ?        00:00:39 gpg-agent
1 S   500  2704     1  0  80   0 -  8455 -      ?        00:15:31 pulseaudio
0 S   500  2707  2704  0  80   0 -  1311 -      ?        00:00:00 gconf-helper
1 S   500  2725     1  0  80   0 -   401 -      ?        00:00:00 start_kdeinit
1 S   500  2726     1  0  80   0 -  7191 -      ?        00:00:00 kdeinit
1 S   500  2729     1  0  80   0 -  4431 -      ?        00:00:15 dcopserver
1 S   500  2731  2726  0  80   0 -  7508 -      ?        00:00:08 klauncher
1 S   500  2733     1  0  80   0 -  9399 -      ?        00:00:31 kded
0 S   500  2738  2611  0  80   0 -   435 -      ?        00:00:01 kwrapper
0 S   500  2740     1  0  80   0 -  6213 -      ?        00:00:01 ksmserver
0 S   500  2741  2726  0  80   0 -  6915 -      ?        00:00:38 kwin
1 S   500  2743     1  0  80   0 - 10988 -      ?        00:02:06 kdesktop
1 S   500  2748     1  0  80   0 -  9189 -      ?        00:01:04 kicker
0 S   500  2755  2726  0  80   0 -  9216 -      ?        00:04:34 artsd
1 S   500  2757     1  0  80   0 -  6180 -      ?        00:00:01 kaccess
0 S   500  2760  2726  0  80   0 -  8986 -      ?        00:00:01 puplet
0 S   500  2761  2726  0  80   0 - 12709 -      ?        00:00:00 nm-applet
1 S   500  2766     1  0  80   0 -  7304 -      ?        00:01:32 klipper
0 S   500  2773     1  0  80   0 - 10386 -      ?        00:00:00 /usr/bin/sealer
1 S   500  2775     1  0  80   0 -  7872 -      ?        00:00:01 kpowersave
0 S   500  2871     1  0  80   0 - 10861 -      ?        00:00:06 notification-da
1 S   500 10790  2726  0  80   0 -  7545 -      ?        00:00:00 kio_file
0 S   500 11681     1  0  80   0 -  2850 -      ?        00:00:00 gnome-vfs-daemo
0 S   500 11687     1  0  80   0 - 18973 -      ?        00:52:05 gnome-settings-
1 S   500 11729     1  0  80   0 -  4318 -      ?        00:00:32 gnome-screensav
0 S   500 13790     1  0  80   0 -   675 -      ?        00:00:00 gam_server
0 S     0 19598  2296  0  80   0 -   849 -      ?        00:00:18 hald-addon-stor
5 S     0 19781     1  0  76  -4 -  3318 -      ?        00:00:07 auditd
0 S     0 19783 19781  0  76  -4 -  3297 -      ?        00:00:03 audispd
1 S   500 19798     1  0  80   0 -  7553 -      ?        00:00:00 kio_uiserver
1 S     0 22591     2  0  80   0 -     0 -      ?        00:00:00 pdflush
1 S     0 22637     2  0  80   0 -     0 -      ?        00:00:00 pdflush
1 S   500 22962     1  0  80   0 -  8948 -      ?        00:00:21 knotify
0 S   500 25277     1  0  80   0 -  1898 -      ?        00:00:00 gconfd-2

-- 
Michael   hennebry(a)web.cs.ndsu.NoDak.edu
"Those parts of the system that you can hit with a hammer (not advised)
are called Hardware;  those program instructions that you can only
curse at are called Software."

[g]

>  Michael Hennebry wrote:
>  What is an sel level? 
SELinux

>  hennebry as usual.
>  yes, no, no. 
was if you had any type of 'file recovery' running'.

>  [hennebry@localhost ~]$ find . -newer tstamp.fn -print -exec ls -ld
> \; > hold.list
>  [hennebry@localhost ~]$ cat hold.list 
>  drwx------ 55 hennebry hennebry 4096 2008-06-07 09:31 .
>  ./.kde/share/config/kdesktoprc 
strange way 'kdesktoprc' is shown, being i have it as a file, not a directory.

anyway, my 'kdesktoprc', sleep enabled and lock disabled shows;

   [ScreenSaver]
   Lock=false
   Saver=KSlideshow.desktop
   Timeout=480

w/ lock enabled;

   [ScreenSaver]
   Saver=KSlideshow.desktop
   Timeout=480

where 'lock=' went, do not know. may be else where with 'display power
off'.
not sure of where it would be tied in, and need 'find /'. being that it is thru
'control center', setup file could be among /etc or /usr.

>  I think something else is demanding a password. 
maybe. 'ps -el|less' to see what else is running.

>  Whatever it is is taking more than 5 minutes to blank the screen.
>  The screensaver is set for an animation. 
nft.

if no one comes up with solution, you could always 'mv .kde .kde.bad'
and run 'startx' again.

yes, i know, re-config kde. but what the heck, it might cure things.
at least you will still have desktop icons. scattered, but there.  :o)

there is always loading source and reading a bunch c files.  :o(


loads of luck and perseverance.


-- 

tc,hago.

g
.

in a free world with out fences, who needs gates...

[Michael Hennebry]

On Sat, 7 Jun 2008, g wrote:

>  Michael Hennebry wrote:
>  > Alas, I wrote too soon.
>  > It seems to have worked just once.
>
>  what sel level? as which user? during same session? x restart? reboot? 
What is an sel level?
hennebry as usual.
yes, no, no.

>  think about this;
>
>  from a term,
>    ~]$ touch tstamp.fn
>
>  run control center, then from a term,
>    ~]$ find . -newer tstamp.fn -print -exec `ls -l` >> hold.list
>  should give you kde files with configs. i would tell you if i knew.
>  file is for compare later when you do what ever you do and you are
>  back where you where. 
[hennebry@localhost ~]$ find . -newer tstamp.fn -print -exec ls -ld \; > hold.list
[hennebry@localhost ~]$ cat hold.list
.
drwx------ 55 hennebry hennebry 4096 2008-06-07 09:31 .
./hold.list
drwx------ 55 hennebry hennebry 4096 2008-06-07 09:31 .
./.kde/share/config
drwx------ 55 hennebry hennebry 4096 2008-06-07 09:31 .
./.kde/share/config/kcontrolrc
drwx------ 55 hennebry hennebry 4096 2008-06-07 09:31 .
./.kde/share/config/kdeglobals
drwx------ 55 hennebry hennebry 4096 2008-06-07 09:31 .
./.kde/share/config/kdesktoprc
drwx------ 55 hennebry hennebry 4096 2008-06-07 09:31 .
./.kde/share/config/kickerrc
drwx------ 55 hennebry hennebry 4096 2008-06-07 09:31 .

I think something else is demanding a password.
Whatever it is is taking more than 5 minutes to blank the screen.
The screensaver is set for an animation.

-- 
Michael   hennebry(a)web.cs.ndsu.NoDak.edu
"Those parts of the system that you can hit with a hammer (not advised)
are called Hardware;  those program instructions that you can only
curse at are called Software."

[g]

Michael Hennebry wrote:
>  Alas, I wrote too soon.
>  It seems to have worked just once. 
what sel level? as which user? during same session? x restart? reboot?

think about this;

from a term,
  ~]$ touch tstamp.fn

run control center, then from a term,
  ~]$ find . -newer tstamp.fn -print -exec `ls -l` >> hold.list
should give you kde files with configs. i would tell you if i knew.
file is for compare later when you do what ever you do and you are
back where you where.

unless some one knows a reason, or better approach.


later.

--

tc,hago.

g
.

in a free world without fences, who needs gates.

[Michael Hennebry]

On Fri, 6 Jun 2008, g wrote:

>  Michael Hennebry wrote:
>  > Thanks.
>
>  you are welcome. glad you got things to work for you.
>
>  > I'd found the spot before, but coudn't get it to work.
>  > 'Require password to stop' wasn't xed, but it was grayed out.
>  > xing 'Start automatically' eliminated the need for a password.
>
>  interesting. "xing 'Start automatically'" is among 1st in my initial
> setup
>  of kde. i like to blank crt. was not aware of effect if password not xed.
>
>  live and learn, die and forget.
>
>  thanks for info. 
Alas, I wrote too soon.
It seems to have worked just once.
It starts automatically whether or not 'Start automatically' is xed.
It wants a password whether or not 'Require password to stop' is xed.

Perhaps I need a background job to nuke
the screensaver whenever it shows up.

-- 
Michael   hennebry(a)web.cs.ndsu.NoDak.edu
"Those parts of the system that you can hit with a hammer (not advised)
are called Hardware;  those program instructions that you can only
curse at are called Software."

[Michael Hennebry]

On Fri, 6 Jun 2008, g wrote:

>  Michael Hennebry wrote:
>  > I recently installed FC8 and  haven't been able to find
>  > the incantation to tell FC8 and KDE not to lock my screen.
>  >
>  > How do I tell them not to lock my screen?
>  >
>
>  bring up kde 'control center', click '[+] appearance & themes',
> click
>  'screen saver', click '[x] require password to stop', leaving,
>  '[ ] require password to stop'.
>
>  should do it. 
Thanks.
I'd found the spot before, but coudn't get it to work.
'Require password to stop' wasn't xed, but it was grayed out.
xing 'Start automatically' eliminated the need for a password.

-- 
Michael   hennebry(a)web.cs.ndsu.NoDak.edu
"Those parts of the system that you can hit with a hammer (not advised)
are called Hardware;  those program instructions that you can only
curse at are called Software."

[g]

Michael Hennebry wrote:
>  I recently installed FC8 and  haven't been able to find
>  the incantation to tell FC8 and KDE not to lock my screen.
>  
>  How do I tell them not to lock my screen?
>   
bring up kde 'control center', click '[+] appearance & themes', click
'screen saver', click '[x] require password to stop', leaving,
'[ ] require password to stop'.

should do it.


-- 


tc,hago.

g
.

in a free world without fences, who needs gates.

[g]

Michael Hennebry wrote:
>  I got around to trying 1 and 2, but no joy.
>  After exiting X, I did notice window manager complaints.
>  I kind of fuzzy on what they were. 
i have yet to close kde and not have a bunch of errors show. most of them are
'error: bad window', but all windows were ok and i just dismiss them.

>  Possibly they were the result of trying to run a gnome desktop
> without gnome.
>  IIRC I didn't clickon gnome during install. 
fedora has gnome as default desktop. to disable gnome, you must unselect it,
as well as you must select kde.

> > 3) r & r kde.
>  
>  I don't know how to r & r KDE or anything else.
>  I presume it doesn't mean rest and recreate. 
no.

>  seaRch and destRoy? 
closer. remove and replace.

it is possible that something was wrong in original install. this is why when
i note problems in a new install, i consider that if there is 1 or 2 problems
that i see, there could be more. so i will do a complete new install. usually
this will fix problems. if not, i install again, but leave out a lot of
manual selections for later if install looks good.


-- 

tc,hago.

g
.

in a free world without fences, who needs gates.

[Michael Hennebry]

On Mon, 9 Jun 2008, g wrote:

>  Michael Hennebry wrote:
>  > I did an experiment.
>  <snip>
>  > Eventually something else blanked the screen and wanted my password.
>
>  2 good reasons for what i have 4 suggestions.
>
>  1a) if not already level 3, change '/etc/inittab' to *id:3:initdefault:*,
> reboot.
>  1b) in 'level 3';
>
>    >$ mv .kde .kde.old
>    >$ startx
>
>  if still,
>  2) add another user, login as, if continues, #3. 
I got around to trying 1 and 2, but no joy.
After exiting X, I did notice window manager complaints.
I kind of fuzzy on what they were.
Possibly they were the result of trying to run a gnome desktop without gnome.
IIRC I didn't clickon gnome during install.
I tried grepping /var/log/* , but didn't find the complaints.

>  3) r & r kde. 
I don't know how to r & r KDE or anything else.
I presume it doesn't mean rest and recreate.
seaRch and destRoy?

>  4) someone else this list |  kde 'tech list' | read source.
>
>  i have tried to dupe problem, unable.
>
>  i have 'touch', 'find', 'grep' and not found any files that give
> clue. 'flag' for
>  screen password lock may be in a 'power save' file, even a display manager.
>
>  if it where a problem i had, i would have r & r kde long ago. whole install,
>  maybe. for sure if i found 'bug' early. 
-- 
Michael   hennebry(a)web.cs.ndsu.NoDak.edu
"Those parts of the system that you can hit with a hammer (not advised)
are called Hardware;  those program instructions that you can only
curse at are called Software."

[g]

Michael Hennebry wrote:
>  I did an experiment. 
<snip>
>  Eventually something else blanked the screen and wanted my password.
2 good reasons for what i have 4 suggestions.

1a) if not already level 3, change '/etc/inittab' to *id:3:initdefault:*, reboot.
1b) in 'level 3';

> $ mv .kde .kde.old
> $ startx 
if still,
2) add another user, login as, if continues, #3.
3) r & r kde.
4) someone else this list |  kde 'tech list' | read source.

i have tried to dupe problem, unable.

i have 'touch', 'find', 'grep' and not found any files that give
clue. 'flag' for
screen password lock may be in a 'power save' file, even a display manager.

if it where a problem i had, i would have r & r kde long ago. whole install,
maybe. for sure if i found 'bug' early.

good luck with venture.


--

tc,hago.

g
.

in a free world with out fences, who needs gates...

[g]

Michael Hennebry wrote:
>  On Sat, 7 Jun 2008, g wrote: 
> > nft. 
>  Not for tourists? 
no telling.

>  interesting times.
>  
>  F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTY          TIME CMD
>  4 S     0     1     0  0  80   0 -   528 -      ?        00:00:13 init 
so are all of these. but no clue.


as in next post, 1 - 2 - 3 - 4...


--

tc,hago.

g
.

in a free world with out fences, who needs gates...

[Michael Hennebry]

I did an experiment.
I used the gui to tell the screensaver to turn one after 1 min.
It worked once.
The next time the screensaver animation didn't come on.
Eventually something else blanked the screen and wanted my password.

-- 
Michael   hennebry(a)web.cs.ndsu.NoDak.edu
"Those parts of the system that you can hit with a hammer (not advised)
are called Hardware;  those program instructions that you can only
curse at are called Software."