[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1057810: marked as done (kodi: doesn't recognize any input device from (pure) commandline)

Your message dated Sat, 09 Dec 2023 04:18:06 +0100
with message-id <2005582.YYGm4AF5Hp@bagend>
and subject line Re: kodi: doesn't recognize any input device from (pure) commandline
has caused the Debian Bug report #1057810,
regarding kodi: doesn't recognize any input device from (pure) commandline
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1057810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057810
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kodi
Version: 2:20.2+dfsg-4+b2
Severity: important

I was trying to test something* in kodi on my Pine64 Rock64 (arm64) and
noticed a few things.

When I run it from the command line with either `kodi --standalone -fs`
or `kodi --standalone -fs --windowing=gbm`, kodi starts up but it
doesn't recognize my keyboard or my LIRC remote.
Both which do work when used with LibreELEC.
Same result if I drop the `--standalone` parameter.
The only way to exit kodi is via ssh killing the kodi process(es) or
with `kodi-send -a "Quit()"`.

```
$ kodi --standalone -fs --windowing=gbm
libva info: VA-API version 1.20.0
libva error: vaGetDriverNames() failed with operation failed
```

I also tried it with the patch from https://bugs.debian.org/1056563
(actually from MR10), but that did not make a difference.
(PS: could you push the latest version to Salsa/git?)


When I first start `sway` (and `foot`), then `kodi --standalone -fs`
does work, but not with the `--windowing=gbm` parameter, but I guess
that's expected:

```
$ kodi --standalone -fs --windowing=gbm
ERROR: Unable to create GUI. Exiting

$ kodi --standalone -fs
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib/aarch64-linux-gnu/dri/rockchip_drv_video.so
libva info: va_openDriver() returns -1
$ kodi --version
Kodi from Debian Media Center 20.2 Debian package version: 2:20.2+dfsg-4+b2
Copyright (C) 2005-2021 Team Kodi from Debian - http://kodi.tv
$ ls -lh /usr/lib/aarch64-linux-gnu/dri/rockchip_dri.so
-rw-r--r--  43 root root 27M Sep 29 07:38 /usr/lib/aarch64-linux-gnu/dri/rockchip_dri.so
$ dpkg -S /usr/lib/aarch64-linux-gnu/dri/rockchip_dri.so
libgl1-mesa-dri:arm64: /usr/lib/aarch64-linux-gnu/dri/rockchip_dri.so
$ find /usr -name '*rockchip_drv_video*' 2>/dev/null
$ (no results)
```

FTR: I don't think 'from Debian' ought to be on the Copyright line?

I don't know if 'VA-API' is a general term that kodi uses (when
logging), but I'm quite sure the video driver (Lima) does not support
the VA API.

*) The thing I'm trying to test is HW accell via the v4l2-request API.

Cheers,
  Diederik

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 6.7.0-0-pine64-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kodi depends on:
ii  kodi-bin   2:20.2+dfsg-4+b2
ii  kodi-data  2:20.2+dfsg-4

Versions of packages kodi recommends:
ii  kodi-repository-kodi [kodi-repository]  2:20.2+dfsg-4
ii  kodi-visualization-spectrum             20.2.0+ds1-1

kodi suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On 08 Dec 2023 20:19:50 +0100 Diederik de Haas <didi.debian@cknow.org> wrote:
> Package: kodi
> Version: 2:20.2+dfsg-4+b2
> Severity: important
> 
> I was trying to test something* in kodi on my Pine64 Rock64 (arm64) and
> noticed a few things.
> 
> When I run it from the command line with either `kodi --standalone -fs`
> or `kodi --standalone -fs --windowing=gbm`, kodi starts up but it
> doesn't recognize my keyboard or my LIRC remote.
> Both which do work when used with LibreELEC.
> ...
> When I first start `sway` (and `foot`), then `kodi --standalone -fs`
> does work...
> ...
> *) The thing I'm trying to test is HW accell via the v4l2-request API.

With that testing someone made a remark about the "input" group the user needs 
to be in ... and that made the inputs work (facepalm).
Thus closing this bug.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: