Hi Luke Skywalker,
Judging by the error message, it looks like your snapd is out of date.
Can you please open a terminal and share the output of "snap info
snapd"? You can also try "snap refresh snapd" to update it.
May the force be with you.
--
You received this bug notification because you
No problem at all, happy journey to Linux!
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
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/2022897
Title:
Hi Chris, thanks for the bug report.
The attached file is not actually a PNG (it is identified as "Paint.NET
image data") and I cannot open it, could you please upload a new one in
a common format?
Could you share address of the affected web site and see if you get
something either in the journal
> When will I see this fix in apt for Luna?
See https://wiki.ubuntu.com/PhasedUpdates.
--
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
Title:
Single click on title bar does not
Public bug reported:
In Wayland,
- Open Chromium or Firefox
- Go to https://mozilla.github.io/webrtc-landing/gum_test.html
- Start full screen capture
- Drag some windows around
Expected: The movement of each window is reproduced in the screen cast smoothly
and immediately.
Observed: It takes a
Hi, what exactly does restarting the session mean? I could verify
whether that would work.
Otherwise the behavior I observed is consistent with
https://source.puri.sm/kop316/mmsd/-/issues/3.
** Bug watch added: source.puri.sm/kop316/mmsd/-/issues #3
https://source.puri.sm/kop316/mmsd/-/issue
I tried it again and could no longer reproduce it, so maybe it was.
--
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/2023365
Title:
Window movement is delayed in screen share in Wayland
Yes, I can confirm that restarting the user session is enough.
** 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
*** This bug is a duplicate of bug 1732482 ***
https://bugs.launchpad.net/bugs/1732482
The problem is https://forum.snapcraft.io/t/how-to-expose-desktop-files-
created-by-snaps-to-the-de.
Probably duplicate of the there mentioned LP:1732482.
I can confirm it is not a problem from Chromium PP
*** This bug is a duplicate of bug 1732482 ***
https://bugs.launchpad.net/bugs/1732482
Thanks for the response, zwm.
The desktop file is necessary for Gnome Shell to categorize the PWA as a
different application — in its own tab group — instead of just another
Chromium window.
This bug is th
** 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/2016972
Title:
Chromium snap does not sup
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Low
** Tags added: log-noise
--
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/1969141
Title:
[snap] seccom
** Tags added: log-noise snap
--
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/1993562
Title:
[snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor,
bios_version
** Tags added: log-noise
--
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/1862262
Title:
[snap] apparmor denials on /sys/devices/virtual/dmi/id/sys_vendor and
product_name
S
** Tags added: log-noise
--
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/1852362
Title:
ColorManager/Avahi apparmor denials when selecting printer
Status in chromium-browser
** Tags added: log-noise
--
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/2017011
Title:
[snap] unable to read /proc/pressure/{cpu,io,memory}
Status in chromium-browser packag
** 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/2006646
Title:
hwacc branch builds that u
** 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/2006966
Title:
Missing flag causing lack
** 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/2004586
Title:
Chromium's minigbm uses in
** Tags added: log-noise
** Changed in: chromium-browser (Ubuntu)
Assignee: Bram Stolk (b-stolk) => (unassigned)
--
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/2000175
Ti
** 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/1987137
Title:
Migrating chromium-browser
This originates from Brave. If someone can reproduce in Chromium please
leave a comment saying so.
Also it would be helpful for importance triaging to know how this
affects the usability of the browser.
** Summary changed:
- There are 2 errors.
+ GetVSyncParametersIfAvailable() failed
** Tags a
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Critical
--
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/1967827
Title:
Screen Keyboard does not open when
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Critical
--
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/1967488
Title:
Chromium stable snap don't work on
Is this still reproducible?
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High
--
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/1967175
Title:
Righ clic
*** This bug is a duplicate of bug 1732482 ***
https://bugs.launchpad.net/bugs/1732482
I'm posting what I've learned so far but there is still much to figure.
> In the comment #5 you mention window classes as a way to do this feat.
The desktop file seems like a possible way to launch Chromium
Thanks for giving it a shot again, your contribution is much
appreciated.
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Released
** Summary changed:
- Righ click on links menu doesn't render 99.0.4844.84
+ Right click on links menu doesn't render 99.0.4844.84
--
You recei
I installed 0.11.1-1ubuntu3 from jammy-proposed and the snap[5] in a
Jammy virtual machine, logged out, logged in, opened Pavucontrol, ran
snap run --shell geheim
XDG_RUNTIME_DIR=/run/user/1000 spd-say hi
and verified that the volume indicator in Pavucontrol moved right after
issuing the comm
Verified in Lobster (0.11.4-2ubuntu0.1) and Kinetic (0.11.3-1ubuntu1.1)
that the test case produces sound.
** Tags removed: verification-needed verification-needed-kinetic
verification-needed-lunar
** Tags added: verification-done verification-done-kinetic
verification-done-lunar
--
You receiv
Removing chromium-browser as affected package because this wasn't
actually verified on Chromium. If it is verified on Chromium, please
revert that.
** No longer affects: chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
*** This bug is a duplicate of bug 2017980 ***
https://bugs.launchpad.net/bugs/2017980
** This bug has been marked a duplicate of bug 2017980
Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission
denied (13)
--
You received this bug notification because you are a me
Thanks for the bug report, Heiko.
We do not have cups-control in Chromium. What is the output of 'snap
connections chromium'? Is the cups one connected?
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of De
It could be a problem in Chromium or Cups then.
If you start Chromium from the command line with
chromium --enable-logging=stderr |& tee chromium.log
and work from there, do you see anything relevant in the output?
If yes, please attach the generated log file to this bug report.
** Changed i
This problem should now be solved for Chromium (>=114.0.5735.198).
Please confirm or deny it if you are a Chromium user previously affected
by this bug.
** Description changed:
Possible, proposed solutions
Option 1: Please install from these channels and repo
Good! Marking it as fixed then, thank you again for reporting back.
** 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.
https://bugs.
I think you had removed the gnome-42-2204 and this caused the interface
not to connect.
> sudo apt install snap --reinstall
> sudo apt install snap --reinstall chromium
You conflated snap[1] and snapd[2] in those instances. If your intention
was to reinstall Chromium (and not snapd), then you co
Is this still a problem? If yes, does the --disable-gpu flag help?
--
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/1563184
Title:
Chromium-browser armhf crashes with "Initiali
You mention snap update in the title. What specific snap are you
referring to, Chromium, Cups or Snapd? The output of "snap changes"
could be useful. If you roll it back with "snap revert ",
does it work again?
> Launching chrome from menu shortcut that is managed by the snap works
> and it u
Thanks for the confirmation, but I don't yet know the context of the
issue.
Did you update from Bionic to Focal or did you simply notice the issue
after the last Chromium update?
Is there any problem when running 'chromium' from a terminal or is it a
issue specific to the launcher?
Please try to
Thank you very much for elaborating, that is much clearer. A couple of
questions:
1. When you do not use /snap/chromium/current/usr/lib/chromium-
browser/chrome, but rather chromium or /snap/bin/chromium, do you ever
get those GLIBC errors? If not, what is the exact error you get? You
mention perm
3. Please specify whether the errors are only observed for headless
Chromium or if it is also observed for normal Chromium.
** Tags added: focal printing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launch
To be clear, the reason why this has hit you is that Chromium in the
stable channel switched from Core20 in 114.0.5735.106 to Core22 in
114.0.5735.198 (this is a downstream, in other words Ubuntu
maintainer's, decision, not Chromium's maintainers').
Core20 is a base from Ubuntu 20.04, while core22
Marcus, from what I gather, and correct me if I'm wrong, you were able
to fix all your problems in your headless environment with Chromium
edge. Not with Chromium stable?
And hats off to you for responding to the proposed questions and
investigating the issue. That was a great help and much apprec
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Invalid
--
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/2026200
Title:
Snap update broke launching and pri
Am 07/07/2023 um 17:59 schrieb Michaelus:
> ... by the Apache user, and, because APT forces the SNAP Chromium
> package, rather than the standard Debian package, and because the Apache
> user's (www-data) home directory is /var/www and not /home/www-data, one
> cannot invoke Chromium via Apache
I also appreciate your situation and I'm sorry this has been giving you
a hard time. I'm happy to help with what I can.
> 1. Is there any way we can influence where chromium looks for glibc to
> find the base 2.35? (Is this something that would be resolved if I
> could get /snap/bin/chromium
-- Michaelus
> you're saying invoking chromium via a fully qualified, real-path, with
a SNAP-created symbolic link to a actual build directory, is a
"unsupported setup" ?
Yes, running a snap via /snap/chromium/current/usr/lib/chromium-
browser/chrome is unsupported. (I don't know how you conclude
That is currently a Snap shortcoming, there is no dependency enforcement
like in Apt. So in general you'd really have to ask. :/
--
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 still maintain that if Ubuntu 20.04 LTS is supported until April
> 2025, and its base SNAP is core20, it is not appropriate (if, only
> because of my biased opinion) to build snaps on core22, which, you
> admit, is the base snap core for Ubuntu 22.04)
I think there is a misunderstanding here.
> I never installed gnome; and surely not with snap.
That snap is just poorly named, it doesn't have only Gnome stuff, but
also other snaps' dependencies, including e.g. Chromium.
There is nothing surprising in the fact that it was refreshed though and
as such gives no insight into the original
Looks like the usual connection problem during installation.
Please attach
snap info chromium
apt list --installed | grep chromium
ls /var/lib/snapd/desktop/applications/chromium*
ls /usr/share/applications
--
You received this bug notification because you are a member of Desktop
Packag
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => 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/2025916
Title:
command-chain ... not found
Sta
If it still shows up in "snap changes" (which at this point is
unfortunately unlikely), please get the ID for the refresh and share the
output of `snap change {ID}`.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubun
Thanks for the report, Andreas.
Other than the error messages, is there any observable misbehavior? I
suppose one of them would be not respecting the Gnutls global
configuration.
You are using latest/edge/hwacc, correct?
--
You received this bug notification because you are a member of Desktop
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs
Ouch... Thank you for the report.
I committed the fix and while the new snap isn't finished building, I
rolled back the edge snap to the previous version.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a mem
Hi Clinton, thanks for your suggestion.
Chromium is a snap in Ubuntu, and as such, it automatically updates when
the process is not running (and forcefully so after 15 days), so I do
not understand the value of adding that.
Upstream might consider it though, you can try a report in
https://crb
** Changed in: chromium-browser (Ubuntu)
Status: New => Won't Fix
--
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/2028711
Title:
Feature Request: out-of-date browser no
As far as I know, Xvfb and --headless result in quite different
environments, as the first will run in normal graphical mode and the
latter won't.
I see no reason why this would affect your extension packing, however I
have no experience with extensions in Chromium. Could the graphical
environ
For the record, currently only x64 has 117, as Launchpad builders are
getting stuck.
** 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 i
Thanks for sharing your resuilts, David!
--
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/2026200
Title:
Snap update broke launching and printing on 20.04 Ubuntu.
Status in ch
** Changed in: chromium-browser (Ubuntu)
Status: Won't Fix => Triaged
** Changed in: firefox (Ubuntu)
Status: Won't Fix => Triaged
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: chromium-browser (Ub
I proposed https://github.com/snapcore/snapd/pull/13130.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
** Changed in: firefox (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which
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 (Ubuntu)
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 chrom
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 chromium-b
** 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.
https://bugs.launchpad.net/bugs/20
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
*** 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 re
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 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 acc
** 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 pa
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> I
> 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 nonethe
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 received
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)
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 i
** 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
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:
cve-2023-4863
** 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 chr
** 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 to
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 co
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 s
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.
https://bugs.launchpad.ne
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"
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/
** 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 me
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] https://gitlab.gnome.org
** 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
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.
https://bugs
** 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.
https://bugs.launchpad.ne
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 becau
** 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.
https://bugs.launchpad.ne
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: 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 sav
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 repor
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,
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 machi
** 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 gn
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 happ
1 - 100 of 983 matches
Mail list logo
