Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Running testing/unstable applications in Debian stable

Share your HowTo, Documentation, Tips and Tricks. Not for support questions!.
Message
Author
User avatar
bester69
Posts: 2072
Joined: 2015-04-02 13:15
Has thanked: 24 times
Been thanked: 14 times

Re: Running testing/unstable applications in Debian stable

#21 Post by bester69 »

Head_on_a_Stick wrote:
bester69 wrote:Ive got this error, any idea how can i fix it?
You need to add some extra flags to systemd-npawn to allow hardware acceleration in the container.

This guide explains how:

https://maci0.wordpress.com/2014/05/02/ ... idgin-vlc/
I used this, and still same error:

Code: Select all

sudo systemd-nspawn --bind /tmp/.X11-unix:/tmp/.X11-unix \
--bind=/dev/shm:/dev/shm --bind=/dev/dri:/dev/dri \
--bind=/run/user/${UID}/pulse:/run/user/${UID}/pulse \
--boot -D /media/buster
bester69 wrote:STOP 2030 globalists demons, keep the fight for humanity freedom against NWO...

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Running testing/unstable applications in Debian stable

#22 Post by Head_on_a_Stick »

^
My link wrote:make sure the OS image you use has the opengl libs for your physical video card, in the steam container the mesa libs are pre-installed
Looks like you may also need `dbus-launch` before the `kodi` command as well but I've never actually tried this (what exactly is wrong with v17.1?) so if you can figure it out please post back with details for the benefit of others.

Otherwise, use stevepusser's binary package instead perhaps?
deadbang

User avatar
bester69
Posts: 2072
Joined: 2015-04-02 13:15
Has thanked: 24 times
Been thanked: 14 times

Re: Running testing/unstable applications in Debian stable

#23 Post by bester69 »

Head_on_a_Stick wrote:^
My link wrote:make sure the OS image you use has the opengl libs for your physical video card, in the steam container the mesa libs are pre-installed
Looks like you may also need `dbus-launch` before the `kodi` command as well but I've never actually tried this (what exactly is wrong with v17.1?) so if you can figure it out please post back with details for the benefit of others.

Otherwise, use stevepusser's binary package instead perhaps?
ok Head, It really doesn matter, I was testing the systemd-nspawn you told me, but i see i cant make it work, so I will keep using chroot, that works great.. , dont waste more time with this; thanks again
My last try by using dbus-launch:

Code: Select all

Unpacking dbus-x11 (1.12.2-1) ...
Setting up dbus-x11 (1.12.2-1) ...
root@buster:~# su puigdemont -c "DISPLAY=:0 QT_X11_NO_MITSHM=1 dbus-launch /usr/bin/kodi --no-qt-privacy-ask"
ALSA lib conf.c:4974:(snd_config_expand) Unknown parameters CARD=Intel,DEV=0
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM surround51:CARD=Intel,DEV=0
ALSA lib conf.c:4974:(snd_config_expand) Unknown parameters CARD=Intel,DEV=0
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM surround71:CARD=Intel,DEV=0
ALSA lib confmisc.c:767:(parse_card) cannot find card 'Intel'
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned error: No such device
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such device
ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM sysdefault:CARD=Intel
ALSA lib confmisc.c:767:(parse_card) cannot find card 'Intel'
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned error: No such device
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such device
ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default:CARD=Intel
ALSA lib conf.c:4974:(snd_config_expand) Unknown parameters CARD=Intel,DEV=0
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM front:CARD=Intel,DEV=0
libGL error: failed to open drm device: Operation not permitted
libGL error: failed to load driver: i965
libEGL warning: DRI2: could not open /dev/dri/card0 (Operation not permitted)
bester69 wrote:STOP 2030 globalists demons, keep the fight for humanity freedom against NWO...

User avatar
llivv
Posts: 5340
Joined: 2007-02-14 18:10
Location: cold storage

Re: Running testing/unstable applications in Debian stable

#24 Post by llivv »

http://forums.debian.net/viewtopic.php?p=622055#p622055
fsmithred
chroots can behave weird at times like anything else inside or around a computer or phone.
{
I noticed you use the mount bind option and I think it's only necessary to bind dev so you can mount dev/pts
( at least up to wheezy anyways ).
If you try another pre chroot mounting scheme it might let you run heavier window managers in the chroot, depending on the chroot host / chroot target combination.
Also be careful about how you mount and than always still be on the lookout for undesired changes to the host system
that occur back from the chroot. It happens even though it's not supposed to.

While typing this I just thought of a way to try to remove the bind option from the mount /dev command as well,, by copying the devs from the host system into place,, pre chroot than seeing if the chroot still works correctly.
Another thing to remember is the chroot target will behave almost exactly like the chroot host garrrrr

If anyone knows howto run a chroot target that runs a different ARCH from the chroot host - Please write it up !
}
after mounting

Code: Select all

#mount -t devtmpfs /dev $chrootdir/dev -o bind
I also mount

Code: Select all

#mount -t devpts /dev/pts $chrootdir/dev/pts
#mount -t tmpfs /dev/shm $chrootdir/dev/shm
because networking usually didn't work without it ( the way I premount the chroot env )

as you'll notice when running

Code: Select all

cat /etc/mtab
system mountpoints are changing a lot
I think squeeze to wheezy changed /dev/shm to /run/shm
and I haven't fiddled enough yet to know what's needed now and what's not
Edit Jan 18 21:19:07 EST 2018
double check the debootstrap man files Examples section for more hints
-keep in mind that the Examples section can show differences DEPENDING on which Debian Version you are viewing the man page from!
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.

ruffwoof
Posts: 298
Joined: 2016-08-20 21:00

Re: Running testing/unstable applications in Debian stable

#25 Post by ruffwoof »

A alternative is to run a read only boot session, and test things out in that, knowing that when you reboot all the changes will have been lost. live-boot is great for that, you can create a empty /live/filesystem.squashfs (needs to exist and have been created as a squashed filesystem) and use your main HDD installed version as the 'persistence' partition for live-boot, but set it to be a read only persistence storage space

Code: Select all

apt-get update
apt-get install live-boot
apt-get install squashfs-tools
mkdir /live
cd /live
mkdir etc
mksquashfs etc filesystem.squashfs
rmdir etc
cd /
echo / union >persistence.conf
echo >>persistence.conf
e2label /dev/sda1 persistence
Edit /etc/grub.d/40-custom to include a entry of

Code: Select all

menuentry 'live-boot' {
set root=(hd0,1)
linux /vmlinuz boot=live persistence persistence-read-only
initrd /initrd.img
}
... and run

Code: Select all

update-grub
Now when you boot there will be a live-boot boot menu option and selecting that will boot a read only session. Try things out etc. and after a reboot all changes are lost.

The above assumes Debian Stretch installed to sda1. Also if you do too much (exhaust memory) then it will falter (range of tests you can run are finite).

man live-boot for alternative arrangements (persistence boot options).

User avatar
sickpig
Posts: 589
Joined: 2019-01-23 10:34

Re: Running testing/unstable applications in Debian stable

#26 Post by sickpig »

@HOAS
Thanks for the how to, I could not run systemd in schroot but I can with systemd-nspawn.

I noticed that this how to does not work if systemd-container package is not installed. I am not sure if it is installed by default or not. If it is then chances are I might have removed it at some point thinking it is superfluous. In that case please disregard this post. Otherwise you might want to update the OP listing systemd-container as a dependency.

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Running testing/unstable applications in Debian stable

#27 Post by Head_on_a_Stick »

Thanks sickpig, I've added a step to install the packages (and updated the Debian redirector URL).
deadbang

User avatar
sickpig
Posts: 589
Joined: 2019-01-23 10:34

Re: Running testing/unstable applications in Debian stable

#28 Post by sickpig »

Appreciate your easy to understand how-tos, what a Legend!

Post Reply