tance: Wishlist
Assignee: Nathan Teodosio (nteodosio)
Status: Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-clocks in Ubuntu.
https://bugs.launchpad.net/bugs/2083306
Title:
New release 47.0
Status in gnome-c
Thanks for the report and also for already having proposed a solution.
I'm adding the interface to all channels, in next builds should be
solved.
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
ort aria-disabled on gridcell
New and updated translations (THANKS EVERYONE!!!):
<---
** Affects: orca (Ubuntu)
Importance: Wishlist
Assignee: Nathan Teodosio (nteodosio)
Status: Triaged
--
You received this bug notification because you are a member of Desktop
Package
** Changed in: gtk4 (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => (unassigned)
** Changed in: gnome-control-center (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
This is certainly not update-manager, maybe not gnome-shell either, but
in any case there is too little information in the bug report. We need
at least your hardware (lspci), the release you were using, the release
you are on now (lsb_release -c).
** Information type changed from Public Security t
Focal)
** No longer affects: shotwell (Ubuntu Jammy)
** Also affects: shotwell (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: shotwell (Ubuntu Noble)
Importance: Undecided => High
** Changed in: shotwell (Ubuntu Noble)
Assignee: (unassigned) => Nathan Teo
hotwell-stat.png"
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/2080004/+attachment/5822094/+files/shotwell-stat.png
** Changed in: shotwell (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: shotwell (Ubuntu)
Status: Triaged => In Pro
) => Nathan Teodosio (nteodosio)
** Summary changed:
- Update-manager crashes when packages are de-selected with the mouse
+ [SRU] Update-manager crashes when packages are de-selected with the mouse
** No longer affects: pygobject (Ubuntu Noble)
** Description changed:
+ Impact
+ --
+
Upd
My understanding is that this is in progress on Snapd's side as per
Zyga's report.
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progress
** Changed in: chromium-browser (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => (unassigned)
--
You received this
That is good news, thank you for the feedback.
** Tags added: core24 hw-specific
--
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/2080953
Title:
Chromium WebGL Errors Leading
What is currently possible in the nightly and beta builds is to load the
opensc-pkcs11 module, by going to 'Settings > Cryptography modules >
Load' and writing (NOT browsing for with the file picker)
/snap/firefox/current/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
The bug cannot be marked as fix
Note also that there is a merge request[1] in progress for making the
path of opensc-pkcs11 less awkward.
[1]https://github.com/canonical/firefox-snap/pull/83
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bug
** Description changed:
- For 22.04, if your smart card is supported by OpenSC
- (https://github.com/OpenSC/OpenSC/wiki/Supported-hardware-%28smart-
- cards-and-USB-tokens%29), we believe the best solution/work-around at
- the moment is:
+ Opensc-pkcs11
+ -
- sudo apt install open
Andreas, thank you for your response. As in my previous message, we
cannot expect such a hack to work outside of 22.04, I updated the
description, sorry for wasting your time with that.
Then, it doesn't matter if /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
is in the host, the snap is on core22 an
I missed the obvious fact that the module will only work if sourced from
a 22.04, as Firefox is based on core22. There is a priori no guarantee
it would work for other series, as it indeed doesn't. If sourced from
24.10, ldd says stuff like
opensc-pkcs11.so: /lib/x86_64-linux-gnu/libc.so.6: vers
** Merge proposal linked:
https://code.launchpad.net/~nteodosio/update-manager/+git/update-manager/+merge/473514
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/2041831
Title:
Up
Sometimes this also appears:
/usr/lib/python3/dist-packages/gi/overrides/Gtk.py:1694: Warning: g_object_ref:
assertion 'G_IS_OBJECT (object)' failed
return _Gtk_main(*args, **kwargs)
(update-manager:188833): Gdk-CRITICAL **: 11:19:39.154: gdk_window_get_display:
assertion 'GDK_IS_WINDOW (wind
After some whack-a-moling, removing the setBusy calls from
toggle_from_items makes the issue go away, as does removing
while Gtk.events_pending():
Gtk.main_iteration()
from setBusy().
--
You received this bug notification because you are a member of Desktop
Packages, which i
crashes when packages are de-selected with the mouse
** Changed in: update-manager (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: update-manager (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a mem
)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
Snap.Changes: no changes found
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (n
Debdiff for 20.04: https://salsa.debian.org/gnome-team/gnome-
shell/-/merge_requests/81.diff
--
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:
[SRU] PWA don't lau
> i'm also confused about that commandline being unsupported -- that's
what clicking on the dock item shows in ps,
Ah, I didn't know it was from ps, looks like a legit issue then. However
when invoking in the command-line you shouldn't use that full qualified
path, but just 'chromium' or 'snap run
> /snap/chromium/2943/usr/lib/chromium-browser/chrome
Can you please verify whether the issue still happens if you substitute
that by /snap/bin/chromium?
The reason is: That command line in unsupported as launches Chromium as
a unsandboxed application, and thus it tries the hosts' shared librarie
Debdiff for 22.04: https://salsa.debian.org/gnome-team/gnome-
shell/-/merge_requests/80.diff
--
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:
[SRU] PWA don't lau
Debdiff for 24.04: https://salsa.debian.org/gnome-team/gnome-
shell/-/merge_requests/79.diff
--
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:
[SRU] PWA don't lau
** Description changed:
- I have recently converted from deb to snap package of chromium and
- progressive web applications (PWAs) launch just as another window of
- chromium and are not recognized as separate application by the window
- manager (for example when switching using Super+Tab) or dock
** Summary changed:
- [snap] PWA don't launch as applications, just another chromium window
+ [SRU] PWA don't launch as applications, just another chromium window
** Changed in: gnome-shell (Ubuntu Focal)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to yaru-theme in Ubuntu.
https://bugs.launchpad.net/bugs/2080923
Title:
Unreadable hyperlink colors in dark t
In this debdiff I'm adding libglib2.0t64 to Chromium's dependencies as
proposed by Julian.
** Patch added: "chromium-2to3.diff"
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918/+attachment/5818460/+files/chromium-2to3.diff
--
You received this bug notification because you a
** Changed in: gnome-shell (Ubuntu)
Status: Opinion => Fix Committed
** Also affects: chromium-browser (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: chromium-browser (Ubun
** Changed in: gnome-control-center (Ubuntu)
Status: New => Fix Released
** Also affects: gnome-control-center (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: gnome-control-center (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => (unassigned)
** Chan
Patch: https://salsa.debian.org/gnome-team/gnome-control-
center/-/merge_requests/43.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2080611
Title:
[SRU] Backport gno
Assignee: Nathan Teodosio (nteodosio)
Status: New
** Tags: noble
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2080611
Title:
[SRU] Backport gnome-control
Duplicate LP:2080578: Upgrading from 22.04 to 24.04 (judging by the line
"Unpacking libibus-1.0-5:amd64 (1.5.29-2) over (1.5.26-4) ..." in the
log) caused the same abortion.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in U
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Changed in: thunderbird (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a me
*** This bug is a duplicate of bug 2061918 ***
https://bugs.launchpad.net/bugs/2061918
** This bug has been marked a duplicate of bug 2061918
package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new
thunderbird package pre-installation script subprocess returned error exit
sta
If it is accepted in 24.10 — and I'm reasonably confident it will —, I'll
afterwards file a backport for 24.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/2007652
Title:
Alright, let us know if the issue appears again.
** 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/2080024
Glad to hear that, thank you for testing!
--
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:
[snap] PWA don't launch as applications, just another chromium window
I submitted a build for 24.04 in that PPA, will be there by the end of the day
if nothing goes wrong.
--
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:
[snap] PWA
> Try tweaking .illustrated-row in shell/style.css ?
That is only in force for picture-disabled, so nothing to do there.
> Alternatively, sadly, try querying the validity of self->media_stream
in panels/common/cc-illustrated-row.c and hide the widget when the media
stream isn't working.
I tried
I confirm they play in Oracular. In the Control Center however they are
still just orange squares. Infuriating.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2077117
Title
Thanks for your help on this.
Those videos do play if gstreamer*bad is not installed, but if it is
installed, then they do not play:
--->
% LC_ALL=C gst-play-1.0 edge-scroll.webm
Press 'k' to see a list of keyboard shortcuts.
Now playing /tmp/edge-scroll.webm
ERROR Internal data stream error. for
Public bug reported:
Built fine in 24.10.
** Affects: orca (Ubuntu)
Importance: Undecided
Assignee: Nathan Teodosio (nteodosio)
Status: Triaged
** Patch added: "ubu-ubu.diff"
https://bugs.launchpad.net/bugs/2079043/+attachment/5813679/+files/ubu-ubu.diff
--
Yo
Merge request: https://salsa.debian.org/gnome-team/gnome-control-
center/-/merge_requests/41.diff
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-con
** Changed in: gnome-control-center (Ubuntu)
Status: Fix Released => Incomplete
** Changed in: gnome-control-center (Ubuntu Noble)
Status: Triaged => Incomplete
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** C
It's pretty mysterious how those are chosen. I found no control on the
GTK side for it.
As a stop-gap we could just un-map those rectangles in case codecalpha
is missing, if we think that the current behavior warrants it, but for
all I know in a new release of it could well start loading a
differ
Do you remember from which version of Ubuntu you upgraded and how exactly you
carried it out (i.e. manually by editing /etc/apt/sources.list,
do-release-upgrade, ...)? This gives me a way to try to reproduce it myself.
--
You received this bug notification because you are a member of Desktop
Pack
How does GTK choose the plug-in? Are we able to change it? VPX is in
good and supports VP9 decoding too:
% gst-inspect-1.0 vpx
vp8dec: On2 VP8 Decoder
vp8
Feel free to take over the bug, you seem to have a better idea of what
is going on.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2077117
Title:
settings - mouse&touchpad - scroll direc
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged => In Progress
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
--
You received
24.10:
Sorry there was a small error in the Oracular patch, fixed now.
** Patch removed: "oracular+parentcontrol-malcontent+apps.patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2072772/+attachment/5812810/+files/oracular+parentcontrol-malcontent+apps.patch
** Patc
** Patch added: "oracular+parentcontrol-malcontent+apps.patch"
https://bugs.launchpad.net/bugs/2072772/+attachment/5812810/+files/oracular+parentcontrol-malcontent+apps.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-contr
24.04:
Salsa has been unbearably slow so I'm not opening a merge request there. I
attach the patch. Alternatively, merge the malcontent branch
of https://salsa.debian.org/nteodosio/gnome-control-center.
Tested that:
- Without malcontent installed, apps show up normally, parent control is not
a
Sebastien clarified that this would be any user in the sudo group, so a
normal Ubuntu user such as the one created during installation will have
those rights.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
Can you please clarify what 'admin' user means in this context? Is it a
user named 'admin' or is it a user with certain administration rights?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.la
** Description changed:
+ If you are hitting this bug, please write your case in
+ https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3984.
+
+ > it'd be good to know when this actually happens to evaluate why it
+ happens, and then evaluate if there is anything we should change.
+
+ ---
Proposed https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3984.
--
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/2069564
Title:
gnome-shell crashed with SIGTRAP in meta_waylan
Thanks, Pedro, but without the hard facts it is difficult to ascertain
whether this is a bug. Namely,
whoami; stat /tmp /tmp/.X11-unix
--
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/bu
In the case that /tmp is owned by ourselves and it matches 0200 but not
0022, it is still writable but it would fail with the present error.
I do not know if this is actually an intended blockage and thus the
description is just not clear enough or if this is an edge case to
consider.
Nor do we k
This comes from ensure_x11_unix_perms, which is determining that the
/tmp/.X11-unix does not have at least permission bits 022:
--->
static gboolean
ensure_x11_unix_perms (GError **error)
{
/* Try to detect systems on which /tmp/.X11-unix is owned by neither root nor
* ourselves because in t
Hi Sandy, thanks for the very clear and thorough bug report.
I can see no issues on Chromium's side.
I'm afraid that is indeed a Whoopsie problem. The
> Your computer does not have enough free memory to automatically
analyze the problem and send a report to the developers.
looks very out of pla
So you mean 'in Chrome', right?
I can indeed no longer reproduce #12.0... Either I screwed up during
testing or something changed in between, which is highly unlikely in
such a short time frame.
Anyway, added debug statements confirm that Chromium is running with
GTK3. Additionally, it DOES recei
8. Chromium is using GTK 3. And the unsandboxed one is too, so the
difference in behavior does not lay on the different GTK versions. Might
be the signal not being caught in the sandbox... I'm building it with a
patch with debugging statements to verify that.
--->
# For snapped Chromium
% for p in
...Chromium builds against GTK 3 but a different version may be loaded
at runtime.
--
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/2077272
Title:
Gnome's large text accessibil
3.1. In GTK4 Chromium listens to the gtk-xft-dpi signal in
//ui/gtk/gtk_ui.cc, thereat calling UpdateDeviceScaleFactor. In GTK3 it
listens to screen resolution's notify::resolution only. Todo: Confirm
the GTK version and whether the respective signal is actually caught and
if so why it cannot do wh
0. Unsandboxed Chromium in Wayland ((unsupported and just for testing
purposes!) /snap/chromium_edge/current/usr/lib/chromium-browser/chrome
--ozone-platform-hint=wayland) has no issues responding to 'large text'
setting. This must be a downstream problem.
1. Chromium in the sandbox can see change
** Changed in: chromium-browser (Ubuntu)
Status: Fix Released => Triaged
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Description changed:
Chromium - 127.0.6533.119
wayland
- Chromium app ignores large text s
** Attachment added: "softpp"
https://bugs.launchpad.net/bugs/2077451/+attachment/5807630/+files/softpp
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2077451
Title:
GNOME 47
I also get a very similar backtraces if I kill Nautilus but mine looks
more useful (see at the end), as it even has the timeout=25000.
Looks like I have been for two years stumbling in this very bug but just
shrugging it off as it happens only in specific circumstances. To
reproduce the bug consis
You got a backtrace for Nautilus? Is it crashing too or are you
interrupting it during this warm-up period of 20 s?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2077451
Title:
Thank you Marco, and as you also pointed out, that is
--->
GLogLevelFlags fatal_mask = (GLogLevelFlags) g_log_set_always_fatal
((GLogLevelFlags) G_LOG_FATAL_MASK);
fatal_mask = (GLogLevelFlags) (fatal_mask | G_LOG_LEVEL_WARNING |
G_LOG_LEVEL_CRITICAL);
g_log_set_always_fatal (fatal_mask);
** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #6947
https://gitlab.gnome.org/GNOME/gtk/-/issues/6947
** Also affects: gtk via
https://gitlab.gnome.org/GNOME/gtk/-/issues/6947
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a mem
Yup, problem still there.
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
Enable gnome-control-center > accessibility > seeing > large text and
open a couple of windows.
Observed: It is difficult to identify open windows in the dock. They are
represented by a small dot to the left of their respective icons.
Expected: It is easy to identify open wi
** Description changed:
MERGE REQUEST https://salsa.debian.org/gnome-
team/gtk4/-/merge_requests/25
+
+ UPSTREAM BUG: https://gitlab.gnome.org/GNOME/gtk/-/issues/6947
These GTK 4.15.5 tests fail:
--->
gtk:gdk / memorytexture
ER
Note that Chromium stable is now back to Xwayland until the real
solution for LP:2077272 is found.
You can however always enable it in about://flags or by invoking with
chromium --ozone-platform-hint=auto.
--
You received this bug notification because you are a member of Desktop
Packages, which
Glad to hear everything fell into place.
> I think it's best to hide this by default to avoid confusing users
like me.
I do not agree there.
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of D
Reversion committed: https://git.launchpad.net/~chromium-team/chromium-
browser/+git/snap-from-
source/commit/?id=66a95be63c03ae2b8c0c5a5d5ee612ded8b51dbd
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a memb
Answering my own question:
> Is anything in your report a regression, i.e., a new issue that was
not there a few days ago?
This is a regression of Chromium in native Wayland, it does not occur in
older releases.
Chromium on Xwayland is fine as tested with --ozone-platform-hint=x11.
** Tags adde
Adding mesa-vulkan-drivers to build-depends makes the memorytexture and
scaling tests fail with segmentation fault, although it solves
dmabufformats test failure.
https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/28880496/+files/buildlog_ubuntu-
oracular-armhf.gtk4_4.15.5+ds-2_BUILD
** Summary changed:
- Difference in behavior in wayland and xorg sessions
+ Gnome's large text accessibility setting not reflect in Chromium in Wayland
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medi
For the top bar, there is a 'use system title bar and borders'. That
works if you turn it off, doesn't it?
--
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/2077272
Title:
Diffe
> open normally on wayland session
What exactly do you mean with open normally? As far as I know, it opened
normally before too. The only abnormal thing was the spinning cursor.
Do you mean the spinning cursor went away in 127.0.6533.119?
The substantial difference in that version is that Chromi
No. I'll try too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2077313
Title:
GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
Status in gtk4 package in Ubuntu:
In Pr
** Description changed:
These GTK 4.15.5 tests fail:
--->
gtk:gdk / memorytexture
ERROR0.33s killed by signal 5 SIGTRAP
gtk:gdk / dmabufformats
ERROR0.21
** Affects: gtk4 (Ubuntu)
Importance: Undecided
Assignee: Nathan Teodosio (nteodosio)
Status: In Progress
** Tags: ftbfs
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/207731
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Chromium opens, but still loads within 15 seconds after opening.
+ Chromium opens, but cursor remains in "loading" state within 15 seconds after
opening.
--
You received this bug notificatio
Is anything in your report a regression, i.e., a new issue that was not
there a few days ago?
What is this large text setting and where is it used? In the web pages
themselves or in Chromium's interface elements such as tab bar,
configurations menu etc.?
What is this 'top bar named New Tab - chro
If you are in a different series of Ubuntu and are interested in the
proposed fix, tell me and I'll build for that release.
--
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/200765
Status: New
** Changed in: gnome-shell (Ubuntu)
Status: New => Opinion
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
** No longer affects: mutter (Ubuntu)
> But if I try
>
> cp ~/snap/chromium/current/*/*.desktop ~/.local/share/applications
>
> then I **can open the PWA from the dock and it behaves as a separate
> application indeed**, but not if opened from inside Chromium,
Even that small consolation suffered a regression in newer Mutter
(testin
*** This bug is a duplicate of bug 2029480 ***
https://bugs.launchpad.net/bugs/2029480
Kitty is also fixed upstream so marking as duplicate for HPLIP which is
the only remaining bug.
** This bug has been marked a duplicate of bug 2029480
SyntaxWarnings with Python3.12
--
You received thi
*** This bug is a duplicate of bug 2029480 ***
https://bugs.launchpad.net/bugs/2029480
This is fixed upstream in Rythmbox:
https://gitlab.gnome.org/GNOME/rhythmbox/-/merge_requests/188.
The HPLIP is to be fixed in LP:2029480.
** No longer affects: python3-defaults (Ubuntu)
--
You received
** Patch added: "invalid-escapes.patch"
https://bugs.launchpad.net/hplip/+bug/2029480/+attachment/5804034/+files/invalid-escapes.patch
** Changed in: hplip (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, wh
I installed gnome-calendar/46.1-0ubuntu1 from proposed.
I opened the Calendar, the menu and chose Online Accounts.
The Settings app opened to the Online Accounts page.
I added a Google account.
I closed the Settings app. Calendar events from my online account showed
in the Calendar app
I click
Is this still an issue?
1. I do not see Failed to begin udev enumeration.
2. In about:usb-internals I see my mouse and webcam.
3. The Chromium's Apparmor profile has all these:
--->
/run/udev/data/c116:[0-9]* r,
/run/udev/data/+sound:card[0-9]* r,
/run/udev/data/c16[67]:[0-9] r, # ACM USB modem
> It seems that the bug is not fixed in the release channel.
Do you mean the stable channel of Snapd? I'd be surprised if after 5
months it still didn't land. If yes can you also provide 'snap info
snapd' so I can ask the Snapd folks?
--
You received this bug notification because you are a membe
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** 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
No.
--
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/2072395
Title:
[snap] Chromium with core24 base won't start: desktop-launch not found
Status in chromium-browser package i
1 - 100 of 1029 matches
Mail list logo
