**** BEGIN LOGGING AT Sat Apr 04 03:00:20 2020
Apr 04 03:00:26 <set_> Nice.
Apr 04 03:00:37 <set_> Django is beating me senseless.
Apr 04 03:00:49 <set_> My ole, one-two is beaten.
Apr 04 03:00:51 <zmatt> KenUnix: I guess no way to connect the beaglebone via ethernet to your router?
Apr 04 03:00:53 <set_> brb
Apr 04 03:01:45 <KenUnix> don't have router. it's ethernet USB or wifi (which sucks)
Apr 04 03:01:56 <zmatt> what does your wifi connect to?
Apr 04 03:02:11 <KenUnix> Comcast
Apr 04 03:02:43 <zmatt> ... it's not like comcast internet descends from the heaven onto your building
Apr 04 03:03:12 <zmatt> there'll be a router that's also the wifi access point, typically
Apr 04 03:03:37 <zmatt> but it sounds like it's not something you can access, so that won't help
Apr 04 03:03:50 <KenUnix> BBB wifi likes to go up/down several times a day. Oh wifi on PC is fast. Yes routers and repeaters here
Apr 04 03:04:10 <zmatt> oh right you tried using some wifi stick
Apr 04 03:04:25 <KenUnix> RTL8188EUS
Apr 04 03:04:47 <zmatt> yeah sounds like it's one that uses a crappy out-of-tree driver
Apr 04 03:05:07 <zmatt> wifi usb sticks on linux tend to be kinda.... hit or miss
Apr 04 03:05:29 <zmatt> (and they also don't have great reception typically)
Apr 04 03:05:31 <KenUnix> Well RCN said with debian 10.3 it was pretty current
Apr 04 03:06:13 <KenUnix> Repeater only about 25' fro here
Apr 04 03:06:36 <zmatt> current or not, pretty sure it's still a crappy out-of-tree driver :P
Apr 04 03:07:28 <KenUnix> OK. Is there a good with build in or loadable drivers? USB based.
Apr 04 03:08:13 <zmatt> if I google "RTL8188EUS linux" the entire page of first results consists of people trying to install drivers for it or saying it doesn't work
Apr 04 03:08:44 <KenUnix> Well it works most of the time
Apr 04 03:09:34 <zmatt> there are, but it's often hard to know which ones will work well before buying and trying... people have noticed that you can even have two sticks that look identical and are sold under the same product name / model number, yet have different wifi chips inside where one works well on linux and the other doesn't
Apr 04 03:10:01 <KenUnix> I have a RTL8188EUS with external antenna. maybe that will help
Apr 04 03:10:14 <zmatt> (because the manufacturer switched wifi chip and didn't feel like that change was relevant enough to change their model number)
Apr 04 03:10:20 <KenUnix> I have a RTL8188EUS on order with external antenna. maybe that will help
Apr 04 03:10:42 <zmatt> if reception is the issue, it might
Apr 04 03:10:51 <zmatt> *it should
Apr 04 03:11:02 <zmatt> if the driver is the issue then it probably won't ;)
Apr 04 03:12:16 <KenUnix> syslog complains about about  "disassocation"
Apr 04 03:14:41 <KenUnix> Oh no now log has  /sbin/crda  what is that
Apr 04 03:15:19 <KenUnix> Apr  3 23:00:25 beaglebone systemd-udevd[862]: Process '/sbin/crda' failed with exit code 249.
Apr 04 03:18:20 <KenUnix> I have had enough fun for one night
Apr 04 03:18:50 <KenUnix> Give na a DEC PDP-11/20 or an HP D9000 server.
Apr 04 03:19:33 <KenUnix> Give me a DEC PDP-11/70 or an HP D9000 server.
Apr 04 03:20:07 <KenUnix> Things were easier then
Apr 04 03:21:30 <KenUnix> Back then a 20  drive raid array was sweet
Apr 04 03:22:47 <KenUnix> I ran 4 HP D330 servers and mucho desktop pc's
Apr 04 03:23:08 <KenUnix> good night
Apr 04 03:31:14 <MattB0ne> is there a easy way to move an install to a larger hard drive
Apr 04 08:20:57 <deepankarmaithan> Hello i am studying the PRUs. I came across  some documents explaining the communication between the PRU and main linux processor using PRU-ICSS and  in some other places this is implemented using remotproc.  Can any one explain what would be the downside  and advantages of one over other
Apr 04 08:27:50 <zmatt> you mean "using uio-pruss" I assume?  since PRU-ICSS is just the name of the subsystem
Apr 04 08:28:02 <deepankarmaithan> Actually i am  trying to make a cape for beaglebone (probably for pocket beagle)  where i can extend the i/o  using a  univesal shift register. and can make a cape  on which there will be a small Nokia 3110 LCD or OLED  and some buttons.  May be this can be useful in products that require alot of i/o  and need to display some data in the field. Lets say on a quardcopter , i need to configure PID values , or a i/o node
Apr 04 08:28:02 <deepankarmaithan> that control irrigation valves and need  some basic info readily avialable on the display. As jkridner  shared with me   i am following  this link https://elinux.org/BeagleBoard/GSoC/2019Proposal/GPIOParallelBidirComm    . I would like to hear  from the community. What do you think about such a cape/shield
Apr 04 08:28:15 <deepankarmaithan> <zmatt "you mean "using uio-pruss" I ass"> yes
Apr 04 08:28:28 <zmatt> ... wall of text
Apr 04 08:30:07 <zmatt> anyway, uio-pruss is older and works stably across pretty much all kernel versions without any significant changes.  it just allows pruss to be mapped entirely into userspace, hence program loading is done there by a library.  it supports shared memory and direct introspection and manipulation of the pru cores
Apr 04 08:31:29 <deepankarmaithan> sorry for the wall of text - I was not aware if that is something frawned upon   :P. wil take care in future
Apr 04 08:32:06 <zmatt> remoteproc-pru is newer, has had the annoying tendency of being (incompatibly) different in each major kernel version (dunno if it's finally stabilized yet), and tbh it's mostly just more limited than uio-pruss.  with remoteproc-pru the kernel performs program loading, and it only supports ELF executables (as produced by clpru) hence it doesn't support executables produced by pasm
Apr 04 08:32:19 <zmatt> it's not really frowned upon, it just takes a bit to read :P
Apr 04 08:33:14 <deepankarmaithan> ok thanks for your valuable inside. will help in my development.
Apr 04 08:33:20 <zmatt> for uio-pruss since program loading is done in userspace, it's up to software what type of executables can be loaded.  the old libprussdrv only supports raw binaries as produced by pasm, while my py-uio python library supports both raw binaries and ELF executables
Apr 04 08:34:32 <zmatt> remoteproc is often used in combination with the C compiler and rpmsg, both of which mostly demolish the benefits of PRU in my opinion
Apr 04 08:35:32 <deepankarmaithan> Actually i am trying to write software for PRU in C. DO you think uio-pruss would be suitable?
Apr 04 08:36:14 <zmatt> I just answered that
Apr 04 08:37:40 <deepankarmaithan> okay thanks 🙂
Apr 04 08:37:41 <zmatt> the C compiler produces ELF executables hence you can't load these with libprussdrv (unless you'd write a tiny ELF loader yourself, which actually isn't that hard but still) though my py-uio library can load them
Apr 04 08:38:05 <zmatt> (making a better C/C++ library for uio-pruss something I still want to do, I just haven't gotten around to it)
Apr 04 08:38:58 <deepankarmaithan> ok i will research more on this and will update if i will find it.   Can you please share the link of your py-uio libarary
Apr 04 08:39:54 <zmatt> just curious... if performance doesn't really matter much in your case (since you're intending to use the C compiler), why use PRU at all?
Apr 04 08:40:00 <zmatt> https://github.com/mvduin/py-uio
Apr 04 08:40:38 <zmatt> also, why not just use an i2c gpio extender?
Apr 04 08:42:29 <zmatt> I guess pru + shift register can definitely perform better, even with C code
Apr 04 08:42:34 <deepankarmaithan> Because i think it would still  be better than  doing it from the linux space and  creating a hardware cape that somebody can  work on with assembly if he/she wants more performance.
Apr 04 08:44:06 <zmatt> well thing is, the main reason to use this is if you're running low on built-in gpios, which probably means that most pins will already be in use by that person for various reasons... which also means that *they* would want to pick which pins are being used for this, which isn't an option if this is made as a cape
Apr 04 08:44:17 <deepankarmaithan> <zmatt "https://github.com/mvduin/py-uio"> thanks for the link
Apr 04 08:45:55 <zmatt> also the modes shown in the those pocketbeagle overviews are just the default modes, nearly all pins can be used as gpio
Apr 04 08:46:40 <zmatt> (and the diagram for the beaglebone isn't even showing default pinmux, I don't know what it's showing)
Apr 04 08:48:06 <zmatt> 45 of the pocketbeagle's pins can be used as gpios
Apr 04 08:49:57 <zmatt> here's an overview of the pocketbeagle's pinmux options, with default modes highlighted in yellow: https://docs.google.com/spreadsheets/d/e/2PACX-1vSlUrBqn1M8obS5eUt1ky7igWEVsqoMstwLifkkBKHGS4s23VqLOodQAyctcCAz-3WEDP2J4_-dJGIS/pubhtml?gid=547449216&single=true
Apr 04 08:50:01 <deepankarmaithan> As i understand it is that only few pins can be used as PRU inputs. But with cape  with shift register which is controlled using few pins with dedicated PRU functionality the ability of PRU to take inputs will increase. I may be wrong on this
Apr 04 08:50:28 <deepankarmaithan> <zmatt "here's an overview of the pocket"> ok i will go through it
Apr 04 08:53:05 <zmatt> yeah, 20 pins are pru inputs (or 22 if you include edio)
Apr 04 08:53:40 <zmatt> but it can also access the gpio controller, and reading gpios via that is faster than reading them via a shift register
Apr 04 08:54:12 <zmatt> ... I think
Apr 04 08:55:27 <deepankarmaithan> i have one more question, is it possible to put the main processor to sleep and do something on PRU and wake the main processor at certain interval?
Apr 04 08:55:44 <zmatt> yeah pru can sends interrupts to the arm processor
Apr 04 08:55:50 <zmatt> py-uio has an example for that
Apr 04 08:55:52 <zmatt> two even
Apr 04 08:58:11 <zmatt> btw that overview tab can be found in my pins spreadsheet, which contains lots more data about the am335x, the beaglebone black, and some info on the beaglebone blue and pocketbeagle: https://goo.gl/Jkcg0w
Apr 04 08:58:47 <zmatt> (the P9/P8 tabs are the most useful for the beaglebone black)
Apr 04 09:01:07 <deepankarmaithan> Okay then may be a senario where i need to save power and  have a cape ( with eink probably) that displays most important info and wakes up the main processor when filesystem is needed or a networking is needed. Also as i can see if i have several other sensors on a i2c bus may be  i2c gpio extender can be problematic. i donot kow never did a gpio extender on i2c. I will explore the possibilities
Apr 04 18:35:25 <MattB0ne> Hello Hello
Apr 04 18:35:34 <MattB0ne> I have a compiler questions for the gallary
Apr 04 18:35:45 <MattB0ne> why the hell wont this make script find these header files
Apr 04 18:36:28 <MattB0ne> https://pastebin.com/WuBMTGpF
Apr 04 18:36:56 <MattB0ne> i can search for them so they are on my system but this configure sript never finds them
Apr 04 18:36:59 <MattB0ne> stumped
Apr 04 18:43:47 <MattB0ne> also do I need to do a clean before running a configure again?
Apr 04 18:48:19 <zmatt> looks like it's trying to find a package via pkg-config but it can't find it
Apr 04 18:49:05 <zmatt> and no you don't need to clean anything before running configure again (generally you can't even, since configure is responsible to generating the makefile)
Apr 04 18:49:47 <zmatt> oh never mind I see now the situation is more subtle
Apr 04 18:50:20 <zmatt> what are you doing anyway, what are these weird qt5 paths?
Apr 04 18:51:24 <MattB0ne> building qt5 from source
Apr 04 18:51:29 <MattB0ne> I just want to slog through it once
Apr 04 18:51:30 <zmatt> why?
Apr 04 18:51:35 <MattB0ne> i am not cross building
Apr 04 18:51:39 <zmatt> ok
Apr 04 18:51:45 <MattB0ne> to learn make and troubleshooting
Apr 04 18:51:46 <zmatt> well, it doesn't seem to be going well ;)
Apr 04 18:51:50 <MattB0ne> lol
Apr 04 18:52:02 <MattB0ne> you learn more from these disasters
Apr 04 18:52:02 <zmatt> qt5 doesn't sound like the best thing to start with to learn make :D
Apr 04 18:52:30 <MattB0ne> probably not though I did notice if I update the make file testing this package
Apr 04 18:52:37 <MattB0ne> I do not notice an update on the rerun
Apr 04 18:52:49 <MattB0ne> so I tried to fix this error by putting /usr/include
Apr 04 18:52:55 <MattB0ne> in the compiler settings
Apr 04 18:53:00 <zmatt> uhhhh
Apr 04 18:53:02 <MattB0ne> but it does not show up on the rerun
Apr 04 18:53:06 <zmatt> ah
Apr 04 18:53:07 <zmatt> yeah
Apr 04 18:53:30 <MattB0ne> -I. -I/home/mastermind/qt5/qt-everywhere-src-5.14.2/qtbase/mkspecs/linux-g++ -I/usr/include
Apr 04 18:53:39 <zmatt> -I/usr/include is nonsense
Apr 04 18:53:44 <MattB0ne> lol
Apr 04 18:53:45 <zmatt> it's part of the default search path
Apr 04 18:53:58 <zmatt> ditto -I.
Apr 04 18:54:10 <zmatt> (pretty sure)
Apr 04 18:54:10 <MattB0ne> i fiigured that but I confirmed that the file is in that directory
Apr 04 18:54:15 <MattB0ne> that is why I am puzzled
Apr 04 18:54:32 <MattB0ne> i can see it by manually browsing
Apr 04 18:54:41 <MattB0ne> those /usr/include is not in my $PATH
Apr 04 18:54:45 <MattB0ne> variable
Apr 04 18:54:51 <zmatt> $PATH is where executables live, not headers
Apr 04 18:55:08 <MattB0ne> I tried making a CPLUS_INCLUDE_PATH
Apr 04 18:55:12 <MattB0ne> exported that
Apr 04 18:55:15 <MattB0ne> still no dice
Apr 04 18:55:23 <MattB0ne>  there is some big concept or error i am making
Apr 04 18:55:38 <MattB0ne> i just want to clear one of these and I will go take a walk
Apr 04 18:55:42 <zmatt> this sounds like something is horribly horribly borked, but I honestly can't even guess what
Apr 04 18:55:50 <MattB0ne> hmmmm
Apr 04 18:55:50 <MattB0ne> ok
Apr 04 18:56:28 <MattB0ne> generally building from source is not painful right
Apr 04 18:56:36 <zmatt> usually not no
Apr 04 18:56:45 <MattB0ne> or this is something you should get good at
Apr 04 18:57:02 <zmatt> no, most commonly things simply build
Apr 04 19:02:03 <zmatt> you can print the include search path using:
Apr 04 19:02:05 <zmatt> `g++ -print-prog-name=cc1plus` -v
Apr 04 19:02:19 <zmatt> (this command will hang on input after printing the path, just cancel it with control-C)
Apr 04 19:03:13 <zmatt> you can add the various -I options to it to get those reflected in the output
Apr 04 19:03:36 <MattB0ne> ok
Apr 04 19:03:41 <MattB0ne> will play around with it
Apr 04 19:04:13 <MattB0ne> somthing is fishy though I literally deleted the file and it still spit back out that same error
Apr 04 19:04:29 <MattB0ne> its like my configure was cached or something
Apr 04 19:04:34 <MattB0ne> doesnt want to run anything
Apr 04 19:04:45 <MattB0ne> or maybe skips compiling?
Apr 04 19:04:47 <MattB0ne> i dunno
Apr 04 19:04:56 <zmatt> ?
Apr 04 19:05:02 <zmatt> deleted what file?
Apr 04 19:09:18 <zmatt> you could also try confirming that if you run the same g++ command as it claims to be running in the same directory (config.tests/speechd) that it gives the same error, and if so it might be informative to run it with   strace -f -e trace=file -o strace.log g++ (..etc..)  to see if the strace log is enlightening at all
Apr 04 19:20:09 <MattB0ne> good point
Apr 04 19:20:12 <MattB0ne> let me check
Apr 05 01:02:26 <KenUnix> Good evening. I've loaded Ubuntu Focal 20.04 but I can't keep the screen saver from kicking. This is what I used:
Apr 05 01:02:30 <KenUnix> org.gnome.desktop.session idle-delay 240
Apr 05 01:03:30 <KenUnix> org.gnome.desktop.session idle-delay 240 <== no matter what number I use it kicks in in 5 minutes
Apr 05 01:10:31 <set_> Do it!
Apr 05 01:10:45 <set_> Kick the screen saver totally.
Apr 05 01:11:45 <set_> What does a 50' cam w/ app get you?
Apr 05 01:11:51 <set_> Sewer inspection!
Apr 05 01:12:32 <set_> I got my auger cabling and it is time to wire this cam into the cabling.
Apr 05 01:13:27 <KenUnix> OK. How do you kick it??????????????:b :b
Apr 05 01:14:25 <KenUnix> I'll be back. I'm upgrading Linux Lite 4.6
Apr 05 01:15:21 <set_> Okay, so when you set up your distro, choose to pick which and what packages are available.
Apr 05 01:15:36 <set_> Let me see what that one is called in gnome.
Apr 05 01:18:26 <set_> https://help.gnome.org/admin/gdm/ means over my head, really. That is an entire book of ideas for gnome gdm.
Apr 05 01:20:19 <set_> Which display manager are you working w/? What exact version?
Apr 05 01:21:26 <KenUnix> Focal is Mate
Apr 05 01:24:08 <set_> https://help.gnome.org/admin/gdm/3.26/configuration.html.en is the gdm gnome set up config. page.
Apr 05 01:24:19 <set_> So, what should we look for in this text?
Apr 05 01:24:44 <set_> Not mate, for sure. But, maybe something else.
Apr 05 01:25:17 <set_> Like...homescreen, lockscreen, screensaver?
Apr 05 01:25:23 <set_> Let me see.
Apr 05 01:26:00 <KenUnix> disable screen saver
Apr 05 01:26:11 <set_> .desktop is a dir. or not?
Apr 05 01:26:18 <set_> Oh.
Apr 05 01:26:21 <set_> You cannot even sign in.
Apr 05 01:26:25 <set_> Yikes.
Apr 05 01:27:22 <set_> I found info. but it is only viable if you can sign in. Dang man, wait for someone else. Sorry.
Apr 05 01:29:08 <set_> KenUnix: Do you know anything about grub?
Apr 05 01:29:45 <set_> Another long book, yikes!
Apr 05 01:31:32 <set_> Do you have time to set up a kernel and trouble shoot?
Apr 05 01:40:11 <set_> I just remember, "back in the day," Linux Distros were done and set up but in a way that made the "user" get fully integrated in the kernel set up.
Apr 05 01:40:25 <set_> It was not just click and done.
Apr 05 01:42:55 <set_> Linux kernel set up is so easy now, no one knows exactly what they are doing unless they dive into grub/grub2.
Apr 05 01:44:25 <KenUnix> .desktop is a directory that contains launcher  xx.desktop file which is properly setup will appear on te Desktop of the main window. I try and avoid grug. Screw that up and there goes your harddrive for booting.
Apr 05 01:44:39 <set_> Okay.
Apr 05 01:44:47 <set_> So, you CAN get into your OS?
Apr 05 01:44:57 <set_> But only for five minutes?
Apr 05 01:45:16 <KenUnix> Oh yes I just want to disable the screen saver
Apr 05 01:45:25 <set_> I was misunderstanding what you were typing earlier.
Apr 05 01:45:36 <set_> Oh.
Apr 05 01:45:36 <set_> !
Apr 05 01:45:57 <set_> Are you using GUI or commandline?
Apr 05 01:47:41 <set_> Usually: -> settings -> power
Apr 05 01:47:52 <KenUnix> Back to the dist-upgrade . Waiting for expansion headers for BBB so they raise the relay cape allowing me to still use the 6 pin console eader. No GUI come up at startup.
Apr 05 01:48:26 <set_> Okay. So, we need to use the command line. Okay. Let me goof around and see what I can find.
Apr 05 01:48:44 <KenUnix> org.gnome.desktop.session idle-delay 240 <== no matter what number I use it kicks in in 5 minutes
Apr 05 01:49:09 <set_> lock.enabled false or something.
Apr 05 01:49:15 <set_> So...
Apr 05 01:49:42 <set_> org.gnome.desktop.session lock-enabled false
Apr 05 01:49:45 <set_> Try that.
Apr 05 01:49:58 <KenUnix> command line : gsettings set org.gnome.desktop.session idle-delay 240
Apr 05 01:50:10 <set_> Hmm.
Apr 05 01:50:13 <set_> Who said that?
Apr 05 01:50:44 <set_> I just looked online. Are you using a Debian based systemd OS?
Apr 05 01:51:02 <KenUnix> Tried lock-enabled false don't work
Apr 05 01:51:20 <set_> Hmm. Try what you typed w/ lock-enabled false
Apr 05 01:51:25 <set_> So...
Apr 05 01:51:30 <KenUnix> Ubuntu Focal Mate 20.04
Apr 05 01:51:51 <set_> gsettings set .org.gnome.desktop.session lock-enabled false
Apr 05 01:52:23 <set_> Dang it.
Apr 05 01:52:42 <KenUnix> That won't work I did get the requirement for pasword to work for 240 minutes
Apr 05 01:52:52 <set_> Hmm.
Apr 05 01:52:56 <set_> Okay.
Apr 05 01:53:23 <KenUnix> gsettings set org.gnome.desktop.screensaver lock-delay 240
Apr 05 01:53:27 <set_> So, your command line is not working b/c of a known password that only works for 240 minutes.
Apr 05 01:53:45 <set_> false
Apr 05 01:53:50 <set_> Not 240!
Apr 05 01:53:58 <set_> I thought you wanted to remove your screensaver?
Apr 05 01:54:34 <KenUnix> by default the screen goes into screen saver mode and requires you password again after 5 idle minutes
Apr 05 01:54:44 <set_> xset s off
Apr 05 01:55:07 <set_> Let me try.
Apr 05 01:55:12 <set_> Sheesh. I am going blind here.
Apr 05 01:55:33 <KenUnix> Can't try now. dist-upgrade is still running
Apr 05 01:56:15 <set_> Okay. I am turning on my linux machine.
Apr 05 01:56:27 <set_> I will attempt everything I find and get back to you.
Apr 05 02:00:00 <set_> lock screen or screen saver?
Apr 05 02:00:11 <set_> I found there is a difference.
Apr 05 02:01:03 <KenUnix> xset s off is no good that's for x11
Apr 05 02:01:22 <set_> Anyway, gsettings get org.gnome.desktop.screensaver false, this should work from what I am reading.
Apr 05 02:01:27 <set_> Dang it.
Apr 05 02:01:30 <set_> Please hold.
Apr 05 02:02:08 <set_> gsettings get org.gnome.desktop.screensaver lock-enabled true
Apr 05 02:02:10 <set_> Try that.
Apr 05 02:02:17 <set_> GET and not SET.
Apr 05 02:02:39 <set_> then...
Apr 05 02:02:44 <KenUnix> No such key “false”
Apr 05 02:02:59 <set_> Okay.
Apr 05 02:03:05 <set_> So...
Apr 05 02:03:44 <KenUnix> gsettings get org.gnome.desktop.screensaver false <<== missing argument
Apr 05 02:04:08 <set_> gsettings set org.gnome.desktop.screensaver lock-enabled false
Apr 05 02:04:25 <KenUnix> gsettings get org.gnome.desktop.screensaver lock-enabled true <== this enables lock
Apr 05 02:04:58 <set_> Right. So, get and then set.
Apr 05 02:05:35 <KenUnix> gsettings set org.gnome.desktop.screensaver lock-enabled false <== don't work unless Ubuntu did something funny as I am runninh beta
Apr 05 02:05:51 <set_> get lock-enabled true && set lock-enabled false
Apr 05 02:05:52 <set_> Hmm.
Apr 05 02:05:53 <set_> Okay.
Apr 05 02:05:59 <set_> I will go and look elsewhere.
Apr 05 02:06:53 <KenUnix> no such sommand 'get'
Apr 05 02:09:21 <MattB0ne> man that is an odd bug
Apr 05 02:09:37 <MattB0ne> are you password locked out once the SS kicks in
Apr 05 02:09:46 <set_> sudo
Apr 05 02:09:56 <set_> uSe SuDo!
Apr 05 02:10:15 <set_> If the system will not listen and you are changing system specific dir. and files, use sudo.
Apr 05 02:11:39 <set_> I found another way.
Apr 05 02:12:10 <set_> gconftool-2 is a utility to use.
Apr 05 02:12:44 <set_> So, from your command line -> gnome-screensaver-preferences
Apr 05 02:12:47 <set_> Let me test it.
Apr 05 02:16:26 <set_> Forget it. Try idle-delay 0.
Apr 05 02:16:30 <set_> W/ gsettings set
Apr 05 02:16:35 <set_> So...
Apr 05 02:17:02 <set_> gsettings set org.gnome.desktop.screensaver idle-delay 0
Apr 05 02:18:39 <set_> you have gnome -v 3+ right/
Apr 05 02:18:40 <set_> ?
Apr 05 02:29:02 <KenUnix> Setting to 0 dosen't do anything but put it back to 5 minutes. Forget about it. Good effort.
Apr 05 02:31:35 <KenUnix> Talk to you tomorrow.
Apr 05 02:33:52 <set_> Blah!
Apr 05 02:37:33 <GenTooMan> well set it's a 4 letter word... you know :D
Apr 05 02:43:47 <set_> Blah plus exclamation points are where it is at!
Apr 05 02:43:54 <set_> a = i
Apr 05 02:45:51 <set_> I really think venv does not work w/ Django. Off to find some docs. on it.
Apr 05 02:46:14 <set_> The Django people swear by virtualenv instead.
Apr 05 02:49:30 <set_> Oh. I need to "fork" it first.
Apr 05 02:52:27 <GenTooMan> Django.. hmmm 3 or 4 tines for the fork?
Apr 05 02:52:44 <GenTooMan> are you using subversion git or mercurial?
**** ENDING LOGGING AT Sun Apr 05 02:59:58 2020