Bug#930744: marked as done (linux-image-4.19.0-5-amd64: wlan/wifi not working)
Your message dated Thu, 20 Jun 2019 00:36:19 + with message-id and subject line Bug#930743: fixed in linux 4.19.37-5 has caused the Debian Bug report #930743, regarding linux-image-4.19.0-5-amd64: wlan/wifi not working to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 930743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.19.37-4 Severity: normal Dear Maintainer, my WiFi stopped working after the kernel upgrade. When booting 4.19.0.4, I see lt-nkiesel kernel: wl: loading out-of-tree module taints kernel. lt-nkiesel kernel: wl: module license 'MIXED/Proprietary' taints kernel. lt-nkiesel kernel: wl: module verification failed: signature and/or required key missing - tainting kernel lt-nkiesel kernel: wlan0: Broadcom BCM43b1 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) lt-nkiesel NetworkManager[771]: [1560965780.6047] wifi-nl80211: (wlan0): using nl80211 for WiFi device control When booting 4.19.0.5, I see lt-nkiesel kernel: wl: loading out-of-tree module taints kernel. lt-nkiesel kernel: wl: module license 'MIXED/Proprietary' taints kernel. lt-nkiesel kernel: wl: module verification failed: signature and/or required key missing - tainting kernel lt-nkiesel kernel: wl: disagrees about version of symbol cfg80211_inform_bss_frame_data lt-nkiesel kernel: wl: Unknown symbol cfg80211_inform_bss_frame_data (err -22) lt-nkiesel kernel: wl: disagrees about version of symbol skb_put lt-nkiesel kernel: wl: Unknown symbol skb_put (err -22) (more complaining about other symbols) -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: Precision M4800 product_version: 00 chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: A19 board_vendor: Dell Inc. board_name: 0WJNC2 board_version: A00 ** Network interface configuration: source /etc/network/interfaces.d/* auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [8086:0c04] (rev 06) Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [1028:05cc] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) (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- Capabilities: Kernel driver in use: pcieport 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05cc] 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: i915 Kernel modules: i915 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [1028:05cc] 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: snd_hda_intel Kernel modules: snd_hda_intel 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Dell 8 Series/C220 Series Chipset Family USB xHCI [1028:05cc] 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: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset
Bug#930743: marked as done (ABI changed without an ABI bump)
Your message dated Thu, 20 Jun 2019 00:36:19 + with message-id and subject line Bug#930743: fixed in linux 4.19.37-5 has caused the Debian Bug report #930743, regarding ABI changed without an ABI bump to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 930743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.19.37-4 Severity: important We forgot to add an ABI reference for 4.19.0-5 after the last ABI bump, and many symbol versions have changed between versions 4.19.37-3 and -4. I don't yet understand why that is, as the corresponding versions for stretch-backports have the same ABI (except in mwifiex, which is ignored). Ben. -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.19.37-5 We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 930...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Jun 2019 23:16:58 +0100 Source: linux Architecture: source Version: 4.19.37-5 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 926539 930743 Changes: linux (4.19.37-5) unstable; urgency=medium . [ Romain Perier ] * [sparc64] Fix device naming inconsistency between sunhv_console and sunhv_reg (Closes: #926539) . [ Ben Hutchings ] * tcp: Avoid ABI change for DoS fixes (Closes: #930743) * Add ABI reference for 4.19.0-5 Checksums-Sha1: 553db42bef4633b7ca929e9b336bbabd21b34504 189124 linux_4.19.37-5.dsc dee856cd02b146cf2d930f80c21e12a463c15577 4255088 linux_4.19.37-5.debian.tar.xz 801e3d99cd42b2f445e948acac43815b6e1e94a7 47317 linux_4.19.37-5_source.buildinfo Checksums-Sha256: c09624619d9808aae877a7fc638f259181d9f9dc53aee789ecbe82a0ed3498eb 189124 linux_4.19.37-5.dsc 5a292f47187414902c906088312b35d320ceeafb9a901ad779e1d6fea5d31b0d 4255088 linux_4.19.37-5.debian.tar.xz cd895cc6f4abb1c9ebe6bd4dea9ae022826ce7672a56e15588abbbf732b7343c 47317 linux_4.19.37-5_source.buildinfo Files: 6effcd246c4e06fbfcc2a93d6d0cea0b 189124 kernel optional linux_4.19.37-5.dsc b684b0c52f7bc7477b1ac054e25e1885 4255088 kernel optional linux_4.19.37-5.debian.tar.xz ff96135cf7fd8017e597ab08341d69d4 47317 kernel optional linux_4.19.37-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAl0K0ZoACgkQ57/I7JWG EQmYvg/+P71WYzYL+OGxriiAPHL9SLAM1t0zb/xjme4RNN967raC11liHTY/TrSl 1PaaI41laRXaobSwOPp11vL0ImRlRqr3XXWPcjBVTeOtaRAOGb4p6uGaH3MNK0m7 NgahWmH4ZwKxncciYVLZjjpgt1h3QVO8+xispaQlHaG+x5X/MX9woN9ZOt31KQOP +ME71SzERkS8XYs+fc31XyjQYi8ushcbrZru9mm2wtK008wWX4UFWD6HZIOf2NaZ hYGmKe5/VtyHK9GbG2nzBx9qVe47KEsFOHFMN47yWzxJcJrhsV6k2mn4+h921myJ wvlaqWHZW6QEA3qn1hazu+3zA0BfnxNHHzaLjcyeiNUVZ4beBUHDjvBItl0oYwMn ZUGfTXqfXsCOJ0EXdb0J9K3Da9McegWPM/J2D3Ko/XcTV2meVEeFhiD7nUR/JbCm 9NRcffW+swGV2DBt2u27lwYswa4ZyDHcd8vtePP4IcApBgFBqu0Dx94niRiKcV78 dletH3v/aL+8PAT1KdxOqj086I2vN9t1jCQ2+dHMTT6oIQ0nXdqdT1EUzuUpr6ch rnHtRHI6ezA2I5IEC78PYancq7Z7kEUaTlyvNlMA2veLiMokngntOD6GTYld+xoJ DQ5cXuj9rTentpx8IChzJcKiyDTXvFFbNtdxrdm9jIvOMboDKl0= =iVca -END PGP SIGNATURE End Message ---
Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop
On Wed, 19 Jun 2019 22:16:58 +0200 Ansgar Burchardt wrote: > Jonathan Dowland writes: > > So far as I am aware there is still radio silence from active GNOME > > packaging team members regarding this issue. No comment yet on the > > patch I adapted, positive or negative; this bug (#927667) remains > > at an RC severity. > > > > I've not yet read all the thread that Samuel linked to[1] but it looks > > like it leans in favour of preserving the current default (xorg). > > > > I'm copying -release team to see if they have any (new) opinions on > > the matter. Otherwise I guess it's up to someone to prepare an NMU > > upload, which I will *try* to look at in the next few days, but can't > > make any guarantees. > > I'm just a GNOME user, but from gdm3's changelog the default was > switched to Wayland in July 2017 (or August 2017 for unstable). I > myself only noticed the switch after reading it happened somewhere on > the internet shortly after it happened. gdm was switched over to use Wayland before the main session was and in Debian we kept that default for gdm (even for stretch, and still true for buster). gdm runs in a much more limited environment though, so some of the limitations (like screen sharing) do not really affect the gdm session. I suppose the a11y issues that were pointed out for Wayland do affect the gdm wayland session though? What kind of display technology gdm is using is a separate discussion though from what kind of desktop session is started as default: GNOME on Xorg or GNOME on Wayland. When you talk about "gdm3's default", what exactly do you mean: the display technology gdm is using or the type of GNOME session that is started as default? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: severity of 930743 is serious
Processing commands for cont...@bugs.debian.org: > severity 930743 serious Bug #930743 [src:linux] ABI changed without an ABI bump Bug #930744 [src:linux] linux-image-4.19.0-5-amd64: wlan/wifi not working Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 930743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930743 930744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop
Hey there, Le 19/06/2019 à 22:19, Simon McVittie a écrit : - Ubuntu GNOME team: which recent Ubuntu versions, if any, are using Wayland for their GNOME-based desktop? We don't have any supported Ubuntu version using Wayland by default, our motivations for sticking to Xorg were mostly desktop sharing/rdp support and the fact that under wayland a gnome-shell segfault takes the whole session down without giving user a chance to save their work. While screen sharing is being actively being worked on, our metrics show that gnome-shell errors are still quite common, even in recent versions so it's not likely that we change our default for the next LTS. Cheers, Sebastien Bacher
Bug#915333: marked as done (git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x))
Your message dated Wed, 19 Jun 2019 21:33:53 + with message-id and subject line Bug#915333: fixed in ghc 8.4.4+dfsg1-3 has caused the Debian Bug report #915333, regarding git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: git-annex Version: 7.20181121-1 Severity: important Dear Maintainer, I wanted to use git-annex on this machine (Fujitsu Q700 NAS), but it Crashes with "Illegal Instruction". I don't have these problems with other Packages or with the upstream build of git-annex. Many Thanks for Maintaining the Debian Package. Regards, Lukas Straub /proc/cpuinfo: processor : 0 model name : Feroceon 88FR131 rev 1 (v5l) BogoMIPS: 400.00 Features: swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part: 0x131 CPU revision: 1 Hardware: Marvell Kirkwood (Flattened Device Tree) Revision: Serial : -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 4.18.0-0.bpo.1-marvell 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) Versions of packages git-annex depends on: ii curl7.62.0-1 ii git 1:2.19.2-1 ii libatomic1 8.2.0-9 ii libc6 2.27-8 ii libffi6 3.2.1-9 ii libgmp102:6.1.2+dfsg-3 ii libmagic1 1:5.34-2 ii libsqlite3-03.25.3-2 ii libxml2 2.9.4+dfsg1-7+b2 ii netbase 5.5 ii openssh-client 1:7.9p1-4 ii rsync 3.1.2-2.2 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages git-annex recommends: ii aria2 1.34.0-3 ii bind9-host 1:9.11.5+dfsg-1 ii git-remote-gcrypt 1.1-1 ii gnupg 2.2.11-1 ii lsof 4.89+dfsg-0.1 ii nocache1.0-1 Versions of packages git-annex suggests: pn adb pn bup pn libnss-mdns pn magic-wormhole pn tahoe-lafs ii tor 0.3.4.9-5 pn uftp pn xdot pn youtube-dl -- no debconf information --- End Message --- --- Begin Message --- Source: ghc Source-Version: 8.4.4+dfsg1-3 We believe that the bug you reported is fixed in the latest version of ghc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated ghc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 20 Jun 2019 00:08:21 +0300 Source: ghc Architecture: source Version: 8.4.4+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 915333 Changes: ghc (8.4.4+dfsg1-3) unstable; urgency=medium . * Use the ARM7TDMI core on armel (Closes: #915333) Checksums-Sha1: bd8389c4a2540751bc2ed6e3dac43720e1566bad 2400 ghc_8.4.4+dfsg1-3.dsc 1276cee9dd4552aa7848179a52f1982733356ea0 59396 ghc_8.4.4+dfsg1-3.debian.tar.xz 22bc2b0285bc7db75011c5c6b3eb6e2873e11706 9954 ghc_8.4.4+dfsg1-3_source.buildinfo Checksums-Sha256: aa8b1f74548dae2a3364fac27a6e130e73a7dc56aca860af37f90d59c953a60b 2400 ghc_8.4.4+dfsg1-3.dsc a5d39632dd783d234b2c18803d285d277b8707e4f91ffb8193b66f3a33e00a0b 59396 ghc_8.4.4+dfsg1-3.debian.tar.xz ae581a5a049381c196e6eb5d16403aeda4aeb5056178b4a970ebe9341f6aed99 9954 ghc_8.4.4+dfsg1-3_source.buildinfo Files: 17fc16dba7138e69f55e0c23a2164216 2400 haskell optional ghc_8.4.4+dfsg1-3.dsc 9e462d56d9efd8eb584c6fcb613da57e 59396 haskell optional ghc_8.4.4+dfsg1-3.debian.tar.xz 9dc9f69e4cb7c932140fec1c0bedccf3 9954 haskell optional ghc_8.4.4+dfsg1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAl0KpmcUHGlsaWFzdHNp
Processed: reassign 929060 to cryptsetup-initramfs, severity of 929060 is important
Processing commands for cont...@bugs.debian.org: > reassign 929060 cryptsetup-initramfs Bug #929060 [initramfs-tools] update-initramfs silently failed to change \ Bug reassigned from package 'initramfs-tools' to 'cryptsetup-initramfs'. Ignoring request to alter found versions of bug #929060 to the same values previously set Ignoring request to alter fixed versions of bug #929060 to the same values previously set > severity 929060 important Bug #929060 [cryptsetup-initramfs] update-initramfs silently failed to change \ Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 929060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929469: systemd-networkd: systemd-networkd: fails with "could not set address: Permission denied"
Hi Raphael, On Tue, 11 Jun 2019 15:51:14 +0200 Raphael Hertzog wrote: > Hi, > > On Wed, 05 Jun 2019, Michael Biebl wrote: > > systemd-networkd.service in v241 is locked down more tightly then v232. > > It might be worth a try to comment out the hardening features one by one > > to see if one of them causes your problem. > > Thanks for the idea! I tried that but it did not help. I found the issue > after a few more tries tweaking the network configuration file. It's > simply that the system has IPv6 disabled in the kernel policy while the > .network file instructs to configure an IPv6 address. > > Both are contradictory but they happily lived together up-to-now. > I don't know what changed but if we don't improve systemd-networkd > to just skip IPv6 configuration when the kernel has a policy disabling > IPv6, then we will have plenty of servers broken on upgrades because > it's quite common to keep the network configuration file provided by > the hoster and just disable IPv6 at the kernel level with sysctl: > > $ grep ipv6 /etc/sysctl.conf > # Disable ipv6 > net.ipv6.conf.all.disable_ipv6 = 1 > net.ipv6.conf.default.disable_ipv6 = 1 > net.ipv6.conf.lo.disable_ipv6 = 1 Ok, thanks for figuring out the root cause. Given that this only happens under very special circumstances and networkd not being enabled by default, I'm not entirely sure if this issue should qualify as RC. Cherry-picking the 6 upstream commits leads to a merge conflict when applied on top of v241 and I haven't yet investigated if those can easily be resolved. TBH, I feel a bit uneasy doing this change so late in the release cycle and personally I would downgrade this issue to non-RC and fix this via a v243 upload to buster-backports. If you feel strongly about this though, please feel free ask the release team if the change is ok. A tested patch set would be great in this case. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop
On Wed, 19 Jun 2019 at 17:33:55 +0100, Jonathan Dowland wrote: > So far as I am aware there is still radio silence from active GNOME > packaging team members regarding this issue. No comment yet on the > patch I adapted, positive or negative; this bug (#927667) remains > at an RC severity. (Adding debian-gtk-gnome, debian-desktop and some people who might have useful input to Cc) In case anyone else in the GNOME team has got the wrong idea from my involvement in #927667: I don't think I am the right person to make a decision on this. So if GNOME team members are waiting for me to either make an upload changing the default back to X11, or veto such an upload: don't wait for that, it is unlikely to happen (unless the team cannot make a decision and punts this to the technical committee, but I hope we don't have to resort to that). I would very much appreciate input from the rest of the team, particularly: - Laurent: I know you've had strong opinions about using Wayland for GNOME. Do you feel strongly that Debian should be defaulting to Wayland? Are there any reasons for that default that are missing from my attempt to summarize earlier on the bug? - Ubuntu GNOME team: which recent Ubuntu versions, if any, are using Wayland for their GNOME-based desktop? I've left some comments on https://salsa.debian.org/gnome-team/gdm/merge_requests/8 regarding the technical side of the proposed change. Thanks, smcv
Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop
Jonathan Dowland writes: > So far as I am aware there is still radio silence from active GNOME > packaging team members regarding this issue. No comment yet on the > patch I adapted, positive or negative; this bug (#927667) remains > at an RC severity. > > I've not yet read all the thread that Samuel linked to[1] but it looks > like it leans in favour of preserving the current default (xorg). > > I'm copying -release team to see if they have any (new) opinions on > the matter. Otherwise I guess it's up to someone to prepare an NMU > upload, which I will *try* to look at in the next few days, but can't > make any guarantees. I'm just a GNOME user, but from gdm3's changelog the default was switched to Wayland in July 2017 (or August 2017 for unstable). I myself only noticed the switch after reading it happened somewhere on the internet shortly after it happened. Switching the default back two weeks before the release seems too late for me. The largest issue seems to be accessibility, but as far as I understand we already recommend a different desktop environment for that. I don't think that warrants changes that would only see very little testing by now :-/ Ansgar
Processed: bind9: CVE-2019-6471: A race condition when discarding malformed packets can cause BIND to exit with an assertion failure
Processing control commands: > clone -1 -2 Bug #930746 [src:bind9] bind9: CVE-2019-6471: A race condition when discarding malformed packets can cause BIND to exit with an assertion failure Bug 930746 cloned as bug 930747 > reassign -2 src:bind 1:9.13.3-1 Bug #930747 [src:bind9] bind9: CVE-2019-6471: A race condition when discarding malformed packets can cause BIND to exit with an assertion failure Bug reassigned from package 'src:bind9' to 'src:bind'. No longer marked as found in versions bind9/1:9.11.5.P4+dfsg-5. Ignoring request to alter fixed versions of bug #930747 to the same values previously set Bug #930747 [src:bind] bind9: CVE-2019-6471: A race condition when discarding malformed packets can cause BIND to exit with an assertion failure Marked as found in versions bind/1:9.13.3-1. > retitle -2 bind: CVE-2019-6471: A race condition when discarding malformed > packets can cause BIND to exit with an assertion failure Bug #930747 [src:bind] bind9: CVE-2019-6471: A race condition when discarding malformed packets can cause BIND to exit with an assertion failure Changed Bug title to 'bind: CVE-2019-6471: A race condition when discarding malformed packets can cause BIND to exit with an assertion failure' from 'bind9: CVE-2019-6471: A race condition when discarding malformed packets can cause BIND to exit with an assertion failure'. -- 930746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930746 930747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#930746: bind9: CVE-2019-6471: A race condition when discarding malformed packets can cause BIND to exit with an assertion failure
Source: bind9 Version: 1:9.11.5.P4+dfsg-5 Severity: grave Tags: security upstream Control: clone -1 -2 Control: reassign -2 src:bind 1:9.13.3-1 Control: retitle -2 bind: CVE-2019-6471: A race condition when discarding malformed packets can cause BIND to exit with an assertion failure Hi, The following vulnerability was published for bind9. CVE-2019-6471[0]: |A race condition when discarding malformed packets can cause BIND to |exit with an assertion failure If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-6471 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6471 [1] https://kb.isc.org/docs/cve-2019-6471 Please adjust the affected versions in the BTS as needed, I think the version back in stretch is not affected but this needs double-checking. Regards, Salvatore
Processed: Re: hkl: FTBFS: ../../hkl/ccan/generator/generator.h:23:2: error: #error Generators require coroutines
Processing control commands: > severity -1 important Bug #929720 [src:hkl] hkl: FTBFS: ../../hkl/ccan/generator/generator.h:23:2: error: #error Generators require coroutines Severity set to 'important' from 'serious' -- 929720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929720: hkl: FTBFS: ../../hkl/ccan/generator/generator.h:23:2: error: #error Generators require coroutines
Control: severity -1 important Hi Lucas, I confirm that I'm the third one who can not reproduce this issue. Can we agree that this bug is maximum of severity important (just set this - feel free to reset to serious if you have good reasons for it). Do you have any further hints how this FTBFS could be reproduced? Kind regards Andreas. -- http://fam-tille.de
Processed: Re: Bug#930671: libauthen-radius-perl: most basic usage stopped working
Processing control commands: > severity -1 serious Bug #930671 [libauthen-radius-perl] libauthen-radius-perl: most basic usage stopped working Severity set to 'serious' from 'important' -- 930671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927667: gnome: please confirm or revert choice of Wayland for default desktop
Hi Andrew So far as I am aware there is still radio silence from active GNOME packaging team members regarding this issue. No comment yet on the patch I adapted, positive or negative; this bug (#927667) remains at an RC severity. I've not yet read all the thread that Samuel linked to[1] but it looks like it leans in favour of preserving the current default (xorg). I'm copying -release team to see if they have any (new) opinions on the matter. Otherwise I guess it's up to someone to prepare an NMU upload, which I will *try* to look at in the next few days, but can't make any guarantees. Further testers of the patch on this bug would be most welcome. [1] https://lists.debian.org/debian-accessibility/2019/02/threads.html#4
Bug#929877: installation-reports: Buster installer hangs at hard disk step with arabic language
Hi, I think it is okay for those diacritics. Regards, ‐‐‐ Original Message ‐‐‐ Le mardi 18 juin 2019 22:26, Holger Wansing a écrit : > Hi, > > Samuel Thibault sthiba...@debian.org wrote: > > > Hello, > > Holger Wansing, le mar. 04 juin 2019 20:59:12 +, a ecrit: > > > > > Am Sonntag, 2. Juni 2019 schrieb Holger Wansing: > > > > > > > Am Sonntag, 2. Juni 2019 schrieb Samuel Thibault: > > > > > > > > > ButterflyOfFire, le dim. 02 juin 2019 15:43:41 +, a ecrit: > > > > > > > > > > > > > "لاحقاً" > > > > > > > > > > > > This word means "later" and can be replaced by "لاحقا". > > > > > > > > > > That avoids the issue here indeed. I however see it used in various > > > > > > > > Hmm. > > > > There has been no changing in the ar.po of partman-auto > > > > for 3 years now (JFTR), thus the real problem seems to be > > > > sitting somewhere else ... > > > > > > How should we proceed here? > > > Since we are late in the freeze, and it's most probably not that > > > easy to find out what happened and what the real issue is: > > > should we go with the "work-around" proposed by > > > Butterflyoffire and confirmed to fix the issue by Samuel? > > > > Personally, I don't think I'll have the time to debug what is actually > > happening inside gtk until the release, so even if it's ugly, I guess > > the browntape fix is the least worst I can come up with. > > That looks fair. > I have committed the proposed fix now. > > @butterflyoffire: could you please take a look at > https://salsa.debian.org/installer-team/d-i/commit/fa17b7afffb2ee4888a371efa4153c5c075915e7 > to double-check if the fix is fine by you? > Thanks! > > Holger > > > - > > Holger Wansing hwans...@mailbox.org > PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#930356: CVE-2019-12760
Hi Piotr > Please see https://bugzilla.redhat.com/show_bug.cgi?id=1718212 > > Patch is at https://gist.github.com/dhondta/f71ae7e5c4234f8edfd2f12503a5dcc7 I know you are usually pretty quick in solving serious issues. I tried to check the issue and think the link provided for a patch is just pointing to a proof of concept exploit. When reading the discussion here https://github.com/davidhalter/parso/issues/75 I understand that it is not fixed but the authors do not consider the issue serious. Could you please give some comment from an insiders point of view (which I'm not). I'm just caring since several Debian Science dependencies are about to be removed from testing due to this bug. Kind regards Andreas. PS: Is there any reason why this package is not on Salsa and not team maintained? -- http://fam-tille.de
Bug#929129: [Pkg-xen-devel] Bug#929129: closed by Hans van Kranenburg (Bug#929129: fixed in xen 4.11.1+92-g6c33308a8d-1)
On 6/19/19 4:43 PM, Wiebe Cazemier wrote: > This is an update to the unstable release. What is one running Debian > stable (9), with Xen Hypervisor 4.8, to do? This is not meant as a middle finger to users of stable. All of the bug numbers will be closed twice, also by the 4.8 upload, which also has to mention them. This is confusing, however the automated behaviour after uploading any of them is to close the bug with that report. At least the 4.11 is out now, last thing I heard about 4.8 was that there are issues compiling the current 4.8-stable upstream branch in Stretch, and that's quite an important prerequisite for continuing. :| Ian needs to work on that. I will see if I can manipulate them a bit. All the other ones mentioned in the changelog should also have the info that it's found in current version in stable attached to them, so that the version graph shows both. Hans
Bug#929129: closed by Hans van Kranenburg (Bug#929129: fixed in xen 4.11.1+92-g6c33308a8d-1)
This is an update to the unstable release. What is one running Debian stable (9), with Xen Hypervisor 4.8, to do?
Bug#930722: arc, arcanist: Both ship arc binary
Le 19/06/2019 à 12:14, Julian Andres Klode a écrit : Package: arc,arcanist Severity: serious arc: /usr/bin/arc arcanist: /usr/bin/arc One of them needs to be renamed, or both. Or change the Debian policy as it is a waste of our time... and no gain for the user. ;) Sylvestre
Bug#929129: marked as done (Xen Hypervisor security update for Intel MDS - XSA 297)
Your message dated Wed, 19 Jun 2019 13:20:09 + with message-id and subject line Bug#929129: fixed in xen 4.11.1+92-g6c33308a8d-1 has caused the Debian Bug report #929129, regarding Xen Hypervisor security update for Intel MDS - XSA 297 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 929129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xen-hypervisor-4.8-amd64 Version: 4.8.5+shim4.10.2+xsa282-1+deb9u11 All Xen Hypervisor packages also need patches against the Intel MDS bug, same as https://www.debian.org/security/2019/dsa-. http://xenbits.xen.org/xsa/advisory-297.html --- End Message --- --- Begin Message --- Source: xen Source-Version: 4.11.1+92-g6c33308a8d-1 We believe that the bug you reported is fixed in the latest version of xen, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 929...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hans van Kranenburg (supplier of updated xen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 18 Jun 2019 09:50:19 +0200 Source: xen Binary: xenstore-utils xen-utils-common xen-hypervisor-common xen-doc xen-utils-4.11 xen-hypervisor-4.11-amd64 xen-system-amd64 xen-hypervisor-4.11-arm64 xen-system-arm64 xen-hypervisor-4.11-armhf xen-system-armhf libxen-dev libxenmisc4.11 libxencall1 libxendevicemodel1 libxenevtchn1 libxenforeignmemory1 libxengnttab1 libxenstore3.0 libxentoolcore1 libxentoollog1 Architecture: all amd64 source Version: 4.11.1+92-g6c33308a8d-1 Distribution: unstable Urgency: high Maintainer: Debian Xen Team Changed-By: Hans van Kranenburg Closes: 929129 929991 929992 929993 929994 929995 929996 929998 92 930001 Description: libxen-dev - Public headers and libs for Xen libxencall1 - Xen runtime library - libxencall libxendevicemodel1 - Xen runtime libraries - libxendevicemodel libxenevtchn1 - Xen runtime libraries - libxenevtchn libxenforeignmemory1 - Xen runtime libraries - libxenforeignmemory libxengnttab1 - Xen runtime libraries - libxengnttab libxenmisc4.11 - Xen runtime libraries - miscellaneous, versioned ABI libxenstore3.0 - Xen runtime libraries - libxenstore libxentoolcore1 - Xen runtime libraries - libxentoolcore libxentoollog1 - Xen runtime libraries - libxentoollog xen-doc- XEN documentation xen-hypervisor-4.11-amd64 - Xen Hypervisor on AMD64 xen-hypervisor-4.11-arm64 - Xen Hypervisor on ARM64 xen-hypervisor-4.11-armhf - Xen Hypervisor on ARMHF xen-hypervisor-common - Xen Hypervisor - common files xen-system-amd64 - Xen System on AMD64 (metapackage) xen-system-arm64 - Xen System on ARM64 (metapackage) xen-system-armhf - Xen System on ARMHF (metapackage) xen-utils-4.11 - XEN administrative tools xen-utils-common - Xen administrative tools - common files xenstore-utils - Xenstore command line utilities for Xen Changes: xen (4.11.1+92-g6c33308a8d-1) unstable; urgency=high . * Update to new upstream version 4.11.1+92-g6c33308a8d, which also contains the following security fixes: - Fix: grant table transfer issues on large hosts XSA-284 (no CVE yet) (Closes: #929991) - Fix: race with pass-through device hotplug XSA-285 (no CVE yet) (Closes: #929998) - Fix: x86: steal_page violates page_struct access discipline XSA-287 (no CVE yet) (Closes: #930001) - Fix: x86: Inconsistent PV IOMMU discipline XSA-288 (no CVE yet) (Closes: #929994) - Fix: missing preemption in x86 PV page table unvalidation XSA-290 (no CVE yet) (Closes: #929996) - Fix: x86/PV: page type reference counting issue with failed IOMMU update XSA-291 (no CVE yet) (Closes: #929995) - Fix: x86: insufficient TLB flushing when using PCID XSA-292 (no CVE yet) (Closes: #929993) - Fix: x86: PV kernel context switch corruption XSA-293 (no CVE yet) (Closes: #92) - Fix: x86 shadow: Insufficient TLB flushing when using PCID XSA-294 (no CVE yet) (Closes: #929992) - Fix: Microarchitectural Data Sampling speculative side channel XSA-297
Bug#930733: evolution: Can't open evolution
Package: evolution
Version: 3.32.2-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When i try to open evolution i have this error :
libEGL warning: DRI2: failed to open i965 (search paths /usr/lib/x86_64-linux-
gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open swrast (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open swrast (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open i965 (search paths /usr/lib/x86_64-linux-
gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open swrast (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open swrast (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open i965 (search paths /usr/lib/x86_64-linux-
gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open swrast (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open swrast (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open i965 (search paths /usr/lib/x86_64-linux-
gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open swrast (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open swrast (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
Failed to initialize gtk+: Impossible d'initialiser le moteur Clutter : aucun
pilote disponible.
-- System Information:
Debian Release: buster/sid
APT prefers stable
APT policy: (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.0.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages evolution depends on:
ii dbus 1.12.12-1
ii evolution-common 3.32.2-1
ii evolution-data-server 3.32.2-2
ii libc6 2.28-8
ii libcamel-1.2-623.32.2-2
ii libclutter-gtk-1.0-0 1.8.4-4
ii libecal-1.2-19 3.32.2-2
ii libedataserver-1.2-24 3.32.2-2
ii libevolution 3.32.2-1
ii libglib2.0-0 2.58.3-1
ii libgtk-3-0 3.24.5-1
ii libical3 3.0.4-3
ii libnotify4 0.7.7-4
ii libsoup2.4-1 2.64.2-2
ii libwebkit2gtk-4.0-37 2.22.7-1
ii libxml22.9.4+dfsg1-7+b3
ii psmisc 23.2-1
Versions of packages evolution recommends:
ii evolution-plugin-bogofilter 3.32.2-1
ii evolution-plugin-pstimport 3.32.2-1
ii evolution-plugins3.32.2-1
ii yelp 3.31.90-1
Versions of packages evolution suggests:
pn evolution-ews
pn evolution-plugins-experimental
ii gnupg 2.2.12-1
ii network-manager 1.14.6-2
-- no debconf information
Bug#930368: marked as done (gatb-core: FTBFS due to inaccurate symbols file)
Your message dated Wed, 19 Jun 2019 11:18:31 + with message-id and subject line Bug#930368: fixed in gatb-core 1.4.1+git20181225.44d5a44+dfsg-3 has caused the Debian Bug report #930368, regarding gatb-core: FTBFS due to inaccurate symbols file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 930368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gatb-core Version: 1.4.1+git20181225.44d5a44+dfsg-2 Severity: serious Justification: FTBFS -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, During a rebuild of gatb-core for unstable on amd64 I experienced a FTBFS at the dh_makeshlibs step: dh_makeshlibs -O--sourcedirectory=gatb-core dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libgatbcore2/DEBIAN/symbols doesn't match completely debian/libgatbcore2.symbols.amd64 - --- debian/libgatbcore2.symbols.amd64 (libgatbcore2_1.4.1+git20181225.44d5a44+dfsg-2_amd64) +++ dpkg-gensymbolsErQvax 2019-06-11 09:56:28.965481025 + @@ -8997,7 +8997,7 @@ _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi1EEEjjjEESaIS7_EE12emplace_backIJS7_EEEvDpOT_@Base 1.4.1+git20181225.44d5a44+dfsg _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi1EEEjjjEESaIS7_EE17_M_realloc_insertIJS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base 1.4.1 _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi1EEEjjjEESaIS7_EE7reserveEm@Base 1.4.1 - - _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi2EEEjjjEESaIS7_EE12emplace_backIJS7_EEEvDpOT_@Base 1.4.1+git20181225.44d5a44+dfsg +#MISSING: 1.4.1+git20181225.44d5a44+dfsg-2# _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi2EEEjjjEESaIS7_EE12emplace_backIJS7_EEEvDpOT_@Base 1.4.1+git20181225.44d5a44+dfsg _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi2EEEjjjEESaIS7_EE17_M_realloc_insertIJS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base 1.4.1 _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi2EEEjjjEESaIS7_EE7reserveEm@Base 1.4.1 _ZNSt6vectorISt5tupleIJjN4gatb4core5tools4math8LargeIntILi3EEEjjjEESaIS7_EE17_M_realloc_insertIJS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base 1.4.1 @@ -9007,7 +9007,7 @@ _ZNSt6vectorISt5tupleIJmiEESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base 1.4.1 _ZNSt6vectorISt5tupleIJmiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaIS7_EE17_M_realloc_insertIJS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base 1.4.1 _ZNSt6vectorISt6threadSaIS0_EE17_M_realloc_insertIJZN10ThreadPoolC4EmEUlvE_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base 1.4.1 - - _ZNSt6vectorIbSaIbEE13_M_initializeEm@Base 1.4.1+git20181225.44d5a44+dfsg +#MISSING: 1.4.1+git20181225.44d5a44+dfsg-2# _ZNSt6vectorIbSaIbEE13_M_initializeEm@Base 1.4.1+git20181225.44d5a44+dfsg _ZNSt6vectorIbSaIbEE13_M_insert_auxESt13_Bit_iteratorb@Base 1.4.1 _ZNSt6vectorIbSaIbEE13_M_reallocateEm@Base 1.4.1 _ZNSt6vectorIbSaIbEE14_M_fill_insertESt13_Bit_iteratormb@Base 1.4.1 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:10: binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Thanks, _g. - -- System Information: Debian Release: buster/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlz/ttsACgkQ7+hsbH/+ z4P/bgf/aI8Kn2N0XrowNHz05+Hw9zTryiLdxmSgqs3HYJwq+bUjzbpZQTbwFb+U Fgosu7yUAzPQSc0XeWAHbE9zosOVH5pqsvIVCvOOcwIrMJ1w28arh0YtsVTNIs71 4Cn1/x22ZZNHe6rbbb1Kzf0gf1JBMm6riKVqXDh1iJf0S4a1O63w1O6gNXGvXPsj cwfqbP6En5Wmqys51FH3ZTAWK/ZF/3LPAyGlxgrK7KiFpub1ckph0WiKlaRFOYAv uzG8Wy7MeVBaG9fpUd/oF+qQiUM+OrHWCXZLLuWKj7UCdCfRgzu3D+t7R5NlTFVr Rh/mAr/U0rbFG7nDa8g0wOCQNrGBIw== =2Gnd -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: gatb-core Source-Version: 1.4.1+git20181225.44d5a44+dfsg-3 We believe that the bug you reported is fixed in the latest version of gatb-core, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for
Bug#927308: marked as done (mysql-5.7: Security fixes from the April 2019 CPU)
Your message dated Wed, 19 Jun 2019 11:08:21 + with message-id and subject line Bug#927308: fixed in mysql-5.7 5.7.26-1 has caused the Debian Bug report #927308, regarding mysql-5.7: Security fixes from the April 2019 CPU to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 927308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mysql-5.7 Version: 5.7.25-1 Severity: grave Tags: security upstream Hi See https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html#AppendixMSQL for a list of CVEs affecting src:mysql-5.7. Regards, Salvatore --- End Message --- --- Begin Message --- Source: mysql-5.7 Source-Version: 5.7.26-1 We believe that the bug you reported is fixed in the latest version of mysql-5.7, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 927...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lars Tangvald (supplier of updated mysql-5.7 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 14 Jun 2019 07:59:19 +0200 Source: mysql-5.7 Binary: libmysqlclient20 libmysqld-dev libmysqlclient-dev mysql-client-core-5.7 mysql-client-5.7 mysql-server-core-5.7 mysql-server-5.7 mysql-server mysql-client mysql-testsuite mysql-testsuite-5.7 mysql-source-5.7 Architecture: source Version: 5.7.26-1 Distribution: unstable Urgency: high Maintainer: Debian MySQL Maintainers Changed-By: Lars Tangvald Description: libmysqlclient-dev - MySQL database development files libmysqlclient20 - MySQL database client library libmysqld-dev - MySQL embedded database development files mysql-client - MySQL database client (metapackage depending on the latest versio mysql-client-5.7 - MySQL database client binaries mysql-client-core-5.7 - MySQL database core client binaries mysql-server - MySQL database server (metapackage depending on the latest versio mysql-server-5.7 - MySQL database server binaries and system database setup mysql-server-core-5.7 - MySQL database server binaries mysql-source-5.7 - MySQL source mysql-testsuite - MySQL regression tests mysql-testsuite-5.7 - MySQL 5.7 testsuite Closes: 927308 Changes: mysql-5.7 (5.7.26-1) unstable; urgency=high (security fixes) . * Imported upstream version 5.7.26 to fix security issues: - https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html - CVE-2019-1559 CVE-2019-2566 CVE-2019-2581 CVE-2019-2592 - CVE-2019-2614 CVE-2019-2627 CVE-2019-2628 CVE-2019-2632 - CVE-2019-2683 CVE-2018-3123 (Closes: #927308) * Disable unstable test xa_prepared_binlog_off for dep8 * d/patches: Remove fix-mysqldump-test-dates The issue has been resolved upstream * d/control: Add build-dep on pkg-config to fix FTBFS Checksums-Sha1: 6d8c865e5301a2d626d8582301c00d046b2de64e 3241 mysql-5.7_5.7.26-1.dsc d92843355a8af65d45305a888eeca4a28ba90c32 51098338 mysql-5.7_5.7.26.orig.tar.gz 77f294a36e7ca364c24414cdbeb85ba538feb8db 156212 mysql-5.7_5.7.26-1.debian.tar.xz Checksums-Sha256: b5385257f0d9e67b971289667ccbf5b8b3e7120e88e7502065f1c385a35ab1fe 3241 mysql-5.7_5.7.26-1.dsc effca6d3aceebc286a9fb046257330d125cc2f4def87081c286bfc4df3d974d1 51098338 mysql-5.7_5.7.26.orig.tar.gz 208bc7455bf0048e791910208bc3f061baa8e110dc6209fe2446ad96b35a8158 156212 mysql-5.7_5.7.26-1.debian.tar.xz Files: 2772441b03dd79dcce625e5c1306995d 3241 database optional mysql-5.7_5.7.26-1.dsc 0fb4db48959b0e05a7dba0bbfbb4f8ca 51098338 database optional mysql-5.7_5.7.26.orig.tar.gz f39686200ad6a31b5ae70d3256c8200c 156212 database optional mysql-5.7_5.7.26-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJdCg/VAAoJEOVkucJ1vdUuo3gQAI5jIgvrq1km5rOUaw6x/LA8 jNs0CKzLbQW9qxFI+4lqleANPgDF9FwqENOFKr4eNUdet5cbd2UL6fMAsJFp2eys aXrxASNMHEUSXCWFkP5ceNDus68rRpn/mAlvhQTUSAf6q7l6aMNnrhhcxK5G2eh5 X4CUN20Iu7QUrT+Ssmy3dLScsMXbVm/tGNNg7TM+ZPH5x9af73cnJlMkEiQOxxQ/ XUEJFN5SrEV008ntK3Tz3W5ILV6dlkaGlB3Q22J1K5YUiJVpYlvCQvW7a5MqJPpx aG97cFSTtg3VWu83xpnWWABuoV7DgzlHaDXDClYw4zbUxMsl3pyRs6ioDPVM9KZj
Bug#930722: arc, arcanist: Both ship arc binary
Package: arc,arcanist Severity: serious arc: /usr/bin/arc arcanist: /usr/bin/arc One of them needs to be renamed, or both. -- System Information: Debian Release: buster/sid APT prefers eoan APT policy: (991, 'eoan'), (500, 'eoan'), (500, 'cosmic-security') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.0-15-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#930682: debian-xcontrol: Remove from archive?
severity 930682 normal reassign 930682 ftp.debian.org retitle 930682 Please remove debian-xcontrol thanks Hi, On Tue, Jun 18, 2019 at 01:35:48PM +0200, Julian Andres Klode wrote: > Package: debian-xcontrol > Version: 0.0.4-1.1 > Severity: serious > There do not seem to be any users of debian-xcontrol left, > and the last update was 9 years ago, so time to let it go? Yes, I thought I had sent a request for its removal years ago. Simon
Processed: tagging 930682
Processing commands for cont...@bugs.debian.org: > tags 930682 + sid buster Bug #930682 [debian-xcontrol] debian-xcontrol: Remove from archive? Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 930682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 930463 in mednafen/1.22.1+dfsg-2~deb10u1, fixed 930464 in mednafen/1.22.1+dfsg-2~deb10u1
Processing commands for cont...@bugs.debian.org:
> fixed 930463 mednafen/1.22.1+dfsg-2~deb10u1
Bug #930463 {Done: Stephen Kitt } [mednafen] mednafen:
potential unchecked memory access in the Lynx emulator
The source mednafen and version 1.22.1+dfsg-2~deb10u1 do not appear to match
any binary packages
Marked as fixed in versions mednafen/1.22.1+dfsg-2~deb10u1.
> fixed 930464 mednafen/1.22.1+dfsg-2~deb10u1
Bug #930464 {Done: Stephen Kitt } [mednafen] mednafen: PS1
emulation regression
The source mednafen and version 1.22.1+dfsg-2~deb10u1 do not appear to match
any binary packages
Marked as fixed in versions mednafen/1.22.1+dfsg-2~deb10u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
930463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930463
930464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
