[Bug 2043609] Re: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK.
I could reproduce it. The old installer makes use of the time zone location to "guess" the desired locale, but that is apparently not the case with the flutter based installer (at least not for the English variants). There is a similar issue reported at GitHub: https://github.com/canonical/ubuntu-desktop-installer/issues/2386 ** Bug watch added: github.com/canonical/ubuntu-desktop-installer/issues #2386 https://github.com/canonical/ubuntu-desktop-installer/issues/2386 ** Summary changed: - 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. + 24.04 install with a British timezone location sets en_US.UTF-8 locale ** Package changed: gnome-control-center (Ubuntu) => ubuntu-desktop- installer ** Changed in: ubuntu-desktop-installer Importance: Undecided => High ** Changed in: ubuntu-desktop-installer Status: Incomplete => Confirmed -- 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/2043609 Title: 24.04 install with a British timezone location sets en_US.UTF-8 locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2043609] Re: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK.
And another question, btw: Did you use the new flutter based installer or the "legacy" Ubiquity one? -- 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/2043609 Title: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2043609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2043609] Re: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK.
Well, that's a different issue. ;) Which time zone location did you select during the install? ** Changed in: gnome-control-center (Ubuntu) Status: Invalid => Incomplete -- 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/2043609 Title: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2043609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2043609] Re: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK.
Thanks for your report. The "Language for menus and windows" setting shows which locale is used to determine the display language. That's unrelated to the keyboard layout for typing. You find the activated keyboard layouts in Settings -> Keyboard. Closing. ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- 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/2043609 Title: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2043609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
Added yelp as affected package too, since you hit this bug if you browse the desktop guide on X11/NVIDIA. ** Also affects: yelp (Ubuntu) Importance: Undecided Status: New ** Changed in: yelp (Ubuntu) Status: New => Triaged -- 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/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2023322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037773] Re: Rebuild against latest webkit2gtk
Ok, thanks. Then we can drop the rebuild idea, so closing this bug. I also added yelp to bug #2023322. ** Changed in: yelp (Ubuntu) Status: In Progress => Invalid ** Changed in: yelp (Ubuntu) Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2037773 Title: Rebuild against latest webkit2gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037773] Re: Rebuild against latest webkit2gtk
@Jack: I don't see a yelp issue in a 23.10 Xorg session with NVIDIA. But I uploaded yelp to this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/yelp Can you please install yelp from there and confirm that it makes a difference for you compared with yelp 42.2-1 in the archive? ** Changed in: yelp (Ubuntu) Status: New => In Progress ** Changed in: yelp (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2037773 Title: Rebuild against latest webkit2gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037773] [NEW] Rebuild against latest webkit2gtk
Public bug reported: Please see this email thread: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2023-September/019607.html ** Affects: yelp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2037773 Title: Rebuild against latest webkit2gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966552] Re: IBus input method candidate box cannot follow the cursor
Marking this as invalid for ibus and ibus-libpinyin. ibus upstream provided an explanation and confirmed that the workaround makes sense. ** Changed in: ibus (Ubuntu) Status: New => Invalid ** Changed in: ibus-libpinyin (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1966552 Title: IBus input method candidate box cannot follow the cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1966552/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 389428] Re: Stop importing RTL translations for CLI apps into Ubuntu
** Changed in: ubuntu-translations Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/389428 Title: Stop importing RTL translations for CLI apps into Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/389428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033059] Re: Unable to add a printer
There are at least three bugs about that already. I don't think yet another bug would make much of a difference. :) -- 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/2033059 Title: Unable to add a printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2033059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033059] Re: Unable to add a printer
Is hplip installed? (For the case you are affected by bug #2033129.) -- 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/2033059 Title: Unable to add a printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2033059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2029148] Re: cups snap - can't add printer
I unfixed it unintentionally as regards hplip, though, see bug #2033129. ** Changed in: ubuntu-meta (Ubuntu) Status: Fix Released => 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/2029148 Title: cups snap - can't add printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2029148/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2031172] Re: Please take a stand on "screen: Use clean env when creating new tab"
Upstream does object to the use of the patch. Please see this comment: https://salsa.debian.org/gnome-team/gnome- terminal/-/commit/c808edb8#note_420724 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2031172 Title: Please take a stand on "screen: Use clean env when creating new tab" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2031172/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2031340] Re: slic3r-prusa autopkgtest flaky
** No longer affects: glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2031340 Title: slic3r-prusa autopkgtest flaky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2031340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2031340] Re: slic3r-prusa autopkgtest flaky
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2031340 Title: slic3r-prusa autopkgtest flaky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2031340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2031172] [NEW] Please take a stand on "screen: Use clean env when creating new tab"
Public bug reported: In gnome-terminal 3.49.92-2ubuntu1 d/p/screen-Use-clean-env-when- creating-new-tab.patch is disabled since the code is applied upstream in 3.49.92. However, upstream hesitates and has now reverted the code in question. Please see this commit message: https://salsa.debian.org/gnome-team/gnome-terminal/-/commit/c808edb8 ** Affects: gnome-terminal (Ubuntu) Importance: High Status: New ** Tags: mantic rls-mm-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2031172 Title: Please take a stand on "screen: Use clean env when creating new tab" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2031172/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866038] Re: By default install Noto fonts for Unicode ranges not already covered by default
As you can see in this discourse topic: https://discourse.ubuntu.com/t/let-selection-of-default-fonts-be-based- on-noto/36923 we are about to install the fonts-noto-core package by default and make Noto default throughout. ** Also affects: language-selector (Ubuntu) Importance: Undecided Status: New ** Changed in: fonts-noto (Ubuntu) Status: Confirmed => Invalid ** Changed in: language-selector (Ubuntu) Status: New => In Progress ** Changed in: language-selector (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1866038 Title: By default install Noto fonts for Unicode ranges not already covered by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1866038/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903277] Re: language layout switch does not work
Thanks for letting us know that it has improved. :) Closing. ** Changed in: gnome-shell (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/1903277 Title: language layout switch does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903277] Re: language layout switch does not work
Is this still a problem with the Ubuntu version you are using now? > This is always on machine with on/off screen. Can you explain what that means exactly. Does it only happen when you return to your session after the screen has turned black or locked? ** Package changed: language-selector (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (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/1903277 Title: language layout switch does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2025290] Re: user-accounts: GFileInfo created without standard::symlink-target
Fixed upstream. https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/701f7c6c -- 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/2025290 Title: user-accounts: GFileInfo created without standard::symlink-target To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2025290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987928] Re: gnome-control-center closes with Gtk Gio Error when trying to access keyboard shortcut details
** Changed in: gnome-control-center (Ubuntu) Status: Expired => New -- 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/1987928 Title: gnome-control-center closes with Gtk Gio Error when trying to access keyboard shortcut details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987928/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2025290] Re: user-accounts: GFileInfo created without standard::symlink-target
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2547 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2547 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2547 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/2025290 Title: user-accounts: GFileInfo created without standard::symlink-target To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2025290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2025290] Re: user-accounts: GFileInfo created without standard::symlink-target
Possibly the updated accountsservice has something to do with it. -- 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/2025290 Title: user-accounts: GFileInfo created without standard::symlink-target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2025290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2025290] [NEW] user-accounts: GFileInfo created without standard::symlink-target
Public bug reported: If I open g-c-c from terminal on an updated mantic install and switch to the Users panel, I see some warning messages (see attachment). I don't know the significance of it, but it does not look right... ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 28 20:55:07 2023 InstallationDate: Installed on 2022-05-07 (416 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-06-20 (8 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "settings-users-warning-messages.txt" https://bugs.launchpad.net/bugs/2025290/+attachment/5682583/+files/settings-users-warning-messages.txt -- 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/2025290 Title: user-accounts: GFileInfo created without standard::symlink-target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2025290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6373 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6373 -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1956916/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4467 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4467 ** Changed in: gnome-shell Status: Fix Released => Unknown ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6373 => gitlab.gnome.org/GNOME/gnome-shell/-/issues #4467 -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1956916/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6373 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6373 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6373 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1956916/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927149] Re: Irrelevant translatable strings
** Changed in: gnome-software (Ubuntu) Status: Fix Released => Fix Committed -- 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/1927149 Title: Irrelevant translatable strings To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1927149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2019906] Re: 23.04 : condensed, bold and black fonts can't be used for interface and title bar
I see the issue in Debian testing with mutter 43.4. So if the issue is not present in 22.10, and if it is a mutter thing, it may have happened somewhere between mutter 43.0 and 43.4. -- 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/2019906 Title: 23.04 : condensed, bold and black fonts can't be used for interface and title bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2019906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
On 2023-05-19 18:45, Angel D. Segarra wrote: > On 23.04 I still get a black window on first firefox start with the > proposed mutter update. Please note that installing the mutter binary package is not sufficient. I suspect that you need to do: sudo apt install libmutter-12-0/lunar-proposed gir1.2-mutter-12/lunar- proposed (and relogin) Please try that and let us know if it helps. -- 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/1987976 Title: firefox black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
** Tags added: update-excuse-lunar -- 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/1987976 Title: firefox black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
As regards the failed autopkgtest on amd64, it's reasonably not related to the proposed change, since also version 44.0-2ubuntu4 fails now (unlike before the 23.04 release). My impression is that it's a problem beyond the mutter package: Running test case... TAP version 13 # random seed: R02S29be415b178acf3a28289b5a6c5eecf4 # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation memory (GMemorySettingsBackend) for ‘gsettings-backend’ # libmutter-MESSAGE: Running Mutter Test (using mutter 44.0) as a Wayland display server Bail out! libmutter-FATAL-WARNING: Failed to open gpu '/dev/dri/card0': Couldn't find render node device for '/dev/dri/card0' Trace/breakpoint trap (core dumped) FAIL: mutter-12/closed-transient-no-input-parent-delayed-focus-default-cancelled.test (Child process exited with code 133) Running test: mutter-12/closed-transient-no-input-no-take-focus-parents.test Starting D-Bus daemons (session & system)... Launching required services... Starting mocked services... Running test case... TAP version 13 # random seed: R02Se6b3bbfe78ba522ee4e9987b0b12eb51 # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation memory (GMemorySettingsBackend) for ‘gsettings-backend’ # libmutter-MESSAGE: Running Mutter Test (using mutter 44.0) as a Wayland display server Bail out! libmutter-FATAL-WARNING: Failed to open gpu '/dev/dri/card0': Couldn't find render node device for '/dev/dri/card0' Trace/breakpoint trap (core dumped) FAIL: mutter-12/closed-transient-no-input-no-take-focus-parents.test (Child process exited with code 133) The very same failure happens in mantic: https://autopkgtest.ubuntu.com/packages/m/mutter/mantic/amd64 but somebody seems to have added a hint so 44.0-2ubuntu6 migrated to mantic-release, and I suppose doing so would be motivated for lunar/amd64 too. As regards the regular verification, I successfully accomplished the steps in the test plan using version 44.0-2ubuntu4.23.04.1 (from lunar- proposed) of the binaries built by the mutter source. ** Tags removed: verification-needed verification-needed-lunar ** Tags added: verification-done verification-done-lunar -- 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/1987976 Title: firefox black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993900] Re: "Switch input sources individually for each window" does not work when a keyboard layout is selected using the mouse
Ah, thank you! ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6484 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1032388 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032388 ** Also affects: gnome-shell (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032388 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/1993900 Title: "Switch input sources individually for each window" does not work when a keyboard layout is selected using the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1993900/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993900] Re: "Switch input sources individually for each window" does not work when a keyboard layout is selected using the mouse
@Fedon: I think this is an issue which should be better reported to GNOME upstream. But gnome-control-center is probably not the correct project, since gnome-control-center just sets the dconf value in question, while the problem is that that value is no longer honored in x11 sessions. So it would be good if you could submit an upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues If you do, please post the URL to it in a comment here. ** Package changed: gnome-control-center (Ubuntu) => gnome-shell (Ubuntu) -- 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/1993900 Title: "Switch input sources individually for each window" does not work when a keyboard layout is selected using the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993900/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003579] Re: Simulating Secondary mouse key fails
** Package changed: xkeyboard-config (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/2003579 Title: Simulating Secondary mouse key fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003581] Re: Mouse keys fails to work after a restart
Thanks for additional info. Well, it was a guess.. Replacing xkeyboard-config with gnome-shell, since I think this is a gnome-shell feature. ** No longer affects: im-config (Ubuntu) ** Package changed: xkeyboard-config (Ubuntu) => gnome-shell (Ubuntu) -- 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/2003581 Title: Mouse keys fails to work after a restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2003581/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
** Description changed:
+ [ Impact ]
+
+ On some systems, when you open the Firefox snap right after having
+ logged in into an Ubuntu on Wayland session, you are met by a black
+ window. This happens because the FF snap is run under Xwayland, and
+ Xwayland may not be enabled early enough to handle the start of the
+ application properly.
+
+ You can easily reproduce the issue in a Wayland session:
+
+ * Close Firefox
+ * Run the command "killall Xwayland" in terminal
+ * Open Firefox
+
+ An upstream mutter change addresses this issue, and the proposed lunar
+ change cherry picks that upstream change as a patch.
+
+ [ Test Plan ]
+
+ On an updated Ubuntu 23.04:
+
+ * Install the mutter related binaries from lunar-proposed
+
+ * Reboot and log in to an Ubuntu on Wayland session
+
+ * Run the command "killall Xwayland"
+
+ * Open the Firefox snap, and find that it starts normally
+
+ [ Where problems could occur ]
+
+ This is the upstream merge request in question:
+
+ https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970
+
+ The changes (except for the test related ones) are small, and
+ specifically intended to address issues like the one reported in this
+ bug. There are also reviews by a couple of experienced GNOME devs.
+
+ So even if the proposed change is not well tested yet, it seems to me
+ that the risk for adverse side effects is limited.
+
+ [ Original description ]
+
nicolas@nicolas-fixe:~$ lsb_release -rd
Description: Ubuntu 22.04.1 LTS
Release: 22.04
nicolas@nicolas-fixe:~$ apt-cache policy firefox
firefox:
Installé : 1:1snap1-0ubuntu2
Candidat : 1:1snap1-0ubuntu2
Table de version :
*** 1:1snap1-0ubuntu2 500
500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
When I boot Ubuntu and start Firefox, the Firefox's window is totally
black. See attachment.
I am at your disposal to answer any question you have.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 28 12:42:29 2022
InstallationDate: Installed on 2022-08-25 (2 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
Snap.Changes: aucun changement trouvé
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
** Also affects: firefox (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
** Also affects: mutter (Ubuntu Lunar)
Importance: High
Assignee: Gunnar Hjalmarsson (gunnarhj)
Status: In Progress
** No longer affects: firefox (Ubuntu Lunar)
** Changed in: firefox (Ubuntu)
Status: Confirmed => Invalid
--
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/1987976
Title:
firefox black window on wayland
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003581] Re: Mouse keys fails to work after a restart
This comment is a guess, and I may be completely wrong, but I wonder if this happens in Ubuntu on Xorg only. If so, it may be related to the fact that ibus wasn't always automatically enabled at the start of the session. That issue was fixed in 22.04 via bug #2007379. So, @nix, it would be interesting to know if the issue is still present after you have upgraded the im-config package to version 0.50-2ubuntu22.04.1. ** Also affects: im-config (Ubuntu) Importance: Undecided Status: New ** Changed in: im-config (Ubuntu) Status: New => Incomplete -- 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/2003581 Title: Mouse keys fails to work after a restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2003581/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
@Andreas: I just wrote this on #ubuntu-desktop: https://irclogs.ubuntu.com/2023/04/20/%23ubuntu-desktop.html#t17:57 -- 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/1987976 Title: firefox black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
Mentioned under "Known Issues" in the lunar release notes. ** Changed in: ubuntu-release-notes Status: New => Fix Released -- 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/1987976 Title: firefox black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
I'm not sure, but I think the issue was present in kinetic. Hence not a regression (probably). I agree. Only this issue would not motivate a respin, and mentioning it in the release note sounds reasonable. -- 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/1987976 Title: firefox black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
Marco Trevisan submitted an upstream mutter merge request with a fix of this issue. I have applied it to the Ubuntu package through a PPA, installed the resulting binaries, and accomplished some tests: * I can no longer reproduce the issue with a black window when opening Firefox in wayland, not even after having run "killall Xwayland". * This sequence: killall Xwayland; sleep 3; GDK_BACKEND=x11 gedit results in a normal gedit window as far as I can tell. * I also entered an x11 session, and also there I can open Firefox without issues. So I uploaded mutter to the lunar unapproved queue for consideration by the release team. ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed -- 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/1987976 Title: firefox black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
** Summary changed: - firefox black window + firefox black window on wayland ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- 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/1987976 Title: firefox black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016918] Re: Firefox snap opens a black window on wayland
*** This bug is a duplicate of bug 1987976 *** https://bugs.launchpad.net/bugs/1987976 Let's use the original bug report instead. ** This bug has been marked a duplicate of bug 1987976 firefox black window -- 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/2016918 Title: Firefox snap opens a black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016918] Re: Firefox snap opens a black window on wayland
I applied a mutter patch written by Marco Trevisan and uploaded to a PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/mutter With the binaries from that PPA build I can no longer reproduce the black window issue described in this bug. Not even after having run: killall Xwayland So I pushed the patch to the repo. https://salsa.debian.org/gnome-team/mutter/-/commit/a400e60d ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- 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/2016918 Title: Firefox snap opens a black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016918] [NEW] Firefox snap opens a black window on wayland
Public bug reported: This may actually be a duplicate of bug #1987976, but I was advised to file a new bug to get attention to this issue for the 23.04 release and consider a possible workaround. https://irclogs.ubuntu.com/2023/04/18/%23ubuntu-desktop.html#t17:42 In short: On a fresh 23.04 install, the first time in each wayland session I try to launch Firefox via the icon in the dock, it just opens a black window. I can close Firefox, and try again, and then it opens as expected. I'd better mention that I have a NVIDIA card, but the issue is present both with the NVIDIA and the Nouveau driver. While it might be some kind of race condition (not everyone is affected), in my case it happens every time. I have a proposed workaround: use the xrefresh command. That could for instance be done with this file: $ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop [Desktop Entry] Name=Launch Xwayland on startup of wayland session Comment=This allows to start the Firefox snap from the dock without a black window Type=Application Exec=sh -c 'if [ "$XDG_SESSION_TYPE" = "wayland" ]; then xrefresh; fi' TryExec=xrefresh OnlyShowIn=GNOME; NoDisplay=true That idea isn't new. We have shipped a similar file (for a similar reason) with ibus-mozc for a few cycles: https://salsa.debian.org/debian/mozc/-/commit/4e48b655 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: High Status: New ** Also affects: firefox (Ubuntu) Importance: Undecided Status: 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/2016918 Title: Firefox snap opens a black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window
This fixes the issue for me: $ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop [Desktop Entry] Name=Launch Xwayland on startup of wayland session Comment=This allows to start the Firefox snap from the dock without a black window Type=Application Exec=sh -c 'if [ "$XDG_SESSION_TYPE" = "wayland" ]; then xrefresh; fi' TryExec=xrefresh OnlyShowIn=GNOME; NoDisplay=true How about letting some package install that, or maybe make use of the xrefresh command in some other way. -- 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/1987976 Title: firefox black window To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927149] Re: Irrelevant translatable strings
During a discussion here: https://salsa.debian.org/gnome-team/gnome-software/-/commit/6e0534db the idea was born to address this issue in a more generic way via dh- translations. So I submitted a pkgbinarymangler merge proposal (see link above). ** Also affects: pkgbinarymangler (Ubuntu) Importance: Undecided Status: New ** Changed in: pkgbinarymangler (Ubuntu) Status: New => In Progress ** Changed in: pkgbinarymangler (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Merge proposal linked: https://code.launchpad.net/~gunnarhj/+git/pkgbinarymangler/+merge/440954 -- 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/1927149 Title: Irrelevant translatable strings To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1927149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015610] [NEW] Input source indicator not shown
Public bug reported: In my 23.04 development installation I installed the ubuntu-unity- desktop package and then logged in to Unity. One observation is that the input source indicator is not shown in the top bar, even if that feature is enabled in Text Entry. Please see the attached screenshot. I can successfully switch between the input sources in the list using Super+Space. First I suspected that this ibus patch has something to do with it: https://salsa.debian.org/debian/ibus/-/blob/master/debian/patches/ubuntu- forward-panel-properties.patch It's there for Unity only. But since the issue is present also with ibus disabled, that does not appear to be the case. ** Affects: indicator-keyboard (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-unity-meta (Ubuntu) Importance: Undecided Status: New ** Tags: lunar ** Attachment added: "no-input-source-indicator.png" https://bugs.launchpad.net/bugs/2015610/+attachment/5662071/+files/no-input-source-indicator.png ** Also affects: ubuntu-unity-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/2015610 Title: Input source indicator not shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/2015610/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012738] Re: language support crashes on install missing translations or writing aids
** Changed in: devscripts (Ubuntu) Status: Fix Committed => Fix Released -- 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/2012738 Title: language support crashes on install missing translations or writing aids To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/2012738/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012788] Re: Entering Unicode characters with code points broken
This is under control now. An upstream ibus commit fixes it (see discussion at upstream issue). Fix uploaded to Debian experimental. ** Changed in: ibus (Ubuntu) Status: Confirmed => In Progress ** Changed in: ibus (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** No longer affects: glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2012788 Title: Entering Unicode characters with code points broken To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2012788/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012788] Re: Entering Unicode characters with code points broken
** Bug watch added: github.com/ibus/ibus/issues #2496 https://github.com/ibus/ibus/issues/2496 ** Also affects: ibus via https://github.com/ibus/ibus/issues/2496 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2012788 Title: Entering Unicode characters with code points broken To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2012788/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
I still have an issue. Not sure if it is related. When clicking the Firefox icon in the dock, a completely black window opens. Then I can close it and try again, and the second time it works as expected. This repeats itself in each session. -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012736] Re: language and region > login screen > formats does not display United Kingdom
Now fixed in upstream's main, and patch in the Ubuntu branch: https://salsa.debian.org/gnome-team/gnome-control- center/-/commit/c25acdf4 ** 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/2012736 Title: language and region > login screen > formats does not display United Kingdom To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2012736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012942] Re: Unable to switch to Chinese IME from Russian
That's expected behavior. But you can change it to better fit your situation: * Open /usr/share/ibus/component/libpinyin.xml for editing. * For the libpinyin engine, change this line: default to: us ** Changed in: ibus-libpinyin (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/2012942 Title: Unable to switch to Chinese IME from Russian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/2012942/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012940] Re: English word as top candidate for some pinyin input
Thanks for your report! I noticed the same thing a while ago, and reported it upstream. The upstream maintainer moved the English candidates after the sentence candidates, and the new behavior should be present in Ubuntu 23.04. ** Changed in: ibus-libpinyin (Ubuntu) Status: New => Fix Released ** Bug watch added: github.com/libpinyin/ibus-libpinyin/issues #378 https://github.com/libpinyin/ibus-libpinyin/issues/378 ** Also affects: ibus-libpinyin via https://github.com/libpinyin/ibus-libpinyin/issues/378 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/2012940 Title: English word as top candidate for some pinyin input To manage notifications about this bug go to: https://bugs.launchpad.net/ibus-libpinyin/+bug/2012940/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012788] Re: Entering Unicode characters with code points broken
If I install ibus 1.5.28-2 from experimental on Debian, there is no code point issue. While the source is identical with 1.5.28-2 on Ubuntu, the binaries on Debian were built with older versions of some libraries. I'm not sure that the problem lies in glib. It's simply my intuition. ;) ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2012788 Title: Entering Unicode characters with code points broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2012788/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012788] Re: Entering Unicode characters with code points broken
Yes, Heinrich, on the surface this seems to be an ibus issue. But I think the root cause lies in some package which ibus is built with. If I downgrade to the binaries built by ibus 1.5.28-1 on February 23, using code points works fine. In 1.5.28-2 two upstream commits were added as patches, but if I now build ibus with those patches disabled, it doesn't help. A no-change rebuild does not help either. Maybe glib is the culprit? ibus 1.5.28-1 was built with glib 2.74. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2012788 Title: Entering Unicode characters with code points broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2012788/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012788] Re: Entering Unicode characters with code points broken
Happens in both x11 and wayland sessions. -- 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/2012788 Title: Entering Unicode characters with code points broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012788/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012788] [NEW] Entering Unicode characters with code points broken
Public bug reported: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. ** Affects: gnome-shell (Ubuntu) Importance: High Status: New ** Tags: lunar regression-release rls-ll-incoming -- 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/2012788 Title: Entering Unicode characters with code points broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012788/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012736] Re: language and region > login screen > formats does not display United Kingdom
Thanks. That helped me reproduce it. It's an upstream thing, and I reported it via the linked upstream issue. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => In Progress ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2418 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2418 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2418 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/2012736 Title: language and region > login screen > formats does not display United Kingdom To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2012736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012736] Re: language and region > login screen > formats does not display United Kingdom
Thanks for your report. I made a quick test, and couldn't reproduce the behavior. After having set "United Kingdom", can you please run the below terminal commands and show us what they output in a comment here. cat /etc/default/locale locale -a locale ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/2012736 Title: language and region > login screen > formats does not display United Kingdom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012552] Re: /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now
Now I have tested too. :/ Switching language does not result in an attempt to reset region, and seems to work as expected. I can no longer reproduce any errors or warnings when starting g-c-c from terminal. ** Changed in: accountsservice (Ubuntu) Status: Incomplete => Invalid -- 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/2012552 Title: /usr/libexec/accounts- daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012552/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012552] Re: /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now
I think I found it: https://salsa.debian.org/gnome-team/gnome-control- center/-/commit/5400a142 Uploaded g-c-c, but keeping the accountsservice task open for now until we see that the problem is no longer present. ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- 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/2012552 Title: /usr/libexec/accounts- daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012552/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011313] Re: gnome-control-center crashes after launch
Thanks for your follow-up, Mark! -- 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/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011313] Re: gnome-control-center crashes after launch
g-c-c 1:44~rc-1ubuntu1 has migrated to lunar-release. ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Released -- 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/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011717] Re: settings crash on open
*** This bug is a duplicate of bug 2011313 *** https://bugs.launchpad.net/bugs/2011313 Thanks for your report. I suspect this is a duplicate of bug #2011313, so marking it as such. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011717/+attachment/5654657/+files/CoreDump.gz ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 2011313 gnome-control-center crashes after launch -- 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/2011717 Title: settings crash on open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011717/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
On 2023-03-14 09:09, Tigran Aivazian wrote: > So, you are saying that with this version I don't need the file > /etc/profile.d/input-method-config.sh and can simply remove it? No. I said that you can do that if you are on an Ubuntu version > 20.04. Given the version you actually are on, instead I would suggest that you reinstall im-config: sudo apt-get install --reinstall im-config That's because the error message indicates that the installation of im- config is not complete. Maybe you tried to partly uninstall it. "E: Script for none not found at run_im." Well, "script for none" should be there: $ ls -1 /usr/share/im-config/data | grep none 78_none.conf 78_none.rc and a reinstall ought to restore those files. Or you can keep your return at the top of the file. That won't hurt if you don't use any input method. > The im-config package could not be removed without removing > gnome-control-center That's true, and the reason is that language-selector-gnome depends on im-config. I should probably relax that to a recommends. > except the strange fact that this file was not removed when im-config > was updated during the normal "sudo apt update" procedure at some point Not strange at all, actually, since you are on bionic. -- 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/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
Another theory is that you may have removed the im-config package without purging it. In latter im-config versions we prevent such a measure from leading to issues, but in the version uploaded due to this bug there was no such protection. -- 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/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
@Tigran: It struck me that /etc/profile.d/input-method-config.sh is an ancient file. Yes, it was introduced in 2017 due to this bug as a fix or workaround, but it was dropped long ago. If you are on an Ubuntu version > 20.04, you can safely just remove it. So how could that happen? My guess is that you at some point of time took a shortcut when upgrading your Ubuntu version. You seem to have switched from some version before 20.04 directly to some version after 20.04. Skipping an LTS like that is not a supported upgrade path, and may result in issues like this one. So I don't think there is much to report. ;) -- 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/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011313] Re: gnome-control-center crashes after launch
On 2023-03-13 07:52, Mark Smith wrote: > Do you know when 1:44~rc will be merged? It has already been merged into the repo. Refreshing one or two patches remains. I would guess it will be uploaded to lunar very soon. -- 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/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011313] Re: gnome-control-center crashes after launch
Yeah.. That "Couldn't get locale for language: (null)" warning comes from a patch which I wrote initially, and first I feared that the segfault is related to that. But it's not. I committed a fix which will get rid of the warning in this situation: https://salsa.debian.org/gnome-team/gnome-control- center/-/commit/53e9a9a2 But it still segfaults. For some reason it fails to fetch the user data properly. My thought is that since the problem seems to be gone in g-c-c 1:44~rc, it's not worth it to figure out why exactly the alpha version crashes. -- 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/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011313] Re: gnome-control-center crashes after launch
Sorry, I was on Ubuntu 22.04 when testing that command, but they seem to have changed the schema name. On 23.04 this would have worked: gsettings reset org.gnome.Settings last-panel -- 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/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
Well, I don't claim that im-config is bug free forever after the fix of this bug. New issues show up. My point is that trying to revive an old and closed bug report is simply not the right way to call the developers' attention to new issues. My advice still stands: Use Ask Ubuntu to get help to sort things out. If you conclude that there is a bug, you are welcome to submit a new bug report about your problem. -- 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/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011313] Re: gnome-control-center crashes after launch
Btw, you can run this terminal command: gsettings reset org.gnome.ControlCenter last-panel and then you should be able to successfully open Settings. But avoid "Users" for now. -- 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/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011313] Re: Ubuntu-Settings crashes after launch
Thanks for your report! I see the same thing when trying to switch to the Users panel with gnome-control-center 1:44~alpha-0ubuntu1, but the issue seems not to be present in the coming version 1:44~rc-1ubuntu1. So stay tuned. :) ** Summary changed: - Ubuntu-Settings crashes after launch + gnome-control-center crashes after launch ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Jeremy Bícha (jbicha) -- 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/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
@Tigran: This bug was closed several years ago, and there is absolutely no point in adding comments to it now. If you have found a new bug, please report it separately. If you need support, please visit some resource for that, e.g. https://askubuntu.com . My guess is that the latter applies to your case. -- 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/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2004241] Re: Update to glib >= 2.75.1
@Daniel: It's already in -proposed. And there are more packages which depend on glib >=2.75. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2004241 Title: Update to glib >= 2.75.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
Added the block-proposed tag to bug #2004241 instead. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2004241] Re: Update to glib >= 2.75.1
While the issue in bug #2008279 will be fixed via a snapd change, it was caused by a glib change. We don't want glib2.0 >=2.75 to migrate before snapd 2.58.3+23.04ubuntu1 has made it to lunar-release and has been confirmed to fix the issue. ** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2004241 Title: Update to glib >= 2.75.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
Removing block-proposed again after a short IRC talk with Sebastien. We don't want to prevent snapd from migrating. ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
Great, Seb. Guess we'd better remove the block-proposed tag then. ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
@Michael: Any chance you can make a new bug fix release of snapd soon? This issue blocks quite a few packages from migrating to lunar-release. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu) Importance: Undecided => High ** Changed in: snapd (Ubuntu) Status: New => In Progress ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => James Henstridge (jamesh) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg
** Description changed: Test Case - From Ubuntu 23.04, install glib >= 2.75.3-3 + + Test 1: Log out Click your name on the login screen. Click the gear button to choose Ubuntu on Xorg Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. + Test 2: + Install the ibus-libpinyin package. + Log out and log in again. + Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)" + to your input sources. + Log out + Click your name on the login screen. + Click the gear button to choose Ubuntu (on Wayland). + Enter your password to finish logging in. + Open Firefox (or Chromium) + Try to enter text in the address bar. + What Happens - No text is input + No text is inputted Other Info -- - This issue appears to only affects the Xorg session. + You see the issue as soon as IBus has been 'turned on'. With the current g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 session IBus is always turned on due to im-config 0.55-1. In a Wayland session you need to tell it to turn IBus on by either adding an IBus input method to your input sources or make use of the Screen Keyboard feature. And I've only seen the issue with the Firefox and Chromium snaps. + Warning message if you start firefox from terminal: + + [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could not + connect: Permission denied: 'glib warning', file + /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167 + + (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to + ibus: Could not connect: Permission denied + gnome-settings-daemon - - It also affected the Wayland session with gnome-settings-daemon 44 Beta, but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93 + gnome-settings-daemon 44 Beta makes the situation worse since it always turns IBus on in both Wayland and X11, but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. - - The issue happens with kinetic's gnome-settings-daemon 43; it just looks - like the gnome-settings-daemon commit made the situation worse but that - commit was reverted. ** Summary changed: - glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg + glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps ** Summary changed: - glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps + glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
** Tags added: lunar -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
@Jeremy: I figured out the nature of the issue you originally reported in this bug. With this combo: $ dpkg-query -W libglib2.0-0 gnome-settings-daemon gnome-settings-daemon 44~beta-1ubuntu1 libglib2.0-0:amd64 2.75.3-3 and as long as no IBus IM has been added to the list of input sources, you can successfully run the Firefox snap in a wayland session. I.e. with that upstream gnome-settings-daemon commit reverted. If you had tried an x11 session, you'd have found that the reversal didn't help (because of im-config 0.55-1). And if you had added some IBus IM (and re-logged in), you'd likewise have found that the reversal didn't help. What does help in all cases ATM is to downgrade the glib2.0 packages to 2.74. So somehow the snaps need to be able to talk with ibus also when glib2.0 2.75 is present. ** Tags removed: update-excuse -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
ibus in lunar-release was built against glib2.0 2.74.5-1. I tried a no- change rebuild of ibus against glib2.0 2.75.3-3, but it didn't help. (Such a rebuild may still be motivated later.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
Want to mention that the issue is not present with glib2.0 2.75.3-3 if fcitx5 is used instead of ibus. :/ ** Also affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
With glib2.0 2.75.3-3 installed and when starting the Firefox snap from terminal I see these warning messages: [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could not connect: Permission denied: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167 (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to ibus: Could not connect: Permission denied FTR the issue is present on both wayland and x11. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
** Summary changed: - xsettings ibus commit broke text input for Firefox & Chromium snaps + glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps ** No longer affects: gnome-settings-daemon (Ubuntu) ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => High ** Tags added: rls-ll-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: xsettings ibus commit broke text input for Firefox & Chromium snaps
Hmm.. Suddenly I could no longer type in the address bar of the Firefox snap. But I think the culprit is glib2.0 2.75.3-3, which I installed from -proposed yesterday in order to test build g-c-c from ubuntu/master. After having downgraded glib2.0 to 2.74.5-1 the issue is no longer present. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags added: block-proposed update-excuse -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: xsettings ibus commit broke text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008770] Re: Sound: seg fault if env variable not set (v41.7)
Thanks for your report! Well, "the user" normally has that variable set. ;) But it's still a valid bug. I pushed a fix to the repo, so it will be fixed in Ubuntu 23.04. ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- 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/2008770 Title: Sound: seg fault if env variable not set (v41.7) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2008770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: xsettings ibus commit broke text input for Firefox & Chromium snaps
Please disregard my "couldn't login" talk in the previous comment. I was confused. Not the first time in history, and not the last. So: The version in my PPA (including that upstream g-s-d commit) works fine for me on my regular lunar install. I can type in the address bar in both the Firefox and the Chromium snap. It also lets me revert the latest im-config change, and it still works on x11 without the issue described in bug #2007379. As expected, in other words. (My VirtualBox "can't login to x11" issue is still there, though. But that's another story.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: xsettings ibus commit broke text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: xsettings ibus commit broke text input for Firefox & Chromium snaps
I built g-s-d in a PPA with the revert reverted: https://launchpad.net/~gunnarhj/+archive/ubuntu/gnome-settings- daemon/+packages On wayland I see no difference; everything works as expected. Also with a fresh lunar install in VirtualBox. But my observations on Xorg with my regular install was a bit surprising. With im-config 0.55-1 present (i.e. GTK_IM_MODULE set to "ibus"), I do not notice any problems with the upstream g-s-d commit. I can type in the Firefox address bar — also in Chinese. But if I revert the latest im-config change, so nothing sets GTK_IM_MODULE, I can't even log in to "Ubuntu on Xorg". So my first theory seems to be very wrong, and rather the opposite is true: The upstream g-s-d commit works for me *only* if also GTK_IM_MODULE is set to "ibus". As regards the VirtualBox fresh install: Couldn't log in to x11 now either. (And this time I used the version of VirtualBox from lunar- release.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: xsettings ibus commit broke text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008451] Re: Ibus-libpinyin crashes after screen lock
"After screen lock" indicates that gnome-shell is involved. Also note: NVIDIA + wayland ** 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/2008451 Title: Ibus-libpinyin crashes after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2008451/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: xsettings ibus commit broke text input for Firefox & Chromium snaps
Btw, im-config 0.55-1 is not in Debian testing yet, which might be the reason why you didn't see the issue there. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: xsettings ibus commit broke text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: xsettings ibus commit broke text input for Firefox & Chromium snaps
Wow.. This is "interesting". Compare this with bug #2007379, where we work around the problem which the now reversed upstream g-s-d commit tries to address. (I wasn't aware of this upstream move.) im-config 0.55-1 is already in lunar-release. Can the fact that im- config now sets GTK_IM_MODULE=ibus be the reason why the upstream commit didn't work out well? Would that g-s-d commit possibly work for us with GTK_IM_MODULE unset? I think this is worth to investigate. At least the g-s-d commit is the right idea. As regards the recent im-config change, I suppose it's motivated in both jammy and Debian 12. (And also in lunar unless we figure out how to avoid the regression you describe in this bug.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: xsettings ibus commit broke text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: xsettings ibus commit broke text input for Firefox & Chromium snaps
** Description changed: While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- - daemon/-/commit/baeeed + daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. I was unable to reproduce the issue on Debian Testing but there may have been differences in how snap was configured there. I'm filing this bug since ideally we would not be diverging from upstream here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: xsettings ibus commit broke text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
