I figured out that there was still an instance of chromium running in
the background. After downgrading to 87.0.4280.141, fonts are working
correctly. The warning message still exists, so I think it is a red
herring.
So there seems to be a regression in how fonts are picked in
88.0.4324.41.
** Su
Forgot to mention running on Ubuntu 20.04.
--
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/1910789
Title:
Font regression in chromium 88 beta
Status in chromium-browser packa
Public bug reported:
When I run chromium, I am getting a weird font in the browser. Sometimes
if you refresh the page, the weirdness might go away. If I run chromium
from the command line, I see the following:
(chrome:1089093): Gtk-WARNING **: 11:50:41.068: Theme parsing error:
gtk.css:1555:23: '
What about the other channels? In particular we need Chromium 85 (for
other reasons) which is the edge channel.
--
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/1887201
Title:
Yes, thank you. I was able to update the post 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/1887201
Title:
[snap] web bluetooth does not work
Status in chromium-browse
This is as far as I got before my account was locked.
https://forum.snapcraft.io/t/request-to-autoconnect-chromium-to-
bluez/18856
--
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
I attempted to post the following request on the snapcraft store to
start the request process, but was not able to because I am a "new" user
(limited to 2 links and one image):
The [chromium](https://snapcraft.io/chromium) web browser has support
for [Web Bluetooth](https://webbluetoothcg.github.i
I can confirm it is working now. Thank you very much for the fix.
Will everyone that wants to use Web Bluetooth have to manually connect
chromium:bluez or will it be connected by default eventually?
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
Public bug reported:
Using the site https://code.pybricks.com, clicking the bluetooth icon
should start scanning for devices (a dialog box should pop up showing
discovered devices). It worked in the debian package of chromium on
Ubuntu 20.04 but today apt installed the snap version instead and
Blu
I assume the patch tag was removed because it has bitrotted?
I have submitted a new patch recently upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=696793
I would really like to see this in 18.04 one way or another. I'm not too
keen on another two years of "ALT+F2 nm-connection-editor" to be
This is a patch that I submitted to Linux Mint to fix this issue (they
maintain a fork of gnome-control-center). It applies cleanly to gnome-
control-center in vivid and I have tested that the package builds and
the patch fixes the problem. I'm not familiar with the patch process for
Ubuntu, so let
Public bug reported:
For those of us that don't want to use gnome-keyring-ssh and use ssh-
agent instead, the changes to fix bug #1271591 prevent us from doing so.
Previously, we were able to disable gnome-keyring-ssh by ediing
/etc/xdg/autostart/gnome-keyring-ssh.desktop and setting
NoDisplay=fa
For those of us that don't want to use gnome-keyring-ssh and use ssh-
agent instead, this breaks our setup.
Previously, we were able to disable gnome-keyring-ssh by ediing
/etc/xdg/autostart/gnome-keyring-ssh.desktop and setting
NoDisplay=false. Then it would be visible in Startup Applications
Pre
Public bug reported:
Using Unity Desktop in Ubuntu 14.04, the application menu in bustle does
not work. You can click the menu itmes and nothing happens.
** Affects: bustle (Ubuntu)
Importance: Undecided
Status: New
** Affects: unity (Ubuntu)
Importance: Undecided
Sta
(In reply to Thomas Sisson from comment #102)
> I'm still having this problem...
Please see comment 97. If your problem sounds like the bug linked there,
you can help by posting more detailed information on that bug, such as
the exact wording of messages that your are seeing or screenshots. If
you
(In reply to Tim K from comment #56)
> (or find
> some extension that maps the Delete key and functionality to "Move to
> Trash").
>
You may find this useful.
https://addons.mozilla.org/en-us/thunderbird/addon/gmailbuttons/
Doesn't have binding to delete key, but at least it has a 'move to
tras
We could take advantage of the X-GM-LABELS and X-GM-MSGID attributes to
fix this bug.
Algorithm would be: If message flags are updated and message has X-GM-
LABELS, then iterate labels and find messages with matching X-GM-MSGID
and update the flags for those messages.
--
You received this bug no
I have a proposed solution to this. I would like some feedback before I
attempt a patch.
As WADA mentioned in Comment 32, the reason for the restriction on
choosing the Trash folder for a GMail account is that TB is using XLIST
to get the trash folder. Whenever TB starts up, the value from the XLI
18 matches
Mail list logo
