Beiträge von benoe

    Here is my remote.xml for xbmc, for reference:



    In order to have the most functionality, I have added these keys to Lircmap.xml:


    Code
    <star>KEY_NUMERIC_STAR</star>
                    <hash>KEY_NUMERIC_POUND</hash>
                    <enter>KEY_ENTER</enter>
                    <clear>KEY_DELETE</clear>


    Pls consider checking and adding these to the defaults/updates. Thanks.

    Thanks, it works, and hopefully it will during future updates as well.


    Here is my keytable:


    Not working: Power, Menu, Back:



    Don't know yet if these are working or not: 4 keys below volume/ch and above numerics:



    and the others, for reference:

    After the recent updates my remote keys "menu" and "back" stopped working.
    Here is the output of list-rc-core.sh



    Pls let me know if any more information is needed. Thanks.


    What did I do? I have no idea what the reason for your problem is. It is working for me. Only the first start of XBMC needs time until it is synced with the vdr.


    Gerald


    Ok, sorry, you just mentioned that xbmc in yavdr has "missing functionality for a clean vdr shutdown", that's why I thought it should be the root of the problem.


    How do you (any of you who read this topic) make your system to sleep automatically after a period of idle time?
    I set it up in xbmc, that after 5 minutes to shut down. This makes the pc to sleep. As I remember, sleep, or reboot in xbmc settings hasn't worked. Is there any other way to achieve this if you use xbmc as a frontend?


    I have more hope to convince pipelka to add the missing functionality for a clean vdr shutdown to his branch.


    Like!


    btw, if this the reason why the message appears there, why do you write it just now, and keep me in doubts that somethig went wrong with my installation?

    After reinstall the simptom changed a bit: (using xbmc as frontend)
    after cold boot or reboot: error message
    after putting the htpc into sleep and waking it up with the remote: no message
    after automatic sleep (enabled in xbmc to switch off the machine after x mins) and wake up with remore: error message.

    Relevant part of the xbmc log:


    Code
    22:39:13 T:140693578156000  NOTICE: Start - EPG thread started
    22:39:13 T:140693578156000  NOTICE: PVRManager - starting up
    22:39:13 T:140693248001792   ERROR: AddOnLog: VDR XVDR Client: Open - Can't connect to XVDR Server: Connection refused
    22:39:13 T:140693248001792   ERROR: ADDON: Dll VDR XVDR Client - Client returned bad status (1) from Create and is not usable
    22:39:13 T:140693248001792   ERROR: PVR - InitialiseClient - can't initialise add-on 'VDR XVDR Client'
    22:39:13 T:140693578156000  NOTICE: initialize done

    Hi!


    I freshly installed yaVDR 0.4, and after every start (even from sleep) XBMC displays this message:



    But the add-ons are already configured, so after pressing ok i see this:



    (engedélyezve = enabled, Kiegészítő tiltva = disabled)


    After I press "back" on this screen, everithing is working as expected.
    Do you have any idea how I could remove this message?


    Just for our curiousity and to confirm the issue, your VDR is now running with VDR 1.7.20 from our testing repositories? Means, the case could be seen as solved?


    Regards
    fnu


    Btw.: The elaborated above mentioned procedure does imply, that you have installed yaVDR 0.3 with all updates from the stable repositories, I should had mentioned this to seahawk1986, sorry ...


    Yes, I had an up-to-date yavdr 0.3 system and also a disk-level backup of it when I started the upgrade process seahawk1986 mentioned.

    Thanks, the upgrade went well!


    only one error appeared after dpkg --remove:


    Code
    dpkg-divert: mismatch on package
      when removing `diversion of /etc/firefox/profile/prefs.js to /etc/firefox/profile/prefs.js.dontremove by yavdr-startup'
      found `diversion of /etc/firefox/profile/prefs.js to /etc/firefox/profile/prefs.js.dontremove by yavdr-utils'
    dpkg: error processing yavdr-utils (--remove):
     subprocess installed post-removal script returned error exit status 2


    but I solved with this:

    Code
    sudo dpkg-divert --remove /etc/firefox/profile/prefs.js


    and after that two of the config files got replaced(or asked if I want to replace): order.conf and tntnet.conf



    I only tried the result with xbmc frontend, and the channels that didn't have sound before now have.


    So thanks for all your effort!


    Well, it hasn't ever been planned to be an upgrade for yaVDR 0.3 and be aware, it hasn't indeed been advertised as an upgrade for yaVDR 0.3 in our blog.


    I only started to test it with 0.3, because you announced it on the web page: "Packages for Ubuntu Lucid (yaVDR 0.3) and Ubuntu Natty (yaVDR 0.4) are now available, but most of them are untested" and was glad that I could solve the aac issue with the current setup, but also want to help you testing it. Otherwise I wouldn't even try, or at least wouldn't report there and here.


    It has rather been an update for all the experienced people out there using the Lucid repositories building VDR machines on their own manner. Doesn't mean you're not experienced, but right know you have to decide between using yaVDR 0.3 or "ppa:yavdr/testing-vdr" && "ppa:yavdr/main" on your own responsibility.


    I tought the opposite, that there is yavdr, the main project, and there is an option, with less attention, for users who want install yavdr on their average desktop machines. Maybe I wasn't just prudent enough in this matter.



    Do not ever use "ppa:yavdr/testing-vdr" with yaVDR 0.3, we won't ever take care if these packages do run with yaVDR 0.3 nor if all dependencies are working, they do just run with Ubuntu 10.04 (lucid).


    Good to know that, as I wrote, I tought the opposite.



    Bottomline we even don't guarantee this for "ppa:yavdr/testing-vdr", whereas please remind, it's name is testing, not stable.


    This, I'm aware of. (testing is testing, not stable :) )



    But we feel that some of you might want to use the newer versions out there with yaVDR 0.3, so we will have a look to resolve at least the dependencies, but there could still some problems kept in the packages of this testing repository.


    Thanks.



    So, please be patient, stay tuned and don't forget yaVDR's future is 0.4!


    Regards
    fnu


    I know the future is 0.4, but right now it is not working for me as it should.
    But I'm also not in a hurry, I could totally accept the "when it is done" method, righ now I satisfied with my current setup, as I wrote already.

    At the moment it is not possible to use yaVDR 0.3 together with the unstable- or testing-PPAs.
    A plain Lucid installation + main + testing-vdr (or even unstable-vdr) should work (at least it does on my primary VDR). If you want to test a more recent version of VDR/yaVDR give yaVDR 0.4pre1 (caution: alpha release) a try.


    Do you have any information when it will be fixed?
    I'm very satisfied with the current setup except the AAC sound issue.
    Btw, I'm also trying 0.4pre1, but I have different problems what I will write down in another thread.

    Code
    cat /etc/apt/sources.list.d/yavdr.listdeb http://ppa.launchpad.net/yavdr/stable-vdr/ubuntu lucid maindeb http://ppa.launchpad.net/yavdr/stable-xbmc/ubuntu lucid maindeb http://ppa.launchpad.net/yavdr/stable-yavdr/ubuntu lucid maindeb http://ppa.launchpad.net/yavdr/main/ubuntu lucid maindeb http://ppa.launchpad.net/yavdr/testing-vdr/ubuntu lucid main




    Code
    apt-cache policy libtntnet8 libtntnet9 vdr yavdr-essentiallibtntnet8:  Installed: 2.0-1yavdr2  Candidate: 2.0-1yavdr2  Version table: *** 2.0-1yavdr2 0        500 http://ppa.launchpad.net/yavdr/stable-vdr/ubuntu/ lucid/main Packages        100 /var/lib/dpkg/status     1.6.3-4 0        500 http://hu.archive.ubuntu.com/ubuntu/ lucid/universe Packageslibtntnet9:  Installed: (none)  Candidate: 2.0+rev.1295-0yavdr3~lucid  Version table:     2.0+rev.1295-0yavdr3~lucid 0        500 http://ppa.launchpad.net/yavdr/main/ubuntu/ lucid/main Packages        100 /var/lib/dpkg/statusvdr:  Installed: 1.7.20-8yavdr1~lucid  Candidate: 1.7.20-8yavdr1~lucid  Version table: *** 1.7.20-8yavdr1~lucid 0        500 http://ppa.launchpad.net/yavdr/testing-vdr/ubuntu/ lucid/main Packages        100 /var/lib/dpkg/status     1.7.16-24yavdr1 0        500 http://ppa.launchpad.net/yavdr/stable-vdr/ubuntu/ lucid/main Packages     1.6.0-9ubuntu2 0        500 http://hu.archive.ubuntu.com/ubuntu/ lucid/universe Packagesyavdr-essential:  Installed: (none)  Candidate: 0.3.0.2089-1yavdr1  Version table:     0.3.0.2089-1yavdr1 0        500 http://ppa.launchpad.net/yavdr/stable-yavdr/ubuntu/ lucid/main Packages