Bug#913102: pulseaudio does not restore correct mic/speaker state

Le 24/07/2019 à 22:08, Алексей Шилин a écrit : > Hi, >   > Could you please test if the issue can be reproduced after building > pulseaudio > with the attached patch? >   >   > -- > Алексей Шилин Hi Just tested it and volume settings do not change anymore within a few seconds after I'm logged

Bug#913102: pulseaudio does not restore correct mic/speaker state

Le 07/11/2018 à 05:32, Alexandre Vaissière a écrit : > Le 06/11/2018 à 23:55, Felipe Sateler a écrit : >> Control: tags -1 moreinfo >> >> On Tue, Nov 6, 2018 at 7:27 PM Alexandre Vaissiere > <mailto:ava...@fmiw.org>> wrote: >> >> Package: puls

Bug#918358: libsane:amd64: Missing permissions for scanner group on usb device

Package: libsane Version: 1.0.27-3.1 Severity: normal Dear Maintainer, I experience this issue since december 2018. I scan my docs every two monthes, so I would not have noticed any change between october and december. Context --- * investigation on the following issue

Bug#913102: pulseaudio does not restore correct mic/speaker state

Le 06/11/2018 à 23:55, Felipe Sateler a écrit : > Control: tags -1 moreinfo > > On Tue, Nov 6, 2018 at 7:27 PM Alexandre Vaissiere > wrote: > > Package: pulseaudio > Version: 12.2-2 > Severity: normal > > > * Expected behaviour > > When I restart my

Bug#744741: breaks yubikey-piv-manager

ile "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 854, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'PySide' distribution was not found and is required by yubikey-piv-manager (while launching the module directly with python -m pivman works). Cheers, -- Alexandre Vaissière

Bug#726670: policyd-weight: broken on system with IPv6-only dns resolver

Le 04/11/2013 22:38, Werner Detter a écrit : Hi Alexandre, This behaviour is also up to the usage of the $res-force_v4(1) call. I've created a little patch to fix the mentioned problems due to the usage of NET::DNS and force_v4() and uploaded the package on mentors[1]. Could you please

Bug#650047: very annoying when used with Xen

Package: radvd Version: 1:1.8.5-1 I have this bug too. I use radvd to announce prefix to Xen domUs and each time I (re)start one, a RA is sent on other VMs virtual interfaces, breaking routing, and making the whole system broken. Worse is when the RA goes to the eth0, even if not listed in

Bug#649349: [Pkg-xen-devel] Bug#649349: xen-hypervisor-4.1-amd64: pygrub fails due to invalid opcode trapped

Le 23/11/2011 15:08, Ian Campbell a écrit : If you boot the same kernel natively what happens when you run pygrub? (this should work natively, although obviously you won't be able to actually start a VM). Yes it does work: I see the grub interface. What happens if you pass noxsave to the

Bug#649349: [Pkg-xen-devel] Bug#649349: xen-hypervisor-4.1-amd64: pygrub fails due to invalid opcode trapped

Le 21/11/2011 11:32, Ian Campbell a écrit : Note that pygrub does NOT fail If I launch 'pygrub mydisk.img' on a standard kernel boot, only if the hypervisor is used (tested with linux-image-3.0.0 and linux-image-2.39.2) Can you try: /usr/lib/xen-default/bin/pygrub --args=root=/dev/xvda2 ro

Bug#649349: [Pkg-xen-devel] Bug#649349: Bug#649349: xen-hypervisor-4.1-amd64: pygrub fails due to invalid opcode trapped

Le 21/11/2011 22:08, Bastian Blank a écrit : Pleast install libc6-dbg, make sure you have an uptodate system and call disassemble when it dies. (gdb) info share ld-linux FromTo Syms Read Shared Object Library 0x77dddaf0 0x77df5833 Yes (*)

Bug#649349: xen-hypervisor-4.1-amd64: pygrub fails due to invalid opcode trapped

Package: xen-hypervisor-4.1-amd64 Version: 4.1.1-3 Severity: important Whenever I try to start a domU, xm create failed for 'Boot loader didn't return any data!'. % sudo xm create -c squeeze.cfg Using config file /etc/xen/squeeze.cfg. Error: Boot loader didn't return any data! It seems related