Bug#1100428: sabnzbdplus: please fix the autopkgtests that use python3-selenium/chromium

Source: sabnzbdplus Control: found -1 sabnzbdplus/4.4.1+dfsg-1 Control: affects -1 chromium Severity: serious Tags: sid trixie The package sabnzbdplus has some autopkgtests in debian/tests/ that seem to randomly fail when different versions of chromium are being tested with it. You can see some

Bug#1099792: chromium 134.0.6998.35-1~deb12u1 into stable-security has broken python3-selenium on bookworm

u1 (source amd64 all) into stable-security (Debian FTP Masters) (signed by: Andres Salomon) to stable-security which upgraded chromium from 133 to 134. Unfortunately, it seems that such an upgrade has broken python3-selenium, which hasn't been upgraded in stable since 4.8.3+dfsg-1, March 2023.

Bug#1096057: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 48

On 3/1/25 16:58, Hank Knox wrote: [...] Let me know the best way to move forward with this. In the meantime, I'll start updating and testing the Debian package. Just ping me if it works out and you need me to handle the upload. Given the short timeline (we're looking at Trixie being frozen

Bug#1099210: chromium: Uninstallable on sid due to old deps

This bug will get fixed with the next source upload (probably on Tuesday). I had to do a binary upload due to NEW processing, which I wasn't anticipating. On 3/2/25 06:02, Tobias Frost wrote: Control: tags -1 unreproducible On Sat, Mar 01, 2025 at 08:24:12PM +0100, Guillem Jover wrote: Packa

Bug#1096057: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 48

Hi Hank, Did you see this? Are you interested in preparing an update for the package? Thanks, Andres On 2/28/25 14:12, Jeremy Bícha wrote: I am explicitly emailing you to let you know that gnome-shell-extension-no-annoyance will be removed from Debian Testing in a few days as part of the GNOME

Bug#1086581: stringencoders: diff for NMU version 3.10.3+git20180306-1.2

On Mon, 30 Dec 2024 20:31:47 + Jonathan Wiltshire wrote: Control: tags 1086581 + pending Dear maintainer, I've prepared an NMU for stringencoders (versioned as 3.10.3+git20180306-1.2) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Thanks for do

Bug#1089181: chromium still not installable via debian-live

I don't know how it debian-live works, is it using an outdated mirror or something? 131.0.6778.139-1~deb12u1 is currently in both stable-security and stable-proposed-updates. On 12/16/24 18:19, Thierry wrote: Package: chromium Version: 131.0.6778.108-1~deb12u1 Dear Maintainer (CC-ing the deb

Bug#1089181: chromium: security update wants to remove chromium package itself

On 12/10/24 14:41, Neil Van Dyke wrote: Are those library updates part of the security update?     The following packages will be REMOVED:   libc++1-16 libc++abi1-16 libunwind-16     The following NEW packages will be installed:   libc++1-19 libc++abi1-19 libunwind-19     The follow

Bug#1089181: chromium: Stable update wants to remove chromium package itself

On 12/7/24 17:53, Cyril Brulebois wrote: Stephen Kitt (2024-12-07): On Sat, 07 Dec 2024 22:27:52 +0500, Alex Volkov wrote: On Sat, 7 Dec 2024 01:18:41 +0100 Santiago Vila wrote: Is this really a work-around? Yes, it is. (try it!) The problem is that the new chrome package is in securit

Bug#1089181: chromium: Stable update wants to remove chromium package itself

Hi, For the time being you'll have to add bookworm-proposed-updates to your /etc/apt/sources.list. For example the following line: deb http://deb.debian.org/debian/ bookworm-proposed-updates main I'm asking the release team how best to handle this. Sorry about that! Thanks, Andres On 12/6/

Bug#1089182: chromium: Cannot install on bookworm, missing abi1-19

Hi, For the time being you'll have to add bookworm-proposed-updates to your /etc/apt/sources.list. For example the following line: deb http://deb.debian.org/debian/ bookworm-proposed-updates main I'm asking the release team how best to handle this. Sorry about that! Thanks, Andres On 12/6/2

Bug#1088974: chromium: 131.0.6778.85-1~deb12u1 in bookworm-security fails to start on arm64: stack smashing detected

Currently waiting on #1088699 to fix this. On 12/3/24 12:06, Emanuele Rocca wrote: Package: chromium Version: 131.0.6778.85-1~deb12u1 Severity: serious User: debian-...@lists.debian.org Usertags: arm64 On arm64 systems, the version of chromium currently in bookworm-security (131.0.6778.85-1~deb

Bug#1084726: chromium: removal of Python standard libraries in Python 3.13

On Mon, 7 Oct 2024 12:26:56 -0400 =?UTF-8?Q?Louis-Philippe_V=C3=A9ronneau?= wrote: Source: chromium Severity: important User: debian-pyt...@lists.debian.org Usertags: pep-594-deprecation-313 Dear maintainer(s), Python 3.13 removes a large amount of so called 'dead battery' libraries from the

Bug#1081194: LLVM 19: lowering severity, and please remove your removal hint

On Fri, 27 Sep 2024 10:21:16 + sylvestre...@ledru.info wrote: Le dimanche 15 septembre 2024 à 21:05, Sylvestre Ledru a écrit : > > Hello, > > Le 15/09/2024 à 20:11, Sebastian Ramacher a écrit : > > > To move forward in this regard, we would like to ask the LLVM > > maintainers to provi

Bug#1082907: chromium: FTBFS with reverted libxml2

Control: tags -1 pending On 9/28/24 02:48, Sebastian Ramacher wrote: Source: chromium Version: 129.0.6668.70-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org libxml2 has been reverted to the 2.9.x s

Bug#1082956: apt: autoremove --purge changed behavior; immediately removes packages

Package: apt Version: 2.9.8 Severity: serious Justification: breaks entire system X-Debbugs-Cc: dilin...@queued.net On bookworm, running 'apt [auto]remove --purge ' will provide a list of packages to be removed, and prompt the user before actually removing those packages. It has been this way (pre

Bug#1052105: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 46

more than enough to know there are gaps in my knowledge of how best use git.) Hank On 8/27/24 21:56, Andres Salomon wrote: Sorry for the delayed response. I was planning to orphan this package, but I wanted to update it before I do that. There is a git repo for the package here:

Bug#1052105: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 46

Sorry for the delayed response. I was planning to orphan this package, but I wanted to update it before I do that. There is a git repo for the package here: https://salsa.debian.org/dilinger/gnome-shell-extension-no-annoyance If you can update that and submit a merge request for that, I'd happ

Bug#1073508: libxml2: just another API+ABI break; please bump soname

On Tue, 25 Jun 2024 04:17:09 -0400 Andres Salomon wrote: [...] The libxml package is currently keeping chromium from migrating to trixie, so I'm looking forward to this getting sorted out (whether upstream or with an SONAME bump or what). Hi, I'm just curious what the stat

Bug#1073508: libxml2: just another API+ABI break; please bump soname

On Mon, 17 Jun 2024 16:38:58 +0200 (CEST) Thorsten Glaser wrote: On Mon, 17 Jun 2024, Aron Xu wrote: >Control: tags -1 - pending Oops, right. >It looks that this libxml2 update is causing more troubles than >expected, I would like to ask for your opinion whether it's better to >revert to an o

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 for

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: se

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 was

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 ve

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 relea

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 n

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 DEL

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

26 AM -04:00:00, 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

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-1

Bug#1051355: Processed: your mail

ff to git 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 -

Bug#1051355: Processed: your mail

023 at 03:07:29 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

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 <

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 phpldap

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 compi

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 bullsey

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: https://github.com/SeleniumHQ/

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, c

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: https://ci.debian.net/packages/j/jquery

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 appear

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

mits/bullseye Based 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 in

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 mos

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: test/shaping/data/in-house/fonts/641ca9d7808b01cafa9a666

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. Bulls

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 sta

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.c

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 buil

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

with mine so that we can identify if something relevant changed in the meantime 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 chan

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 not

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 Profi

Bug#1009359: New security upgrade prevent Chromium from starting

ws, one does work but the 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

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/ sta

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: > > https://frama

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 node-p

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 re

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 p

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 dependenci

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 a

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 ev

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 wa

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

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 o

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 o

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

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, that's

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 soo

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

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 builda

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 seein

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 th

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 will

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 r

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: shim-helper

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 yo

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 dev

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 -

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 "rando

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 pack

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. https://bu

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 "/usr/lib/x86_64-linux-gn

  1   2   3   >