/srv/irclogs.ubuntu.com/2015/06/11/#ubuntu-mythtv.txt

spoky99hi all09:46
spoky99hi all10:50
spoky99hi all12:38
spoky99I 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:43
spoky99I don't know what goes wrong, I cecked all the configuration menu (mythwelcome setup, general setup into mythfrontend and mythtv-setup) and they seem correct12:44
spoky99there is a way to know what stop mythwelcome?12:44
spoky99hi all15:34
spoky99I 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:34
spoky99launching mythbackend -v idle,system seems that mythtv repeat many times mythshutdown --check15:38
spoky99hi gedakc15:39
spoky99hi #gedakc15:43
gedakcspoky99:  Hi.  :-)15:47
spoky99I'm still there :D15:47
gedakcDid you get it working?15:47
spoky99don't work -_-15:47
spoky99launching mythbackend -v idle,system seems that mythtv repeat many times mythshutdown --check15:47
gedakcDid you try using all the steps I had in the tutorial I wrote?15:48
spoky99yesss15:48
gedakcDoes MythTV work for everything else (recording, watching shows, etc)?  'Just not for auto shutdown and wakeup?15:49
spoky99yes15:49
spoky99the other computer work :)15:50
gedakcAnd just to confirm, was the test of RTC wakeup on your motherboard successful?15:50
gedakcHmm... so your other computer works....15:52
spoky99the old-new mediacenter make from mythbuntu 14.04 don't work properly, during shutdown frozed15:52
spoky99war 1 or 2 month that was on witouth shutdown15:53
gedakcCould you describe "frozed"?15:53
spoky99I put shutdown -P15:53
spoky99and now shutdown15:53
gedakcDoes it shutdown properly now?15:54
spoky99I really don't know why froze, start go down service and suddenly he stopped, without write someting in the log file15:55
spoky99now It work15:55
spoky99(the next step was connect a serial cable and start telnet connection for to see what goes wrong)15:56
gedakcDo you recall making a change that caused shutdown to start working?15:56
spoky99shutdown -P15:57
gedakcOkay.  If I recall correctly some systems did need that.15:57
spoky99sometime they shutdown well before this change, sometime froze15:57
spoky99I read it15:58
spoky99I'm not luky :)15:58
spoky99sometime don't wakeup, I don't know if is a motherboard problem or a system problem, and I'm trying to replace motherboard and filesysem15:59
spoky99filesystem15:59
gedakcIn the MythBackend setup, have you disabled "block shutdown before client connected"?15:59
spoky99but I don't want use mythbuntu16:00
spoky99yesss! I disable it, is uncecked16:00
gedakcOh, sorry, my mistake.  I assumed you were using mythbuntu.  What distro are you using?16:00
spoky99ubuntu with mate desktopmanager16:01
gedakcI haven't used that setup.16:01
spoky9914.0416:01
gedakcOnly kubuntu, ubuntu, lubuntu, and xubuntu.16:02
spoky99in theory it should not change anything16:02
spoky99mate use ligtdm like xubuntu16:02
gedakc'Agreed, although there are differences that might impact the setup.16:02
spoky99and sometime gnome16:03
gedakcFrom my past experience, intermittent problems are often caused by faulty hardware.16:03
spoky99maybe16:03
gedakcIf the problem is consistent (repeatable), then I've often found it to be with software.16:03
gedakcSince you have one computer working, that implies that you have correctly set up MythTV at least once.16:04
gedakcYou might try comparing settings between the systems to see if there are any key differences.16:04
spoky99I'm not shure with the old computer, but new motherboard work well, the tvcard work well, harddisk is ok16:04
spoky99Is exactly the same16:04
gedakcIf 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:05
spoky99I compare the screen of the setup, checking each caracter and spooky space16:06
gedakcThat would be the first thing I would try.  However, comparing screens is a manual process and something might be missed.16:07
spoky99there is not difference, I check mythfrontend general, mytwelcome --setup and mytwelocme -i and mythtv-setup16:07
spoky99I know16:07
gedakcThe problem might be in a script or some other area too.16:07
gedakcSince it is the same hardware, it should work with exactly the same settings.16:08
gedakcIs the firmware the same version on the motherboards?16:08
spoky99yesterday 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:08
spoky99are two different motherboard16:09
spoky99is not the same hardware16:09
spoky99is not new hardware, but it work16:10
spoky99launching the script from bash... work16:10
gedakcI guess when you said "exactly the same", you meant the MythTV setup, not the hardware.16:10
spoky99mytwelcome enters loop and does not exceed the check16:11
spoky99yess the configuration is the same16:11
spoky99same script16:11
spoky99same path16:11
spoky99no16:11
gedakcSo mythwelcome is in a loop (does not shutdown)?16:11
spoky99is not true, now in the new there is your setting16:12
spoky99yess16:12
gedakcMythwelcome runs a script to check if it is okay to shutdown before it invokes the shutdown.16:12
spoky99launching from bash mythbackend -v idle,system seems that mythtv repeat many times mythshutdown --check16:12
spoky99yes I know16:12
spoky99I read someting about put env into sudoers file16:13
gedakcSo then there is something causing mythshutdown --check to report that "It is not okay to shutdown".16:13
spoky99I son't know, I suppose16:13
gedakcYou can check from the command line by running "mythshutdown --check" and then immediately looking at the return code.16:14
gedakcUse "echo $?" to get the return code of the last executed command.16:14
spoky99ahaha16:15
spoky99they return16:15
spoky99OK to shutdown16:15
gedakcBy OK do you mean it returns zero "0" or a non-zero value?16:16
spoky99no return exactly "OK to shutdown"16:16
spoky99and mythbackend repeat16:17
gedakcHmm...16:17
spoky99I managed child (pid 292020) has started! command=/usr/bin/mythshutdown --check, timeout=016:18
gedakcIf it is "OK to shutdown", then mythtv is supposed to run the "command to set wakeup time".16:18
spoky99I managed child (pid 292020) has started! command=/usr/bin/mythshutdown --check, status=32512, result=12716:18
gedakcresult=127?  I thought the return code had to be zero to shutdown...16:19
spoky99I cat /proc/driver/rtc and... the wakeup time is the same of the next record16:21
gedakcOkay.  I assume same time of upcoming recording minus a few minutes to allow the system to start up.16:21
spoky99return could be 0 and not 127?16:21
gedakcIt is possible that "result" is not equal to "return code".16:22
gedakcIt would seem that the time is being set in the RTC for the next recording.16:22
gedakcSo.... that means that there might be a problem with the actual shutdown command.16:23
spoky99yes, seem thath setwakeup $time is execute16:23
gedakcWhat do you have "Server halt command" set to?16:23
gedakcMine is:16:23
gedakcsudo sh -c "mythshutdown --shutdown"16:23
spoky99I'm rebooting16:25
spoky99I copy the shutdown comand into a terminal and it work16:25
spoky99mythwelcome comand16:26
spoky99now, when reboot I restart mythtv-setup and copy the mythshutdown path into a terminal16:26
gedakcOkay.  It should shutdown then.16:27
gedakcDid it reboot by itself, or did you power it on?16:28
gedakcMine used to go into a reboot loop.  To stop it I  had to set "Command to reboot" to "/sbin/poweroff".16:29
spoky99I look some strange thing16:30
spoky99copy the command directly into the bash there is a return from mythshutdown and --16:31
spoky99I understand the problem, launch sudo -sh -c "/usr/bin/mythshutdown --shutdown" from bash ask me password16:34
spoky99I could insert sh into sudoers16:34
gedakcYes, that is needed.16:35
gedakc/sbin/shutdown, /bin/sh, /usr/bin/setwakeup.sh, /usr/bin/mythshutdown, /sbin/poweroff, /sbin/reboot16:35
spoky99now from bash it work! :)16:36
spoky99was ok for the other command I don't insert /bin/sh16:36
gedakcI think you might have solved the problem.  :-)16:37
spoky99I'm ceck it!16:38
spoky99thank's16:38
gedakcYou're welcome.16:38
spoky99:D16:38
spoky99work it!!!!16:38
gedakcCongratulations!16:39
spoky99It was giving birth!16:39
spoky99ahahahaha16:39
spoky99I owe you one16:40
gedakcI hope you enjoy your working PVR.  :-)16:40
spoky99ahaha16:40
spoky99I use mythtv for 12 year, the old old hardware it worked with nvram-wakeup -_-16:41
spoky99and worked fine for a long time, acpi is not the same :P16:42
gedakcYes, it is a challenge to keep up with changing hardware.16:42
gedakcI've only been using MythTV since 2011.  I built 3 PVRs the exact same for family and a friend.16:42
gedakcAnd regarding "you owe me one", just pass the favour along to the next person needing help.  :-)16:44
spoky99I did and I will continue to do so16:46
gedakcCool.  You don't owe me anything.  'Glad to help.16:46
spoky99nothing is due16:47
gedakc:-)16:47
spoky99I remember two guys, one help me many times the other tell me 10 years ago that the analogic audio output was outdated16:49
spoky99and my audio problem was not a problem :)16:50
gedakcThere is a lot of trial and error involved with helping others.16:51
gedakcThe same goes for diagnosing and fixing problems by yourself.  ;-)16:51
gedakcAnyways, I'm off for now.  Have a great day spoky99!16:52
spoky99now I could invent a way to decrease the temperature into the mobo without noise, with summer don't work well16:54
spoky99thanks16:54
spoky99and bye!16:54

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!