date:20220517

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Tags added: resume suspend-resume

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1973827

Title:
  Laptop freezes when recovering from suspend / sleep mode

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I lock the laptop and unlock it - I have no issues.

  If I allow it to lock and then sleep, or close the lid and suspend -
  when I open it again, I get the login prompt but cannot use mouse /
  keyboard.

  The only solution I have is to press and hold the power button and
  force shutdown and then boot back up

  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  No particular package being used.

  I would expect the system to recover from suspend / sleep and allow me
  to enter password.

  The laptop froze completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 17 21:45:17 2022
  InstallationDate: Installed on 2022-04-22 (25 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973827/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1871262] Re: gnome-shell freezes/crashes with meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

It appears in meta_window_set_stack_position_no_sync that:

  g_return_if_fail (window->stack_position >= 0);

is non-fatal and has been that way for almost 10 years.

This means whatever freezes or crashes you are experiencing are
happening somewhere else. Everyone please follow the instructions in
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
and open new bugs with your findings.

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1871262

Title:
  gnome-shell freezes/crashes with
  meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  GNOME Shell-Message: 20:18:17.677: Telepathy is not available, chat 
integration will be disabled.
  Gjs-Message: 20:18:18.189: JS WARNING: 
[/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1028]: 
unreachable code after return statement
  Ubuntu AppIndicators-Message: 20:18:19.456: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.79/org/ayatana/NotificationItem/software_update_available
  Ubuntu AppIndicators-Message: 20:18:19.461: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem :1.79/org/ayatana/NotificationItem/livepatch
  GNOME Shell-Message: 20:18:19.742: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation

  (gnome-shell:21601): mutter-CRITICAL **: 20:18:45.274:
  meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

  Was the error I got after restarting Gnome after it froze when I
  closed Visual Studio Code but the right-click menu appeared for it
  after Ubuntu froze for a second because I had regions enabled on my
  touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Mon Apr  6 20:16:51 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2020-04-04 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2020-04-04 (5 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1871262/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor

Actually I should be asking that same question in bug 1871262.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1973802

Title:
  Gnome Shell crashes when disconnecting external monitor

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04, gnome-shell 42.0-2ubuntu1

  When unplugging an external monitor connected via USB-C to my Thinkpad
  P14s, the entire UI session crashes. While the external monitor is
  plugged in, it is configured as the primary display. Here are the
  gnome-shell logs of the latest incident, I suppose the relevant part
  is `assertion 'window->stack_position >= 0' failed`.

  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212959 does not exist.
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212963 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212964 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212965 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212966 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212967 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 38 with keysym 38 (keycode 11).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 39 with keysym 39 (keycode 12).
  May 17 09:56:51 snaut gnome-shell[2048]: Could not create transient scope for 
PID 213085:

[Desktop-packages] [Bug 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
70~ubuntu3.21.10.1

---
gnome-shell-extension-ubuntu-dock (70~ubuntu3.21.10.1) impish; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * locations: Do not manually dispose objects (LP: #1949352, #1951599)
  * windowPreview: Try generating previews clones on meta later only if have 
valid size
(LP: #1949572)
  * locations: Use native GIcon as location Apps-icons (LP: #1874578)
  * debian: Update branch info for impish

  [ nename0 ]
  * Cleanup nautilus listeners (LP: #1949352)

  [ Pepijn Bogaard ]
  * appIcons: Fixed logic on handling preview click actions (LP: #1947445)

 -- Marco Trevisan (Treviño)   Tue, 25 Jan 2022
01:08:43 +0100

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1947445

Title:
  Click actions "previews" and "minimize-or-previews" are broken

Status in Dash to dock:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Impish:
  Fix Released

Bug description:
  [ Impact ]

  Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or-
  previews" options no longer work as expected.

  [ Test case ]

  1. gsettings set org.gnome.shell.extensions.dash-to-dock click-action 
"previews"
   - Open multiple windows for an application
   - Click on the icon, previews should be shown

  2. gsettings set org.gnome.shell.extensions.dash-to-dock click-action 
"minimize-or-previews"
- Open multiple windows for an application
- Click on the icon, previews should be shown

  [ Regression potential ]

  Wrong action is taken if an application has urgent windows

  
  

  For "previews":
  No previews are shown when clicking on the app icon.

  For "minimize-or-previews":
  When multiple windows of the same application are open and I click on the app 
icon, no previews are shown anymore.

  Schema: org.gnome.shell.extensions.dash-to-dock
  Name: click-action
  Value: "minimize-or-previews"
  Value: "previews"

  Description:  Ubuntu 21.10
  Release:  21.10

  gnome-shell-extension-ubuntu-dock:
    Installed: 70~ubuntu3

  ProblemType: BugDistroRelease: Ubuntu 21.10
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 11:32:51 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-21 (1090 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1947445/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1874578] Update Released

The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1874578

Title:
  Dock has very long load time when show-mounts is enabled

Status in Dash to dock:
  New
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Impish:
  Fix Released

Bug description:
  [ Impact ]

  Icons are not showing on loading when mount-points are showing

  [ Test case ]

  - Start a new session (ensure that the system has mounted devices)
  - The launcher icons should show promptly without any delay

  [ Regression potential ]

  Mounted devices will have wrong or no icon.

  

  I just upgraded from Ubuntu 18.04 to 20.04.

  When I boot my system I have to wait at least 10 to 15 seconds for the
  application icons to load on dock. Meanwhile everything else seems to
  be working properly. I didn't experience this behavior in Ubuntu
  18.04.

  Also the dock doesn't trigger when I move my cursor to the left of the 
screen. (I have set the docker to Auto-Hide mode and it's position is on the 
left of my screen).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2016-08-03 (1359 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags: focal third-party-packages wayland-session
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1874578] Re: Dock has very long load time when show-mounts is enabled

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
70~ubuntu3.21.10.1

---
gnome-shell-extension-ubuntu-dock (70~ubuntu3.21.10.1) impish; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * locations: Do not manually dispose objects (LP: #1949352, #1951599)
  * windowPreview: Try generating previews clones on meta later only if have 
valid size
(LP: #1949572)
  * locations: Use native GIcon as location Apps-icons (LP: #1874578)
  * debian: Update branch info for impish

  [ nename0 ]
  * Cleanup nautilus listeners (LP: #1949352)

  [ Pepijn Bogaard ]
  * appIcons: Fixed logic on handling preview click actions (LP: #1947445)

 -- Marco Trevisan (Treviño)   Tue, 25 Jan 2022
01:08:43 +0100

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1874578

Title:
  Dock has very long load time when show-mounts is enabled

Status in Dash to dock:
  New
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Impish:
  Fix Released

Bug description:
  [ Impact ]

  Icons are not showing on loading when mount-points are showing

  [ Test case ]

  - Start a new session (ensure that the system has mounted devices)
  - The launcher icons should show promptly without any delay

  [ Regression potential ]

  Mounted devices will have wrong or no icon.

  

  I just upgraded from Ubuntu 18.04 to 20.04.

  When I boot my system I have to wait at least 10 to 15 seconds for the
  application icons to load on dock. Meanwhile everything else seems to
  be working properly. I didn't experience this behavior in Ubuntu
  18.04.

  Also the dock doesn't trigger when I move my cursor to the left of the 
screen. (I have set the docker to Auto-Hide mode and it's position is on the 
left of my screen).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2016-08-03 (1359 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags: focal third-party-packages wayland-session
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else

This bug was fixed in the package gtk+3.0 - 3.24.30-1ubuntu1.1

---
gtk+3.0 (3.24.30-1ubuntu1.1) impish; urgency=medium

  * debian/patches/git_wayland_clipboard.patch:
- wayland: Ensure clipboard handling doesn't lock up in certain
  corner cases, fix copy from firefox being unreliable (lp: #1913775)

 -- Sebastien Bacher   Wed, 12 Jan 2022 12:44:47
+0100

** Changed in: gtk+3.0 (Ubuntu Impish)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1913775

Title:
  Copy from Firefox Wayland fails to be pasted anywhere else

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Impish:
  Fix Released

Bug description:
  * Impact

  The clipboard copies from GTK based software sometime stop working
  under wayland

  * Test Case

  - in a wayland session try to copy text between software, from firefox
  to gedit for example, it should work in a consistent manner

  alternative testcase inspired from the gitlab ticket
  - install wl-clipboard
  - use evince to open a pdf
  - select and copy some content
  - on a cmdline do 
  $ wl-paste -t TEXT
  - try to paste then in another software, gedit for example

  the copied text should be pasted

  
  * Regression potential

  The changes are in the wayland selection source so the impact should
  only be for wayland users and limited to clipboard interactions

  
  --

  
  Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on 
Wayland native

  Version   84.0.2
  Build ID  20210105180113

  Window Protocol   wayland
  Desktop Environment   gnome

  DESCRIPTION OF THE PROBLEM:

  If I copy text from a web page and try to paste it into another
  Firefox page, the text is pasted correctly.

  If I copy text from a web page and try to paste it in [gedit,
  libreoffice, thunderbird, terminal, slack (electron)] nothing happens.
  The Gnome Clipboard extension stays empty when content is copied from
  Firefox Wayland.

  Pasting *from* another app *to* Firefox works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1913775/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1947445] Update Released

The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1947445

Title:
  Click actions "previews" and "minimize-or-previews" are broken

Status in Dash to dock:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Impish:
  Fix Released

Bug description:
  [ Impact ]

  Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or-
  previews" options no longer work as expected.

  [ Test case ]

  1. gsettings set org.gnome.shell.extensions.dash-to-dock click-action 
"previews"
   - Open multiple windows for an application
   - Click on the icon, previews should be shown

  2. gsettings set org.gnome.shell.extensions.dash-to-dock click-action 
"minimize-or-previews"
- Open multiple windows for an application
- Click on the icon, previews should be shown

  [ Regression potential ]

  Wrong action is taken if an application has urgent windows

  
  

  For "previews":
  No previews are shown when clicking on the app icon.

  For "minimize-or-previews":
  When multiple windows of the same application are open and I click on the app 
icon, no previews are shown anymore.

  Schema: org.gnome.shell.extensions.dash-to-dock
  Name: click-action
  Value: "minimize-or-previews"
  Value: "previews"

  Description:  Ubuntu 21.10
  Release:  21.10

  gnome-shell-extension-ubuntu-dock:
    Installed: 70~ubuntu3

  ProblemType: BugDistroRelease: Ubuntu 21.10
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 11:32:51 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-21 (1090 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1947445/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1949352] Re: Removable drives are not auto-mounted after screen lock/unlock

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
70~ubuntu3.21.10.1

---
gnome-shell-extension-ubuntu-dock (70~ubuntu3.21.10.1) impish; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * locations: Do not manually dispose objects (LP: #1949352, #1951599)
  * windowPreview: Try generating previews clones on meta later only if have 
valid size
(LP: #1949572)
  * locations: Use native GIcon as location Apps-icons (LP: #1874578)
  * debian: Update branch info for impish

  [ nename0 ]
  * Cleanup nautilus listeners (LP: #1949352)

  [ Pepijn Bogaard ]
  * appIcons: Fixed logic on handling preview click actions (LP: #1947445)

 -- Marco Trevisan (Treviño)   Tue, 25 Jan 2022
01:08:43 +0100

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1949352

Title:
  Removable drives are not auto-mounted after screen lock/unlock

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Won't Fix
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Impish:
  Fix Released

Bug description:
  [ Impact ]

  If I lock and then unlock the screen, and then connect a removable
  drive, it is not recognized by the GNOME shell. The kernel logs show
  the drive, I can mount it manually, but it is not mounted
  automatically. The logged errors are attached.

  [ Test case ]

  - Mount a device
  - Lock the screen
  - Unlock the screen
  - The device should be re-mounted (and no errors in journal)

  [ Regression Potential ]

  Devices could be leaked if gc doesn't work as expected

  ---

  I could fix the issue by modifying the source code as given in the attached 
patch.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-01 (1 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1949352/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1949352] Update Released

The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1949352

Title:
  Removable drives are not auto-mounted after screen lock/unlock

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Won't Fix
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Impish:
  Fix Released

Bug description:
  [ Impact ]

  If I lock and then unlock the screen, and then connect a removable
  drive, it is not recognized by the GNOME shell. The kernel logs show
  the drive, I can mount it manually, but it is not mounted
  automatically. The logged errors are attached.

  [ Test case ]

  - Mount a device
  - Lock the screen
  - Unlock the screen
  - The device should be re-mounted (and no errors in journal)

  [ Regression Potential ]

  Devices could be leaked if gc doesn't work as expected

  ---

  I could fix the issue by modifying the source code as given in the attached 
patch.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-01 (1 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1949352/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1949572] Re: Shell freeze after right click on the app in the dock

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
70~ubuntu3.21.10.1

---
gnome-shell-extension-ubuntu-dock (70~ubuntu3.21.10.1) impish; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * locations: Do not manually dispose objects (LP: #1949352, #1951599)
  * windowPreview: Try generating previews clones on meta later only if have 
valid size
(LP: #1949572)
  * locations: Use native GIcon as location Apps-icons (LP: #1874578)
  * debian: Update branch info for impish

  [ nename0 ]
  * Cleanup nautilus listeners (LP: #1949352)

  [ Pepijn Bogaard ]
  * appIcons: Fixed logic on handling preview click actions (LP: #1947445)

 -- Marco Trevisan (Treviño)   Tue, 25 Jan 2022
01:08:43 +0100

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1949572

Title:
  Shell freeze after right click on the app in the dock

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Invalid
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Won't Fix
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Impish:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Impish:
  Fix Released

Bug description:
  [ Impact ]

  When you click the icon of the app in the dock to open it for the
  first time and then immediately right click to see options, everything
  freezes and you are forced to reboot.

  [ Test case ]

  - Under wayland, open an application and immediately right-click its icon
  - The shell should show the application window that has just been opened in
the windows submenu, and continue working

  [ Regression potential]

  No windows previews are showing in the application menu

  ---

  I'm using Ubuntu 21.10. I installed it today.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-03 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1949572/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1951599] Update Released

The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1951599

Title:
  gnome-shell logs errors when ejecting SD card

Status in OEM Priority Project:
  Triaged
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Impish:
  Fix Released

Bug description:
  [ Impact ]

  When I click eject SD card in Files(nautilus), I found the gnome-shell
  reported some crash logs.

  [ Test case ]

  - Mount a device
  - Eject the device
  - No errors should be shown and the device re-mountable

  [ Regression Potential ]

  Devices could be leaked if gc doesn't work as expected

  
  ---

  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object 
.Gjs_components_autorunManager_AutorunSource (0x55a9d8e846e0), has been already 
deallocated â€” impossible to emit any signal on it. This might be caused by 
the object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object 
Gio.Settings (0x55a9db521970), has been already deallocated â€” impossible to 
access it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack 
trace for context 0x55a9d8a00120 ==
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0   
7ffc0b63cc20 b   resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 
@ 149)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1   
55a9d8f150b0 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 
69)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2   
55a9d8f15018 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 
25)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3   
7ffc0b63d8c0 b   self-hosted:850 (1ec3f0b2a650 @ 454)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1951599/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1949572] Update Released

The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1949572

Title:
  Shell freeze after right click on the app in the dock

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Invalid
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Won't Fix
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Impish:
  Invalid
Status in gnome-shell-extension-ubuntu-dock source package in Impish:
  Fix Released

Bug description:
  [ Impact ]

  When you click the icon of the app in the dock to open it for the
  first time and then immediately right click to see options, everything
  freezes and you are forced to reboot.

  [ Test case ]

  - Under wayland, open an application and immediately right-click its icon
  - The shell should show the application window that has just been opened in
the windows submenu, and continue working

  [ Regression potential]

  No windows previews are showing in the application menu

  ---

  I'm using Ubuntu 21.10. I installed it today.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-03 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1949572/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1951599] Re: gnome-shell logs errors when ejecting SD card

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
70~ubuntu3.21.10.1

---
gnome-shell-extension-ubuntu-dock (70~ubuntu3.21.10.1) impish; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * locations: Do not manually dispose objects (LP: #1949352, #1951599)
  * windowPreview: Try generating previews clones on meta later only if have 
valid size
(LP: #1949572)
  * locations: Use native GIcon as location Apps-icons (LP: #1874578)
  * debian: Update branch info for impish

  [ nename0 ]
  * Cleanup nautilus listeners (LP: #1949352)

  [ Pepijn Bogaard ]
  * appIcons: Fixed logic on handling preview click actions (LP: #1947445)

 -- Marco Trevisan (Treviño)   Tue, 25 Jan 2022
01:08:43 +0100

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1951599

Title:
  gnome-shell logs errors when ejecting SD card

Status in OEM Priority Project:
  Triaged
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Impish:
  Fix Released

Bug description:
  [ Impact ]

  When I click eject SD card in Files(nautilus), I found the gnome-shell
  reported some crash logs.

  [ Test case ]

  - Mount a device
  - Eject the device
  - No errors should be shown and the device re-mountable

  [ Regression Potential ]

  Devices could be leaked if gc doesn't work as expected

  
  ---

  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object 
.Gjs_components_autorunManager_AutorunSource (0x55a9d8e846e0), has been already 
deallocated â€” impossible to emit any signal on it. This might be caused by 
the object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object 
Gio.Settings (0x55a9db521970), has been already deallocated â€” impossible to 
access it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack 
trace for context 0x55a9d8a00120 ==
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0   
7ffc0b63cc20 b   resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 
@ 149)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1   
55a9d8f150b0 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 
69)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2   
55a9d8f15018 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 
25)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3   
7ffc0b63d8c0 b   self-hosted:850 (1ec3f0b2a650 @ 454)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1951599/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1973827] Re: Laptop freezes when recovering from suspend / sleep mode

2022-05-17 Thread Chris Guiver

Thanks for taking the time to report this bug and helping to make Ubuntu
better.

Your log indicates you installed Ubuntu 22.04 LTS, are still using it
and haven't upgraded to a later release such as Ubuntu kinetic using
Ubuntu-release-upgrader.  I've thus changed package to gnome-shell.
(apologies if still an incorrect package)

** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell
(Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1973827

Title:
  Laptop freezes when recovering from suspend / sleep mode

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I lock the laptop and unlock it - I have no issues.

  If I allow it to lock and then sleep, or close the lid and suspend -
  when I open it again, I get the login prompt but cannot use mouse /
  keyboard.

  The only solution I have is to press and hold the power button and
  force shutdown and then boot back up

  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  No particular package being used.

  I would expect the system to recover from suspend / sleep and allow me
  to enter password.

  The laptop froze completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 17 21:45:17 2022
  InstallationDate: Installed on 2022-04-22 (25 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973827/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]

2022-05-17 Thread ManOnTheMoon

Having the same error message"error reading events from display:
Protocol error" when running wayland. However, extension manager having
no issue opening in x11. Ubuntu 22.04 with Nividia driver 510

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1965563

Title:
  gnome-extensions-app fails to start [Error reading events from
  display: Protocol error]

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1973827] [NEW] Laptop freezes when recovering from suspend / sleep mode

You have been subscribed to a public bug:

When I lock the laptop and unlock it - I have no issues.

If I allow it to lock and then sleep, or close the lid and suspend -
when I open it again, I get the login prompt but cannot use mouse /
keyboard.

The only solution I have is to press and hold the power button and force
shutdown and then boot back up

Description:Ubuntu 22.04 LTS
Release:22.04

No particular package being used.

I would expect the system to recover from suspend / sleep and allow me
to enter password.

The laptop froze completely.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.10
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Tue May 17 21:45:17 2022
InstallationDate: Installed on 2022-04-22 (25 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade jammy wayland-session
-- 
Laptop freezes when recovering from suspend / sleep mode
https://bugs.launchpad.net/bugs/1973827
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor

Thanks for the bug report. This looks like bug 1871262 but actually I'm
not convinced that bug report is accurate. If the assertion failure is
non-fatal then cause of the crash might actually be something different
slightly after that...

Please try following:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** Tags added: jammy

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** Tags added: multimonitor

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1973802

Title:
  Gnome Shell crashes when disconnecting external monitor

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04, gnome-shell 42.0-2ubuntu1

  When unplugging an external monitor connected via USB-C to my Thinkpad
  P14s, the entire UI session crashes. While the external monitor is
  plugged in, it is configured as the primary display. Here are the
  gnome-shell logs of the latest incident, I suppose the relevant part
  is `assertion 'window->stack_position >= 0' failed`.

  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212959 does not exist.
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212963 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212964 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212965 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212966 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212967 does not exist.
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
  May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).

[Desktop-packages] [Bug 1973660] Re: [vmwgfx] Login screen not refreshing properly on vSphere

Thanks. This looks like a bug in the VMware Xorg graphics driver.

Strangely it does not appear your login screen is using Wayland when it
should be default. So even the login screen will be victim to any bugs
in the VMware Xorg graphics driver. Maybe check that you haven't
accidentally set WaylandEnable=false in /etc/gdm3/custom.conf

Other than the above I can only suggest:

 (a) try changing the display controller type in the hypervisor; or

 (b) Ubuntu 22.04 which is the latest long term support release.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1973660

Title:
  [vmwgfx] Login screen not refreshing properly on vSphere

Status in xserver-xorg-video-vmware package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using,
  gnome-shell:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal-updates/main amd64 
Packages
  500 http://cn.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal/main amd64 Packages
  500 http://cn.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) What you expected to happen
  The login screen can resize properly and all its widgets shows properly. 

  4) What happened instead
  Login screen doesn't refresh properly when resize vShpere window, so that 
can't input username and password. And I found pressing Ctl-Alt-Tab can force 
the login screen refresh.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.screensaver' b'lock-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2020-08-13 (641 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 [modified: 
usr/lib/gnome-shell/libgnome-shell.so]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1973660/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1973660] Re: [vmwgfx] Login screen not refreshing properly on vSphere

** Summary changed:

- Login screen not refreshing properly on vSphere
+ [vmwgfx] Login screen not refreshing properly on vSphere

** Tags added: vmwgfx

** Package changed: gnome-shell (Ubuntu) => xserver-xorg-video-vmware
(Ubuntu)

** Changed in: xserver-xorg-video-vmware (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1973660

Title:
  [vmwgfx] Login screen not refreshing properly on vSphere

Status in xserver-xorg-video-vmware package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using,
  gnome-shell:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal-updates/main amd64 
Packages
  500 http://cn.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal/main amd64 Packages
  500 http://cn.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) What you expected to happen
  The login screen can resize properly and all its widgets shows properly. 

  4) What happened instead
  Login screen doesn't refresh properly when resize vShpere window, so that 
can't input username and password. And I found pressing Ctl-Alt-Tab can force 
the login screen refresh.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.screensaver' b'lock-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2020-08-13 (641 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 [modified: 
usr/lib/gnome-shell/libgnome-shell.so]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1973660/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1973397] Re: Ubuntu 22.04: Display manager resets when trying to change it using gear icon in login window

> [   18.338220] n-dominus gnome-shell[1115]: Running GNOME Shell (using mutter 
> 42.0) as a Wayland display server
> [   18.441210] n-dominus org.gnome.Shell.desktop[1115]: Failed to setup: No 
> GPUs found

This suggests your kernel is missing or has disabled the graphics
driver. Please ensure you are not using the 'nomodeset' kernel
parameter.

> 2022-05-01 09:05 2022-05-01 07:05 UTC Crash /usr/libexec/gnome-
session-binary

This may also be related to the problem you describe so please look at
https://errors.ubuntu.com/user/ID where ID is the content of file
/var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to
recent problems on that page? If so then please send the links to us.

Please also run:

  lspci -k > lspci.txt
  journalctl -b0 > journal.txt

and attach the resulting text files here.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1973397

Title:
  Ubuntu 22.04: Display manager resets when trying to change it using
  gear icon in login window

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I would like to select wayland display manager on login screen. But
  when I click on the gear icon in login screen, screen resets to
  terminal view for a few seconds and black login screen is displayed.
  There is no more gear icon, I enter login info and can log into the
  session. But the activated display manager is X.org.

  Must I wait for some fixes, in order to be able to list different
  display managers in login window (the rest on gear icon is normal), or
  can I configure the system somehow in order to enable change of
  display managers?

  less /etc/gdm3/custom.conf
  ...
  [daemon]
  # Uncomment the line below to force the login screen to use Xorg
  #WaylandEnable=false
  WaylandEnable=true
  ...

  echo $XDG_SESSION_TYPE
  x11

  syslog file attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2020-12-15 (517 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: gnome-shell 42.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (24 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973397/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1970658] Re: Update zenity to 3.42.1

This bug was fixed in the package zenity - 3.42.1-0ubuntu1

---
zenity (3.42.1-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1970658)

 -- Jeremy Bicha   Sun, 01 May 2022 14:39:37 -0400

** Changed in: zenity (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zenity in Ubuntu.
https://bugs.launchpad.net/bugs/1970658

Title:
  Update zenity to 3.42.1

Status in zenity package in Ubuntu:
  Fix Released
Status in zenity source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  New stable release in the 3.42 series.

  https://gitlab.gnome.org/GNOME/zenity/-/blob/3.42.1/NEWS

  Test Case
  -
  zenity --info --text="1234566789 223456789 323456789 423456789 523456789 
623456789 723456789 823456789 923456789"

  Should wrap the dialog onto 2 lines, instead of one line for each set
  of numbers.

  What Could Go Wrong
  ---
  This is part of core GNOME so it falls under the microrelease exception.
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1970658/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1970658] Update Released

The verification of the Stable Release Update for zenity has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zenity in Ubuntu.
https://bugs.launchpad.net/bugs/1970658

Title:
  Update zenity to 3.42.1

Status in zenity package in Ubuntu:
  Fix Released
Status in zenity source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  New stable release in the 3.42 series.

  https://gitlab.gnome.org/GNOME/zenity/-/blob/3.42.1/NEWS

  Test Case
  -
  zenity --info --text="1234566789 223456789 323456789 423456789 523456789 
623456789 723456789 823456789 923456789"

  Should wrap the dialog onto 2 lines, instead of one line for each set
  of numbers.

  What Could Go Wrong
  ---
  This is part of core GNOME so it falls under the microrelease exception.
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1970658/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

Just add MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment and then
reboot.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1968040/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions

No there have been no updates to gnome-shell or mutter yet in 22.04.

Still, if you experience this bug then please just select a Xorg session
on the login screen.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1970291

Title:
  [nvidia] Secondary monitor performance is slow on an Nvidia hybrid
  system in Wayland sessions

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  In session with Wayland the Nvidia driver settings do not load. And
  there is a sluggishness when opening apps, show applications menu,
  maximize, changing workspace, resize, changing monitor windows etc.
  When in an Xorg session the Nvidia settings load correctly and the
  performance is satisfactory.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 21:18:08 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] 
[8086:2086]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] 
[8086:2086]
  InstallationDate: Installed on 2022-04-24 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: Avell High Performance A60 MUV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QCCFL357.0122.2020.0911.1520
  dmi.board.name: Avell High Performance
  dmi.board.vendor: Avell High Performance
  dmi.chassis.type: 10
  dmi.chassis.vendor: Avell High Performance
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV:
  dmi.product.family: A60 MUV
  dmi.product.name: A60 MUV
  dmi.product.sku: A60 MUV
  dmi.sys.vendor: Avell High Performance
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1970291/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot

I'm not sure we even need switch-on-connect anymore. It was introduced
as a patch in 2017 (bug 1702794) at the request of Will Cooke but I
suspect later upstream changes within the module logic like module-
switch-on-port-available might suffice now.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1877194

Title:
  switch-on-connect mistakes startup for USB hotplug, so seemingly
  ignores the old default device on reboot

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  New
Status in pulseaudio source package in Kinetic:
  Triaged
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  In short:
  1. Boot system
  2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
  3. Reboot.
  4 Output device is now back to "Analogue Output - RODE NT-USB".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1877194/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1855595] Re: CUPS fails to print to autodetected printers because of cups-browsed error

2022-05-17 Thread Lawrence

Same issue on Linux Mint 20.3.

sudo systemctl stop cups-browsed
sudo systemctl disable cups-browsed

that got rid of the defective autocreated printers. When I went into
Printers and did Add, I had much more specific options: LPD, IPP, and
driverless IPP. I chose IPP network printer via DNS-SD and everything
works great now :-)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1855595

Title:
  CUPS fails to print to autodetected printers because of cups-browsed
  error

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  When trying to autodetected IPP printers, print job stays in queue.

  lpstat -l:

  HP_LaserJet_CM1415fn_44A808_-23 erik 30720   So 08 Dez 2019 
15:50:20 CET
  Status: No suitable destination host found by cups-browsed.
  Alarme: resources-are-not-ready
  in Warteschlange eingereiht für HP_LaserJet_CM1415fn_44A808_

  Removing the print job, restarting cups-browsed with `service cups-
  browsed restart` followed by `service cups restart` enables printing
  for one print job; the next one fails again with the same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.25.13-1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sun Dec  8 16:06:02 2019
  InstallationDate: Installed on 2019-10-19 (50 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191019)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd: Permission denied
   grep: /etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd: Permission 
denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_utwd0l@/vmlinuz-5.3.0-24-generic 
root=ZFS=rpool/ROOT/ubuntu_utwd0l ro quiet splash vt.handoff=1
  SourcePackage: cups-filters
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1855595/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1973660] Re: Login screen not refreshing properly on vSphere

2022-05-17 Thread Hank Keanu

This issue seems not related to the resource of cpu and memory. The
following is my VM current hardware configuration:

~# lscpu
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
Address sizes:   43 bits physical, 57 bits virtual
CPU(s):  8
On-line CPU(s) list: 0-7
Thread(s) per core:  1
Core(s) per socket:  1
Socket(s):   8
NUMA node(s):1
Vendor ID:   GenuineIntel
CPU family:  6
Model:   106
Model name:  Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz
Stepping:6
CPU MHz: 1995.312
BogoMIPS:3990.62
Hypervisor vendor:   VMware
Virtualization type: full
L1d cache:   384 KiB
L1i cache:   256 KiB
L2 cache:10 MiB
L3 cache:336 MiB
NUMA node0 CPU(s):   0-7
Vulnerability Itlb multihit: KVM: Mitigation: VMX unsupported
Vulnerability L1tf:  Not affected
Vulnerability Mds:   Not affected
Vulnerability Meltdown:  Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled 
via prctl and seccomp
Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort:   Not affected
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon nopl xtopology tsc_reliable nonstop_tsc 
cpuid tsc_known_
 freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 
sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
hypervisor lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single ssbd ibrs ibpb 
stibp ibrs_enha
 nced fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
invpcid avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw 
avx512vl xsaveopt xsavec xsaves arat pku ospke md_clear flush_l1d 
arch_capabilities

~# free -mh
  totalusedfree  shared  buff/cache   available
Mem:   47Gi   1.5Gi39Gi23Mi   5.6Gi44Gi
Swap: 1.8Gi  0B   1.8Gi

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1973660

Title:
  Login screen not refreshing properly on vSphere

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using,
  gnome-shell:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal-updates/main amd64 
Packages
  500 http://cn.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt focal/main amd64 Packages
  500 http://cn.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) What you expected to happen
  The login screen can resize properly and all its widgets shows properly. 

  4) What happened instead
  Login screen doesn't refresh properly when resize vShpere window, so that 
can't input username and password. And I found pressing Ctl-Alt-Tab can force 
the login screen refresh.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.screensaver' b'lock-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2020-08-13 (641 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 [modified: 
usr/lib/gnome-shell/libgnome-shell.so]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu

[Desktop-packages] [Bug 1969934] Update Released

2022-05-17 Thread Brian Murray

The verification of the Stable Release Update for evolution-data-server
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1969934

Title:
  Update evolution-data-server to 3.44.1

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series (corresponding with GNOME 42).

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.1/NEWS

  It is required to update evolution to 3.44.1 (LP: #1969935)

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1969934/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1969934] Re: Update evolution-data-server to 3.44.1

This bug was fixed in the package evolution-data-server -
3.44.1-0ubuntu2

---
evolution-data-server (3.44.1-0ubuntu2) jammy; urgency=medium

  * Don't build with libgweather4

evolution-data-server (3.44.1-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1969934)

evolution-data-server (3.44.0-3) unstable; urgency=medium

  * Build with libgweather4

 -- Jeremy Bicha   Mon, 09 May 2022 19:16:50 -0400

** Changed in: evolution-data-server (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1969934

Title:
  Update evolution-data-server to 3.44.1

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series (corresponding with GNOME 42).

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.1/NEWS

  It is required to update evolution to 3.44.1 (LP: #1969935)

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1969934/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1971475] Re: Ubuntu 22.04 snap firefox doesn't save downloads to /mnt subfolders

2022-05-17 Thread pnck

The status is incomplete. Should i add some more information? The
mozilla bug is https://bugzilla.mozilla.org/show_bug.cgi?id=1767868

** Bug watch added: Mozilla Bugzilla #1767868
   https://bugzilla.mozilla.org/show_bug.cgi?id=1767868

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1971475

Title:
  Ubuntu 22.04 snap firefox doesn't save downloads to /mnt subfolders

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When I try to download file or save page to hard disks mounted to /mnt
  download process doesn't start. However download to /media works as
  expected. Moreover another snap GIMP saves files to /mnt. Snap
  connection to removable-media is done.

  pnck@ubuntupc:~$ lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  pnck@ubuntupc:~$ apt-cache policy firefox
  firefox:
Installed: (none)
Candidate: 1:1snap1-0ubuntu2
Version table:
   1:1snap1-0ubuntu2 500
  500 http://ru.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  
  pnck@ubuntupc:~$ snap info firefox
  name:  firefox
  summary:   Mozilla Firefox web browser
  publisher: Mozilla✓
  store-url: https://snapcraft.io/firefox
  license:   unset
  description: |
Firefox is a powerful, extensible web browser with support for modern web 
application
technologies.
  commands:
- firefox
  snap-id:  3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  tracking: latest/stable/ubuntu-22.04
  refresh-date: 2 days ago, at 19:34 MSK
  channels:
latest/stable:99.0.1-12022-04-13 (1232) 163MB -
latest/candidate: 100.0-2 2022-05-02 (1300) 168MB -
latest/beta:  101.0b1-1   2022-05-03 (1306) 169MB -
latest/edge:  102.0a1 2022-05-03 (1307) 180MB -
esr/stable:   91.8.0esr-1 2022-04-05 (1184) 161MB -
esr/candidate:91.9.0esr-1 2022-04-27 (1284) 161MB -
esr/beta: ↑   
esr/edge: ↑   
  installed:  99.0.1-1   (1232) 163MB -

  
  pnck@ubuntupc:~$ snap connections firefox
  Interface PlugSlot
 Notes
  audio-playbackfirefox:audio-playback  :audio-playback 
 -
  audio-record  firefox:audio-record:audio-record   
 -
  avahi-observe firefox:avahi-observe   :avahi-observe  
 -
  browser-support   firefox:browser-sandbox :browser-support
 -
  camerafirefox:camera  :camera 
 -
  content[gnome-3-38-2004]  firefox:gnome-3-38-2004 
gnome-3-38-2004:gnome-3-38-2004  -
  content[gtk-3-themes] firefox:gtk-3-themes
gtk-common-themes:gtk-3-themes   -
  content[icon-themes]  firefox:icon-themes 
gtk-common-themes:icon-themes-
  content[sound-themes] firefox:sound-themes
gtk-common-themes:sound-themes   -
  cups-control  firefox:cups-control:cups-control   
 -
  dbus  -   firefox:dbus-daemon 
 -
  desktop   firefox:desktop :desktop
 -
  desktop-legacyfirefox:desktop-legacy  :desktop-legacy 
 -
  gsettings firefox:gsettings   :gsettings  
 -
  hardware-observe  firefox:hardware-observe:hardware-observe   
 -
  home  firefox:home:home   
 -
  joystick  firefox:joystick:joystick   
 -
  mpris -   firefox:mpris   
 -
  network   firefox:network :network
 -
  network-observe   firefox:network-observe -   
 -
  openglfirefox:opengl  :opengl 
 -
  personal-filesfirefox:dot-mozilla-firefox :personal-files 
 -
  removable-media   firefox:removable-media :removable-media
 -
  screen-inhibit-controlfirefox:screen-inhibit-control  
:screen-inhibit-control  -
  system-files  firefox:etc-firefox-policies:system-files   
 -
  system-packages-doc   firefox:system-packages-doc 
:system-packages-doc -
  u2f-devices   firefox:u2f-devices :u2f-devices
 -
  unity7firefox:unity7  :unity7 
 -

[Desktop-packages] [Bug 1971538] Re: My machine as Wi-Fi Hotspot broken after upgrade to 22.04

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1971538

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 22.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  Upon updating to 22.04, none of my machines can use the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions

2022-05-17 Thread Zingam

Hi, Daniel, I got a big update yesterday. I feel subjectively that the
situation improved significantly (Wayland). Was there a fix for the
issue?

Though I still feel that macOS on Iris Graphics HD4000 is still smoother
on 1440p than what I get on my hybrid HD630/1050Ti.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1970291

Title:
  [nvidia] Secondary monitor performance is slow on an Nvidia hybrid
  system in Wayland sessions

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  In session with Wayland the Nvidia driver settings do not load. And
  there is a sluggishness when opening apps, show applications menu,
  maximize, changing workspace, resize, changing monitor windows etc.
  When in an Xorg session the Nvidia settings load correctly and the
  performance is satisfactory.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 21:18:08 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] 
[8086:2086]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] 
[8086:2086]
  InstallationDate: Installed on 2022-04-24 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: Avell High Performance A60 MUV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QCCFL357.0122.2020.0911.1520
  dmi.board.name: Avell High Performance
  dmi.board.vendor: Avell High Performance
  dmi.chassis.type: 10
  dmi.chassis.vendor: Avell High Performance
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV:
  dmi.product.family: A60 MUV
  dmi.product.name: A60 MUV
  dmi.product.sku: A60 MUV
  dmi.sys.vendor: Avell High Performance
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1970291/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1973816] [NEW] Deja Dup's Google support will break in September 2022 for versions < 43.3

2022-05-17 Thread Michael Terry

Public bug reported:

Hello! I'm the maintainer of Deja Dup. I was recently made aware that
Google is removing an oauth workflow that Deja Dup uses, in September.

Here's their blog post about it:
https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html

Here's the upstream bug about switching to a new oauth flow:
https://gitlab.gnome.org/World/deja-dup/-/issues/222

I've released version 43.3 with a new oauth workflow. This basically
switches us from redirecting the oauth page to a local
http://localhost:/ page being served by deja-dup and instead has the
browser launch a custom URI like
'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches
deja-dup and gives it the correct oauth token.

The key differences for packagers is just to note that now deja-dup will
register itself as a handler for those weird URI schemes (they are
specific to deja-dup, as they include its client ids for the service).

I think this deserves a backport to all supported releases. I can whip
up a patch for you in a bit, just wanted to get this registered as an
issue.

To be a bit more specific about what will break:
- Existing users that have already granted deja-dup access to Google will 
continue to work without any issue.
- In August, users will see a warning on the oauth screen.
- And then in September, any new attempt to connect deja-dup to Google will not 
work.

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1973816

Title:
  Deja Dup's Google support will break in September 2022 for versions <
  43.3

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Hello! I'm the maintainer of Deja Dup. I was recently made aware that
  Google is removing an oauth workflow that Deja Dup uses, in September.

  Here's their blog post about it:
  https://developers.googleblog.com/2022/02/making-oauth-flows-
  safer.html

  Here's the upstream bug about switching to a new oauth flow:
  https://gitlab.gnome.org/World/deja-dup/-/issues/222

  I've released version 43.3 with a new oauth workflow. This basically
  switches us from redirecting the oauth page to a local
  http://localhost:/ page being served by deja-dup and instead has
  the browser launch a custom URI like
  'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches
  deja-dup and gives it the correct oauth token.

  The key differences for packagers is just to note that now deja-dup
  will register itself as a handler for those weird URI schemes (they
  are specific to deja-dup, as they include its client ids for the
  service).

  I think this deserves a backport to all supported releases. I can whip
  up a patch for you in a bit, just wanted to get this registered as an
  issue.

  To be a bit more specific about what will break:
  - Existing users that have already granted deja-dup access to Google will 
continue to work without any issue.
  - In August, users will see a warning on the oauth screen.
  - And then in September, any new attempt to connect deja-dup to Google will 
not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1973816/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot

2022-05-17 Thread Steve Langasek

This behavior particularly affects Raspberry Pis, where USB is the only
bus available for a lot of devices and treating this as "hotplug" gives
wrong results.

That doesn't mean the default should change for pulseaudio on the
desktop in general, but should somehow be treated in a hardware-specific
manner.

I would suggest making /etc/pulse/default.pa key its loading of module-
switch-on-connect on the absence of a flag file, which could then be
provided by raspberry pi images.

I'm going to open a task on ubuntu-settings for the moment, since it
provides ubuntu-raspi-settings that seems the most likely existing
package to attach the raspi side of this to.

** Also affects: ubuntu-settings (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-settings (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

** Also affects: pulseaudio (Ubuntu Kinetic)
   Importance: Low
   Status: Triaged

** Also affects: ubuntu-settings (Ubuntu Kinetic)
   Importance: Undecided
 Assignee: Dave Jones (waveform)
   Status: New

** Tags added: rls-jj-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1877194

Title:
  switch-on-connect mistakes startup for USB hotplug, so seemingly
  ignores the old default device on reboot

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  New
Status in pulseaudio source package in Kinetic:
  Triaged
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  In short:
  1. Boot system
  2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
  3. Reboot.
  4 Output device is now back to "Analogue Output - RODE NT-USB".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1877194/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1973618] Re: can no longer open new windows after some time

2022-05-17 Thread Bug Watch Updater

Launchpad has imported 2 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1769594.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2022-05-16T16:53:00+00:00 Krister Swenson wrote:

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:100.0) Gecko/20100101
Firefox/100.0

Steps to reproduce:

After some time using firefox, I can no longer open a new window.

=> ps -ef | grep -c firefox
21

=> /snap/bin/firefox

=> ps -ef | grep -c firefox
21


Actual results:

=> ps -ef | grep -c firefox
21

There is no new process created and the window never appears.
I can open new tabs, but when I drag the tab to make it a new window, it is 
never created.

The only remedy is to restart firefox. Sometimes I need to SIGTERM all
of the zombi processes.


Expected results:

The window should have opened.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973618/comments/3


On 2022-05-16T17:17:55+00:00 Release-mgmt-account-bot wrote:

The [Bugbug](https://github.com/mozilla/bugbug/) bot thinks this bug
should belong to the 'Core::Widget: Gtk' component, and is moving the
bug to that component. Please correct in case you think the bot is
wrong.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973618/comments/5


** Changed in: firefox
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1973618

Title:
  can no longer open new windows after some time

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  After some time using firefox, I can no longer open a new window.

  => ps -ef | grep -c firefox
  21

  => /snap/bin/firefox

  => ps -ef | grep -c firefox
  21

  There is no new process created and the window never appears.
  I can open new tabs, but when I drag the tab to make it a new window, it is 
never created.

  The only remedy is to restart firefox. Sometimes I need to SIGTERM all
  of the zombi processes.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 19:45:08 2022
  InstallationDate: Installed on 2021-10-12 (215 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1973618/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1970662] Re: Update gnome-remote-desktop to 42.1.1

** Description changed:

  NOTE
  
- This adds a dependency on mutter 42.1 so mutter 42.1 needs to reach 
jammy-updates (and I assume fully phased) before we let this update in to 
jammy-updates.
+ This adds a dependency on mutter 42.1 so mutter 42.1 needs to reach 
jammy-updates (and I assume fully phased) before we let this update in to 
jammy-updates. The dependency was added to not regress support for Nvidia users.
  
  Impact
  --
- TODO
+ This is a new stable release in the GNOME 42 series
  
- Test Case
- 
- TODO
+ https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/42.1.1/NEWS
+ 
+ 
+ Test Case #1
+ 
+ Install all updates. Log out and log back in.
+ Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote 
Desktop Sharing.
+ Turn it off then on because there may be a gnome-control-center bug with 
initial enabling.
+ 
+ From a second computer, connect to the first computer using Remmina.
+ 
+ The Remote Desktop page on the first computer provides the username and
+ password to use. I wasn't able to get the "Remote Desktop Address" to
+ work (maybe avahi doesn't work well?) so just use the first computer's
+ IP address.
+ 
+ So something like:
+ RDP jeremy@192.168.1.1
+ 
+ Ensure that the connection works.
+ 
+ Test Case #2
+ 
+ Do test case #1 but this time also enable the Legacy VNC option on the Remote 
Desktop Sharing page.
+ Connect using VNC instead and ensure that the connection works.
  
  What Could Go Wrong
  ---
- TODO
+ RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. 
(Previously only VNC Sharing was offered.)
+ 
+ RDP Sharing can be used for providing remote support so it's important
+ that this feature works well because it may be difficult for the remote
+ admin to fix issues in person.
+ 
+ gnome-remote-desktop is part of GNOME Core and falls under the GNOME
+ Stable Release Update microrelease exception
+ 
+ https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1970662

Title:
  Update gnome-remote-desktop to 42.1.1

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Jammy:
  In Progress

Bug description:
  NOTE
  
  This adds a dependency on mutter 42.1 so mutter 42.1 needs to reach 
jammy-updates (and I assume fully phased) before we let this update in to 
jammy-updates. The dependency was added to not regress support for Nvidia users.

  Impact
  --
  This is a new stable release in the GNOME 42 series

  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/42.1.1/NEWS

  
  Test Case #1
  
  Install all updates. Log out and log back in.
  Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote 
Desktop Sharing.
  Turn it off then on because there may be a gnome-control-center bug with 
initial enabling.

  From a second computer, connect to the first computer using Remmina.

  The Remote Desktop page on the first computer provides the username
  and password to use. I wasn't able to get the "Remote Desktop Address"
  to work (maybe avahi doesn't work well?) so just use the first
  computer's IP address.

  So something like:
  RDP jeremy@192.168.1.1

  Ensure that the connection works.

  Test Case #2
  
  Do test case #1 but this time also enable the Legacy VNC option on the Remote 
Desktop Sharing page.
  Connect using VNC instead and ensure that the connection works.

  What Could Go Wrong
  ---
  RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. 
(Previously only VNC Sharing was offered.)

  RDP Sharing can be used for providing remote support so it's important
  that this feature works well because it may be difficult for the
  remote admin to fix issues in person.

  gnome-remote-desktop is part of GNOME Core and falls under the GNOME
  Stable Release Update microrelease exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970662/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1971195] Re: gnome-remote-desktop leads to a session crash inside qemu with virtio-vga

** Description changed:

- Steps to reproduce:
+ Impact
+ ==
+ A minimal QEMU image of Ubuntu Desktop will fail to start after installing.
This is because of a gnome-remote-desktop crash made worse because the
gnome-remote-desktop service was always running. This update fixes the crash
and stops gnome-remote-desktop from running when it's not in use.
+
+ We worked around this bug before the Ubuntu 22.04 LTS release by
+ updating osinfo-db so that installs using GNOME Boxes and Virt Manager
+ would do the right thing by default. But that didn't help for this
+ particular test case.
+
+ Test Case
+ =
1. On a jammy host, create a jammy guest:
$ qemu-img create -f qcow2 vm.qcow2 50G
$ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device
virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO]

2. Install Ubuntu in that VM (minimal install), no problems are expected
yet.

3. After the installation is concluded and the VM reboots, try to login
using the Wayland session (it should be the default, no need to select
anything). It will fail and bring you back to the login screen
(apparently due to a gnome-shell crash; I don't think the details are
relevant to the problem here).

What is expected: that both the Wayland and X11 sessions work out-of-
the-box.

- Workaround: remove gnome-remote-desktop, and the Wayland session will
- work just fine in the conditions described above. This is why I'm
- reporting this issue in gnome-remote-desktop instead of Wayland or
- gnome-shell or qemu. I might be wrong though...
+ Workaround
+ ===
+ remove gnome-remote-desktop, and the Wayland session will work just fine in
the conditions described above. This is why I'm reporting this issue in
gnome-remote-desktop instead of Wayland or gnome-shell or qemu. I might be
wrong though...

- Extra information:
+ Extra information
+ =
1. gnome-shell starts as expected if the X11 session is selected instead.
2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it
work in both the X11 and Wayland sessions:
$ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device
virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2
+
+ What Could Go Wrong
+ ===
+ See the master update bug report at LP: #1970662

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1971195

Title:
gnome-remote-desktop leads to a session crash inside qemu with virtio-
vga

Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in gnome-remote-desktop source package in Jammy:
In Progress

Bug description:
Impact
==
A minimal QEMU image of Ubuntu Desktop will fail to start after installing.
This is because of a gnome-remote-desktop crash made worse because the
gnome-remote-desktop service was always running. This update fixes the crash
and stops gnome-remote-desktop from running when it's not in use.

We worked around this bug before the Ubuntu 22.04 LTS release by
updating osinfo-db so that installs using GNOME Boxes and Virt Manager
would do the right thing by default. But that didn't help for this
particular test case.

Test Case
=
1. On a jammy host, create a jammy guest:
$ qemu-img create -f qcow2 vm.qcow2 50G
$ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device
virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO]

2. Install Ubuntu in that VM (minimal install), no problems are
expected yet.

3. After the installation is concluded and the VM reboots, try to
login using the Wayland session (it should be the default, no need to
select anything). It will fail and bring you back to the login screen
(apparently due to a gnome-shell crash; I don't think the details are
relevant to the problem here).

What is expected: that both the Wayland and X11 sessions work out-of-
the-box.

Workaround
===
remove gnome-remote-desktop, and the Wayland session will work just fine in
the conditions described above. This is why I'm reporting this issue in
gnome-remote-desktop instead of Wayland or gnome-shell or qemu. I might be
wrong though...

Extra information
=
1. gnome-shell starts as expected if the X11 session is selected instead.
2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it
work in both the X11 and Wayland sessions:
$ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device
virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2

What Could Go Wrong
===
See the master update bug report at LP: #1970662

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971195/+subscriptions

--
Mailing list:

[Desktop-packages] [Bug 1973028] Re: gnome-remote-desktop user service is always running

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Status: Triaged => In Progress

** Description changed:

Impact
--
The gnome-remote-desktop systemd user service is always running.

This was a contributing factor for LP: #1971415

Although it's "harmless" for the user service to be running if remote
desktop sharing is not enabled, it's a waste of resources to run a
service if it's not needed.

Test Case
-
Install all Ubuntu updates and the gnome-remote-desktop update.
From a clean install (or new user), run this command:
systemctl --user status gnome-remote-desktop.service

It should show the service as "Active: inactive"

Open the Settings app to the Sharing page. Turn on Sharing and turn on
Remote Desktop. Use the systemctl command to verify that the service is
"Active: active (running). Log out and log back in and reverify.

Now turn off Remote Desktop Sharing and verify that the service is
inactive. Log out and log back in and reverify.

More details
---
- This fix uses a dpkg maintscript to remove
/etc/systemd/user/gnome-session.target.wants/gnome-remote-desktop.service .
(That file is a symlink to the actual service).
+ This fix uses a dpkg postinst script to remove
/etc/systemd/user/gnome-session.target.wants/gnome-remote-desktop.service .
(That file is a symlink to the actual service). We couldn't use
https://manpages.debian.org/unstable/dpkg-maintscript-helper because the file
is technically not a "conffile" as recognized by dpkg.

It also modifies debian/rules so that that file is no longer
automatically added.

Instead of /etc/systemd/user/ , the user service is intended to be
enabled with the symlink ~/.config/systemd/user/gnome-
session.target.wants/gnome-remote-desktop.service . That is appropriate
since the GNOME implementation is per-user, not system-wide and it is
also disabled by default.

Fixing this bug has been strongly urged by the GNOME Remote Desktop
maintainers, and this brings us in line with how non-Debian distros have
been packaging gnome-remote-desktop.

What could go wrong
---
The RDP and VNC sharing services in GNOME could start when they shouldn't or
not start when they should.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1973028

Title:
gnome-remote-desktop user service is always running

Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in gnome-remote-desktop source package in Jammy:
In Progress

Bug description:
Impact
--
The gnome-remote-desktop systemd user service is always running.

This was a contributing factor for LP: #1971415

Although it's "harmless" for the user service to be running if remote
desktop sharing is not enabled, it's a waste of resources to run a
service if it's not needed.

Test Case
-
Install all Ubuntu updates and the gnome-remote-desktop update.
From a clean install (or new user), run this command:
systemctl --user status gnome-remote-desktop.service

It should show the service as "Active: inactive"

Open the Settings app to the Sharing page. Turn on Sharing and turn on
Remote Desktop. Use the systemctl command to verify that the service
is "Active: active (running). Log out and log back in and reverify.

Now turn off Remote Desktop Sharing and verify that the service is
inactive. Log out and log back in and reverify.

More details
---
This fix uses a dpkg postinst script to remove
/etc/systemd/user/gnome-session.target.wants/gnome-remote-desktop.service .
(That file is a symlink to the actual service). We couldn't use
https://manpages.debian.org/unstable/dpkg-maintscript-helper because the file
is technically not a "conffile" as recognized by dpkg.

It also modifies debian/rules so that that file is no longer
automatically added.

Instead of /etc/systemd/user/ , the user service is intended to be
enabled with the symlink ~/.config/systemd/user/gnome-
session.target.wants/gnome-remote-desktop.service . That is
appropriate since the GNOME implementation is per-user, not system-
wide and it is also disabled by default.

Fixing this bug has been strongly urged by the GNOME Remote Desktop
maintainers, and this brings us in line with how non-Debian distros
have been packaging gnome-remote-desktop.

What could go wrong
---
The RDP and VNC sharing services in GNOME could start when they shouldn't or
not start when they should.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1973028/+subscriptions

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help :

[Desktop-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: fuse3 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: gnome-remote-desktop (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** No longer affects: fuse3 (Ubuntu)

** No longer affects: fuse3 (Ubuntu Jammy)

** No longer affects: linux (Ubuntu Jammy)

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
   Importance: Undecided => Low

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1970411

Title:
  gnome-remote-desktop-daemon crashes on fuse_thread_func →
  g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
  missing fusermount3)

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in gnome-remote-desktop source package in Jammy:
  In Progress
Status in gnome-remote-desktop package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  GNOME Remote desktop crashes if fuse3 package is not installed as it provides 
fusermount3, that fuse_session_mount() implicitly requires.

  Test Case
  =
  Verify that gnome-remote-desktop has a dependency on fuse3

  What Could Go Wrong
  ==
  This just adds a dependency.

  This bug should be very uncommon because a system without fuse3 also
  wouldn't have xdg-desktop-portal installed meaning Snaps don't work
  and wouldn't have ubuntu-desktop-minimal installed.

  Other Info
  =
  libfuse3 is currently suggesting fusermount3, I'm wondering if we should 
instead recommending it, given that one of the library function relies on that. 
It's possible for things to use the library without that function so that's why 
it's proposed to be only a Recommends and not a Depends.

  For Ubuntu 22.10, we should see if the kernel can support this
  natively without needing fusermount3 as suggested in comment 1.

  
  Stack trace:

  #0  g_log_structured_array (log_level=, fields=0x7f7859fefdd0, 
n_fields=3) at ../../../glib/gmessages.c:557
  writer_func = 
  writer_user_data = 
  recursion = 
  depth = 
  __func__ = "g_log_structured_array"
  _g_boolean_var_ = 
  #1  0x7f79092e2f99 in g_log_default_handler 
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, 
message=message@entry=0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem", unused_data=unused_data@entry=0x0) at 
../../../glib/gmessages.c:3295
  fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 
0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 
0x7f790939a109, length = -1}, {key = 0x7f790932a09f  
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 
140157821898257}}
  n_fields = 
  #2  0x7f79092e43fa in g_logv (log_domain=0x0, 
log_level=G_LOG_LEVEL_ERROR, format=, args=) at 
../../../glib/gmessages.c:1387
  domain = 0x0
  data = 0x0
  depth = 
  log_func = 0x7f79092e2ee0 
  domain_fatal_mask = 
  masquerade_fatal = 0
  test_level = 6
  was_fatal = 
  was_recursion = 
  buffer = 
  msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  i = 2
  size = 
  #3  0x7f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, 
log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 
"[FUSE Clipboard] Failed to mount FUSE filesystem") at 
../../../glib/gmessages.c:1456
  args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
  #4  0x5605ec5c0920 in fuse_thread_func (data=0x5605ed301820) at 
../src/grd-rdp-fuse-clipboard.c:1321
  rdp_fuse_clipboard = 0x5605ed301820
  args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
  argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"}
  result = 

  Further details:
   - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970411/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1970662] Re: Update gnome-remote-desktop to 42.1.1