Bug#1071197: ninja-build: 1.12 breaks chromium build

Control: reassign -1 src:chromium On 5/16/24 11:49, Felix Geyer wrote: On 15.05.24 23:49, Andres Salomon wrote: Package: ninja-build Version: 1.12.1-1 Severity: serious Tags: affects -1 chromium X-Debbugs-Cc: Andres Salomon Chromium in unstable breaks with ninja-build 1.12. See here

Bug#1071197: ninja-build: 1.12 breaks chromium build

Damn, now I can't reproduce it in my chroot. Oh well, I did a giveback on chromium just in case this was a temporary problem.. I'll see in a few hours what happens. On Wed, 15 May 2024 17:49:18 -0400 Andres Salomon wrote: Package: ninja-build Version: 1.12.1-1 Severity: serious Tags

Bug#1071197: ninja-build: 1.12 breaks chromium build

Package: ninja-build Version: 1.12.1-1 Severity: serious Tags: affects -1 chromium X-Debbugs-Cc: Andres Salomon Chromium in unstable breaks with ninja-build 1.12. See here for example, where the same chromium version (124.0.6367.201-1) built fine on architectures where older ninja-build

Bug#1070266: nmu: chromium_124.0.6367.118-1

Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: serious Hello, Snappy 1.2.0-1 was uploaded with broken symbols (see https://bugs.debian.org/1070217). This is fixed in snappy 1.2.0-2, but chromium in sid had already built against the broken

Bug#1070227: Fails to start with undefined symbol

Thanks. This is a duplicate (https://bugs.debian.org/1070217), but I'm leaving it open to ensure that chromium doesn't accidentally migrate to trixie while built against a broken libsnappy. And as a reminder that we'll probably need a binNMU once snappy is fixed, unless upstream has a new

Bug#1068540: chromium: depends on pre-t64 library

On 4/7/24 04:28, Sebastian Ramacher wrote: Source: chromium Version: 123.0.6312.105-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org chromium has a hard-coded dependency on libgtk-3-0 which changed the package name as part of the time_t transition. Please update the dependency accordingly

Bug#1066910: chromium: downloads non-free component libchromescreenai.so without asking

Control: tags -1 pending On Fri, 15 Mar 2024 13:33:47 -0400 Andres Salomon wrote: Control: tags -1 bookworm trixie sid On 3/15/24 06:57, Helmut Grohne wrote: > Package: chromium > Version: 122.0.6261.128-1 > Severity: serious > > In recent versions, chromium started dow

Bug#1066910: chromium: downloads non-free component libchromescreenai.so without asking

Control: tags -1 bookworm trixie sid On 3/15/24 06:57, Helmut Grohne wrote: Package: chromium Version: 122.0.6261.128-1 Severity: serious In recent versions, chromium started downloading a file ~/.config/chromium/screen_ai/*/libchromescreenai.so. Evidently, the source of this shared object is

Bug#1063461: Bug#1065283: lsof: diff for NMU version 4.95.0-1.1

Thanks! I'd planned to wait until the t64 transition was complete before doing a new upstream release of lsof, but a NMU to fix this FTBFS issue is good. On 3/10/24 07:45, Sebastian Ramacher wrote: Dear maintainer, I've prepared an NMU for lsof (versioned as 4.95.0-1.1) and uploaded it to

Bug#1053142: freetype proposed update breaks chromium

On Fri, Sep 29 2023 at 10:23:25 PM +10:00:00, Hugh McMaster wrote: Control: reassign 1053142 libfreetype6 2.12.1+dfsg-5+deb12u1 On Fri, 29 Sep 2023 10:37:22 +0200 Cord Beermann wrote: Hi, just wanted to give you a heads up on

Bug#1051787: Subject: CVE-2023-4863: Heap buffer overflow in WebP

, Andres Salomon wrote: clone 1051787 -1 reassign -1 libwebp thanks This bug's actually in libwebp. Unfortunately we're still embedding it in chromium, so we likely need to fix both chromium *and* libwebp in debian. There hasn't been a libwebp release yet, but the two relevant git commits

Bug#1051787: Subject: CVE-2023-4863: Heap buffer overflow in WebP

clone 1051787 -1 reassign -1 libwebp thanks This bug's actually in libwebp. Unfortunately we're still embedding it in chromium, so we likely need to fix both chromium *and* libwebp in debian. There hasn't been a libwebp release yet, but the two relevant git commits are

Bug#1051355: Processed: your mail

On Mon, Sep 11 2023 at 03:27:30 PM -03:00:00, Leandro Cunha wrote: On Mon, Sep 11, 2023 at 4:07 AM Andres Salomon <mailto:dilin...@queued.net>> wrote: So apparently it's already fixed in sid and trixie: <https://tracker.debian.org/news/1454349/accepted-llvm-toolchain-16-116

Bug#1051355: Processed: your mail

so you can give it a test build on ppc. On Mon, Sep 11 2023 at 12:37:39 AM -05:00:00, Timothy Pearson wrote: For 16 to work we'll need the Debian clang team to include this patchset: <https://reviews.llvm.org/D158066> Any chance of that happening? - Original Message - From: "An

Bug#1051355: Processed: your mail

PM -03:00:00, Leandro Cunha wrote: Hi, Em dom., 10 de set. de 2023 15:01, Andres Salomon mailto:dilin...@queued.net>> escreveu: Unfortunately 117 *also* segfaults on sid. I'm tempted to try a newer clang, but probably not 15 since debian's planning to remove it. 16, I guess? Arch i

Bug#1051355: Processed: your mail

Unfortunately 117 *also* segfaults on sid. I'm tempted to try a newer clang, but probably not 15 since debian's planning to remove it. 16, I guess? On Fri, Sep 8 2023 at 05:36:17 PM -03:00:00, Leandro Cunha wrote: Hi, On Fri, Sep 8, 2023 at 4:39 PM Andres Salomon <mailto:di

Bug#1051355: Processed: your mail

On Fri, Sep 8 2023 at 03:31:37 PM -03:00:00, Leandro Cunha wrote: Hi, On Fri, Sep 8, 2023 at 10:03 AM Debian Bug Tracking System mailto:ow...@bugs.debian.org>> wrote: Processing commands for cont...@bugs.debian.org : > affects 1051355 phpsysinfo

Bug#1051355: chromium: Segmentation fault

Downgrading to 116.0.5845.140-1 worked, so on a hunch I rebuilt .140-1 against current sid and.. it crashes immediately the same way. So something in sid that we depend on changed between 8/31 and 9/6 that is causing this crash. Unfortunately no useful backtrace, so I'm guessing something

Bug#1024216: mkchromecast: please change dependency from youtube-dl to yt-dlp

Control: tags -1 - bookworm On Tue, Jul 11 2023 at 12:45:13 PM +03:00:00, Adrian Bunk wrote: Control: tags -1 bookworm trixie sid On Wed, Jan 04, 2023 at 01:42:22AM -0500, Andres Salomon wrote: On Wed, 16 Nov 2022 00:58:30 -0500 Andres Salomon mailto:dilin...@queued.net>>

Bug#1036272: youtube-dl - Should this be released with Bookworm?

On Thu, 18 May 2023 12:56:22 +0200 Bastian Blank wrote: > Source: youtube-dl > Version: 2021.12.17-2 > Severity: serious > > We have a maintained and uptodate fork of this package in the archive > and the release: yt-dlp. Do we really need to release this package in a > not so usable state?

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

On Sat, 11 Mar 2023 11:04:15 + James Addison wrote: > Package: nodejs > Followup-For: Bug #1030284 > X-Debbugs-Cc: t...@debian.org > > Guidance received from the V8 project (a vendored dependency in the upstream > NodeJS codebase) on the v8-dev mailing list is, in summary/interpretation:

Bug#1031114: fwd

Major releases are monthly, so v111 will be uploaded in a month, and v112 the month after that. Versions for stable are handled through security uploads, so 110 is currently in bullseye-security and sid (but not yet bookworm due to the migration issues). The ci tests don't really affect

Bug#1031114: fwd

On Sun, 12 Feb 2023 11:41:17 +0100 William Desportes wrote: > Control: tags -1 + pending > Control: forwarded -1 https://salsa.debian.org/js-team/jquery-timepicker/-/commit/21f37b5345ccd800507ca3293d12de70ccee5437 > > It seems like this selenium issue was right:

Bug#1031114: jquery-timepicker: autopkgtest failures

On Sun, Feb 12 2023 at 02:42:12 AM +0100, William Desportes wrote: I think this has nothing to do with my package :) selenium.common.exceptions.WebDriverException: Message: unknown error: unable to discover open pages And this should be enough to reproduce it (deps: python3-selenium,

Bug#1031114: jquery-timepicker: autopkgtest failures

Source: jquery-timepicker Control: found -1 jquery-timepicker/1.6.3-3 Control: affects -1 chromium Severity: serious Tags: sid bookworm It would appear that jquery-timepicker's autopkgtests are failing with chromium. You can see some of the failures here:

Bug#1030160: chromium: FTBFS on arm64/armhf in bullseye-security (V4L issues)

On Thu, Feb 2 2023 at 02:14:42 PM +, "Steinberg, Benjamin" wrote: On Tue, 31 Jan 2023 13:35:49 -0500 Andres Salomon wrote: > Thanks! I forgot that it can only be enabled on sid when I merged the > new release into bullseye. This will get fixed in the next se

Bug#1029845: harfbuzz: non-distributable font included in source

On Wed, Feb 1 2023 at 10:09:15 AM +0100, Emilio Pozuelo Monfort wrote: On 01/02/2023 09:47, Andres Salomon wrote: Hi Security Team & Jeremy, I had originally planned to ask the release team about fixing #1029845 (the bug below) in bullseye via t-p-u. However, it would ap

Bug#1029845: harfbuzz: non-distributable font included in source

ased on what's decided, I can adjust it and do a MR to whatever your preferred branch name is. On Sat, 28 Jan 2023 13:05:01 -0500 Andres Salomon wrote: > Source: harfbuzz > Severity: serious > Version: 6.0.0-1 > Justification: Policy 2.1 > > Harfbuzz includes a nondistribu

Bug#1030160: chromium: FTBFS on arm64/armhf in bullseye-security (V4L issues)

On Tue, 31 Jan 2023 17:53:12 + "Adam D. Barratt" wrote: > Source: chromium > Version: 109.0.5414.119-1~deb11u1 > Severity: serious > Tags: FTBFS > X-Debbugs-CC: t...@security.debian.org > Control: affects -1 + security.debian.org > Control: affects -1 + release.debian.org > > Hi, > > The

Bug#1029845: harfbuzz: non-distributable font included in source

Source: harfbuzz Severity: serious Version: 6.0.0-1 Justification: Policy 2.1 Harfbuzz includes a nondistributable font in its test suite. I thought it was just in sid/bookworm, but it's apparently also in bullseye as well. In bullseye:

Bug#1029153: virtualbox: CVE-2023-21884 CVE-2023-21885 CVE-2023-21886 CVE-2023-21889 CVE-2023-21898 CVE-2023-21899

On Wed, 18 Jan 2023 17:28:47 +0100 =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= wrote: > Source: virtualbox > X-Debbugs-CC: t...@security.debian.org > Severity: grave > Tags: security > > Hi, > > The following vulnerabilities were published for virtualbox. > > Fixed in 7.0.6 > Also fixed in 6.1.42.

Bug#1028567: acetoneiso: should not download and run random binaries off the internet

Package: acetoneiso Version: 2.4-3 Severity: serious Tags: security While looking through the code to see about replacing youtube-dl (#1024231), I noticed the following in acetoneiso/sources/utube.h's metacafe() function: if (system ("cd $HOME/.acetoneiso/;wget

Bug#1004441: unblocking chromium?

On Fri, Jan 6 2023 at 11:36:02 AM +0200, Adrian Bunk wrote: On Fri, Jan 06, 2023 at 10:18:16AM +0100, Moritz Muehlenhoff wrote: ... We might consider to set some expectation for oldstable-security, though e.g state that oldstable-security updates stop three months after the release of

Bug#1025394: clang-14: undefined symbol errors on chromium with basic_string

Source: llvm-toolchain-14 Version: 1:14.0.6-8 Severity: serious Tags: ftbfs fixed-upstream patch sid Justification: fails to build from source When building chromium, I hit the following: ld.lld: error: undefined symbol: void std::__cxx11::basic_string, std::allocator >::_M_construct(char16_t

Bug#1016254: lomiri-url-dispatcher: FTBFS: overlay-tracker-mir.cpp:95:45: error: variable ‘std::array urls’ has initializer but incomplete type

Control: tags -1 patch Here's a fix for this one, which is blocking geary from bookworm. I've also a MR upstream, with the MR link in the patch. Description: Fix build failure from missing header in gcc 12.1.0 (#1016254) Author: Andres Salomon Forwarded: https://gitlab.com/ubports

Bug#1011914: lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1

severity 1011914 minor tags 1011914 = wontfix retitle 1011914 lsof: FTBFS during unit tests when hostname cannot be resolved forward 1011914 https://github.com/lsof-org/lsof/issues/61 thanks On Sun, Jun 5, 2022 at 11:13, Lucas Nussbaum wrote: Hi Andres, [...] This is not related to the

Bug#1011914: lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1

dpkg-buildpackage -us -uc -ui dpkg-buildpackage: info: source package lsof dpkg-buildpackage: info: source version 4.95.0-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Andres Salomon dpkg-source --before-build . dpkg-buildpackage: info: host ar

Bug#1010407: chromium: Chromium immediately crashes on Illegal instruction on Buster i386

Severity: normal Control: retitle 1010407 chromium: does not support older CPUs without SSE3 instructions Tags: wontfix Thanks for the report! It looks like chromium officially dropped older CPU support: https://www.tomshardware.com/news/chrome-stops-working-on-old-processors There's

Bug#1009359: New security upgrade prevent Chromium from starting

Hm, good question. What I'd start doing is looking at the ~/.cache/chromium and ~/.config/chromium snapshots, making copies, and then trying to run chromium with random stuff deleted. For example, on my system I have ~/.cache/chromium/Profile 1/old_Cache_000 and ~/.cache/chromium/System

Bug#1009359: New security upgrade prevent Chromium from starting

other one makes it crash. So I guess one of the tab is triggering the error. I will try to isolate it and get more debug info. If you have commands to do that let me know. Thanks LeTic --- Original Message --- On Tuesday, April 12th, 2022 at 22:28, Andres Salomon dilin...@queued.net wrot

Bug#1009359: New security upgrade prevent Chromium from starting

On 4/12/22 08:02, Anthony Callegaro wrote: Hi guys, I tried a few additional things to try to sort it out : - downgraded to my latest upgrade date : cat /etc/apt/sources.list.d/snapshot.list deb [check-valid-until=no] http://snapshot.debian.org/archive/debian-security/20220404T151623Z/

Bug#1008080: Some sites do not work

Control: severity -1 normal On Tue, 22 Mar 2022 08:15:27 +0100 =?utf-8?q?St=C3=A9phane_Glondu?= wrote: > Package: chromium > Version: 99.0.4844.74-1 > Severity: grave > > Dear Maintainer, > > On two different, up-to-date Debian testing machines, at least the > following sites: > >

Bug#1007983: node-puppeteer: broken autopkgtest keeping chromium from migrating to testing

On Sat, 19 Mar 2022 17:44:02 -0400 Andres Salomon wrote: > Source: node-puppeteer > Control: found -1 node-puppeteer/13.1.0+dfsg-6 > Control: affects -1 chromium > Severity: serious > Tags: sid bookworm > > node-puppeteer is keeping chromium from migrating; as > https:

Bug#1007983: node-puppeteer: broken autopkgtest keeping chromium from migrating to testing

Source: node-puppeteer Control: found -1 node-puppeteer/13.1.0+dfsg-6 Control: affects -1 chromium Severity: serious Tags: sid bookworm node-puppeteer is keeping chromium from migrating; as https://tracker.debian.org/pkg/chromium describes, "Issues preventing migration: ∙ ∙ autopkgtest for

Bug#1006009: fixed in libwebp 1.2.2-1

Hi Jeff, I'm planning to a NMU of libwebp in 2 days (Tues Mar 15th) to fix this bug, if you lack the time to fix it before then. Thanks, Andres On 3/13/22 01:22, Jeremy Bicha wrote: Please set the urgency to high when you do the upload to fix the new regression. That will automatically

Bug#1006009: fixed in libwebp 1.2.2-1

On Thu, 10 Mar 2022 18:19:09 + Debian FTP Masters wrote: > Changes: > libwebp (1.2.2-1) unstable; urgency=medium > . > * New upstream release. > * Fixes test failure on mipsel architecture (closes: #1006110) > * Fixes test failure on mipsel architecture (closes: #1006009) > Checksums-Sha1: >

Bug#1005466: chromium: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'gen/chrome/browser/resources/pdf/pdf_internal_plugin_wrapper.rollup.js'

On Sun, 13 Feb 2022 03:12:03 -0500 Andres Salomon wrote: > On Sun, 13 Feb 2022 08:16:32 +0100 Lucas Nussbaum wrote: > > Source: chromium > > Version: 98.0.4758.80-1 > > Severity: serious > > Justification: FTBFS > > Tags: bookworm sid ftbfs > > User: lu...@

Bug#1005466: chromium: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'gen/chrome/browser/resources/pdf/pdf_internal_plugin_wrapper.rollup.js'

On Sun, 13 Feb 2022 08:16:32 +0100 Lucas Nussbaum wrote: > Source: chromium > Version: 98.0.4758.80-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220212 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your

Bug#1005230: chromium: essential dependencies (libgtk-3-0) no longer depended on

On Wed, 09 Feb 2022 09:45:44 -0600 edsu...@eshop-kiosk.physics.wisc.edu wrote: > Package: chromium > Version: 98.0.4758.80-1~deb11u1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: t...@security.debian.org > > Hi, > Jumping from chromium 90 to 98 causes many

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 1/10/22 05:01, Mattia Rizzolo wrote: On Sun, Jan 09, 2022 at 11:23:20PM -0500, Andres Salomon wrote: Btw, https://salsa.debian.org/dilinger/chromium/-/tree/stable is my branch with cleaned-up commits. That's what I'll use for the NMU, which I'm preparing now. If you all agree, you could

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 1/9/22 19:06, Andres Salomon wrote: On 1/9/22 02:27, Andres Salomon wrote: On 1/9/22 00:56, Andres Salomon wrote: On 1/8/22 15:57, Mattia Rizzolo wrote: On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote: If you want to try with chromium 97; it now builds as an official

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 1/9/22 02:27, Andres Salomon wrote: On 1/9/22 00:56, Andres Salomon wrote: On 1/8/22 15:57, Mattia Rizzolo wrote: On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote: If you want to try with chromium 97; it now builds as an official build, so those DCHECKs shouldn't even

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 1/9/22 00:56, Andres Salomon wrote: On 1/8/22 15:57, Mattia Rizzolo wrote: On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote: If you want to try with chromium 97; it now builds as an official build, so those DCHECKs shouldn't even be compiled in. It also supports wayland

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 1/8/22 15:57, Mattia Rizzolo wrote: On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote: If you want to try with chromium 97; it now builds as an official build, so those DCHECKs shouldn't even be compiled in. It also supports wayland automatically, in case that's related

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 1/5/22 13:14, Mattia Rizzolo wrote: On Wed, Jan 05, 2022 at 01:52:33PM +0100, Mattia Rizzolo wrote: I suppose I'll see how it goes in the coming few days. So it's not crashing but it's being unbearably slow in gmail, to the point that I just wasn't able to type a mail there, while throwing

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 1/5/22 13:14, Mattia Rizzolo wrote: On Wed, Jan 05, 2022 at 01:52:33PM +0100, Mattia Rizzolo wrote: I suppose I'll see how it goes in the coming few days. So it's not crashing but it's being unbearably slow in gmail, to the point that I just wasn't able to type a mail there, while throwing

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 1/4/22 15:15, Mattia Rizzolo wrote: On Tue, Jan 04, 2022 at 02:50:20PM -0500, Andres Salomon wrote: Okay, that's funny - appears to be a fatal error due to being run under gdb. Well, it was also crashing outside of gdb ^^ I pushed a commit to the skip-a11y-checks branch, please give

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 1/4/22 11:46, Mattia Rizzolo wrote: [...] [413:413:0104/174404.300230:FATAL:render_process_host_impl.cc(4227)] Check failed: host->GetBrowserContext() == browser_context (0x645f47d0 vs. 0x658dcb30) Single-process mode does not support multiple browser contexts. Okay,

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

Thanks for testing! Are you doing this under sid? On 1/3/22 7:39 AM, Mattia Rizzolo wrote: On Sun, Jan 02, 2022 at 06:53:52PM +0100, Mattia Rizzolo wrote: the v96 branch of https://salsa.debian.org/dilinger/chromium FWIW, I'm trying to build it myself as well Here it started chrashing as

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On Sun, 2 Jan 2022 15:32:28 -0500 Andres Salomon wrote: > On Sun, 2 Jan 2022 20:15:01 +0100 > Moritz Muehlenhoff wrote: > > > On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote: > > > How should I handle this? NMU to sid, let people try it out, and >

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On Sun, 2 Jan 2022 20:15:01 +0100 Moritz Muehlenhoff wrote: > On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote: > > How should I handle this? NMU to sid, let people try it out, and > > then deal with buster/bullseye? > > Yeah, let's proceed with unsta

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 1/2/22 12:53 PM, Mattia Rizzolo wrote: On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote: I've got 96.0.4664.110 building on both bullseye and sid Trying it, I see it still build-depends on python-jinja2. That package is now gone, so it's not actually buildable in sid

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On Thu, 23 Dec 2021 01:49:53 -0500 Andres Salomon wrote: > On 12/13/21 5:31 PM, Moritz Muehlenhoff wrote: > > On Sun, Dec 12, 2021 at 08:11:00PM -0500, Andres Salomon wrote: > >> On 12/5/21 6:41 AM, Moritz Mühlenhoff wrote: > >>> Am Sun, Dec 05, 2021 at 10:53:

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 12/13/21 5:31 PM, Moritz Muehlenhoff wrote: On Sun, Dec 12, 2021 at 08:11:00PM -0500, Andres Salomon wrote: On 12/5/21 6:41 AM, Moritz Mühlenhoff wrote: Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers: Exactly that. I'd suggest anyone who's interested in seeing Chromium

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On 12/5/21 6:41 AM, Moritz Mühlenhoff wrote: Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers: Exactly that. I'd suggest anyone who's interested in seeing Chromium supported to first update it in unstable (and then work towards updated in bullseye-security). I started doing just

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

On Sun, 24 Oct 2021 15:06:50 -0400 Andres Salomon wrote: > Stable (bullseye) still contains chromium 90, which has had many > security issues. Testing & unstable contain 93, and stable should really > be quickly updated via stable-security to at least chromium 93 (as its > alrea

Bug#1001120: src:pyaxmlparser: fails to migrate to testing for too long: uploader built arch:all binaries

On 12/4/21 2:51 PM, Paul Gevers wrote: Source: pyaxmlparser Version: 0.3.24-1 [...] Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

Stable (bullseye) still contains chromium 90, which has had many security issues. Testing & unstable contain 93, and stable should really be quickly updated via stable-security to at least chromium 93 (as its already been packaged and proven to build) or ideally 95 (the latest stable chromium

Bug#990069: openssh-server: Not accepting new connections during Debian 10 -> 11 upgrade

Hi, So this only affects users who do or do not have the ssh metapackage installed? This bug report is a bit confusing. Thanks, Andres

Bug#991788: xfce4-settings: black screen after suspend when laptop lid is closed and re-opened

On 8/3/21 11:05 AM, truetec...@tutanota.com wrote: This is on the 5.10.0-8 kernel on Debian Bullseye with Nvidia graphics with the proprietary driver installed. I am using light-locker 1.8.0 and upower 0.99.11-2 with the desktop configured to suspend my computer on lid closures. This happens

Bug#991788: xfce4-settings: black screen after suspend when laptop lid is closed and re-opened

On Mon, 2 Aug 2021 02:08:09 +0200 (CEST) truetec...@tutanota.com wrote: > Package: xfce4-settings > Version: 4.16.0-1 > Severity: critical > > On Debian and, by extension, Ubuntu, when suspending a laptop via closing the lid on XFCE, the screen stays black after resuming from suspend. The only

Bug#990966: grub-efi-arm64: breaks upgrades when the efivarfs is mounted read-only

Package: grub-efi-arm64 Version: 2.04-19 Severity: serious I experienced the follow on multiple ARM64 systems (both a Rock64 board and a Raspberry Pi 4b board) during an unattended-upgrades run: Unattended upgrade result: All upgrades installed Packages that attempted to upgrade:

Bug#989244: spectral: behaves unpredictably when logged in with username only (segfaults, dead controls, etc.)

On 5/31/21 7:04 AM, Mike Gabriel wrote: On Mo 31 Mai 2021 03:59:12 CEST, Andres Salomon wrote: Spectral is not good about showing login failures. This isn't something that affects regular users (since you only ever log in once), but it's annoying for first-time users. Make sure you're using

Bug#989244: spectral: login works, but then no chats/rooms etc. appear, nothing can be clicked on

On 5/30/21 5:48 AM, Mike Gabriel wrote: Package: spectral Version: 0.0~git20210114.30028a2-2 Severity: grave I have just tested the spectral [matrix]-Client on Debian bullseye (still testing) and only thing I can do with it is logon (giving matrix server name, username and password, plus

Bug#989244: spectral: login works, but then no chats/rooms etc. appear, nothing can be clicked on

On 5/30/21 9:59 PM, Andres Salomon wrote: On 5/30/21 5:48 AM, Mike Gabriel wrote: It seems that this application is not really suitable for Debian 11 inclusion, is it? What am I missing? It's rough around the edges, but has been perfectly usable for me. Oh, and to be clear - once

Bug#982740: pulseaudio: FTBFS on ppc64el

On Fri, 26 Feb 2021 03:21:36 +0200 Faidon Liambotis wrote: [...] > > pa_cpu_init_orc() returns true only if cpu_info.cpu_type == > PA_CPU_X86. This should not be the case here, but cpu_info is being > passed to the function uninitialized, and... as luck would have it, > cpu_info.cpu_type's

Bug#964884: gplaycli does not seem to be suitable for stable releases

severity 964884 normal thanks After talking with the fasttrack folks, I'm lowering the severity of this bug. This package seems more akin to youtube-dl than anything else, and they (correctly) pointed out that I should've done a stable-proposed-update when the API broke rather than having the

Bug#982740: pulseaudio: FTBFS on ppc64el

On Sun, 14 Feb 2021 19:27:03 +0200 Adrian Bunk wrote: > > > > FAIL: cpu-volume-test > > = > > > > Running suite(s): CPU > > 0%: Checks: 1, Failures: 1, Errors: 0 > > tests/cpu-volume-test.c:81:F:svolume:svolume_orc_test:0: Failed > > FAIL cpu-volume-test (exit status: 1) > >

Bug#982740: pulseaudio: FTBFS on ppc64el

Package: pulseaudio Version: 14.2-1 Severity: serious Pulseaudio is failing to build on ppc64el. The version of pulseaudio in bullseye suffers from a pretty serious usability bug (see #980836) which should arguably be a higher severity, but let's focus on getting 14.2-1 built properly.

Bug#970747: liblinphone-dev: should depend on liblinphone++10

Package: liblinphone-dev Version: 4.4.0-1 Severity: serious While building linphone-desktop, I hit the following build error: CMake Error at /usr/share/LinphoneCxx/cmake/LinphoneCxxTargets.cmake:70 (message): The imported target "linphone++" references the file

Bug#964884: gplaycli does not seem to be suitable for stable releases

Correct me if I'm wrong Matlink, but I believe that this is the first Google API change/breakage in gplaycli's 4+ year history of being included in Debian? I'm not seeing a huge risk with allowing bullseye to release with this package (although obviously I can't predict the future). I know

Bug#950112: gplaycli: 502 Bad Gateway, does not work at all

On Sat, 28 Mar 2020 09:10:49 +0800 Paul Wise wrote: > Control: tags -1 + fixed-upstream > > On Tue, 28 Jan 2020 23:50:24 +0100 Thorsten Glaser wrote: > > > After installation, gplaycli --help works (but please do add > > a manual page), but nothing else: > > The error is now different: > > $

Bug#950112: gplaycli: 502 Bad Gateway, does not work at all

Thanks for your bug reports! So at this point, I'm wondering what to do with the current package, now that I've uploaded a version that fixes the other bugs. The package is still useful to me as a means to grab apks, even though it required adding a google login/password. I see a few different

Bug#951085: gcc-10: FTBFS due to missing parens in versioned break

Package: gcc-10 Version: 10-20200210-1 Severity: serious gcc-10 is failing to build with the following error: dpkg-gencontrol: error: error occurred while parsing Breaks field: cryptsetup-initramfs << 2:2.2.2-3~, dh_gencontrol: error: dpkg-gencontrol -plibgcc-s1 -ldebian/changelog

Bug#928210: CVE-2019-11471

Hi, Just FYI, there's a bunch of additional fuzz-related fixes in libheif's upstream git repo. I don't see any assigned CVEs other than the one you've tagged in this bug, but this heap buffer overflow fix in particular caught my eye as something we may want to include:

Bug#928417: Bug#928415,#928417: [firefox] All extensions are disabled

Thanks for the tip, Alexis! Installing the Debian-packaged plugins does the trick - hands down the easiest way to work around this bug.

Bug#927057: 1Gb of logs is too much

I think the issue here is that python's logging isn't compressing older files. total 1.1G -rw-r--r-- 1 matrix-synapse matrix-synapse 68M Apr 22 02:12 homeserver.log -rw-r--r-- 1 matrix-synapse matrix-synapse 100M Apr 18 05:13 homeserver.log.1 -rw-r--r-- 1 matrix-synapse matrix-synapse 100M Feb

Bug#903201: cinnamon: CVE-2018-13054: privilege escalation in cinnamon-settings-users.py GUI

On Mon, Jan 14, 2019 at 5:39 PM, Andres Salomon wrote It's not a critical bug (cinnamon-settings-users continues running), it just can't update the file. That needs to be fixed upstream if it's not already, by changing ownership or deleting the old file before dropping privileges. I've

Bug#903201: cinnamon: CVE-2018-13054: privilege escalation in cinnamon-settings-users.py GUI

Hi, Is there a reason why this hasn't been fixed in stretch yet? The upstream commit is here: https://github.com/linuxmint/Cinnamon/commit/66e54f43f179fdf041a3e5232178a9910963cfb5 https://github.com/linuxmint/Cinnamon/commit/66e54f43f179fdf041a3e5232178a9910963cfb5.patch It applies to the

Bug#916160: lsof FTBFS with glibc 2.28

For anyone looking at this bug (especially folks at bug squashing parties): I've filed an Intent To Salvage for this package (https://bugs.debian.org/917937), and assuming I don't hear from the maintainer by January 21st, will be uploading a version of lsof that fixes this bug.

Bug#916160: lsof FTBFS with glibc 2.28

Hi, Just FYI, this build failure is already fixed in the latest version of lsof (4.91). I've attached a backport of the upstream fix. I (or someone else) could NMU 4.89, but given that we're still a month away from the transition freeze I'd much rather see lsof updated to the new version.

Bug#903718: gplaycli currently unusable in stable/backport/testing/unstable

As you discovered, the version in experimental works. Unfortunately, googleplay-api (which gplaycli uses) has a strict dependency on newer versions of protobuf, which are available only in experimental. So we've been stuck waiting on protobuf 3.6 to transition to unstable. It is not the only

Bug#897151: Package erroneously expects googletest headers in /usr/include

Hi, Protobuf 3.0.0-9.1 (the version in unstable) already depends upon libgtest-dev; the FTBFS is due to a missing build-dependency on libgmock-dev. The version of protobuf in experimental (3.5.2-2) includes a build-dep on both libgtest-dev and libgmock-dev, so it should build properly with the

Bug#895792: gplaycli: dependency androguard switched to Python 3, gplaycli is incompatible with Python 3

On Tue, Apr 24, 2018 at 6:04 PM, Andres Salomon <dilin...@queued.net> wrote: Just FYI, I have a new gplaycli package prepared (and its new gpapi dependency). It is python3 only. However, it requires a newer version of protobuf, so we've been stuck waiting on that. See https://bugs.debi

Bug#895792: gplaycli: dependency androguard switched to Python 3, gplaycli is incompatible with Python 3

Just FYI, I have a new gplaycli package prepared (and its new gpapi dependency). It is python3 only. However, it requires a newer version of protobuf, so we've been stuck waiting on that. See https://bugs.debian.org/874498 for the status of that. And, of course, the gpapi package will be

Bug#817602: olpc-xo1: Removal of debhelper compat 4

On December 24, 2016 7:24:00 PM PST, Paul Wise <p...@debian.org> wrote: >On Sun, Dec 25, 2016 at 10:38 AM, Andres Salomon wrote: > >> Thanks for the patch. Given that OLPC isn't really alive any more, >> I'm thinking the OLPC packages should probably just be remo

Bug#817602: olpc-xo1: Removal of debhelper compat 4

On Sat, 24 Dec 2016 20:26:06 -0500 Logan Rosen wrote: > Control: tags -1 patch > > Dear Maintainer, > > In Ubuntu, the attached patch was applied to achieve the following: > > * debian/compat: Bump to 10. > * debian/control: > - Build-depend on debhelper (>= 10). >

Bug#726057: msr-tools and cpuid: error when trying to install together

On Sun, 20 Oct 2013 21:45:41 +0600 Andrey Rahmatullin w...@wrar.name wrote: On Fri, Oct 11, 2013 at 08:25:17PM +0200, Ralf Treinen wrote: dpkg: error processing /var/cache/apt/archives/msr-tools_1.3-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/cpuid.1.gz', which is

Bug#689578: sysklogd modifies /etc/syslog.conf with helper script

On Mon, 21 Jan 2013 07:59:58 +0100 Michael Biebl bi...@debian.org wrote: Am 21.01.2013 02:32, schrieb Andres Salomon: A better approach imho would be to simply remove sysklogd from the archive. It's dead upstream, apparently no longer properly maintained in Debian, and there are enough

Bug#689578: sysklogd modifies /etc/syslog.conf with helper script

On Sat, Oct 13, 2012 at 00:41:35 +0200, Michael Biebl wrote: A better approach imho would be to simply remove sysklogd from the archive. It's dead upstream, apparently no longer properly maintained in Debian, and there are enough more then suitable alternatives. With rsyslog we even have

  1   2   >