Hello,
On Tue, 18 Jun 2019 12:46:30 +0200 Julian Andres Klode
wrote:
> Package: goplay
> Severity: serious
>
> Hi folks,
>
> goplay has not received any updates since 2015, it uses libept,
> which we'd like to get rid of eventually I think, as it's also
> unmaintained, so I think it would be
On Sat, 1 Jun 2019 06:16:58 +0530 Raj Kiran Grandhi <
grajki...@gmail.com> wrote:
> Hi,
>
> In a fresh install of Buster with XFCE desktop, locking the screen
> blanks the monitor and the monitor enters a power save state. After
> that, neither moving the mouse nor typing on the keyboard would
Please note that there are many visually impaired users who must use the
Orca screen reader which speaks the content on screen. If pulseaudio
would not start automatically then for the blind user like me it would
be impossible to use the computer.
Your message dated Sat, 22 Jun 2019 22:10:34 +0200
with message-id <20190622201034.ga4...@home.ouaza.com>
and subject line Re: Bug#930929: libvirt: is no longer able to use kvm
has caused the Debian Bug report #930929,
regarding libvirt: is no longer able to use kvm
to be marked as done.
This
On Sat, 22 Jun 2019, Raphael Hertzog wrote:
> And despite this I still have the error and yet the libvirt-qemu user
> is part of the kvm group:
> $ id libvirt-qemu
> uid=124(libvirt-qemu) gid=130(kvm) groupes=130(kvm),132(libvirt-qemu)
Still I confirm that the libvirt-qemu user is not able to
Your message dated Sat, 22 Jun 2019 19:49:07 +
with message-id
and subject line Bug#929662: fixed in docker.io 18.09.1+dfsg1-7.1
has caused the Debian Bug report #929662,
regarding docker.io: CVE-2018-15664
to be marked as done.
This means that you claim that the problem has been dealt with.
On Sat, Jun 22, 2019 at 3:07 PM Fabrice Dagorn wrote:
>
> Hi,
>
> it seems that docker.io would be removed from buster if nothing changes
> in the next 3 days [0].
>
> Do you need help to fix this ?
>
[...]
> > thanks for reaching out. I applied the patch, that is no problem.
> > However the
Source: webkit2gtk
Version: 2.24.1-2
Severity: serious
Tags: patch
webkit2gtk violates the baseline on i386 by using SSE.
While keeping floating point values consistent between
32bit and 64bit is nice in general, it is bad if this
makes the code crash on large parts of the supported
i386
On 2019-06-22 10:51:35 +0200, Vincent Lefevre wrote:
> The /etc/mailcap file contains many rules with '%s' instead of %s,
> for instance:
>
> text/*; less '%s'; needsterminal
> audio/ogg; ogginfo '%s'; copiousoutput
>
> This is incorrect. [...]
I suppose that the update-mime script could
Control: found -1 5.0.0-3
Control: found -1 5.2.0-2
On Sat, 22 Jun 2019, Raphaël Hertzog wrote:
> For a few days/weeks (I'm not sure when it started exactly), I can no
> longer run my VM with virt-manager.
I tried downgrading to the version in testing, but the problem stayed the
same. I also
Processing control commands:
> found -1 5.0.0-3
Bug #930929 [src:libvirt] libvirt: is no longer able to use kvm
Marked as found in versions libvirt/5.0.0-3.
> found -1 5.2.0-2
Bug #930929 [src:libvirt] libvirt: is no longer able to use kvm
Marked as found in versions libvirt/5.2.0-2.
--
930929:
Hi Daniel,
On Tue, 14 May 2019 06:18:31 + Daniel Kahn Gillmor
wrote:
> gnupg2 (2.2.13-2) unstable; urgency=medium
> .
>* Correct gpg-wks-server manpage (Closes: #927431) Thanks, ju xor!
>* Fix handling private keys with comments (Closes: #928963, #928964)
>* clean up logcheck
Source: libvirt
Version: 5.0.0-4
Severity: serious
For a few days/weeks (I'm not sure when it started exactly), I can no
longer run my VM with virt-manager.
On startup of libvirtd I have many messages like this one (one for each VM
I guess):
libvirtd[8281]: invalid argument: could not find
Control: forwarded -1 https://github.com/davidhalter/parso/issues/75
I wonder if this is going to pan out like CVE-2014-3539...unpatched
upstream for five years. But on the upside, it's more difficult to
exploit and lower severity. On a related note, could Rope's
"signature verification [for]
Processing control commands:
> forwarded -1 https://github.com/davidhalter/parso/issues/75
Bug #930356 [src:parso] CVE-2019-12760
Set Bug forwarded-to-address to
'https://github.com/davidhalter/parso/issues/75'.
--
930356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930356
Debian Bug
Il 22/06/19 12:46, Diederik de Haas ha scritto:
On vrijdag 21 juni 2019 16:53:11 CEST Dean Loros wrote:
Can I confirm that this is a problem with AMD graphics only--or will this
affect all systems regardless of Video card type?
Yes. (bug is filed against firmware-amd-graphics)
Michael
On vrijdag 21 juni 2019 16:53:11 CEST Dean Loros wrote:
> Can I confirm that this is a problem with AMD graphics only--or will this
> affect all systems regardless of Video card type?
Yes. (bug is filed against firmware-amd-graphics)
Michael Becker: what CPU do you have?
Antonio De Luci: Are
On 2019-06-22 10:51:35 +0200, Vincent Lefevre wrote:
> execve("/home/vinc17/bin/sh.screen", ["sh", "-c", "less
> ''/var/tmp/_.txt''"], 0x564ffe666f40 /* 132 vars */) = 0
>
> i.e. the filename is eventually not quoted!
>
> Here the filename is sanitized, but I'm not sure that this is always
>
On Sat, Jun 22, 2019 at 11:26:40AM +0200, Tobias Hansen wrote:
> On 6/21/19 10:54 PM, Adam Borowski wrote:
> > (patch is
> > https://salsa.debian.org/pulseaudio-team/pulseaudio/merge_requests/5)
> >
> > On Fri, Jun 21, 2019 at 11:37:48AM +0200, Tobias Hansen wrote:
> >> I just updated by system
Package: python-musicbrainz2
Version: 0.7.4-2
Severity: grave
Justification: renders package unusable
The web service this package uses (MusicBrainz API v1) is discontinued and
will not be reactivated. All requests get answered with 410 (Gone).
Thus, this package should not be in Buster.
--
On 6/21/19 10:54 PM, Adam Borowski wrote:
> Control: severity -1 grave
> Control: tags -1 +patch
>
> (patch is
> https://salsa.debian.org/pulseaudio-team/pulseaudio/merge_requests/5)
>
> On Fri, Jun 21, 2019 at 11:37:48AM +0200, Tobias Hansen wrote:
>> I just updated by system from stretch to
On Sat, Jun 22, 2019 at 08:06:08AM +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
>
> > severity 930869 serious
> Bug #930869 [pm-utils] needs purging of quirks
> Severity set to 'serious' from 'wishlist'
> > retitle 930869 Don't release with buster
>
On 2019-06-22 10:51:35 +0200, Vincent Lefevre wrote:
[...]
> as seen in strace output:
>
> execve("/home/vinc17/bin/sh.screen", ["sh", "-c", "less
> ''/var/tmp/_.txt''"], 0x564ffe666f40 /* 132 vars */) = 0
FYI, the sh.screen is due to a modification I've done and is used
as a sh wrapper to
gregor herrmann writes:
> Upstream has now closed the CPAN RT ticket and released a 0.31
> version which fixes the issue (differently).
>
> I've "backported" the fix (i.e. took most of the 0.31 diff and added
> it as a quilt patch) and pushed it to git. For convenience I'm also
> attaching the
Processing commands for cont...@bugs.debian.org:
> affects 930908 mutt
Bug #930908 [general] general: incorrect rules for %s in /etc/mailcap yielding
potentially unquoted metacharacters
Added indication that 930908 affects mutt
>
End of message, stopping processing here.
Please contact me if
Package: general
Severity: grave
Tags: security
Justification: user security hole
Affects: mutt
The /etc/mailcap file contains many rules with '%s' instead of %s,
for instance:
text/*; less '%s'; needsterminal
audio/ogg; ogginfo '%s'; copiousoutput
This is incorrect. For instance, Mutt quotes
Processing commands for cont...@bugs.debian.org:
> severity 930869 serious
Bug #930869 [pm-utils] needs purging of quirks
Severity set to 'serious' from 'wishlist'
> retitle 930869 Don't release with buster
Bug #930869 [pm-utils] needs purging of quirks
Changed Bug title to 'Don't release with
Hi,
it seems that docker.io would be removed from buster if nothing changes
in the next 3 days [0].
Do you need help to fix this ?
Fabrice
[0] https://lists.debian.org/debian-release/2019/06/msg00542.html
On Mon, 10 Jun 2019 11:54:08 +0700 Arnaud Rebillout
wrote:
> Hi,
>
> thanks
28 matches
Mail list logo
