[gelöst] yaVDR 0.1.1 : XBMC startet nicht mehr

Hello,

thanks for your reply.

Zitat

Originally posted by gda
Hi David4,

Sorry to hear that, but it looks like we have to wait for an experienced Linux user with the same Problem to solve it. We don't see this Problem and can't do it by ourselves.

Because of the last tests I doubt that there is a problem with the permissions.

Ok, are there some tests which I can do?
I hope that I'm experienced enough to check what is neccessary if you'll give me hints on what to look for.

start-xbmc permissions are:

vdr@sun:~$ ls -l /usr/bin/start-xbmc
-rwxr-xr-x 1 root root 149 2010-02-18 19:39 /usr/bin/start-xbmc

Zitat

Maybe it is a race condition. Play a little bit with the script start-xbmc.
Put a

Code

sleep 5

under the line

Code

sudo /sbin/initctl stop vdr-frontend

, or comment this line out.

This currently looks as most probable cause for me now. I'll test this when I'll be back home in the afternoon.

Zitat

I don't have to mention that it is mandatory if you face problems to do

Code

sudo apt-get update
sudo apt-get dist-upgrade

, have I?

I already did update/upgrade yesterday when I found this problem, with no effect.

Just to provide more information, this is part of the /var/log/user.log which covers messages from externalplayer plugin when it tries to start xbmc:

Feb 24 21:40:02 sun vdr: [1874] SOFTOSD: FadeIn Step 6 from 8 FlushTime = 2 ms
Feb 24 21:40:02 sun vdr: [1874] SOFTOSD: FadeIn Step 7 from 8 FlushTime = 3 ms
Feb 24 21:40:02 sun vdr: [1874] SOFTOSD: FadeIn Step 8 from 8 FlushTime = 2 ms
Feb 24 21:40:03 sun vdr: [1874] [xine..put] OSD bandwidth: 343964 bytes/s (2687 kbit/s)
Feb 24 21:40:04 sun vdr: [1874] [xine..put] OSD bandwidth: 171910 bytes/s (1343 kbit/s)
Feb 24 21:40:05 sun vdr: [1874] externalplayer-plugin: starting player: XBMC
Feb 24 21:40:05 sun vdr: [1874] externalplayer-plugin: disable remotes
Feb 24 21:40:05 sun vdr: [1944] IPTV streamer thread ended (pid=1874, tid=1944)
Feb 24 21:40:05 sun vdr: [1874] SOFTOSD: FadeOut Step 1 from 8 FlushTime = 3 ms
Feb 24 21:40:05 sun vdr: [1874] SOFTOSD: FadeOut Step 2 from 8 FlushTime = 2 ms
Feb 24 21:40:05 sun vdr: [1874] SOFTOSD: FadeOut Step 3 from 8 FlushTime = 2 ms
Feb 24 21:40:05 sun vdr: [1874] SOFTOSD: FadeOut Step 4 from 8 FlushTime = 2 ms
Feb 24 21:40:05 sun vdr: [1943] receiver on device 10 thread ended (pid=1874, tid=1943)
Feb 24 21:40:05 sun vdr: [1874] SOFTOSD: FadeOut Step 5 from 8 FlushTime = 3 ms
Feb 24 21:40:05 sun vdr: [1874] SOFTOSD: FadeOut Step 6 from 8 FlushTime = 3 ms
Feb 24 21:40:05 sun vdr: [1874] SOFTOSD: FadeOut Step 7 from 8 FlushTime = 3 ms
Feb 24 21:40:05 sun vdr: [1874] SOFTOSD: FadeOut Step 8 from 8
Feb 24 21:40:05 sun vdr: [1973] externalplayer-plugin: executing "sudo start-xbmc"
Feb 24 21:40:05 sun vdr: [1874] externalplayer-plugin: PID of child process: 1973
Feb 24 21:40:06 sun vdr: [1874] externalplayer-plugin: shutting down player
Feb 24 21:40:06 sun vdr: [1874] externalplayer-plugin: enable remotes
Feb 24 21:40:06 sun vdr: [1874] switching to channel 1
Feb 24 21:40:06 sun vdr: [1974] receiver on device 10 thread started (pid=1874, tid=1974)
Feb 24 21:40:06 sun vdr: [1976] IPTV streamer thread started (pid=1874, tid=1976)
Feb 24 21:40:07 sun vdr-sxfe[1921]: [1936] [demux_vdr] PMT changed
Feb 24 21:40:12 sun vdr: [1874] SOFTOSD: FadeIn Step 1 from 8 FlushTime = 1 ms
Feb 24 21:40:12 sun vdr: [1874] SOFTOSD: FadeIn Step 2 from 8 FlushTime = 3 ms
Feb 24 21:40:12 sun vdr: [1874] SOFTOSD: FadeIn Step 3 from 8 FlushTime = 1 ms
Feb 24 21:40:12 sun vdr: [1874] SOFTOSD: FadeIn Step 4 from 8 FlushTime = 1 ms

Just to notice, it was completely clean install of yaVDR 0.1.1 (downloaded yesterday from yavdr.org).

My HTPC components:
CPU: AMD Sempron(tm) 140 Processor
MB: MICRO-STAR 770-C45
GPU: nVidia Corporation G94 [GeForce GT 130] (rev a1)

Cheers,
David

Zitat

Original von David4

This currently looks as most probable cause for me now. I'll test this when I'll be back home in the afternoon.

I am not so sure, the profile .xbmc that Hepi mentioned ist a candidate for me too.

Gerald

Zitat

Original von Bernie7

Damit kann ich leider nicht dienen, zu mehr als "ls -l" reichen meine Kenntnisse leider nicht.

Aber ein

sudo rm -rf /var/lib/vdr/.xbmc

bekommst du auch hin.
Versuch mal ob es danach geht.

Gerald

Zitat

Original von Bernie7

Nein.

das schränkt die Suche schon mal ein, danke.

Ein paar Fragen noch.
Unmittelbar nach diesem Versuch, hat da XBMC wieder ein Verzeichnis /var/lib/vdr/.xbmc angelegt, oder ist es immer noch weg? Voraussetzung ist natürlich, dass du zwischenzeitlich xbmc nicht per Hand gestartet hast.

Wieviel Grafik-Speciher hast du im BIOS eingestellt? Versuche mal 512MB wenn es noch nicht passiert ist.

Gerald

connected on ssh

vdr@htpc:~$ export DISPLAY=:1

vdr@htpc:~$ sudo /sbin/initctl stop vdr-frontend
vdr-frontend stop/waiting

vdr@htpc:~$ su -c "/usr/bin/xbmc --standalone" vdr
Password: 
open /dev/sequencer or /dev/snd/seq: Nessun file o directory

xbmc will starts well

vdr@htpc:~$ sudo /sbin/initctl start vdr-frontend
vdr-frontend start/running, process 3927

but from menu applikationen xbmc not work.

xzero2

Zitat

Original von xzero2
but from menu applikationen xbmc not work.

Yes, we know this already, thanks.

Please try to change the start of xbmc in start-xbmc to this:

su -c "/usr/bin/xbmc --standalone 2>&1 >/tmp/start-xbmc.log" vdr

and post the file /tmp/start-xbmc.log. Additionally send your /etc/sudoers file.

Gerald

Ich denke ich habe den Grund für euer Problem gefunden. Ich gehe davon aus, dass ihr bei der Installation auf die Frage nach dem Usernamen den Namen "vdr" eingegeben habt, richtig? Ihr Blindfische, der Name ist tabu.

Weil ihr den Namen vdr genommen habt, landet der user vdr in der Gruppe der admins, das soll er aber nicht. Jetzt zieht nämlich die letzte Zeile aus der /etc/sudoers:

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL

Das bedeutet, aller Admins dürfen alles, aber MIT Passwort!
Das überschreibt automatisch diese Zeilen:

# Added by yavdr-startup, don't remove
vdr ALL=NOPASSWD: /sbin/initctl
# Added by yavdr-startup, don't remove
vdr ALL=NOPASSWD: /usr/bin/start-xbmc

mit denen wir dem user vdr erlauben start-xbmc und initctl OHNE Passwort zu benutzen.

Wir könnten jetzt versuchen, dass unsere Zeilen immer die letzten sind, aber wir wollen sowieso nicht, dass der normale user vdr heißt, weil das ein erhöhtes Sicherheitsrisiko wäre.

Kommt jetzt nicht damit, dass wir irgendwie verhindern sollen, dass der User vdr genommen werden kann. Wegen dieser Sache patche ich den Ubuntu-Installer nicht.

NEVER USE THE USERNAME VDR!

Gerald

Zitat

Original von Bernie7
Steht sogar groß in meiner Anleitung : http://www.partyfotos.de/vdr/

Du kannst doch nicht im Ernst annehmen, dass ich eine Anleitung lese ;).

Gerald

Hello Gerald,

I see that you probably found the reason for xbmc start fail.
I'm not good in german, so I don't see the details, could you please briefly describe what was the problem?
Is it in /etc/sudoers or in the fact that I have chosen username vdr for the user under which vdr runs?

Cheers,
David

Zitat

Original von David4
Hello Gerald,

I see that you probably found the reason for xbmc start fail.
I'm not good in german, so I don't see the details, could you please briefly describe what was the problem?
Is it in /etc/sudoers or in the fact that I have chosen username vdr for the user under which vdr runs?

Cheers,
David

Alles anzeigen

The user you choose during installation goes always into the group admin.
because of this, this line in /etc/sudoers:

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL

overwrites the preceding lines:

# Added by yavdr-startup, don't remove
vdr ALL=NOPASSWD: /sbin/initctl
# Added by yavdr-startup, don't remove
vdr ALL=NOPASSWD: /usr/bin/start-xbmc

that means the user vdr is allowed to do everything but with password, but it should only get the permission to start-xbmc and initctl without password. The start of start-xbmc fails because it asks for a password that it doesn't get.

The other sentences mean that we will do nothing to prevent this in future. I think there is no need to translate the unfriendly part of the post.

Gerald

Zitat

Original von Bernie7
But I don't know another username now, I have no fantasy

Maybe myvdr ?

You are strange, you are this user! The name is bernd.

Gerald

Hello Gerald,

thanks for explanation in english and your help.
Now I understand the issue, it has really no sense to make any changes to prevent this, I see that there's a note on yaVDR.org/installation that the "vdr" user is reserved (I don't remember whether it was there yesterday ).

Once again, thanks for help, yaVDR is great piece of software.

Best regards,
David

Zitat

Original von David4
(I don't remember whether it was there yesterday

It wasn't there 5 hours ago.

Zitat

Original von gda
NEVER USE THE USERNAME VDR!
Gerald

hm wenn ich mich aber recht erinnere hat das bei yavdr 0.1 (sprich beim ersten iso) ohne probleme geklappt......

gruss gerd