{2024} BM²LTS-v4.4.x-Ubuntu 22.04.4- > DD-NET & NetCeiver

cinfo · 27. Januar 2021

Hi,

neue Version BM2LTS v3.4.18

soon as possible

Code

############################################################################################
v3.4.18 - BM2LTS Ubuntu 20.04.1 LTS
############################################################################################
- VDR-2.4.6 & Plugins
- Kernel 5.11.0-051100rc5-generic x86_64
- Intel-Firmware "i915" aktualisiert
- Plugin graphlcd mit graphlcd-base für REEL-Display
- libcec4 & Plugin CECremote überarbeitet
- markad 2.5.4
- Plugin mcli überarbeitet
- route66 Anpassungen
- Plugin osdteletext mit Patch by- "pbiering"

Alles anzeigen

Grüße

cinfo

gggggg · 27. Januar 2021

Hi , bei dem

Code

vdr: [1664] ERROR: video data stream broken

kommt danach der Hinweis auf den Notaustieg im Setup (der disabled ist). Was bewirkt der ?

Code

vdr: [1664] emergency exit request ignored according to setup

Code

Jan 26 07:06:01 BM2LTSR66Nuc64native-MCLI vdr: [1451] timer 1 (2 0706-0708 'ZIB') start
Jan 26 07:06:01 BM2LTSR66Nuc64native-MCLI vdr: [1451] Title: 'ZIB' Subtitle: ''
Jan 26 07:06:01 BM2LTSR66Nuc64native-MCLI vdr: [1451] executing '/media/hd/recordings before "/media/hd/recordings/ZIB/2021-01-26.07.06.2-0.rec"'
Jan 26 07:06:01 BM2LTSR66Nuc64native-MCLI vdr[1663]: sh: 1: /media/hd/recordings: Permission denied
Jan 26 07:06:01 BM2LTSR66Nuc64native-MCLI vdr: [1451] record /media/hd/recordings/ZIB/2021-01-26.07.06.2-0.rec
Jan 26 07:06:01 BM2LTSR66Nuc64native-MCLI vdr: [1451] creating directory /media/hd/recordings/ZIB/2021-01-26.07.06.2-0.rec
Jan 26 07:06:01 BM2LTSR66Nuc64native-MCLI cron[443]: (*system*sa) INSECURE MODE (group/other writable) (/etc/cron.d/sa)
Jan 26 07:06:03 BM2LTSR66Nuc64native-MCLI vdr: [1451] recording to '/media/hd/recordings/ZIB/2021-01-26.07.06.2-0.rec/00001.ts'
Jan 26 07:06:03 BM2LTSR66Nuc64native-MCLI vdr: [1664] recording thread started (pid=1451, tid=1664, prio=high)
Jan 26 07:06:03 BM2LTSR66Nuc64native-MCLI vdr: [1451] markad: cStatusMarkAd::Recording(): recording <ZIB> [/media/hd/recordings/ZIB/2021-01-26.07.06.2-0.rec] started
Jan 26 07:06:03 BM2LTSR66Nuc64native-MCLI vdr: [1451] markad: cannot find timer for <ZIB>
Jan 26 07:06:03 BM2LTSR66Nuc64native-MCLI vdr: [1665] device 2 receiver thread started (pid=1451, tid=1665, prio=high)
Jan 26 07:06:04 BM2LTSR66Nuc64native-MCLI vdr[1667]: ? getopt returned character code 0107 ? (option_index 0)
Jan 26 07:06:04 BM2LTSR66Nuc64native-MCLI vdr: [1451] markad: executing "/usr/bin"/markad  -v  -G  -O --svdrpport=6419  -R  --vps  --autologo=2  -l "/opt/vdr/plugins/markad" --online=2 before "/media/hd/recordings/ZIB/2021-01-26.07.06.2-0.rec"
Jan 26 07:06:05 BM2LTSR66Nuc64native-MCLI vdr: [1451] markad: cStatusMarkAd::Add():: create epg event handler
Jan 26 07:06:05 BM2LTSR66Nuc64native-MCLI vdr[1451]: Mcli::recv_ts_func: Discontinuity on receiver 0x561cf450b7f0 for pid 3000: 8->5 at pos 1/7
Jan 26 07:06:05 BM2LTSR66Nuc64native-MCLI vdr: [1451] writing timer id '1@10.75.25.22' to /media/hd/recordings/ZIB/2021-01-26.07.06.2-0.rec/.timer
Jan 26 07:06:05 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload timers
Jan 26 07:06:05 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload timers
Jan 26 07:06:05 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload channels list
Jan 26 07:06:05 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload recordings list
Jan 26 07:06:07 BM2LTSR66Nuc64native-MCLI vdr: [1664] executing '/media/hd/recordings started "/media/hd/recordings/ZIB/2021-01-26.07.06.2-0.rec"'
Jan 26 07:06:07 BM2LTSR66Nuc64native-MCLI vdr[1670]: sh: 1: /media/hd/recordings: Permission denied
Jan 26 07:06:08 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload recordings list
Jan 26 07:06:10 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload timers
Jan 26 07:06:10 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload channels list
Jan 26 07:06:15 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload timers
Jan 26 07:06:18 BM2LTSR66Nuc64native-MCLI vdr[1451]: Mcli::recv_ts_func: Discontinuity on receiver 0x561cf44b6ff0 for pid 767: 10->12 at pos 0/7
Jan 26 07:06:20 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload timers
Jan 26 07:06:45 BM2LTSR66Nuc64native-MCLI vdr: message repeated 5 times: [ [1495] VNSI: Requesting clients to reload timers]
Jan 26 07:06:45 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload channels list
Jan 26 07:06:47 BM2LTSR66Nuc64native-MCLI vdr: [1664] ERROR: video data stream broken
Jan 26 07:06:47 BM2LTSR66Nuc64native-MCLI vdr: [1664] emergency exit request ignored according to setup
Jan 26 07:06:50 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload timers
Jan 26 07:07:00 BM2LTSR66Nuc64native-MCLI vdr: message repeated 2 times: [ [1495] VNSI: Requesting clients to reload timers]
Jan 26 07:07:01 BM2LTSR66Nuc64native-MCLI cron[443]: (*system*sa) INSECURE MODE (group/other writable) (/etc/cron.d/sa)
Jan 26 07:07:02 BM2LTSR66Nuc64native-MCLI vdr[1451]: Mcli::recv_ts_func: Discontinuity on receiver messages suppressed in 44 seconds: 19
Jan 26 07:07:02 BM2LTSR66Nuc64native-MCLI vdr[1451]: Mcli::recv_ts_func: Discontinuity on receiver 0x561cf4512250 for pid 0: 7->9 at pos 0/1
Jan 26 07:07:05 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload timers
Jan 26 07:07:15 BM2LTSR66Nuc64native-MCLI vdr: message repeated 2 times: [ [1495] VNSI: Requesting clients to reload timers]
Jan 26 07:07:17 BM2LTSR66Nuc64native-MCLI vdr: [1664] ERROR: video data stream broken
Jan 26 07:07:17 BM2LTSR66Nuc64native-MCLI vdr: [1664] emergency exit request ignored according to setup
Jan 26 07:07:20 BM2LTSR66Nuc64native-MCLI vdr: [1495] VNSI: Requesting clients to reload timers
Jan 26 07:07:45 BM2LTSR66Nuc64native-MCLI vdr: message repeated 5 times: [ [1495] VNSI: Requesting clients to reload timers]
Jan 26 07:07:47 BM2LTSR66Nuc64native-MCLI vdr: [1664] ERROR: video data stream broken
Jan 26 07:07:47 BM2LTSR66Nuc64native-MCLI vdr: [1664] emergency exit request ignored according to setup

Alles anzeigen

utiltiy · 27. Januar 2021

Zitat von gggggg

Was bewirkt der ?

Eine Restart vom VDR

gggggg · 27. Januar 2021

Danke,

nachdem das mit mcli+CAM zu obigem Fehler führt muss ich die NUCs retournieren. Die weiteren Experimente werde ich mit dem HP PC machen.

Bez. IR Empfänger, habe ich gelesen was ihr empfiehlt, aber leicht zu kaufen sind halt die Folgenden:

Ich habe diesen zu Hause und der wird ja in der Bucht als MCE konform angepriesen, weil beim Test v. EasyVDR wollte er OOTB nicht oder soll ich diesen von HP bestellen ?

pbrb · 28. Januar 2021

Zitat von pbrb

Front-Panel: need a electronical adapter to get the power button back to work

Front-Panel+Remote-Control: need serial connection to existing cables + related reelbox daemon

I will publish helper scripts (for frontpanel) sometime in the future, also the schematics for the adapter...currently my setup is still not publishable...lack of time...

here it is, good luck: https://github.com/pbiering/ReelBoxNG

schematics will come next...

BTW: in case of BM2LTS take over some scripts and has to modify, please modify in the way it's not breaking current compatibility, then please push any changes back via PR - thank you!

Alexandro77 · 28. Januar 2021

pbrb Thank you very much for you work. It is great that a long-time dead additional VDR feature is now alive again.

seahawk1986 Dear seahawk, do you think that pbrb work can be adapted as yavdr ansible plugin? It will be great. Thank you in advance.

Best regards.

seahawk1986 · 28. Januar 2021

Zitat von Alexandro77

Dear seahawk, do you think that pbrb work can be adapted as yavdr ansible plugin? It will be great. Thank you in advance.

That is a lot of special configuration for a piece of hardware I do not own (and there are some overlapping things like systemd services for starting Xorg, which is handled differently by yavdr-ansible, so there is some work to do to sort everything out) - I can see integrating this in the playbook if someone provides an ansible role, but doing this without access to the hardware is way to much effort for me.

Alexandro77 · 28. Januar 2021

Totally understandable.

Thank you very much for your answer. Hope pbrb can adapt it for YaVDR-Ansible as well.

pbrb · 28. Januar 2021

I have no YaVDR ansible and have no plans to use it...but there is no need to takeover the systemd extensions except for the mcli and remote preparation...but even such particular script calls by systemd can be integrated into existing or handled differently...only the sequence would be important.

gggggg · 28. Januar 2021

Hi, lastlog ist nicht lesbar. Könntest du das bitte in der nächsten Version beheben.

gggggg · 28. Januar 2021

Welche Ursachen vermutet ihr hinter dem "ERROR: video data stream broken", ich frage mich warum er bisher nur während Aufnahmen kam ?

14:22:00 Timer 1 startet 14:22

14:23:00 Error

14:23:17 exit code 1

14:23:27 Timer 1 wird fortgesetzt

Der Error kommt exakt 1 min. nach dem Start !

Hier habe ich im Setup den Notausstieg erlaubt:

Code

14:22:00 vdr: [1472] switching device 2 to channel 2 S19.2E-1-1005-13304 (ORF2O HD)
14:22:00 vdr: [1472] timer 1 (2 1422-1425 'Sturm der Liebe') start
14:22:00 vdr: [1472] Title: 'Silvia kocht' Subtitle: ''
14:22:00 vdr: [1472] executing '/media/hd/recordings before "/media/hd/recordings/Sturm_der_Liebe/2021-01-28.14.22.2-0.rec"'
14:22:00 vdr[1704]: sh: 1: /media/hd/recordings: Permission denied
14:22:00 vdr: [1472] record /media/hd/recordings/Sturm_der_Liebe/2021-01-28.14.22.2-0.rec
14:22:00 vdr: [1472] creating directory /media/hd/recordings/Sturm_der_Liebe
14:22:01 vdr: [1472] creating directory /media/hd/recordings/Sturm_der_Liebe/2021-01-28.14.22.2-0.rec
14:22:01 cron[444]: (*system*sa) INSECURE MODE (group/other writable) (/etc/cron.d/sa)
14:22:03 vdr: [1472] recording to '/media/hd/recordings/Sturm_der_Liebe/2021-01-28.14.22.2-0.rec/00001.ts'
14:22:03 vdr: [1705] recording thread started (pid=1472, tid=1705, prio=high)
14:22:03 vdr: [1472] markad: cStatusMarkAd::Recording(): recording <Sturm der Liebe> [/media/hd/recordings/Sturm_der_Liebe/2021-01-28.14.22.2-0.rec] started
14:22:03 vdr: [1472] markad: cannot find timer for <Sturm der Liebe>
14:22:03 vdr: [1706] device 2 receiver thread started (pid=1472, tid=1706, prio=high)
14:22:05 vdr[1708]: ? getopt returned character code 0107 ? (option_index 0)
14:22:05 vdr: [1472] markad: executing "/usr/bin"/markad  -v  -G  -O --svdrpport=6419  -R  --vps  --autologo=2  -l "/opt/vdr/plugins/markad" --online=2 before "/media/hd/recordings/Sturm_der_Liebe/2021-01-28.14.22.2-0.rec"
14:22:05 vdr: [1472] markad: cStatusMarkAd::Add():: create epg event handler
14:22:05 vdr[1472]: Mcli::recv_ts_func: Discontinuity on receiver 0x5573f8d0b7b0 for pid 3000: 5->4 at pos 0/7
14:22:06 vdr: [1472] writing timer id '1@10.75.25.22' to /media/hd/recordings/Sturm_der_Liebe/2021-01-28.14.22.2-0.rec/.timer
14:22:06 vdr: [1534] VNSI: Requesting clients to reload timers
14:22:06 vdr: [1534] VNSI: Requesting clients to reload timers
14:22:06 vdr: [1534] VNSI: Requesting clients to reload recordings list
14:22:07 vdr: [1705] executing '/media/hd/recordings started "/media/hd/recordings/Sturm_der_Liebe/2021-01-28.14.22.2-0.rec"'
14:22:07 vdr[1711]: sh: 1: /media/hd/recordings: Permission denied
14:22:08 vdr: [1534] VNSI: Requesting clients to reload recordings list
14:22:11 vdr: [1534] VNSI: Requesting clients to reload timers
14:22:13 vdr: [1505] loading /media/hd/recordings/Der_Bergdoktor/2021-01-27.20.15.2-0.rec/marks
14:22:13 vdr: [1505] loading /media/hd/recordings/Ruhe!_Hier_stirbt_Lothar/2021-01-27.20.15.4-0.rec/marks
14:22:13 vdr: [1505] loading /media/hd/recordings/Der_Ranger_-_Paradies_Heimat:_Junge_Liebe_Fernsehfilm_Deutschland_2021/2021-01-22.20.11.4-0.rec/marks
14:22:13 vdr: [1505] loading /media/hd/recordings/Columbo_-_Schwanengesang/2021-01-17.01.20.3-0.rec/marks
14:22:13 vdr: [1505] loading /media/hd/recordings/Die_Mumie/2021-01-14.20.14.1-0.rec/marks
14:22:13 vdr: [1505] loading /media/hd/recordings/Das_Traumschiff/2021-01-01.20.13.2-0.rec/marks
14:22:13 vdr: [1505] loading /media/hd/recordings/Falk_(12)/Rosa_Rauschen/2020-12-22.20.13.4-0.rec/marks
14:22:13 vdr: [1505] loading /media/hd/recordings/Ben_Hur/2020-12-20.20.13.37-0.rec/marks
14:22:13 vdr: [1505] loading /media/hd/recordings/Tatort/2020-12-13.20.13.2-0.rec/marks
14:22:16 vdr: [1534] VNSI: Requesting clients to reload timers
14:22:26 vdr: message repeated 2 times: [ [1534] VNSI: Requesting clients to reload timers]
14:22:27 dhclient[1426]: DHCPDISCOVER on eth0.2 to 255.255.255.255 port 67 interval 9 (xid=0xab9fb951)
14:22:27 sh[1426]: DHCPDISCOVER on eth0.2 to 255.255.255.255 port 67 interval 9 (xid=0xab9fb951)
14:22:31 vdr: [1534] VNSI: Requesting clients to reload timers
14:22:31 vdr[1472]: Mcli::recv_ts_func: Discontinuity on receiver 0x5573f8ca2730 for pid 767: 2->10 at pos 0/7
14:22:36 vdr: [1534] VNSI: Requesting clients to reload timers
14:22:36 systemd[1]: systemd-resolved.service: Succeeded.
14:22:37 systemd-resolved[1723]: Positive Trust Anchors:
14:22:37 systemd-resolved[1723]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
14:22:37 systemd-resolved[1723]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
14:22:37 systemd-resolved[1723]: Using system hostname 'BM2LTSR66Nuc64native-MCLI'.
14:22:37 systemd-resolved[1723]: DNSStubListener= is disabled, but /etc/resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.conf which expects DNSStubListener= to be enabled.
14:22:37 systemd[1]: Started Network Name Resolution.
14:22:37 systemd[1]: Reloading Samba SMB Daemon.
14:22:37 systemd[1]: Reloaded Samba SMB Daemon.
14:22:37 avahi-autoipd(eth0.2)[1734]: Found user 'avahi-autoipd' (UID 106) and group 'avahi-autoipd' (GID 112).
14:22:37 avahi-autoipd(eth0.2)[1734]: Successfully called chroot().
14:22:37 avahi-autoipd(eth0.2)[1734]: Successfully dropped root privileges.
14:22:37 avahi-autoipd(eth0.2)[1734]: Starting with address 169.254.6.226
14:22:41 vdr: [1534] VNSI: Requesting clients to reload timers
14:22:43 avahi-autoipd(eth0.2)[1734]: Callout BIND, address 169.254.6.226 on interface eth0.2
14:22:43 avahi-daemon[439]: Joining mDNS multicast group on interface eth0.2.IPv4 with address 169.254.6.226.
14:22:43 avahi-daemon[439]: New relevant interface eth0.2.IPv4 for mDNS.
14:22:43 avahi-daemon[439]: Registering new address record for 169.254.6.226 on eth0.2.IPv4.
14:22:46 vdr: [1534] VNSI: Requesting clients to reload timers
14:22:47 avahi-autoipd(eth0.2)[1734]: Successfully claimed IP address 169.254.6.226
14:22:47 sh[1445]: ifup: interface eth0.2 already configured
14:22:51 vdr: [1534] VNSI: Requesting clients to reload timers
14:22:56 vdr: [1534] VNSI: Requesting clients to reload timers
14:23:00 vdr: [1705] ERROR: video data stream broken
14:23:00 vdr: [1705] initiating emergency exit
14:23:01 vdr: [1534] VNSI: Requesting clients to reload timers
14:23:01 vdr: [1472] emergency exit requested - shutting down
14:23:01 cron[444]: (*system*sa) INSECURE MODE (group/other writable) (/etc/cron.d/sa)
14:23:02 vdr: [1655] SVDRP client handler thread ended (pid=1472, tid=1655)
14:23:02 vdr: [1654] SVDRP server handler thread ended (pid=1472, tid=1654)
14:23:02 vdr: [1472] saving /var/cache/vdr/cam.data
14:23:02 vdr: [1705] recording thread ended (pid=1472, tid=1705)
14:23:02 vdr: [1706] device 2 receiver thread ended (pid=1472, tid=1706)
14:23:02 vdr: [1472] buffer stats: 1901056 (9%) used
14:23:02 vdr: [1472] timer 1 (2 1422-1425 'Sturm der Liebe') stop
14:23:02 vdr: [1472] removing /media/hd/recordings/Sturm_der_Liebe/2021-01-28.14.22.2-0.rec/.timer
14:23:02 vdr: [1472] markad: cStatusMarkAd::Recording(): recording <(null)> [/media/hd/recordings/Sturm_der_Liebe/2021-01-28.14.22.2-0.rec] stopped
14:23:02 vdr: [1472] executing '/media/hd/recordings after "/media/hd/recordings/Sturm_der_Liebe/2021-01-28.14.22.2-0.rec"'
14:23:02 vdr: [1776] EPGSearch: recdone thread started (pid=1472, tid=1776, prio=high)
14:23:02 vdr: [1776] EPGSearch: recdone thread ended (pid=1472, tid=1776)
14:23:02 vdr[1778]: sh: 1: /media/hd/recordings: Permission denied
...
14:23:06 vdr: [1472] ERROR:  thread 1505 won't end (waited 3 seconds) - canceling it...
14:23:16 vdr: [1472] emergency exit!
14:23:16 vdr: [1472] exiting, exit code 1
?

Alles anzeigen

gggggg · 28. Januar 2021

Ich habe jetzt Markad disabled und 5 Aufnahmen waren OK. teste weiter! Ich bin bisher ohnehin ein fan von noad.

cinfo Es wäre super, wenn du noad mit aufnehmen könntest. So wäre ein Gegentest möglich.

seahawk1986 · 28. Januar 2021

Man kann in den OSD-Einstellungen von markad auch festlegen, dass es erst nach den Aufnahmen laufen soll, falls man Geschwindigkeitsprobleme hat. Wenn der VDR die Daten bei laufenden Aufnahmen nicht schnell genug wegschreiben kann, müsste man das aber eigentlich im sehen, weil dann der Buffer mit den DVB-Daten vollläuft.

gggggg · 28. Januar 2021

Zitat von seahawk1986

Man kann in den OSD-Einstellungen von markad auch festlegen, dass es erst nach den Aufnahmen laufen soll, falls man Geschwindigkeitsprobleme hat. Wenn der VDR die Daten bei laufenden Aufnahmen nicht schnell genug wegschreiben kann, müsste man das aber eigentlich im sehen, weil dann der Buffer mit den DVB-Daten vollläuft.

Danke, ich bin grade dabei das markad.log inkl. Aufnahme hochzuladen ... Buffer ... wo soll der Laie da nachsehen ?

seahawk1986 · 28. Januar 2021

Zitat von gggggg

wo soll der Laie da nachsehen

In den Logmeldungen, die der VDR so von sich gibt (das landet dann üblicherweise im Syslog).

cinfo · 28. Januar 2021

Hi,

wäre es möglich über Probleme von Plugins / Log´s & auch Harwareumbauten ein neues Thema aufzumachen?

Es wäre meiner Sicht nach besser für den Support. Es wäre auch gut im Thema zum Plugin über seine Ergebnisse zu Berichten,

damit das dann auch dort in die Entwicklungsarbeit einfliessen kann.

Grüße

cinfo

gggggg · 28. Januar 2021

Alter MAnn ist kein D-Zug ... sofort erledigt nachdem ich es auf das Plugin eingegrenzt habe ... ist noad noch möglich ?

cinfo · 28. Januar 2021

Hi,

neue Version BM2LTS 3.4.18 zum Download

Download hier:

Grüße

cinfo

gggggg · 29. Januar 2021

Danke, der AC3 Downmix fix ist lt. 9000H in den hier genannten Versionen verfügbar. Könntest du mir das bitte als patch bauen ?!

Dann noch eine DAU Frage. Beim Reel-VDR konnte man per steuerkreuz rechts/links zur nächsten Sprungmarke v. Noad springen ... wie geht das beim aktuellen vdr ?

utiltiy · 29. Januar 2021

7 und 9 sollte das sein was du meinst

{2024} BM²LTS-v4.4.x-Ubuntu 22.04.4- > DD-NET & NetCeiver

Jetzt mitmachen!

Teilen

Tags

Benutzer online in diesem Thema