** Patch added: "speechd-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+attachment/5674811/+files/speechd-jammy.debdiff
** Changed in: speech-dispatcher (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you
** Patch added: "speechd-kinetic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+attachment/5674789/+files/speechd-kinetic.debdiff
** Changed in: speech-dispatcher (Ubuntu Kinetic)
Status: New => Confirmed
--
You received this bug notification
** Patch added: "speechd-lunar.debdiff"
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+attachment/5674787/+files/speechd-lunar.debdiff
** Changed in: speech-dispatcher (Ubuntu Lunar)
Status: New => Confirmed
--
You received this bug notification because you
** Description changed:
[Description]
Systemd socket activation for Speech Dispatcher.
- Creates the speech-dispatcher.socket;
- Modifies the server so that it can detect it was automatically launched
by that socket activation; and
- Modifies the Autotools files
** Description changed:
[Description]
Systemd socket activation for Speech Dispatcher.
- Creates the speech-dispatcher.socket;
- Modifies the server so that it can detect it was automatically launched
by that socket activation; and
- Modifies the Autotools files
affects: speech-dispatcher (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: speech-dispatcher (Ubuntu Focal)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: speech-dispatcher (Ubuntu Jammy)
Assignee: (unassigned) => Nathan Teodosio (nte
> This bug is not fixed. Still happening for me in Xorg on Mantic.
The fix works for me (mutter 44.1-1ubuntu1).
Did you log out?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2013216
> dont we risk having different versions of speech-dispatcher between
host and snap and potential weird bugs?
Since the patch would have to be backported to Jammy first so that
Firefox could pick it up (I assume we wouldn't want it's snapcraft.yaml
to pick up stuff from a PPA), I thought that a
(In reply to Alexandre LISSY :gerard-majax from comment #19)
> (In reply to Nathan Teodosio :nteodosio from comment #18)
> > I built the patched speech-dispatcher in a PPA[1] and then a snap[2] with
> > spd-say to test
> >
> > After installing them,
> >
I built the patched speech-dispatcher in a PPA[1] and then a snap[2]
with spd-say to test
After installing them,
systemctl start --user speech-dispatcher.socket
snap run --shell geheim
$ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi
[1]
** Attachment added: "speechd.debdiff"
https://bugs.launchpad.net/bugs/1991022/+attachment/5672708/+files/speechd.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to speech-dispatcher in Ubuntu.
** Description changed:
[Description]
Systemd socket activation for Speech Dispatcher.
- Creates the speech-dispatcher.socket;
- Modifies the server so that it can detect it was automatically launched
by that socket activation; and
- Modifies the Autotools files
** Description changed:
I am experiencing a rendering regression after upgrading from Kinetic to
Lunar.
Google Docs using the Ubuntu font family are displayed incorrectly in
Chromium: the normal weight font is rendered identically to the bold weight
one, instead of being thicker than light
> One thing that may be relevant: if I force-refresh my test Google Doc
I see all four Ubuntu font lines initially being rendered as bold. The
light and medium lines are then re-rendered with the correct weight.
It's as if bold was the default weight and the normal variant
disappeared.
I can confirm this with the new font 0.863-0ubuntu3, though not with the
0.83-6ubuntu1.
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** Also affects: fonts-ubuntu (Ubuntu)
Importance:
** Description changed:
To test the snap with VA-API changes,
1. Install the Chromium snap,
- sudo snap install --channel stable/hwacc chromium
+ sudo snap install --channel candidate/hwacc chromium
2. Start Chromium,
snap run chromium
3. Open a video, e.g. one
Solved with "apt install gnome-desktop^", which, apropos, removed
Pulseaudio from my system.
** Attachment added: "mkv.log"
https://bugs.launchpad.net/bugs/2018972/+attachment/5671863/+files/mkv.log
** Attachment added: "mp4.log"
Public bug reported:
I use simplescreenrecorder to record screen.
If I use ALSA, I can play the recorded videos with MPV, i.e. all is
fine.
If I use Pulseaudio, the resulting videos are not playable. Attached is
the output of mpv -v -v for each of them.
PS: I cannot screen cast with the Gnome
** Description changed:
Possible, proposed solutions
- Please install from these channels and report back with success or
- failure.
+ Option 1: Please install from these channels and report back with
+ success or failure.
- snap refresh --channel
** Changed in: chromium-browser (Ubuntu)
Importance: Low => Medium
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
> there also doesn't seem to be anywhere in settings to turn it off
If you don't like it you can snap remove cups?
** Changed in: chromium-browser (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Sorry, there won't be a new release for Bionic. Since there is no reason
this would not apply to the snap too, I leave the bug report for the
package open.
** Changed in: chromium-browser (Ubuntu Bionic)
Status: New => Won't Fix
--
You received this bug notification because you are a
Thanks for the bug report and sorry for the delay responding to this.
Is there an unwanted behavior resulting from this mismatch? You mention
that the mismatch fixes Youtube playback so it wouldn't look worth
"fixing" this?
** Also affects: chromium-browser (Ubuntu Bionic)
Importance:
Thanks for the additional data points, that is much appreciated.
** Description changed:
+ Possible, proposed solutions
+
+
+ Please install from these channels and report back with success or
+ failure.
+
+ snap refresh --channel candidate/core22 firefox
+
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2016972
Title:
Chromium snap does not
Thanks for testing, that's good news.
CBCM is disabled since the build is not Chrome branded; That diagnostic
message is expected.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Any change the edge channel (in which we have now more up to date
libraries) works for you?
sudo snap refresh --edge chromium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Closing as Floc has been removed and didn't come back.
** Changed in: chromium-browser (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => (unassigned)
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification becau
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1987137
Title:
Migrating chromium-browser to
Good news, I got core22 on edge/hwacc. The problems here list apparently
went away in the meantime.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1987137
Title:
Migrating
Chromium built with core22 is available at edge/hwacc. It would be great
if you could test it on the target hardware.
I ran the manual tests and could detect no regression, although I can’t
test video playback due to a bug I’ve hit (unrelated to Chromium).
--
You received this bug notification
> Maybe this is helpful - a difference I noticed in the output of chromium
> when run without and with the --disable-gpu flag is that, when run
> without it there is a log line
>
> amdgpu: os_same_file_description couldn't determine if two DRM fds
> reference the same file description.
>
> while
I can verify that in Bionic (with the deb) the application shows in
Gnome's task bar as a separate application, not grouped under Chromium,
and that in Lunar (with the snap) it shows in Gnome's task bar grouped
under the Chromium button.
However,
1. Wmctrl shows that the window classes and
** Attachment added: "xprop"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+attachment/5664802/+files/google-chat.xprop
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Thanks for providing a reproduction case.
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2007652
For your information, if trying this in a snap, make sure to supply a
correct XDG_RUNTIME_DIR as that seems to be modified by snapcraft or
snapd.
Namely, in a `snap run --shell {snap-name-with-spd}`, this fails:
```
$ spd-say bye
Failed to connect to Speech Dispatcher:
Error: Can't connect to
I tried
https://github.com/brailcom/speechd/commit/4fc86d73a87c9e120489b89b43d4e9423b68df4f
and that seems to have solved the problem here!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
** Tags added: ftbfs
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to screen-resolution-extra in Ubuntu.
https://bugs.launchpad.net/bugs/2015777
Title:
Fix build for screen-resolution-extra 0.18.2 on Lunar
Status in
Can give an example for testing?
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2007652
Title:
: Undecided
Assignee: Nathan Teodosio (nteodosio)
Status: Confirmed
** Patch added: "a.patch"
https://bugs.launchpad.net/bugs/2015777/+attachment/5662758/+files/a.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
> According to upstream, some of the problems with socket activation are
now fixed. Let's give a new try to this feature.
Alexander, even with e7e188 in, I couldn't get the socket activation to
actually work[1].
[1] https://github.com/brailcom/speechd/issues/809
--
You received this bug
Public bug reported:
Some custom shortcuts with super key will not work. The failing ones I
found:
Super + {1..9}
--
These will say
> Super+{Number} is already being used for Activate favorite app 9. If
you replace it, Activate favorite app 9 will be disabled.
That is not what
** Description changed:
Single clicking the title bar of windows without a complex title bar
(namely a title bar with additional buttons besides the
close/maximinze/minimize) does not transfer focus to them.
+
+ Reproduction recipe:
+
+ 1. Open gnome-terminal.
+ 2. Run xedit.
+ 3. Focus
Public bug reported:
Single clicking the title bar of windows without a complex title bar
(namely a title bar with additional buttons besides the
close/maximinze/minimize) does not transfer focus to them.
I can reproduce this in my main, up to date Lunar system in Xorg and
also in a virtual
This issue happens for each individual volume.
I cannot trigger the bug again by dismounting and trying again; Nautilus
opens fine in that case.
I can only trigger the bug again for a said volume after rebooting.
--
You received this bug notification because you are a member of Desktop
** Tags added: rls-ll-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2013070
Title:
100% CPU after clicking a mountable in the dock
Status in gnome-shell package in
** Description changed:
I click a mountable volume in the Gnome dock, gnome-shell starts
consuming 100% CPU and also it misbehaves: New windows don't show up, if
you try to logout via upper-right corner > Log out it doesn't show the
log out dialog.
Killing it twice restores a working
Public bug reported:
I click a mountable volume in the Gnome dock, gnome-shell starts
consuming 100% CPU and also it misbehaves: New windows don't show up, if
you try to logout via upper-right corner > Log out it doesn't show the
log out dialog.
Killing it twice restores a working session.
** Changed in: software-properties (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/2006940
Title:
PIN validation
Public bug reported:
The latest Debian version of Deja Dup is
--->
deja-dup (44.0-2) unstable; urgency=medium
* debian/control:
- Suggests: python3-pydrive2
* debian/rules:
- set -Dpydrive_pkgs=python3-pydrive2 since it's not available in Debian
*
** Patch added: "Debdiff between tiff_4.5.0-5 and tiff_4.5.0-5ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+attachment/5656640/+files/deb-ubu.diff
** Patch removed: "deb-ubu.diff"
** Patch added: "debdiff between tiff_4.5.0-4ubuntu1 and tiff_4.5.0-5ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+attachment/5656638/+files/ubu-ubu.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tiff in
** Patch added: "deb-ubu.diff"
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+attachment/5656639/+files/deb-ubu.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tiff in Ubuntu.
Public bug reported:
Please merge tiff 4.5.0-5 from Debian unstable.
** Affects: tiff (Ubuntu)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tiff in Ubuntu.
Actually only the minor part of your problem has been fixed, the
password notice.
Still, the passwords, of course, should not disappear. And in my tests
in the Ubuntu GNOME desktop they really don't.
However, I just tested in my simplified dwm environment and I can
confirm that, although the
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2011589
Title:
Segfault when trying to move/maximize window
Status in nautilus package in Ubuntu:
New
Bug description:
In Kinetic
** Attachment added: "ThreadStacktrace"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654419/+files/ThreadStacktrace
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
** Attachment added: "StacktraceTop"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654420/+files/StacktraceTop
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
** Attachment added: "StacktraceSource"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654421/+files/StacktraceSource
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
** Attachment added: "Stacktrace"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654417/+files/Stacktrace
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
** Attachment removed: "Nautilus crash file"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654401/+files/lac2
** Attachment removed: "ProcCpuinfoMinimal.txt"
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2011589/+attachment/5654403/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2011589/+attachment/5654404/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
** Attachment added: "Nautilus crash file"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654401/+files/lac2
** Tags added: apport-collected
** Description changed:
In Kinetic -- server + gnome package + nautilus/kinetic-proposed package
+ reboot -- under
Public bug reported:
In Kinetic -- server + gnome package + nautilus/kinetic-proposed package
+ reboot -- under Qemu I often get segfaults when trying to
move/maximize Nautilus.
This is without ubuntu-desktop package so I'm not sure as to whether
such a configuration is supported.
ProblemType:
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2008433
Title:
Request to enable
Glad to hear that, and thanks for the cooperation!
** Changed in: chromium-browser (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
** Tags added: password-storage
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2011281
Title:
chromium snap upgrade "lost" my passwords
Status in chromium-browser package
Public bug reported:
I use dwm as my window manager, which I start from console with startx;
Nonetheless the Gnome Keyring running and unlocked,
% ps ax|grep [g]nome-key
2745 ?Sl 0:00 /usr/bin/gnome-keyring-daemon --start --foreground
--components=secrets
2746 ?SLsl
> At this point though, we might just be better off getting rid of that,
since the mentioned fix was released about two months ago and, because
of the snap forcing upgrades, the transition should have been done for
practically all users already.
I confirmed this. Getting rid of the notice.
**
Thanks for the report, Steve.
I agree that it is not user friendly, especially in this case where
things have gone wrong. At least the back up file served its purpose and
you could restore your passwords.
That notice only appears when the user has the password-manager-service
interface
For 113, guide-0.9.1:a49acb3:one-copy.diff fails to apply.
** Tags removed: dev-ok
** Tags added: dev-failed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2006641
Title:
** Also affects: chromium-browser (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: chromium-browser (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Can you please try ppa:canonical-chromium-builds/stage?
https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Indeed, on an upgrade today I got:
--->
dpkg: error processing archive
/tmp/apt-dpkg-install-ufaKMu/10-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also
in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1
<---
Ah, didn't know you were in Bionic. I'll build it in a PPA.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2008433
Title:
Request to enable WidevineCDM checking on ARM64
Marking as "fix committed" but before passing it on to the other
channels I'd need confirmation.
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Improbable that it had anything to do with the problem going away, but
Chromium had a minor release today (.100->.177).
At any rate, I then close this bug, please open set it back to "new" if
it happens again.
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You
Thanks for the detailed report, Franziska. I tried to reproduce it but
Chromium worked alright.
In your test, did you try to open the instances of Chromium to launch at
the same time or at different times?
The most conspicuous error there is
--->
Reverted to working snap. Thanks for the report.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Hi Ivan,
Unfortunate that it fixes the error message but not the bug...
Anyway many thanks for your helpfulness going out of your way to give
the test fix a go, that's much appreciated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Temporary workaround while this isn't solved:
chromium --user-agent='Mozilla/5.0 (X11; Linux x86_64)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36'
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Triaged
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Critical
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug not
Can you please test the snap from the edge channel (snap refresh
--channel edge chromium) and report whether it solves the issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
What can be said is: You can restore **Chromium** passwords that way,
even if you delete all the keyring data.
> This means I can safely delete the hundreds of google chrome
passwords stored in the gnome keyring?
> (under application chrome-16295873)
_That_ I wouldn't go so far as to say.
The passwords are always in "Login Data" (hereby LD) file and remain in
that file.
If the password-manager-service interface (as displayed by 'snap
connnections chromium') is
- connected, then --password-store=gnome and the passwords in Chromium
(stored in LD) are encrypted with a key stored
Martin, if you rename 'Login Data' -> 'Login Data.old' (or whatever
other name), then your passwords will be saved in 'Login Data.old'.
Chromium will not use that file, it only recognizes 'Login Data', so you
will not be able to access the passwords from Chromium until you rename
it back to 'Login
Thanks for the bug report.
The error is
> Run configure hook of "chromium" snap if present (run hook
"configure": cannot locate base snap core20: No such file or directory)
This is probably a transient problem, or at least should be fixable with
snap remove core20
snap install core20
At
Indeed, and, if I'm reading it correctly, that's why widevine-enable-
version-string.patch[1] has changes such as
-#if BUILDFLAG(BUNDLE_WIDEVINE_CDM)
+#if BUILDFLAG(ENABLE_WIDEVINE_CDM_COMPONENT)
Since I don't see why Widevine shouldn't be enabled on Armhf too, I'm
simply removing the
On the hardware acceleration front, there has also been recent fixes to
AMD GPUs failing to find drivers. It's probably unrelated to the present
problem, but if you want to try it anyway, it's on the beta/hwacc
channel:
snap install --channel beta/hwacc chromium
--
You received this bug
Given the error message from chromium.log,
> amdgpu: os_same_file_description couldn't determine if two DRM fds reference
> the same file description.
> If they do, bad things may happen!
I think this might be the kcmp's denial fault.
Can you please execute the following commands to whitelist
Invoking Chromium with --disable-gpu should make the problem go away.
But it is not a solution to the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1948052
Title:
*** This bug is a duplicate of bug 1948052 ***
https://bugs.launchpad.net/bugs/1948052
Invoking Chromium with --disable-gpu should make the problem go away.
But it is not a solution to the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2004586
Title:
Chromium's minigbm uses
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2006646
Title:
hwacc branch builds that
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: chromium-browse
** Merge proposal linked:
https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/437855
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2004586
** Merge proposal linked:
https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/437855
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2006646
Thanks for submitting a report with your patch.
> currently BUNDLE_WIDEVINE_CDM does not get set for arm64 linux (but
does on amd64 linux)
Do you have evidence for amd64 having it bundled? I don't think we
bundle Widevine for any oarchitecture.
As such, I wonder whether the last two sections of
301 - 400 of 715 matches
Mail list logo
