Package Base Details: kodi-standalone-service

Git Clone URL: https://aur.archlinux.org/kodi-standalone-service.git (read-only, click to copy)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 61
Popularity: 0.001726
First Submitted: 2014-11-05 20:25
Last Updated: 2020-02-02 19:47

Latest Comments

« First ‹ Previous ... 4 5 6 7 8 9 10 11 12 13 Next › Last »

tetris11 commented on 2015-12-17 15:40

After uninstalling and reinstalling I can't seem to recreate the error message. Sorry, ignore please. Works well, as expected.

graysky commented on 2015-12-17 12:33

@tetris - Shouldn't have anything to do with deps as everything it needs is already a dep. Not sure why you have an error... is the error keeping kodi from launching since you say, "kodi.service itself seems to run fine" I do not understand.

Error = break ; warning = still runs.

tetris11 commented on 2015-12-17 12:26

Upon starting the service I'm getting:

Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)

The kodi.service itself seems to run fine.

My desktop is literally just xinit and metacity, so maybe it's just a complaint about not finding gnome/kde?

graysky commented on 2015-11-21 12:53

@hendry - Your log shows you're running this on an ARM processor. I implicitly defined only i686 and x86_64 for this package because kodi on Arch ARM has its own implementation of the standalone service. Recommend that you remove this package on that device.

hendry commented on 2015-11-21 10:51

http://s.natalian.org/2015-11-21/kodi_crashlog-20151121_104439.log

On my alarm rpi2:

10:44:38 T:1945907792 ERROR: Failed to choose a config 12288
10:44:38 T:1945907792 ERROR: Failed to query native visual id
10:44:38 T:1945907792 ERROR: Failed to find matching visual

Any ideas what's that about?

graysky commented on 2015-10-18 19:49

I can't explain. I just tested on a new partition (with kodi-standalone-service in a local repo). After configuring the root passwd, network, etc. and enabling kodi.service, it booted right into it.

# pacstrap -i /mnt base sudo kodi-standalone-service xf86-video-intel

bananabrain commented on 2015-10-18 18:47

Sorry for the delay in replying. I still have this problem of being unable to start the kodi service without an Xwrapper.config file in place. Yes, I have the xf86-video-ati driver installed and have used this machine with an X environment in the past without issue. It would be good to know what's missing from a machine with just the basic xorg system and graphics card driver that prevents the kodi service from working as expected, but I haven't been able to work this out for myself.

Manually running "systemctl start kodi" puts the following into the journal (time stamps and hostname removed):


polkitd[434]: Registered Authentication Agent for unix-process:444:5962 (system bus name :1.6 [/usr/bin/pkttyagent --notify-fd 4 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8)

systemd[1]: Started Starts instance of Kodi using xinit.

polkitd[434]: Unregistered Authentication Agent for unix-process:444:5962 (system bus name :1.6, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) (disconnected from bus)

systemd[450]: pam_unix(login:session): session opened for user kodi by (uid=0)

systemd[1]: Created slice user-420.slice.

systemd[1]: Starting User Manager for UID 420...

systemd-logind[313]: New session c3 of user kodi.

systemd[1]: Started Session c3 of user kodi.

systemd[453]: pam_unix(systemd-user:session): session opened for user kodi by (uid=0)

systemd[453]: Reached target Timers.

systemd[453]: Listening on D-Bus User Message Bus Socket.

systemd[453]: Reached target Sockets.

systemd[453]: Reached target Paths.

systemd[453]: Reached target Basic System.

systemd[453]: Reached target Default.

systemd[453]: Startup finished in 48ms.

systemd[1]: Started User Manager for UID 420.

graysky commented on 2015-09-21 21:44

No, that isn't it. I see on some other minimal boxes that particular driver is not installed. Have you installed a video driver?

graysky commented on 2015-09-21 10:31

Works for me in a fresh VM with just base and the deps plus I had to install a driver. For the VM I used xf86-video-fbdev only. Perhaps this needs to be added to the deps array? Is it present on other full desktops?

OlafLostViking commented on 2015-09-21 09:42

@graysky Unfortunately I have the same problem as @bananabrain. But I can start an X-session as non-root with startx, with xinit it only works as root. So probably the reason for the failure lies "deeper". Some setup steps or packages are missing, perhaps. As I only installed kodi on this system and no other desktop or graphical packages (despite xterm to test X).