Bug#907652: grep: please use libpcre2 instead of pcre3

Upstream patches were proposed in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=47264 , and they've been merged upstream. The next upstream grep release, whenever that is, should allow this debian bug to be closed.

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

severity 964884 serious thanks This now appears to no longer be developed upstream, and also is currently broken. It probably should not be released with bookworm.

Bug#956012: Frightening!

I agree that it's a pretty annoying and scary message (and incorrect - "If a software program on your system has set enterprise policies that affect how Chrome works, you’ll see this message—even if it’s not fully managed by an organization."

Bug#956012: Frightening!

It looks like the other way to do this is through /etc/chromium/master_preferences, which will only take effect when people first install and run chromium. "search_provider_overrides": [{ "enabled": true, "encoding": "UTF-8", "favicon_url": "https://duckduckgo.com/favicon.ico;,

Bug#973240: chromium: APNGs flicker

On Thu, 6 Jan 2022 05:40:37 -0500 Andres Salomon wrote: > On Thu, 06 May 2021 13:05:58 +0300 Henry Jameson wrote: > > There's a similar bug report in ArchLinux: > > https://bugs.archlinux.org/task/67105 > > > > Supposedly they had some custom patch

Bug#1011346: Enabling V4L2 Driver in Chromium Builds

Thanks for the patch! The merged upstream patch is in chromium v105, but it's not in v104 (which is what we're currently on). v105 is slated for release on Aug 30th. I'll will try including your patch in the v105 upload, at least for sid. Since it depends on kernel 5.17 headers, I'm not yet

Bug#1016900: chromium: advertisement on default startpage

The next chromium upload will default to using duckduckgo instead of google. https://salsa.debian.org/chromium-team/chromium/-/commit/b7adbaea2c73ce836fd3bc6371d96766da655027 On Tue, Aug 9, 2022 at 14:06, Christian Göttsche wrote: Package: chromium Version: 104.0.5112.79-1 The default

Bug#1016768: dino-im: please include patch to resolve known xmpp: links

attached the patch that I included in my own builds at https://people.debian.org/~dilinger/dino-im/ , if that's helpful. >From ec2e6192d6cf01ab57326ac4cc9ffc99eae89f95 Mon Sep 17 00:00:00 2001 From: Andres Salomon Date: Sat, 12 Mar 2022 17:23:14 -0500 Subject: [PATCH] Display friendlier x

Bug#956012: debian-edu-config: use DuckDuckGo as Chromium's default search provider

Alright, got it - using the "recommended" subdirectory instead of "managed" does the trick. It'll be in the next release after 104.0.5112.79-1. On Wed, Aug 3, 2022 at 14:07, Andres Salomon wrote: On Mon, 06 Apr 2020 06:30:53 + Mike Gabriel wrote: > Packa

Bug#956012: debian-edu-config: use DuckDuckGo as Chromium's default search provider

On Mon, 06 Apr 2020 06:30:53 + Mike Gabriel wrote: > Package: chromium > Severity: wishlist > > Currently (during the bullseye release cycle), chromium uses Google as > the default search provider. > > With the below snippet dropped into > /etc/chromium/policies/managed/.json we could

Bug#1006457:

The builds are almost identical, except for the compiler (clang 11) and build environment used. Clang 13 has been backported to stable (it's currently in stable-proposed-updates, and should be in the bullseye 11.5 release). The next chromium upload should be built against clang-13, which may

Bug#994151: youtube-dl seems to be alive again

On Tue, 26 Jul 2022 02:44:37 +0200 Christoph Anton Mitterer wrote: > On Tue, 2022-07-26 at 02:36 +0200, Diederik de Haas wrote: > > It looks like things have changed and 'dirkf' has become the new > > maintainer: > > My understanding was the was mostly "maintaining" it for stuff that > doesn't

Bug#1016047: RFH: chromium -- web browser

Package: wnpp Severity: normal I'm currently the only active maintainer for the chromium package in Debian. This really needs to be maintained by a team, especially since it requires security updates for stable at least two times per month. It is likely that chromium will not be included in

Bug#992360: #992360 xfce4-notes-plugin in sid/bullseye

On Thu, 23 Jun 2022 15:42:33 -0400 Andres Salomon wrote: > > On Thu, Jun 23, 2022 at 20:08, Yves-Alexis Perez > wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > On Wed, 2022-06-22 at 19:11 -0400, Andres Salomon wrote: > >> Can we

Bug#956012: RE: chromium: use DuckDuckGo as Chromium's default search provider

On Mon, 17 Jan 2022 14:03:53 -0300 Leandro Cunha wrote: > Hi, > > What do you think, Andres? > This idea is good. > I use duckduckgo as my default search engine. > I don't know if your idea is to continue with browser maintenance. Thanks for the nudge on this, and sorry for the late response.

Bug#1012905: chromium: ftbfs with GCC-12

This is fixed upstream with the following commit, which is included in the latest chromium in sid: https://chromium.googlesource.com/chromium/src/+/9dd0503835dc875807ab63efb1f477bffed2a852%5E%21/ Please retest with chromium 103.0.5060.53-1 in sid & bookworm and let me know if it still FTBFS.

Bug#992360: #992360 xfce4-notes-plugin in sid/bullseye

On Thu, Jun 23, 2022 at 20:08, Yves-Alexis Perez wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2022-06-22 at 19:11 -0400, Andres Salomon wrote: Can we please get an upload of xfce4-notes-plugin 1.9.0 to unstable? I'm happy to do a backport to bullseye once it migrates

Bug#992360: #992360 xfce4-notes-plugin in sid/bullseye

On 6/22/22 19:11, Andres Salomon wrote: On Mon, 23 Aug 2021 15:50:31 +0200 Adam Borowski wrote: [...] > > Thus: XFCE guys, please upload to unstable and bullseye-backports! > Thanks for your good work so far. > Can we please get an upload of xfce4-notes-plugin 1.9.0 to unstable

Bug#992360: #992360 xfce4-notes-plugin in sid/bullseye

On Mon, 23 Aug 2021 15:50:31 +0200 Adam Borowski wrote: [...] > > Thus: XFCE guys, please upload to unstable and bullseye-backports! > Thanks for your good work so far. > Can we please get an upload of xfce4-notes-plugin 1.9.0 to unstable? I'm happy to do a backport to bullseye once it

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#1011078: chromium: arm64 package not available in bullseye-security

upload. Thank you! On Sat, May 28, 2022 at 14:04, Salvatore Bonaccorso wrote: Hi Andres, On Fri, May 27, 2022 at 09:18:02PM -0400, Andres Salomon wrote: I uploaded chromium-102 to bullseye-security, and I don't see armhf binary packages. Salvatore, can you please tell me if that build

Bug#1011078: chromium: arm64 package not available in bullseye-security

, 2022 at 17:27, Salvatore Bonaccorso wrote: Hi, On Mon, May 16, 2022 at 03:53:25PM -0400, Andres Salomon wrote: clone 1011078 -1 retitle -1 chromium: i386 and armhf packages FTBFS in bullseye tags -1 bullseye ftbfs severity -1 serious thanks On Mon, 16 May 2022 20:33:46 +0200 Salvatore

Bug#1006807: chromium: No access yahoo and gmail

At the time that I sent that followup, 100 was the latest version. 102 is now the latest version, so please test with that instead. It is in both sid (unstable) and bullseye-security (stable), but both were uploaded early today so might not show up on some mirrors yet. On Wed, May 25, 2022

Bug#1011346: Enabling V4L2 Driver in Chromium Builds

Package: chromium Severity: wishlist On Fri, May 20, 2022 at 06:42, Eschenbacher.Stefan wrote: Dear Debian Chromium Team, I am testing Debian Testing/Bookworm ARM64 with a NXP i.MX8MM board and Kernel 5.17. I try to use the new stateless v4l2 Linux API for video acceleration. The i.MX8MM

Bug#1011078: chromium: arm64 package not available in bullseye-security

clone 1011078 -1 retitle -1 chromium: i386 and armhf packages FTBFS in bullseye tags -1 bullseye ftbfs severity -1 serious thanks On Mon, 16 May 2022 20:33:46 +0200 Salvatore Bonaccorso wrote: [...] > Hi Andres, > > On Mon, May 16, 2022 at 12:36:38PM -0400, Andres Salomon wrote: >

Bug#1011078: chromium: arm64 package not available in bullseye-security

On 5/16/22 11:35, Ben Steinberg wrote: Package: chromium Version: 101.0.4951.64-1~deb11u1 Severity: normal X-Debbugs-Cc: bsteinb...@law.harvard.edu Dear Maintainer, Chromium 101.0.4951.64-1~deb11u1 has been accepted for bullseye-security, and the package is present for the amd64 architecture.

Bug#1010708: cryptsetup: init script doesn't appear to do anything with force-start due to masked systemd services

Package: cryptsetup Version: 2:2.3.7-1+deb11u1 This is on a newly installed Debian 11 system, and an external USB drive that had previously been used on a Debian 9 or 10 (I forget which) system. dilinger@hm90:~$ /sbin/blkid /dev/sda /dev/sda: UUID="2d95e6f9-bdfd-4045-8683-42cdef679b6a"

Bug#1010609: chromium: Missing suggested package chromium-l10n on 101.0.4951.54-1 upgrade

Hi, It should all be installable now. Is it? Thanks, Andres On 5/5/22 08:13, Ernesto Domato wrote: Package: chromium Version: 101.0.4951.41-2 Severity: normal X-Debbugs-Cc: edo...@gmail.com Hi, The package chromium-l10n is missing when trying to upgrade to 101.0.4951.54-1 Greets, Ernesto

Bug#1010676: chromium-l10n: -l10n version behind chromium version in Sid

It should all be installable now. Is it? On 5/6/22 16:31, Andres Salomon wrote: I think the buildd got stuck: https://buildd.debian.org/status/package.php?p=chromium It finally built the arch:all package(s) 5 hours ago, so they should enter the archive soon. I noticed earlier that it had

Bug#1010676: chromium-l10n: -l10n version behind chromium version in Sid

I think the buildd got stuck: https://buildd.debian.org/status/package.php?p=chromium It finally built the arch:all package(s) 5 hours ago, so they should enter the archive soon. I noticed earlier that it had been building for 2+ days, despite normally taking about 15 mins to build. :) On

Bug#1010407: chromium: does not support older CPUs that lack SSE3 instructions

Okay, the next release will include the explicit check for SSE3: https://salsa.debian.org/chromium-team/chromium/-/commit/836b9da55c776a27d884d0405f385dcb7ef6f12e This is replacing the old check for SSE2.

Bug#1010415: www.debian.org: please slightly clarify description of 'grave' bug severity

Package: www.debian.org Severity: wishlist On https://www.debian.org/Bugs/Developer, the description for the severity level of grave reads, "makes the package in question unusable or mostly so, or causes data loss, or introduces a security hole allowing access to the accounts of users who

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#867977: youtube-dl: Arbitary JavaScript execution?

On Mon, 10 Jul 2017 22:02:20 +0200 =?utf-8?q?Joonas_Kylm=C3=A4l=C3=A4?= wrote: > Package: youtube-dl > Version: 2017.05.18.1-1 > Severity: normal > > Dear Maintainer, > > Recently Trisquel GNU/Linux users discovered that youtube-dl might in > some cases execute (as far as I understood) arbitary

Bug#994151: New release

On Sun, 19 Dec 2021 14:54:12 +0100 Adrien CLERC wrote: > Hi, > > As a matter of fact, there was a new release 3 days ago: > https://github.com/ytdl-org/youtube-dl/releases/tag/2021.12.17 > > However, the main maintainer remove himself from the list of active > developers: >

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#1009802: Warning: The home dir /var/lib/usbmux you specified can't be accessed: No such file or directory

On 4/18/22 02:34, Scott Corcoran wrote: Package: chromium Version: 100.0.4896.88-1 Severity: normal Dear Maintainer, Warning: The home dir /var/lib/usbmux you specified can't be accessed: No such file or directory Adding system user `usbmux' (UID 113) ... Adding new user `usbmux' (UID 113)

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#1006457: Chromium fails to start on aarch64 systems

On Sat, 2 Apr 2022 00:06:04 +0200 MichaIng wrote: > > Package: chromium > Version: 99.0.4844.74-1~deb11u1 > > > Which boards did you test with? > > We observed the issue on these boards: > - Odroid C2 > - Odroid C4 > - Odroid N2+ > - Radxa ROCK Pi 4 > - Radxa Zero > > > What desktops were you

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#1009284: util-linux: new upstream release with lsfd command

Package: util-linux Version: 2.37.3-1+b1 Severity: wishlist Hi, I see that util-linux 2.38-rc2 is in experimental, but final 2.38 has been released. As the lsof maintainer, I'm interested in seeing how usable lsfd is in this release. It's meant to replace lsof on linux. Lsfd was merged in rc1,

Bug#1004521: lsof: New upstream release (4.94.0, 2020 Nov 10)

On 1/30/22 04:40, Florian Ernst wrote: On Sat, Jan 29, 2022 at 03:10:46PM -0500, Andres Salomon wrote: Thanks, I'm aware. I pushed a bunch of patches upstream and was waiting for 4.95 to get released, but it's taking longer than expected. :( Thanks for the feedback, and thanks for taking care

Bug#893448: please add a chromium-source binary package

On Mon, 15 Oct 2018 23:00:23 +0200 =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= wrote: > On Mon, Oct 15, 2018 at 10:41:25PM +0200, Steinar H. Gunderson wrote: > > On Mon, Oct 15, 2018 at 10:33:11PM +0200, Moritz Muehlenhoff wrote: > > > Ultimately this is up for Michael to decide, as he's dealing with

Bug#995903: chromium: Download manager, bookmark manager and extension manager is not showing when on there tab

On Fri, 19 Nov 2021 22:40:15 +0200 Sophoklis Goumas wrote: > Package: chromium > Version: 93.0.4577.82-1 > Followup-For: Bug #995903 > > I too confirm this is affecting me in a way that makes Chromium's use deprived > of core functionality as I can't access my bookmarks and extensions. > Hi,

Bug#1006807: chromium: No access yahoo and gmail

Just FYI, I'm currently working on chromium 100. If this is something related to chromium 99, the 100 release might help. Also, try running as 'chromium --user-data-dir=/tmp' or 'chromium --temp-profile'; you'll have to manually enter logins/passwords for yahoo/gmail, but that could tell you

Bug#987292: chromium: Use system libxnvctrl

On Tue, 20 Apr 2021 23:52:12 +0200 Bastian Germann wrote: > Package: chromium > Severity: wishlist > > debian/TODO says: "remove third_party/libXNVCtrl (package currently in contrib, bug #747837)" > > The bug is done and libxnvctrl-dev is in main now. Please compile against the system library.

Bug#201448: StepMania4 reached Alpha

On Thu, 9 Apr 2009 14:11:49 -0400 Danny Piccirillo wrote: > StepMania 4 has now reached alpha (and actually is now at alpha 3 after only > a few days). It has a new theme and is very stable! I'm not interested in maintaining this, but I did have to build it because the last release is from

Bug#1005269: chromium-driver: hangs more often than not when initializing Chrome

On Thu, 10 Feb 2022 08:49:16 +0100 =?utf-8?q?IOhannes_m_zm=C3=B6lnig_=28Debian/GNU=29?= wrote: > Package: chromium-driver > Version: 98.0.4758.80-1 > Severity: important > > Dear Maintainer, > > i've been using chromium-driver in a small selenium python3 script > almost daily for more than a

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#934025: chromium: can't access mic ( no audio input ), works fine in firefox

Hi, Can you tell me if this issue is resolved with the latest chromium (v99) or not? Thanks, Andres On Tue, 06 Aug 2019 01:08:00 -0700 Ximin Luo wrote: > Package: chromium > Version: 76.0.3809.87-2+b1 > Severity: important > > Dear Maintainer, > > Chromium can't access the microphone, the

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#1007913: wine: Upstream version 7.4

Control: retitle -1 wine: new upstream version 7.0 I'd like to see wine 7.0 in sid, as roblex requires it (https://roblox.fandom.com/wiki/Roblox_on_Linux). On Fri, 18 Mar 2022 18:21:44 +0100 Antoine Le Gonidec wrote: > Le 18/03/2022 à 14:27, Matthias Urlichs a écrit : > > WINE Upstream is

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#1006457: Chromium fails to start on aarch64 systems

On Fri, 25 Feb 2022 20:45:55 +0100 MichaIng wrote: > > Package: chromium > Version: 98.0.4758.102-1~deb11u1 > > Latest Chromium on Debian Bullseye fails to start on aarch64/arm64 > systems. Different ones with different kernels were tested, though all > Linux 5.10 variants, using (and generally

Bug#1006822: chromium: Chromium doesn't start on sway after latest securty update

On Sat, 05 Mar 2022 21:34:29 +0100 Andreas Juch wrote: > Package: chromium > Version: 99.0.4844.51-1~deb11u1 > Severity: important > X-Debbugs-Cc: t...@security.debian.org > > Dear Maintainer, > > After the latest security update of chromium from 98 to 99 chromium > doesn't start any more. I'm

Bug#1006807: chromium: No access yahoo and gmail

On Sat, 05 Mar 2022 10:06:44 -0500 bw wrote: > Package: chromium > Version: 99.0.4844.51-1~deb11u1 > Severity: normal > > Dear Maintainer, > > I appreciate you trying to keep up with all the changes. > > Since the last ver, unable to login to gmail or yahoo mail. Tried clearing cookies > and

Bug#1004368: chromium: "Stack smashing detected" messages

On Wed, 26 Jan 2022 03:11:16 -0500 Andres Salomon wrote: > > *** stack smashing detected ***: terminated > > I backported clang-13 to debian stable and used it to build chromium. Nothing else was backported or changed (other than the requisite changes needed to tell chromium to

Bug#1003622: chromium: microphone stopped working after upgrade

On 2/19/22 05:53, Francesco Poli wrote: On Thu, 10 Feb 2022 20:51:43 +0100 Francesco Poli wrote: On Mon, 7 Feb 2022 03:48:15 -0500 Andres Salomon wrote: [...] Edit /etc/chromium.d/default-flags, and add --disable-features=AudioServiceSandbox to one of those CHROMIUM_FLAGS variables

Bug#989529: ITP: neochat -- Client for Matrix chat

reopen 989529 Andres Salomon retitle 989529 RFP: neochat -- Client for Matrix chat thanks Hi Norbert, I'm sorry to hear that. Thank you for your work on debian! On Sat, 19 Feb 2022 13:47:46 +0900 Norbert Preining wrote: > Hi Andres, > > thanks for your message, but I have no i

Bug#1004155: dino-im: new upstream version

On Fri, 21 Jan 2022 18:04:12 -0500 Andres Salomon wrote: > On Fri, 21 Jan 2022 16:20:50 -0500 Andres Salomon wrote: > > > > I ran into a dino-im bug (couldn't hear output from audio calls), and > > in attempting to debug it I realized that there's been a new > > &g

Bug#989529: ITP: neochat -- Client for Matrix chat

On 11/7/21 02:03, Norbert Preining wrote: Hi Andres, Norbert, I'd planned to remove Spectral from sid once you uploaded Neochat. Do you have a timeline for when you plan to do that? Since Spectral was Hmm, the current released version is - well - not sure how useful. I tried it without too

Bug#1005808: chromium: ERR_SSL_VERSION_OR_CIPHER_MISMATCH after upgrade to 98.0.4758.80

On 2/17/22 02:21, Benoît Panizzon wrote: Hi Andres I'm a bit confused by this bug report. Why do you need chromium (presumably over https) talking to network hardware drivers? Or do you mean you have older network hardware where the firmware exposes an https port, and chromium no longer

Bug#1005169: regression: Chromium is not using plasma file dialog anymore since overlast update

clone 1005169 -1 reassign -1 src:plasma-desktop retitle -1 plasma-desktop: plasma-desktop should probably depend upon xdg-desktop-portal-kde affects chromium -1 thanks Rather than just reassigning this, I'm going to leave it open for a while with chromium. Even if it gets fixed in

Bug#1005410: chromium: debug trap warning on browser start up

On 2/13/22 14:12, 10dmar10 wrote: Strange, with installed debug packages still no symbols: # aptitude search chromium i chromium - Webbrowser p chromium-bsu - Schneller, scrollender Space Shooter im Arkadestil p

Bug#1005083: Chromium 99 update

On 2/16/22 00:08, Timothy Pearson wrote: There is a long and complex history here, much of it out of the public eye, but the long and short of it is that Google simply doesn't want to put effort into supporting an architecture it doesn't use / ship hardware products (Chromebook / Pixel) for.

Bug#989377: chromium: keymap changes with xmodmap after chromium launches cause problems

On Wed, 2 Jun 2021 03:17:50 -0400 Jason Woofenden wrote: > Package: chromium > Version: 90.0.4430.212-1 > Severity: normal > > Dear Maintainer, > > Thanks for all your work on packaging chromium, I imagine that this > is a big job! > > My keyboard lacks an AltGr key, so I use xmodmap to turn my

Bug#1005083: Chromium 99 update

On Tue, 8 Feb 2022 14:16:26 -0600 (CST) Timothy Pearson wrote: > Here is a verified patch to enable ppc64el support on the Chromium 99 version in experimental. I also fixed the build issue with the PDF viewer web optimization that (probably?) impacts all architectures on (at least) sid. > >

Bug#1005808: chromium: ERR_SSL_VERSION_OR_CIPHER_MISMATCH after upgrade to 98.0.4758.80

On Tue, 15 Feb 2022 14:13:38 +0100 Benoit Panizzon wrote: > Package: chromium > Version: 98.0.4758.80-1~deb11u1 > Severity: important > X-Debbugs-Cc: t...@security.debian.org > > Dear Maintainer, > > It looks like some 'outdated' version of SSL has been completely disabled with the newest

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#1005410: chromium: debug trap warning on browser start up

On 2/13/22 13:56, 10dmar10 wrote: Hm, that's new. What does that backtrace look like if you install the chromium-dbgsym package? There is no such package available in testing... Oh, you have to add the debug repository to apt (replacing "unstable" with testing or whatever you're using):

Bug#1005410: chromium: debug trap warning on browser start up

On Sat, 12 Feb 2022 23:30:48 +0100 10dmar10 <10dma...@gmail.com> wrote: > Package: chromium > Version: 98.0.4758.80-1 > Severity: minor > > Hi, > > since upgrading chromium to 97.0.4692.99-1 (and still present in 98.0.4758.80-1) > I noticed some debug breakpoint warnings in the system log. >

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#1005169: regression: Chromium is not using plasma file dialog anymore since overlast update

On 2/8/22 23:55, Andres Salomon wrote: On 2/8/22 13:25, Matthias Gies wrote: Hi, thanks for the quick response. "echo $XDG_CURRENT_DESKTOP" returns "KDE" "dbus-update-activation-environment --systemd XDG_CURRENT_DESKTOP" does not return anything. No chang

Bug#1005169: regression: Chromium is not using plasma file dialog anymore since overlast update

On 2/8/22 13:25, Matthias Gies wrote: Hi, thanks for the quick response. "echo $XDG_CURRENT_DESKTOP" returns "KDE" "dbus-update-activation-environment --systemd XDG_CURRENT_DESKTOP" does not return anything. No change in behavior after restarting Chromium. Still stuck with GTK file dialog.

Bug#985934: chromium: Built in update feature appears to be enabled

On Sun, 28 Mar 2021 18:44:48 +0200 Michel Le Bihan wrote: > Hello, > > Are you sure that you were using Chromium from the Debian package? > > Michel Le Bihan > > > Hi, I don't know if you saw Michel's response. Can you please let us know if it was the debian package chromium (the About

Bug#1005169: regression: Chromium is not using plasma file dialog anymore since overlast update

On Tue, 08 Feb 2022 12:55:39 +0100 Matthias Gies wrote: > Package: chromium > Version: 98.0.4758.80-1~deb11u1 > Severity: normal > X-Debbugs-Cc: matthiasg...@gmail.com > > Dear Maintainer, > > I chose to use chromium over firefox because it it used the regular plasma file > dialog. Since the

Bug#1003622: chromium: microphone stopped working after upgrade

On Sat, 22 Jan 2022 17:21:05 +0100 Francesco Poli wrote: > On Thu, 20 Jan 2022 19:45:48 -0500 Andres Salomon wrote: > > [...] > > Upstream seems to have a lot of bugs with audio sandboxing, so this > > narrows it down quite a bit. > > Good. > > Does any of the

Bug#1004521: lsof: New upstream release (4.94.0, 2020 Nov 10)

On 1/29/22 15:05, Florian Ernst wrote: Package: lsof Version: 4.93.2+dfsg-1.1 Severity: wishlist Dear maintainer, there is a new upstream release available, cf. , including numerous changes / bugfixes. Please update the package when you

Bug#1003689: chromium: Chromium doesn't start

On 1/27/22 18:50, Amr Ibrahim wrote: Hello, I just want to give a small guide into how to enable Wayland again for people like me who prefer Wayland and it works well for them: 1. Start chromium 2. Type chrome://flags in the address bar 3. Search for ozone 4. Change "Preferred Ozone platform"

Bug#1004368: chromium: "Stack smashing detected" messages

On Wed, 26 Jan 2022 03:50:53 +0200 Spiky Caterpillar wrote: > > Chromium complains about stack smashing whenever started. I'm starting it from > an xterm, and the output when starting to a blank tab with Google as the search > engine is: > >

Bug#970831: please include a config snippet for nginx that includes the fpm unix socket

reopen 970831 reassign 970831 php8.1-fpm thanks This bug remains relevant to 8.1.

Bug#1003952: chromium: Can't attach tab to window or move tab window horizontaly

On Tue, 18 Jan 2022 15:43:48 +0100 Florian Goth wrote: > Package: chromium > Version: 97.0.4692.71-0.1~deb11u1 > Severity: normal > Tags: upstream > X-Debbugs-Cc: t...@security.debian.org > > Dear Maintainer, > > chromium-97 contains a bug with moving the tabs. It is fixed upstream with version

Bug#1003753: Acknowledgement (chromium: chromium --temp-profile window displays only as a white box)

On 1/23/22 14:52, Salvatore Bonaccorso wrote: Source: chromium Source-Version: 97.0.4692.99-1~deb11u1 On Sun, Jan 23, 2022 at 01:30:04PM -0600, Karl O. Pinc wrote: Hello, Upgrading to the latest chromium seems to have fixed the problem of the window being displayed as a white box without any

Bug#988781: hurfbuzz: please package harfbuzz-subset

On Tue, 8 Jun 2021 15:17:15 +0200 Mattia Rizzolo wrote: > Hi Emilio, > > thanks for reaching back. > > On Tue, Jun 08, 2021 at 11:55:03AM +0200, Emilio Pozuelo Monfort wrote: > > > Could you please consider including it in the Debian packaging? > > > > It's not packaged because the API was (maybe

Bug#994888: chromium: chrome://extensions/ broken

On Wed, 12 Jan 2022 16:51:02 +0100 Stefano Callegari wrote: > Package: chromium > Followup-For: Bug #994888 > > Dear Maintainer, > > the last version seems back to work all th chrome:// listed above. > > But Amazon Music still to ask me to update... > Thank you for the update. I'm going to

Bug#1004155: dino-im: new upstream version

On Fri, 21 Jan 2022 16:20:50 -0500 Andres Salomon wrote: > > I ran into a dino-im bug (couldn't hear output from audio calls), and > in attempting to debug it I realized that there's been a new > upstream release of dino-im and a bunch of commits on top of that. Ugh, for the recor

Bug#1004155: dino-im: new upstream version

Package: dino-im Version: 0.2.1+git20210824.93e2e0d-1 Severity: wishlist Hi, I ran into a dino-im bug (couldn't hear output from audio calls), and in attempting to debug it I realized that there's been a new upstream release of dino-im and a bunch of commits on top of that. It would be great if

Bug#1003689: chromium: Chromium doesn't start

On 1/21/22 03:21, Martin Dosch wrote: Hi, there you go. Best regards, Martin Thanks! Wow, okay, this is not what I expected. The upstream version has hardware acceleration disabled for your graphics hardware. Yet it's only disabled if running in wayland native mode; it's enabled for X11

Bug#1003689: chromium: Chromium doesn't start

On 1/21/22 03:04, Martin Dosch wrote: Hi, On 20.01.2022 19:51, Andres Salomon wrote: I uploaded 99.0.4818.0-0.1 to experimental. It would be really helpful if you could also test with that version, so I can figure out if the wayland graphics problem is introduced by debian's various patches

Bug#1003689: chromium: Chromium doesn't start

On 1/17/22 05:20, Martin Dosch wrote: Hi, On 17.01.2022 03:00, Andres Salomon wrote: I would encourage both of you to also grab a stock chromium binary from upstream (via snap or whatever mechanism you prefer), and file bug reports upstream if --ozone-platform=wayland still fails to run

Bug#1003736: chromium: Casting via website provided app causes crash

On Fri, 14 Jan 2022 19:27:49 -0500 Andres Salomon wrote: > On Fri, 14 Jan 2022 19:45:16 +0200 Kyle Robbertze wrote: > > Package: chromium > > Version: 97.0.4692.71-0.1 > > Severity: normal > > > > Dear Maintainer, > > > > When castin

Bug#1003622: chromium: microphone stopped working after upgrade

On 1/19/22 17:37, Francesco Poli wrote: $ chromium --disable-features=AudioServiceSandbox gives no warnings and the microphone seems to work on $ chromium --disable-features=AudioServiceOutOfProcess again gives no warnings and the microphone seems to

Bug#1003861: chromium: IME cannot be used in chromium

On Mon, 17 Jan 2022 11:28:28 +0800 Zhaofeng Yang wrote: > Package: chromium > Version: 97.0.4692.71-0.1~deb11u1 > Severity: important > > Dear Maintainer, > > After upgrading my chromium to 97.0.4692.71-0.1~deb11u1 from > bullseye-security, I find that it IME cannot be used to type non-latin >

Bug#1001036: chromium: build-depends on uglifyjs.terser which is going away

On 1/20/22 16:13, Jonas Smedegaard wrote: Also, if you are talking about the semi-official¹ backports target in Debian, then I am not sure if fallback-dependencies are taken into account or deliberately suppressed for the reason of ensuring reproducibility, same as for the official targets.

Bug#1001036: chromium: build-depends on uglifyjs.terser which is going away

On 1/20/22 15:26, Jonas Smedegaard wrote: Hi Andres, Quoting Andres Salomon (2022-01-20 19:46:13) On Thu, 02 Dec 2021 22:41:48 +0100 Jonas Smedegaard wrote: Source package chromium build-depends on uglifyjs.terser which will soon be dropped. Please instead build-depend on package terser

Bug#861796: fixed in chromium 97.0.4692.71-0.1

reopen 861796 thanks On Mon, 10 Jan 2022 22:04:37 + Debian FTP Masters wrote: > Source: chromium > Source-Version: 97.0.4692.71-0.1 > Done: Andres Salomon > > We believe that the bug you reported is fixed in the latest version of > chromium, which is due to be installed

<    1   2   3   4   5   6   7   8   9   >