** Changed in: gnome-software (Ubuntu Focal)
Assignee: Olivier Tilloy (osomon) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1914868
Title:
gn
** Changed in: snapd
Assignee: Olivier Tilloy (osomon) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1968548
Title:
firefox snap unable to open fi
** Changed in: xdg-desktop-portal (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: xdg-desktop-portal (Ubuntu)
Importance: Undecided => High
** Changed in: xdg-desktop-portal (Ubuntu)
Status: New => In Progress
** Also affects: xdg-desktop-porta
Public bug reported:
(this was initially reported here: https://github.com/flatpak/xdg-
desktop-portal/pull/705#issuecomment-1123392120)
When testing the WebExtensions portal against the only known client so
far (firefox snap + the corresponding upstream patch
Yes, a workaround was distro-patched into mutter 42.0-3ubuntu1 in Ubuntu 22.04
(see https://launchpad.net/bugs/1964541 for details).
So I think it is safe to mark this resolved.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter
Following my own suggestion, I submitted
https://github.com/snapcore/snapd/pull/11892.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => In Progress
** Changed in: snapd
Assignee: (unassigned) => Olivier Tilloy (osomon)
-
Well, I personally think that $HOME/.cache isn't the right place to
unpack temporary files, those should probably be unpacked somewhere
under $TMPDIR by default. But that wouldn't really solve this bug,
because the firefox snap, being strictly confined, would still be unable
to read these files.
** Changed in: xdg-desktop-portal (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1978341
Title:
Merge for
Public bug reported:
This is an upstream issue (https://github.com/flatpak/xdg-desktop-
portal/issues/564) that was fixed in xdg-desktop-portal 1.10.0.
I'm proposing to SRU the corresponding patch to focal. This will be
especially useful for browsers packaged as snaps (see bug #1887195 for
Indeed, by default file-roller will temporarily unpack files in the
user's cache folder (it can in some cases fall back to the user's home
directory, or a temporary directory, see
https://gitlab.gnome.org/GNOME/file-roller/-/blob/master/src/file-
utils.c#L55).
Given this, I wonder whether it
the patch doesn't fix the issue it claims it resolves.
** Affects: xdg-desktop-portal (Ubuntu)
Importance: Medium
Assignee: Olivier Tilloy (osomon)
Status: Fix Released
** Affects: xdg-desktop-portal (Ubuntu Jammy)
Importance: Medium
Assignee: Olivier Tilloy (osomon)
(In reply to jaz.zimms from comment #8)
> Do you have more context on this fix? I could use some assistance on how to
> implement it.
There is nothing to implement: the issue is in gtk/mutter, and will be
worked around/fixed there. See
https://gitlab.gnome.org/GNOME/mutter/-/issues/2216 for
I can confirm MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 reliably makes the
problem go away for me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040
Title:
Blanked screen doesn't wake
Attaching the requested output of drm_info.
** Attachment added: "drminfo.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5580371/+files/drminfo.txt
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because
Now testing MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0, and it seems to fix my
problem. I'll continue experimenting with it some more to confirm.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Just tested MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1, and I can still
observe the problem.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040
Title:
Blanked screen doesn't wake
Yes, that's definitely the intention. Mozilla was concerned that they
didn't have automated testing in place to catch bugs and regressions in
a timely manner, hence the temporary revert. See
https://bugzilla.mozilla.org/show_bug.cgi?id=1725245 for more details.
** Bug watch added: Mozilla
Corrado is right, but that's a side effect of disabling native wayland
support in the firefox snap, thus having it use xwayland, rather than an
actual fix to the root cause of the problem. But as Daniel is pointing
out, a proper fix is coming.
Note that only the stable channel has been reverted
I reverted to stock mutter (42.0-1ubuntu1), enabled KMS debug in mutter,
and observed that the problem persists. Attaching the corresponding
journal.
** Attachment added: "journal-with-kms-debug.log"
mutter 42.0-1ubuntu2~ppa1 is a locally-patched version with a work-
around for https://gitlab.gnome.org/GNOME/mutter/-/issues/2216, as not
being able to re-order my tabs in firefox was bothering me.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2216
Update from the launchpad bug:
I bisected mutter and gnome-shell until I identified the revision in
mutter that caused the regression:
https://gitlab.gnome.org/GNOME/mutter/-/commit/26676a829e74859488154cd8c45de1d0b629f3ca.
More specifically, the changes to src/core/events.c. Indeed I rebuilt
I can reproduce the issue described here. I'm using stock Ubuntu dock,
no other gnome-shell extensions other than the ones enabled by default
in Ubuntu, and I'm on jammy fully up-to-date. After I lock my screen and
let the monitor blank, when I unlock it I find that one or several of my
fullscreen
Crash report for gnome-session-binary:
https://errors.ubuntu.com/oops/d5e2d4b2-b62f-11ec-a2f0-fa163ef35206
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1968040
Title:
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2216
https://gitlab.gnome.org/GNOME/mutter/-/issues/2216
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/2216
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Attaching my journal for the current boot, where I have observed the
issue a few times already.
I'm seeing some critical error messages for gnome-session-binary and one
segfault, unsure whether this is related to the problem though.
** Attachment added: "journal.log"
Public bug reported:
(initially reported as a comment on bug #1965085, and split into a
separate bug report)
After I lock my screen and let it blank, moving the mouse or pressing
any key on the keyboard won't wake it up. The only reliable workaround
I've found is to press Ctrl+Alt+F1.
That's on
Done: bug #1968040.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1965085
Title:
Login screen sometimes unresponsive to mouse clicks (after waking from
sleep)
To manage
I read again the description and it says the login screen is
unresponsive, not that the screen doesn't wake up. Additionally the tab
key doesn't work to wake the screen for me, only Ctrl+Alt+F1. So it is a
different bug after all. I'll file a new one.
--
You received this bug notification
I'm seeing the same symptoms as Corrado (comment #4). After I lock my
screen and let it blank, moving the mouse or pressing any key on the
keyboard won't wake it up. The only reliable workaround I've found is to
press Ctrl+Alt+F1.
That's on a fully up-to-date jammy, my hardware is an Intel NUC
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1831039
Title:
When using Wayland, the onscreen
That's a known issue, see https://forum.snapcraft.io/t/cannot-open-
display-after-session-type-changed-wayland-x11/23838. The problem
appears to be partly in gnome-session
(https://gitlab.gnome.org/GNOME/gnome-session/-/issues/75), partly in
the snapcraft desktop extensions that assume a wayland
** Bug watch added: Debian Bug tracker #923345
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923345
** Also affects: evince (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923345
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Just tested the following on a laptop running fully up-to-date 22.04, in the
default Wayland session:
- firefox snap (97.0)
- firefox deb (97.0)
- chromium snap (98.0.4758.80)
Screen sharing (entire screen and selected windows) works as expected in
all cases.
marco, could you please test
Tentatively marking the xdg-desktop-portal-gtk task fixed, per my last
comment. Feel free to re-open if it's not working for you.
** Changed in: xdg-desktop-portal-gtk (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Invalid
Just tested on impish with thunderbird 91.5.1, and the problem persists.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1932328
Title:
Thunderbird under Wayland does not correctly
Indeed, and this appears to be a GTK bug
(https://gitlab.gnome.org/GNOME/gtk/-/issues/4340), for which a fix was
merged a week ago.
For reference, the upstream firefox bug was
https://bugzilla.mozilla.org/show_bug.cgi?id=1722369.
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
*** This bug is a duplicate of bug 1913775 ***
https://bugs.launchpad.net/bugs/1913775
** This bug has been marked a duplicate of bug 1913775
Copy from Firefox Wayland fails to be pasted anywhere else
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
This sounds like https://bugzilla.mozilla.org/show_bug.cgi?id=1731495,
which claims that the regression was worked around in Firefox 94, and
that workaround was backported to 93. So presumably the problem
shouldn't happen with 94.0.2-2 as a snap and xdg-desktop-portal-gtk
1.10.
** Bug watch
I can confirm the bug still exists with mutter 40.5-1ubuntu3 and
thunderbird 1:91.3.2+build1-0ubuntu1, as tested in a fully up-to-date
jammy VM.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1950484
Title:
Adding an admin user a Gnome Control Center should set the right
groups
Interestingly, it appears that accountsservice has a build-time option
to enable extra admin groups (extra_admin_groups), but the version in
focal (0.6.55-0ubuntu12~20.04.4) has a debian patch that ignores it.
That patch was recently reworked to not ignore the option:
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1950484
Title:
Adding an admin user a
Note that firefox 94.0 is now in the stable channel, so there is no need
to switch to the candidate channel to get the update.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1794064
Title:
Clicking a hyperlink in a PDF fails to
This has come up again, now that the default browser in impish is the
firefox snap (see https://discourse.ubuntu.com/t/feature-freeze-
exception-seeding-the-official-firefox-snap-in-ubuntu-
desktop/24210/107).
Jamie, I assume this should be unassigned, as you're not actively
working on this, are
WRT comment #10, +1 from me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1940925
Title:
[FFe] Do not activate spread view on first boot
To manage notifications about this
I have managed to reproduce the issue with the upstream build for
78.13.0, downloaded from thunderbird.net, in a fully up-to-date hirsute
VM, executed with MOZ_ENABLE_WAYLAND=1.
This rules out a packaging problem.
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance:
** Changed in: gnome-software (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1938630
Title:
Sorting by Évaluation
To manage
That's exactly what private/incognito modes are for, and what privacy
/security-conscious people use. People who don't understand the risks
inherent to web browsing should be educated, and I highly doubt offering
two web browsers by default would contribute to educating people (that's
if it
Which version of Ubuntu? If it's 20.04, that would be bug #1914868
(which you reported yourself).
** Changed in: gnome-software (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software
I have updated the affected package.
** Package changed: firefox (Ubuntu) => gedit (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1915498
Title:
Copy / paste in Firefox
** Changed in: gnome-software (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1914868
Title:
gnome-software-dev doesn't
** Changed in: gnome-software (Ubuntu)
Status: New => Confirmed
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1914868
Title:
I uploaded 3.36.1-0ubuntu0.20.04.1 to the focal queue, it's now in the
hands of the SRU team.
** Description changed:
+ [Impact]
+
+ * gnome-system-monitor 3.36.1 is the latest minor update in the 3.36
+ series
+
+ * it fixes one bug (https://gitlab.gnome.org/GNOME/gnome-system-
+
*** This bug is a duplicate of bug 1881197 ***
https://bugs.launchpad.net/bugs/1881197
** This bug has been marked a duplicate of bug 1881197
No network usage info presented, always 0 bytes/s.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Changed in: gnome-system-monitor (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: gnome-system-monitor (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gnome-system-monitor (Ubuntu Focal)
Assignee: (unassigned) => Olivier Tilloy (
> Should groovy also get the fix for upstream issue 642?
I suppose it wouldn't hurt. Adding the rls-gg-incoming tag to consider
whether this is worthwhile.
** Tags added: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Uploaded librsvg 2.48.9-1ubuntu0.20.04.1, now sitting in the focal
unapproved queue, waiting for the SRU team to review and accept it.
** Changed in: librsvg (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop
librsvg 2.50.2+dfsg-1 is now in hirsute. We can proceed with the SRU.
** Changed in: librsvg (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: librsvg (Ubuntu)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop
Federico confirmed he plans on releasing librsvg 2.50.2 soon (November
21st at the latest). Once that is out, I'll update the package in Debian
and Ubuntu 21.04, and we can then proceed with the SRU.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I tentatively added a gnome-shell task.
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1902900
ahead.
** Bug watch added: gitlab.gnome.org/GNOME/librsvg/-/issues #642
https://gitlab.gnome.org/GNOME/librsvg/-/issues/642
** Also affects: librsvg (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: librsvg (Ubuntu Focal)
Assignee: (unassigned) => Olivier Til
Thank you Salim, I'll take care of preparing and uploading the SRU.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/1903329
Title:
SRU the current 2.48.9 stable update
To manage
The reporter didn't mention this was happening after resuming from
suspend, though.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1893217
Title:
[nvidia] Chrome window is corrupt
Not that I can tell.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1894627
Title:
[nvidia] Web browser distorted after hibernation/power save when idle
To manage notifications
By just comparing the screenshots, this looks more similar to bug
#1855757. But I'll let Daniel comment as he's more familiar with graphic
drivers issues than I am.
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => New
** Changed in: mutter (Ubuntu)
Status: Incomplete
Kashad, could you please confirm that chromium (and firefox if you can
test) are similarly affected?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1894627
Title:
[nvidia] Web
I updated librsvg to 2.48.7-1ubuntu0.20.04.1 from focal-proposed in an
otherwise fully up-to-date focal VM (amd64), logged out and back in, and did
some extensive smoke testing, both targetted (opening and manipulating various
SVG images in eog and gimp), and general (launched several
Hey Łukasz, that's a good point.
Those are not public symbols, they are part of the implementation-
specific layer of librsvg (all symbols named "rsvg_rust_*" fall in this
category).
Neither the C headers nor the GObject introspection and Vala vapi files
installed by librsvg2-dev expose them.
Brian: librsvg is indeed not a direct dependency of the gnome-core
metapackage, however it is a direct dependency of other core components
and apps such as gnome-shell and eog. In that regard I think it
qualifies, but we should probably clarify the policy to clearly map to
Attaching a debdiff for the SRU, please sponsor.
** Attachment added: "librsvg-focal.debdiff.gz"
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1884326/+attachment/5385451/+files/librsvg-focal.debdiff.gz
--
You received this bug notification because you are a member of Ubuntu
testing to try and detect SVG rendering
issues should be performed.
** Affects: librsvg (Ubuntu)
Importance: High
Assignee: Olivier Tilloy (osomon)
Status: Fix Released
** Affects: librsvg (Ubuntu Focal)
Importance: High
Assignee: Olivier Tilloy (osomon)
Status
** Package changed: firefox (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1883831
Title:
my laptop screen crashes when i take my laptop with
/GNOME.
Switch to adwaita and verify that all icons in the shell and in GTK
applications are rendered correctly.
* Regression potential
Visual changes only.
** Affects: adwaita-icon-theme (Ubuntu)
Importance: Medium
Assignee: Olivier Tilloy (osomon)
Status: Fix Released
Nevermind, the SRU to focal is already tracked by bug #1876256, and an
upload is already sitting in the queue.
** Tags removed: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
I think the fix should be SRUed to focal, indeed.
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1862553
Title:
gnome-control-center
Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1639863
Title:
Firefox and Thunderbird don't appear in the (new) appstream metadata
And here is the distro patch: https://salsa.debian.org/gnome-team/gnome-
control-center/-/commit/3badf8b53efee9d0be49ae0af12833b0fa02b107
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of
** Changed in: gnome-control-center (Ubuntu)
Assignee: Robert Ancell (robert-ancell) => Olivier Tilloy (osomon)
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Submitted upstream to start the discussion:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/748
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
The following patch fixes the crash for me, at the cost of probably
introducing a memory leak:
--- panels/online-accounts/cc-online-accounts-panel.c.orig 2020-04-27
17:07:18.366421418 +0200
+++ panels/online-accounts/cc-online-accounts-panel.c 2020-04-27
17:08:12.634932818 +0200
@@
Fixed with
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.focal/revision/1375.
** Changed in: firefox (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: firefox (Ubuntu)
Importance: Undecided => Medium
** Changed in: firefox (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are
slightly related: bug #1871723
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1639863
Title:
Firefox and Thunderbird don't appear in the (new) appstream metadata
To manage
>From the upstream bug report (https://gitlab.gnome.org/GNOME/gnome-
control-center/-/issues/401), there's an even simpler way to reproduce:
$ gnome-control-center info-overview
$ gnome-control-center online-accounts add google
** Bug watch added:
I'm attaching a simple python script that automates the reproduction of
the bug:
1) In a terminal window, run "gnome-control-center info-overview"
2) In another terminal window, run the attached script
3) Observe how the gnome-control-center process crashed in the first terminal
window
**
This was originally worked around by https://gitlab.gnome.org/GNOME
/gnome-control-center/-/commit/f5d601d3b023e6d869f40415e1e31aebfb7b1d01,
but for some reason this workaround is no longer working.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
The crash is caused by the GOA panel being disposed prematurely, in
get_all_providers_cb: user_data (the panel) is being g_autoptr'd, and as
a consequence it is destroyed when exiting the scope of the callback.
This appears to be an unwanted regression/side effect of
Unassigning and resetting the status as this doesn't appear to have been
worked on.
** Changed in: firefox (Ubuntu)
Assignee: FanJun Kong - ( BH1SCW ) (fjkong) => (unassigned)
** Changed in: thunderbird (Ubuntu)
Assignee: FanJun Kong - ( BH1SCW ) (fjkong) => (unassigned)
** Changed
I'm not familiar with the generator code (I don't even know where it
lives to be honest). How hard would it be to make it understand
symlinks? (I'm not opposed to implementing Laney's suggestion though, I
just want to get a better understanding of the problem).
--
You received this bug
Done, here is the upstream bug: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/2543.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2543
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2543
** Also affects: gnome-shell via
*** This bug is a duplicate of bug 1869835 ***
https://bugs.launchpad.net/bugs/1869835
I wonder how I managed to file the same bug twice, concurrently. Did I
involuntarily double-click on the submit button fast enough that
Launchpad hadn't greyed it out yet?
--
You received this bug
This looks similar to https://gitlab.gnome.org/GNOME/gdm/-/issues/462,
although that upstream bug seems to imply the problem happens
systematically, whereas in my case it's random.
** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #462
https://gitlab.gnome.org/GNOME/gdm/-/issues/462
--
Public bug reported:
I have seen that happening randomly during the 20.04 development cycle,
and I think more often in the last week or so, but never consistently:
when I turn on my laptop, on the GDM greeter screen the keyboard layout
that's selected is en-US, instead of my default preference
Public bug reported:
I have seen that happening randomly during the 20.04 development cycle,
and I think more often in the last week or so, but never consistently:
when I turn on my laptop, on the GDM greeter screen the keyboard layout
that's selected is en-US, instead of my default preference
This looks similar to https://gitlab.gnome.org/GNOME/gdm/-/issues/462,
although that upstream bug seems to imply the problem happens
systematically, whereas in my case it's random.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3
Thanks for the feedback. Feel free to re-open if the problem surfaces
again.
** Changed in: firefox (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Can you please be more specific, i.e. detail the test case, what you
would expect, and what happens instead?
>From the bug report, you're using a wayland session, is the bug also
present in a default xorg session?
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
You received
After successfully downgrading, I upgraded again to 1:13.99.1-1ubuntu1,
rebooted my laptop, and lo and behold, my bluetooth headset works again.
I wonder if simply reinstalling the pulseaudio packages instead of
downgrading and upgrading again would have fixed the problem. I'll test
that if it
I downgraded pulseaudio to 1:13.0-3ubuntu2, and the problem is gone, so
this appears to be a pulseaudio regression.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
1 - 100 of 392 matches
Mail list logo