Control: reassign -1 src:systemd
On Mon, 2014-11-10 at 02:13 +0100, Tomas Fasth wrote:
> Package: general
> Severity: normal
>
> I use Virtualbox to run test environments for the packages I maintain
> (just a few really). I install virtualbox-guest-utils in my guest
> installations to adjust system clock after hibernation.
>
> In Jessie, there seem to be a problem with the virtualbox guest service.
> It fails to start and, as usual, I look in the system log for clues.
[...]
> // log extract begins
> nov 10 01:36:47 debian-systemd sudo[1429]: tomfa : TTY=pts/0 ; PWD=/home/tomfa ; USER=root ; COMMAND=/usr/sbin/service virtualbox-guest-utils start
> nov 10 01:36:47 debian-systemd sudo[1429]: pam_unix(sudo:session): session opened for user root by tomfa(uid=0)
> nov 10 01:36:47 debian-systemd virtualbox-guest-utils[1447]: Starting VirtualBox AdditionsNo suitable module for running kernel found ... failed!
> nov 10 01:36:47 debian-systemd virtualbox-guest-utils[1447]: failed!
> nov 10 01:36:47 debian-systemd sudo[1429]: pam_unix(sudo:session): session closed for user root
> nov 10 01:36:47 debian-systemd systemd[1]: virtualbox-guest-utils.service: control process exited, code=exited status=1
> nov 10 01:36:47 debian-systemd systemd[1]: Failed to start LSB: VirtualBox Linux Additions.
> -- Subject: Unit virtualbox-guest-utils.service has failed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
The 'LSB:' prefix indicates the systemd unit was defined by an init
script with LSB headers. The support URL is generated by systemd's
generic support for init scripts, which could easily be changed.
However, native systemd unit definitions can and probably will also
specify their own uptream support URL.
> -- Unit virtualbox-guest-utils.service has failed.
> --
> -- The result is failed.
> nov 10 01:36:47 debian-systemd systemd[1]: Unit virtualbox-guest-utils.service entered failed state.
> // log extract ends
>
> I don't understand why there should be a reference to an external support
> entity when the issue obviously is Debian related and should be reported
> as such in Debian-related forums. My specific issue has nothing to do
> with systemd or FreeDesktop.ORG. I want the external reference removed.
> If it stays it will only create confusion and misunderstanding.
This is useful for third-party packages and unpackaged software but I
agree that for packaged software systemd error logging should clearly
refer to both Debian and upstream sources for support.
Ben.
--
Ben Hutchings
Experience is directly proportional to the value of equipment destroyed.
- Carolyn Scheppner
Attachment:
signature.asc
Description: This is a digitally signed message part