[Bug 1848556] Re: qemu-img check failing on remote image in Eoan

2019-10-21 Thread Max Reitz
Hi Christian, I don’t see any issue but the fact that the whole series should be backported (0487861685294660b23bc146e1ebd5304aa8bbe0 through bfb23b480a49114315877aacf700b49453e0f9d9, maybe also c34dc07f9f01cf686, but that isn’t strictly necessary). Max -- You received this bug notification bec

[Bug 1848556] Re: qemu-img check failing on remote image in Eoan

2019-10-21 Thread Max Reitz
Hi Rod, You don’t need to add anything, but maybe there’s some library missing. --enable-curl should force support and then tell you whether there’s something missing. Max -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.

[Bug 1848556] Re: qemu-img check failing on remote image in Eoan

2019-10-18 Thread Max Reitz
Hi, Could you try the qemu’s master branch? bfb23b480a49114315877aacf700b49453e0f9d9 has fixed an issue that sounds very much like this. The problem in that case is that libcurl 7.59.0 changed behavior, so bisecting qemu will not produce results. Max -- You received this bug notification becau

[Bug 1025244] Re: qcow2 image increasing disk size above the virtual limit

2014-12-16 Thread Max Reitz
@Mario, in theory an image "that should be taking up 30 GB" with four snapshots should be taking up at most about 150 GB, of course. Now the question is what you mean by "should be taking up 30 GB" and by "is taking 600+ GB". For the latter, did you query the file length (ls -l) or the actual size

[Bug 495101] Re: Anonymous mmap crashes with SIGSEGV

2010-05-25 Thread Max Reitz
I asked someone to test it for me on Ubuntu 10.04 and the bug seems to be fixed (appearently no error). Thanks! -- Anonymous mmap crashes with SIGSEGV https://bugs.launchpad.net/bugs/495101 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 495101] [NEW] Anonymous mmap crashes with SIGSEGV

2009-12-10 Thread Max Reitz
Public bug reported: This (possible) bug is not related to any package but to the libc itself maybe (or the kernel or whatever). When executing this program on Kubuntu 9.10: #include #include #include #include void segfault_handler(int num) { fprintf(stderr, "Segfault happened, exiting.\