Processed: Re: Bug#929511: qtcreator: Segfault on start
Processing commands for cont...@bugs.debian.org: > tag 929511 unreproducible moreinfo Bug #929511 [qtcreator] qtcreator: Segfault on start Added tag(s) moreinfo and unreproducible. > severity 929511 important Bug #929511 [qtcreator] qtcreator: Segfault on start Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 929511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929511: qtcreator: Segfault on start
tag 929511 unreproducible moreinfo severity 929511 important thanks Hi Martin! On Sat, 25 May 2019 at 05:06, Martin Haase wrote: > > Package: qtcreator > Version: 4.8.2-1 > Severity: grave > Tags: upstream > Justification: renders package unusable I can't reproduce the behavior and I have also just installed buster and unstable system in which to use qtcreator this very same week without issues (it happens to be one of my principal tools for $job). In none of those cases I could see a crash, so it's clearly not happening to everyone and thus I'm lowering the severity. It is however something we need to triage for buster. > This is what I get when I try to start qtcreator: > > Program received signal SIGSEGV, Segmentation fault. > 0x7fffe6091e3c in llvm::SmallPtrSetImplBase::Grow(unsigned int) () > from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1 OK, so LLVM involved. > Complete backtrace, as from gdb: > > #0 0x7fffe6091e3c in llvm::SmallPtrSetImplBase::Grow(unsigned int) () > from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1 > #1 0x7fffe6091ff3 in llvm::SmallPtrSetImplBase::insert_imp(void const*) > () from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1 > #2 0x7fffe6060d24 in llvm::cl::OptionCategory::registerCategory() () > from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1 > #3 0x7fffd7602082 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1 > #4 0x77fe439a in call_init (l=, argc=argc@entry=1, > argv=argv@entry=0x7fffe498, env=env@entry=0x7fffe4a8) > at dl-init.c:72 > #5 0x77fe4496 in call_init (env=0x7fffe4a8, argv=0x7fffe498, > argc=1, l=) at dl-init.c:30 > #6 _dl_init (main_map=main_map@entry=0x55909600, argc=1, > argv=0x7fffe498, env=0x7fffe4a8) at dl-init.c:119 > #7 0x77fe8303 in dl_open_worker (a=a@entry=0x7fffda10) at > dl-open.c:517 > #8 0x76447f8f in __GI__dl_catch_exception (exception= out>, operate=, args= out>) at dl-error-skeleton.c:196 > #9 0x77fe7bea in _dl_open (file=0x55909538 > "/usr/lib/x86_64-linux-gnu/qtcreator/plugins/libClangTools.so", > mode=-2147479551, caller_dlopen=0x76ceffac, nsid=, > argc=1, argv=0x7fffe498, env=0x7fffe4a8) at dl-open.c:599 > #10 0x7630f256 in dlopen_doit (a=a@entry=0x7fffdc30) at > dlopen.c:66 > #11 0x76447f8f in __GI__dl_catch_exception > (exception=exception@entry=0x7fffdbd0, operate=, > args=) > at dl-error-skeleton.c:196 > #12 0x7644801f in __GI__dl_catch_error (objname=0x5558cd00, > errstring=0x5558cd08, mallocedp=0x5558ccf8, > operate=, args=) at > dl-error-skeleton.c:215 > #13 0x7630f975 in _dlerror_run (operate=operate@entry=0x7630f200 > , > args=args@entry=0x7fffdc30) at dlerror.c:163 > #14 0x7630f2e6 in __dlopen (file=, mode= out>) at dlopen.c:87 > #15 0x76ceffac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #16 0x76ce9c25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #17 0x76cea1d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #18 0x77fad5dc in > ExtensionSystem::Internal::PluginSpecPrivate::loadLibrary() () > from /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4 > #19 0x77fa54cd in > ExtensionSystem::Internal::PluginManagerPrivate::loadPlugin(ExtensionSystem::PluginSpec*, > ExtensionSystem::PluginSpec::State) () from > /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4 > #20 0x77fa6650 in > ExtensionSystem::Internal::PluginManagerPrivate::loadPlugins() () > from /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4 > #21 0xeeb6 in ?? () > #22 0x7633709b in __libc_start_main (main=0xca40, argc=1, > argv=0x7fffe498, init=, fini=, > rtld_fini=, stack_end=0x7fffe488) at > ../csu/libc-start.c:308 > #23 0xf50a in ?? () > > I tried the crude hack renaming the lib and symlinking to a newer > version, but that made things even worse. Besides, other programs > will be affected, too. I would expect that, yes. I need some extra info: - Which video card are you using? - Please create a new user and try starting qtcreator there. Moving out Qt creator's config is also possible, but more involved: you need to move ~/.config/QtCreatorrc *and* ~/.config/QtProject/qtcreator/ *and* ~/.config/QtProject/QtCreator* (without qtcreator running) and then start it. - Have you installed any third party plugin? The crash seems to come from loading a plugin. Thanks for your report and your help, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Bug#929531: grub-pc: grub2 fat_test fails with 4.19.0-5-amd64 kernel if one ensure it does not gets auto-skipped
Package: grub-pc Version: 2.02+dfsg1-18 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, while grub2 build fine as common users, i.e., the one created by the Debian Installer with the addition that it's added to the 'kvm' group, it does currently not as root depending on the Linux Kernel booted as with some the fat_test fail. Reproducer: * installing Debian from recent weekly testing ISO, boot, install build-essentials and devscripts * # uname -a Linux bussard 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64 GNU/Linux * # apt source grub2 * # apt buil-dep grub2 * # cd grub2-2.02+dfsg1/ * # debuild -b -uc -us ... mkdir: cannot create directory ‘/tmp/tmp.gfJAxp7sgv/vfat12a_rw///0//1/2/3//4/5’: Input/output error (full test-suite.log inlined below) kernel logged: > May 25 20:27:51 bussard kernel: FAT-fs (loop0): error, corrupted directory > (invalid entries) > May 25 20:27:51 bussard kernel: FAT-fs (loop0): Filesystem has been set > read-only > May 25 20:27:51 bussard kernel: FAT-fs (loop0): error, fat_get_cluster: > invalid cluster chain (i_pos 0) I tried multiple times, most of them with a reboot plus a complete cleanup and re-download of the source inbetween, but did not always saw the same error, different directories As I had build this in the past sucessfully I was a bit thrown-off first, reverting back to and older Kernel (first one I had lying arround was linux-image-4.16.0-1-amd64) it worked again, and build successfully. So, IMHO, there's an issue with either VFAT in the kernel itself, or how GRUB2 (test) uses VFAT under current Kernels, which just does not shows up as those FS test get skipped as common, unpriviledged, user, as the mkfs and loop device handling is normally not allowed for them. While yes, building as root is far from nice, it's the simplest way to actually ensure those FS test get run and thus show up an issue. I tested out some Kernels, most from the Ubuntu Mainline kernel ppa: https://kernel.ubuntu.com/~kernel-ppa/mainline/ I had varying results, it seems that 4.19.1-041901-generic always worked, but 4.19.37-041937-generic worked once, then on two different VMs I got errors too, so a bit strange, a 4.19.28-041928-generic failed to here, I did not invest more time into bisectin the issue because I had not much available and was a bit confused by the behaviour.. Below the test-suite log output. I hope I got this to the correct package people, as may have suited better on the kernel package, but as I only could trigger this by building grub with the test running I choose to initially report it here, sorry if it wasn't correct. ### BEGIN /root/grub2-2.02+dfsg1/obj/grub-pc/test-suite.log ### == GRUB 2.02+dfsg1-18: ./test-suite.log == # TOTAL: 81 # PASS: 63 # SKIP: 17 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 SKIP: squashfs_test === mksquashfs not installed; cannot test squashfs. SKIP: hfsplus_test == mkfs.hfsplus not installed; cannot test hfsplus. SKIP: ntfs_test === mkfs.ntfs not installed; cannot test ntfs. SKIP: reiserfs_test === mkfs.reiserfs not installed; cannot test reiserfs. FAIL: fat_test == mkfs.fat 4.1 (2017-01-24) Warning: More than 32765 sector need TOS 1.04 or higher. Device proc: Filesystem type procfs - Sector size 512B - Total size 0KiB Device loop0: Filesystem type fat - Label `GRUBTEST ;_', UUID - - Sector size 512B - Total size 3KiB Device host: Filesystem type hostfs - Sector size 512B - Total size 0KiB umount: /tmp/tmp.wcIfohU4Fn/vfat16a_rw: not mounted. mkfs.fat 4.1 (2017-01-24) Warning: More than 32765 sector need TOS 1.04 or higher. Device proc: Filesystem type procfs - Sector size 512B - Total size 0KiB Device loop0: Filesystem type fat - Label `GRUBTEST ;_', UUID - - Sector size 512B - Total size 3KiB Device host: Filesystem type hostfs - Sector size 512B - Total size 0KiB umount: /tmp/tmp.wcIfohU4Fn/vfat16a_rw: not mounted. mkfs.fat 4.1 (2017-01-24) Warning: More than 32765 sector need TOS 1.04 or higher. Device proc: Filesystem type procfs - Sector size 512B - Total size 0KiB Device loop0: Filesystem type fat - Label `GRUBTEST ;_', UUID - - Sector size 512B - Total size 3KiB Device host: Filesystem type hostfs - Sector size 512B - Total size 0KiB umount: /tmp/tmp.wcIfohU4Fn/vfat16a_rw: not mounted. mkfs.fat 4.1 (2017-01-24) Warning: More than 32765 sector need TOS 1.04 or higher. Device proc: Filesystem type procfs - Sector size 512B - Total size 0KiB Device loop0: Filesystem type fat - Label `GRUBTEST ;_', UUID - - Sector size 512B
Bug#928770: sqlite3: CVE-2019-5018: Window Function Remote Code Execution Vulnerability
> Alternatively, it could be related to: > https://www.sqlite.org/src/info/4feb3159c6bc3f7e33959 > > This was released as a part of 3.27.2 and looks like it has the right > text as well. What concerns me is that the ticket[0] is almost a week > before TALOS's timeline for "Vendor patched" plus it mentioned "free > that has not been malloc'ed" rather than "use after free". That said, > the test case examples for both issue are similar. This looks like a promising candidate. If you have the actual test case examples (I don't seem to be able to find them) it's surely "just" a matter of trying the PoC against this revision and its parent. Or going a bit further, using it to bisect between 3.27 and 3.28 (using a git mirror of the source). robert.
Bug#924787: Bug#926556: unblock: yubikey-personalization/1.19.3-3
It appears that the needed changes are located in Salsa [1], and that the release was prepared but not uploaded (since it's nowhere to be found). This package is team maintained, and since it's not clear to me if the rest of the team is aware of this issue, I'm CC'ing the team address in this message. If there's no response from nicoo or the rest of the team, I would like to go ahead with an NMU, assuming that's permissible under these circumstances. [1] https://salsa.debian.org/auth-team/yubikey-personalization/commits/debian/master -- GPG: 5CDD 0C9C F446 BC1B 2509 8791 1762 E022 7034 CF84
Bug#929527: /usr/sbin/xtables-nft-multi: restoring IP Tables with an self-defined chain segfaults in libnftnl.so
> [snip] > Anyway, on a Debian Stretch system installed from latest weekly ISO > restoring a relative simple IP Table with a single "intermediate" chain > causes a segfaul and no restoration of said table. sorry, above I meant: s/Stretch/Buster/
Processed: poppler: diff for NMU version 0.71.0-4.1
Processing control commands: > tags 924029 + pending patch Bug #924029 [libpoppler-glib8] evince: Crashes when opening a PDF Bug #922397 [libpoppler-glib8] libevdocument3-4: Evince passes NULL pointer to poppler_date_parse Bug #922398 [libpoppler-glib8] libevdocument3-4: Evince passes NULL pointer to poppler_date_parse Bug #927764 [libpoppler-glib8] evince crashes in poppler on unusual pdf document Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. -- 922397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922397 922398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922398 924029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924029 927764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924029: poppler: diff for NMU version 0.71.0-4.1
Control: tags 924029 + pending patch
Dear maintainer,
I've prepared an NMU for poppler (versioned as 0.71.0-4.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
Jonathan Wiltshire j...@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
diff -Nru poppler-0.71.0/debian/changelog poppler-0.71.0/debian/changelog
--- poppler-0.71.0/debian/changelog 2019-05-23 21:18:49.0 +0100
+++ poppler-0.71.0/debian/changelog 2019-05-25 17:10:35.0 +0100
@@ -1,3 +1,11 @@
+poppler (0.71.0-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Prevent a crash due to null pointer dereferencing in
+goo/GooString.h (Closes: #924029)
+
+ -- Jonathan Wiltshire Sat, 25 May 2019 17:10:35 +0100
+
poppler (0.71.0-4) unstable; urgency=medium
* CVE-2018-16646 (Closes: #909802)
diff -Nru poppler-0.71.0/debian/patches/bug924029-goostring-null-pointers.patch poppler-0.71.0/debian/patches/bug924029-goostring-null-pointers.patch
--- poppler-0.71.0/debian/patches/bug924029-goostring-null-pointers.patch 1970-01-01 01:00:00.0 +0100
+++ poppler-0.71.0/debian/patches/bug924029-goostring-null-pointers.patch 2019-05-25 17:09:50.0 +0100
@@ -0,0 +1,97 @@
+Subject: Make GooString constructible and assignable from null pointers again
+ since some of the code expects it.
+Origin: https://gitlab.freedesktop.org/poppler/poppler/commit/8f158da92c53ae16a368f844965f57ba8ffed77d
+Bug: https://gitlab.freedesktop.org/poppler/poppler/commit/8f158da92c53ae16a368f844965f57ba8ffed77d
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924029
+Reviewed-by: Jonathan Wiltshire
+Applied-Upstream: yes
+Last-Update: 2019-05-25
+
+--- poppler-0.71.0.orig/goo/GooString.h
poppler-0.71.0/goo/GooString.h
+@@ -60,7 +60,7 @@
+ GooString& operator=(const GooString ) = delete;
+
+ // Create a string from a C string.
+- explicit GooString(const char *sA) : std::string(sA) {}
++ explicit GooString(const char *sA) : std::string(sA ? sA : "") {}
+
+ // Zero-cost conversion from and to std::string
+ explicit GooString(const std::string& str) : std::string(str) {}
+@@ -70,18 +70,18 @@
+
+ // Create a string from chars at . This string
+ // can contain null characters.
+- GooString(const char *sA, int lengthA) : std::string(sA, lengthA) {}
++ GooString(const char *sA, int lengthA) : std::string(sA ? sA : "", sA ? lengthA : 0) {}
+
+ // Create a string from chars at in .
+ GooString(const GooString *str, int idx, int lengthA) : std::string(*str, idx, lengthA) {}
+
+ // Set content of a string to .
+- GooString* Set(const GooString *newStr) { assign(*newStr); return this; }
+- GooString* Set(const char *newStr) { assign(newStr); return this; }
+- GooString* Set(const char *newStr, int newLen) { assign(newStr, newLen); return this; }
++ GooString* Set(const GooString *newStr) { assign(newStr ? static_cast(*newStr) : std::string{}); return this; }
++ GooString* Set(const char *newStr) { assign(newStr ? newStr : ""); return this; }
++ GooString* Set(const char *newStr, int newLen) { assign(newStr ? newStr : "", newStr ? newLen : 0); return this; }
+
+ // Copy a string.
+- explicit GooString(const GooString *str) : std::string(*str) {}
++ explicit GooString(const GooString *str) : std::string(str ? static_cast(*str) : std::string{}) {}
+ GooString *copy() const { return new GooString(this); }
+
+ // Concatenate two strings.
+--- poppler-0.71.0.orig/qt5/tests/check_goostring.cpp
poppler-0.71.0/qt5/tests/check_goostring.cpp
+@@ -11,6 +11,7 @@
+ void testInsertData();
+ void testInsert();
+ void testFormat();
++void testFromNullptr();
+ };
+
+ void TestGooString::testInsertData_data()
+@@ -122,6 +123,42 @@
+ }
+ }
+
++void TestGooString::testFromNullptr()
++{
++ {
++GooString str{static_cast(nullptr)};
++QCOMPARE(str.getLength(), 0);
++ }
++
++ {
++GooString str;
++str.Set(static_cast(nullptr));
++QCOMPARE(str.getLength(), 0);
++ }
++
++ {
++GooString str{static_cast(nullptr)};
++QCOMPARE(str.getLength(), 0);
++ }
++
++ {
++GooString str{static_cast(nullptr), 0};
++QCOMPARE(str.getLength(), 0);
++ }
++
++ {
++GooString str;
++str.Set(static_cast(nullptr));
++QCOMPARE(str.getLength(), 0);
++ }
++
++ {
++GooString str;
++str.Set(static_cast(nullptr), 0);
++QCOMPARE(str.getLength(), 0);
++ }
++}
++
+ QTEST_GUILESS_MAIN(TestGooString)
+ #include "check_goostring.moc"
+
diff -Nru poppler-0.71.0/debian/patches/series poppler-0.71.0/debian/patches/series
--- poppler-0.71.0/debian/patches/series 2019-05-23 21:18:49.0 +0100
+++ poppler-0.71.0/debian/patches/series 2019-05-25 17:03:52.0 +0100
@@ -11,3 +11,4 @@
CVE-2019-9200.patch
CVE-2019-9631.patch
CVE-2019-10873.patch
Bug#929527: /usr/sbin/xtables-nft-multi: restoring IP Tables with an self-defined chain segfaults in libnftnl.so
Package: iptables Version: 1.8.2-4 Severity: grave File: /usr/sbin/xtables-nft-multi Justification: renders package unusable by segfaulting on usage Dear Maintainer, First, it may be that this should be actually filed against nftables, so I'd like to say sorry in advance if made noise to the wrong people. Anyway, on a Debian Stretch system installed from latest weekly ISO restoring a relative simple IP Table with a single "intermediate" chain causes a segfaul and no restoration of said table. Reproducer: # cat simple-segv-table *filter :NEW-OUTPUT - [0:0] -A OUTPUT -j NEW-OUTPUT -F NEW-OUTPUT -A NEW-OUTPUT -j ACCEPT COMMIT # iptables ./simple-segv-table Segmentation fault # dmesg | tail -1 [12860.813350] traps: iptables-restor[19173] general protection ip:7f4894682793 sp:7ffcedc177d0 error:0 in libnftnl.so.11.0.0[7f4894677000+17000] # addr2line -e /usr/lib/x86_64-linux-gnu/libnftnl.so.11.0.0 -fCi $(printf "%x" $[0x7f2cb9882793 - 0x7f2cb9877000]) nftnl_batch_is_supported ??:? (hope that my addr2line foo isn't to much off) Above example works just fine on a Debian Stretch 9.9 based machine. As intially I produced this on a, let's say, far from minimal and a bit Frankenstein'ed Buster, I installed the netinst weekly ISO again in a QEMU/KVM backed VM, same outcome. As said, this may well be an issue in the linked libnftnl shared library, but could also be an issue from how iptables uses it, as I produced the error by calling into a iptables provided binary I choose to report it here (not sure if one can report against multiple packages). -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages iptables depends on: ii libc62.28-10 ii libip4tc01.8.2-4 ii libip6tc01.8.2-4 ii libiptc0 1.8.2-4 ii libmnl0 1.0.4-2 ii libnetfilter-conntrack3 1.0.7-1 ii libnfnetlink01.0.1-3+b1 ii libnftnl11 1.1.2-2 ii libxtables12 1.8.2-4 Versions of packages iptables recommends: ii nftables 0.9.0-2 Versions of packages iptables suggests: ii kmod 26-1 -- no debconf information
Processed: closing 929526
Processing commands for cont...@bugs.debian.org: > close 929526 1:1.0.1-1 Bug #929526 [xfonts-scalable] xfonts-scalable: fails to install in lenny/i386: fmt: invalid width: `63482' Marked as fixed in versions xfonts-scalable/1:1.0.1-1. Bug #929526 [xfonts-scalable] xfonts-scalable: fails to install in lenny/i386: fmt: invalid width: `63482' Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 929526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929526: xfonts-scalable: fails to install in lenny/i386: fmt: invalid width: `63482'
Package: xfonts-scalable Version: 1:1.0.0-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up xfonts-scalable (1:1.0.0-6) ... fmt: invalid width: `63482' fmt: invalid width: `63482' fmt: invalid width: `63482' dpkg: error processing xfonts-scalable (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: xfonts-scalable It installs fine in squeeze/i386 with the version from squeeze. cheers, Andreas xfonts-scalable_1:1.0.0-6.log.gz Description: application/gzip
Bug#929151: netdata-core: version in stretch-backports newer than version in buster
Hi backports team, On Sat, 18 May 2019 10:22:10 +0200 Andreas Beckmann wrote: > Package: netdata-core > Version: 1.12.0-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: close -1 1.12.1-2 > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'stretch-backports' to 'buster' due to a version oerdering violation. > > netdata-core | 1.12.0-1| testing | amd64, arm64, armel, > armhf, i386, mips, mips64el, mipsel, ppc64el, s390x > netdata-core | 1.12.1-2~bpo9+1 | stretch-backports | amd64, arm64, armel, > armhf, i386, mips, mips64el, mipsel, ppc64el, s390x > netdata-core | 1.12.2-2| unstable | amd64, arm64, armel, > armhf, i386, mips, mips64el, mipsel, ppc64el, s390x > netdata-core | 1.14.0-1| experimental | amd64, arm64, armel, > armhf, i386, mips, mips64el, mipsel, ppc64el, s390x The current version of netdata-core in unstable is very unlikely to get unblocked. What do you suggest to do in such a case, remove the package from stretch-backports? It doesn't comply with the backports policy. Paul signature.asc Description: OpenPGP digital signature
Bug#929511: qtcreator: Segfault on start
For some reason unknown to me there are several packages still depending on this special version of libLLVM. When I try to remove it, qtcreator is listed among them. As is xorg - which prevents me from performing the `apt-get remove`. On Sat, 25 May 2019 12:59:16 +0300 Alexander Kernozhitsky wrote: > Hello, > > I am using Qt Creator on Buster and don't see any problems on start. > > BTW, why do you have /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1? I searched on > packages.debian.org and I didn't find the package with such library for amd64. > Is it the old package that was manually installed or it didn't get removed on > updates? > > -- > Alexander Kernozhitsky > > > >
Bug#929511: qtcreator: Segfault on start
Hello, I am using Qt Creator on Buster and don't see any problems on start. BTW, why do you have /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1? I searched on packages.debian.org and I didn't find the package with such library for amd64. Is it the old package that was manually installed or it didn't get removed on updates? -- Alexander Kernozhitsky
Processed: Re: mutt: undefined behavior on huge integer in a RFC 2231 header
Processing commands for cont...@bugs.debian.org: > tags 929017 + pending patch Bug #929017 [mutt] mutt: undefined behavior on huge integer in a RFC 2231 header Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 929017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929017: mutt: undefined behavior on huge integer in a RFC 2231 header
tags 929017 + pending patch thanks I've uploaded mutt 1.10.1-2.1 to DELAYED/5: mutt (1.10.1-2.1) unstable; urgency=medium * Non-maintainer upload. * Apply patch from upstream to prevent undefined behaviour when parsing invalid Content-Disposition mail headers. The atoi() function was being called on a number which can potentially overflow and thus can have security implications depending on the atoi() implementation. (Closes: #929017) The full debdiff is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diffstat for mutt-1.10.1 mutt-1.10.1 changelog | 11 +++ patches/series|1 + patches/upstream/929017-atoi-undefined-behavior.patch | 18 ++ 3 files changed, 30 insertions(+) diff -Nru mutt-1.10.1/debian/changelog mutt-1.10.1/debian/changelog --- mutt-1.10.1/debian/changelog2018-08-07 09:31:52.0 +0100 +++ mutt-1.10.1/debian/changelog2019-05-25 09:57:12.0 +0100 @@ -1,3 +1,14 @@ +mutt (1.10.1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Apply patch from upstream to prevent undefined behaviour when +parsing invalid Content-Disposition mail headers. The atoi() function was +being called on a number which can potentially overflow and thus can have +security implications depending on the atoi() implementation. +(Closes: #929017) + + -- Chris Lamb Sat, 25 May 2019 09:57:12 +0100 + mutt (1.10.1-2) unstable; urgency=low [ Jonathan Nieder ] diff -Nru mutt-1.10.1/debian/patches/series mutt-1.10.1/debian/patches/series --- mutt-1.10.1/debian/patches/series 2018-08-07 09:31:15.0 +0100 +++ mutt-1.10.1/debian/patches/series 2019-05-25 09:57:12.0 +0100 @@ -12,3 +12,4 @@ upstream/905551-oauthbearer-imap.patch upstream/905551-oauthbearer-smtp.patch upstream/905551-oauthbearer-refresh.patch +upstream/929017-atoi-undefined-behavior.patch diff -Nru mutt-1.10.1/debian/patches/upstream/929017-atoi-undefined-behavior.patch mutt-1.10.1/debian/patches/upstream/929017-atoi-undefined-behavior.patch --- mutt-1.10.1/debian/patches/upstream/929017-atoi-undefined-behavior.patch 1970-01-01 01:00:00.0 +0100 +++ mutt-1.10.1/debian/patches/upstream/929017-atoi-undefined-behavior.patch 2019-05-25 09:57:12.0 +0100 @@ -0,0 +1,18 @@ +https://gitlab.com/muttmua/mutt/commit/3b6f6b829718ec8a7cf3eb6997d86e83e6c38567 + +--- mutt-1.10.1.orig/rfc2231.c mutt-1.10.1/rfc2231.c +@@ -147,7 +147,12 @@ void rfc2231_decode_parameters (PARAMETE + encoded = (*t == '*'); + *t = '\0'; + +- index = atoi (s); ++ /* RFC 2231 says that the index starts at 0 and increments by 1, ++ thus an overflow should never occur in a valid message, thus ++ the value INT_MAX in case of overflow does not really matter ++ (the goal is just to avoid undefined behavior). */ ++ if (mutt_atoi (s, )) ++index = INT_MAX; + + conttmp = rfc2231_new_parameter (); + conttmp->attribute = p->attribute;
Bug#929297: minissdpd: CVE-2019-12106
Hey, > > The following vulnerability was published for minissdpd. > > > > CVE-2019-12106[0]: > > | The updateDevice function in minissdpd.c in MiniUPnP MiniSSDPd 1.4 and > > | 1.5 allows a remote attacker to crash the process due to a Use After > > | Free vulnerability. […] > Chris, thanks for your proposal to update Stretch, I very much > appreciate it. Another gentle ping, security team? Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#926180: scilab: FTBFS on all
On 23/05/2019 22:35, Rebecca N. Palmer wrote: It now looks like these are actually "valgrind doesn't understand Java memory allocation" The Valgrind documentation says --smc-check=all should fix this, but it doesn't. Ubuntu has a 6.0.2 package that builds in Debian, but it still has this bug. (Same stacktrace as 6.0.1 under gdb; once a different one (below) under valgrind --smc-check=all --error-limit=no --log-file=scilab_valgrind%n .) WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.scilab.modules.jvm.LibraryPath (file:/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/modules/jvm/jar/org.scilab.modules.jvm.jar) to field java.lang.ClassLoader.sys_paths WARNING: Please consider reporting this to the maintainers of org.scilab.modules.jvm.LibraryPath WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release terminate called after throwing an instance of 'GiwsException::JniCallMethodException' what(): Exception when calling Java method : at java.base/java.util.TreeMap.getEntry(TreeMap.java:350) at java.base/java.util.TreeMap.containsKey(TreeMap.java:231) at java.base/java.util.TreeSet.contains(TreeSet.java:234) at org.scilab.modules.graphic_objects.utils.MenuBarBuilder$MenuBarConfigurationHandler.invoke(Unknown Source) at com.sun.proxy.$Proxy0.addMenus(Unknown Source) at org.scilab.modules.graphic_objects.utils.MenuBarBuilder.buildMenuBar(Unknown Source) at org.scilab.modules.graphic_objects.utils.MenuBarBuilder.buildFigureMenuBar(Unknown Source) at org.scilab.modules.graphic_objects.CallGraphicController.buildFigureMenuBar(Unknown Source) at java.base/java.util.TreeMap.getEntry(TreeMap.java:350) at java.base/java.util.TreeMap.containsKey(TreeMap.java:231) at java.base/java.util.TreeSet.contains(TreeSet.java:234) at org.scilab.modules.graphic_objects.utils.MenuBarBuilder$MenuBarConfigurationHandler.invoke(Unknown Source) at com.sun.proxy.$Proxy0.addMenus(Unknown Source) at org.scilab.modules.graphic_objects.utils.MenuBarBuilder.buildMenuBar(Unknown Source) at org.scilab.modules.graphic_objects.utils.MenuBarBuilder.buildFigureMenuBar(Unknown Source) at org.scilab.modules.graphic_objects.CallGraphicController.buildFigureMenuBar(Unknown Source) A fatal error has been detected by Scilab. Please check your user-defined functions (or external module ones) should they appear in the stack trace. Otherwise you can report a bug on http://bugzilla.scilab.org/ with: * a sample code which reproduces the issue * the result of [a, b] = getdebuginfo() * the following information: [rnpalmer-laptop:05275] Signal: Aborted (6) [rnpalmer-laptop:05275] Signal code: (-6) Call stack: 1: 0x377bb (/lib/x86_64-linux-gnu/libc.so.6) 2: 0x22535 (/lib/x86_64-linux-gnu/libc.so.6) 3: 0x8c983 < > (/usr/lib/x86_64-linux-gnu/libstdc++.so.6) 4: 0x928c6 < > (/usr/lib/x86_64-linux-gnu/libstdc++.so.6) 5: 0x92901 < > (/usr/lib/x86_64-linux-gnu/libstdc++.so.6) 6: 0x92b34 < > (/usr/lib/x86_64-linux-gnu/libstdc++.so.6) 7: 0x1e0d6 int)> (/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/modules/graphic_objects/.libs/libscigraphic_objects.so.6) 8: 0x6525e (/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/modules/graphics/.libs/libscigraphics.so.6) 9: 0x66180 (/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/modules/graphics/.libs/libscigraphics.so.6) 10: 0x49c33 (/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/modules/graphics/.libs/libscigraphics.so.6) 11: 0x1b9694 (/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/modules/.libs/libscilab-cli.so.6) 12: 0x2360 (/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/.libs/scilab-bin) 13: 0x2409b <__libc_start_main> (/lib/x86_64-linux-gnu/libc.so.6) 14: 0x2dfa < > (/home/rnpalmer/Debian/builds/stackbuild/scilab-6.0.2/.libs/scilab-bin) End of stack Last error (of ~10,000) in the Valgrind log: ==5275== Invalid write of size 4 ==5275==at 0x2D810AE8: ??? ==5275==by 0x5907680: ??? (in /usr/lib/jvm/java-11-openjdk-amd64/lib/server/libjvm.so) ==5275==by 0x5976F8C: ??? (in /usr/lib/jvm/java-11-openjdk-amd64/lib/server/libjvm.so) ==5275==by 0x597874D: ??? (in /usr/lib/jvm/java-11-openjdk-amd64/lib/server/libjvm.so) ==5275==by 0x4EA1C12: JNIEnv_::CallObjectMethod(_jobject*, _jmethodID*, ...) (jni.h:906) ==5275==by 0x4EA0CBB: GiwsException::JniException::retrieveExceptionName[abi:cxx11](JNIEnv_*) (GiwsException.cpp:217) ==5275==by 0x4EA0F6F: GiwsException::JniException::JniException(JNIEnv_*) (GiwsException.cpp:37) ==5275==by 0x4EA1830: GiwsException::JniCallMethodException::JniCallMethodException(JNIEnv_*) (GiwsException.cpp:288) ==5275==by 0x4FF50BF: org_scilab_modules_graphic_objects::CallGraphicController::buildFigureMenuBar(JavaVM_*,
Bug#929511: qtcreator: Segfault on start
Package: qtcreator Version: 4.8.2-1 Severity: grave Tags: upstream Justification: renders package unusable This is what I get when I try to start qtcreator: Program received signal SIGSEGV, Segmentation fault. 0x7fffe6091e3c in llvm::SmallPtrSetImplBase::Grow(unsigned int) () from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1 Complete backtrace, as from gdb: #0 0x7fffe6091e3c in llvm::SmallPtrSetImplBase::Grow(unsigned int) () from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1 #1 0x7fffe6091ff3 in llvm::SmallPtrSetImplBase::insert_imp(void const*) () from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1 #2 0x7fffe6060d24 in llvm::cl::OptionCategory::registerCategory() () from /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1 #3 0x7fffd7602082 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-7.so.1 #4 0x77fe439a in call_init (l=, argc=argc@entry=1, argv=argv@entry=0x7fffe498, env=env@entry=0x7fffe4a8) at dl-init.c:72 #5 0x77fe4496 in call_init (env=0x7fffe4a8, argv=0x7fffe498, argc=1, l=) at dl-init.c:30 #6 _dl_init (main_map=main_map@entry=0x55909600, argc=1, argv=0x7fffe498, env=0x7fffe4a8) at dl-init.c:119 #7 0x77fe8303 in dl_open_worker (a=a@entry=0x7fffda10) at dl-open.c:517 #8 0x76447f8f in __GI__dl_catch_exception (exception=, operate=, args=) at dl-error-skeleton.c:196 #9 0x77fe7bea in _dl_open (file=0x55909538 "/usr/lib/x86_64-linux-gnu/qtcreator/plugins/libClangTools.so", mode=-2147479551, caller_dlopen=0x76ceffac, nsid=, argc=1, argv=0x7fffe498, env=0x7fffe4a8) at dl-open.c:599 #10 0x7630f256 in dlopen_doit (a=a@entry=0x7fffdc30) at dlopen.c:66 #11 0x76447f8f in __GI__dl_catch_exception (exception=exception@entry=0x7fffdbd0, operate=, args=) at dl-error-skeleton.c:196 #12 0x7644801f in __GI__dl_catch_error (objname=0x5558cd00, errstring=0x5558cd08, mallocedp=0x5558ccf8, operate=, args=) at dl-error-skeleton.c:215 #13 0x7630f975 in _dlerror_run (operate=operate@entry=0x7630f200 , args=args@entry=0x7fffdc30) at dlerror.c:163 #14 0x7630f2e6 in __dlopen (file=, mode=) at dlopen.c:87 #15 0x76ceffac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x76ce9c25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x76cea1d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x77fad5dc in ExtensionSystem::Internal::PluginSpecPrivate::loadLibrary() () from /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4 #19 0x77fa54cd in ExtensionSystem::Internal::PluginManagerPrivate::loadPlugin(ExtensionSystem::PluginSpec*, ExtensionSystem::PluginSpec::State) () from /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4 #20 0x77fa6650 in ExtensionSystem::Internal::PluginManagerPrivate::loadPlugins() () from /usr/bin/../lib/x86_64-linux-gnu/qtcreator/libExtensionSystem.so.4 #21 0xeeb6 in ?? () #22 0x7633709b in __libc_start_main (main=0xca40, argc=1, argv=0x7fffe498, init=, fini=, rtld_fini=, stack_end=0x7fffe488) at ../csu/libc-start.c:308 #23 0xf50a in ?? () I tried the crude hack renaming the lib and symlinking to a newer version, but that made things even worse. Besides, other programs will be affected, too. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_GB.ISO-8859-15) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages qtcreator depends on: ii libbotan-2-9 2.9.0-2 ii libc6 2.28-1 ii libclang1-71:7.0.1-8 ii libgcc11:8.3.0-7 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libllvm7 1:7.0.1-8 ii libqbscore1.12 1.12.2+dfsg-2 ii libqbsqtprofilesetup1.12 1.12.2+dfsg-2 ii libqt5concurrent5 5.11.3+dfsg1-1 ii libqt5core5a [qtbase-abi-5-11-3] 5.11.3+dfsg1-1 ii libqt5designer55.11.3-4 ii libqt5designercomponents5 5.11.3-4 ii libqt5gui5 5.11.3+dfsg1-1 ii libqt5help55.11.3-4 ii libqt5network5 5.11.3+dfsg1-1 ii libqt5printsupport55.11.3+dfsg1-1 ii libqt5qml5 [qtdeclarative-abi-5-11-2] 5.11.3-4 ii libqt5quick5 5.11.3-4 ii libqt5quickwidgets55.11.3-4 ii libqt5script5 5.11.3+dfsg-3 ii libqt5serialport5
Bug#926182: Patch: Use alternatives system for guile-2.2-dev binaries
Le 25/05/2019 à 01:18, Rob Browning a écrit : > Rob Browning writes: > >> I'm not certain, but I'm planning to work on guile over the next week. >> If so, I should be able to take a look. > > Just as an update, I obviously didn't get to it earlier this week, but > I'm looking in to it now. > > After I poke around a bit, I suspect the next step will be to contact > the release managers to see what they think about any proposed changes > because of course if they're not in favor, then the changes may have to > wait. > > I expect I'll be able to report back in a couple of days. Dear Rob, Since this change would be revertible in sid, you can safely upload already and then contact the release team with the unblock request and a source debdiff. Kind regards, Thibaut. signature.asc Description: OpenPGP digital signature
Bug#929506: gbrowse FTBFS: tests fail
Source: gbrowse Version: 2.56+dfsg-4 Severity: serious Tags: ftbfs sid gbrowse fails to build from source using sbuild in unstable: | Test Summary Report | --- | t/00.compile.t (Wstat: 4608 Tests: 87 Failed: 18) | Failed tests: 1, 3, 5, 7, 10, 15, 17-18, 25, 28, 30, 32 | 34, 40, 44, 46, 59, 86 | Non-zero exit status: 18 | t/01.yeast.t(Wstat: 512 Tests: 0 Failed: 0) | Non-zero exit status: 2 | Parse errors: Bad plan. You planned 7 tests but ran 0. | t/02.rearchitecture.t (Wstat: 512 Tests: 0 Failed: 0) | Non-zero exit status: 2 | Parse errors: Bad plan. You planned 90 tests but ran 0. | t/03.render.t (Wstat: 512 Tests: 0 Failed: 0) | Non-zero exit status: 2 | Parse errors: No plan found in TAP output | t/04.remoteserver.t (Wstat: 512 Tests: 0 Failed: 0) | Non-zero exit status: 2 | Parse errors: Bad plan. You planned 43 tests but ran 0. | t/05.deferredrendering.t (Wstat: 512 Tests: 0 Failed: 0) | Non-zero exit status: 2 | Parse errors: No plan found in TAP output | t/06.featuresearch.t(Wstat: 512 Tests: 0 Failed: 0) | Non-zero exit status: 2 | Parse errors: Bad plan. You planned 26 tests but ran 0. | t/07.karyotype.t(Wstat: 512 Tests: 0 Failed: 0) | Non-zero exit status: 2 | Parse errors: Bad plan. You planned 3 tests but ran 0. | Files=10, Tests=93, 2 wallclock secs ( 0.03 usr 0.00 sys + 1.88 cusr 0.27 csys = 2.18 CPU) | Result: FAIL | Failed 8/10 test programs. 18/93 subtests failed. | dh_auto_test: perl Build test --verbose 1 "TEST_FILES=t/02.rearchitecture.t t/05.deferredrendering.t t/00.compile.t t/01.yeast.t t/07.balancer.t t/08.calign.t" returned exit code 255 | make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:12: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 This is also observed by reproducible builds using pbuilder: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/gbrowse_2.56+dfsg-4.rbuild.log.gz According to reproducible builds, it does not fail in buster or earlier. Helmut
