*** This bug is a duplicate of bug 1967632 ***
https://bugs.launchpad.net/bugs/1967632
Hi, Pascal. The snap with the new pcscd interface is awaiting approval
from the Snapcraft team.
Once that is done I'll post here so that someone can attempt to verify
the fix.
> I think I incidentally
Daniel, thanks a lot for guiding the debugging on this, and Andreas for
carrying the debugging out.
I thought incorrectly that this was already stated: The leak does not
happen with VAAPI disabled
--->
chromium
--disable-features=VaapiVideoDecoder,VaapiVideoEncoder,VaapiVideoDecodeLinuxGL
** Tags removed: hwacc
** Tags added: kivu
--
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/2009739
Title:
hwacc build crashes on direct scanout.
Status in chromium-browser
** Tags added: kivu
--
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/2033433
Title:
Chromium leaks tens of gigabytes of pixmaps (in the Xorg process)
after using hardware
> Currently, I have a ~/snap/chromium/common/chromium/Default/Login Data which
> was last modified September 5. So perhaps passwords are still being written
> here.
Does this file have the expected number of entries, with sites you
recognize as having your saved passwords that you cannot
Forgot the attachments, here they are.
** Attachment added: "passwd.png"
https://bugs.launchpad.net/bugs/2011281/+attachment/5699821/+files/passwd.png
** Attachment added: "login-data.dump"
https://bugs.launchpad.net/bugs/2011281/+attachment/5699822/+files/login-data.dump
--
You
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => 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/2035220
Title:
cve-2023-4863
Status in
Thanks, it seems you already pinned down the issue, I'll investigate how
to get the newer Mesa in (I think that's provided by a gnome-* snap) and
all the following is just for completeness.
Can you attach the following information?
--->
snap info chromium firefox
snap connections chromium
snap
Public bug reported:
https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic-
amd64.duplicity_1.2.2-1_BUILDING.txt.gz
** Affects: duplicity (Ubuntu)
Importance: Undecided
Assignee: Nathan Teodosio (nteodosio)
Status: Triaged
** Tags: ftbfs
--
You received this bug
** Patch added: "duplicity.diff"
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+attachment/5700826/+files/duplicity.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2035360
Title:
GPU hangs in SketchUp on Intel gen12 due
Asked about the possibility of a rebuild at
https://github.com/ubuntu/gnome-sdk/issues/167.
** Bug watch added: github.com/ubuntu/gnome-sdk/issues #167
https://github.com/ubuntu/gnome-sdk/issues/167
--
You received this bug notification because you are a member of Desktop
Packages, which is
For consistency I followed the maintainer's patch style.
** Patch added: "duplicity.diff"
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+attachment/5700853/+files/duplicity.diff
** Patch removed: "duplicity.diff"
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Committed
** Changed in: firefox (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Description changed:
For chrome apps, the create shortcuts action should create desktop files
but it d
Yes.
>logfile 2>&1 snap run chromium --enable-logging
If that doesn't prove sufficient you can also add --v=1.
Having journalctl -f running at the same time will allow you to see
Apparmor denials.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Duly reproduced. I don't have SSH set up here and couldn't get out with
Ctrl+Alt+Backspace either, had to resort to Sysrq.
The journal shows a nouveau fault at the time of the crash.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
** Changed in: chromium-browser
If you hit that again can you please also retrieve the log?
--
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/2033433
Title:
Xorg 100% CPU and frozen desktop after closing
The journal and
>log 2>&1 snap run --strace='-o strace' chromium --enable-
logging=stderr
would be very thorough if that runs fine.
Thanks for testing and have a good crash!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Critical
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug not
Marking Firefox as fix released as well since now Firefox is on core22
and that was confirmed in earlier comments to solve the problem. Please
reset if observed otherwise.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser
Santiago, Spotify is proprietary, there is nothing for us to do. You
have to request them to update their base from core20 to core22.
According to 'snap info spotify', their contact link is
https://community.spotify.com/t5/Desktop-Linux/bd-p/desktop_linux.
** No longer affects: snapd (Ubuntu)
For your information, Chromium is now in 116.0.5845.187 in x86, and
should be in ARM too tomorrow.
--
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/2035220
Title:
In bug description:
1> when I went to use my saved passwords in chromium today, I found that
they were absent.
In your last comment:
2> chromium continues to be able to *use* my saved passwords. But I
don't know where they're actually saved
Which one is correct/up to date?
Likewise for
3>
** This bug is no longer a duplicate of bug 1732482
[snap] doesn't properly save desktop files for "create shortcuts" action
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
** Description changed:
https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic-
amd64.duplicity_1.2.2-1_BUILDING.txt.gz
+
+ For the record this builds fine with the latest upstream release
+ setup.py so I'm not poking them.
--
You received this bug notification because you are a
With the help of 3v1n0 it's confirmed that this is Mutter interpretation
of a sandboxed application.
Whether this is a bug is then a matter of opinion and actually
complicated[1].
You may need to convince Gnome maintainers about it or use another
desktop environment.
[1]
The Gnome snap has been built with a newer Mesa.
Could you try
snap refresh --candidate gnome-42-2204
and then start the browser? Does the issue go away?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Public bug reported:
Builds successfully in Mantic.
** Affects: network-manager-applet (Ubuntu)
Importance: Wishlist
Status: Confirmed
** Patch added: "nma.diff"
https://bugs.launchpad.net/bugs/2039460/+attachment/5709932/+files/nma.diff
--
You received this bug notification
The last patch wouldn't build in Jammy due to older Glib, this one
builds there too (attached build log in Jammy).
** Patch added: "xdg-deskop-portal-gtk3.diff"
https://bugs.launchpad.net/bugs/2039187/+attachment/5709124/+files/xdg-deskop-portal-gtk3.diff
** Attachment added:
> According to the chromium documented cited, this is wrong.
Maybe it's a different way of interpreting the terminology.
If it applied a rot13 to your password (of course that would be very
stupid but it's just for the sake of the argument) and stored that in a
file, I could say that it is
> What is there to prove? The documentation *literally* says it is plain
> text.
The documentation isn't the code that is executed. The only source of
truth is code and the proof is in the pudding, namely execution. However
that was not my point at all, you didn't read what I said carefully
*** This bug is a duplicate of bug 1996267 ***
https://bugs.launchpad.net/bugs/1996267
That is a good target for a duplicate, marking it accordingly, thanks
for the heads-up.
** This bug has been marked a duplicate of bug 1996267
[snap] Doesn't store encrypted passwords unless interface
I'm proposing changing the version number from 1:85.0.4183.83-0ubuntu3
to 2:1+snap, similar to what Firefox does.
** Description changed:
For Ubuntu >= Focal the transitional debs are frozen at the version
number 1:85...
- This might make one think[1] that it will install a critically
Great! Thanks for testing. This will slowly flow into other channels.
--
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/2038727
Title:
Chromium snap theme parsing error
Status
Hi Lukas, thanks for having a look!
> But I wonder if we should rather change the version number to
> "2:1snap1-0ubuntu1", in order to use a similar format as we have on
> Firefox (LP: #1892724)? What do you think?
So, my hunch reaction to that scheme is "god, are all those numbers
really
Parallel install is OK, I committed the fix for that weeks ago... In the
wrong branch. (:
Rebuilt now, with my limited connection I cannot donwload it to test it,
but I tested by making local changes by unsquashing and trying the snap.
Can you please give it another try and let me know? The
Thanks for having a look, Bryce.
I addressed your points; the build is [2].
Should I always propose the debdiff with the release name instead of
UNRELEASED even though it is unreleased at that given point? I'm used
not to, but maybe that's something particular of Gnome[1].
[1]
Public bug reported:
Works for nautilus, gnome-{power-statistics,disks}.
Doesn't work for gnome-{control-center,text-editor,calculator,calendar},
which remain on light mode.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu2
ProcVersionSignature: Ubuntu
ADW_COLOR_SCHEME_FORCE_DARK=. fixes it but only in a Gnome environment.
--
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/2042077
Title:
Dark mode only works for some GTK windows
** Attachment added: "Screenshot from 2023-10-31
10-47-43.png"
https://bugs.launchpad.net/bugs/2042077/+attachment/5714608/+files/Screenshot%20from%202023-10-31%0A%2010-47-43.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Thanks for the report. Do you recognize your issue in LP:2007652?
If you right click and add to favorites, does the icon show on the dock?
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages,
*** This bug is a duplicate of bug 2007652 ***
https://bugs.launchpad.net/bugs/2007652
Yeah sorry about that, this is actually the way Gnome Shell interprets
sandboxed applications — other desktop environments have the desired
behavior.
** This bug has been marked a duplicate of bug 2007652
** Bug watch added: Mozilla Bugzilla #1849961
https://bugzilla.mozilla.org/show_bug.cgi?id=1849961
** Also affects: chromium-browser via
https://bugzilla.mozilla.org/show_bug.cgi?id=1849961
Importance: Unknown
Status: Unknown
** No longer affects: chromium-browser
** Also
For some reason some binaries are no longer making it into the snap. :|
I'm investigating...
--
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/1967632
Title:
[snap] apparmor
Thanks for your input Gunnar, that might be really playing a role in the
problem.
After all, it turns out the error Andreas reported is also present when
the behavior is correct, i.e. with ubuntu-fonts-classic I get
--->
Failed to get origin+type directory: { uri:
No problem, Simon, thank you for responding and sponsoring!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/2039460
Title:
Please merge network-manager-applet 1.34.0-1
This is supposedly fixed in edge and beta channels (x86 and ARMv8):
snap refresh --edge chromium
#Or
snap refresh --beta chromium
#And then connect the required plugs:
snap connect chromium:dot-local-share-applications
snap connect chromium:dot-local-share-icons
Your
Yesterday I got crashes whenever I tried to maximize it or resize it.
I started Ubuntu on Wayland from SDDM though.
After I started it from GDM I no longer reproduce the problem, although
I rebooted in between so...
I didn't get a crash file in /var/crash. I attach the journal from
yesterday,
Sorry, I hadn't seen you already had done those tests in the linked bug
report.
> the chromium snap needs the updated MESA library
It uses the one gnome-42-2204 exposes. If migrating to candidate didn't
help, then the problem should be something else.
--
You received this bug notification
The problem looks to be
var bodyinput = yield session.send_async (message, 1, new
GLib.Cancellable());
That is not the signature of the function and it doesn't return the body
input.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => New
** Changed in: firefox (Ubuntu)
Status: Fix Committed => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
I will, but just to update expectations: Each revision of Chromium in
beta and edge need to be manually reviewed because of a new plug[1].
So expect some a couple of days of delay. Or install it manually from
[2].
[1]
Andreas noticed in the duplicate report that
> The chromium console log also shows a lot of these 404 errors for *.woff2
> fonts:
>
> GET
> filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2
> net::ERR_FILE_NOT_FOUND
--
You received this bug
Thanks Ludovic, so for those smart cards, the pcscd interface has been
merged in Snapd (but is apparently only available from 2.60.4 on, so
currently you need the beta channel of it), and so I update the test
case to a simpler:
--->
snap refresh --beta snapd
snap refresh --channel stable/pkcs
*** This bug is a duplicate of bug 2019045 ***
https://bugs.launchpad.net/bugs/2019045
Thanks for the report, Andreas, this is a duplicate of LP:2019045, you
noticed something important in the log and I'm passing your comment to
that report.
** This bug has been marked a duplicate of bug
Hi Peter, thanks for doing that!
> as it says in my other post i did try running with --disable-gpu
No, you tried chromium --disable-gpu-driver-bug-workarounds, which is
not the same.
> there was a new Chromium snap this morning, and it seems to have fixed
the bug! yay! my props to the dev team
*** This bug is a duplicate of bug 2037151 ***
https://bugs.launchpad.net/bugs/2037151
** This bug has been marked a duplicate of bug 2037151
Chromium glitches, Brave too, might be GPU
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Great, thanks for your continued testing on this bug report!
I'm pushing it to beta as well.
--
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/2033433
Title:
Chromium leaks
This is now released to beta and edge.
And thank you, Jianhui, for contributing the fix!
** 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
As said in #12 this should be fixed by now.
If not, please state if this is observed in both programs (Libreoffice
and Chromium) or only one of them or a different one, and also attach
the output of
apt list --installed | grep desktop-portal
** Changed in: chromium-browser (Ubuntu)
** 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/1732482
Title:
[snap] doesn't properly
Hi Peter, thanks for trying to submit a bug report via Apport. As it
seems it initially failed to target the correct package, can you try
'apport-collect 2037151'?
Is the issue reproducible if you completely disable hardware
acceleration, i.e. 'chromium --disable-gpu'? What if you revert to the
I'm committing this to edge only as there are reports of H264 failure in
the upstream tracker. Let's see if we can reproduce it.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages,
Thanks for the report, Gloria.
Can you please run 'apport-collect 2037093'?
Is the issue reproducible if you disable hardware acceleration, i.e.
'chromium --disable-gpu'? What if you revert to the previous revision
with 'snap revert chromium'?
Does Chromium report something suspicious in
Thanks for testing!
Julian, I think you already know that and just wanted to perform
thorough testing, but in case it was not clear, the fix is not yet in
stable.
Yet you noted something in test case A:
> File chrome-pdplehbldmmknfihajdehomkoigcbhib-Default.desktop was
created in ~/Desktop
Did
WBGSReject, you seem to have tested stable! And apparently you observed
the same as Julian (#34) in test A. So I also extend my question to you:
Do you expect the PWA on the desktop or as a launcher?
I'll be investigating if there is any consensus on that, but otherwise I
might simply combine the
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: libreoffice (Ubuntu)
Status: Incomplete => Fix Released
--
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: 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/1732482
Title:
[snap] doesn't properly
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
--
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/2038727
Title:
Chromium snap theme parsing
Given that this stopped working for you exactly in 117.0.5938.149, which
included some related changes (e.g. changing the default XDG_DATA_HOME),
one of them is probably affecting you here.
But before we continue, please clarify this: You only notice it not only
in the stderr log but also in
Well true, I'm removing the duplicate mark, however it does explain why
we cannot do this:
https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and-
password-manager-service-interfaces-for-the-chromium-snap/4592/6
** This bug is no longer a duplicate of bug 1836616
[snap] Upgrade
Andy, I released a tentative fix to the edge channel.
If you want to try it, refresh your snap with
snap refresh --edge chromium
Please note that a transition back to stable channel might not always be
smooth (e.g. password storage can become incompatible), so you could
generate a snapshot
)
Importance: Undecided
Assignee: Nathan Teodosio (nteodosio)
Status: Confirmed
** Tags: patch
** Patch added: "xdg-deskop-portal-gtk.diff"
https://bugs.launchpad.net/bugs/2039187/+attachment/5708881/+files/xdg-deskop-portal-gtk.diff
--
You received this bug no
So I followed up there and now I know the full recipe for you, with no
need to worry about backwards incompatibility:
* [Create a snapshot] snap save chromium
* [Switch to edge] snap refresh --edge chromium
* Launch Chromium normally, see if the problem is fixed
* [Switch back to stable (if
Ah, sorry, silly I dispatched builds a bit before I committed changes.
At least both of us learned something new about the snapshots.
I'll build again and let you know, thanks for your disposition in
testing the fix.
--
You received this bug notification because you are a member of Desktop
> I don't see how this debate is apropos. Whether or not the passwords
are stored in the clear, or obscured with symmetric encryption using
hard coded parameters in chrome is irrelevant. Both of these scenarios
are entirely unacceptable.
You are right, but if a statement presented as a certainty
Another possible hint to collect: Does this happen both in X11 and
Wayland?
--
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/2039701
Title:
chromium freezes gnome if hardware
> Was able to reboot with strg+alt+F(x) sudo reboot
Once this happens again, can you please collect dmesg and journalctl
(some hundreds of lines are probably enough) before rebooting?
Instead of launching Chromium normally, use
chromium --enable-logging=stderr > chromium.log 2>&1
Also:
Thanks for the report.
Cannot reproduce. The bookmark manager is chrome://bookmarks/, right?
Anyway, this would be most likely a ticket for upstream to tackle,
crbug.com.
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
If password-manager-service is connected with
snap connect chromium:password-manager-service
then it uses the operating system's key ring.
So are you pointing out that Chromium ought to use gnome-libcrypt
instead of basic when no key ring is detected?
--
You received this bug notification
** 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/2038875
Title:
Snap uses hardcoded key and salt for password and cookie encryption
Status in
> --->
> How do you set your theme?
>
> I set my theme using xfce4-settings-manager "Appearance" and "Window Manager"
> selections. Should I be doing something else?
> <---
I don't think so, that should be a valid use case, we can surely rule
out the possibility of XFCE setting the system
What is $HOME/.config/gtk-3.0/settings.ini?
--
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/2038727
Title:
Chromium snap theme parsing error
Status in chromium-browser
Do you have a reproducer recipe?
I tried with various themes I found in /usr/share/themes:
GTK_THEME=Yaru-viridian chromium
GTK_THEME=Yaru-blue chromium
and it seems to be working fine.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** 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/2038727
Title:
Chromium snap theme
** 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/1836616
Title:
[snap] Upgrade from deb to snap forgets saved passwords
Status in
*** This bug is a duplicate of bug 1836616 ***
https://bugs.launchpad.net/bugs/1836616
Found the duplicate target; See there that the interface auto-connection
was denied by Snap Store.
** This bug has been marked a duplicate of bug 1836616
[snap] Upgrade from deb to snap forgets saved
heme
in one case and a dark one in other, I don't know yet.
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Tags added: regression
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug no
Can you ascertain if your smart card is supported by OpenSC?
--
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/1967632
Title:
[snap] apparmor denied when trying to load pkcs11
Hi Lucas, thanks for having a look.
> Just to understand a bit better, is this bug affecting just Jammy? Any
> other Ubuntu series? Please target the correct series in the bug.
No, it goes all the way to Focal. The mention to Jammy was because in
the upstream pull request the first version of
OK, hang on, the title claims that Gnome crashes if hardware
acceleration is activated. You are now reporting problems also with it
deactivated, right?
> If its turned off then it is ok. But it crashed anyway when the
indicator applet was showing incoming mail last time.
With hardware
** Patch removed: "xdg-deskop-portal-gtk2.diff"
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+attachment/5709117/+files/xdg-deskop-portal-gtk2.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Workaround:
apt install fonts-ubuntu- fonts-ubuntu-classic
--
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/2019045
Title:
[snap] New Ubuntu font with normal weight
The new font relies on some different mechanism to determine the style
of a given typeface, as each different style points to a same file. The
old font doesn't do that. Maybe that could be tripping the resolution.
--->
# ubuntu-fonts
lrwxrwxrwx 1 root root 20 jun 21 10:35 UbuntuMono-B.ttf ->
I see the bug is addressed, but for what it's worth, one more data
point.
I just run into the issue today when doing
apt remove fonts-ubuntu*
What I didn't notice was that a replacement instead of a removal was
carried out
fonts-ubuntu (0.83-6ubuntu1 => 0.869-0ubuntu1)
After a while I
Bold renders fine given simple CSS:
Ubuntu.
Ubuntu bold.
This looks specific to Google Docs.
** Attachment added: "fonts.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+attachment/5712423/+files/fonts.png
--
You received this bug notification because
More information dump:
* It's easier to see the error Andreas mentioned with --enable-
logging=stderr:
--->
[246126:246235:1023/123348.818876:WARNING:obfuscated_file_util.cc(1323)] Failed
to get origin+type directory: { uri:
It's built now, please have a look if it fixes the issue now.
--
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/2038727
Title:
Chromium snap theme parsing error
Status in
*** This bug is a duplicate of bug 1967632 ***
https://bugs.launchpad.net/bugs/1967632
Hi Pascal, not sure you receive notifications for the duplicate, but in
LP:1967632 I have released a tentative fix with a test case.
--
You received this bug notification because you are a member of
1 - 100 of 715 matches
Mail list logo
