[09:46] <spoky99> hi all
[10:50] <spoky99> hi all
[12:38] <spoky99> hi all
[12:43] <spoky99> I have problem with mythwelcome, when I leave mythfrontend does the count down but don't execute the script (that are executable and tested from bash)
[12:44] <spoky99> I don't know what goes wrong, I cecked all the configuration menu (mythwelcome setup, general setup into mythfrontend and mythtv-setup) and they seem correct
[12:44] <spoky99> 	there is a way to know what stop mythwelcome?
[15:34] <spoky99> hi all
[15:34] <spoky99> I have problem with mythwelcome, when I leave mythfrontend does the count down but don't execute the script (that are executable and tested from bash)
[15:38] <spoky99> launching mythbackend -v idle,system seems that mythtv repeat many times mythshutdown --check
[15:39] <spoky99> hi gedakc
[15:43] <spoky99> hi #gedakc
[15:47] <gedakc> spoky99:  Hi.  :-)
[15:47] <spoky99> I'm still there :D
[15:47] <gedakc> Did you get it working?
[15:47] <spoky99> don't work -_-
[15:47] <spoky99> launching mythbackend -v idle,system seems that mythtv repeat many times mythshutdown --check
[15:48] <gedakc> Did you try using all the steps I had in the tutorial I wrote?
[15:48] <spoky99> yesss
[15:49] <gedakc> Does MythTV work for everything else (recording, watching shows, etc)?  'Just not for auto shutdown and wakeup?
[15:49] <spoky99> yes
[15:50] <spoky99> the other computer work :)
[15:50] <gedakc> And just to confirm, was the test of RTC wakeup on your motherboard successful?
[15:52] <gedakc> Hmm... so your other computer works....
[15:52] <spoky99> the old-new mediacenter make from mythbuntu 14.04 don't work properly, during shutdown frozed
[15:53] <spoky99> war 1 or 2 month that was on witouth shutdown
[15:53] <gedakc> Could you describe "frozed"?
[15:53] <spoky99> I put shutdown -P
[15:53] <spoky99> and now shutdown
[15:54] <gedakc> Does it shutdown properly now?
[15:55] <spoky99> I really don't know why froze, start go down service and suddenly he stopped, without write someting in the log file
[15:55] <spoky99> now It work
[15:56] <spoky99> (the next step was connect a serial cable and start telnet connection for to see what goes wrong)
[15:56] <gedakc> Do you recall making a change that caused shutdown to start working?
[15:57] <spoky99> shutdown -P
[15:57] <gedakc> Okay.  If I recall correctly some systems did need that.
[15:57] <spoky99> sometime they shutdown well before this change, sometime froze
[15:58] <spoky99> I read it
[15:58] <spoky99> I'm not luky :)
[15:59] <spoky99> sometime don't wakeup, I don't know if is a motherboard problem or a system problem, and I'm trying to replace motherboard and filesysem
[15:59] <spoky99> filesystem
[15:59] <gedakc> In the MythBackend setup, have you disabled "block shutdown before client connected"?
[16:00] <spoky99> but I don't want use mythbuntu
[16:00] <spoky99> yesss! I disable it, is uncecked
[16:00] <gedakc> Oh, sorry, my mistake.  I assumed you were using mythbuntu.  What distro are you using?
[16:01] <spoky99> ubuntu with mate desktopmanager
[16:01] <gedakc> I haven't used that setup.
[16:01] <spoky99> 14.04
[16:02] <gedakc> Only kubuntu, ubuntu, lubuntu, and xubuntu.
[16:02] <spoky99> in theory it should not change anything
[16:02] <spoky99> mate use ligtdm like xubuntu
[16:02] <gedakc> 'Agreed, although there are differences that might impact the setup.
[16:03] <spoky99> and sometime gnome
[16:03] <gedakc> From my past experience, intermittent problems are often caused by faulty hardware.
[16:03] <spoky99> maybe
[16:03] <gedakc> If the problem is consistent (repeatable), then I've often found it to be with software.
[16:04] <gedakc> Since you have one computer working, that implies that you have correctly set up MythTV at least once.
[16:04] <gedakc> You might try comparing settings between the systems to see if there are any key differences.
[16:04] <spoky99> I'm not shure with the old computer, but new motherboard work well, the tvcard work well, harddisk is ok
[16:04] <spoky99> Is exactly the same
[16:05] <gedakc> If it's exactly the same, you might try making an image backup of both computers.  Then restore the image from the working computer onto the non-working computer to see if that fixes the problem.
[16:06] <spoky99> I compare the screen of the setup, checking each caracter and spooky space
[16:07] <gedakc> That would be the first thing I would try.  However, comparing screens is a manual process and something might be missed.
[16:07] <spoky99> there is not difference, I check mythfrontend general, mytwelcome --setup and mytwelocme -i and mythtv-setup
[16:07] <spoky99> I know
[16:07] <gedakc> The problem might be in a script or some other area too.
[16:08] <gedakc> Since it is the same hardware, it should work with exactly the same settings.
[16:08] <gedakc> Is the firmware the same version on the motherboards?
[16:08] <spoky99> yesterday the old mediacenter don't shutdown because I leave a strange caracter in the path (insert for don't shutdown the computer for the problem ahead)
[16:09] <spoky99> are two different motherboard
[16:09] <spoky99> is not the same hardware
[16:10] <spoky99> is not new hardware, but it work
[16:10] <spoky99> launching the script from bash... work
[16:10] <gedakc> I guess when you said "exactly the same", you meant the MythTV setup, not the hardware.
[16:11] <spoky99> mytwelcome enters loop and does not exceed the check
[16:11] <spoky99> yess the configuration is the same
[16:11] <spoky99> same script
[16:11] <spoky99> same path
[16:11] <spoky99> no
[16:11] <gedakc> So mythwelcome is in a loop (does not shutdown)?
[16:12] <spoky99> is not true, now in the new there is your setting
[16:12] <spoky99> yess
[16:12] <gedakc> Mythwelcome runs a script to check if it is okay to shutdown before it invokes the shutdown.
[16:12] <spoky99> launching from bash mythbackend -v idle,system seems that mythtv repeat many times mythshutdown --check
[16:12] <spoky99> yes I know
[16:13] <spoky99> I read someting about put env into sudoers file
[16:13] <gedakc> So then there is something causing mythshutdown --check to report that "It is not okay to shutdown".
[16:13] <spoky99> I son't know, I suppose
[16:14] <gedakc> You can check from the command line by running "mythshutdown --check" and then immediately looking at the return code.
[16:14] <gedakc> Use "echo $?" to get the return code of the last executed command.
[16:15] <spoky99> ahaha
[16:15] <spoky99> they return
[16:15] <spoky99> OK to shutdown
[16:16] <gedakc> By OK do you mean it returns zero "0" or a non-zero value?
[16:16] <spoky99> no return exactly "OK to shutdown"
[16:17] <spoky99> and mythbackend repeat
[16:17] <gedakc> Hmm...
[16:18] <spoky99> I managed child (pid 292020) has started! command=/usr/bin/mythshutdown --check, timeout=0
[16:18] <gedakc> If it is "OK to shutdown", then mythtv is supposed to run the "command to set wakeup time".
[16:18] <spoky99> I managed child (pid 292020) has started! command=/usr/bin/mythshutdown --check, status=32512, result=127
[16:19] <gedakc> result=127?  I thought the return code had to be zero to shutdown...
[16:21] <spoky99> I cat /proc/driver/rtc and... the wakeup time is the same of the next record
[16:21] <gedakc> Okay.  I assume same time of upcoming recording minus a few minutes to allow the system to start up.
[16:21] <spoky99> return could be 0 and not 127?
[16:22] <gedakc> It is possible that "result" is not equal to "return code".
[16:22] <gedakc> It would seem that the time is being set in the RTC for the next recording.
[16:23] <gedakc> So.... that means that there might be a problem with the actual shutdown command.
[16:23] <spoky99> yes, seem thath setwakeup $time is execute
[16:23] <gedakc> What do you have "Server halt command" set to?
[16:23] <gedakc> Mine is:
[16:23] <gedakc> sudo sh -c "mythshutdown --shutdown"
[16:25] <spoky99> I'm rebooting
[16:25] <spoky99> I copy the shutdown comand into a terminal and it work
[16:26] <spoky99> mythwelcome comand
[16:26] <spoky99> now, when reboot I restart mythtv-setup and copy the mythshutdown path into a terminal
[16:27] <gedakc> Okay.  It should shutdown then.
[16:28] <gedakc> Did it reboot by itself, or did you power it on?
[16:29] <gedakc> Mine used to go into a reboot loop.  To stop it I  had to set "Command to reboot" to "/sbin/poweroff".
[16:30] <spoky99> I look some strange thing
[16:31] <spoky99> copy the command directly into the bash there is a return from mythshutdown and --
[16:34] <spoky99> I understand the problem, launch sudo -sh -c "/usr/bin/mythshutdown --shutdown" from bash ask me password
[16:34] <spoky99> I could insert sh into sudoers
[16:35] <gedakc> Yes, that is needed.
[16:35] <gedakc> /sbin/shutdown, /bin/sh, /usr/bin/setwakeup.sh, /usr/bin/mythshutdown, /sbin/poweroff, /sbin/reboot
[16:36] <spoky99> now from bash it work! :)
[16:36] <spoky99> was ok for the other command I don't insert /bin/sh
[16:37] <gedakc> I think you might have solved the problem.  :-)
[16:38] <spoky99> I'm ceck it!
[16:38] <spoky99> thank's
[16:38] <gedakc> You're welcome.
[16:38] <spoky99> :D
[16:38] <spoky99> work it!!!!
[16:39] <gedakc> Congratulations!
[16:39] <spoky99> It was giving birth!
[16:39] <spoky99> ahahahaha
[16:40] <spoky99> I owe you one
[16:40] <gedakc> I hope you enjoy your working PVR.  :-)
[16:40] <spoky99> ahaha
[16:41] <spoky99> I use mythtv for 12 year, the old old hardware it worked with nvram-wakeup -_-
[16:42] <spoky99> and worked fine for a long time, acpi is not the same :P
[16:42] <gedakc> Yes, it is a challenge to keep up with changing hardware.
[16:42] <gedakc> I've only been using MythTV since 2011.  I built 3 PVRs the exact same for family and a friend.
[16:44] <gedakc> And regarding "you owe me one", just pass the favour along to the next person needing help.  :-)
[16:46] <spoky99> I did and I will continue to do so
[16:46] <gedakc> Cool.  You don't owe me anything.  'Glad to help.
[16:47] <spoky99> nothing is due
[16:47] <gedakc> :-)
[16:49] <spoky99> I remember two guys, one help me many times the other tell me 10 years ago that the analogic audio output was outdated
[16:50] <spoky99> and my audio problem was not a problem :)
[16:51] <gedakc> There is a lot of trial and error involved with helping others.
[16:51] <gedakc> The same goes for diagnosing and fixing problems by yourself.  ;-)
[16:52] <gedakc> Anyways, I'm off for now.  Have a great day spoky99!
[16:54] <spoky99> now I could invent a way to decrease the temperature into the mobo without noise, with summer don't work well
[16:54] <spoky99> thanks
[16:54] <spoky99> and bye!