Source: qemu
Version: 1:2.1+dfsg-12
Severity: important
Tags: security upstream patch fixed-upstream
There's a floating point exception in qemu-system vnc server,
being tracked as CVE-2015-8504. Upstream commit:
http://git.qemu.org/?p=qemu.git;a=commit;h=4c65fed8bdf96780735dbdb92a8bd0d6b6526cc3
Just to clarify. This is a remotely-triggerable crash of qemu
process if vnc port is enabled.
/mjt
Source: qemu
Severity: important
Tags: security upstream patch
Version: 1.1.2+dfsg-1
Qemu emulator built with the USB EHCI emulation support is vulnerable to an
infinite loop issue. It occurs during communication between host controller
interface(EHCI) and a respective device driver. These two com
Source: qemu
Severity: important
Tags: upstream security patch
Version: 1.5.0~rc0+dfsg-1
Two host memory leaks found in vmxnet3 device implementation
in qemu.
http://www.openwall.com/lists/oss-security/2015/12/15/10
This device first appeared in version 1.5.0 of qemu, so only
jessie and current
Control: notfound -1 1.1.2+dfsg-1
Control: found -1 1.3.0+dfsg-1~exp1
16.12.2015 16:29, Salvatore Bonaccorso wrote:
[]
>>->
>> http://git.qemu.org/?p=qemu.git;a=commit;h=43b11a91dd861a946b231b89b754285
>
> Question back: wasn't that introduced with
> http://git.qemu.org/?p=qemu.git;a=commitd
Control: forwarded -1 http://thread.gmane.org/gmane.comp.emulators.qemu/383093
Control: tag -1 + upstream confirmed
19.12.2015 01:52, Vincent Bernat wrote:
> Package: qemu-system-x86
> Version: 1:2.5+dfsg-1
> Severity: normal
> File: /usr/bin/qemu-system-x86_64
>
> Hi!
>
> Since version 2.5, mou
Control: tag -1 + patch pending
The issue has been fixed upstream by this patch:
http://thread.gmane.org/gmane.comp.emulators.qemu/383164
I'll include it in the next debian release.
Thanks,
/mjt
On Thu, 21 Aug 2014 12:51:31 +0400 Michael Tokarev wrote:
> > Ceph packages are present in wheezy-backports repository, so I don't
> > understand why RBD support is systematicaly disabled as in changelog
> > for version 2.1+dfsg-2~bpo70+2.
Just a small clarificatio
There's a bug filed against debian qemu package, there:
http://bugs.debian.org/758881
which says about problems sending keypress events over VNC to
a qemu guest, -- some keypresses gets lost, at least.
The bisection between qemu 2.0 and 2.1 leads to this commit:
commit 2858ab09e6f708e381fc1a1c
Control: tag -1 + moreinfo
Control: severity -1 normal
24.08.2014 07:09, stevie wrote:
> Package: qemu-kvm
> Version: 2.1+dfsg-2
> Severity: important
>
> Dear Maintainer,
>
>* What led up to the situation?
> I added a virtio-9P filesystem device to an existing VM which then
> fail
Control: tag -1 - moreinfo + confirmed upstream
Control: retitle -1 9pfs should report actual init-time errors
Control: severity -1 wishlist
Okay. I see where the problem is.
The problem is that qemu does not report actual errors returned by the
system - in this case, to statfs() syscall which it
I haven't noticed this email - which is almost a month old now - until today.
So replying now...
30.07.2014 21:43, Aneesh Kumar K.V wrote:
> "Aneesh Kumar K.V" writes:
>
>> Michael Tokarev writes:
>>
>>> Apparently the the mapped-* security models
26.08.2014 09:40, Gerd Hoffmann wrote:
> There should be a delay after every character. It can be pretty small.
> 10ms should be enough (you should set TCP_NODELAY though to make sure
> the key events are not buffered in the network stack).
Is this delay qemu-specific (or, rather, virtualization-
I applied the suggested patch to our systemd as well.
We were hit badly by this bug, about 400 systems are
generating these messages and spam logs (actually
only just a few we upgraded from sysvinit to systemd,
we stopped the process due to this).
After applying the patch, systemd does not produce
Control: severity -1 wishlist
10.06.2016 04:31, Henrique de Moraes Holschuh wrote:
...
> One must enable SCTERC (e.g. with smartctl -l scterr,70,500) before
> starting the array (initramfs included). Fortunately, suport for SCTERC
> can be detected, and it can be queried, so one would only mess w
Control: tag -1 + moreinfo
13.06.2016 11:15, uli iske wrote:
> Package: qemu
> Version: 2.6+dfsg-1+b1
>
> When trying to start or migrate Guest with ceph rbd Disk image
> connected I get the following error message:
>
> internal error: process exited while connecting to monitor:
> 2016-06-13T08:
13.06.2016 12:31, uli iske wrote:
>> Please give complete qemu error message, not the interpretation
>> given by libvirt.
>
> Is there a log somewhere or do I have to start the guest with
> qemu-system-x86_64 ?
I don't know libvirt enough to be able to answer this question, sorry.
Thanks,
/mjt
Control: forwarded -1
https://lists.nongnu.org/archive/html/qemu-devel/2016-06/msg03272.html
14.06.2016 13:25, Peter Maydell wrote:
> I investigated this qemu-img segfault, and it turns out to be
> due to a conflict between QEMU not marking its coroutine stacks
> as executable and the MIPS kernel
06.05.2016 12:22, Chris Lamb wrote:
> Source: qemu
> Version: 1:2.5+dfsg-5
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
>
> Dear Maintainer,
>
> qem
Control: severity -1 important
while this bug is important enough for a given use case and architecture,
it is definitely not an RC-critical bug. Lowering the severity.
Especially since it isn't quite easy to fix it.
Thanks,
/mjt
24.06.2016 12:47, Jeffrey Walton wrote:
> Package: qemu-user-static
> Version: 1:2.6+dfsg-3
> Severity: important
I'm not sure at all why you're filing this for qemu.
> I: Running command: debootstrap --arch sparc --foreign --keyring
> /usr/share/keyrings/debian-ports-archive-keyring.gpg --varian
24.06.2016 13:50, Jeffrey Walton wrote:
[sparc architecture]
> Why does the Ports page (https://www.debian.org/ports/) list it as an
> official port if its not supported?
I don't know. Sparc architecture has been dropped in jessie, maybe
even in wheezy, I don't remember already, and dropped in a
Control: severity -1 wishlist
Control: tag -1 + moreinfo
02.07.2016 08:23, westlake wrote:
> Package: qemu-system-x86
> Version: 1:2.5+dfsg-4~bpo8+1
> Severity: important
>
> x-data-plane is now known as iothread and is missing from this build of qemu
This option is always built into qemu, it i
24.04.2016 23:09, Martin Michlmayr wrote:
>> /usr/include/xfs/xfs_fs.h:42:8: error: redefinition of 'struct fsxattr'
>> struct fsxattr {
>> ^
>> /usr/include/linux/fs.h:155:8: note: originally defined here
>> struct fsxattr {
>> ^
This smells like a bug in the build environment,
Control: tag -1 + moreinfo unreproducible
23.11.2014 20:34, pe...@easthope.ca wrote:
> Package: qemu-system
>
> Dear Maintainer,
> *** Please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
> Attempt to access host floppy /dev/fd0.
24.11.2014 00:19, Geert Stappers wrote:
>> and also specify which version of qemu you're using - your bug report does
>> not specify this.
>
> Bugreport 770742 is from the same reporter and states version: 1.1.2+dfsg-6
>
> B.R. #770740 and #770742 are merged and for convience this URL
> http://b
24.11.2014 00:04, pe...@easthope.ca wrote:
>> Control: tag -1 + moreinfo unreproducible
>
> Sorry, I forgot to add the Package and Version tags to the
> first email submission of 770742. I file only a few reports
> per year and tend to forget to add tags.
>
> Package and Version can be automa
24.11.2014 11:14, Michael Tokarev wrote:
> 24.11.2014 00:04, pe...@easthope.ca wrote:
[]
>> No problem with an image file. The problem is with the
>> real diskette, /dev/fd0. [..]
One more thing I forgot to mention.
For qemu, both an image file and a real floppy drive
are e
09.07.2014 08:19, C. Wolf writes:
Hi,
I've found a viable solution to this problem.
I've putted following script into /etc/pm/sleep.d:
#!/bin/bash
#
# A script to pause virtual machines before going into suspend
declare -r SAVES_DIRECTORY="/var/lib/libvirt/qemu/save"
This does not save any
Control: severity -1 minor
10.07.2014 04:15, lcell...@lycee-joliverie.fr wrote:
Package: qemu-user-static
Version: 2.0.0+dfsg-6+b1
Severity: important
Tags: upstream
Hello,
I can't run some mips32 binaries with qemu:
root@localhost:/tmp# chroot /tmp/temp/ /usr/bin/qemu-mips-static /bin/dmesg
Control: reopen -1
I'm not sure what to do with this really.
Yesterday I upgraded my wheezy system and come to this very issue there.
Because I had systemd installed from wheezy-backports, and now this bug
reappeared in a backported version, ofcourse initscripts in wheezy is
not patched.
At least
Control: severity -1 wishlist
Control: tag -1 + confirmed upstream
05.07.2014 23:08, Bastian Blank wrote:
> Package: qemu-system-x86
> Version: 2.0.0+dfsg-6+b1
> Severity: normal
>
> qemu allows definition of several devices with type ide-hd or ide-cd.
> All of them are assigned to the same bus,
26.07.2014 15:15, Michael Tautschnig wrote:
> Hi,
>
> As our systems are also being bitten by this bug, I was wondering whether
> there
> was any chance of this bug seeing attention before the freeze? I am happy to
> help if I can be of any assistance, of course.
There's no progress at all. Aft
26.07.2014 20:13, Mitsuya Shibata wrote:
> Package: qemu-user-static
> Version: 2.0.0+dfsg-7
> Severity: normal
>
> Dear Maintainer,
>
> qemu-debootstrap --arch=s390x fails with "dpkg --install" on second stage.
>
> $ sudo qemu-debootstrap --verbose --arch=s390x unstable test
Just one question
27.07.2014 02:31, Pedro Ribeiro wrote:
> Package: qemu-kvm
> Version: 2.0.0+dfsg-6+b1
> Severity: normal
>
> Hi,
>
> When I set up a virtual machine with a SATA drive, the VM fails to start with
> the following message:
> Error starting domain: unsupported configuration: SATA is not supported wit
25 июля 2014 г. 13:31:08 GMT+04:00, Vincent Lefevre пишет:
>Package: qemu-user-binfmt
>Version: 2.0.0+dfsg-7
>Severity: minor
>
>The qemu-user-binfmt short description is:
>
> QEMU user mode binfmt registration for qemu-user (empty package)
>
>This is confusing because when looking at dpkg -l out
Control: severity -1 minor
Control: merge 751754 -1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Control: severity -1 normal
Control: found -1 1.7.0+dfsg-1
Control: tag -1 + upstream confirmed
Control: severity 751078 normal
Control: merge 751078 -1
Control: retitle 751078 legacy -cdrom/-hda/drive if=ide options does not work
with q35
On Sat, 05 Jul 2014 21:05:07 +0200 Bastian Blank wrote:
Control: tag -1 + moreinfo
23.07.2014 01:11, Bastian Blank wrote:
> Package: qemu-system-x86
> Version: 2.0.0+dfsg-6+b1
> Severity: important
>
> The local 9p support supports readdir. It does not translate the value
> of d_type, so the guest always sees a regular file, even in a lstat call
> de
Control: tag -1 + moreinfo
06.07.2014 00:10, Bastian Blank wrote:
> Control: found -1 2.0.0+dfsg-6+b1
>
> The problem showed up again.
>
> Command line:
> | qemu-system-x86_64 -machine pc-q35-2.0 -m 2048 -serial stdio -drive
> file=wheezy_amd64_base,id=ide0.0,if=none,cache=writeback -device
>
Control: reassign -1 libvirt-bin
27.07.2014 09:07, Michael Tokarev wrote:
> 27.07.2014 02:31, Pedro Ribeiro wrote:
>> Package: qemu-kvm
>> Version: 2.0.0+dfsg-6+b1
>> Severity: normal
>>
>> Hi,
>>
>> When I set up a virtual machine with a SATA drive
30.07.2014 23:29, Bastian Blank wrote:
> On Wed, Jul 30, 2014 at 05:39:41PM +0400, Michael Tokarev wrote:
>> 23.07.2014 01:11, Bastian Blank wrote:
>> I'm not sure what do you mean by "translate". It passes d_type from host.
>> And it works in guest as is.
On Sat, 5 Jul 2014 12:27:48 -0500 Arthur Marble wrote:
> Package: libiscsi
> Severity: minor
> Usertags: clang-ftbfs
> User: pkg-llvm-t...@lists.alioth.debian.org
> Tag: patch
>
>
> Hello,
>
> Using the rebuild infrastructure, your package fails to build with clang
> (instead of gcc).
Care to
Control: tag -1 + moreinfo
31.07.2014 11:56, Zimmermann, Alexander wrote:
> Package: busybox
> Version: 1:1.22.0-6
> Severity: important
>
> Dear Maintainer,
>
> we have a PXE environments in our lab, where we boot both physical boxes
> and XEN machines via NFS from one centralized Debian SID im
01.08.2014 15:37, Zimmermann, Alexander wrote:
> As you can see, we use a vanilla 3.14 Kernel, patched w/ official AUFS patch
> (see
> http://aufs.sourceforge.net)
I too use aufs here, for a very long time. But I never tried
nfs-root together with aufs, I used if in slightly different
scenarios
Control: reassign -1 libvirt-bin
02.08.2014 05:17, 積丹尼 Dan Jacobson wrote:
> Package: qemu-system-x86
> Version: 2.1+dfsg-1
> Severity: grave
>
> Setting up qemu-system-x86 (2.1+dfsg-1) ...
> update-rc.d: warning: start and stop actions are no longer supported; falling
> back to defaults
> insse
Control: severity -1 normal
Control: merge 751754 -1
Stop doing this nonsense. Thank you.
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Control: severity -1 minor
Control: merge 751754 -1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
02.08.2014 09:15, Michael Tokarev wrote:
> Control: reassign -1 libvirt-bin
>
> 02.08.2014 05:17, 積丹尼 Dan Jacobson wrote:
>> Package: qemu-system-x86
>> Version: 2.1+dfsg-1
>> Severity: grave
>>
>> Setting up qemu-system-x86 (2.1+dfsg-1) ...
>> update
Hello.
Do you still remember this old bug from late-2012? Do you still have any issues
outlined there? I weren't able to reproduce it meantime, and both qemu and
seabios undergone several releases.
Can we close this bugreport now maybe? :)
Thanks,
/mjt
31.12.2012 01:03, Michael To
02.08.2014 13:12, 積丹尼 Dan Jacobson wrote:
> Package: qemu-system-common
> Version: 2.1+dfsg-2
> Severity: minor
> File: /usr/share/doc/qemu-system-common/qemu-doc.html
>
> In many places in the docs we see e.g.,
>
>5.2.1 Quick Start
>
>In order to launch a Linux process, QEMU needs the p
Package: qemu-system-ppc
Version: 2.1+dfsg-1
Severity: normal
Tags: confirmed
Since qemu 2.1, there's a e500 ppc emulation implemented in qemu.
However, due to DFSG, we have to strip blobs from the source packages,
and while qemu do provide u-boot.e500 sources, it can only be built
on a powerpc pl
Control: retitle -1 qemu-mips-static doesn't recognize broken ELF headers
I'm retitling this bugreport to reflect reality. Qemu implements its own
ELF parser, and it looks like it is a bit stricter than the one in linux
kernel. I'm not sure whenever to treat it as a bug or a feature. And
these
05.08.2014 00:37, Vagrant Cascadian wrote:
> On 2014-08-02, Michael Tokarev wrote:
>> Since qemu 2.1, there's a e500 ppc emulation implemented in qemu.
>> However, due to DFSG, we have to strip blobs from the source packages,
>> and while qemu do provide u-boot.e500 sou
Control: found -1 2.1.5-2
On Mon, 04 Aug 2014 15:05:40 +0200 Alexander Kurtz wrote:
> Version: 2.1.5-1
>
> https://packages.qa.debian.org/v/vlc/news/20140729T215036Z.html says:
>
> vlc (2.1.5-1) unstable; urgency=medium
> .
>[ Benjamin Drung ]
>* New upstream release.
>* Add FFmpe
05.08.2014 17:36, Zimmermann, Alexander wrote:
> Despite the fact that I was unable to write a proper wrapper :-) - the kernel
> crashes -
> I know now that neither busybox nor AUFS is the culprit. See below:
Um. The wrapper should be something like:
#! /bin/sh
echo mounts before-init:
mount
21.05.2015 15:51, Vincent Bernat wrote:
> The new download page is here:
> http://code.coreboot.org/p/seabios/downloads/
>
> But I don't see how uscan could discover the right URL without some kind of
> redirector.
That's exactly the reason why I haven't updated d/watch file for a while.
I know
22.05.2015 13:01, Gerd Hoffmann wrote:
> On Mi, 2015-05-20 at 14:44 +0300, Michael Tokarev wrote:
>> A (friendly) ping? :)
>>
>>> The solution appears to be trivial (see also some background
>>> at http://blog.nielshorn.net/2011/03/qemu-and-brazilian-keyboards/ ),
22.05.2015 16:20, Gerd Hoffmann wrote
> Hi,
>
>>> Anyone having such a keyboard and willing to run some tests?
>>
>> Adding Cc's. This has been reported to debian too,
>> http://bugs.debian.org/772422 (also in Cc).
>
> Ok, so just replying should stick this into the debian bug tracker, right?
Control: reopen -1
Control: found -1 3.0.2-17
On Mon, 03 Feb 2014 10:47:02 +0100 Jakob Hirsch wrote:
> Daniel Baumann, 2014-02-01 06:11:
> > close 735357
> > thanks
> >
> > this doesn't happen with recent enough kernel (>=3.11).
>
> I have kernel 3.12.6-2 (from jessie) running and it still happ
Control: severity -1 wishlist
Control: merge 775431 -1
28.05.2015 18:48, Nico Schottelius wrote:
[]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
31.05.2015 18:56, Marc Meledandri wrote:
> Is any further info needed here?
>
> I've run into this bug with _both_ GPT and MBR partition tables.
It is independent of the type of underlying devices.
The problem is that with incremental array assembly, when not all
devices are present, we need som
31.05.2015 23:05, Info Geek wrote:
> I'm not into scripting voodo but if this is of any help this is a reply I got
> when I asked about it, before the bug report:
>
>
> http://serverfault.com/questions/688207/how-to-auto-start-degraded-software-raid1-under-debian-8-0-0-on-boot
This is a wrong s
07.07.2015 11:48, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
>
>> affects 785557 src:perl
> Bug #785557 [qemu-system-x86] QEMU: causes vCPU steal time overflow on live
> migration
> Added indication that 785557 affects src:perl
Dominic, care to explain?
Control: tag -1 + unreproducible
17.07.2015 20:20, Vladmimir Stavrinov wrote:
> Package: ovmf
> Version: 0~20150106.5c2d456b-1
> Severity: normal
>
> Dear Maintainer,
>
> It still working with 3.2 kernel, but stop booting with 3.16 at some point
> (see snapshot).
It works for me just fine.
Th
17.07.2015 21:44, Vladimir Stavrinov wrote:
> On Fri, Jul 17, 2015 at 08:53:01PM +0300, Michael Tokarev wrote:
>
>> some systemd debugging. I'm afraid there's nothing we can do here,
>
> I've tried switch back to sysvinit, but it doesn't help.
>
&
18.07.2015 10:23, Vladimir Stavrinov wrote:
> On Fri, Jul 17, 2015 at 10:23:40PM +0300, Michael Tokarev wrote:
>
>> These can be facts for you. As long as I can't reproduce this behavour
>
> To "reproduce this behavior" try install only base system with
> de
18.07.2015 11:23, Vladimir Stavrinov wrote:
> On Sat, Jul 18, 2015 at 11:07:49AM +0300, Vladimir Stavrinov wrote:
>
>> Is it pristine base system only, installed with debootstrap, or You used
>> standard Debian installer?
You said debootstrap so I used debootstrap.
> I just tried official Debian
18.07.2015 11:33, Michael Tokarev wrote:
>> http://cdimage.debian.org/debian-cd/8.1.0/multi-arch/iso-cd/debian-8.1.0-amd64-i386-netinst.iso
>>
>>
>> After "successful" installation system does not boot at all. Even grub
>> doesn't appear.
>
18.07.2015 11:52, Michael Tokarev wrote:
[]
> The last message is:
>
> [1.322591] fb: switching to bochsdrmfb from simple
>
> Booting with serial console enabled reveals that the
> system boots just fine, the only problem is that there's
> nothing on the console a
Control: unarchive 763043
Control: notfixed 763043 qemu/2.1+dfsg-8
Control: tag 763043 - unreproducible
Control: merge 763043 -1
07.05.2015 08:14, Guo Yixuan (郭溢譞) wrote:
> Package: src:qemu
> Severity: normal
> Tags: patch
>
> Hello,
>
> This bug follows #763043, with some updates.
>
> Summary
07.05.2015 09:09, Michael Tokarev wrote:
[]
> I'm trying to merge the two bugs together, let's see how it goes.
After some thoughts I unmerged the two bugs. The problem is that
the other, first bug of this theme mentioned only x86_64 and it was
marked as fixed for jessie. But app
08.05.2015 03:44, Bernhard Übelacker wrote:
> Package: qemu-system-x86
> Version: 1:2.1+dfsg-11
> Severity: normal
> Tags: upstream
>
> Dear Maintainer,
> I quite regularly install some qemu VMs by just doing something like this:
> qemu-system-x86_64 --enable-kvm -drive file=disk.img -cdrom cd
08.05.2015 11:10, Michael Tokarev wrote:
...
> Note that on all these systems, the guest X window does not have a title
> to click on, but you mentioned that in kde environment you can click on
> a title. Maybe this is some non-standard behavour of kde.
Hmm. This is ofcourse wrong,
11.05.2015 19:09, Josh Triplett wrote:
> Package: qemu-system-x86
> Version: 1:2.1+dfsg-11
> Severity: important
>
> I don't know if this bug lies in qemu or in the kernel. I can reproduce it
> with the latest kernel from git (4.1-rc3), as well as with 3.16 (Debian
> package
> 3.16.7-ckt9-3). I
Control: retitle -1 KVM emulation failure: eptad, triggered by (old) OVMF code
Control: severity -1 minor
Control: tag -1 + upstream confirmed
18.05.2015 04:54, Josh Triplett wrote:
[]
> I can confirm that updating to a newer OVMF makes this problem go away.
> If there's no way of supporting page
[Dropping Paolo as this is now related solely to debian internals]
18.05.2015 10:42, Josh Triplett wrote:
[]
> I would have gone upstream if Paolo hadn't immediately jumped in and
> started diagnosing this.
Oh. So my attempt to get upstream's attention was actually wrong :)
>> There's no reason
10.06.2015 13:40, Robert.K. wrote:
> I am also hit by this bug in Debian Jessie 8. I got it in a virtualized
> Virtualbox machine with one virtual disk (VDI file) and one disk attached
> through USB where the root was located on a md device.
This is #714155 which is fixed by increasing rootdelay
11.06.2015 14:21, Robert.K. wrote:
> I apologize if I missed something, but ONLY adding rootdelay=XX guessed
> seconds does not help against being dropped to an initramfs-shell.
>
> There may be two different bugs?
>
> One for when not waiting for slow devices but the boot continues, which is
>
11.06.2015 20:13, Robert.K. wrote:
> The bug in this report (#784070) is about being dropped to a shell when there
> are missing disks in a software RAID1 configuration upon boot.
Ok, this makes sense.
It is not RAID1 it is any RAID level, and it has nothing to do with GPT.
/mjt
--
To UNSUB
Control: reassign -1 qemu-system-x86
Control: severity -1 normal
Control: merge 786789 -1
Thanks,
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Control: retitle -1 Using mdadm to install Debian on Intel IMSM RAID array
stopped working between Wheezy 7.8 and Jessie RC1
Control: reassign -1 mdadm
Control: tag -1 + help
05.02.2015 17:43, Benjamin Black wrote:
> Package: debian-installer
> Version: used in Debian GNU/Linux Jessie-DI-rc1 "Jes
03.12.2014 21:37, Jonathan Wiltshire wrote:
> Control: tag -1 moreinfo
>
> On Sun, Nov 30, 2014 at 03:42:56PM +0100, Diederik de Haas wrote:
>> What needs to be done further so that busybox transitions into testing?
>> --
>> GPG: 0x138E41915C7EFED6
>
>
> Well, sid now has 1:1.22.0-14, so the be
Package: qemu-system, qemu-kvm
Version: 1.1.2+dfsg-1
Severity: critical
Tags: security patch upstream fixed-upstream
There's a CVE-2014-8106 reported against qemu.
The prob exists in earlier versions of qemu too,
affecting stable (wheezy) release as well.
/mjt
--
To UNSUBSCRIBE, email to debia
+
+ -- Michael Tokarev Thu, 04 Dec 2014 00:10:43 +0300
+
qemu (2.1+dfsg-8) unstable; urgency=low
[ Michael Tokarev ]
diff -Nru
qemu-2.1+dfsg/debian/patches/cirrus-don-t-overflow-CirrusVGAState-cirrus_bltbuf-CVE-2014-8106.patch
qemu-2.1+dfsg/debian/patches/cirrus-don-t-overflow-CirrusVGAStat
On Tue, 2 Dec 2014 10:10:52 +0300 Andrey Nikitin
wrote:
> Today again md-arrays runs in degraded mode.
>
> [0.709392] sd 0:0:0:0: [sda] 312579695 512-byte logical blocks: (160
> GB/149 GiB)
> [0.777502] sd 0:0:0:0: [sda] Attached SCSI disk
> ...
> [7.135661] sd 2:0:0:0: [sdb] 781422
Control: tag -1 + moreinfo
01.06.2012 14:11, Alastair Irvine (Warpspace IT) wrote:
> Package: mdadm
> Version: 3.1.4-1+8efb9d1+squeeze1
> Severity: important
>
> /usr/share/initramfs-tools/scripts/local-top/mdadm does not wait after
> loading modules in the "Loading MD modules" step. Therefore,
Control: tag -1 + moreinfo
[Replying to a relatively old bugreport]
04.11.2013 06:27, Marc Lehmann wrote:
> Package: mdadm
> Version: 3.3-2
> Severity: normal
>
> Dear Maintainer,
> *** Please consider answering these questions, where appropriate ***
>
> I attached 4 disks to my computer (alrea
Neil, will you take the patch in this bugreport for the next version?
http://bugs.debian.org/763917.
Thanks,
/mjt
On Fri, 3 Oct 2014 20:24:54 +0200 Jan Echternach wrote:
> Package: mdadm
> Version: 3.3.2-1
> Severity: minor
> Tags: patch
>
>
> While setting up a new system, I noticed an inco
Package: qemu-system
Version: 2.1+dfsg-3
Severity: serious
Many qemu-system-* system-mode emulators don't work anymore because
they can't find firmware files.
For example, many even non-x86 systems can have PCI VGA/video cards,
which needs firmware (vgabios). Alpha, mips*, ppc*, sparc64 (besides
08.05.2013 17:30, Lisandro Damián Nicanor Pérez Meyer wrote:
> Package: qemu-user-static
> Version: 1.1.2+dfsg-6a
> Severity: important
>
> Hi! I'm using qemu-mips-static to build some packages in a chroot.
> Up to late last year I could do this without problems, using
> a 64 bits wheezy host and
25.11.2014 00:42, Stepan Golosunov wrote:
> Package: mdadm
> Version: 3.3.2-2
>
> On the next reboot after upgrading mdadm from 3.2.5-5 to 3.3.2-2 I was
> greeted with a fatal fsck error. Turned out symlinks like /dev/md/boot
> were missing. Manual creation of the necessary symlink allowed boot to
05.12.2014 18:00, Michael Tokarev wrote:
> 25.11.2014 00:42, Stepan Golosunov wrote:
>> Package: mdadm
>> Version: 3.3.2-2
>>
>> On the next reboot after upgrading mdadm from 3.2.5-5 to 3.3.2-2 I was
>> greeted with a fatal fsck error. Turned out symlinks like /de
06.12.2014 00:06, Marc Lehmann wrote:
> On Fri, Dec 05, 2014 at 01:23:19PM +0300, Michael Tokarev
> wrote:
>> I'm not sure what to make out of this bugreport really. Tagging with
>> `moreinfo' for now.
>
> Not sure what more info I could deliver, it seems to b
Control: tag -1 + upstream confirmed
Control: forwarded -1 https://bugs.launchpad.net/qemu/+bug/1038136
Control: severity -1 normal
Control: found -1 1.1.2+dfsg-1
06.12.2014 21:04, R. Lemos wrote:
> Package: qemu
> Version: 2.1+dfsg-7+b1
> Severity: important
>
> Dear Maintainer,
>
> when host X
06.12.2014 21:51, R. Lemos wrote:
>> Thanks, and please excuse me for being unconstructive.
> ("unconstructive" to say the least)
Well, as I said, it is not my area. Another possibility was to just
ignore this bugreport, but I at least tried to outline my position
as the package maintainer. I can
On Thu, 15 May 2014 20:06:26 +0100 althaser wrote:
> version: 3.4.2.1-4
>
> I'm closing this bug now since it seems to be fine.
>
> If you can still reproduce it feel free to reopen and provide more info.
I'm sorry but I fail to see how it is "fine" if the problem actually
exists and affects ma
Package: gnome-control-center
Version: 1:3.14.1-1
Followup-For: Bug #624714
This bug is still present for me in 1:3.14.1-1.
No matter which volume I set the alert sound at or whenever I
mute it or not, the sound is played at the loudest volume.
It is current jessie-to-be, updated today.
Thanks,
Control: found -1 1:3.14.1-1
On Thu, 1 Dec 2011 12:02:47 + Jonathan McCrohan wrote:
> I can also confirm this bug.
>
> A workaround is to manually mute the sound using dconf-editor:
> org -> gnome -> desktop -> sound -> event-sound
Yes, this way one can turn the sound off completely. I'd r
11.12.2014 10:52, Ivo De Decker wrote:
[]
> As the libc issue with the static binary seems to be fixed in the libc version
> in both jessie and sid, the only remaining issue is the missing build-using,
> which can wait till after jessie.
>
> Could you do a new upload with only the security fix?
I
1001 - 1100 of 2616 matches
Mail list logo
