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

Bug#860482: marked as done (Missing dependencies for *xinit* and *dbus-x11* used in systemd service unit)

Your message dated Sat, 4 May 2019 19:40:26 +0200
with message-id <[🔎] CAK0OdpycioJEopEPZa+avoHHdVyRN_y6Upc8XJOWZBDQeYTjVw@mail.gmail.com>
and subject line Re: Bug#860482: Missing dependencies for *xinit* and *dbus-x11* used in systemd service unit
has caused the Debian Bug report #860482,
regarding Missing dependencies for *xinit* and *dbus-x11* used in systemd service unit
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.)


-- 
860482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860482
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kodi
Severity: normal

Dear Debian folks,


The systemd service unit file `/lib/systemd/system/kodi.service`
currently needs the binaries `/usr/bin/xinit` and `/usr/bin/dbus-
launch` [1].

```
ExecStart=/usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7
```

Both executables are currently not present as the packages providing
these files – *xinit* and *dbus-x11* – are not dependencies.

As the service file is disabled by default, I am unsure what rule
applies here. I’d prefer a dependency over a recommendation. Currently,
the installed size of *xinit* is 80 kB, and of *dbus-x11* 140 kB.

Also, I am unsure about the correct severity of this issue. Therefore,
I am leaving it at the default, which is *normal*.


Thanks,

Paul


[1] https://sources.debian.net/src/kodi/2:17.1%2Bdfsg1-2/debian/kodi.service/

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


--- End Message ---
--- Begin Message --- 
Control: found -1 2:17.0+dfsg1-3
Control: fixed -1 2:17.6+dfsg1-2

Dear Paul and Johannes,


2017-12-25 23:52 GMT+01:00 Johannes Schauer <josch@debian.org>:
> On Mon, 17 Apr 2017 18:39:24 +0200 Paul Menzel <pm.debian@googlemail.com> wrote:
>> The systemd service unit file `/lib/systemd/system/kodi.service`
>> currently needs the binaries `/usr/bin/xinit` and `/usr/bin/dbus-
>> launch` [1].
>>
>> ```
>> ExecStart=/usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7
>> ```
>>
>> Both executables are currently not present as the packages providing
>> these files -- *xinit* and *dbus-x11* -- are not dependencies.
>>
>> As the service file is disabled by default, I am unsure what rule
>> applies here. I'd prefer a dependency over a recommendation. Currently,
>> the installed size of *xinit* is 80 kB, and of *dbus-x11* 140 kB.
>
> That is not entirely correct. You also have to consider the reverse
> dependencies here. If installing these packages on a minimal system, then
> including Recommends, apt reports that "334 MB of additional disk space will be
> used."
>
> Without Recommends this goes down to 6354 kB but then you are also left without
> xserver-xorg or x-session-manager/x-window-manager.
>
> But even when these packages are installed, the provided kodi.service is still
> not functional because:
>
> /usr/bin/Xorg.wrap: Only console users are allowed to run the X server
>
> So in addition to installing these packages, one also has to edit
> /etc/X11/Xwrapper.config and add:
>
> allowed_users = anybody
>
> But even then it is questionable whether starting kodi like this via systemd is
> the right approach. Kodi is not a system-wide service. As it is implemented
> here, it is not possible to have a separate instance for each session. And
> according to FernetMenta, the author of Kodi's X11 windowing system kodi should
> never be started without a window manager [1]. The article under [1] also
> includes the kodi.service file from the Debian package but is declared as
> outdated.
>
> On the other hand, I was also unable to find the "right" way to start kodi
> automatically on bootup as the only running graphical application. I would
> suspect that the right way involves crafting a custom session that start all
> the necessary programs? So like a .desktop file in /usr/share/xsessions/.

According to upstream's current recommendation I removed the .service
file and suggest starting Kodi from a user session, possibly with
auologin.

This makes the bug solved since there is no need for the extra
dependencies anymore.

Cheers,
Balint

>
> But I'm not an expert either. Just my 2c.
>
> Thanks!
>
> cheers, josch
>
>
> [1] http://kodi.wiki/view/Archive:HOW-TO:Autostart_Kodi_for_Linux

--- End Message ---
Reply to: