Bug#1094893: Fixed upstream; need new upstream release
Tags: fixed-upstream See https://github.com/astropy/astropy-healpix/pull/234
Bug#1037322: Shadow : CVE-2023-35789
Hi Team, We are currently using Debian Bookworm 12.8 and have identified a vulnerability issue with the librabbitmq package. Could you please confirm if there is an ETA for a fix or update to address this in an upcoming Bookworm release? Additionally, if there are any available workarounds or interim solutions, kindly share those as well. Regards, Tamil Selvam .P
Bug#1037322: Librabbitmq : CVE-2023-35789
Hi Team, We are currently using Debian Bookworm 12.8 and have identified a vulnerability issue with the librabbitmq package. Could you please confirm if there is an ETA for a fix or update to address this in an upcoming Bookworm release? Additionally, if there are any available workarounds or interim solutions, kindly share those as well. Regards, Tamil Selvam .P
Bug#1086251: proftpd-dev: #include breaks several packages
On Wed, Oct 30, 2024 at 05:11:10PM +0100, Hilmar Preuße wrote: Hi, am I correct, that in this case one normally schedules an binNMU to solve the issue? In our specific case this is not sufficient, b/c the test suite is broken; fix is on salsa: rev -3. Well, yes but I see at least a couple of different RC bugs pending and -3 is undergone since June, so I would call for a binNMU shot for all -mod packages after uploading a new proftpd core package, possibly with a proper fix of #1082326i, if possible. I can't do anything before Saturday b/c the local WLAN does not allow SSH connections to anywhere. H. I don't think there is a specific urgency, I'll be off for a few days too. -- ⢀⣴⠾⠻⢶⣦⠀ Francesco Paolo Lovergine ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ 0579 A97A 2238 EBF9 BE61 ⠈⠳⣄ ED02 0F02 A5E1 1636 86A4
Bug#1086251: proftpd-dev: #include breaks several packages
On Tue, Oct 29, 2024 at 06:57:07PM +0100, Santiago Vila wrote: Package: proftpd-dev Version: 1.3.8.b+dfsg-2 Severity: grave Dear maintainer: Package proftpd-mod-clamav and many others currently FTBFS in this way: ck-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -fno-omit-frame-po inter -fno-strict-aliasing -Werror=implicit-function-declaration -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_ clamav.c -fPIC -DPIC -o .libs/mod_clamav.o In file included from /usr/include/proftpd/conf.h:105, from mod_clamav.c:30: /usr/include/proftpd/fsio.h:41:13: fatal error: attr/xattr.h: No such file or directory 41 | # include | ^~ compilation terminated. prxs: error executing command (1) make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:10: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 I just had a look into this issue. TJ code already dynamically checks for sys/xattr.h and attr/xattr.h with specific vars in the autoconf configure.in. # On Linux/MacOSX, it's sys/xattr.h AC_CHECK_HEADER(sys/xattr.h, [AC_DEFINE(HAVE_SYS_XATTR_H, 1, [Define if sys/xattr.h is present.]) AC_DEFINE(PR_USE_XATTR, 1, [Define if using xattr support.]) AC_CHECK_HEADERS(attr/xattr.h) ... Now, proftpd depends on libacl1-dev which depends on libattr1-dev and so indirecly find the obsolete attr/xattr.h in the system at build time. That of course coherently introduces a tentative include in proftpd dev headers. SO, I guess the next upload of proftpd will simply force this issue disappearing and a coherent rebuild of all -mod after that will adjust things. -- ⢀⣴⠾⠻⢶⣦⠀ Francesco Paolo Lovergine ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ 0579 A97A 2238 EBF9 BE61 ⠈⠳⣄ ED02 0F02 A5E1 1636 86A4
Bug#1064293: less: CVE-2022-48624
On 2024-04-20 at 16:19, Christoph Anton Mitterer wrote: > On Sat, 2024-04-20 at 07:54 -0400, P. J. McDermott wrote: > > Then the salvage procedure can play out for the full 28+ days > > specified > > by developers-reference (21 days to allow the maintainer to object > > followed by a DELAYED/7 adoption upload). I've already soft-proposed > > to > > salvage in bug #1069280 yesterday. And as mentioned there I'm not > > yet a > > DD or DM, so I'd need to find a sponsor (and access to > > debian/less.git). > > In the light of the recent XZ backdoor, wouldn't it generally be more > desirable to get more co-maintainers, rather than replacing an existing > one? Sure, that's exactly the plan. I don't intend to remove or prevent anyone from co-maintaining src:less. Note that my proposal to adopt, co-maintain, or salvage (bug #1069280) said that I would keep the current maintainer in Uploaders or Maintainer unless he requests otherwise. My intent is not to force out the existing maintainer, but to help where he seems to have been too busy to properly maintain src:less for at least two years. (No shame in being busy, but it looks like the package could use some help keeping up with new upstream releases, security issues like these, etc.) And the repository is already in the "debian" Salsa group (formerly "collab-maint" on Alioth), where any DD can commit to it. Also, if I adopt or salvage src:less, I plan to allow low-threshold NMU[1]. Other than that, I don't know of an appropriate team for it. [1]: https://wiki.debian.org/LowThresholdNmu -- Patrick "P. J." McDermott: http://www.pehjota.net/ Lead Developer, ProteanOS: http://www.proteanos.com/ Founder and CEO, Libiquity: http://www.libiquity.com/
Bug#1064293: less: CVE-2022-48624
On 2024-04-19 at 15:55, Salvatore Bonaccorso wrote: > Hi, > > FWIW, I'm actually preparing a security update for the two CVEs and > for bookworm I was first planning to do a 590-2.1 reaching unstable, > and so then 590-2.1~deb12u1 for bookworm. > > But if you want to override it with a NMU and proposing to salvage the > package this is equally fine. Your DELAYED/2 NMU is probably the fastest and best way to get these CVEs fixed in unstable and bookworm, so that's fine, thanks. Any plans for 551-2 in bullseye? The two patches in your NMU apply cleanly there. Then the salvage procedure can play out for the full 28+ days specified by developers-reference (21 days to allow the maintainer to object followed by a DELAYED/7 adoption upload). I've already soft-proposed to salvage in bug #1069280 yesterday. And as mentioned there I'm not yet a DD or DM, so I'd need to find a sponsor (and access to debian/less.git). If your NMU and my salvaging procedure go through, I'll rebase my work upon and acknowledge your NMU. And I'd like to backport a 643-1 to bookworm and bullseye sloppy (and update bullseye-backports with your NMU, unless you do that). You and I both apparently made the exact same changes to backport the CVE-2024-32487 patch (except your patch still has the original upstream diffstat instead of the backport, which is fine), so that's a good confirmation that my patch was (and yours is) correct. -- Patrick "P. J." McDermott: http://www.pehjota.net/ Lead Developer, ProteanOS: http://www.proteanos.com/ Founder and CEO, Libiquity: http://www.libiquity.com/
Bug#1064293: less: CVE-2022-48624
On 2024-04-12 at 16:10, Christoph Anton Mitterer wrote: > Hey. > > There seems to be a somewhat similar issue reported by Jakub Wilk on > oss-security: > https://www.openwall.com/lists/oss-security/2024/04/12/5 > > where quoting causes troubles (though I couldn't replay the demo). That was since assigned CVE-2024-32487 and Debian bug #1068938. > Any chance to get both fixed in Debian unstable? While the maintainer appears to be somewhat active elsewhere in Debian, this package hasn't seen an upload in over a year and the packaged version is getting close to three years old. (Although I found that updating to the latest upstream release version introduces new test suite and lintian issues requiring some upstream patches backported and reverted/fixed.) In my Salsa fork[1] I have updated the package (fixing CVE-2022-48624) and backported (with necessary code changes) the CVE-2024-32487 fix. I would like to adopt, co-maintain, or if necessary salvage src:less (see bug #1069280). But the procedure[2] for that requires 28 days of waiting for the maintainer to respond. Perhaps in the meantime a new upstream version NMU is warranted, or should the procedure be sped up somehow? [1]: https://salsa.debian.org/pehjota/less [2]: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#how-to-salvage-a-package -- Patrick "P. J." McDermott: http://www.pehjota.net/ Lead Developer, ProteanOS: http://www.proteanos.com/ Founder and CEO, Libiquity: http://www.libiquity.com/
Bug#1065110: ypbind-mt: FTBFS: missing build-dep on libnsl-dev
On Thu, Feb 29, 2024 at 10:03:53PM +0100, Aurelien Jarno wrote: This could be fixed by adding an explicit Build-Depends on libnsl-dev. The glibc change will likely be reverted in the short term, but given its a change we want to do for Trixie, this will only lower the severity of the bug. Regards Aurelien Thanks, this seems the less impacting solution. -- ⢀⣴⠾⠻⢶⣦⠀ Francesco Paolo Lovergine ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ 0579 A97A 2238 EBF9 BE61 ⠈⠳⣄ ED02 0F02 A5E1 1636 86A4
Bug#1063707: liblua5.4-0: C++ library missing all "lua*" function symbols
Control: tags -1 - patch After submitting the aforementioned merge request (and another one with other improvements including CI pipelines), I see now that the patch removal was intentional: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032533 On 2023-03-08 at 14:44, Jackson wrote: > This patchfile undermines that Lua can be built as C++ to manage unwinding > exceptions; according to the date, it has been in the Debian Lua repository > for > over seven years. For example, future releases of MAME (package: mame) will > break using USE_SYSTEM_LUA_LIB if this fallacy not resolved, since they link > their own copy. I'm not sure what this bug report is trying to say or how `extern "C"` (simply preventing C++ name mangling) could undermine or break anything in what is really a C library (C symbol names, just compiled to throw and catch C++ exceptions). (Does MAME link against both a system C++ Lua and its own C Lua copy?) But whatever. And from https://salsa.debian.org/lua-team/lua5.4/-/merge_requests/4#note_444235 > With this we found that the current c++ library in sid is probably broken > (and unused since nobody complained so far) Yes, it is broken, but I'm trying to use it for the upcoming wesnoth-1.18 which can now use a system copy of Lua (after over a month of work toward that goal): https://github.com/wesnoth/wesnoth/pull/8234 Since lua5.4 was promoted to Ubuntu main in 23.10 and Wesnoth now uses Lua without modifications, the goal is for wesnoth-1.18 to use the lua5.4 package supported in Ubuntu main (instead of Wesnoth's embedded code copy stuck in universe) before the Ubuntu Noble Debian Import Freeze on 2024-02-29. So I hope this can somehow be fixed well before then (wesnoth-1.18 still has to go through NEW before that date). I found that the reason it is broken with `extern "C"` removed and name mangling newly enabled is that debian/patches/0001-build-system.patch links using the export map debian/version-script which doesn't list the C++ symbols. Adding the C++ symbols to debian/version-script and debian/liblua5.4-0.symbols as I attempted in the updated merge requests would fix this, however C++ symbol names are architecture-specific. So we'll have to either collect arch-specific names with `(arch=foo)` tags[1] (by making buildds fail for a while[2]) or switch to using shlibs[3]. The wiki recommends shlibs: "For C++ libraries it is often better not to ship symbols files."[1] Sounds good, especially since going through multiple uploads and waiting for buildds to fail would take time. Except switching to shlibs means losing the version information noting that the mangled symbols didn't exist before now, so users who install a package (that uses the C++ library's mangled symbols) without updating liblua5.4-0 will see run-time linker errors. To solve that, we need to also bump the C++ library's SONAME version (which is appropriate anyway, given that the ABI completely changed). So unless you disagree (or beat me to it), I'll work on switching to shlibs and bumping the SONAME version. Restoring `extern "C"` would avoid all this mess and keep the previous unmangled symbols in case anyone was using the C++ library before now. But the previous bug report claims that this breaks something (so let's break everything else instead). [1]: https://wiki.debian.org/UsingSymbolsFiles#C.2B-.2B-_libraries [2]: https://www.eyrie.org/~eagle/journal/2012-01/008.html [3]: https://www.eyrie.org/~eagle/journal/2012-02/001.html -- Patrick "P. J." McDermott: http://www.pehjota.net/ Lead Developer, ProteanOS: http://www.proteanos.com/ Founder and CEO, Libiquity: http://www.libiquity.com/
Bug#1063707: liblua5.4-0: C++ library missing all "lua_*" function symbols
tags -1 + patch thanks https://salsa.debian.org/lua-team/lua5.4/-/merge_requests/5 -- Patrick "P. J." McDermott: http://www.pehjota.net/ Lead Developer, ProteanOS: http://www.proteanos.com/ Founder and CEO, Libiquity: http://www.libiquity.com/
Bug#1063707: liblua5.4-0: C++ library missing all "lua_*" function symbols
Package: liblua5.4-0 Version: 5.4.6-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: p...@pehjota.net Hi, Since version 5.4.6-1, liblua5.4-c++.so.0.0.0 defines no "lua_*" function symbols (only "lua_ident@@LUA_5.4"): $ readelf -s /usr/lib/x86_64-linux-gnu/liblua5.4-c++.so.0.0.0 | grep -F lua_ 101: 000315e0 129 OBJECT GLOBAL DEFAULT 15 lua_ident@@LUA_5.4 $ readelf -s /usr/lib/i386-linux-gnu/liblua5.4-c++.so.0.0.0 | grep -F lua_ 106: 00030600 129 OBJECT GLOBAL DEFAULT 15 lua_ident@@LUA_5.4 Version 5.4.4-3 is OK: $ readelf -s /usr/lib/x86_64-linux-gnu/liblua5.4-c++.so.0.0.0 | grep -F lua_ | head -n 5 102: a610 220 FUNCGLOBAL DEFAULT 13 lua_pus[...]@@LUA_5.4 103: a940 160 FUNCGLOBAL DEFAULT 13 lua_getfield@@LUA_5.4 104: a5e048 FUNCGLOBAL DEFAULT 13 lua_pus[...]@@LUA_5.4 105: b330 273 FUNCGLOBAL DEFAULT 13 lua_set[...]@@LUA_5.4 107: bbf086 FUNCGLOBAL DEFAULT 13 lua_toclose@@LUA_5.4 $ readelf -s /usr/lib/i386-linux-gnu/liblua5.4-c++.so.0.0.0 | grep -F lua_ | head -n 5 107: 678064 FUNCGLOBAL DEFAULT 13 lua_pus[...]@@LUA_5.4 108: 6a10 173 FUNCGLOBAL DEFAULT 13 lua_getfield@@LUA_5.4 109: 674060 FUNCGLOBAL DEFAULT 13 lua_pus[...]@@LUA_5.4 110: 74f0 253 FUNCGLOBAL DEFAULT 13 lua_set[...]@@LUA_5.4 112: 7c3085 FUNCGLOBAL DEFAULT 13 lua_toclose@@LUA_5.4 The problem is that 0003-extern_C.patch was refreshed but mistakenly removed from debian/patches/series in version 5.4.6-1 (commit d46ea48) and then removed completely from debian/patches/ in version 5.4.6-2 (commit 02278c6).
Bug#1035438: cl-quicklisp: installation instructions do not work
Package: cl-quicklisp Version: 20150128-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: msoul...@digitaltorque.ca Dear Maintainer, I followed the instructions in the README msoulier@cortado:~$ sbcl --script /usr/share/common- lisp/source/quicklisp/quicklisp.lisp quicklisp quickstart 2015-01-28 loaded To continue with installation, evaluate: (quicklisp-quickstart:install) For installation options, evaluate: (quicklisp-quickstart:help) So I loaded sbcl and ran the command: * (quicklisp-quickstart:install) debugger invoked on a SB-INT:SIMPLE-READER-PACKAGE-ERROR in thread #: Package QUICKLISP-QUICKSTART does not exist. So the installation did not make the library available, and it cannot be used. -- System Information: Debian Release: 11.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-21-amd64 (SMP w/8 CPU threads) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cl-quicklisp depends on: ii sbcl [lisp-compiler] 2:2.1.1-2 cl-quicklisp recommends no packages. cl-quicklisp suggests no packages.
Bug#1022070: Info received (Booting semi-hangs with 'drm_atomic_helper_wait_for_flip_done' errors and alike)
... and of course I managed to make a typo. It should be Kernel: 5.10.0-19-amd64 x86_64 as in the original report. Apologies for the noise. Peter Van: Debian Bug Tracking System Verzonden: donderdag 20 oktober 2022 14:12 Aan: Kroon P C, Peter Onderwerp: Bug#1022070: Info received (Booting semi-hangs with 'drm_atomic_helper_wait_for_flip_done' errors and alike) Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): unknown-pack...@qa.debian.org If you wish to submit further information on this problem, please send it to 1022...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1022070: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.debian.org%2Fcgi-bin%2Fbugreport.cgi%3Fbug%3D1022070&data=05%7C01%7Cp.c.kroon%40pl.hanze.nl%7C8e4d84cbae284876a89308dab2945783%7Ca3b390147adc48faa11437c2434dbd69%7C0%7C0%7C638018647788582517%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Tt9qgmwWl2%2BPfXgtY1OecRmGRLiVLvJFBQImbWU97Ok%3D&reserved=0 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022070: Booting semi-hangs with 'drm_atomic_helper_wait_for_flip_done' errors and alike
Hi all, I'm encountering the same issue on the following hardware: Kernel: 5.10.0-18-amd64 x86_64 bits: 64 Distro: Debian GNU/Linux 11 (bullseye) Machine type: Mini-pc System: ASUSTeK product: MINIPC PN50 UEFI: ASUSTeK CPU Info: Quad Core AMD Ryzen 3 4300U with Radeon Graphics [MCP] speed: 1367 MHz min/max: 1400/2700 MHz Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel Display server: X.org 1.20.11 loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa Happy to help, let me know if I can provide more details. Peter
Bug#1012600:
The 2.1.5 packages have made their way into bookworm, and my system is now happily running kernel 5.18 with ZFS.
Bug#1012600:
I'm no expert, but since these packages are in 'contrib' I suspect they don't have the ability to block package upgrades in 'main'. On Sun, Jun 19, 2022 at 5:51 AM Chris Putnam wrote: > > Apologies if this question is well-answered, but why isn't this package > holding back the kernel to 5.17? In my mind an "apt upgrade" should not have > pulled 5.18, especially when the net result may well be an unbootable system. > Surely there's some way to mark this package as broken in tandem with 5.18? > > I'm also quite surprised this wasn't caught in sid before it was pulled into > testing. Is there any form of testing for this package going on in sid?
Bug#1012637: libsystemd-shared: libsystemd-share dependency problem prevents configuration of systemd
It occurs when the command 'lb bootstrap' from the 'live-build' package is run, which in turn runs '/usr/lib/live/build/bootstrap' On 6/10/22 14:06, Michael Biebl wrote: Control: tags -1 + moreinfo Am 10.06.22 um 22:53 schrieb Felicia P: Package: libsystemd-shared Version: 251.2-4 Severity: important Dear Maintainer, While running the scripts to build a Debian-live system the following command is failing apparently due to an issue with libsystemd-shared_251.2-4_amd64.deb: Please provide instructions how this problem can be reproduced (i.e. please provide the full scripts that you are using).
Bug#1011720: python-apt also fails with this error
Building python-apt 2.3.0 also fails with the same error, so I suspect the cause is in libapt-pkg, not libqapt.
Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads
Hello Diederik, Thanks for your quick reply: Am Sa., 19. Feb. 2022, um 22:36 +0100 schrieb Diederik de Haas : > On Saturday, 19 February 2022 22:04:14 CET Petra R.-P. wrote: > > Package: src:linux > > Version: 5.16.7-2 [...] > > pn firmware-iwlwifi > > I see you don't have firmware-iwlwifi installed, but there have been other > bug > reports which could be similar, so with the 5.15 kernel, do you have the > 'iwlwifi' kernel module loaded? On one of the old Thinkpads in question, running the 5.15 kernel: ~ > lsmod | grep iwlwifi ~ > lsmod | grep wifi ~ > So I suppose that module is _not_ loaded ... > If so, could you blacklist that and try to > reboot into the 5.16 kernel and see whether it then works? Nevertheless, I created /etc/modprobe.d/blacklist.conf as root, and: ~ > cat /etc/modprobe.d/blacklist.conf blacklist iwlwifi ~ > Sadly, this has no effect whatsoever on the 5.16.0-1 kernel. When trying to boot it it 'hangs' exactly as before. Thanks all the same, and best regards, Petra
Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads
Package: src:linux Version: 5.16.7-2 Severity: critical Justification: breaks the whole system Dear Maintainer, This new kernel version does not boot on two fairly similar old IBM T41 Thinkpads. What reproducibly happens is as follows: After the lines Loading Linux 5.16.0-1-686 ... Loading initial ramdisk ... the screen gets flushed, and I see: [ 4.xx] ata1.00: Read log 0x00 page 0x00 failed Emask 0x1 The "xx" vary for every try. Then nothing else happens. Ctrl-Alt-Del has no effect. I have to reset the computer by pressing the button. On an old PC running the same kernel the same message "ata1.00: Read log ..." appears, but then the boot process continues normally. linux-image-5.15.0-3-686, which I am using to write this message, runs fine. Thanks for maintaining this package and best regards, Petra R.-P. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O Controller [8086:3340] (rev 03) Subsystem: IBM Thinkpad T40 series [1014:0529] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP Controller [8086:3341] (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01) (prog-if 00 [UHCI]) Subsystem: IBM ThinkPad [1014:052d] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 81) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge [8086:24cc] (rev 01) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: snd_intel8x0 Kernel modules: snd_intel8x0 00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller [8086:24c6] (rev 01) (prog-if 00 [Generic]) Subsystem: IBM ThinkPad T4x Series [1014:0524] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: snd_intel8x0m Kernel modules: snd_intel8x0m 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV200/M7 [Mobility Radeon 7500] [1002:4c57] (prog-if 00 [VGA controller]) Subsystem: IBM ThinkPad T4x Series [1014:0530] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B+ DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: radeon Kernel modules: radeonfb, radeon 02:00.0 CardBus bridge [0607]: Texas Instruments PCI4520 PC card Cardbus Controller [104c:ac46] (rev 01) Subsystem: IBM ThinkPad [1014:0552] Physical Slot: 1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset+ 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 Capabilities: Kernel driver in use: yenta_cardbus Kernel modules: yenta_socket 02:00.1 CardBus bridge [0607]: Texas Instruments PCI4520 PC card Cardbus Controller [104c:ac46] (rev 01) Subsystem: IBM ThinkPad [1014:0552] Physical Slot: 1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- Fas
Bug#997430: xaw3d: FTBFS: -q: invalid option -- '.'
tags 997430 + help
thanks
On Sat, Oct 23, 2021 at 10:36:29PM +0200, Lucas Nussbaum wrote:
Source: xaw3d
Version: 1.5+F-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
[...]
This seems more a breakage in binutils and/or xmkmf generated Makefile, than a
problem in the problem in the Imakefile per se, which does not define anything
related to the static library linkage.
Any ideas would be appreciated about this issue.
rm -f libXaw3d.so.6.1~
+ cd .
+ gcc -o ./libXaw3d.so.6.1~ -shared -Wl,-soname,libXaw3d.so.6 AllWidgets.o
AsciiSink.o AsciiSrc.o AsciiText.o Box.o Command.o Dialog.o Form.o Grip.o
Label.o Layout.o List.o MenuButton.o Paned.o Panner.o Porthole.o Repeater.o
Scrollbar.o Simple.o SimpleMenu.o Sme.o SmeBSB.o SmeLine.o SmeThreeD.o
StripChart.o Text.o TextSink.o TextSrc.o TextAction.o TextPop.o TextTr.o
ThreeD.o Tip.o Toggle.o Tree.o Vendor.o Viewport.o Xaw3dP.o XawInit.o laygram.o
laylex.o MultiSrc.o MultiSink.o XawIm.o XawI18n.o -lXmu -lXt -lSM -lICE -lXext
-lX11 -lXt -lSM -lICE -lXpm -lXext -lX11 -lc
/usr/bin/ld: AsciiSrc.o: in function `InitStringOrFile':
/<>/xc/lib/Xaw3d/AsciiSrc.c:1067: warning: the use of `tmpnam' is
dangerous, better use `mkstemp'
+ rm -f libXaw3d.so.6
+ ln -s libXaw3d.so.6.1 libXaw3d.so.6
rm -f libXaw3d.so.6.1
mv -f libXaw3d.so.6.1~ libXaw3d.so.6.1
+ rm -f libXaw3d.so
+ ln -s libXaw3d.so.6.1 libXaw3d.so
rm -f libXaw3d.a
+ cd unshared
+ ar clq ../libXaw3d.a AllWidgets.o AsciiSink.o AsciiSrc.o AsciiText.o Box.o
Command.o Dialog.o Form.o Grip.o Label.o Layout.o List.o MenuButton.o Paned.o
Panner.o Porthole.o Repeater.o Scrollbar.o Simple.o SimpleMenu.o Sme.o SmeBSB.o
SmeLine.o SmeThreeD.o StripChart.o Text.o TextSink.o TextSrc.o TextAction.o
TextPop.o TextTr.o ThreeD.o Tip.o Toggle.o Tree.o Vendor.o Viewport.o Xaw3dP.o
XawInit.o laygram.o laylex.o MultiSrc.o MultiSink.o XawIm.o XawI18n.o
-q: invalid option -- '.'
Usage: ar [emulation options] [-]{dmpqrstx}[abcDfilMNoOPsSTuvV] [--plugin
] [member-name] [count] archive-file file...
ar -M [ ] - specify the dependencies of this library
[S] - do not build a symbol table
[T] - make a thin archive
[v] - be verbose
[V] - display the version number
@ - read options from
--target=BFDNAME - specify the target object format as BFDNAME
--output=DIRNAME - specify the output directory for extraction operations
--record-libdeps= - specify the dependencies of this library
optional:
--plugin - load the specified plugin
emulation options:
No emulation specific options
ar: supported targets: elf64-x86-64 elf32-i386 elf32-iamcu elf32-x86-64
pei-i386 pe-x86-64 pei-x86-64 elf64-l1om elf64-k1om elf64-little elf64-big
elf32-little elf32-big pe-bigobj-x86-64 pe-i386 srec symbolsrec verilog tekhex
binary ihex plugin
make[2]: *** [Makefile:1158: libXaw3d.a] Error 1
--
Francesco P. Lovergine
Bug#989929: Suddenly restarting fetchmail started to fail with error about its global pidfile
On Thu, Jun 24, 2021 at 07:11:02PM +0200, László Böszörményi (GCS) wrote: Control: tags -1 +pending moreinfo On Wed, Jun 16, 2021 at 10:00 AM Francesco P. Lovergine wrote: This is currently run on testing since ages. I had to restart due to a changed fingerprint and the global service started to fail with: [...] giu 16 08:07:28 klecker fetchmail[846499]: fetchmail: lock creation failed, pidfile "/run/fetchmail/fetchmail.pid": File o directory non esistente Thanks for the report and the proposed fix! Can you please check if the updated package[1] is fine for you now? Cheers, Laszlo/GCS [1] dget -x https://people.debian.org/~gcs/fetchmail_6.4.16-2.dsc Yes it is working. -- Francesco P. Lovergine
Bug#989929: Suddenly restarting fetchmail started to fail with error about its global pidfile
Package: fetchmail Version: 6.4.16-1 Severity: grave This is currently run on testing since ages. I had to restart due to a changed fingerprint and the global service started to fail with: $ systemctl status fetchmail.service ● fetchmail.service - LSB: init-Script for system wide fetchmail daemon Loaded: loaded (/etc/init.d/fetchmail; generated) Active: active (exited) since Wed 2021-06-16 08:07:28 CEST; 1h 23min ago Docs: man:systemd-sysv-generator(8) Tasks: 0 (limit: 9313) Memory: 0B CPU: 0 CGroup: /system.slice/fetchmail.service giu 16 08:07:28 klecker systemd[1]: Starting LSB: init-Script for system wide fetchmail daemon... giu 16 08:07:28 klecker fetchmail[846490]: Starting mail retriever agent: fetchmail. giu 16 08:07:28 klecker systemd[1]: Started LSB: init-Script for system wide fetchmail daemon. giu 16 08:07:28 klecker fetchmail[846499]: starting fetchmail 6.4.16 daemon giu 16 08:07:28 klecker fetchmail[846499]: fetchmail: lock creation failed, pidfile "/run/fetchmail/fetchmail.pid": File o directory non esistente The /run/fetchmail directory ownership is correct (fetchmail:nogroup) and if I start the process by hand with: sudo -u fetchmail -- fetchmail --pidfile /run/fetchmail/fetchmail.pid --nosslcertck -f /etc/fetchmailrc --syslog it works regularly. So the problem is with the init script, still used by systemd. Here: start-stop-daemon -S -o -q -p $PIDFILE -x $DAEMON -u $USER -c $USER -- $OPTIONS; I think the problem resides. I see that the pidfile is passed at the same time to start-stop-daemon and the daemon (-p and $OPTIONS) which run in unprivileged mode. I changed the instruction into: start-stop-daemon -S -o -q -x $DAEMON -u $USER -c $USER -- $OPTIONS; and now it works. Note that currently man page reports: Warning: Using this match option with a world-writable pidfile or using it alone with a daemon that writes the pidfile as an unprivileged (non-root) user will be refused with an error (since version 1.19.3) as this is a security risk, because either any user can write to it, or if the daemon gets compromised, the contents of the pidfile cannot be trusted, and then a privileged runner (such as an init script executed as root) would end up acting on any system process. Using /dev/null is exempt from these checks. and bullseye runs dpkg v1.20.9 currently. I'm tagging this bug as grave because even if fetchmail is not always used in daemon mode, it breaks for sure existing configurations in an unexpected way (and the reason is quite obscure for the casual user) - cheers -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fetchmail depends on: ii adduser 3.118 ii debianutils 4.11.2 ii libc6 2.31-12 ii libcom-err2 1.46.2-1 ii libgssapi-krb5-2 1.18.3-5 ii libkrb5-3 1.18.3-5 ii libssl1.1 1.1.1k-1 ii lsb-base 11.1.0 Versions of packages fetchmail recommends: ii ca-certificates 20210119 Versions of packages fetchmail suggests: ii exim4-daemon-heavy [mail-transport-agent] 4.94.2-5 pn fetchmailconf pn resolvconf -- Configuration Files: /etc/default/fetchmail changed: OPTIONS=--nosslcertck START_DAEMON=yes PIDFILE=/run/fetchmail/fetchmail.pid -- no debconf information -- Francesco P. Lovergine
Bug#988322: brave-browser: random crashes since latest upgrade
Package: brave-browser Version: 1.22.71 Severity: grave Justification: causes non-serious data loss Dear Maintainer, I have noticed since my latest upgrade that brave-browser is randomly crashing when it seemed quite solid before. I have maybe 20 random tabs open, sometimes multiple to youtube and one to a video conference site. When it comes back up it offers to restore pages, and I try to pick up where it left off. -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-16-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages brave-browser depends on: ii brave-keyring 1.10 ii ca-certificates 20200601~deb10u2 ii dpkg1.19.7 ii fonts-liberation1:1.07.4-9 ii libasound2 1.1.8-1 ii libatk-bridge2.0-0 2.30.0-5 ii libatk1.0-0 2.30.0-2 ii libatspi2.0-0 2.30.0-7 ii libc6 2.28-10 ii libcairo2 1.16.0-4+deb10u1 ii libcups22.2.10-6+deb10u4 ii libdbus-1-3 1.12.20-0+deb10u1 ii libdrm2 2.4.97-1 ii libexpat1 2.2.6-2+deb10u1 ii libgbm1 18.3.6-2+deb10u1 ii libgcc1 1:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-02.58.3-2+deb10u2 ii libgtk-3-0 3.24.5-1 ii libnspr42:4.20-1 ii libnss3 2:3.42.1-1+deb10u3 ii libpango-1.0-0 1.42.4-8~deb10u1 ii libx11-62:1.6.7-1+deb10u1 ii libxcb1 1.13.1-2 ii libxcomposite1 1:0.4.4-2 ii libxdamage1 1:1.1.4-3+b3 ii libxext62:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxkbcommon0 0.8.2-1 ii libxrandr2 2:1.5.1-1 ii libxshmfence1 1.3-1 ii wget1.20.1-1.1 ii xdg-utils 1.1.3-1+deb10u1 Versions of packages brave-browser recommends: ii libu2f-udev 1.1.9-1 ii libvulkan1 1.1.97-2 brave-browser suggests no packages. -- no debconf information
Bug#984616: nis: prompting due to modified conffiles which were not modified by the user: /etc/default/nis
On Fri, Mar 05, 2021 at 09:57:27PM +0100, Andreas Beckmann wrote: during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... This is a violation of policy 10.7.3, see https://www.debian.org/doc/debian-policy/ch-files.html#behavior, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens." This is a non sense, the 4 series is proposing a relevant change to the system, that is having all services off in that stupid file (the previous insane default was having the system in client+broadcast mode). The simple mechanism of conffiles can only undestand if the new default is different from the current file, not if the user maintained that on purpose or not. So a the question IS relevant. The whole wide changes are explained in the NEWS file and a sane admin will prefer to have all services stopped and act for the better. -- Francesco P. Lovergine
Bug#980030: vim-gtk3: gvim Could not load pixbuf defaults to vim with no gui
Package: vim-gtk3 Version: 2:8.2.1913-1+b2 Severity: grave Justification: renders package unusable Dear Maintainer, After latest system update gvim does not load gui.It shows following error messages. * (gvim:1792): Gtk-WARNING **: 12:28:53.889: Could not load a pixbuf from /org/gtk/libgtk/icons/16x16/status/image-missing.png. This may indicate that pixbuf loaders or the mime database could not be found. ** Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3) Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3) Vim: Caught deadly signal ABRT Vim: Finished. E852: The child process failed to start the GUI Press ENTER or type command to continue * Tried update-mime-database /usr/share/mime and also /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders --update-cache Also tried after removing .vimrc. -- Package-specific info: --- real paths of main Vim binaries --- /usr/bin/vi is /usr/bin/vim.gtk3 /usr/bin/vim is /usr/bin/vim.gtk3 /usr/bin/gvim is /usr/bin/vim.gtk3 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=ml_IN.UTF-8@pvm, LC_CTYPE=ml_IN.UTF-8@pvm (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vim-gtk3 depends on: ii libacl1 2.2.53-9 ii libc62.31-9 ii libcairo21.16.0-5 ii libcanberra0 0.30-7 ii libgdk-pixbuf2.0-0 2.40.2-2 ii libglib2.0-0 2.66.4-1 ii libgpm2 1.20.7-6 ii libgtk-3-0 3.24.24-1 ii libice6 2:1.0.10-1 ii liblua5.2-0 5.2.4-1.1+b3 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libperl5.32 5.32.0-6 ii libpython3.9 3.9.1-1 ii libruby2.7 2.7.2-3 ii libselinux1 3.1-2+b2 ii libsm6 2:1.2.3-1 ii libtcl8.68.6.11+dfsg-1 ii libtinfo66.2+20201114-2 ii libx11-6 2:1.6.12-1 ii libxt6 1:1.2.0-1 ii vim-common 2:8.2.1913-1 ii vim-gui-common 2:8.2.1913-1 ii vim-runtime 2:8.2.1913-1 vim-gtk3 recommends no packages. Versions of packages vim-gtk3 suggests: pn cscope ii fonts-dejavu 2.37-2 ii gnome-icon-theme 3.12.0-3 pn vim-doc -- no debconf information
Bug#978340: proftpd-mod-dnsbl: FTBFS: Cannot compile mod_dnsbl using prxs
Oh well, proftpd-mod-dnsbl is now obsoleted by proftpd-core who also Provides it in sid, and the source package should be removed in testing/sid to allow migration of current proftpd. I have a lapsus about that, should I ask an explicit remove to d-release? On Sat, Dec 26, 2020 at 11:08:09PM +0100, Lucas Nussbaum wrote: Source: proftpd-mod-dnsbl Version: 0.1.5-5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/<>' DESTDIR=/<>/debian/proftpd-mod-dnsbl prxs -c mod_dnsbl.c Cannot compile mod_dnsbl using prxs; use existing ./configure script instead: ./configure make make install make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/12/26/proftpd-mod-dnsbl_0.1.5-5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-proftpd-maintainers mailing list pkg-proftpd-maintain...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-proftpd-maintainers -- Francesco P. Lovergine
Bug#977349: Current package does not ensure a smooth upgrade from stable due to breakage of past config and new binary modules.
On Tue, Dec 15, 2020 at 09:01:51PM +0100, Hilmar Preuße wrote: Am 14.12.2020 um 11:02 teilte Francesco Paolo Lovergine mit: Hi Paolo, After upgrade: $ sudo proftpd -t Checking syntax of configuration file 2020-12-14 09:59:09,942 legolas proftpd[5444]: mod_dso/0.5: unable to load 'mod_tls.c'; check to see if '/usr/lib/proftpd/mod_tls.la' exists Please note that put the new packages into the Recommend line of proftp-basic. So people using a default apt config would get both new packages. At least on one of my installations this worked fine. Not in general, the default policy of installing Recommends could be relaxed by users for all packages in /etc/apt/apt.conf or even for single upgrades by options in apt-get/aptitude. So it would be a policy violation in any case. Not sure if this is the correct migration path according to policy. I'm sorry for the work I've caused! Well, there were in any case other details to manage. -- Francesco P. Lovergine
Bug#977090: The 1.3.7a original tarball includes IETF RFCs documents
Source: proftpd-dfsg Version: 1.3.7a-1 Severity: serious Justification: Policy 2.2.1 As in subject, the RFCs need to be stripped before uploading a new upstream tarball, because not compliant to DFSG. That step was missed at the time of upload. -- Francesco P. Lovergine
Bug#973630: fetchmail: OpenSSL library mismatch
Package: fetchmail Version: 6.4.13-1 Severity: grave Justification: renders package unusable Dear Maintainer, after the upgrade of today fetchmail is not anymore able to use OpenSSL. Upon calling fetchmail from mutt I get the following fatal error. fetchmail: Query status=2 (SOCKET) fetchmail: Loaded OpenSSL library 0x1010107f older than headers 0x1010108f, refusing to work. I think it's a kind of library mismatch. Best regards Giorgio -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=it_CH.UTF-8, LC_CTYPE=it_CH.UTF-8 (charmap=UTF-8), LANGUAGE=it_CH:it Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fetchmail depends on: ii adduser 3.118 ii debianutils 4.11.2 ii libc6 2.31-4 ii libcom-err2 1.45.6-1 ii libgssapi-krb5-2 1.17-10 ii libkrb5-3 1.17-10 ii libssl1.1 1.1.1g-1 ii lsb-base 11.1.0 Versions of packages fetchmail recommends: ii ca-certificates 20200601 Versions of packages fetchmail suggests: ii exim4-daemon-light [mail-transport-agent] 4.94-8 pn fetchmailconf pn resolvconf -- no debconf information
Bug#949518: (no subject)
A work-around is to uninstall ufw and install firewalld with firewall-config. For uncomplicated firewall configurations, the firewall-config GUI can be used to reconfigure the desired rules. On Tue, Feb 11, 2020 at 8:03 AM Vasanth Srivatsa wrote: > Is this bug fixed or still open? When can users expect a fix (approximate > time)? I have servers which are non-functional due to this bug. I just > updated them yesterday and they are blocking all incoming connections. > [image: Sent from Mailspring]
Bug#949644: libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0
I can confirm this bug. Downloading and installing the previous sqlite3 and libsqlite3 packages fixes the issue https://snapshot.debian.org/package/sqlite3/ look for versions 3.30.1+fossil191229-1 # dpkg -i libsqlite3-0_3.30.1+fossil191229-1_amd64.deb sqlite3_3.30.1+fossil191229-1_amd64.deb libsqlite3-0_3.30.1+fossil191229-1_i386.deb 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#947907: Same here
Also experiencing this same bug. $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux bullseye/sid Release: unstable Codename: sid ii ure 6.4.0~rc1-4 amd64 LibreOffice UNO runtime environment 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#943664: xserver-xorg-video-radeon 19.1 (ppc64) crash at startup: undefined symbol: exaGetPixmapDriverPrivate
Hi. I assume that the error occurs on the PPC64 system because of disabled HA (Hardware Acceleration) too: According to https://bugs.freedesktop.org/show_bug.cgi?id=99851 a "ring 0 test failed" message from drm means that HA gets disabled. dmesg | grep -i drm [5.621228] [drm] radeon kernel modesetting enabled. [5.662906] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68FA 0x174B:0xE127 0x00). [5.974683] [drm] GPU not posted. posting now... [6.017017] [drm] Detected VRAM RAM=1024M, BAR=256M [6.017018] [drm] RAM width 64bits DDR [6.082254] [drm] radeon: 1024M of VRAM memory ready [6.195713] [drm] radeon: 1024M of GTT memory ready. [6.220009] [drm] Loading CEDAR Microcode [6.335990] [drm] Internal thermal controller with fan control [6.364947] [drm] radeon: dpm initialized [6.396903] [drm] GART: num cpu pages 16384, num gpu pages 262144 [6.458639] [drm] PCIE GART of 1024M enabled (table at 0x0015). [6.531588] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [6.576700] [drm] Driver supports precise vblank timestamp query. [6.641177] [drm] radeon: irq initialized. [6.834702] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [6.863707] [drm] Radeon Display Connectors [6.880862] [drm] Connector 0: [6.880863] [drm] DVI-I-1 [6.880865] [drm] HPD2 [6.880867] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c [6.880868] [drm] Encoders: [6.880869] [drm] DFP1: INTERNAL_UNIPHY1 [6.880870] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [6.880875] [drm] Connector 1: [6.902720] [drm] DVI-I-2 [6.913316] [drm] HPD4 [6.987101] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c [7.001856] [drm] Encoders: [7.007757] [drm] DFP2: INTERNAL_UNIPHY [7.016093] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [7.112647] [drm] fb mappable at 0x9036 [7.120638] [drm] vram apper at 0x9000 [7.128797] [drm] size 7733248 [7.134875] [drm] fb depth is 24 [7.141298] [drm]pitch is 6400 [7.212427] radeon :0a:00.0: fb0: radeondrmfb frame buffer device [7.238821] [drm] Initialized radeon 2.50.0 20080528 for :0a:00.0 on minor 0 I tested these kernel versions: 4.18.0-3-powerpc64 (official kernel from Debian PPC64 sid) 4.19.28-rt16 (self compiled, with realtime patches) Both result in "ring 0 test failed". In my opinion it would be great if: 1) xserver-xorg-video-radeon_1%3a19.1.0-1 would not fail but fall back to frame buffer device like xserver-xorg-video-radeon_1%3a19.0.1-1 2) the "ring 0 test" would not fail According to the last post from the link above the failure was seen in 4.14.4 and 4.15-rc2 but not in kernel 4.17.2. Maybe I should get/compile a linux 4.17.2 kernel. Thank you and best regards, Ralf
Bug#943664: xserver-xorg-video-radeon: Same behaviour on Thinkpad T41
Am Mo., 4. Nov. 2019, um 09:13 +0100 schrieb Michel Dänzer : > On 2019-11-01 5:25 p.m., Petra R.-P. wrote: > > > > Section "Device" > > Identifier "Configured Video Device" > > Driver"modesetting" > > EndSection [...] > On this machine, you need to add > > Option "AccelMethod" "none" > > to Section "Device". Thanks an awful lot! This solved the problem for me :-) Best regards, Petra
Bug#943664: xserver-xorg-video-radeon: Same behaviour on Thinkpad T41
Am Fr., 1. Nov. 2019, um 17:25 +0100 schrieb Petra R.-P. : > Maybe I should mention that this old notebook is running with an > external monitor because its own display is faulty. I have just performed the (weekly) Debian testing updates on my other computers (the problematic notebook I was writing about is updated on a daily basis): -> another Thinkpad T41, but with intact display and without external monitor, -> a Thinkpad T420, -> a "normal" PC. There was no problem with any of them :-) So the cause of the problem may well be the external monitor, or HW acceleration. How can I find out if this is activated in the "good" T41? Best regards, Petra
Bug#943664: xserver-xorg-video-radeon: Same behaviour on Thinkpad T41
On Thu 31 Oct 2019 at 20:39:18 +0100 Michel Dänzer wrote: > We'd again need to see the corresponding Xorg log file. 1. Modified /etc/X11/xorg.conf : # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de" # Option"XkbVariant""nodeadkeys" Option"XkbOptions" "compose:caps" # P. R.-P., Mo., 25. Mai 2009 EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" Driver"modesetting" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection 2. /home/petra/.local/share/xorg/Xorg.0.log : [ 451.063] X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 [ 451.063] Build Operating System: Linux 4.9.0-8-amd64 i686 Debian [ 451.064] Current Operating System: Linux netty 5.2.0-3-686 #1 SMP Debian 5.2.17-1 (2019-09-26) i686 [ 451.064] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.2.0-3-686 root=UUID=496e0e0a-6e7c-46c2-9132-315243394a2d ro framebuffer=false quiet fb=false systemd.show_status=true [ 451.065] Build Date: 05 March 2019 08:11:12PM [ 451.065] xorg-server 2:1.20.4-1 (https://www.debian.org/support) [ 451.065] Current version of pixman: 0.36.0 [ 451.066]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 451.066] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 451.068] (==) Log file: "/home/petra/.local/share/xorg/Xorg.0.log", Time: Thu Oct 31 21:08:45 2019 [ 451.098] (==) Using config file: "/etc/X11/xorg.conf" [ 451.106] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 451.232] (==) No Layout section. Using the first Screen section. [ 451.232] (**) |-->Screen "Default Screen" (0) [ 451.232] (**) | |-->Monitor "Configured Monitor" [ 451.268] (==) No device specified for screen "Default Screen". Using the first device section listed. [ 451.268] (**) | |-->Device "Configured Video Device" [ 451.268] (==) Automatically adding devices [ 451.268] (==) Automatically enabling devices [ 451.268] (==) Automatically adding GPU devices [ 451.268] (==) Max clients allowed: 256, resource mask: 0x1f [ 451.369] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 451.369]Entry deleted from font path. [ 451.509] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 451.509] (==) ModulePath set to "/usr/lib/xorg/modules" [ 451.509] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 451.509] (II) Loader magic: 0x6eb740 [ 451.509] (II) Module ABI versions: [ 451.509]X.Org ANSI C Emulation: 0.4 [ 451.509]X.Org Video Driver: 24.0 [ 451.509]X.Org XInput driver : 24.1 [ 451.509]X.Org Server Extension : 10.0 [ 451.512] (++) using VT number 1 [ 451.519] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_35 [ 451.522] (II) xfree86: Adding drm device (/dev/dri/card0) [ 451.524] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0 [ 451.531] (--) PCI:*(1@0:0:0) 1002:4c57:1014:0530 rev 0, Mem @ 0xe000/134217728, 0xc010/65536, I/O @ 0x3000/2
Bug#943664: xserver-xorg-video-radeon: Same behaviour on Thinkpad T41
Am Do., 31. Okt. 2019, um 18:01 +0100 schrieb Michel Dänzer : > On 2019-10-30 2:15 p.m., Petra R.-P. wrote: > This happens when HW acceleration is disabled. If you can't or don't > want to enable HW acceleration, I can't because I don't know how to do this. > I recommend using the Xorg modesetting > driver for the time being, by either uninstalling > xserver-xorg-video-radeon or explicitly setting the driver in > /etc/X11/xorg.conf, see below. Without HW acceleration, the radeon > driver doesn't really provide much if any benefit over modesetting. > > > Section "Device" > > Identifier "whateveryoulike" > > Driver "modesetting" > > EndSection I tried both variants without success. Both resulted in something like Server terminated with error (1). xinit: giving up xinit: unable to connect to X server: Conncection refused xinit: server error Old xserver-xorg-video-radeon 19.0.1-1 still works fine :-) Petra
Bug#943664: xserver-xorg-video-radeon: Same behaviour on Thinkpad T41
Package: xserver-xorg-video-radeon Version: 1:19.1.0-1 Followup-For: Bug #943664 Dear Maintainer, I can confirm every detail of the original report, except that this happens here on an old IBM Thinkpad T 41. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 May 22 2009 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Mar 5 2019 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV200/M7 [Mobility Radeon 7500] [1002:4c57] Xorg X server configuration file status: -rw-r--r-- 1 root root 1183 May 25 2009 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de" # Option"XkbVariant""nodeadkeys" Option"XkbOptions" "compose:caps" # P. R.-P., Mo., 25. Mai 2009 EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 5.2.0-3-686 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-22)) #1 SMP Debian 5.2.17-1 (2019-09-26) Xorg X server log files on system: -- -rw-r--r-- 1 root root 36267 Aug 8 2015 /var/log/Xorg.1.log -rw-r--r-- 1 root root 37471 Oct 25 2015 /var/log/Xorg.0.log -rw-r--r-- 1 petra petra 46383 Mar 10 2018 /home/petra/.local/share/xorg/Xorg.2.log -rw-r--r-- 1 petra petra 46383 Mar 10 2018 /home/petra/.local/share/xorg/Xorg.3.log -rw-r--r-- 1 petra petra 46383 Mar 10 2018 /home/petra/.local/share/xorg/Xorg.4.log -rw-r--r-- 1 petra petra 46383 Mar 10 2018 /home/petra/.local/share/xorg/Xorg.5.log -rw-r--r-- 1 petra petra 46383 Mar 10 2018 /home/petra/.local/share/xorg/Xorg.6.log -rw-r--r-- 1 petra petra 46383 Mar 10 2018 /home/petra/.local/share/xorg/Xorg.7.log -rw-r--r-- 1 petra petra 46383 Mar 10 2018 /home/petra/.local/share/xorg/Xorg.8.log -rw-r--r-- 1 petra petra 51769 Mar 10 2018 /home/petra/.local/share/xorg/Xorg.9.log -rw-r--r-- 1 petra petra 53220 Mar 10 2018 /home/petra/.local/share/xorg/Xorg.10.log -rw-r--r-- 1 petra petra 52334 Mar 10 2018 /home/petra/.local/share/xorg/Xorg.11.log -rw-r--r-- 1 petra petra 54232 Mar 10 2018 /home/petra/.local/share/xorg/Xorg.12.log -rw-r--r-- 1 petra petra 37588 Oct 30 13:52 /home/petra/.local/share/xorg/Xorg.1.log -rw-r--r-- 1 petra petra 24233 Oct 30 14:05 /home/petra/.local/share/xorg/Xorg.0.log Contents of most recent Xorg X server log file (/home/petra/.local/share/xorg/Xorg.0.log): -- [ 122.848] X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 [ 122.849] Build Operating System: Linux 4.9.0-8-amd64 i686 Debian [ 122.849] Current Operating System: Linux netty 5.2.0-3-686 #1 SMP Debian 5.2.17-1 (2019-09-26) i686 [ 122.850] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.2.0-3-686 root=UUID=496e0e0a-6e7c-46c2-9132-315243394a2d ro framebuffer=false quiet fb=false systemd.show_status=true [ 122.850] Build Date: 05 March 2019 08:11:12PM [ 122.851] xorg-server 2:1.20.4-1 (https://www.debian.org/support) [ 122.851] Current version of pixman: 0.36.0 [ 122.851]Before reporting problems, check http://wiki.x.org
Bug#943664: xserver-xorg-video-radeon 19.1 (ppc64) crash at startup: undefined symbol: exaGetPixmapDriverPrivate
Package: xserver-xorg-video-radeon Version: 1:19.0.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, on the ppc64 architecture the package xserver-xorg-video-radeon_1%3a19.1.0-1_ppc64.deb crashes the xserver at startup. Xorg complains about an undefined symbol: exaGetPixmapDriverPrivate The bug occured after an update from: xserver-xorg-video-radeon_1%3a19.0.1-1_ppc64.deb to:xserver-xorg-video-radeon_1%3a19.1.0-1_ppc64.deb To make sure the bug is in xserver-xorg-video-radeon 19.1.0-1 I switched several times between these two versions of the package. As soon as version 19.0.1-1 is installed, Xorg runs well. Log from Xorg (in console): X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.19.0-2-powerpc64 ppc64 Debian Current Operating System: Linux g5-1 4.19.28-rt16rp1 #1 SMP Tue Apr 30 21:12:53 CEST 2019 ppc64 Kernel command line: BOOT_IMAGE=/boot/vmlinux-4.19.28-rt16rp1 root=UUID=0b889fec-98b2-4e34-ade1-1a43105f8417 ro Build Date: 05 March 2019 08:11:12PM xorg-server 2:1.20.4-1 (https://www.debian.org/support) Current version of pixman: 0.36.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/home/ralf/.local/share/xorg/Xorg.1.log", Time: Sun Oct 27 15:29:03 2019 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (II) [KMS] Kernel modesetting enabled. /usr/lib/xorg/Xorg: symbol lookup error: /usr/lib/xorg/modules/drivers/radeon_drv.so: undefined symbol: exaGetPixmapDriverPrivate xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- :0a:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 7350/8350 / R5 220] [1002:68fa] DRM Information from dmesg: -- -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64 Kernel: Linux 4.19.28-rt16rp1 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xserver-xorg-video-radeon depends on: ii libc6 2.29-2 ii libdrm-radeon1 2.4.99-1 ii libgbm119.2.1-1 ii libudev1 242-7 ii xserver-xorg-core [xorg-video-abi-24] 2:1.20.4-1 xserver-xorg-video-radeon recommends no packages. Versions of packages xserver-xorg-video-radeon suggests: ii firmware-amd-graphics 20180825+dfsg-1 -- no debconf information
Bug#917491: debian-installer-9-netboot-amd64: Did this bug crop up again in 20170615+deb9u6 (released Apr 2019)?
Package: debian-installer-9-netboot-amd64 Version: 20170615+deb9u6 Followup-For: Bug #917491 Dear Maintainer, Some weeks ago, my Debian stretch netboot installer told me that I needed to update, so I proceeded to download the new files: http://ftp.debian.org/debian/dists/stretch/main/installer-amd64/current/images/netboot/netboot.tar.gz http://ftp.debian.org/debian/dists/stretch/main/installer-amd64/current/images/SHA256SUMS http://ftp.debian.org/debian/dists/stretch/Release http://ftp.debian.org/debian/dists/stretch/Release.gpg and run the normal sha256 checksums on the various files, per the Debian wiki: $cat SHA256SUMS | grep -F netboot/netboot.tar.gz c2d37c3652f993bc07039f68cc1876ef343a9bb30fca29ca5aa9de0e93a9c4fd ./netboot/netboot.tar.gz $sha256sum netboot.tar.gz c2d37c3652f993bc07039f68cc1876ef343a9bb30fca29ca5aa9de0e93a9c4fd netboot.tar.gz $sha256sum SHA256SUMS 083e4910e7af0f6e0b40809456ff373704bb7c27731f9edd73d9d93628267a6f SHA256SUMS $cat Release | grep -A 10 '^SHA256' | grep -F installer-amd64/current/images/SHA256SUMS 083e4910e7af0f6e0b40809456ff373704bb7c27731f9edd73d9d93628267a6f 74077 main/installer-amd64/current/images/SHA256SUMS $gpg --verify Release.gpg Release gpg: Signature made Sat 27 Apr 2019 04:30:44 AM CDT gpg:using RSA key A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553 gpg: Good signature from "Debian Archive Automatic Signing Key (7.0/wheezy) " [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: A1BD 8E9D 78F7 FE5C 3E65 D8AF 8B48 AD62 4692 5553 gpg: Signature made Sat 27 Apr 2019 04:30:44 AM CDT gpg:using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010 gpg: Good signature from "Debian Archive Automatic Signing Key (8/jessie) " [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 126C 0D24 BD8A 2942 CC7D F8AC 7638 D044 2B90 D010 gpg: Signature made Sat 27 Apr 2019 04:33:33 AM CDT gpg:using RSA key 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500 gpg: Good signature from "Debian Stable Release Key (9/stretch) " [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 067E 3C45 6BAE 240A CEE8 8F6F EF0F 382A 1A7B 6500 I noticed that the Release file had been signed with A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553 which matches the signature for "Debian Archive Automatic Signing Key (7.0/wheezy) " not for "Debian Stable Release Key (9/stretch) " as I would expect for the Stretch release (stretch key for stretch release, yes?). A search brought me to this bug, which sounds a lot like what I've seen. If this is a "should be reported elsewhere", I would be happy to do so. Thanks for all your work on making the installer setups go! -- System Information: Debian Release: 9.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/24 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) debian-installer-9-netboot-amd64 depends on no packages. debian-installer-9-netboot-amd64 recommends no packages. Versions of packages debian-installer-9-netboot-amd64 suggests: pn tftpd-hpa
Bug#930168: plasma-discover hangs while looking for updates, emits many notifications when closed
Package: plasma-discover Version: 5.14.5.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, I've installed Kali Linux (rolling release) and selected the KDE/Plasma desktop. There's an icon on the taskbar that indicates there are upates available. Clicking on the icon pops up a window that says there's 12 updates available, with a 'view updates' button. Clicking on the button brings up plasma-discover, which starts off in 'Checking for updates...' mode, with 'Fetching...' in the title bar, and 'Fetching...' and 'Looking for updates' in the main pane, but it just sits there doing nothing. A few seconds after I close plasma-discover, a stream of 20+ "Searching for file: Finished" desktop notifications pop up. I've learned to not update the system using plasma-discover and instead use 'apt-get dis-upgrade'. :-) Good luck! -- System Information: Distributor ID: Kali Description:Kali GNU/Linux Rolling Release:2019.2 Codename: n/a Architecture: x86_64 Kernel: Linux 4.19.0-kali5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-discover depends on: ii appstream0.12.5-1 ii apt-config-icons 0.12.5-1 ii kio 5.54.1-1 ii libappstreamqt2 0.12.5-1 ii libc62.28-10 ii libkf5attica55.54.0-1 ii libkf5configcore55.54.0-1 ii libkf5configwidgets5 5.54.0-1 ii libkf5coreaddons55.54.0-1 ii libkf5crash5 5.54.0-1 ii libkf5dbusaddons55.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5itemmodels55.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5kiowidgets55.54.1-1 ii libkf5newstuffcore5 5.54.0-2 ii libkf5notifications5 5.54.0-1 ii libkf5service-bin5.54.0-1 ii libkf5service5 5.54.0-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5xmlgui55.54.0-1 ii libpackagekitqt5-1 1.0.1-1 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5dbus5 5.11.3+dfsg1-1 ii libqt5gui5 5.11.3+dfsg1-1 ii libqt5network5 5.11.3+dfsg1-1 ii libqt5qml5 5.11.3-4 ii libqt5quick5 5.11.3-4 ii libqt5widgets5 5.11.3+dfsg1-1 ii libqt5xml5 5.11.3+dfsg1-1 ii libstdc++6 8.3.0-6 ii packagekit 1.1.12-5 ii plasma-discover-common 5.14.5.1-1 ii qml-module-org-kde-kcoreaddons 5.54.0-1 ii qml-module-org-kde-kirigami2 5.54.0-1 ii qml-module-org-kde-kquickcontrols5.54.0-1 ii qml-module-org-kde-kquickcontrolsaddons 5.54.0-1 ii qml-module-org-kde-qqc2desktopstyle 5.54.0-1 ii qml-module-qtquick-dialogs 5.11.3-2 Versions of packages plasma-discover recommends: ii apt-config-icons-large 0.12.5-1 ii software-properties-kde 0.96.20.2-2 Versions of packages plasma-discover suggests: pn apt-config-icons-hidpi pn plasma-discover-backend-flatpak -- no debconf information
Bug#930088: mpg123 plays back gibberish instead of music from mp3 files
Package: mpg123 Version: 1.25.10-2 Severity: grave Justification: renders package unusable Dear Maintainer, I wanted to play some music on my freshly set up laptop, and my usual approach is to type 'mpg123 -Z *.mp3'. However, no matter which mp3 file I played (out of 100+), they all came out sounding like static. Running 'mplayer *.mp3' and 'mpg321 -Z *.mp3' worked correctly, and music played. Typing 'file *.mp3' shows the files are this type: file *.mp3 | cut -d: -f2- | sed 's/^ *//' | sort | uniq -c 1 Audio file with ID3 version 2.4.0, contains:MPEG ADTS, layer III, v1, 160 kbps, 48 kHz, Stereo 11 Audio file with ID3 version 2.4.0, contains:MPEG ADTS, layer III, v1, 64 kbps, 44.1 kHz, Stereo 48 Audio file with ID3 version 2.4.0, contains:MPEG ADTS, layer III, v1, 64 kbps, 48 kHz, Stereo It's not clear what's going wrong. -- System Information: Distributor ID: Kali Description:Kali GNU/Linux Rolling Release:2019.2 Codename: n/a Architecture: x86_64 Kernel: Linux 4.19.0-kali5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mpg123 depends on: ii libasound21.1.8-1 ii libaudio2 1.9.4-6 ii libc6 2.28-10 ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2 ii libmpg123-0 1.25.10-2 ii libopenal11:1.19.1-1 ii libout123-0 1.25.10-2 ii libportaudio2 19.6.0-1 ii libpulse0 12.2-4 mpg123 recommends no packages. Versions of packages mpg123 suggests: ii alsa-utils 1.1.8-2 pn jackd pn nas pn oss-compat pn oss4-base ii pulseaudio 12.2-4 -- no debconf information
Bug#928417: Temporary fix: set xpinstall.signatures.required to false
An immediate fix is to set xpinstall.signatures.required to false in about:config 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#927747: [Pkg-samba-maint] Bug#927747: bind9_dlz backend is entirely broken in Debian
Hai, > > 3.Patching "named.conf" template to load the correct bind9 module (i.e 9.11) > I _think_ samba_dnsupgradedns writes a new config fragment. No you need adjustments in bind as shown below. after the 4 points, im missing the following. Addding point 5. The end result should look like this: ls -al /var/lib/samba/bind-dns/ total 28 drwxrwx--- 3 root bind 4096 Apr 24 08:17 . drwxr-xr-x 10 root root 4096 Apr 8 15:03 .. drwxrwx--- 3 root bind 4096 Feb 27 16:38 dns -rw-r- 2 root bind 877 Apr 28 2015 dns.keytab -rw-r--r-- 1 root root 781 Feb 27 16:38 named.conf -r--r--r-- 1 root root 312 Feb 27 16:41 named.conf.update -rw-r--r-- 1 root root 2092 Feb 27 16:38 named.txt Take note that dns.keytab isnt moved by default but should be moved. This is one i did manualy. After that change you need to adjust : /etc/bind/named.conf.options. // https://wiki.samba.org/index.php/Dns-backend_bind // DNS dynamic updates via Kerberos (optional, but recommended) // old path //tkey-gssapi-keytab "/var/lib/samba/private/dns.keytab"; tkey-gssapi-keytab "/var/lib/samba/bind-dns/dns.keytab"; and in : /etc/bind/named.conf.local. change // adding the dlopen ( Bind DLZ ) module for samba, include "/var/lib/samba/bind-dns/named.conf"; Now bind9 restart then samba restart. to make sure the restart order is correct and it always works. systemctl edit samba-ad-dc.service # /etc/systemd/system/samba-ad-dc.service.d/override.conf [Unit] After=network.target network-online.target bind9.service Maybe its an option to add it as default that samba always starts after bind9 started. Greetz, Louis
Bug#923926: proftpd has memory leaks, allows Denial-Of-Service attack
On Fri, Apr 05, 2019 at 01:46:23PM +0200, Markus Koschany wrote: Hi, Am 29.03.19 um 16:44 schrieb Francesco P. Lovergine: On Thu, Mar 28, 2019 at 01:49:51PM +0100, Markus Koschany wrote: Hello Francesco, I intend to upgrade proftpd in Jessie to fix the memory leaks and another unrelated issue. I think it would be best to backport the version in testing. If you agree, I could also update proftpd in stable. Please let me know if I can proceed. A conservative approach would be using latest 1.3.5 version, instead of 1.3.6. I have backported version 1.3.5e to Stretch. I don't have access to the Git repository but I have uploaded the new package to people.debian.org. https://people.debian.org/~apo/proftpd/ where you can grab the sources. There were at least three different memory leak issues that were fixed. Two of them are related to the mod_sftp module and this bug report, another one was in mod_facl. I intend to contact the release team next week for a stretch-pu. Regards, Markus That should be definitively the easiest solutions. Of course 1.3.5e does not strictly fix only those three leaks, so that update could be non acceptable for a secteam upload. -- Francesco P. Lovergine
Bug#923926: proftpd has memory leaks, allows Denial-Of-Service attack
On Thu, Mar 28, 2019 at 01:49:51PM +0100, Markus Koschany wrote: Hello Francesco, I intend to upgrade proftpd in Jessie to fix the memory leaks and another unrelated issue. I think it would be best to backport the version in testing. If you agree, I could also update proftpd in stable. Please let me know if I can proceed. A conservative approach would be using latest 1.3.5 version, instead of 1.3.6. -- Francesco P. Lovergine
Bug#921324: astropy-healpix FTBFS on i386: test filure
On Mon, 04 Feb 2019 11:16:29 +0200 Adrian Bunk wrote:
> Fix:
>
> --- debian/rules.old 2019-02-04 09:12:02.674701984 +
> +++ debian/rules 2019-02-04 09:13:52.286700939 +
> @@ -9,6 +9,10 @@
> # Astropy-affiliated packages do.
> export PYBUILD_AFTER_INSTALL := find {destdir} -name '*.c' -delete
>
> +ifeq ($(DEB_HOST_ARCH),i386)
> + export DEB_CFLAGS_MAINT_APPEND=-ffloat-store
> +endif
> +
> %:
> dh $@ --with python3 --buildsystem=pybuild
I recall that setting -mpc64 also fixed this, but I gather from the gcc
documentation that -ffloat-store is more correct because it ensures correct
rounding for both single and double precision variables. Do you agree?
Thanks,
Leo
Bug#905735: emacs-goodies-el: postinst failure due to missing lcomp.el
On Wed, 8 Aug 2018 22:50:16 -0400, Nicholas D Steeves wrote: [...] > It is highly probable that this bug occurred due to breaking changes > introduced with emacsen-common 3.0.2, rather than from removal of this > file. But I have emacsen-common 2.0.8 installed as per the report. >> -- System Information: Debian Release: buster/sid APT prefers testing >> APT policy: (990, 'testing'), (300, 'unstable') Architecture: amd64 >> (x86_64) Foreign Architectures: i386 > I see you're mixing testing and unstable. Are you willing to test an > upgrade to unversioned emacs? It would be a valuable data-point to > solving this emacs-goodies-el bug! If so, please use the following > procedure: > # This bit returns goodies to the state it was for Stretch > apt purge --autoremove emacs-goodies-el > wget > https://snapshot.debian.org/archive/debian/20161122T032842Z/pool/main/e/emacs-goodies-el/emacs-goodies-el_36.3_all.deb > # this next line might be paranoia > apt autoremove --purge > # and finally install the package > dpkg -i emacs-goodies-el_36.3_all.deb > # This installs emacs-goodies-el from stretch, and will pull in the > new unversioned emacs. Please note the list of packages, in case you > need to roll back. > apt install emacs-goodies-el=40.1 The last step failed for me: ------ Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: emacs-goodies-el : Depends: emacsen-common (>= 3.0.2) but 2.0.8 is to be installed Recommends: elpa-bm but it is not installable E: Unable to correct problems, you have held broken packages. --- --- But succeeded by letting it choose my default testing version of the package (40.0): --- --- $ sudo aptitude safe-upgrade The following packages will be upgraded: emacs-goodies-el 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/96.4 kB of archives. After unpacking 3,177 kB will be freed. Do you want to continue? [Y/n/?] y Reading changelogs... Done (Reading database ... 682251 files and directories currently installed.) Preparing to unpack .../emacs-goodies-el_40.0_all.deb ... Remove emacs-goodies-el for emacs25 remove/emacs-goodies-el: purging byte-compiled files for emacs25 Unpacking emacs-goodies-el (40.0) over (36.3) ... Processing triggers for install-info (6.5.0.dfsg.1-4) ... Setting up emacs-goodies-el (40.0) ... Install emacsen-common for emacs25 emacsen-common: Handling install of emacsen flavor emacs25 Install emacs-goodies-el for emacs25 install/emacs-goodies-el: Handling emacs25, logged in /tmp/elc_b2o0sx.log Building autoloads for emacs25 in /usr/share/emacs25/site-lisp/emacs-goodies-el install/emacs-goodies-el: Deleting /tmp/elc_b2o0sx.log Current status: 0 (-1) upgradable. --- --- Thank you for your quick follow-up and hopefully this is useful. -- Seb
Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)
Hello,
currently I have virtualbox 5.2.14-dfsg-4 installed and I still can't start
any of my VMs. The error is the same:
Failed to open a session for the virtual machine ubuntu.
Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits failed
(VERR_LDRELF_RELOCATION_NOT_SUPPORTED).
Failed to load VMMR0.r0 (VERR_LDRELF_RELOCATION_NOT_SUPPORTED).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
"apt update" does not give any updates.
Am I the only one with this error in the new version? Please let me know if
you have any questions or how can I help with troubleshooting. So far I
have tried purging virtualbox and installing again with the same result.
Thank you!
Best regards,
athmoss
On Thu, 12 Jul 2018 08:28:03 -0500 Roy wrote:
> Works for me also. Thank you. -Roy
>
>
> On 07/12/2018 07:30 AM, Christian Marillat wrote:
> > On 12 juil. 2018 11:14, Volker Christian <
volker.christ...@fh-hagenberg.at> wrote:
> >
> >> I can confirm that the virtual machines start again with this fix!
> > Works for me too with 32 and 64 bits guests.
> >
> >> Thank you very much!
> > Me too.
> >
> > Christian
> >
>
>
>
Bug#900533: chromium: Still exits in 68.0.3440.7-1
Package: chromium
Version: 68.0.3440.7-1
Followup-For: Bug #900533
--- Chromium debug log browsing youtube ---
Setting up chromium (68.0.3440.7-1) ...
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
s0m3f00l@Cumulus-deb:~$ chromium
[5140:5346:0611/061317.394966:ERROR:object_proxy.cc(616)] Failed to call
method: org.freedesktop.Notifications.GetCapabilities: object_path=
/org/freedesktop/Notifications: org.freedesktop.DBus.Error.ServiceUnknown: The
name org.freedesktop.Notifications was not provided by any .service files
[5140:5140:0611/061317.839680:ERROR:background_mode_manager_aura.cc(14)] Not
implemented reached in virtual void
BackgroundModeManager::EnableLaunchOnStartup(bool)
[5140:5170:0611/061318.462403:ERROR:connection.cc(1890)] Passwords sqlite error
2067, errno 0: UNIQUE constraint failed: logins.origin_url,
logins.username_element, logins.username_value, logins.password_element,
logins.signon_realm, sql: INSERT INTO logins (origin_url, action_url,
username_element, username_value, password_element, password_value,
submit_element, signon_realm, preferred, date_created, blacklisted_by_user,
scheme, password_type, times_used, form_data, date_synced, display_name,
icon_url, federation_url, skip_zero_click, generation_upload_status,
possible_username_pairs) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
[5140:5140:0611/061319.441272:ERROR:display_info_provider.cc(175)] Not
implemented reached in virtual void
extensions::DisplayInfoProvider::UpdateDisplayUnitInfoForPlatform(const
display::Display&, extensions::api::system_display::DisplayUnitInfo*)
[98:136:0611/061326.971352:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[98:136:0611/061326.971603:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[98:98:0611/061326.972184:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[98:98:0611/061326.973008:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[98:136:0611/061326.979177:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[98:98:0611/061326.979617:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[121:151:0611/061335.811354:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[121:121:0611/061335.867090:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
[121:151:0611/061336.600994:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[121:121:0611/061336.603162:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chromium depends on:
ii chromium-common 68.0.3440.7-1
ii libasound2 1.1.6-1
ii libatk-bridge2.0-0 2.26.2-1
ii libatk1.0-0 2.28.1-1
ii libavcodec57 7:3.4.2-2+b1
ii libavformat577:3.4.2-2+b1
ii libavutil55 7:3.4.2-2+b1
ii libc62.27-3
ii libcairo21.15.10-3
ii libcups2 2.2.8-2
ii libdbus-1-3 1.12.8-3
ii libevent-2.1-6 2.1.8-stable-4
ii libexpat12.2.5-3
ii libflac8 1.3.2-3
ii libfontconfig1 2.13.0-5
ii libfreetype6 2.8.1-2
ii libgcc1 1:8.1.0-5
ii libgdk-pixbuf2.0-0 2.36.11-2
ii libglib2.0-0 2.56.1-2
ii libgtk-3-0 3.22.30-1
ii libharfbuzz0b1.7.6-1+b1
ii libicu60 60.2-6
ii libjpeg62-turbo 1:1.5.2-2+b1
ii liblcms2-2 2.9-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.19-3
ii libnss3 2:3.37.1-1
ii libopenjp2-7 2.3.0-1
ii libopus0 1.3~beta+20180518-1
ii libpango-1.0-0 1.42.1-1
ii libpangocairo-1.0-0 1.42.1-1
ii libpng16-16 1.6.34-1
ii libpulse011.1-5
ii libre2-4 20180301+dfsg-1
ii libsnappy1v5 1.1.7-1
ii libstdc++6 8.1.0-5
ii libvpx5 1.7.0-3
ii libwebp6 0.6.1-2
ii libwebpdemux20.6.1-2
ii libwebpmux3 0.6.1-2
ii libx11-6 2:1.6.5-1
ii libx11-xcb1 2:1.6.5-1
ii libxcb1 1.13-1
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.1.15-1
ii libxdamage1
Bug#900533: chromium: This Bug still exits in Source-Version: 67.0.3396.79-2 I get the same errors
Package: chromium
Version: 67.0.3396.79-1
Followup-For: Bug #900533
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgraded from upgrading from 66.0.3359.181-1 to 67.0.3396.79-1
Can't use video on youtube. Gif's no longer work. And I cannot get media to
play.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Reverted to 66.0.3359.181-1
* What was the outcome of this action?
Media works again
* What outcome did you expect instead?
Media should work in 66.0.3359.181-1
--Chromium Bug Log browsing youtube--
Debian@PC-deb:~$ chromium
[3314:3521:0611/060922.753881:ERROR:object_proxy.cc(617)] Failed to call
method: org.freedesktop.Notifications.GetCapabilities: object_path=
/org/freedesktop/Notifications: org.freedesktop.DBus.Error.ServiceUnknown: The
name org.freedesktop.Notifications was not provided by any .service files
[3314:3314:0611/060923.089406:ERROR:background_mode_manager_aura.cc(13)] Not
implemented reached in virtual void
BackgroundModeManager::EnableLaunchOnStartup(bool)
[3314:3343:0611/060923.676483:ERROR:connection.cc(1888)] Passwords sqlite error
2067, errno 0: UNIQUE constraint failed: logins.origin_url,
logins.username_element, logins.username_value, logins.password_element,
logins.signon_realm, sql: INSERT INTO logins (origin_url, action_url,
username_element, username_value, password_element, password_value,
submit_element, signon_realm, preferred, date_created, blacklisted_by_user,
scheme, password_type, times_used, form_data, date_synced, display_name,
icon_url, federation_url, skip_zero_click, generation_upload_status,
possible_username_pairs) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
[3314:3314:0611/060924.411617:ERROR:display_info_provider.cc(189)] Not
implemented reached in virtual void
extensions::DisplayInfoProvider::UpdateDisplayUnitInfoForPlatform(const
display::Display&, extensions::api::system_display::DisplayUnitInfo*)
[98:144:0611/060931.047056:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[98:98:0611/060931.047624:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[98:144:0611/060931.053916:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[98:98:0611/060931.054403:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[98:144:0611/060931.054651:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[98:98:0611/060931.055432:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[127:160:0611/060936.821264:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[127:127:0611/060936.876064:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
[127:160:0611/060937.479760:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[127:127:0611/060937.481080:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chromium depends on:
ii chromium-common 67.0.3396.79-1
ii libasound2 1.1.6-1
ii libatk-bridge2.0-0 2.26.2-1
ii libatk1.0-0 2.28.1-1
ii libavcodec57 7:3.4.2-2+b1
ii libavformat577:3.4.2-2+b1
ii libavutil55 7:3.4.2-2+b1
ii libc62.27-3
ii libcairo21.15.10-3
ii libcups2 2.2.8-2
ii libdbus-1-3 1.12.8-3
ii libevent-2.1-6 2.1.8-stable-4
ii libexpat12.2.5-3
ii libflac8 1.3.2-3
ii libfontconfig1 2.13.0-5
ii libfreetype6 2.8.1-2
ii libgcc1 1:8.1.0-5
ii libgdk-pixbuf2.0-0 2.36.11-2
ii libglib2.0-0 2.56.1-2
ii libgtk-3-0 3.22.30-1
ii libharfbuzz0b1.7.6-1+b1
ii libicu60 60.2-6
ii libjpeg62-turbo 1:1.5.2-2+b1
ii liblcms2-2 2.9-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.19-3
ii libnss3 2:3.37.1-1
ii libopenjp2-7 2.3.0-1
ii libopus0 1.3~beta+20180518-1
ii libpango-1.0-0 1.42.1-1
ii libpangocairo-1.0-0 1.42.1-1
ii libpng16-16 1.6.34-1
ii libpulse011.1-5
ii libre2-4 201
Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work
Package: chromium
Version: 67.0.3396.62-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Can't use video on youtube. Gif's no longer work. And I cannot get media to
play. This started after upgrading from 66.0.3359.181-1 to 67.0.3396.62-1
* What exactly did you do (or not do) that was effective (or
ineffective)?
Reverting the package was the only solution I could find. It appears the app
build may be missing some flags in the build. I found this that had similar
errors to my situation
https://groups.google.com/a/chromium.org/forum/?nomobile=true#!msg/android-webview-dev/oVjyFhhxOQ8/ns8q9uPrCAAJ
* What was the outcome of this action?
chromium 66.0.3359.181-1 was reinstalled, video is working again.
* What outcome did you expect instead?
chromium 67.0.3396.62-1 video should work after install.
Chromium Log while trying to play files
[129:160:0531/181749.318090:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[129:129:0531/181749.320645:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[129:160:0531/181749.352209:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[129:129:0531/181749.354280:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
[129:160:0531/181749.551754:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[129:129:0531/181749.559473:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
[129:160:0531/181750.431299:ERROR:render_media_log.cc(30)] MediaEvent:
MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
[129:129:0531/181750.433293:ERROR:render_media_log.cc(30)] MediaEvent:
PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
libpng warning: iCCP: known incorrect sRGB profile
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chromium depends on:
ii chromium-common 67.0.3396.62-1
ii libasound2 1.1.6-1
ii libatk-bridge2.0-0 2.26.2-1
ii libatk1.0-0 2.28.1-1
ii libavcodec57 7:3.4.2-2+b1
ii libavformat577:3.4.2-2+b1
ii libavutil55 7:3.4.2-2+b1
ii libc62.27-3
ii libcairo21.15.10-3
ii libcups2 2.2.7-5
ii libdbus-1-3 1.12.8-2
ii libevent-2.1-6 2.1.8-stable-4
ii libexpat12.2.5-3
ii libflac8 1.3.2-3
ii libfontconfig1 2.13.0-5
ii libfreetype6 2.8.1-2
ii libgcc1 1:8.1.0-4
ii libgdk-pixbuf2.0-0 2.36.11-2
ii libglib2.0-0 2.56.1-2
ii libgtk-3-0 3.22.30-1
ii libharfbuzz0b1.7.6-1+b1
ii libicu60 60.2-6
ii libjpeg62-turbo 1:1.5.2-2+b1
ii liblcms2-2 2.9-1
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.19-3
ii libnss3 2:3.37.1-1
ii libopenjp2-7 2.3.0-1
ii libopus0 1.3~beta+20180518-1
ii libpango-1.0-0 1.42.1-1
ii libpangocairo-1.0-0 1.42.1-1
ii libpng16-16 1.6.34-1
ii libpulse011.1-5
ii libre2-4 20180301+dfsg-1
ii libsnappy1v5 1.1.7-1
ii libstdc++6 8.1.0-4
ii libvpx5 1.7.0-3
ii libwebp6 0.6.1-2
ii libwebpdemux20.6.1-2
ii libwebpmux3 0.6.1-2
ii libx11-6 2:1.6.5-1
ii libx11-xcb1 2:1.6.5-1
ii libxcb1 1.13-1
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.1.15-1
ii libxdamage1 1:1.1.4-3
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-1
ii libxi6 2:1.7.9-1
ii libxml2 2.9.4+dfsg1-7
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.32-2
ii libxss1 1:1.2.2-1+b2
ii libxtst6 2:1.2.3-1
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages chromium recommends:
ii fonts-liberation 1:1.07.4-7
ii libgl1-mesa-dri 18.0.4-1
Versions of packages chromium suggests:
pn chromium-driver
pn chromium-l10n
pn chromium-shell
-- no debconf information
Bug#894667: beep bug
How similar is beep to beep2? I use beep2 on Smoothwall Express. It is not installed suid root. Rather, I changed beep2's default output device to /dev/tty13 (would be just as easy to use tty63) and changed the perms on that TTY to 622. Without suid root, beep2 can only open files for input or output for which its user has access; with similar treatment, beep should be almost properly limited. Neal
Bug#892468: proftp: Prevent migration to testing
On Fri, Mar 09, 2018 at 12:13:55PM +0100, Hilmar Preuße wrote: Package: proftpd-basic Version: 1.3.6-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, for now we want to prevent the package from migrating to testing until we are sure all bugs are fixed. For now already three bugs were reported telling that some modules do not build any more: - Bug#892371: proftpd-mod-vroot FTBFS with proftpd 1.3.6-1 - Bug#892372: proftpd-mod-msg FTBFS with proftpd 1.3.6-1 - Bug#892373: proftpd-mod-fsync FTBFS with proftpd 1.3.6-1 Hilmar, I just followed up error reports with hints for fixing. Do you mind to work on them? -- Francesco P. Lovergine
Bug#892372: [INFO] Bug#892372: proftpd-mod-msg FTBFS with proftpd 1.3.6-1
On Thu, Mar 08, 2018 at 05:27:10PM +0200, Adrian Bunk wrote: Source: proftpd-mod-msg Version: 0.4.1-1.1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proftpd-mod-msg.html ... mod_msg.c:56:3: error: #error "mod_msg requires Controls support (--enable-ctrls)" # error "mod_msg requires Controls support (--enable-ctrls)" ^ This is another trivial fix, just s/USE_CTRLS/PR_USE_CTRLS/ in source. -- Francesco P. Lovergine
Bug#892371: [INFO] Bug#892371: proftpd-mod-vroot FTBFS with proftpd 1.3.6-1
On Thu, Mar 08, 2018 at 05:25:20PM +0200, Adrian Bunk wrote:
Source: proftpd-mod-vroot
Version: 0.9.4-1
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proftpd-mod-vroot.html
...
mod_vroot.c:1518:19: error: void value not ignored as it ought to be
if (cmd->argv[1][pathlen - 1] != '/') {
^
...
mod_vroot.c: In function 'vroot_pre_pass':
mod_vroot.c:1651:7: error: 'pr_fs_t {aka struct fs_rec}' has no member named
'creat'; did you mean 'read'?
fs->creat = vroot_creat;
^
This is fixed in 0.9.7, better upgrading.
--
Francesco P. Lovergine
Bug#892373: [INFO] Bug#892373: proftpd-mod-fsync FTBFS with proftpd 1.3.6-1
On Thu, Mar 08, 2018 at 05:28:49PM +0200, Adrian Bunk wrote: Source: proftpd-mod-fsync Version: 0.2-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proftpd-mod-fsync.html ... mod_fsync.c:184:10: error: implicit declaration of function 'HANDLED'; did you mean 'PR_HANDLED'? [-Werror=implicit-function-declaration] return HANDLED(cmd); ^~~ ... mod_fsync.c: In function 'fsync_postparse_ev': mod_fsync.c:269:12: error: 'LOG_SYMLINK' undeclared (first use in this function); did you mean 'PR_LOG_SYMLINK'? case LOG_SYMLINK: ^~~ PR_LOG_SYMLINK mod_fsync.c:269:12: note: each undeclared identifier is reported only once for each function it appears in mod_fsync.c:274:12: error: 'LOG_WRITEABLE_DIR' undeclared (first use in this function); did you mean 'PR_LOG_WRITABLE_DIR'? case LOG_WRITEABLE_DIR: ^ Here the fix is trivial as suggested. Even in this case it is better upgrading to current upstream version. -- Francesco P. Lovergine
Bug#890922: sane: Agfa SnapScan 1212U does not work after upgrade to stretch.
Package: sane Version: 1.0.14-12 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After an upgrade to Debian Stretch, the scanner would not work. * What exactly did you do (or not do) that was effective (or ineffective)? I connected the scanner's USB cable to my laptop which is still running Debian Jessie. The scanner worked. I made sure that the configuration files in /etc/sane.d were correct, and that the firmware file was properly installed in /usr/share/sane/snapscan. I found bug # 856811 which seemed virtually identical to my bug. I ran ln -s /usr/lib64/sane /usr/lib as suggested in the bug conversation, and tested again. No joy. * What was the outcome of this action? root@hen3ry:/home/mike# lsusb : : Bus 002 Device 004: ID 06bd:2061 AGFA-Gevaert NV SnapScan 1212U (?) : root@hen3ry:/home/mike# scanimage -L device `snapscan:libusb:002:004' is a AGFA SNAPSCAN flatbed scanner root@hen3ry:/home/mike# scanimage --format=tiff >/root/image.tiff scanimage: no SANE devices found * What outcome did you expect instead? When "lsusb" and "scanimage -L" both worked, I expected a scan to work. It failed with both "scanimage --format=tiff >/root/image.tiff" and gscan2pdf. -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sane depends on: ii libc6 2.24-11+deb9u1 ii libgimp2.02.8.18-1+deb9u1 ii libglib2.0-0 2.50.3-2 ii libgtk2.0-0 2.24.31-2 ii libsane 1.0.25-4.1 sane recommends no packages. Versions of packages sane suggests: ii gimp 2.8.18-1+deb9u1 -- no debconf information
Bug#886742: [INFO] Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch
On Tue, Jan 09, 2018 at 02:37:44PM +0100, Jürgen Fuchsberger wrote: > >> What did you try, and what didn't work? > > > > Probably pg_upgradecluster, and that is not supported for databases with > > the postgis extension. > > > Exactly. Just wanted to point out that upgrading was no possibility > either, the actual problem was that the database could not be accessed > or dumped after the upgrade. While ideally one could use hook scripts to manage such kind of extensions I would not try that approach in any case. A Postgis hard upgrade is generally a trial-and-error nightmare^Wexperience and it depends on languages, extensions, encodings. Last time, I had to perform a series of ad hoc setups before trying the restore. I strongly suggest to run both servers and extensions on the host in order to run a successfully shop upgrade later. That is definitively possible, I have at least one server still running both 8.4 and 9.4 with required Postgis extensions. -- Francesco P. Lovergine
Bug#869364: libtext-iconv-perl: unable to install libtext-iconv-perl (1.7-5) on Debian sid
Package: libtext-iconv-perl Version: 1.7-5 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Trying to install the package * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? # apt-get install libtext-iconv-perl Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libtext-iconv-perl : Depends: perlapi-5.24.1 E: Unable to correct problems, you have held broken packages. # dpkg -l perl-base Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii perl-base 5.26.0-4 amd64minimal Perl system # * What outcome did you expect instead? I would expect the package to be installed. It seems the package still depends on perl-base 5.24.1 when perl-5.26.0 is installed by all updates. -- System Information: Debian Release: buster/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.7-std-3 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libtext-iconv-perl depends on: ii libc6 2.24-12 ii perl-base 5.26.0-4 pn perlapi-5.24.1 libtext-iconv-perl recommends no packages. libtext-iconv-perl suggests no packages.
Bug#865776: Fixed upstream
Frédéric Bonnard's change applied. See https://github.com/lpereira/hardinfo/commit/285a6cbcd5e1ca7e9857b0e16adba61a3197fed1 -- Burt
Bug#864924: virtualbox GUI not more working
Package: virtualbox Version: 5.1.22-dfsg-1 Severity: grave Dear Maintainer, the program fails to start with the following message: $ LANG=C virtualbox Qt FATAL: This application failed to start because it could not find or load the Qt platform plugin "xcb" in "". Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, xcb. Reinstalling the application may fix this problem. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages virtualbox depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii libc6 2.24-11 ii libcurl3-gnutls 7.52.1-5 ii libdevmapper1.02.12:1.02.137-2 ii libgcc1 1:6.3.0-18 ii libgsoap102.8.35-4 ii libpng16-16 1.6.28-1 ii libpython3.5 3.5.3-3 ii libsdl1.2debian 1.2.15+dfsg1-4 ii libssl1.1 1.1.0f-3 ii libstdc++66.3.0-18 ii libvncserver1 0.9.11+dfsg-1 ii libvpx4 1.6.1-3 ii libx11-6 2:1.6.4-3 ii libxcursor1 1:1.1.14-1+b4 ii libxext6 2:1.3.3-1+b2 ii libxml2 2.9.4+dfsg1-2.2 ii libxmu6 2:1.1.2-2 ii libxt61:1.1.5-1 ii procps2:3.3.12-3 ii python3 3.5.3-1 ii python3.5 3.5.3-3 ii virtualbox-dkms [virtualbox-modules] 5.1.22-dfsg-1 ii zlib1g1:1.2.8.dfsg-5 Versions of packages virtualbox recommends: ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5opengl5 5.7.1+dfsg-3+b1 ii libqt5widgets55.7.1+dfsg-3+b1 ii virtualbox-qt 5.1.22-dfsg-1 Versions of packages virtualbox suggests: pn vde2 ii virtualbox-guest-additions-iso 5.1.22-1 -- no debconf information
Bug#863888: openjdk-8-jdk: cannot install package
Package: openjdk-8-jdk Version: 8u131-b11-1~bpo8+1 Severity: grave Justification: renders package unusable I was looking for a jdk to install, so I picked the latest jdk. msoulier@cappuccino:~$ sudo apt-get install openjdk-8-jdk Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: openjdk-8-jdk : Depends: openjdk-8-jre (= 8u131-b11-1~bpo8+1) but it is not going to be installed Depends: openjdk-8-jdk-headless (= 8u131-b11-1~bpo8+1) but it is not going to be installed so I can't install it, and it is not clear how I might install it beyond not using the debian packages. msoulier@cappuccino:~$ sudo cat /etc/apt/sources.list deb http://ftp.ca.debian.org/debian/ jessie main contrib non-free deb-src http://ftp.ca.debian.org/debian/ jessie main contrib non-free deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free # jessie-updates, previously known as 'volatile' deb http://ftp.ca.debian.org/debian/ jessie-updates main contrib non-free deb-src http://ftp.ca.debian.org/debian/ jessie-updates main contrib non-free # jessie backports deb http://ftp.debian.org/debian jessie-backports main -- System Information: Debian Release: 8.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#863040: rawtherapee: Crash at lauch time with message: Error in rawtherapee: munmap_chunk(): invalid pointer
Hello Philip, Thank you very much for your reply and advise. I did what you suggested. After removing the original paquet, I installed the new one (Your commands were ok Unfortunately the crash is still present in same conditions and errors. Rgds, Philippe Le 20/05/2017 à 18:28, Philip Rinn a écrit : > Control: tags -1 jessie > Control: fixed -1 5.0-1 > > > Hi, > > this only affects jessie. Seem to be a problem with libpng12, probably just a > binNMU is needed. I'll check during the next days. > You could try by rebuilding rawtherapee from source[1] with roughly those > commands > [didn't test them]: > > apt-get source rawtherapee > sudo apt-get build-dep rawtherapee > cd rawtherapee-4.2 > debuild -b -uc -us > cd .. > sudo dpkg -i rawtherapee*.deb > > > Best, > Philip > > [1] https://wiki.debian.org/BuildingTutorial > > >
Bug#858895: stk: fails to find soundfile
Package: stk Version: 4.5.2+dfsg-4 Severity: serious Justification: grave Dear Maintainer, Launching stk-demo TubeBell -or throws an error FileRead::open: could not open or find file (../../rawwaves/sinewave.raw)! while the file searched for is in place in /usr/share/stk/rawwaves/sinewave.raw Most likely the source of the error is http://sources.debian.net/src/stk/unstable/projects/demo/demo.cpp/#L216 -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (900, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages stk depends on: ii libasound21.1.3-5 ii libc6 2.24-9 ii libgcc1 1:6.3.0-10 ii libjack0 [libjack-0.125] 1:0.125.0-2 ii librtaudio5a 4.1.2~ds0-4 ii librtmidi32.1.1~ds0-4 ii libstdc++66.3.0-10 ii libstk-4.5.0 4.5.2+dfsg-4 ii tk8.6.0+9 stk recommends no packages. stk suggests no packages. -- no debconf information
Bug#858564: [Pkg-samba-maint] Bug#858564: samba: Since 8u4, Samba does not allow files not in root directory of share
What happens if you add: read only = No ( or writeable = yes ) to your share, and not in the global settings. Greetz, Louis > -Oorspronkelijk bericht- > Van: Pkg-samba-maint [mailto:pkg-samba-maint- > bounces+belle=bazuin...@lists.alioth.debian.org] Namens James Bellinger > Verzonden: donderdag 23 maart 2017 17:41 > Aan: Debian Bug Tracking System > Onderwerp: [Pkg-samba-maint] Bug#858564: samba: Since 8u4, Samba does not > allow files not in root directory of share > > Package: samba > Version: 2:4.2.14+dfsg-0+deb8u2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate > *** > >* What led up to the situation? > I upgraded to 8u4 through unattended upgrades. >* What exactly did you do (or not do) that was effective (or > ineffective)? > (1) I attempt to create a file not in the root directory of the > share. > (2) I try to write to files not in the root directory of the share. >* What was the outcome of this action? > (1) Windows Explorer freezes entirely until I end task it. > (2) It says permission denied. >* What outcome did you expect instead? > (1) Normally I can create files. > (2) Normally I can access files. > > I have reverted back to 8u2 and am no longer experiencing problems. > Access to the root directory of the share works fine. > > My smb.conf is as follows: > (start) > [global] > server string = Server > workgroup = WORKGROUP > log level = 1 > > interfaces = eth0 eth0:0 eth0:1 eth0:2 eth0:3 > bind interfaces only = yes > socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=65536 SO_RCVBUF=65536 > > server role = standalone server > disable netbios = yes > disable spoolss = yes > csc policy = disable > oplocks = no > server min protocol = NT1 > > passdb backend = tdbsam > encrypt passwords = yes > invalid users = root fsadmin > disable netbios = yes > disable spoolss = yes > csc policy = disable > oplocks = no > server min protocol = NT1 > > passdb backend = tdbsam > encrypt passwords = yes > invalid users = root fsadmin > > follow symlinks = no > hide dot files = no > wide links = no > > create mask = 660 > directory mask = 770 > > vfs objects = acl_xattr streams_xattr full_audit > full_audit:prefix = %S|%u|%I > follow symlinks = no > hide dot files = no > wide links = no > > create mask = 660 > directory mask = 770 > > vfs objects = acl_xattr streams_xattr full_audit > full_audit:prefix = %S|%u|%I > full_audit:success = mkdir open opendir rename rmdir unlink > full_audit:failure = all !getxattr !removexattr !is_offline !readdir_att$ > full_audit:facility = LOCAL7 > full_audit:priority = ALERT > > map acl inherit = yes > store dos attributes = yes > > browseable = no > writeable = yes > > include = /etc/samba/smb.conf.%i > (end) > > As an example of the IP-address specific file, here's one: > (start) > [hr$] > comment = HR Server > path = /mnt/data/hr > force group = +AccessHR > valid users = @AccessHR > (end) > > Permissions are absolutely fine. They are essentially 770. > AppArmor is enabled, but I disabled it and the problem still exists in > 8u4. > It does not exist in 8u2. > > *** End of the template - remove these template lines *** > > > -- System Information: > Debian Release: 8.7 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages samba depends on: > ii adduser 3.113+nmu3 > ii dpkg 1.17.27 > ii libbsd0 0.7.0-2 > ii libc62.19-18+deb8u7 > ii libhdb9-heimdal [heimdal-hdb-api-8] 1.6~rc2+dfsg-9 > ii libldb1 2:1.1.20-0+deb8u1 > ii libpam-modules 1.1.8-3.1+deb8u2 > ii libpam-runtime 1.1.8-3.1+deb8u2 > ii libpopt0 1.16-10 > ii libpython2.7 2.7.9-2+deb8u1 > ii libtalloc2 2.1.2-0+deb8u1 > ii libtdb1 1.3.6-0+deb8u1 > ii libtevent0 0.9.28-0+deb8u1 > ii lsb-base 4.1+Debian13+nmu1 > ii multiarch-support2.19-18+deb8u7 > ii procps 2:3.3.9-9 > ii python 2.7.9-1 > ii python-dnspython 1.12.0-1 > ii python-ntdb 1.0-5 > ii python-samba 2:4.2.14+dfsg-0+deb8u2 > pn python2.7:any > ii samba-common 2:4.2.14+dfsg-0+deb8u2 > ii samba-common-bin
Bug#843898: Something to try
On Sun, 20 Nov 2016 19:57:53 -0600, Sebastian P. Luque wrote: > On Sun, 20 Nov 2016 21:01:08 +, > Tobias Hansen wrote: > [...] >>> $ ls -alh ~/.local/lib/python2.7/site-packages/backports/ total 12K >>> drwxr-xr-x 3 sluque sluque 4.0K Oct 30 16:16 . drwx-- 20 sluque >>> sluque 4.0K Oct 30 16:18 .. drwxr-xr-x 2 sluque sluque 4.0K Oct 30 >>> 16:16 configparser >> What happens if you rename that for a moment? Does it fix the >> problem? > No; same result. I just tried a different approach, and it's revealing: $ python -s Python 2.7.12+ (default, Sep 1 2016, 20:27:38) [GCC 6.2.0 20160927] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from backports.shutil_get_terminal_size import get_terminal_size Why on Earth did moving ~/.local/lib/python2.7/site-packages/backports not have the same effect is beyond me. -- Seb
Bug#843898: Something to try
On Sun, 20 Nov 2016 21:01:08 +, Tobias Hansen wrote: [...] >> $ ls -alh ~/.local/lib/python2.7/site-packages/backports/ total 12K >> drwxr-xr-x 3 sluque sluque 4.0K Oct 30 16:16 . drwx-- 20 sluque >> sluque 4.0K Oct 30 16:18 .. drwxr-xr-x 2 sluque sluque 4.0K Oct 30 >> 16:16 configparser > What happens if you rename that for a moment? Does it fix the problem? No; same result. -- Seb
Bug#843898: Something to try
On Sun, 20 Nov 2016 19:17:49 +, Tobias Hansen wrote: > If you google this you see that tons of people have similar issues: > https://github.com/ipython/ipython/issues/9656 > https://github.com/ipython/ipython/issues/9815 > https://github.com/chrippa/backports.shutil_get_terminal_size/issues/9 > The most common "solution" there is reinstalling something with > pip. My suspicion is that the people who see this on Debian also used > pip and there is something interfering. Did you guys use pip (or > something else to install Python modules not from Debian) and have a > backports module or backports.shutil_get_terminal_size itself > installed there? I do use pip within virtual environments, but these shouldn't interfere. First, as per Julien's request, here's my output: $ python Python 2.7.12+ (default, Sep 1 2016, 20:27:38) [GCC 6.2.0 20160927] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from backports.shutil_get_terminal_size import get_terminal_size Traceback (most recent call last): File "", line 1, in ImportError: No module named shutil_get_terminal_size When using pip within virtual environments, packages/modules get installed in ~/.local/lib/python2.7 in my case. There I see one potentially interfering backports module, which shows these contents: $ ls -alh ~/.local/lib/python2.7/site-packages/backports/ total 12K drwxr-xr-x 3 sluque sluque 4.0K Oct 30 16:16 . drwx-- 20 sluque sluque 4.0K Oct 30 16:18 .. drwxr-xr-x 2 sluque sluque 4.0K Oct 30 16:16 configparser -- Seb
Bug#843898: Isn't python-backport-shutil-get-terminal-size installed?!
I'm having the same issue, even though python-backports-shutil-get-terminal-size (1.0.0-3) is installed. Cannot use ipython 2 at all. -- Seb
Bug#836933:
This has been fixed in a more recent version. https://github.com/mstorsjo/fdk-aac/commit/ef30836651bf059c3120c03dd11e08b6aafdae13 -- Burt
Bug#825437: talloc fails building on very clean system. +1
Hai, Found one extra. ( already reported ) talloc : /bin/sh: 1: pyversions: not found sudo apt-get install python-minimal --no-install-recommends new, but same. .. the following message. dpkg-checkbuilddeps: Unmet build dependencies: docbook-xml docbook-xsl xsltproc dh-exec libpopt-dev python-dev (>= 2.6.6-3) python3-dev W: Unmet build-dependency in source dpkg-buildpackage: source package talloc dpkg-buildpackage: source version 2.1.6-1~bpo8+1 dpkg-buildpackage: source distribution jessie-backports dpkg-buildpackage: source changed by Louis van Belle dpkg-source --before-build talloc-2.1.6 dpkg-checkbuilddeps: Unmet build dependencies: docbook-xml docbook-xsl xsltproc dh-exec libpopt-dev python-dev (>= 2.6.6-3) python3-dev dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.) dpkg-buildpackage: warning: this is currently a non-fatal warning with -S, but will probably become fatal in the future fakeroot debian/rules clean dh clean --parallel --with python2 dh: unable to load addon python2: Can't locate Debian/Debhelper/Sequence/python2.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python2 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at (eval 11) line 2. BEGIN failed--compilation aborted at (eval 11) line 2. debian/rules:24: recipe for target 'clean' failed make: *** [clean] Error 2 dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 Build error : libtalloc-dev Package python supplies : Debian/Debhelper/Sequence/python2.pm sudo apt-get install python --no-install-recommends So the source is missing also build depends python or python3 in totaal , pre build needed sources sudo apt-get install python-minimal --no-install-recommends sudo apt-get install python --no-install-recommends and/or sudo apt-get install python3-minimal --no-install-recommends sudo apt-get install python3 --no-install-recommends Now i installed python-minimal and python and building in the pbuilder env works fine now.
Bug#823274: login error
Package: sso.debian.org Severity: grave Hi, I can't login to sso.debian.org using my Alioth account "hemaprathaban-guest". Error message: Authentication failed Invalid authenticating information Thanks Hema
Bug#823236: login error
Package: sso.debian.org Severity: grave Justification: renders package unusable Hi, I can't login to sso.debian.org using my Alioth account "hemaprathaban-guest". Error message: Authentication failed Invalid authenticating information
Bug#823235: login error
Package: sso.debian.org Severity: grave Justification: renders package unusable Hi, I can't login to sso.debian.org using my Alioth account "onovy-guest". Error message: Authentication failed Invalid authenticating information
Bug#794763: mplayer2: MPlayer interrupted by signal 11 in module: demux_open
Package: mplayer2 Version: 2.0-728-g2c378c7-4+b1 Severity: grave Justification: renders package unusable Dear Maintainer, Mplayer2 seems to be broken. For all videos in different formats I tried to watch I get: $ mplayer video.avi MPlayer2 2.0-728-g2c378c7-4+b1 (C) 2000-2012 MPlayer Team Cannot open file '/home/aleksandr/.mplayer/input.conf': No such file or directory Failed to open /home/aleksandr/.mplayer/input.conf. Cannot open file '/etc/mplayer/input.conf': No such file or directory Failed to open /etc/mplayer/input.conf. Playing video.avi. MPlayer interrupted by signal 11 in module: demux_open - MPlayer crashed by bad usage of CPU/FPU/RAM. Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash. - MPlayer crashed. This shouldn't happen. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your gcc version. If you think it's MPlayer's fault, please read DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and won't help unless you provide this information when reporting a possible bug. Backtrace: (gdb) run video.avi Starting program: /usr/bin/mplayer video.avi [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". MPlayer2 2.0-728-g2c378c7-4+b1 (C) 2000-2012 MPlayer Team Cannot open file '/home/aleksandr/.mplayer/input.conf': No such file or directory Failed to open /home/aleksandr/.mplayer/input.conf. Cannot open file '/etc/mplayer/input.conf': No such file or directory Failed to open /etc/mplayer/input.conf. Playing video.avi. Program received signal SIGSEGV, Segmentation fault. strlen () at ../sysdeps/x86_64/strlen.S:106 106 ../sysdeps/x86_64/strlen.S: No such file or directory. Maybe information from valgrind will be useful (see attachment) The same bug can be found at https://trac.mplayerhq.hu/ticket/2237 Some similar bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760669 https://trac.videolan.org/vlc/ticket/11851 Best regards, Alexandr -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mplayer2 depends on: ii liba52-0.7.4 0.7.4-17 ii libasound21.0.28-1 ii libass5 0.10.2-3 ii libavcodec56 6:11.4-1~deb8u1 ii libavformat56 6:11.4-1~deb8u1 ii libavresample26:11.4-1~deb8u1 ii libavutil54 6:11.4-1~deb8u1 ii libbluray11:0.6.2-1 ii libbs2b0 3.1.0+dfsg-2.1 ii libc6 2.19-18 ii libcaca0 0.99.beta19-2 ii libcdio-cdda1 0.83-4.2 ii libcdio-paranoia1 0.83-4.2 ii libcdio13 0.83-4.2 ii libdca0 0.0.5-7 ii libdirectfb-1.2-9 1.2.10.0-5.1 ii libdv41.0.0-6 ii libdvdread4 5.0.0-1 ii libenca0 1.16-1 ii libfaad2 2.7-8 ii libgif4 4.1.6-11 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20140719git3eb0ae6a~dfsg-2 ii libjpeg62-turbo 1:1.3.1-12 ii liblcms2-22.6-3+b3 ii liblircclient00.9.0~pre1-1.2 ii libmad0 0.15.1b-8 ii libmpg123-0 1.20.1-2 ii libogg0 1.3.2-1 ii libpng12-01.2.50-2+b2 ii libpostproc52 6:0.git20120821-4 ii libpulse0 5.0-13 ii libquvi7 0.4.1-3 ii libsdl1.2debian 1.2.15-10+b1 ii libsmbclient 2:4.1.17+dfsg-2 ii libspeex1 1.2~rc1.2-1 ii libswscale3 6:11.4-1~deb8u1 ii libtheora01.1.1+dfsg.1-6 ii libtinfo5 5.9+20140913-1+b1 ii libvdpau1 0.8-3 ii libvorbis0a 1.3.4-2 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxinerama1 2:1.1.3-1+b1 ii libxss1 1:1.2.2-1 ii libxv12:1.0.10-1+b1 ii libxvidcore4 2:1.3.3-1 ii libxxf86vm1 1:1.1.3-1+b1 ii zlib1g1:1.2.8.dfsg-2+b1 mplayer2 recommends no packages. mplay
Bug#785472: parcellite: Parcellite fails to start after upgrading to Jessie
Package: parcellite Version: 1.1.9-1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages parcellite depends on: ii libappindicator1 0.4.92-3.1 ii libatk1.0-0 2.14.0-1 ii libc62.19-18 ii libcairo21.14.0-2.1 ii libdbusmenu-glib412.10.2-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-3 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-0 2.24.25-3 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-01.36.8-3 ii libx11-6 2:1.6.2-3 parcellite recommends no packages. parcellite suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#781265: gnome-power-manager: gnome-power-statistics segfaults always under certain case
On 3/27/15, Andreas Cadhalpun wrote: > Hi Mohammed, > > This looks like a duplicate of #774546 [1]. > Can you install libupower-glib3 0.99.2-2 from experimental and report > if that fixed this problem? > Yes, It does fix the bug. Please close the bug. Thank you. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#781265: gnome-power-manager: gnome-power-statistics segfaults always under certain case
Package: gnome-power-manager Version: 3.14.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Opened `gnome-power-statistics' (via GNOME Terminal emulator), switched between the Tabs, and it segfaults on certain cases. * What exactly did you do (or not do) that was effective (or ineffective)? Clicked on `Laptop battery.'and selected `History' (or `Statistics') Tab. Then clicked on `AC Adapter.' * What was the outcome of this action? The program simply closes spitting out `Segmentation fault' to GNOME Terminal Emulator. * What outcome did you expect instead? The programs shouldn't be stopped, and the `AC Adapter' tab should be shown instead. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-power-manager depends on: ii dbus-x11 1.8.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gnome-settings-daemon3.14.2-3 ii libc62.19-15 ii libcairo21.14.0-2.1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libupower-glib3 0.99.1-3.1 ii upower 0.99.1-3.1 gnome-power-manager recommends no packages. Versions of packages gnome-power-manager suggests: ii policykit-1 0.105-8 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#781243: network-manager-gnome: Wireless Hotspot cannot be reconfigured
Package: network-manager-gnome Version: 0.9.10.0-2 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Created a new Hotspot via `gnome-control-center network'. Status: OK, Hostspot working. * What exactly did you do (or not do) that was effective (or ineffective)? Modified Hotspot settings via `nm-connection-editor' and saved. Then tried to create the Hotspot again. * What was the outcome of this action? Status: Hotspot settings was reset. A new configuration was made by network-manager and that was used for the new Hotspot, regradless of how the user configured. * What outcome did you expect instead? The Hotpot should be working with the changed configuration. * What cannot be configured ? Nothing: `ESSID,' `Password,' `Security,' etc. * Other details 1. Desktop Environment : GNOME with GNOME shell 2. Tested on a fresh install of Debian testing weekly DVD released on 2015-03-23. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager-gnome depends on: ii dbus-x11 1.8.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gconf-service3.2.6-3 ii gnome-icon-theme 3.12.0-1 ii libc62.19-15 ii libcairo21.14.0-2.1 ii libdbus-1-3 1.8.16-1 ii libdbus-glib-1-2 0.102-1 ii libgconf-2-4 3.2.6-3 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgnome-keyring03.12.0-1+b1 ii libgtk-3-0 3.14.5-1 ii libmm-glib0 1.4.0-1 ii libnm-glib-vpn1 0.9.10.0-6 ii libnm-glib4 0.9.10.0-6 ii libnm-gtk0 0.9.10.0-2 ii libnm-util2 0.9.10.0-6 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libsecret-1-00.18-1+b1 ii network-manager 0.9.10.0-6 ii policykit-1-gnome0.105-2 Versions of packages network-manager-gnome recommends: ii gnome-keyring 3.14.0-1+b1 ii iso-codes 3.57-1 ii mobile-broadband-provider-info 20140317-1 ii notification-daemon 0.7.6-2 Versions of packages network-manager-gnome suggests: pn network-manager-openconnect-gnome pn network-manager-openvpn-gnome pn network-manager-pptp-gnome pn network-manager-vpnc-gnome -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774700: initramfs-tools: Cryptsetup tools are not included by update-initramfs command
Hi, On [2015-01-19 11:06:06], Jonas Meurer wrote: > Hi Michael, > > On Tue, 06 Jan 2015 14:40 "Michael P." wrote: > > The update-initramfs command create a initrd.img without cryptsetup > > tools, but my root partition is crypted. > > > > I tried to debug a little the > > /usr/share/initramfs-tools/hooks/cryptroot file and found that the > > add_device() function returned an empty string, when passing > > /faith--vg-root as first argument. > > > > I am on a new machine. Everything was fine after a fresh install from > > jessie beta 2 installer. But after an update, the machine didn't > > reboot anymore: grub halted after "Waiting for root device". > > I changed the logic of add_device() recently in order to fix another > bug. I fear that you discovered a new bug that I introduced by these > changes. > > In order to help me to better understand what is going on, please do the > following (as root, on the broken system): > > 1) append '-x' to the end of the first line at > /usr/share/initramfs-tools/hooks/cryptroot, so that it is: '#/bin/sh -x'. > > 2) execute '/usr/sbin/mkinitramfs -o /tmp/initrd.img-$(uname -r) $(uname > -r) >/tmp/mkinitramfs_debug.log 2>&1' > > 3) send /tmp/mkinitramfs_debug.log to this bugreport. > > 4) change the first line of /usr/share/initramfs-tools/hooks/cryptroot > back to '#/bin/sh' (i.e. remove the trailing '-x'). > > 5) remove the created files: 'rm /tmp/initrd.img-$(uname -r) > /tmp/mkinitramfs_debug.log'. I am sorry, but I couldn’t wait so I re-installed every thing. And now I don’t get the probleme anymore. For now, every thing works fine with the following versions: ii cryptsetup 2:1.6.6-4amd64disk encryption support - startup ii cryptsetup-bin 2:1.6.6-4amd64disk encryption support - command ii initramfs-tool 0.118all generic modular initramfs generat ii libcryptsetup4 2:1.6.6-4amd64disk encryption support - shared The diffences between the two installations I made is that I was more careful with the second one: I updated packages, and installed new ones step by step, with several reboots after each big steps. The first installation was more "brute": 1. Installation with jessie installer beta 2 2. Reboot 3. Remove systemd 4. Reboot 5. Upgrade to Sid 6. Installation of a lot of packages 7. Reboot 8. Bug #774700 Tell me if I still can helpfull, Cheers, -- Michaël P. gpg:D4C8 F73D A000 71C7 44EF 27E6 8982 4991 7126 3CE3 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774700: initramfs-tools: Cryptsetup tools are included by update-initramfs command
Package: initramfs-tools Version: 0.118 Severity: grave Justification: renders package unusable The update-initramfs command create a initrd.img without cryptsetup tools, but my root partition is crypted. I tried to debug a little the /usr/share/initramfs-tools/hooks/cryptroot file and found that the add_device() function returned an empty string, when passing /faith--vg-root as first argument. I am on a new machine. Everything was fine after a fresh install from jessie beta 2 installer. But after an update, the machine didn't reboot anymore: grub halted after "Waiting for root device". Then I booted in rescue mode, and compare the initrd.img of the bugged machine with the one from another machine installed the same way and working well. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 15M Jan 5 21:08 /boot/initrd.img-3.16-2-amd64 -rw-r--r-- 1 root root 15M Jan 5 22:49 /boot/initrd.img-3.16.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/install.amd/vmlinuz vga=788 initrd=/install.amd/initrd.gz rescue/enable=true -- quiet -- resume RESUME=/dev/mapper/faith--vg-swap_1 -- /proc/filesystems iso9660 btrfs ext3 ext2 ext4 jfs xfs vfat -- lsmod Module Size Used by xts12679 1 gf128mul 12970 1 xts dm_crypt 22595 1 dm_mod 89373 8 dm_crypt raid45677514 0 async_raid6_recov 16626 1 raid456 async_memcpy 12394 2 raid456,async_raid6_recov async_pq 12561 2 raid456,async_raid6_recov async_xor 12429 3 async_pq,raid456,async_raid6_recov async_tx 12566 5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov raid1 34596 0 raid0 17001 0 md_mod107672 3 raid456,raid0,raid1 vfat 17135 0 fat61986 1 vfat xfs 779874 0 libcrc32c 12426 1 xfs jfs 172859 0 ext4 469572 2 crc16 12343 1 ext4 mbcache17171 1 ext4 jbd2 82413 1 ext4 crc32c_generic 12656 2 btrfs 859433 0 xor21040 2 btrfs,async_xor raid6_pq 95238 3 async_pq,btrfs,async_raid6_recov ax88179_178a 17852 0 usbnet 30844 1 ax88179_178a mii12675 2 usbnet,ax88179_178a iwlwifi92451 0 cfg80211 405538 1 iwlwifi rfkill 18867 1 cfg80211 nls_utf8 12456 1 isofs 38965 1 hid_multitouch 17057 0 usbhid 44467 0 hid 102264 2 hid_multitouch,usbhid vga16fb21211 0 vgastate 16521 1 vga16fb usb_storage56215 1 sg 29973 0 sd_mod 44356 5 crc_t10dif 12431 1 sd_mod crct10dif_common 12356 1 crc_t10dif ehci_pci 12512 0 ahci 29195 2 libahci27158 1 ahci ehci_hcd 69837 1 ehci_pci libata177457 2 ahci,libahci xhci_hcd 148941 0 scsi_mod 191405 4 sg,usb_storage,libata,sd_mod usbcore 195340 7 usb_storage,ehci_hcd,ehci_pci,usbhid,usbnet,ax88179_178a,xhci_hcd usb_common 12440 1 usbcore thermal17559 0 thermal_sys27642 1 thermal sdhci_acpi 12810 0 sdhci 35153 1 sdhci_acpi mmc_core 102374 2 sdhci,sdhci_acpi -- /etc/initramfs-tools/modules -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n COMPRESS=gzip DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /etc/crypttab sda5_crypt UUID=45ba5770-fc21-4316-b150-5495a6166b7b none luks -- /proc/mdstat Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] unused devices: -- mkinitramfs hooks /etc/initramfs-tools/hooks/: /usr/share/initramfs-tools/hooks: busybox cryptgnupg cryptkeyctl cryptopenct cryptopensc cryptpassdev cryptroot cryptroot~ dmsetup fsck fuse keymap klibc kmod log ntfs_3g resume thermal udev zz-busybox -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages initramfs-tools depends on: ii busybox 1:1.22.0-14 ii cpio 2.11+dfsg-4 ii klibc-utils 2.0.4-2 ii kmod 18-3 ii udev
Bug#772623: imapfilter: Fails to connect to imap mailboxes
severity 772623 important tag 772623 + moreinfo thanks It seems a problem due to your specific configuration. Please provide config.lua and a verbose session. On Tue, Dec 09, 2014 at 10:04:40AM +0100, Johannes Fichtinger wrote: > Package: imapfilter > Version: 1:2.5.2-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > After a recent update of Debian testing, imapfilter fails to login into > mailboxes. The following error message is shown: > > imapfilter: error while initiating connection to IMAPSERVER at port 993 > imapfilter: login request to MYACCOUNT failed > > Before the most recent system updates in testing, i.e. before the 8/12/2014 > 3:00 CET, everything worked well. Please note that login to the very same > mailboxes from other emailclients on the same machine works flawlessly. > > There is a new version available upstream - maybe packaging that one could > help for this issue? > > I am more than happy to provide you with additional info if requested. > > > -- System Information: > Debian Release: 8.0 > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: sysvinit (via /sbin/init) > > Versions of packages imapfilter depends on: > ii libc62.19-13 > ii liblua5.2-0 5.2.3-1.1 > ii libpcre3 1:8.35-3.1 > ii libssl1.0.0 1.0.1j-1 > > imapfilter recommends no packages. > > imapfilter suggests no packages. > > -- no debconf information > > -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771778: Acknowledgement (squid3: Pinger segfault with libc)
extra info. This is on debian wheezy, squid recompiled from jesse with icap and i did rebuild to a deb : squidclamav 6.11 bug 760303, which looks like it. The bugcheck is : 2014/12/02 06:00:10 kid1| NETDB state saved; 633 entries, 2 msec 2014/12/02 06:25:04 kid1| Closing Pinger socket on FD 26 2014/12/02 06:25:18| Pinger exiting. *** glibc detected *** (pinger): free(): invalid next size (normal): 0x7fb19ba45df0 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x76a16)[0x7fb1987b6a16] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7fb1987bb7bc] /usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZNSt19basic_ostringstreamIcSt11char_traitsIcESaIcEED0Ev+0xa6)[0x7fb19900dae6] (pinger)(+0x8d99)[0x7fb19a108d99] (pinger)(+0x59c5)[0x7fb19a1059c5] (pinger)(main+0x2a0)[0x7fb19a104550] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7fb19875eead] (pinger)(+0x50a9)[0x7fb19a1050a9] === Memory map: 7fb19400-7fb194021000 rw-p 00:00 0 7fb194021000-7fb19800 ---p 00:00 0 7fb19811-7fb198116000 r-xp ca:01 134270 /usr/lib/libnfnetlink.so.0.2.0 7fb198116000-7fb198315000 ---p 6000 ca:01 134270 /usr/lib/libnfnetlink.so.0.2.0 7fb198315000-7fb198316000 rw-p 5000 ca:01 134270 /usr/lib/libnfnetlink.so.0.2.0 7fb198318000-7fb19831c000 r-xp ca:01 44 /lib/x86_64-linux-gnu/libattr.so.1.1.0 7fb19831c000-7fb19851b000 ---p 4000 ca:01 44 /lib/x86_64-linux-gnu/libattr.so.1.1.0 7fb19851b000-7fb19851c000 r--p 3000 ca:01 44 /lib/x86_64-linux-gnu/libattr.so.1.1.0 7fb19851c000-7fb19851d000 rw-p 4000 ca:01 44 /lib/x86_64-linux-gnu/libattr.so.1.1.0 7fb19852-7fb198537000 r-xp ca:01 64 /lib/x86_64-linux-gnu/libpthread-2.13.so 7fb198537000-7fb198736000 ---p 00017000 ca:01 64 /lib/x86_64-linux-gnu/libpthread-2.13.so 7fb198736000-7fb198737000 r--p 00016000 ca:01 64 /lib/x86_64-linux-gnu/libpthread-2.13.so 7fb198737000-7fb198738000 rw-p 00017000 ca:01 64 /lib/x86_64-linux-gnu/libpthread-2.13.so 7fb198738000-7fb19873c000 rw-p 00:00 0 7fb19873f000-7fb19874 rw-p 00:00 0 7fb19874-7fb1988c2000 r-xp ca:01 3330 /lib/x86_64-linux-gnu/libc-2.13.so 7fb1988c2000-7fb198ac2000 ---p 00182000 ca:01 3330 /lib/x86_64-linux-gnu/libc-2.13.so 7fb198ac2000-7fb198ac6000 r--p 00182000 ca:01 3330 /lib/x86_64-linux-gnu/libc-2.13.so 7fb198ac6000-7fb198ac7000 rw-p 00186000 ca:01 3330 /lib/x86_64-linux-gnu/libc-2.13.so 7fb198ac7000-7fb198acc000 rw-p 00:00 0 7fb198ad-7fb198ae5000 r-xp ca:01 15 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb198ae5000-7fb198ce5000 ---p 00015000 ca:01 15 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb198ce5000-7fb198ce6000 rw-p 00015000 ca:01 15 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb198ce8000-7fb198d69000 r-xp ca:01 3335 /lib/x86_64-linux-gnu/libm-2.13.so 7fb198d69000-7fb198f68000 ---p 00081000 ca:01 3335 /lib/x86_64-linux-gnu/libm-2.13.so 7fb198f68000-7fb198f69000 r--p 0008 ca:01 3335 /lib/x86_64-linux-gnu/libm-2.13.so 7fb198f69000-7fb198f6a000 rw-p 00081000 ca:01 3335 /lib/x86_64-linux-gnu/libm-2.13.so 7fb198f7-7fb199058000 r-xp ca:01 133196 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.17 7fb199058000-7fb199258000 ---p 000e8000 ca:01 133196 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.17 7fb199258000-7fb19926 r--p 000e8000 ca:01 133196 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.17 7fb19926-7fb199262000 rw-p 000f ca:01 133196 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.17 7fb199262000-7fb199277000 rw-p 00:00 0 7fb199278000-7fb19927a000 r-xp ca:01 /lib/x86_64-linux-gnu/libdl-2.13.so 7fb19927a000-7fb19947a000 ---p 2000 ca:01 /lib/x86_64-linux-gnu/libdl-2.13.so 7fb19947a000-7fb19947b000 r--p 2000 ca:01 /lib/x86_64-linux-gnu/libdl-2.13.so 7fb19947b000-7fb19947c000 rw-p 3000 ca:01 /lib/x86_64-linux-gnu/libdl-2.13.so 7fb19948-7fb199487000 r-xp ca:01 3348 /lib/x86_64-linux-gnu/librt-2.13.so 7fb199487000-7fb199686000 ---p 7000 ca:01 3348 /lib/x86_64-linux-gnu/librt-2.13.so 7fb199686000-7fb199687000 r--p 6000 ca:01 3348 /lib/x86_64-linux-gnu/librt-2.13.so 7fb199687000-7fb199688000 rw-p 7000 ca:01 3348 /lib/x86_64-linux
Bug#769981: closed by "Bernhard R. Link" (reply to 769...@bugs.debian.org) (Re: Bug#769981: reprepro complaining about 'all' architecture)
On Nov 19, 2014, at 12:45 PM, Debian Bug Tracking System wrote: > - delete "all" from all Architecture: lines in conf/distributions > - run reprepro --delete clearvanished (reprepro should tell you to do > this if you try to run it) So for my packages that will run on any platform, should they be architecture “any” then? Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769981: reprepro complaining about 'all' architecture
Package: reprepro Version: 4.12.5-1 Severity: serious Justification: Policy 5.6.8 Dear Maintainer, I tried to include a package in my existing custom apt repository, and now all it does is complain about the 'all' architecture, which is apparently a valid architecture. https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture bear:/var/www/apt# reprepro list wheezy Error: Distribution wheezy contains an architecture called 'all'. There have been errors! So now I cannot update my repository. This worked previously, and I do not understand the nature of the complaint. It is not providing sufficient detail, and my inquiries on the debian-user list go unanswered. I am not sure how to proceed. -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-486 Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages reprepro depends on: ii libarchive12 3.0.4-3+nmu1 ii libbz2-1.0 1.0.6-4 ii libc6 2.13-38+deb7u4 ii libdb5.1 5.1.29-5 ii libgpg-error0 1.10-3.1 ii libgpgme11 1.2.0-1.4+deb7u1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages reprepro recommends: ii apt 0.9.7.9+deb7u5 Versions of packages reprepro suggests: pn gnupg-agent pn inoticoming pn lzip ii lzma 9.22-2 ii xz-utils [lzma] 5.1.1alpha+20120614-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#757308: grass: Please update to use wxpython3.0
On Wed, Aug 20, 2014 at 05:53:18PM +1200, Hamish wrote: > Hamish wrote: > > > grass 6.4.4.packaging is currently (basically) ready in DebianGIS > > > git. > > Sebastiaan: > > But not by using git-import-orig. The upstream branch hasn't been > > updated with the grass_6.4.4.orig.tar.gz contents. > > it was done in the master branch, > > http://git.linuxminded.nl/?p=pkg-grass/grass;a=commit;h=d183a32b883dbad88e0d751d030e177dd90926a0 > > tagging is currently incomplete, but known todo and discussed privately. > > ... Do you mind to discuss NOT privately? > > You should run lintian showing all tags after your build to get an > > idea of what is left to fix before I would consider an upload. > > er, you really think we don't do that and know exactly what they are? > We've been busy packaging this software for more than a dozen years! > Not masking false positives and "real but won't-fix in this major > version" lintian issues is not a bug IMHO. > Bas, the grass package has a long list of lintian issues due mainly to specific choices of upstream team and historical reasons. It is quite pointless trying to respect the full policy by patching at every new release, and it would be also an heavy job (with no hopes of being accepted upstream for merging). This is well expected for such a scientific program born in the 80s and having a very conservative and tiny development team. > No doubt the main rules file could use a bit of a refresh here and there > (supporting 'make -j' would be nice), but let's continue this > conversation on the DebainGIS list, not in a ticket about transitioning > to wxpython3.0. > I don't understand *why* the d-gis repo is not already up-to-date with an appropriate branching and tagging for the proper support. It is quite annoying working with yet-another-git-archive. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747899: hgview crashes since upgrade to mercurial 2.9.2-1
Package: hgview Version: 1.8.0-1 Severity: grave Justification: renders package unusable jeremyp@sky[~]> cd /tmp/ jeremyp@sky[/tmp]> mkdir test jeremyp@sky[/tmp]> cd test/ jeremyp@sky[/tmp/test]> hg init jeremyp@sky[/tmp/test]> hg --version Mercurial Distributed SCM (version 2.9.2) (see http://mercurial.selenic.com for more information) Copyright (C) 2005-2014 Matt Mackall and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. jeremyp@sky[/tmp/test]> dpkg -l mercurial Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii mercurial 2.9.2-1 amd64easy-to-use, scalable distributed version control system jeremyp@sky[/tmp/test]> hgview Traceback (most recent call last): File "/usr/local/bin/hgview", line 38, in main() File "/usr/local/lib/python2.7/dist-packages/hgviewlib/application.py", line 225, in main sys.exit(start(repo, opts, args, parser.error)) File "/usr/local/lib/python2.7/dist-packages/hgviewlib/application.py", line 173, in start app = Application(repo, opts, args) File "/usr/local/lib/python2.7/dist-packages/hgviewlib/qt4/application.py", line 54, in __init__ super(HgViewQtApplication, self).__init__(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hgviewlib/application.py", line 83, in __init__ self.choose_viewer() File "/usr/local/lib/python2.7/dist-packages/hgviewlib/application.py", line 107, in choose_viewer viewer = self.HgRepoViewer(self.repo) File "/usr/local/lib/python2.7/dist-packages/hgviewlib/qt4/hgrepoviewer.py", line 90, in __init__ self.setupBranchCombo() File "/usr/local/lib/python2.7/dist-packages/hgviewlib/qt4/hgrepoviewer.py", line 168, in setupBranchCombo allbranches = sorted(self.repo.branchtags().items()) AttributeError: 'localrepository' object has no attribute 'branchtags' -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages hgview depends on: ii hgview-common 1.8.0-1 ii python 2.7.5-5 ii python-docutils 0.11-3 ii python-qscintilla2 2.8.1-1 ii python-qt4 4.10.3+dfsg1-1+b1 hgview recommends no packages. hgview suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#746167: FTBFS in sid/Tcl 8.6
On Sun, Apr 27, 2014 at 05:15:43PM +0100, Michael Tautschnig wrote: > Package: aolserver4-nsopenssl > Version: 3.0beta26-4 > Severity: serious > Usertags: goto-cc > > While compiling the package using our research compiler infrastructure the > build > failed with the following error: > > [...] > gcc -g -I/usr/include/openssl -I/usr/kerberos/include -O2 -Wall -fPIC > -I/usr/include/aolserver4 -I/usr/include/tcl8.6 -DNO_CONST > -DUSE_INTERP_ERRORLINE -DPACKAGE_NAME=\"tcl\" -DPACKAGE_TARNAME=\"tcl\" > -DPACKAGE_VERSION=\"8.6\" -DPACKAGE_STRING=\"tcl\ 8.6\" > -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 > -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 > -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 > -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 > -D_THREAD_SAFE=1 -DHAVE_PTHREAD_ATTR_SETSTACKSIZE=1 -DHAVE_PTHREAD_ATFORK=1 > -DTCL_THREADS=1 -DTCL_CFGVAL_ENCODING=\"iso8859-1\" -DHAVE_ZLIB=1 > -DMODULE_SCOPE=extern -DHAVE_CAST_TO_UNION=1 -DTCL_SHLIB_EXT=\".so\" > -DNDEBUG=1 -DTCL_CFG_OPTIMIZED=1 -DTCL_TOMMATH=1 -DMP_PREC=4 > -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_IS_LONG=1 -DHAVE_GETCWD=1 > -DHAVE_MKSTEMP=1 -DHAVE_OPENDIR=1 -DHAVE_STRTOL=1 -DHAVE_WAITPID=1 > -DHAVE_GETNAMEINFO=1 -DHAVE_GETADDRINFO=1 -DHAVE_FREEADDRINFO=1 > -DHAVE_GAI_STRERROR=1 -DHAVE_STRUCT_ADDRINFO=1 -DHAVE_STRUCT_IN6_ADDR=1 > -DHAVE_STRUCT_SOCKADDR_IN6=1 -DHAVE_STRUCT_SOCKADDR_STORAGE=1 > -DHAVE_GETPWUID_R_5=1 -DHAVE_GETPWUID_R=1 -DHAVE_GETPWNAM_R_5=1 > -DHAVE_GETPWNAM_R=1 -DHAVE_GETGRGID_R_5=1 -DHAVE_GETGRGID_R=1 > -DHAVE_GETGRNAM_R_5=1 -DHAVE_GETGRNAM_R=1 -DHAVE_GETHOSTBYNAME_R_6=1 > -DHAVE_GETHOSTBYNAME_R=1 -DHAVE_GETHOSTBYADDR_R_8=1 -DHAVE_GETHOSTBYADDR_R=1 > -DHAVE_TERMIOS_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_TIME_H=1 > -DTIME_WITH_SYS_TIME=1 -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 -DHAVE_MKTIME=1 > -DHAVE_TM_GMTOFF=1 -DHAVE_TIMEZONE_VAR=1 -DHAVE_STRUCT_STAT_ST_BLOCKS=1 > -DHAVE_STRUCT_STAT_ST_BLKSIZE=1 -DHAVE_BLKCNT_T=1 -DHAVE_INTPTR_T=1 > -DHAVE_UINTPTR_T=1 -DHAVE_SIGNED_CHAR=1 -DHAVE_LANGINFO=1 -DHAVE_MKSTEMPS=1 > -DHAVE_FTS=1 -DHAVE_SYS_IOCTL_H=1 -DTCL_UNLOAD_DLLS=1 -DHAVE_CPUID=1 > -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" > -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DTCL_CFG_OPTIMIZED=1 > -DTCL_CFG_DEBUG=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 > -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 > -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_INTTYPES_H=1 > -DHAVE_TIMEGM=1 -DHAVE_DRAND48=1 -DHAVE_RANDOM=1 -DHAVE_POLL=1 > -DHAVE_GETADDRINFO=1 -DHAVE_GETNAMEINFO=1-c -o tclcmds.o tclcmds.c > :0:0: warning: "PACKAGE_NAME" redefined [enabled by default] > :0:0: note: this is the location of the previous definition > :0:0: warning: "PACKAGE_TARNAME" redefined [enabled by default] > :0:0: note: this is the location of the previous definition > :0:0: warning: "PACKAGE_VERSION" redefined [enabled by default] > :0:0: note: this is the location of the previous definition > :0:0: warning: "PACKAGE_STRING" redefined [enabled by default] > :0:0: note: this is the location of the previous definition > tclcmds.c: In function 'NsTclOpenSSLObjCmd': > tclcmds.c:338:31: error: 'Tcl_Interp' has no member named 'result' > sprintf(interp->result, "%d", sslconn->peerport); >^ Thanks, legacy code requires -DUSE_INTERP_RESULT definition to build under 8.6, the fix will be applied ASAP. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#746168: FTBFS in sid/Tcl 8.6
The same fix of #746167 is required, thanks.
On Sun, Apr 27, 2014 at 05:18:51PM +0100, Michael Tautschnig wrote:
> Package: aolserver4-nspostgres
> Version: 4.5+20110709-1
> Severity: serious
> Usertags: goto-cc
>
> While compiling the package using our research compiler infrastructure the
> build
> failed with the following error:
>
> [...]
> gcc -Wall -g -Wl,--no-as-needed -O2 -DBIND_EMULATION
> -I/usr/include/postgresql -DFOR_ACS_USE -O2 -Wall -fPIC
> -I/usr/include/aolserver4 -I/usr/include/tcl8.6 -DNO_CONST
> -DUSE_INTERP_ERRORLINE -DPACKAGE_NAME=\"tcl\" -DPACKAGE_TARNAME=\"tcl\"
> -DPACKAGE_VERSION=\"8.6\" -DPACKAGE_STRING=\"tcl\ 8.6\"
> -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
> -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1
> -D_THREAD_SAFE=1 -DHAVE_PTHREAD_ATTR_SETSTACKSIZE=1 -DHAVE_PTHREAD_ATFORK=1
> -DTCL_THREADS=1 -DTCL_CFGVAL_ENCODING=\"iso8859-1\" -DHAVE_ZLIB=1
> -DMODULE_SCOPE=extern -DHAVE_CAST_TO_UNION=1 -DTCL_SHLIB_EXT=\".so\"
> -DNDEBUG=1 -DTCL_CFG_OPTIMIZED=1 -DTCL_TOMMATH=1 -DMP_PREC=4
> -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_IS_LONG=1 -DHAVE_GETCWD=1
> -DHAVE_MKSTEMP=1 -DHAVE_OPENDIR=1 -DHAVE_STRTOL=1 -DHAVE_WAITPID=1
> -DHAVE_GETNAMEINFO=1 -DHAVE_GETADDRINFO=1 -DHAVE_FREEADDRINFO=1
> -DHAVE_GAI_STRERROR=1 -DHAVE_STRUCT_ADDRINFO=1 -DHAVE_STRUCT_IN6_ADDR=1
> -DHAVE_STRUCT_SOCKADDR_IN6=1 -DHAVE_STRUCT_SOCKADDR_STORAGE=1
> -DHAVE_GETPWUID_R_5=1 -DHAVE_GETPWUID_R=1 -DHAVE_GETPWNAM_R_5=1
> -DHAVE_GETPWNAM_R=1 -DHAVE_GETGRGID_R_5=1 -DHAVE_GETGRGID_R=1
> -DHAVE_GETGRNAM_R_5=1 -DHAVE_GETGRNAM_R=1 -DHAVE_GETHOSTBYNAME_R_6=1
> -DHAVE_GETHOSTBYNAME_R=1 -DHAVE_GETHOSTBYADDR_R_8=1 -DHAVE_GETHOSTBYADDR_R=1
> -DHAVE_TERMIOS_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_TIME_H=1
> -DTIME_WITH_SYS_TIME=1 -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 -DHAVE_MKTIME=1
> -DHAVE_TM_GMTOFF=1 -DHAVE_TIMEZONE_VAR=1 -DHAVE_STRUCT_STAT_ST_BLOCKS=1
> -DHAVE_STRUCT_STAT_ST_BLKSIZE=1 -DHAVE_BLKCNT_T=1 -DHAVE_INTPTR_T=1
> -DHAVE_UINTPTR_T=1 -DHAVE_SIGNED_CHAR=1 -DHAVE_LANGINFO=1 -DHAVE_MKSTEMPS=1
> -DHAVE_FTS=1 -DHAVE_SYS_IOCTL_H=1 -DTCL_UNLOAD_DLLS=1 -DHAVE_CPUID=1
> -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DTCL_CFG_OPTIMIZED=1
> -DTCL_CFG_DEBUG=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_INTTYPES_H=1
> -DHAVE_TIMEGM=1 -DHAVE_DRAND48=1 -DHAVE_RANDOM=1 -DHAVE_POLL=1
> -DHAVE_GETADDRINFO=1 -DHAVE_GETNAMEINFO=1-c -o nspostgres.o nspostgres.c
> :0:0: warning: "PACKAGE_NAME" redefined [enabled by default]
> :0:0: note: this is the location of the previous definition
> :0:0: warning: "PACKAGE_TARNAME" redefined [enabled by default]
> :0:0: note: this is the location of the previous definition
> :0:0: warning: "PACKAGE_VERSION" redefined [enabled by default]
> :0:0: note: this is the location of the previous definition
> :0:0: warning: "PACKAGE_STRING" redefined [enabled by default]
> :0:0: note: this is the location of the previous definition
> nspostgres.c: In function 'Ns_PgSetErrorstate':
> nspostgres.c:246:5: warning: enumeration value 'PGRES_COPY_BOTH' not handled
> in switch [-Wswitch]
> switch (PQresultStatus(nsConn->res)) {
> ^
> nspostgres.c:246:5: warning: enumeration value 'PGRES_SINGLE_TUPLE' not
> handled in switch [-Wswitch]
> nspostgres.c: In function 'PgCmd':
> nspostgres.c:1772:23: error: 'Tcl_Interp' has no member named 'result'
> sprintf(interp->result, "%u", nspgConn->cNum);
>^
> nspostgres.c:1778:19: error: 'Tcl_Interp' has no member named 'result'
> interp->result = "ok";
>^
> nspostgres.c:1780:19: error: 'Tcl_Interp' has no member named 'result'
> interp->result = "bad";
>^
> nspostgres.c: In function 'pg_column_command':
> nspostgres.c:1985:17: error: 'Tcl_Interp' has no member named 'result'
> sprintf (interp->result, "%d", tinfo->ncolumns);
> ^
> make[1]: *** [nspostgres.o] Error 1
>
> Looking at the latest build logs for the package, this may be caused by the
> updates to Tcl (the latest build was against Tcl 8.5, but sid now has 8.6).
>
> The full build log is attached.
>
> Best,
> Michael
>
--
Francesco P. Lovergine
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742148: shapelib: FTBFS on powerpc (Both BIG_ENDIAN and LITTLE_ENDIAN defined!
On Wed, Mar 26, 2014 at 02:17:50PM +0100, Cyril Brulebois wrote: > Francesco P. Lovergine (2014-03-26): > > While I accepted the patch a few minutes ago, indeed I seriously now doubt > > that > > the fix is correct. > > > > It seems to me that in the original program the LITTLE_ENDIAN should be > > intended as a static build-time definition for the host where the program > > is built. > > > > So the NAN definition should be intended instead as nan(). That's because > > the shapefile format is endianess-independent and shapelib reads/writes > > fields on the > > basis of the host platform to respect the format. So the NAN should be > > intended as the *host* NaN format, indeed (to be translated in the shp > > format NaN, i.e. little endian). > > That poses a problem on the pcc architecture for instance: __nan_bytes will > > be not the > > correct NaN value and will result as a big endian in the file. > > > > See http://dl.maptools.org/dl/shapelib/shapefile.pdf for format. > > > > Do you agree? > > To be frank I didn't quite get why it was considered a good idea to > hardcode setting -Dfoo in contrib/Makefile unconditionally instead of > looking at the relevant arch-specific bits. So I assumed this was > deliberate and that this setting was orthogonal to what's in system > headers, that's why I proposed the patch you saw. > > (From a quick look between last two upstream releases, this part didn't > change; I guess this issue popped up due to updated system headers, but > I didn't look into it to see what exactly triggered it.) > I guess the contrib stuff is not so well maintained and probably not too much coherent. > I guess looking at __BYTE_ORDER would be a better way to actually check > a system's endianness, #error-ing if it's neither __LITTLE_ENDIAN or > __BIG_ENDIAN; I have no idea how much that is portable, but upstream > should probably now a bit about msvc and advise whether that's a viable > option. > Well, I would avoid to upset the upstream code that much, a simple use of nan() instead of NAN could propagate correctly. My only doubt is about the possible inclusion of special IEEE values within the final shapefile, a condition that should not be admitted on the basis of the specs. But this is bread for upstream's teeth. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742148: shapelib: FTBFS on powerpc (Both BIG_ENDIAN and LITTLE_ENDIAN defined!
ian/patches/series > shapelib-1.3.0/debian/patches/series > --- shapelib-1.3.0/debian/patches/series 2014-03-18 22:47:55.0 > +0100 > +++ shapelib-1.3.0/debian/patches/series 2014-03-26 10:38:26.0 > +0100 > @@ -2,3 +2,4 @@ > 0003-Properly-use-libtool.patch > 0004-Dynamically-link-the-shp-binaries-to-libshp.patch > 0005-Stop-setting-CFLAGS-and-PREFIX-in-the-Makefile.patch > +0006-Fix-FTBFS-avoid-clash-with-_ENDIAN-defines.patch > ___ > Pkg-grass-devel mailing list > pkg-grass-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742273: osgearth: unsatisfiable libv8-dev build-dep
On Fri, Mar 21, 2014 at 03:26:04PM +0100, Sebastiaan Couwenberg wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 03/21/2014 02:53 PM, Julien Cristau wrote: > > osgearth added an unconditional build-dep on libv8-dev, however > > that package is only built on little endian archs by the looks of > > it (it's missing on mips, powerpc, s390x and sparc). > > Because libv8 is not available on all architectures, I've filed an RM > request for osgearth on the architectures where it cannot be built. > (#742261) > The point is: is it possible to build without libv8-dev on those archs and still having a working product? In that case we could change the b-d chain appropriately. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735814: ossim: FTBFS: configure: error: libtiff support required!
On Sun, Feb 16, 2014 at 12:23:31AM -0800, Hamish wrote: > Hi, > > I thought I'd do an info drop. > > So in the past years Frankie maintained the package from DebianGIS > git on Alioth (now the git repo on spawn-of-Alioth). > > http://anonscm.debian.org/gitweb/?p=pkg-grass/ossim.git;a=summary > > and you'll see there that he started on packaging the newer 1.8 > version, with libtiff updated, but I think he found the build system > too much of a mess so stopped working on it in favour of letting > someone else on the DebianGIS team try. > Yep, I can confirm that. Also, my main interest at the time was about packaging orfeotoolbox, which still has issues (currently almost solved) in using external stuff. So I stopped the upgrading of the ossim library and tools. > Since then OSSIM has moved to cmake and the build system is much > improved. A fine Google of Code student named M. Rashad worked on > OSSIM last summer, and after the summer was over started on > new-generation OSSIM deb packages. Hopefully me & Massimo can > convince him to join DebianGIS and continue the work there. :-) > > Anyway it is his packages you'll find in UbuntuGIS's ppa, and yes, > they'll be a good starting point for the Mk III version of the OSSIM > package in Debian. (see also ancient ossim-old/ in alioth pkg-grass > svn repo for MkI) > That could be possibily a good target for next orfeo package. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699647: proftpd-mod-geoip: /usr/lib/proftpd/mod_geoip.so missing after upgrade from sid
On Mon, Jan 27, 2014 at 08:35:02PM +0100, Andreas Beckmann wrote: > Won't work. Even if you ensure via Conflicts/Pre-Depends that the buggy > package gets removed, the postrm script will stay around. You cannot force a > package to be purged. > (Changing the module filename would work.) which seems to me much better than a ugly hack such as the proposed one. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699647: proftpd-mod-geoip: /usr/lib/proftpd/mod_geoip.so missing after upgrade from sid
On Sun, Jan 26, 2014 at 02:02:30PM +0100, Guillem Jover wrote: > Hi! > > On Sun, 2014-01-26 at 13:06:47 +0100, Andreas Beckmann wrote: > > what are your deprecation plans for dpkg-query --control-path? > > > > This is an actual use-case that requires --control-path in wheezy and > > jessie. Or is there a "better" way to achieve this with dpkg? > > > Old postrm is broken and will play havoc after the new package was > > unpacked. Therefore we have to delete it in the new preinst. > I wonder if the correct fix would be simply moving the Breaks/Replaces in the proftpd-basic binary section instead of the proftpd-mod-geoip pkg. That would force removing of the old package before proceeding with the installation of both -basic and the new package. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#736334: Sqlite3 backend not more working
On Wed, Jan 22, 2014 at 10:18:59AM -0600, Sébastien Villemot wrote: > > > downgrading solve the issue? > > > > > > > As written, no. It is still broken after downgrading and cleaned the guile > > cache. Any other suggestion? > > Sorry, I had read your message too quickly, and was confused by your > statement that the bug was unrelated to upgrades. > > What about downgrading libdbi1 ? > Ah right, it works by downgrading both libdbd-sqlite3 AND libdbi1. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#736334: Sqlite3 backend not more working
On Wed, Jan 22, 2014 at 07:53:47AM -0600, Sébastien Villemot wrote: > Le mercredi 22 janvier 2014 à 12:34 +0100, Francesco Paolo Lovergine a > écrit : > > I use gnucash daily, with the sqlite3 backend for all my stuff. Today after > > updating my this sid box, gnucash is not more able to load any sqlite3 > > gnucash > > file (with a message like: no suitable backend found for file .gnucash). > > All worked perfectly and my files are still usable on other sid boxes. > > Even cleaning the guile cache gave no results. > > > Curiously the list of today upgrades on this box seem unrelated: > [...] > > 2014-01-22 09:42:28 upgrade libdbd-sqlite3:i386 0.8.3-1+s-5+b1 0.9.0-1 > > No so unrelated, since you upgraded libdbd-sqlite3 (see above). Does > downgrading solve the issue? > As written, no. It is still broken after downgrading and cleaned the guile cache. Any other suggestion? -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
