Package Details: kodi-standalone-service 1.137-2

Git Clone URL: https://aur.archlinux.org/kodi-standalone-service.git (read-only, click to copy)
Package Base: kodi-standalone-service
Description: Systemd services to run kodi in stand-alone mode without a DE
Upstream URL: https://github.com/graysky2/kodi-standalone-service
Licenses: MIT
Replaces: kodi-standalone-gbm-service, kodi-standalone-wayland-service, kodi-standalone-x11-service
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 68
Popularity: 0.29
First Submitted: 2014-11-05 20:25 (UTC)
Last Updated: 2024-07-06 08:38 (UTC)

Dependencies (6)

Required by (1)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 Next › Last »

CandyAngel commented on 2016-04-04 22:31 (UTC)

I've found that, with the nVidia driver installed, this service won't start Kodi as systemd-logind will interfere and make X think the nVidia driver isn't viable (then X won't find any screens). I had to override ExecStart with the below to get it to work with nVidia: /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone (removed everything after '--' in the original). Credit (and thanks) to grazzolini in #archlinux for this solution.

graysky commented on 2016-02-01 20:33 (UTC)

I will add a post_install message to users of the open source ATI driver but I need to know: is it the xf86-video-ati package that provides this driver?

graysky commented on 2016-01-17 13:54 (UTC)

I can't comment since I do not have ATI hardware for testing. Is the use of the open source ATI driver true for everyone who has experienced this problem? Are there any users of the open source ATI driver that do NOT need to create this file?

Kalq commented on 2016-01-16 22:18 (UTC)

Confirming that I too need the Xwrapper.config file. I'm using the open source ATI driver. When I was using the Catalyst driver I didn't need it.

graysky commented on 2016-01-02 19:12 (UTC)

@epinephrine - That is not needed. Confirmed on a fresh install just now. Upon rebooting into it, I was greeted with kodi with no additional setup. I suspect you are missing something with regard to your ati drivers... unless the ATI drivers for some reason require that file which would surprise me. I have not ATI hardware for testing. mount /dev/sda4 /mnt/mini pacstrap -i /mnt/mini base xf86-video-intel kodi kodi-standalone-service echo "LABEL=mini / ext4 defaults,relatime 0 1" >> /mnt/mini/etc/fstab echo mini > /mnt/mini/etc/hostname sed -i 's/#en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/' /mnt/mini/etc/locale.gen echo "LANG=en_US.UTF-8" > /mnt/mini/etc/locale.conf arch-chroot /mnt/mini /bin/bash passwd sed -i '/^MODULES/ s,"","i915",' /etc/mkinitcpio.conf mkinitcpio -p linux locale-gen systemctl enable kodi exit reboot

sebstar commented on 2016-01-02 17:07 (UTC)

Just want to mention that I also needed the Xwrapper.config file with 'needs_root_rights = yes'. I use the ati drivers and have a minimal X installation, i.e., the only xorg related software that I installed is kodi. Maybe this package should include the Xwrapper.config file or at least a post-installation comment that this file might be needed.

tetris11 commented on 2015-12-17 15:40 (UTC) (edited on 2015-12-17 15:41 (UTC) by tetris11)

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 (UTC)

@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 (UTC)

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?

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 Next › Last »