[Bug 1968395] [NEW] Wayland
Public bug reported: Wayland is with the black screen when I share it. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 Uname: Linux 5.16.0-051600-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 01:40:22 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-20 (19 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-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/1968395 Title: Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968395/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889057] Re: shares-admin can't install services - failed to install package: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .s
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- 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/1889057 Title: shares-admin can't install services - failed to install package: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1889057/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904460] Re: Gnome disks icon is missing when upgraded from 18.04 to 20.04
[Expired for gnome-disk-utility (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-disk-utility (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1904460 Title: Gnome disks icon is missing when upgraded from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1904460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964442] Re: Key repeats forever if a shell popover steals focus during a keypress
** Changed in: gnome-shell (Ubuntu Jammy) Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: mutter (Ubuntu Jammy) Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu Jammy) Status: In Progress => Won't Fix ** Changed in: mutter (Ubuntu Jammy) 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/1964442 Title: Key repeats forever if a shell popover steals focus during a keypress To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1964442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968390] [NEW] JS ERROR: TypeError: this.window_container is null
Public bug reported: Ubuntu 22.04 Development A 3 finger touchpad swipe up/down gesture with 1 application open outputs a lot of JS errors and stacks to the journal. This issue may be the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 but the output is somewhat different when you have more than 1 app open. This also happens with all extensions disabled, does not happen in Fedora 36. To reproduce 1. login and open terminal and watch the journal 2. perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 3. See journal Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Button (0x56219f5b8060), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:566 (4ce0bb0ac40 @ 10) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:567 (4ce0bb0ac40 @ 36) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:570 (4ce0bb0ac40 @ 77) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:638 (4ce0bb0ae20 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:353 (4ce0bb0a5b0 @ 62) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:357 (4ce0bb0a5b0 @ 87) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:364 (4ce0bb0a600 @ 8) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:160 (330c4e3cc560 @ 43) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a9a70 b resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #4 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08 21:18:49 x1c gnome-shell[21675]: #5 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Label (0x56219f5a8440), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a98b0 b resource:///org/gnome/shell/ui/environment.js:361 (330c4e3ccc90 @ 43) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:163 (330c4e3cc560 @ 91) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 7ffc4c0a9a70 b resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109) Apr 08 21:18:49 x1c gnome-shell[21675]: #4 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #5 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08
[Bug 1964541]
Update from the launchpad bug:
I bisected mutter and gnome-shell until I identified the revision in
mutter that caused the regression:
https://gitlab.gnome.org/GNOME/mutter/-/commit/26676a829e74859488154cd8c45de1d0b629f3ca.
More specifically, the changes to src/core/events.c. Indeed I rebuilt
mutter in jammy with the following patch, and the issue with the firefox
snap was gone:
--- a/src/core/events.c
+++ b/src/core/events.c
@@ -523,10 +523,6 @@ meta_display_handle_event (MetaDisplay
#ifdef HAVE_WAYLAND
if (wayland_compositor && !bypass_wayland)
{
- if (window && event->type == CLUTTER_MOTION &&
- event->any.time != CLUTTER_CURRENT_TIME)
-meta_window_check_alive_on_event (window, event->any.time);
-
if (meta_wayland_compositor_handle_event (wayland_compositor, event))
bypass_clutter = TRUE;
}
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1964541
Title:
Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964541]
(In reply to Olivier Tilloy from comment #7)
> Update from the launchpad bug:
>
> I bisected mutter and gnome-shell until I identified the revision in mutter
> that caused the regression:
> https://gitlab.gnome.org/GNOME/mutter/-/commit/26676a829e74859488154cd8c45de1d0b629f3ca.
>
> More specifically, the changes to src/core/events.c. Indeed I rebuilt mutter
> in jammy with the following patch, and the issue with the firefox snap was
> gone:
>
> --- a/src/core/events.c
> +++ b/src/core/events.c
> @@ -523,10 +523,6 @@ meta_display_handle_event (MetaDisplay
> #ifdef HAVE_WAYLAND
>if (wayland_compositor && !bypass_wayland)
> {
> - if (window && event->type == CLUTTER_MOTION &&
> - event->any.time != CLUTTER_CURRENT_TIME)
> -meta_window_check_alive_on_event (window, event->any.time);
> -
>if (meta_wayland_compositor_handle_event (wayland_compositor,
> event))
> bypass_clutter = TRUE;
> }
Do you have more context on this fix? I could use some assistance on how
to implement it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1964541
Title:
Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964541]
*** Bug 1763162 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot use Drag and Drop in gnome-shell 42 (Wayland session) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821754] Re: huge files created when copying from a network drive.
** No longer affects: ubuntu-mate ** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1821754 Title: huge files created when copying from a network drive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1821754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860975] Re: Cannot set image as desktop background from Shotwell
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1860975 Title: Cannot set image as desktop background from Shotwell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1860975/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled via gnome-system-tools
** Changed in: ubuntu-mate-meta (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-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled via gnome- system-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1706770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860976] Re: Shotwell's 'Send To...' feature does not work in MATE without creating 'nautilus-sendto' link
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1860976 Title: Shotwell's 'Send To...' feature does not work in MATE without creating 'nautilus-sendto' link To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja-extensions/+bug/1860976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968213] Re: Icon theme reverts to Yaru when entering Appearance settings
Well, in Ubuntu we don't support custom themes when you use the Ubuntu session (while you're free to tweak your GNOME session when using that - need to apt install gnome-session). So if you change the accent color, both icon and gtk themes will be changed. We may avoid changing them if a non-Yaru theme was used previously, but I've the feeling that we'd may instead look as broken for those people who have customized their ubuntu session previously and they now want to switch to one of the stock yaru themes. -- 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/1968213 Title: Icon theme reverts to Yaru when entering Appearance settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
This issue is caused by the Users and Groups utility which is part of `gnome-system-tools`. When changing the password from "Asked on logon" to "Not asked on logon" the user is added to the `nopasswdlogin` group and this is what causes the switch-user screen to not ask for a password. If you select the option to not require a password to login during installation, it is not possible to bypass authentication when switching users. This is because `autologin-user` is set to your username in `/etc/lightdm/lightdm.conf` and that works correctly. `gnome-system-tools` was originally included in Ubuntu MATE because it offers user and time management features. But it can now be removed from the Ubuntu MATE default install because recent versions of MATE Control Center provide user and time management. ** Changed in: ubuntu-mate-meta (Ubuntu) Status: Triaged => In Progress ** Summary changed: - Lock screen can be bypassed when auto-login is enabled. + Lock screen can be bypassed when auto-login is enabled via gnome-system-tools -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled via gnome- system-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1706770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
** Also affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-mate-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu) Status: Fix Committed => Invalid ** Changed in: arctica-greeter (Ubuntu) Status: New => Invalid ** Changed in: gnome-system-tools (Ubuntu) Status: New => Confirmed ** Changed in: gnome-system-tools (Ubuntu) Status: Confirmed => Triaged ** Changed in: mate-screensaver (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-mate-meta (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-mate-meta (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-mate-meta (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1706770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968099] Re: gnome shell crashes after disconnecting external monitors
- happens when windows are open on external monitor before unplugging it - happens when dock is enabled (seems not to happen when dock is disabled) -- 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/1968099 Title: gnome shell crashes after disconnecting external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968099/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968383] Re: Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been
** Description changed: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up - touch gesture to enter the application grid and then back down to return - to the desktop, journal spits out js stacktrace. + touchpad gesture to enter the application grid and then back down to + return to the desktop, journal spits out js stacktrace. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ** Summary changed: - Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. + Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. -- 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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904460] Re: Gnome disks icon is missing when upgraded from 18.04 to 20.04
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1904460 Title: Gnome disks icon is missing when upgraded from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1904460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968382] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1965702 *** https://bugs.launchpad.net/bugs/1965702 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1965702, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968382/+attachment/5578411/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1968382/+attachment/5578413/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1968382/+attachment/5578416/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1968382/+attachment/5578417/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1968382/+attachment/5578418/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1968382/+attachment/5578419/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968382/+attachment/5578420/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1965702 ** Tags removed: need-amd64-retrace -- 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/1968382 Title: gnome-control-center crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968382/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968383] [NEW] Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having be
Public bug reported: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touch gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- 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/1968383 Title: Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968382] Re: gnome-control-center crashed with SIGSEGV
** Information type changed from Private to Public -- 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/1968382 Title: gnome-control-center crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968382/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857539] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?)
** Tags added: bugpattern-needed ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1857539 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968381] Re: nautilus crashed with SIGSEGV
*** This bug is a duplicate of bug 1857539 *** https://bugs.launchpad.net/bugs/1857539 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1857539, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968381/+attachment/5578399/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1968381/+attachment/5578401/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1968381/+attachment/5578405/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1968381/+attachment/5578406/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1968381/+attachment/5578407/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1968381/+attachment/5578408/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968381/+attachment/5578409/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1857539 nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?) ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1968381 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968381/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884379] Re: Mass Storage is not unmounted after logoff
** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1884379 Title: Mass Storage is not unmounted after logoff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1884379/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889057] Re: shares-admin can't install services - failed to install package: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .s
** No longer affects: ubuntu-mate -- 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/1889057 Title: shares-admin can't install services - failed to install package: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1889057/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
** Changed in: gnome-shell (Ubuntu) Status: Triaged => Won't Fix ** Changed in: libcanberra (Ubuntu) Status: Triaged => Fix Committed ** Changed in: libcanberra (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968364] [NEW] [FFe] Switch gnome-shell to use gnome-bluetooth3
Public bug reported: Why It's Needed --- This will fix LP: #1738838 gnome-shell 42 stable release updates for Ubuntu 22.04 will be easier since we don't have to revert all the bluetooth-related commits. Why, More Details - GNOME Shell 42 uses API from the new gnome-bluetooth library to fix LP: #1738838 The API changes were not practical to forward-port (switch to a new GListModel API). Ubuntu's gnome-shell packaging had to revert ~6 commits to keep using the older gnome-bluetooth library, which is more awkward to maintain. Because of how GNOME Shell extensions work, if an extension tries to modify the bluetooth part of the system status menu in the top right corner of the screen, the extension may not work because Ubuntu's GNOME Shell 42 is different than what every other distro provides. I assess this concern as very low since extensions are "use at your own risk" and there aren't many working bluetooth extensions. The new gnome-bluetooth3 series has an expanded build test suite and has received lots of fixes that won't be ported to the older gnome-bluetooth series. Why It Wasn't Done Before - We needed to get a MIR to allow gnome-bluetooth3 in to main while the old gnome-bluetooth is still in main. See https://launchpad.net/bugs/1964600 . Sorry this is a bit late. Still about a week before Final Freeze to revert these changes is issues are identified but we're feeling confident this will be a worthwhile improvement. Other Change If this FFE is approved, we'd like to go ahead and drop the gir package built by the old gnome-bluetooth since nothing is using it. It is believed that gnome-shell is the only user of the gnome-bluetooth gir bindings. ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Description changed: Why It's Needed --- This will fix LP: #1738838 gnome-shell 42 stable release updates for Ubuntu 22.04 will be easier since we don't have to revert all the bluetooth-related commits. Why, More Details - GNOME Shell 42 uses API from the new gnome-bluetooth library to fix LP: #1738838 The API changes were not practical to forward-port (switch to a new GListModel API). Ubuntu's gnome-shell packaging had to revert ~6 commits to keep using the older gnome-bluetooth library, which is more awkward to maintain. Because of how GNOME Shell extensions work, if an extension tries to modify the bluetooth part of the system status menu in the top right corner of the screen, the extension may not work because Ubuntu's GNOME Shell 42 is different than what every other distro provides. I assess this concern as very low since extensions are "use at your own risk" and there aren't many working bluetooth extensions. + The new gnome-bluetooth3 series has an expanded build test suite and has + received lots of fixes that won't be ported to the older gnome-bluetooth + series. + Why It Wasn't Done Before - We needed to get a MIR to allow gnome-bluetooth3 in to main while the old gnome-bluetooth is still in main. See https://launchpad.net/bugs/1964600 . - Sorry this is a bit late. + Sorry this is a bit late. Still about a week before Final Freeze to + revert these changes is issues are identified but we're feeling + confident this will be a worthwhile improvement. Other Change If this FFE is approved, we'd like to go ahead and drop the gir package built by the old gnome-bluetooth since nothing is using it. It is believed that gnome-shell is the only user of the gnome-bluetooth gir bindings. ** Package changed: gnome-bluetooth3 (Ubuntu) => gnome-bluetooth (Ubuntu) ** 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-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1968364 Title: [FFe] Switch gnome-shell to use gnome-bluetooth3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1968364/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968364] [NEW] [FFe] Switch gnome-shell to use gnome-bluetooth3
You have been subscribed to a public bug: Why It's Needed --- This will fix LP: #1738838 gnome-shell 42 stable release updates for Ubuntu 22.04 will be easier since we don't have to revert all the bluetooth-related commits. Why, More Details - GNOME Shell 42 uses API from the new gnome-bluetooth library to fix LP: #1738838 The API changes were not practical to forward-port (switch to a new GListModel API). Ubuntu's gnome-shell packaging had to revert ~6 commits to keep using the older gnome-bluetooth library, which is more awkward to maintain. Because of how GNOME Shell extensions work, if an extension tries to modify the bluetooth part of the system status menu in the top right corner of the screen, the extension may not work because Ubuntu's GNOME Shell 42 is different than what every other distro provides. I assess this concern as very low since extensions are "use at your own risk" and there aren't many working bluetooth extensions. The new gnome-bluetooth3 series has an expanded build test suite and has received lots of fixes that won't be ported to the older gnome-bluetooth series. Why It Wasn't Done Before - We needed to get a MIR to allow gnome-bluetooth3 in to main while the old gnome-bluetooth is still in main. See https://launchpad.net/bugs/1964600 . Sorry this is a bit late. Still about a week before Final Freeze to revert these changes is issues are identified but we're feeling confident this will be a worthwhile improvement. Other Change If this FFE is approved, we'd like to go ahead and drop the gir package built by the old gnome-bluetooth since nothing is using it. It is believed that gnome-shell is the only user of the gnome-bluetooth gir bindings. ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- [FFe] Switch gnome-shell to use gnome-bluetooth3 https://bugs.launchpad.net/bugs/1968364 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
This is the root issue: https://gitlab.gnome.org/GNOME/glib/-/issues/389 ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #389 https://gitlab.gnome.org/GNOME/glib/-/issues/389 -- 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/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968357] [NEW] While logginto unity session the message that'the system has crashed and cannot be recovered. the extentions have been disabled"
Public bug reported: While logging into unity session the message that'the system has crashed and cannot be recovered. the extensions have been disabled'. However, logging into ubuntu session does not show any error. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: unity-session 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 22:06:16 2022 InstallationDate: Installed on 2022-04-02 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220401) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1968357 Title: While logginto unity session the message that'the system has crashed and cannot be recovered. the extentions have been disabled" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1968357/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over program after resuming from blank screen
I can reproduce the issue described here. I'm using stock Ubuntu dock, no other gnome-shell extensions other than the ones enabled by default in Ubuntu, and I'm on jammy fully up-to-date. After I lock my screen and let the monitor blank, when I unlock it I find that one or several of my fullscreen windows (e.g. firefox snap, gedit deb) is now maximized under the dock. It looks like the fix for bug #1917939 isn't enough. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over program after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818348] Re: When window title bar controls are on left, close window button is cut off in title bar of Disks application
The bug is fixed with Ubuntu 22.04 5.15.0-25-generic x86_64 GNOME 42.0. ** Changed in: gnome-disk-utility (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1818348 Title: When window title bar controls are on left, close window button is cut off in title bar of Disks application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1818348/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832606] Re: GNOME Disks Missing 'Close' Window Button When Set To Left-Hand Side
The bug is fixed with Ubuntu 22.04 5.15.0-25-generic x86_64 GNOME 42.0. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1832606 Title: GNOME Disks Missing 'Close' Window Button When Set To Left-Hand Side To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1832606/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832606] Re: GNOME Disks Missing 'Close' Window Button When Set To Left-Hand Side
There is a manual fix for this, but it has to be done every time you open "Gnome Disks". The app is divided into 2 sections (the left one where disks are listed, and the right one where details about a disk are shown) that are divided by a... divider :) The fix is to grab (click+hold) the divider and move it to the right, which will make room for all the buttons in the top bar. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1832606 Title: GNOME Disks Missing 'Close' Window Button When Set To Left-Hand Side To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1832606/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968215] Re: [FFe] include a new webextensions portal to be used by firefox and other confined browsers
This bug was fixed in the package xdg-desktop-portal - 1.14.2-1ubuntu1 --- xdg-desktop-portal (1.14.2-1ubuntu1) jammy; urgency=medium * Import https://github.com/flatpak/xdg-desktop-portal/pull/705 as a distro-patch (add a portal for managing WebExtensions native messaging servers, LP: #1968215) - debian/patches/webextensions-portal.patch -- Olivier Tilloy Fri, 08 Apr 2022 11:16:45 +0200 ** Changed in: xdg-desktop-portal (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1968215 Title: [FFe] include a new webextensions portal to be used by firefox and other confined browsers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1968215/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967127] Re: [FFe] update libarchive to 3.6.0
This bug was fixed in the package evince - 42.1-2 --- evince (42.1-2) unstable; urgency=medium * debian/control.in: Bump minimum libarchive to 3.6.0 * Drop libarchive revert commits (LP: #1967127) -- Jeremy Bicha Wed, 30 Mar 2022 08:17:47 -0400 ** Changed in: evince (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1967127 Title: [FFe] update libarchive to 3.6.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1967127/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968332] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1965702 *** https://bugs.launchpad.net/bugs/1965702 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1965702, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968332/+attachment/5578248/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1968332/+attachment/5578250/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1968332/+attachment/5578254/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1968332/+attachment/5578255/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1968332/+attachment/5578256/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1968332/+attachment/5578257/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968332/+attachment/5578258/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1965702 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1968332 Title: gnome-control-center crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968333] [NEW] FTBFS
Public bug reported: All archs have build from 2020, except riscv64 which does not have any available: I tried to rebuild this package in my PPA [1] and it fails. I fixed all vala compilation errors that I was seeing locally (but not in the build logs above) and fixed an outdated path to dconf-service: you can find the diff attached. But then tests fail and I fail to fix this: make check-TESTS make[5]: Entering directory '/home/ubuntu/indicator-keyboard/indicator-keyboard/tests' # random seed: R02S17152843af8958ff21f0460bf77a5d11 1..9 # Start of indicator-keyboard-service tests dbus-daemon[96717]: [session uid=1000 pid=96717] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=96722 comm="gsettings set org.gnome.desktop.input-sources curr" label="unconfined") dbus-daemon[96717]: [session uid=1000 pid=96717] Successfully activated service 'ca.desrt.dconf' dbus-daemon[96717]: [session uid=1000 pid=96717] Activating service name='com.canonical.indicator.keyboard' requested by ':1.0' (uid=1000 pid=96716 comm="./indicator-keyboard-tests " label="unconfined") dbus-daemon[96717]: [session uid=1000 pid=96717] Activating service name='org.gtk.vfs.Daemon' requested by ':1.4' (uid=1000 pid=96735 comm="/home/ubuntu/indicator-keyboard/indicator-keyboard" label="unconfined") dbus-daemon[96717]: [session uid=1000 pid=96717] Successfully activated service 'org.gtk.vfs.Daemon' (indicator-keyboard-service:96735): IBUS-CRITICAL **: 12:09:45.004: ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed (indicator-keyboard-service:96735): IBUS-CRITICAL **: 12:09:45.005: ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed (indicator-keyboard-service:96735): IBUS-CRITICAL **: 12:09:45.005: ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed dbus-daemon[96717]: [session uid=1000 pid=96717] Successfully activated service 'com.canonical.indicator.keyboard' current = 2 output = "uint32 2 " A connection to the bus can't be made # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created ok 1 /indicator-keyboard-service/activate-input-source # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created dbus-daemon[96761]: [session uid=1000 pid=96761] Activating service name='com.canonical.indicator.keyboard' requested by ':1.0' (uid=1000 pid=96716 comm="./indicator-keyboard-tests " label="unconfined") dbus-daemon[96761]: [session uid=1000 pid=96761] Activating service name='org.gtk.vfs.Daemon' requested by ':1.1' (uid=1000 pid=96763 comm="/home/ubuntu/indicator-keyboard/indicator-keyboard" label="unconfined") dbus-daemon[96761]: [session uid=1000 pid=96761] Successfully activated service 'org.gtk.vfs.Daemon' (indicator-keyboard-service:96763): IBUS-CRITICAL **: 12:09:46.792: ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed (indicator-keyboard-service:96763): IBUS-CRITICAL **: 12:09:46.793: ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed (indicator-keyboard-service:96763): IBUS-CRITICAL **: 12:09:46.793: ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed dbus-daemon[96761]: [session uid=1000 pid=96761] Successfully activated service 'com.canonical.indicator.keyboard' [Invalid UTF-8] Bail out! GLib-GObject-FATAL-WARNING: g_object_notify: object class 'Service' has no property named '\xc0[u\x1d\x9fU' (./indicator-keyboard-tests:96716): GLib-GObject-WARNING **: 12:09:46.826: g_object_notify: object class 'Service' has no property named '\xc0[u\u001d\x9fU' Trace/breakpoint trap (core dumped)
[Bug 1968301] Re: evolution crashed with SIGSEGV
*** This bug is a duplicate of bug 1965798 *** https://bugs.launchpad.net/bugs/1965798 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1965798, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968301/+attachment/5578171/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1968301/+attachment/5578173/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1968301/+attachment/5578176/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1968301/+attachment/5578177/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1968301/+attachment/5578178/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1968301/+attachment/5578179/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968301/+attachment/5578180/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1965798 evolution crashed with SIGSEGV using WAYLAND ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1968301 Title: evolution crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1968301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
running fluxbox still can trigger this in 22.04 Affected scripts in my case: /etc/X11/Xsession.d/30x11-common_xresources /etc/X11/Xsession.d/90x11-common_ssh-agent -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1928261] Re: gnome-shell[1713]: libinput error: client bug: timer event0 debounce short: scheduled expiry is in the past (-22ms), your system is too slow
*** This bug is a duplicate of bug 1870597 *** https://bugs.launchpad.net/bugs/1870597 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1928261 Title: gnome-shell[1713]: libinput error: client bug: timer event0 debounce short: scheduled expiry is in the past (-22ms), your system is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1928261/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968255] Re: Sudden, unexpected restart of the whole system. Reporting after automatic restart
** Package changed: 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/1968255 Title: Sudden, unexpected restart of the whole system. Reporting after automatic restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968255] [NEW] Sudden, unexpected restart of the whole system. Reporting after automatic restart
You have been subscribed to a public bug: Using browser the system just stopped and restarted. Browser hardware acceleration option was on. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 07:25:13 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-02 (1344 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-07 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- Sudden, unexpected restart of the whole system. Reporting after automatic restart https://bugs.launchpad.net/bugs/1968255 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968268] Re: gnome-control-center crashed with SIGSEGV in google sign-in
*** This bug is a duplicate of bug 1965702 *** https://bugs.launchpad.net/bugs/1965702 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1965702, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968268/+attachment/5578103/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1968268/+attachment/5578105/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1968268/+attachment/5578108/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1968268/+attachment/5578109/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1968268/+attachment/5578110/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1968268/+attachment/5578111/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968268/+attachment/5578112/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1965702 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1968268 Title: gnome-control-center crashed with SIGSEGV in google sign-in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968268/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968213] Re: Icon theme reverts to Yaru when entering Appearance settings
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1968213 Title: Icon theme reverts to Yaru when entering Appearance settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
