[Bug 1914868] Re: gnome-software-dev doesn't contain all the header files in /usr/include/gnome-software
** 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: gnome-software-dev doesn't contain all the header files in /usr/include/gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1914868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968548] Re: firefox snap unable to open files from file-roller
** 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 files from file-roller To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1968548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1982340] Re: Clients of the WebExtensions portal see the FDs as closed when the portal is used for the first time
** 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-portal (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: xdg-desktop-portal (Ubuntu Jammy) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: xdg-desktop-portal (Ubuntu Jammy) Importance: Undecided => High ** Changed in: xdg-desktop-portal (Ubuntu Jammy) Milestone: None => ubuntu-22.04.1 ** Changed in: xdg-desktop-portal (Ubuntu Jammy) Status: New => In Progress -- 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/1982340 Title: Clients of the WebExtensions portal see the FDs as closed when the portal is used for the first time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1982340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1982340] [NEW] Clients of the WebExtensions portal see the FDs as closed when the portal is used for the first time
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 https://phabricator.services.mozilla.com/D140803), I'm consistently seeing the following problem: the first time the user is prompted for authorization and accepts, the portal will spawn the native connector and pass the file descriptors to the client (firefox snap), but the client sees the file descriptors as closed. Closing the client and re- opening it doesn't help. Only when the portal is terminated and restarted does communication through FDs start working normally. It turns out this is caused by a missing variable initialization, which is trivially fixed by https://github.com/jhenstridge/xdg-desktop- portal/pull/2. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.14.4-1ubuntu1~22.04.1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 20 14:03:15 2022 InstallationDate: Installed on 2020-09-16 (671 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: xdg-desktop-portal UpgradeStatus: Upgraded to jammy on 2022-03-19 (122 days ago) ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images wayland-session -- 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/1982340 Title: Clients of the WebExtensions portal see the FDs as closed when the portal is used for the first time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1982340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964541]
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 in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot use Drag and Drop in gnome-shell 42 (Wayland session) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968548] Re: firefox snap unable to open files from file-roller
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) -- 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 files from file-roller To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1968548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968548] Re: firefox snap unable to open files from file-roller
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. And there might actually be a good reason for file- roller to unpack files under $HOME/.cache/ that I'm not aware of. Thinking about it again, I'm not sure that the OpenFile method of the FileChooser portal would be of any help here. It's firefox that is sandboxed, not file-roller. -- 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 files from file-roller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1968548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1978341] Re: Merge for xdg-desktop-portal 1.14.4 from Debian unstable
** 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 xdg-desktop-portal 1.14.4 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1978295] [NEW] org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file
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 chromium, and https://bugzilla.mozilla.org/show_bug.cgi?id=1772063 for firefox). ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: xdg-desktop-portal (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: xdg-desktop-portal (Ubuntu) Status: New => Fix Released ** Also affects: xdg-desktop-portal (Ubuntu Focal) Importance: Undecided Status: New -- 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/1978295 Title: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968548] Re: firefox unable to open files from file-roller
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 would be acceptable to allow firefox
(and other browser snaps) to read files under @{HOME}/.cache/fr-*/, by
amending an existing snapd interface.
Or could file-roller be patched to use the OpenFile method of the
FileChooser portal (https://flatpak.github.io/xdg-desktop-portal/#gdbus-
method-org-freedesktop-portal-FileChooser.OpenFile)? Would you mind
filing a file-roller bug at https://gitlab.gnome.org/GNOME/file-
roller/-/issues to request this, and link back to it here?
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
** Tags added: snap
** Changed in: firefox (Ubuntu)
Importance: Undecided => Medium
** Summary changed:
- firefox unable to open files from file-roller
+ firefox snap unable to open files from file-roller
** Also affects: file-roller (Ubuntu)
Importance: Undecided
Status: New
** Changed in: file-roller (Ubuntu)
Status: New => Confirmed
--
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 files from file-roller
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1968548/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1973596] [NEW] SRU 1.14.3-0ubuntu3 to jammy
Public bug reported:
[Impact]
When testing native messaging support with the firefox snap (not yet
released, see https://github.com/flatpak/xdg-desktop-portal/pull/705),
gnome-shell won't prompt the user for permission to authorize a given
extension to access the portal, because the app id being passed to the
authorization request isn't what gnome-shell expects. This is
https://github.com/flatpak/xdg-desktop-portal/issues/769.
As a consequence, access is always denied, and native messaging just
doesn't work.
The patch that fixes this issue was discussed with the author of the
native messaging portal (James Henstridge) and approved by him, and is
now being cherry-picked here.
[Test Plan]
On jammy, fetch and install the latest test snap from
https://launchpad.net/~osomon/+snap/firefox-native-messaging (manual
installation requires the --dangerous flag).
Install the chrome-gnome-shell native connector (`sudo apt install
chrome-gnome-shell`).
Open firefox and browse to
https://addons.mozilla.org/firefox/addon/gnome-shell-integration/.
Click the "Add to Firefox" button on the page.
Accept the authorization request that appears as a popup to install the GNOME
Shell integration extension.
Browse to https://extensions.gnome.org/local/.
You should be getting a GNOME Shell modal dialog that prompts you whether to
allow Firefox to make use of the WebExtensions portal to launch the
org.gnome.chrome_gnome_shell native connector.
Without this patch, GNOME Shell silently rejects the authorization request, and
you won't see any prompt.
Note that if you've tested the functionality before installing the
patched version of xdg-desktop-portal, you'll need to delete the
database that stores the permissions on disk
(~/.local/share/flatpak/db/webextensions) and restart the portal.
[Where problems could occur]
This patch affects a portal that is not being used anywhere yet (the
implementation in the Firefox snap is work in progress and serves as a
proof of concept). So there is no risk of affecting existing
functionality or other portals.
At worst, 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)
Status: In Progress
** Changed in: xdg-desktop-portal (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: xdg-desktop-portal (Ubuntu)
Importance: Undecided => Medium
** Changed in: xdg-desktop-portal (Ubuntu)
Status: New => Fix Released
** Also affects: xdg-desktop-portal (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: xdg-desktop-portal (Ubuntu Jammy)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: xdg-desktop-portal (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: xdg-desktop-portal (Ubuntu Jammy)
Status: New => In Progress
--
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/1973596
Title:
SRU 1.14.3-0ubuntu3 to jammy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973596/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964541]
(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 details. -- 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/1964541 Title: Cannot use Drag and Drop in gnome-shell 42 (Wayland session) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking
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 up after locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking
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 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 up after locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking
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. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking
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 up after locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
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 Bugzilla #1725245 https://bugzilla.mozilla.org/show_bug.cgi?id=1725245 -- 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/1964541 Title: Cannot use Drag and Drop in gnome-shell 42 (Wayland session) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
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 to xwayland, the firefox snap in beta and edge will still do wayland natively. -- 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/1964541 Title: Cannot use Drag and Drop in gnome-shell 42 (Wayland session) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking
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" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5579395/+files/journal-with-kms-debug.log ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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 up after locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking
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 https://gitlab.gnome.org/GNOME/mutter/-/issues/2216 -- 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 up after locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964541]
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
mutter in jammy with the following patch, and the issue with the firefox
snap was gone:
--- a/src/core/events.c
+++ b/src/core/events.c
@@ -523,10 +523,6 @@ meta_display_handle_event (MetaDisplay
#ifdef HAVE_WAYLAND
if (wayland_compositor && !bypass_wayland)
{
- if (window && event->type == CLUTTER_MOTION &&
- event->any.time != CLUTTER_CURRENT_TIME)
-meta_window_check_alive_on_event (window, event->any.time);
-
if (meta_wayland_compositor_handle_event (wayland_compositor, event))
bypass_clutter = TRUE;
}
--
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/1964541
Title:
Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over program after resuming from blank screen
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 windows (e.g. firefox snap, gedit deb) is now maximized under the dock. It looks like the fix for bug #1917939 isn't enough. -- 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/1961508 Title: Dock displaying over program after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking
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: Blanked screen doesn't wake up after locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
** 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 you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot use Drag and Drop in gnome-shell 42 (Wayland session) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking
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" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1968040/+attachment/5577651/+files/journal.log -- 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: Blanked screen doesn't wake up after locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] [NEW] Blanked screen doesn't wake up after locking
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 a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages uec-images wayland-session ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965085] Re: Login screen sometimes unresponsive to mouse clicks (after waking from sleep)
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965085] Re: Login screen sometimes unresponsive to mouse clicks (after waking from sleep)
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965085] Re: Login screen sometimes unresponsive to mouse clicks (after waking from sleep)
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 with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). Daniel, I can file a separate bug if you think it deserves one, but it has enough similarities with the description that I thought I'd first comment here. I'm also happy to help debugging the problem and/or test potential fixes. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome
** 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 keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1831039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965113] Re: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions if a Wayland session has been used
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 session if there's a lingering wayland socket (https://github.com/snapcore/snapcraft/blob/main/extensions/desktop/common/desktop- exports#L240). It is not specific to the firefox snap, and it can be worked around by running the apps with DISABLE_WAYLAND=1. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-session/-/issues #75 https://gitlab.gnome.org/GNOME/gnome-session/-/issues/75 ** Package changed: firefox (Ubuntu) => gnome-session (Ubuntu) ** Also affects: gnome-session via https://gitlab.gnome.org/GNOME/gnome-session/-/issues/75 Importance: Unknown Status: Unknown ** Also affects: snapcraft Importance: Undecided Status: New ** Summary changed: - Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions if a Wayland session has been used + Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used -- 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/1965113 Title: Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1965113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** 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 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 open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10
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 again and share feedback here? -- 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/1950040 Title: Wayland Screensharing broken in Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10
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 -- 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/1950040 Title: Wayland Screensharing broken in Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
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 close (or manage) windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
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 Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4340 https://gitlab.gnome.org/GNOME/gtk/-/issues/4340 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/4340 Importance: Unknown Status: Unknown ** Changed in: firefox (Ubuntu) Status: Confirmed => Invalid ** Bug watch added: Mozilla Bugzilla #1722369 https://bugzilla.mozilla.org/show_bug.cgi?id=1722369 ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1953694] Re: wayland clipboard handing locks up in certain corner cases
*** 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, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1953694 Title: wayland clipboard handing locks up in certain corner cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1953694/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10
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 added: Mozilla Bugzilla #1731495 https://bugzilla.mozilla.org/show_bug.cgi?id=1731495 -- 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/1950040 Title: Wayland Screensharing broken in Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
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. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950484] Re: Adding an admin user a Gnome Control Center should set the right groups
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1950484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950484] Re: 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: https://salsa.debian.org/freedesktop- team/accountsservice/-/commit/b1724af16828c08543cfae167daad46269051028. This would require version 0.6.55-2. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1950484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950484] Re: Adding an admin user a Gnome Control Center should set the right groups
** 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 Gnome Control Center should set the right groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1950484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10
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. https://bugs.launchpad.net/bugs/1950040 Title: Wayland Screensharing broken in Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** 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 open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
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 you? -- 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 open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1940925] Re: [FFe] Do not activate spread view on first boot
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 bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1940925/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
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: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1932328/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1938630] Re: Sorting by Évaluation
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1938630/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925266] Re: Ubuntu should have two web browsers installed by default.
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 doesn't confuse them further about what a web browser is). That would also raise some interesting questions, like where to open a link from another application by default? ** Changed in: gnome-software (Ubuntu) Status: New => Opinion -- 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/1925266 Title: Ubuntu should have two web browsers installed by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1925266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1919043] Re: gnome-software-dev misses dependencies required for development
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 in Ubuntu. https://bugs.launchpad.net/bugs/1919043 Title: gnome-software-dev misses dependencies required for development To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1919043/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915498] Re: Copy / paste in Firefox randomly broken
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 randomly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1915498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1914868] Re: gnome-software-dev doesn't contain all the header files in /usr/include/gnome-software
** 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 contain all the header files in /usr/include/gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1914868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1914868] Re: gnome-software-dev doesn't contain all the header files in /usr/include/gnome-software
** 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: gnome-software-dev doesn't contain all the header files in /usr/include/gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1914868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881197] Re: No network usage info presented, always 0 bytes/s.
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- + monitor/-/issues/142), and includes translation updates for a few + languages, but these won't impact the package in Ubuntu because it uses + the gnome language packs + + [Test Case] + + * In gnome-system-monitor's preferences window, in the resources tab, set the update interval to 0.5 seconds + * Open the resources tab and watch the network traffic graph while generating incoming and outgoing traffic (for example by running speedtest-cli) + * Expected result: outgoing and incoming traffic on the graph is consistent with the actual traffic + * Actual result without the bugfix in 3.36.1: the graph shows null outgoing and incoming traffic, even though the totals seem to be updated in the labels below the graph + + [Where problems could occur] + + * Given the one and only code change in this update is a one-liner that + adds a cast to double (https://gitlab.gnome.org/GNOME/gnome-system- + monitor/-/commit/3e916c4ee21cede8465e9378fa07e9a71a472c2f), regression + potential seems fairly limited. Looking at the code in more details, the + change is in a function that is used only to draw the network traffic + graph, it's not common code used to draw other graphs. So verifying that + the bug is indeed fixed should be enough to be confident there are no + regressions. Testing should be carried out with various values for the + update interval, both integers and non-integers. + + * As mentioned in the impact section, this update includes translation + updates, but those shouldn't apply because translations for gnome- + system-monitor are shipped externally as part of the language-pack- + gnome-*-base packages + + [Original description] + 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) gnome-system-monitor: - Instalado: 3.36.0-1 - Candidato: 3.36.0-1 - Tabela de versão: - *** 3.36.0-1 500 - 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status - 3.28.1-1 500 - 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Instalado: 3.36.0-1 + Candidato: 3.36.0-1 + Tabela de versão: + *** 3.36.0-1 500 + 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages + 100 /var/lib/dpkg/status + 3.28.1-1 500 + 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) There should be a graph drawn with the info about my network usage, as well as number on the download/upload speeds. 4) Pretty much nothing happens. It calculates how much data I've downloaded/uploaded since the OS was booted, but that's it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 17:51:55 2020 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2019-12-06 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: - LANGUAGE=pt_BR:pt:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pt_BR.UTF-8 - SHELL=/bin/bash + LANGUAGE=pt_BR:pt:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pt_BR.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-04-25 (33 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1881197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871069] Re: Speed in network history grossly exaggerated
*** 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 subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1871069 Title: Speed in network history grossly exaggerated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1871069/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881197] Re: No network usage info presented, always 0 bytes/s.
** 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 (osomon) ** Changed in: gnome-system-monitor (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1881197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903329] Re: SRU the current 2.48.9 stable update
> 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 to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903329] Re: SRU the current 2.48.9 stable update
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903329] Re: SRU the current 2.48.9 stable update
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903329] Re: SRU the current 2.48.9 stable update
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 subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1902900] Re: Workspaces menu flashes when moving between workspace A and workspace B having B Firefox with a video in full screen on it
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 Title: Workspaces menu flashes when moving between workspace A and workspace B having B Firefox with a video in full screen on it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1902900/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903329] Re: SRU the current 2.48.9 stable update
Note that the fix for upstream issue 642, which is one of the drivers for this SRU, hasn't been released in the 2.50.x series yet (it's only a commit on the master branch: https://gitlab.gnome.org/GNOME/librsvg/-/commit/da90a31c6604f747f290e236045d8c79d1186747). The SRU process requires that a bug be fixed in the development release first, before considering a stable update (https://wiki.ubuntu.com/StableReleaseUpdates#Procedure). I asked Federico what his plans are for a 2.50.2 release (https://gitlab.gnome.org/GNOME/librsvg/-/issues/642#note_957195), let's see what he says before going 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 Tilloy (osomon) ** Changed in: librsvg (Ubuntu Focal) Importance: Undecided => High ** Changed in: librsvg (Ubuntu Focal) Status: New => Confirmed -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903329] Re: SRU the current 2.48.9 stable update
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1893217] Re: [nvidia] Chrome window is corrupt - has a hole in it showing the desktop
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 - has a hole in it showing the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1893217/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1894627] Re: [nvidia] Web browser distorted after hibernation/power save when idle
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894627/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1894627] Re: [nvidia] Web browser distorted after hibernation/power save when idle
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 => New -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894627/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1894627] Re: [nvidia] Web browser distorted after hibernation/power save when idle
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 browser distorted after hibernation/power save when idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894627/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884326] Re: SRU the current 2.48.7 stable update
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 applications and verified that they render correctly their UI and content). Everything looks fine, I couldn't spot any regression. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1884326 Title: SRU the current 2.48.7 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1884326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884326] Re: SRU the current 2.48.7 stable update
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. The symbols are exported in the so file though, so there is a very slim chance that they might be used in the wild. However according to http://codesearch.debian.net/ they are not used in Debian, and Google doesn't return any meaningful reference in third-party code either, so this looks quite safe to me. This is not the first time something like this happens in the librsvg Debian package without a soname bump, FWIW: https://salsa.debian.org /gnome-team/librsvg/-/commit/8c692609c3bba7d70bb269082a2e3b16f2f19007. -- 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/1884326 Title: SRU the current 2.48.7 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1884326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884326] Re: SRU the current 2.48.7 stable update
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 https://gitlab.gnome.org/GNOME/gnome-build-meta/-/tree/master/elements. Regardless, this is a bugfix update and the desktop team would like to update it as a SRU, thanks for considering it! ** Changed in: librsvg (Ubuntu Focal) Status: Incomplete => Fix Committed -- 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/1884326 Title: SRU the current 2.48.7 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1884326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884326] Re: SRU the current 2.48.7 stable update
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 Desktop Bugs, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1884326 Title: SRU the current 2.48.7 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1884326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884326] [NEW] SRU the current 2.48.7 stable update
Public bug reported: * Impact That's the current GNOME stable update, which fixes a number of issues: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke 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: In Progress ** Changed in: librsvg (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: librsvg (Ubuntu) Importance: Undecided => High ** Changed in: librsvg (Ubuntu) Status: New => Fix Released ** Also affects: librsvg (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: librsvg (Ubuntu Focal) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: librsvg (Ubuntu Focal) Importance: Undecided => High ** Changed in: librsvg (Ubuntu Focal) Status: New => In Progress -- 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/1884326 Title: SRU the current 2.48.7 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1884326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1883831] Re: my laptop screen crashes when i take my laptop with one hand in some positios , the display have multiple rectangle with white gray and pixels , after restart it is normal , this was
** 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 one hand in some positios , the display have multiple rectangle with white gray and pixels , after restart it is normal ,this was happen for two times.Yesterday and today To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1883831/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878010] [NEW] SRU the current 3.36.1 stable update
Public bug reported: * Impact That's the current GNOME stable update, which includes a handful of icon updates/fixes (https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/blob/master/NEWS). * Test case The update is part of GNOME stable updates: https://wiki.ubuntu.com/StableReleaseUpdates/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 ** Affects: adwaita-icon-theme (Ubuntu Focal) Importance: Medium Assignee: Olivier Tilloy (osomon) Status: New ** Also affects: adwaita-icon-theme (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: adwaita-icon-theme (Ubuntu Focal) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: adwaita-icon-theme (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to adwaita-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1878010 Title: SRU the current 3.36.1 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1878010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
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. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
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 crashed with SIGSEGV in cc_panel_get_title_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1639863] Re: Firefox and Thunderbird don't appear in the (new) appstream metadata
Fixed with https://bazaar.launchpad.net/~mozillateam/thunderbird/thunderbird.groovy/revision/531. ** Changed in: thunderbird (Ubuntu) Importance: Undecided => Medium ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: thunderbird (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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1639863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
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 Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
** 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, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
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. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
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
@@ -874,7 +874,7 @@
GAsyncResult *res,
gpointer user_data)
{
- g_autoptr(CcGoaPanel) self = user_data;
+ CcGoaPanel *self = CC_GOA_PANEL (user_data);
GList *providers;
GList *l;
As suggested by seb128, a minor leak is preferable than a crash (I fully
agree), so we should probably apply this as a distro-patch while we
request feedback from upstream on the proper way to fix the problem
without a leak.
--
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 crashed with SIGSEGV in
cc_panel_get_title_widget()
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1639863] Re: Firefox and Thunderbird don't appear in the (new) appstream metadata
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. https://bugs.launchpad.net/bugs/1639863 Title: Firefox and Thunderbird don't appear in the (new) appstream metadata To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1639863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1639863] Re: Firefox and Thunderbird don't appear in the (new) appstream metadata
** 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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1639863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1639863] Re: Firefox and Thunderbird don't appear in the (new) appstream metadata
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1639863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
>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: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #401 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/401 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/401 Importance: Unknown Status: Unknown -- 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 crashed with SIGSEGV in cc_panel_get_title_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
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 ** Attachment added: "launch-gcc-oa-add-ubuntu-sso.py" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+attachment/5357631/+files/launch-gcc-oa-add-ubuntu-sso.py -- 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 crashed with SIGSEGV in cc_panel_get_title_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
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 subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
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 https://gitlab.gnome.org/GNOME/gnome-control- center/-/commit/5579314a38aa3aa26e8f833661fe898d31f327f7. -- 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 crashed with SIGSEGV in cc_panel_get_title_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1639863] Re: Firefox and Thunderbird don't appear in the (new) appstream metadata
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 in: firefox (Ubuntu) Status: In Progress => Confirmed -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1639863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1639863] Re: Firefox and Thunderbird don't appear in the (new) appstream metadata
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1639863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869835] Re: Login screen randomly reverts my default keyboard layout to en-US
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 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2543 Importance: Unknown Status: Unknown -- 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/1869835 Title: Login screen randomly reverts my default keyboard layout to en-US To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869835/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869836] Re: Login screen randomly reverts my default keyboard layout to en-US
*** 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 notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1869836 Title: Login screen randomly reverts my default keyboard layout to en-US To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869836/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869835] Re: Login screen randomly reverts my default keyboard layout to en-US
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 -- 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/1869835 Title: Login screen randomly reverts my default keyboard layout to en-US To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869835/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869835] [NEW] Login screen randomly reverts my default keyboard layout to en-US
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 (fr-bépo). To give an example of the randomness, this is what I did this morning: 1) Cold booted my laptop, selected my user, typed my password, login got denied, looked at the keyboard layout indicator and realized it was en-US instead of fr-bépo 2) Selected fr-bépo in the indicator, typed my password again and successfully logged in (and indicator in the session remained fr-bépo as expected) 3) From the menu, rebooted laptop 4) On the GDM login screen, keyboard layout indicator was reverted to en-US, again 5) Changed indicator to fr-bépo, logged in, used gnome-terminal and apt to dist-upgrade, then rebooted laptop from menu 6) This time on the GDM login screen, my default preference (fr-bépo) was selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 07:16:14 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (1367 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-01-12 (78 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1869835 Title: Login screen randomly reverts my default keyboard layout to en-US To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869835/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869836] [NEW] Login screen randomly reverts my default keyboard layout to en-US
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 (fr-bépo). To give an example of the randomness, this is what I did this morning: 1) Cold booted my laptop, selected my user, typed my password, login got denied, looked at the keyboard layout indicator and realized it was en-US instead of fr-bépo 2) Selected fr-bépo in the indicator, typed my password again and successfully logged in (and indicator in the session remained fr-bépo as expected) 3) From the menu, rebooted laptop 4) On the GDM login screen, keyboard layout indicator was reverted to en-US, again 5) Changed indicator to fr-bépo, logged in, used gnome-terminal and apt to dist-upgrade, then rebooted laptop from menu 6) This time on the GDM login screen, my default preference (fr-bépo) was selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 07:16:14 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (1367 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-01-12 (78 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal rls-ff-incoming ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #462 https://gitlab.gnome.org/GNOME/gdm/-/issues/462 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1869836 Title: Login screen randomly reverts my default keyboard layout to en-US To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869836/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869836] Re: Login screen randomly reverts my default keyboard layout to en-US
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 in Ubuntu. https://bugs.launchpad.net/bugs/1869836 Title: Login screen randomly reverts my default keyboard layout to en-US To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869836/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868999] Re: Characters in the web browser do not work
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. https://bugs.launchpad.net/bugs/1868999 Title: Characters in the web browser do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868999] Re: Characters in the web browser do not work
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 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/1868999 Title: Characters in the web browser do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers
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 happens again. I'm removing the rls-ff-incoming tag for now. ** 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. https://bugs.launchpad.net/bugs/1850766 Title: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1850766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers
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. https://bugs.launchpad.net/bugs/1850766 Title: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1850766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
