[Desktop-packages] [Bug 1947434] Re: Windows always open across monitors in a multi-monitor setup

[Najeeb Anwer]

This setting (center-new-windows) was already set to false. I have Gnome
Tweaks installed and this was one of the first settings I checked. This
setting can be true or false; it has no effect.

Curiously, the behavior changes if I use the "Dash to Dock" extension
instead of the "Ubuntu Dock".

With "Dash to Dock", the app window remembers it's size and position
better (i.e. If I move the window to the primary monitor and resize it,
it opens up at the same size and place).

With "Ubuntu Dock" enabled, the window always seems to randomly open on
the secondary monitor, or get resized, or straddles the two displays as
previously reported. Firefox and Terminal, in particular, always open
with their window straddling the two displays. If I move the app window
to the primary monitor, close it and reopen it, it goes back to
straddling the displays.

-- 
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/1947434

Title:
  Windows always open across monitors in a multi-monitor setup

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor 
(Dell U2719DC).
  Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 
21.04 too.

  If I log in using Wayland (the default), the initial window position
  of any app is always in the middle (half on the internal display and
  half on the external monitor). No setting that I have found appears to
  be able to change this behavior.

  If I switch to Xorg, this problem does not exist. With Xorg, the app window 
always opens on the primary monitor (the external one, in my case). This is the 
preferred behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-06-18 (487 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (3 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/1947434/+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 1939740] Re: Reporting a bug fails because of error message "Invalid core dump"

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

-- 
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/1939740

Title:
  Reporting a bug fails because of error message "Invalid core dump"

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  After starting my desktop, I received a message that (I believe)
  gnome-shell encountered an issue and I confirmed to send this report
  to ubuntu. However, the submission process failed because of the
  following error message:

  "Problem in gnome-shell

  Das Problem kann nicht gemeldet werden:

  Invalid core dump: BFD:warning: /tmp/apport_core_wu53zz5_ is
  truncated: expected core file size >= 611393536, found: 356581376"

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 12 20:41:22 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-07-16 (27 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210715)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  SourcePackage: gnome-shell
  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/1939740/+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 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"

[Alex Tu]

** Also affects: subiquity
   Importance: Undecided
   Status: New

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

Title:
  "ubuntu-drivers install" needs to be used when installing nvidia-
  driver if enabling "third-party packages"

Status in OEM Priority Project:
  Confirmed
Status in subiquity:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released

Bug description:
  ubiquity calls
  ```
  ubuntu-drivers install $FREEONLY $NOOEM --package-list 
/run/ubuntu-drivers.autoinstall
  ```
  to generate package list during live system but "ubuntu-drivers install" not 
only install packages but also create some config files for switching nvidia 
mode (e.g. on-demand) and change the runtime config as well (e.g. modify the 
iniramfs).

  Thus, not only package list needs to be referred but also the
  configuration.

  ---

  In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to 
install package. It also skipping the nvidia-mode changing (made by 
ubuntu-drivers install).
  ```
  $ cat ubiquity/target-config/31ubuntu_driver_packages
  #!/bin/sh
  set -e

  # install all packages that "ubuntu-drivers autoinstall" installed into the
  # live system. Ubiquity calls this with --package-list 
/run/ubuntu-drivers.autoinstall

  PKGLIST=/run/ubuntu-drivers.autoinstall
  [ -e $PKGLIST ] || exit 0

  for p in `cat $PKGLIST`; do
  apt-install $p
  done
  ```

  ---

  We need to use a same approach to make sure the nvidia mode is same on
  a same system (either all handing by ubuntu-drivers install or change
  the logic to maintainer script in each package).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943816/+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 1774053] Re: Missing characters in gnome-shell after lock screen

[Daniel van Vugt]

See also bug 1876632.

-- 
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/1774053

Title:
  Missing characters in gnome-shell after lock screen

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I locked my screen, came back from lunch, and found that about half
  the characters in the lock screen were missing. After I logged back
  in, half the characters in the desktop were missing
  
(https://drive.google.com/file/d/1mIDF4_jY0PIFOT53FoOOVoTY1BWeaNfy/view?usp=sharing).
  Chrome and Nautilus are not missing any characters, just the system
  UI.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 29 12:25:58 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com']"
   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-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-10 (48 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1774053/+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 1947597] Re: Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[Daniel van Vugt]

*** This bug is a duplicate of bug 1774053 ***
https://bugs.launchpad.net/bugs/1774053

There is also an Nvidia-specific cause of this issue in bug 1876632.

** This bug has been marked a duplicate of bug 1774053
   Missing characters in gnome-shell after lock screen

-- 
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/1947597

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-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..0a.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  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:53:12 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] 
[1458:37c2]
  InstallationDate: Installed on 2021-10-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947597/+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 1947597] Re: Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[Daniel van Vugt]

*** This bug is a duplicate of bug 1774053 ***
https://bugs.launchpad.net/bugs/1774053

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1774053, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

-- 
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/1947597

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-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..0a.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  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:53:12 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] 
[1458:37c2]
  InstallationDate: Installed on 2021-10-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

[Daniel van Vugt]

** Summary changed:

- [nvidia] Corrupted shell textures when switching users or resuming from 
suspend
+ [nvidia] Corrupted/missing shell textures when switching users or resuming 
from suspend

-- 
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/1876632

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed

Bug description:
  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .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  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1876632/+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 1947597] Re: Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[Daniel van Vugt]

*** This bug is a duplicate of bug 1774053 ***
https://bugs.launchpad.net/bugs/1774053

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470
(Ubuntu)

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

** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-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..0a.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  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:53:12 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] 
[1458:37c2]
  InstallationDate: Installed on 2021-10-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947597/+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 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock

[Daniel van Vugt]

In the log of comment #6 it looks like you managed a soft reboot rather
than the hard reboot I was expecting. That's good news for you but made
understanding the log a bit more difficult. It appears the problem you
hit was a gnome-shell crash:

Oct 18 12:52:58 fluffy gnome-shell[4425]: The program 'gnome-shell' received an 
X Window System error.
  This probably reflects a bug in the 
program.
  The error was 'BadRROutput (invalid 
Output parameter)'.
(Details: serial 1470 error_code 
145 request_code 139 (RANDR) minor_code 30)
(Note to programmers: normally, X 
errors are reported asynchronously;
 that is, you will receive the 
error a while after causing it.
 To debug your program, run it with 
the GDK_SYNCHRONIZE environment
 variable to change this behavior. 
You can then get a meaningful
 backtrace from your debugger if 
you break on the gdk_x_error() function.)
Oct 18 12:52:58 fluffy kernel: traps: gnome-shell[4425] trap int3 
ip:7f0e88877647 sp:7ffe8b7aa5a0 error:0 in 
libglib-2.0.so.0.6800.1[7f0e88834000+8d000]

So once you manage to report your .crash files (using apport-cli),
please provide a link to what it created.

-- 
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/1947194

Title:
  When using Wayland in 21.04, the display often never wakes up after
  lock

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using Wayland in 21.04, the display often never wakes up after
  lock up. Also, on boot up, desktop icons and most favorites on dash
  are not displayed, even though desktop icons are enabled. I can get
  them to show up only by re-enabling desktop icons. The workaround now
  is to disable Wayland, and the original xorg server works fine. The
  display driver is:

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  The monitor is an HP 22cwa running of of a displayport interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 14 14:32:26 2021
  DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:047e]
  InstallationDate: Installed on 2018-12-04 (1044 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. OptiPlex 990
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago)
  dmi.bios.date: 11/24/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


-- 

[Desktop-packages] [Bug 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock

[Daniel van Vugt]

Also, please edit /etc/environment and add a line:

  GDK_SYNCHRONIZE=1

That will slow the system slightly but will make the next crash occur in
a more *debuggable* way. It will create a new unique crash so please
tell us the link to that one too.

-- 
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/1947194

Title:
  When using Wayland in 21.04, the display often never wakes up after
  lock

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using Wayland in 21.04, the display often never wakes up after
  lock up. Also, on boot up, desktop icons and most favorites on dash
  are not displayed, even though desktop icons are enabled. I can get
  them to show up only by re-enabling desktop icons. The workaround now
  is to disable Wayland, and the original xorg server works fine. The
  display driver is:

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  The monitor is an HP 22cwa running of of a displayport interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 14 14:32:26 2021
  DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:047e]
  InstallationDate: Installed on 2018-12-04 (1044 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. OptiPlex 990
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago)
  dmi.bios.date: 11/24/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+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 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock

[Daniel van Vugt]

If ubuntu-bug fails then try apport-cli instead.

-- 
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/1947194

Title:
  When using Wayland in 21.04, the display often never wakes up after
  lock

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using Wayland in 21.04, the display often never wakes up after
  lock up. Also, on boot up, desktop icons and most favorites on dash
  are not displayed, even though desktop icons are enabled. I can get
  them to show up only by re-enabling desktop icons. The workaround now
  is to disable Wayland, and the original xorg server works fine. The
  display driver is:

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  The monitor is an HP 22cwa running of of a displayport interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 14 14:32:26 2021
  DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:047e]
  InstallationDate: Installed on 2018-12-04 (1044 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. OptiPlex 990
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago)
  dmi.bios.date: 11/24/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

[Daniel van Vugt]

It appears comments are displayed in chronological order rather than the
numerical order they were added to the page. Those can be different when
we import comments from another bug tracker (those with a grey
background). It's weird but seems to make sense.

-- 
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/1932328

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in GNOME Shell:
  Unknown
Status in Mozilla Thunderbird:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" 
does not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side

[Daniel van Vugt]

Yes the fix is scheduled to arrive first in Ubuntu 22.04. Although I
have not seen the bug in a long time myself so I won't rush backporting
the fix until we're sure it's working in 22.04.

-- 
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/1882291

Title:
  Gnome Shell clock is truncated/corrupt on the right side

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  When clock changes value, it doesn't displaying time properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1882291/+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 1947587] Re: Context (right click) menu does not appear on dual-monitor setup when dock is active on all screens

[Daniel van Vugt]

*** This bug is a duplicate of bug 1930567 ***
https://bugs.launchpad.net/bugs/1930567

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1930567, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1930567
   Popup menus don't appear at all if opened close to inter-monitor boundaries 
in Wayland sessions

-- 
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/1947587

Title:
  Context (right click) menu does not appear on dual-monitor setup when
  dock is active on all screens

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, primary monitor on the left, secondary
  monitor on the right, exactly lined up, on Wayland, Intel graphics
  drivers, Ubuntu 21.10 (but issue was already present in 21.04)

  I have Ubuntu Dock enabled on all monitors, on the left side of the
  screen (which is default) and symbol size 28 (but this size does not
  seem to matter).

  Independent from the running program, when I try to bring up the
  context (right click) menu close to the right side of the left screen,
  the context menu will not show up.

  I disabled the "dock on all monitors" and _then_ the context menu will
  show up, but weirdly on the right monitor stuck to the left side of
  the screen - even if the context menu gladly will right-align when not
  too close to the border of the screen.

  Now the dock and the weird context menu behaviour seem to overlap
  somehow and the context menu will not show up at all.

  Sounds similar to this:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/1783

  and while searching I found this:
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930567
  which sounds very similar or might be even the same.

  
  I will try in X11 and report if the issue is there as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  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: Mon Oct 18 14:38:50 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-15 (489 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-15 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947587/+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 1947434] Re: Windows always open across monitors in a multi-monitor setup

[Daniel van Vugt]

Please try:

  gsettings set org.gnome.mutter center-new-windows false

** Changed in: gnome-shell (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/1947434

Title:
  Windows always open across monitors in a multi-monitor setup

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor 
(Dell U2719DC).
  Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 
21.04 too.

  If I log in using Wayland (the default), the initial window position
  of any app is always in the middle (half on the internal display and
  half on the external monitor). No setting that I have found appears to
  be able to change this behavior.

  If I switch to Xorg, this problem does not exist. With Xorg, the app window 
always opens on the primary monitor (the external one, in my case). This is the 
preferred behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-06-18 (487 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (3 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/1947434/+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 1947519] Re: Unless gedit is installed, "Appearance" causes control center to crash

[Daniel van Vugt]

That doesn't look like a fix. You can prevent a program from
crashing/exiting when a schema is missing, but I forget the exact API
changes required.

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

Title:
  Unless gedit is installed, "Appearance" causes control center to crash

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 21.10. Gedit not installed from deb (I use a Flatpak version).

  Steps to reproduce:

  - sudo apt remove gedit
  - sudo apt autoremove
  - gnome-control-center ubuntu

  Expected: control center opens with Appearance tab shown
  Experienced: nothing happens, log in terminal:

  (gnome-control-center:27462): GLib-GIO-ERROR **: 22:03:20.416:
  Settings schema 'org.gnome.gedit.preferences.editor' is not installed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 17 21:57:23 2021
  InstallationDate: Installed on 2021-06-30 (109 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-15 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947519/+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 1820523] Re: OSK Enter, space and backspace keys don't work when typing in Greek

[Daniel van Vugt]

Upstream says it is fixed in
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1955

** Changed in: gnome-shell (Ubuntu)
   Status: Won't Fix => Fix Committed

** Tags added: fixed-in-41.1 fixed-upstream

** Package changed: gnome-shell (Ubuntu) => mutter (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/1820523

Title:
  OSK Enter, space and backspace keys don't work when typing in Greek

Status in GNOME Shell:
  New
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  The enter, space and backspace keys on the Ubuntu On-screen keyboard
  don't work when typing in Greek.

  Applies to Ubuntu 18.10 and 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1820523/+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 1947642] [NEW] ipv6 enabled despite 'disabled' setting?

[Seth Arnold]

Public bug reported:

Hello,

Periodically our OpenVPN sessions fail in such a way that automated
tooling that talks to Launchpad will take minutes before timing out.

See https://portal.admin.canonical.com/132804 for details.

We've found that manually disabling ipv6 helps, eg:

sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1

The network-manager-openvpn portion of the bug is that we've got IPv6
set to "disabled" in the network manager vpn GUI. Somehow this isn't
sufficient on its own. The sysctl does the trick.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager-openvpn 1.8.12-1
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname: Linux 5.4.0-77-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_4_0_77_86_generic_81 
lkp_Ubuntu_5_4_0_77_86_generic_79 zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Oct 18 23:55:49 2021
SourcePackage: network-manager-openvpn
UpgradeStatus: Upgraded to focal on 2020-01-24 (633 days ago)

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  ipv6 enabled despite 'disabled' setting?

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  Hello,

  Periodically our OpenVPN sessions fail in such a way that automated
  tooling that talks to Launchpad will take minutes before timing out.

  See https://portal.admin.canonical.com/132804 for details.

  We've found that manually disabling ipv6 helps, eg:

  sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1

  The network-manager-openvpn portion of the bug is that we've got IPv6
  set to "disabled" in the network manager vpn GUI. Somehow this isn't
  sufficient on its own. The sysctl does the trick.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager-openvpn 1.8.12-1
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_77_86_generic_81 
lkp_Ubuntu_5_4_0_77_86_generic_79 zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Oct 18 23:55:49 2021
  SourcePackage: network-manager-openvpn
  UpgradeStatus: Upgraded to focal on 2020-01-24 (633 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1947642/+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 1939592] Re: Login screen (gdm3) is purple blank after switching userA -> userB -> userA again

[Launchpad Bug Tracker]

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

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

-- 
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/1939592

Title:
  Login screen (gdm3) is purple blank after switching userA -> userB ->
  userA again

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

Bug description:
  Login screen (gdm3) is purple blank after switching userA -> userB ->
  userA again.

  Sometimes need to switch 5 times.. but definitely after around 5 times
  gdm3 breaks (it shows just a blank purple screen with the cursor).

  ## Workaround

  Ctrl+Alt+F3 (or F4.. F5...) until I get to the user I need to (and unlock the 
screensaver there).
  OR: switch to the console and run "exec sudo systemctl restart gdm3". ("exec" 
is not necessary but highly desirable from the security point of view, so there 
won't be a logged in session).

  ## Workaround 2

  To not use gdm3. There are alternatives such as sddm or ligthdm:

  sudo apt install lightdm

  Ctrl+Alt+F5 (drop to a console)
  sudo systemctl stop gdm3
  exec sudo systemctl start display-manager

  ## Details

  arno@z390-linux:~$ dpkg -l gdm3
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--=
  ii  gdm3   3.36.3-0ubuntu0.20.04.4 amd64GNOME Display Manager

  arno@z390-linux:~$ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.11.0-25-generic 
root=UUID=a39515ec-3bed-493b-8286-3904a4aac9de ro quiet splash vt.handoff=7

  arno@z390-linux:~$ nvidia-smi
  Wed Aug 11 16:42:07 2021
  
+-+
  | NVIDIA-SMI 460.91.03Driver Version: 460.91.03CUDA Version: 11.2 
|
  
|---+--+--+
  | GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC 
|
  | Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. 
|
  |   |  |   MIG M. 
|
  
|===+==+==|
  |   0  GeForce RTX 207...  Off  | :01:00.0  On |  N/A 
|
  |  0%   37CP817W / 215W |473MiB /  7979MiB |  1%  Default 
|
  |   |  |  N/A 
|
  
+---+--+--+

  
+-+
  | Processes:  
|
  |  GPU   GI   CIPID   Type   Process name  GPU Memory 
|
  |ID   ID   Usage  
|
  
|=|
  |0   N/A  N/A  2211  G   /usr/lib/xorg/Xorg 35MiB 
|
  |0   N/A  N/A 10496  G   /usr/lib/xorg/Xorg106MiB 
|
  |0   N/A  N/A 10626  G   /usr/bin/gnome-shell  157MiB 
|
  |0   N/A  N/A 16828  G   /usr/lib/xorg/Xorg 35MiB 
|
  |0   N/A  N/A 38063  G   ...A= --shared-files   80MiB 
|
  
+-+

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.36.3-0ubuntu0.20.04.4
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 11 16:37:35 2021
  InstallationDate: Installed on 2020-09-26 (318 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1939592/+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 1939592] Re: Login screen (gdm3) is purple blank after switching userA -> userB -> userA again

[Launchpad Bug Tracker]

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

** Changed in: gdm3 (Ubuntu)
   Status: New => Confirmed

-- 
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/1939592

Title:
  Login screen (gdm3) is purple blank after switching userA -> userB ->
  userA again

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

Bug description:
  Login screen (gdm3) is purple blank after switching userA -> userB ->
  userA again.

  Sometimes need to switch 5 times.. but definitely after around 5 times
  gdm3 breaks (it shows just a blank purple screen with the cursor).

  ## Workaround

  Ctrl+Alt+F3 (or F4.. F5...) until I get to the user I need to (and unlock the 
screensaver there).
  OR: switch to the console and run "exec sudo systemctl restart gdm3". ("exec" 
is not necessary but highly desirable from the security point of view, so there 
won't be a logged in session).

  ## Workaround 2

  To not use gdm3. There are alternatives such as sddm or ligthdm:

  sudo apt install lightdm

  Ctrl+Alt+F5 (drop to a console)
  sudo systemctl stop gdm3
  exec sudo systemctl start display-manager

  ## Details

  arno@z390-linux:~$ dpkg -l gdm3
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--=
  ii  gdm3   3.36.3-0ubuntu0.20.04.4 amd64GNOME Display Manager

  arno@z390-linux:~$ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-5.11.0-25-generic 
root=UUID=a39515ec-3bed-493b-8286-3904a4aac9de ro quiet splash vt.handoff=7

  arno@z390-linux:~$ nvidia-smi
  Wed Aug 11 16:42:07 2021
  
+-+
  | NVIDIA-SMI 460.91.03Driver Version: 460.91.03CUDA Version: 11.2 
|
  
|---+--+--+
  | GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC 
|
  | Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. 
|
  |   |  |   MIG M. 
|
  
|===+==+==|
  |   0  GeForce RTX 207...  Off  | :01:00.0  On |  N/A 
|
  |  0%   37CP817W / 215W |473MiB /  7979MiB |  1%  Default 
|
  |   |  |  N/A 
|
  
+---+--+--+

  
+-+
  | Processes:  
|
  |  GPU   GI   CIPID   Type   Process name  GPU Memory 
|
  |ID   ID   Usage  
|
  
|=|
  |0   N/A  N/A  2211  G   /usr/lib/xorg/Xorg 35MiB 
|
  |0   N/A  N/A 10496  G   /usr/lib/xorg/Xorg106MiB 
|
  |0   N/A  N/A 10626  G   /usr/bin/gnome-shell  157MiB 
|
  |0   N/A  N/A 16828  G   /usr/lib/xorg/Xorg 35MiB 
|
  |0   N/A  N/A 38063  G   ...A= --shared-files   80MiB 
|
  
+-+

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.36.3-0ubuntu0.20.04.4
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 11 16:37:35 2021
  InstallationDate: Installed on 2020-09-26 (318 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1939592/+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 1869734] Re: openjade segfaults on all arch

[Bryce Harrington]

** Changed in: pgpool2 (Ubuntu)
   Status: New => Fix Released

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

Title:
  openjade segfaults on all arch

Status in openjade package in Ubuntu:
  Fix Released
Status in pgpool2 package in Ubuntu:
  Fix Released
Status in openjade package in Debian:
  Fix Released

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1947420] Re: Buggish interface @ workstation panels previews when using dual portrait

[Norbert]

Friends, you can read and check a temporary solution from
https://ubuntu-mate.community/t/workspace-switcher-scaling-issue-on-
ubuntu-mate-21-10-diagnosis-and-temporary-fix/24686/5 .

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

Title:
  Buggish interface @ workstation panels previews when using dual
  portrait

Status in MATE Desktop:
  New
Status in Ubuntu MATE:
  Confirmed
Status in libwnck3 package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Confirmed

Bug description:
  ...Freshly upgraded to 21.10 using the same OS that I used to open
  most of my previous video glitches ever...

  Using 2x monitor in portrait mode, the preview panel/widget(?) located
  at the bottom right side shows 2 things wrong:

  1. The "Workspace 1" preview is very elongated when compared to not only all 
of it's previous incarnations (from 14.04 to 21.10) but also has an 
inconsistent size when compared to it's neighbouring "Workspace 2". 
Expectation: both 1 and 2 should be sized identically.
  2. When hovering the mouse cursor on "Workspace 2" only it's left portion 
will highlight.
  Expectation: both monitors of "2" should highlight

  See enclosed picture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1947420/+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 1947635] [NEW] package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-340 skrypt post-installation zwrócił kod błędu 10

[TomCrusher]

Public bug reported:

Has not been installed under upgrade from 18.04 to 20.04

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu5.20.04.2
ProcVersionSignature: Ubuntu 4.15.0-159.167-generic 4.15.18
Uname: Linux 4.15.0-159-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.11-0ubuntu27.20
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Oct 18 22:49:48 2021
ErrorMessage: podproces zainstalowany pakiet nvidia-340 skrypt 
post-installation zwrócił kod błędu 10
InstallationDate: Installed on 2015-12-31 (2118 days ago)
InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140806.1)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: 
podproces zainstalowany pakiet nvidia-340 skrypt post-installation zwrócił kod 
błędu 10
UpgradeStatus: Upgraded to focal on 2021-10-18 (0 days ago)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade:
  podproces zainstalowany pakiet nvidia-340 skrypt post-installation
  zwrócił kod błędu 10

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  Has not been installed under upgrade from 18.04 to 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: Ubuntu 4.15.0-159.167-generic 4.15.18
  Uname: Linux 4.15.0-159-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Oct 18 22:49:48 2021
  ErrorMessage: podproces zainstalowany pakiet nvidia-340 skrypt 
post-installation zwrócił kod błędu 10
  InstallationDate: Installed on 2015-12-31 (2118 days ago)
  InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release 
amd64 (20140806.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: 
podproces zainstalowany pakiet nvidia-340 skrypt post-installation zwrócił kod 
błędu 10
  UpgradeStatus: Upgraded to focal on 2021-10-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1947635/+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 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file des

[Launchpad Bug Tracker]

This bug was fixed in the package gdebi - 0.9.5.7+nmu6

---
gdebi (0.9.5.7+nmu6) unstable; urgency=medium

  * Non-maintainer upload

  [ Christian Ehrhardt ]
  * GDebi/GDebiGtk.py:
- Don't call gio_copy_in_place if there is no path / uri being
  passed (LP: #1931394, closes: #989647).

  [ Dani Llewellyn ]
  * GDebi/GDebiGtk.py:
- Drop Ubuntu-specific changes - no-longer needed
  (LP: #1756238, LP: #1946499)

 -- Gunnar Hjalmarsson   Thu, 14 Oct 2021 23:45:16
+0200

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

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Invalid
Status in gdebi package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Confirmed
Status in gdebi source package in Impish:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   

[Desktop-packages] [Bug 1947630] [NEW] Ubuntu 21.10 - Raspbery Pi 4 (4G) desktop locks after boot

[Doug Baden]

Public bug reported:

I updated 20.40 to 21.10 this morning.  
I added the linux-modules-extra-raspi so I can start docker, which needs the 
veth module.  

Now the desktop freezes.  Attempted a full reboot - no changes.  
I ssh'ed into the system and docker is running all restarted modules 
(Prometheus, Grafana and AlertManager).  

I tried a sudo service gdm3 restart and watched gnome restart.  It freezes 
after a few minutes.
Tried the restart again and same symptoms.  

lsb_release -rd
Description:Ubuntu 21.10
Release:21.10

apt-cache policy gdm3
gdm3:
  Installed: 41~rc-0ubuntu2
  Candidate: 41~rc-0ubuntu2
  Version table:
 *** 41~rc-0ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports impish/main arm64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gdm3 41~rc-0ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14
Uname: Linux 5.13.0-1008-raspi aarch64
ApportVersion: 2.20.11-0ubuntu70
Architecture: arm64
CasperMD5CheckResult: unknown
Date: Mon Oct 18 16:25:57 2021
ImageMediaBuild: 20201022
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to impish on 2021-10-18 (0 days ago)
mtime.conffile..etc.gdm3.custom.conf: 2021-03-19T12:23:23.841423

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug arm64 arm64-image impish raspi-image

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

Title:
  Ubuntu 21.10 - Raspbery Pi 4 (4G) desktop locks after boot

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I updated 20.40 to 21.10 this morning.  
  I added the linux-modules-extra-raspi so I can start docker, which needs the 
veth module.  

  Now the desktop freezes.  Attempted a full reboot - no changes.  
  I ssh'ed into the system and docker is running all restarted modules 
(Prometheus, Grafana and AlertManager).  

  I tried a sudo service gdm3 restart and watched gnome restart.  It freezes 
after a few minutes.
  Tried the restart again and same symptoms.  

  lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10

  apt-cache policy gdm3
  gdm3:
Installed: 41~rc-0ubuntu2
Candidate: 41~rc-0ubuntu2
Version table:
   *** 41~rc-0ubuntu2 500
  500 http://ports.ubuntu.com/ubuntu-ports impish/main arm64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdm3 41~rc-0ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14
  Uname: Linux 5.13.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Mon Oct 18 16:25:57 2021
  ImageMediaBuild: 20201022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to impish on 2021-10-18 (0 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2021-03-19T12:23:23.841423

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1947630/+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 1947627] [NEW] Sound > Output Device selection reverts to default after resuming from sleepng from

[Oliver Smith]

Public bug reported:

My Dell XPS 13 is connected to a Lenovo Thinkpad docking station.

By default the audio output is selected as the audio out from the
docking station.

I manually select the output device to be the XPS speakers.

After going into standby/suspend mode the audio output reverts to the
docking station audio out.

Expected behaviour: The selected audio output device settings would be
persistent across standby/suspend.

Potentially this may be expected to be persistent across power off/on or
disconnect/reconnect as other settings (eg number of displays, order and
orientation) are maintained.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-control-center 1:3.38.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 18 20:58:55 2021
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2021-06-19 (121 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute wayland-session

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

Title:
  Sound > Output Device selection reverts to default after resuming from
  sleepng from

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  My Dell XPS 13 is connected to a Lenovo Thinkpad docking station.

  By default the audio output is selected as the audio out from the
  docking station.

  I manually select the output device to be the XPS speakers.

  After going into standby/suspend mode the audio output reverts to the
  docking station audio out.

  Expected behaviour: The selected audio output device settings would be
  persistent across standby/suspend.

  Potentially this may be expected to be persistent across power off/on
  or disconnect/reconnect as other settings (eg number of displays,
  order and orientation) are maintained.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-control-center 1:3.38.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 20:58:55 2021
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2021-06-19 (121 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947627/+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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

[Al Savage]

Interestingly, comments #18-23 are all missing for me; when I view the
comments online @
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328 , the
comments skip from #17 to #24.  Logged in or not.

-- 
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/1932328

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in GNOME Shell:
  Unknown
Status in Mozilla Thunderbird:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" 
does not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

[Tim Passingham]

On impish, wayland, Tbird 91.1.2 the problem returned.  I redid comment
18, since the new Tbird had updated the sh file.

-- 
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/1932328

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in GNOME Shell:
  Unknown
Status in Mozilla Thunderbird:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" 
does not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1873093] Re: Gnome-terminal tab bar steals keyboard focus

[Launchpad Bug Tracker]

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

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Confirmed

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

Title:
  Gnome-terminal tab bar steals keyboard focus

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure when it started, but using the version of Gnome-Terminal
  in latest ubuntu (GT 3.34.2), I regularly find the tab bar stealing
  keyboard focus.

  This is dangerous.

  The problem is usually that I click on a tab, leave the mouse there,
  and start typing. The tab bar then steals the first character typed.
  Sometimes I click in the terminal window, and then move the mouse out
  of the way (to the tab bar). Sometimes it happens later, when the
  mouse drifts onto a tab (maybe I knock it slightly while typing).

  There are many cases in which the unexpected loss of a character typed
  could lead to significant damage. For example,

  rm *~

  losing the tilde. Or

  sudo rm -rf /mnt/1/*

  losing the 1.

  I have preferred click to focus (as opposed to focus-follows-mouse) in
  X for nearly 30 years. Gnome-Terminal should not pervert this
  preference.

  Reported upstream - https://gitlab.gnome.org/GNOME/gnome-
  terminal/-/issues/245

  Not clear that this is 100% a bug with gnome-terminal, or whether it
  is an interaction between it and another part of the
  XWayland/gnome/gnome-shell setup.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-terminal 3.34.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 16 10:16:15 2020
  InstallationDate: Installed on 2020-03-15 (31 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1873093/+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

Re: [Desktop-packages] [Bug 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock

[Chris Hall]

I tried this with my 2 crash reports but ubuntu-bug reported an internal 
error each time, so I doubt that they became attached to the bug report.

Chris

On 2021-10-18 3:40 a.m., Daniel van Vugt wrote:
> Please also check for crashes using these steps:
> https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
>

-- 
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/1947194

Title:
  When using Wayland in 21.04, the display often never wakes up after
  lock

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using Wayland in 21.04, the display often never wakes up after
  lock up. Also, on boot up, desktop icons and most favorites on dash
  are not displayed, even though desktop icons are enabled. I can get
  them to show up only by re-enabling desktop icons. The workaround now
  is to disable Wayland, and the original xorg server works fine. The
  display driver is:

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  The monitor is an HP 22cwa running of of a displayport interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 14 14:32:26 2021
  DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:047e]
  InstallationDate: Installed on 2018-12-04 (1044 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. OptiPlex 990
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago)
  dmi.bios.date: 11/24/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+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 1946558] Re: [SRU] libreoffice 7.2.2 for impish

[Brian Murray]

Hello Rico, or anyone else affected,

Accepted libreoffice into impish-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.2-0ubuntu0.21.10.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libreoffice (Ubuntu Impish)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

Title:
  [SRU] libreoffice 7.2.2 for impish

Status in libreoffice package in Ubuntu:
  Triaged
Status in libreoffice source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.2.2 is in its second bugfix release of the 7.2 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.2_release

   * Version 7.2.1 is currently released in impish. For a list of fixed bugs 
compared to 7.2.1 see the list of bugs fixed in the release candidates of 7.2.2 
(that's a total of 68 bugs):
   https://wiki.documentfoundation.org/Releases/7.2.2/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.2.2/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_72/854/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/amd64/libr/libreoffice/20211010_212128_a2213@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/arm64/libr/libreoffice/20211011_063847_cff27@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/armhf/libr/libreoffice/20211010_152042_46a77@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/ppc64el/libr/libreoffice/20211010_131403_b895a@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/s390x/libr/libreoffice/20211010_145947_98155@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 68 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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


-- 
Mailing 

Re: [Desktop-packages] [Bug 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock

[Chris Hall]

One more thing. I was using Focal Fossa, but it was incompatible with a 
library needed for a program I needed for my work (gle-graphics). This 
forced me to upgrade to Groovy Gorilla and then Hirsute Hippo. My 
problems started because 21.04 defaulted to wayland. I have tried out 
Impish Indrie on an old Toshiba laptop, but the upgrade froze solid and 
then after reboot it said it could only do a partial upgrade. The 
partial upgrade works, but it has made me nervous at this time to try 
and upgrade my much more important desktop. for now, I can live with 
xorg, which works fine.

Chris

On 2021-10-17 10:21 p.m., Daniel van Vugt wrote:
> OK, thanks.
>
> Please:
>
> 1. Reproduce the bug in Wayland again.
>
> 2. Wait 10 seconds.
>
> 3. Reboot.
>
> 4. Run:
>
> journalctl -b-1 > prevboot.txt
>
> 5. Attach the resulting text file here.
>
> 6. Also consider trying Ubuntu 21.10 which was just released a couple of
> days ago.
>
> ** Summary changed:
>
> - Wayland only partially works
> + When using Wayland in 21.04, the display often never wakes up after lock
>
> ** Package changed: ubuntu => mutter (Ubuntu)
>

-- 
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/1947194

Title:
  When using Wayland in 21.04, the display often never wakes up after
  lock

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using Wayland in 21.04, the display often never wakes up after
  lock up. Also, on boot up, desktop icons and most favorites on dash
  are not displayed, even though desktop icons are enabled. I can get
  them to show up only by re-enabling desktop icons. The workaround now
  is to disable Wayland, and the original xorg server works fine. The
  display driver is:

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  The monitor is an HP 22cwa running of of a displayport interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 14 14:32:26 2021
  DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:047e]
  InstallationDate: Installed on 2018-12-04 (1044 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. OptiPlex 990
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago)
  dmi.bios.date: 11/24/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+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 1929999] Re: [SRU] libreoffice 6.4.7.2.M3 for Focal

[Brian Murray]

** Changed in: libreoffice (Ubuntu)
   Status: New => Invalid

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

Title:
  [SRU] libreoffice 6.4.7.2.M3 for Focal

Status in libreoffice package in Ubuntu:
  Invalid
Status in libreoffice source package in Focal:
  Triaged

Bug description:
  [Impact]

  * LibreOffice 6.4.7.2.M3 is a bug-fix release of the 6.4 line:
  It receives important bug-fixes on top of the 6.4 branch which is EOL 
since November 30, 2020. Currently maintained by Andras Timar for France's MIMO 
(https://blog.documentfoundation.org/blog/2013/06/17/the-document-foundation-welcomes-frances-mimo-in-the-advisory-board/)

  * Version 6.4.7 is currently released in focal.
  https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-6-4
  (that's a total of ?? bugs)

  * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

  * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  
https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/12712294/+listing-archive-extra

  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/amd64/libr/libreoffice/20210921_030416_a2220@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/arm64/libr/libreoffice/20210921_010758_2afcd@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/armhf/libr/libreoffice/20210920_223713_b4dfd@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/ppc64el/libr/libreoffice/20210920_232648_4df4d@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-ricotz-ppa/focal/s390x/libr/libreoffice/20210921_020008_6c843@/log.gz

  * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented
  by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

  * A minor release with a total of ?? bug fixes always carries the
  potential for introducing regressions, even though it is a bug-fix-
  only release, meaning that no new features were added, and no existing
  features were removed.

  * A combination of autopkgtests and careful smoke testing as described
  above should provide reasonable confidence that no regressions sneaked
  in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/192/+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

Re: [Desktop-packages] [Bug 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock

[Chris Hall]

Thanks Daniel. Here's the prevboot.txt file. There were 2 separate crash 
files generated when I booted using wayland. The first with my user 
permission was generated immediately and this was when there were no 
dash icons present. The second was generated with root ownership when 
the screen tried to dim (a cursor was visible in the top left of the 
screen). I needed to ctrl-alt-del to get the machine to reboot. It's a 
Dell Optiplex 990 mini-tower. I will try to attach the 2 crash reports 
using ubuntu-bug.

Chris

On 2021-10-17 10:21 p.m., Daniel van Vugt wrote:
> OK, thanks.
>
> Please:
>
> 1. Reproduce the bug in Wayland again.
>
> 2. Wait 10 seconds.
>
> 3. Reboot.
>
> 4. Run:
>
> journalctl -b-1 > prevboot.txt
>
> 5. Attach the resulting text file here.
>
> 6. Also consider trying Ubuntu 21.10 which was just released a couple of
> days ago.
>
> ** Summary changed:
>
> - Wayland only partially works
> + When using Wayland in 21.04, the display often never wakes up after lock
>
> ** Package changed: ubuntu => mutter (Ubuntu)
>


** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/bugs/1947194/+attachment/5533965/+files/prevboot.txt

-- 
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/1947194

Title:
  When using Wayland in 21.04, the display often never wakes up after
  lock

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using Wayland in 21.04, the display often never wakes up after
  lock up. Also, on boot up, desktop icons and most favorites on dash
  are not displayed, even though desktop icons are enabled. I can get
  them to show up only by re-enabling desktop icons. The workaround now
  is to disable Wayland, and the original xorg server works fine. The
  display driver is:

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  The monitor is an HP 22cwa running of of a displayport interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 14 14:32:26 2021
  DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:047e]
  InstallationDate: Installed on 2018-12-04 (1044 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. OptiPlex 990
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago)
  dmi.bios.date: 11/24/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

[Olivier Tilloy]

Sam, I know this doesn't address your main grief (it is actively being
worked on and tracked in a separate place), but for support purposes,
the "Help > About Firefox" dialog will show you whether the application
is packaged as a snap. Alternatively opening "about:support" will also
reveal this information. That's probably a bit easier than asking users
to run commands in a terminal.

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

Title:
  [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Fix Released
Status in ubuntu-settings source package in Impish:
  Fix Released

Bug description:
  Per Canonical's distribution agreement with Mozilla, we're making the
  snap¹ the default installation of firefox on desktop ISOs starting
  with Ubuntu 21.10.

  The snap is built and published for amd64, armhf and arm64. It is
  jointly maintained by Mozilla and the Ubuntu desktop team, and
  published by Mozilla.

  This requires updating the desktop-minimal seed, as well as ubuntu-
  release-upgrader.

  ¹ https://snapcraft.io/firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1947607] Re: Docs state to use ctrl-alt-shift-R to record screen recording, which will NEVER work correctly

[Gunnar Hjalmarsson]

Thanks for your report.

It's not clear to me how that step-by-step page encourages users to
"mis-use" the feature.

Anyway, the page in question is from GNOME Help, and if you want to
discuss its wording, I would recommend you to submit an upstream issue:

https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues

If you do, please post the URL to the upstream issue here for tracking
purposes.

** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu)

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

Title:
  Docs state to use ctrl-alt-shift-R to record screen recording, which
  will NEVER work correctly

Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  Ubuntu docs: https://help.ubuntu.com/stable/ubuntu-help/screen-shot-
  record.html are incorrectly sayig to mis-use this Gnome feature as a
  user-focussed 'Make a Screencast'

  According to the Gnome developers who implement/maintain this feature,
  it's only to be used for recording 30-second snippets and reporting
  bugs in Gnome.

  By design there is no warning that a screen-recording has been
  terminated at the 30 seconds mark, and it should (apparently) never be
  used for general screen-recordings. Ubuntu is encouraging people to
  mis-use this feature and thereby lose data (many bug reports against
  Gnome going back 5+ years of people requesting it be changed, closed
  as WONTFIX / by-design).

  It's non-trivial to make the feature work as described in the ubuntu
  docs, and there's no mention that it's hardcoded to 30 seconds max.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1947607/+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 1947607] [NEW] Docs state to use ctrl-alt-shift-R to record screen recording, which will NEVER work correctly

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu docs: https://help.ubuntu.com/stable/ubuntu-help/screen-shot-
record.html are incorrectly sayig to mis-use this Gnome feature as a
user-focussed 'Make a Screencast'

According to the Gnome developers who implement/maintain this feature,
it's only to be used for recording 30-second snippets and reporting bugs
in Gnome.

By design there is no warning that a screen-recording has been
terminated at the 30 seconds mark, and it should (apparently) never be
used for general screen-recordings. Ubuntu is encouraging people to mis-
use this feature and thereby lose data (many bug reports against Gnome
going back 5+ years of people requesting it be changed, closed as
WONTFIX / by-design).

It's non-trivial to make the feature work as described in the ubuntu
docs, and there's no mention that it's hardcoded to 30 seconds max.

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

-- 
Docs state to use ctrl-alt-shift-R to record screen recording, which will NEVER 
work correctly
https://bugs.launchpad.net/bugs/1947607
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-user-docs 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 1947434] ProcCpuinfoMinimal.txt

[Najeeb Anwer]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1947434/+attachment/5533912/+files/ProcCpuinfoMinimal.txt

-- 
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/1947434

Title:
  Windows always open across monitors in a multi-monitor setup

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor 
(Dell U2719DC).
  Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 
21.04 too.

  If I log in using Wayland (the default), the initial window position
  of any app is always in the middle (half on the internal display and
  half on the external monitor). No setting that I have found appears to
  be able to change this behavior.

  If I switch to Xorg, this problem does not exist. With Xorg, the app window 
always opens on the primary monitor (the external one, in my case). This is the 
preferred behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-06-18 (487 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (3 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/1947434/+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 1947434] GsettingsChanges.txt

[Najeeb Anwer]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1947434/+attachment/5533911/+files/GsettingsChanges.txt

-- 
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/1947434

Title:
  Windows always open across monitors in a multi-monitor setup

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor 
(Dell U2719DC).
  Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 
21.04 too.

  If I log in using Wayland (the default), the initial window position
  of any app is always in the middle (half on the internal display and
  half on the external monitor). No setting that I have found appears to
  be able to change this behavior.

  If I switch to Xorg, this problem does not exist. With Xorg, the app window 
always opens on the primary monitor (the external one, in my case). This is the 
preferred behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-06-18 (487 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (3 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/1947434/+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 1947434] ShellJournal.txt

[Najeeb Anwer]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1947434/+attachment/5533913/+files/ShellJournal.txt

-- 
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/1947434

Title:
  Windows always open across monitors in a multi-monitor setup

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor 
(Dell U2719DC).
  Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 
21.04 too.

  If I log in using Wayland (the default), the initial window position
  of any app is always in the middle (half on the internal display and
  half on the external monitor). No setting that I have found appears to
  be able to change this behavior.

  If I switch to Xorg, this problem does not exist. With Xorg, the app window 
always opens on the primary monitor (the external one, in my case). This is the 
preferred behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-06-18 (487 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (3 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/1947434/+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 1947434] monitors.xml.txt

[Najeeb Anwer]

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1947434/+attachment/5533914/+files/monitors.xml.txt

-- 
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/1947434

Title:
  Windows always open across monitors in a multi-monitor setup

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor 
(Dell U2719DC).
  Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 
21.04 too.

  If I log in using Wayland (the default), the initial window position
  of any app is always in the middle (half on the internal display and
  half on the external monitor). No setting that I have found appears to
  be able to change this behavior.

  If I switch to Xorg, this problem does not exist. With Xorg, the app window 
always opens on the primary monitor (the external one, in my case). This is the 
preferred behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-06-18 (487 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (3 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/1947434/+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 1947434] Re: Windows always open across monitors in a multi-monitor setup

[Najeeb Anwer]

apport information

** Tags added: apport-collected wayland-session

** Description changed:

  I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor 
(Dell U2719DC).
  Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 
21.04 too.
  
  If I log in using Wayland (the default), the initial window position of
  any app is always in the middle (half on the internal display and half
  on the external monitor). No setting that I have found appears to be
  able to change this behavior.
  
- If I switch to Xorg, this problem does not exist. With Xorg, the app
- window always opens on the primary monitor (the external one, in my
- case). This is the preferred behavior.
+ If I switch to Xorg, this problem does not exist. With Xorg, the app window 
always opens on the primary monitor (the external one, in my case). This is the 
preferred behavior.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu70
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2020-06-18 (487 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ Package: gnome-shell 40.5-1ubuntu2
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
+ RelatedPackageVersions: mutter-common 40.5-1ubuntu2
+ Tags:  impish wayland-session
+ Uname: Linux 5.13.0-19-generic x86_64
+ UpgradeStatus: Upgraded to impish on 2021-10-14 (3 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1947434/+attachment/5533910/+files/Dependencies.txt

-- 
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/1947434

Title:
  Windows always open across monitors in a multi-monitor setup

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor 
(Dell U2719DC).
  Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 
21.04 too.

  If I log in using Wayland (the default), the initial window position
  of any app is always in the middle (half on the internal display and
  half on the external monitor). No setting that I have found appears to
  be able to change this behavior.

  If I switch to Xorg, this problem does not exist. With Xorg, the app window 
always opens on the primary monitor (the external one, in my case). This is the 
preferred behavior.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-06-18 (487 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (3 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/1947434/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Olivier Tilloy]

After rebuilding the chromium snap with the above patch applied to
snap/command-chain/desktop-launch, and running it with the following
command line:

LIBVA_DRIVER_NAME=iHD
LIBVA_DRIVERS_PATH=/snap/chromium/x1/usr/lib/x86_64-linux-gnu/dri
LIBVA_MESSAGING_LEVEL=2 snap run chromium --enable-
features=VaapiVideoDecoder

I'm seeing "Video Decode: Hardware accelerated" in chrome://gpu, but
FFmpegVideoDecoder is still being used for decoding H264 videos, and
consequently the decoding is *not* hardware accelerated.

This is the relevant excerpt from chrome://media-internals:

info"Failed to initialize DecryptingVideoDecoder"
info"Failed to initialize Unknown Video Decoder"
info"Failed to initialize VpxVideoDecoder"
info"Failed to initialize Dav1dVideoDecoder"
kIsVideoDecryptingDemuxerStream false
kVideoDecoderName   "FFmpegVideoDecoder"
kIsPlatformVideoDecoder false
info"Selected FFmpegVideoDecoder for video decoding, config: codec: h264, 
profile: h264 high, level: not available, alpha_mode: is_opaque, coded size: 
[1920,1080], visible rect: [0,0,1920,1080], natural size: [1920,1080], has 
extra data: false, encryption scheme: Unencrypted, rotation: 0°, flipped: 0, 
color space: {primaries:BT709, transfer:BT709, matrix:BT709, range:LIMITED}"

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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

Re: [Desktop-packages] [Bug 1934194] Re: package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned err

[Carter Mills]

I'm the original bug reporter.

Carter
(615) 337-2472

On Mon, Oct 18, 2021, 10:40 AM Olivier Tilloy <1934...@bugs.launchpad.net>
wrote:

> Carter, are you the original bug reporter, or did you come across this
> bug searching for a problem similar to yours?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1934194
>
> Title:
>   package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to
>   install/upgrade: new chromium-browser package pre-installation script
>   subprocess returned error exit status 1
>
> Status in chromium-browser package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Just installed and received system unstable messages.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 20.04
>   Package: chromium-browser 91.0.4472.101-0ubuntu0.18.04.1
>   ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
>   Uname: Linux 5.4.0-77-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.18
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   DRM.card0-DVI-I-1:
>enabled: disabled
>dpms: On
>status: disconnected
>edid-base64:
>modes:
>   DRM.card0-HDMI-A-1:
>enabled: enabled
>dpms: On
>status: connected
>edid-base64:
> AP///wBBDAhXAQEBAQAXAQOAZjl4CvntplJQnyQKR0qhCACBwIGAswCpwAEBAQEBAQEBAjqAGHE4LUBYLEUA+jwyAAAeqRoAoFAAFjAwIDcA+jwyAAAa/AAzMlBGTDU3MDgvRjcK/QAXTA9RDwAKICAgICAgAV0CAx9xSQECAwQFByCQBiYJBwcVB1BmAwwAIACA4gAPAjqAGHE4LUBYLEUA+jwyAAAeAR2AGHEcFiBYLCUA+jwyAACeAR0AclHQHiBuKFUA+jwyAAAejArQiiDgLRAQPpYA+jwyAAAYjAqgFFHwFgAmfEMA+jwyAACYzw==
>modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080i
> 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1280x768 1280x720 1280x720
> 1280x720 1024x768 1440x480i 800x600 720x480 720x480 720x480 720x480 720x480
> 720x480i 720x480i 720x480i 720x480i 640x480 640x480 640x480 720x400
>   Date: Wed Jun 30 16:37:28 2021
>   Desktop-Session:
>'None'
>'None'
>'None'
>   Env:
>'None'
>'None'
>   ErrorMessage: new chromium-browser package pre-installation script
> subprocess returned error exit status 1
>   InstallationDate: Installed on 2020-09-01 (302 days ago)
>   InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release amd64
> (20190304.5)
>   InstalledPlugins:
>
>   Load-Avg-1min: 6.32
>   Load-Processes-Running-Percent:   0.2%
>   MachineType: Hewlett-Packard s5-1070t
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic
> root=UUID=a8b4761a-7e53-4c94-9a12-3ace3096a126 ro quiet splash vt.handoff=7
>   Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
> 3.8.2-0ubuntu2
>   PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2,
> 2.7.17-4
>   SourcePackage: chromium-browser
>   Title: package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to
> install/upgrade: new chromium-browser package pre-installation script
> subprocess returned error exit status 1
>   UpgradeStatus: Upgraded to focal on 2021-06-30 (0 days ago)
>   dmi.bios.date: 10/05/2011
>   dmi.bios.vendor: AMI
>   dmi.bios.version: 7.16
>   dmi.board.name: 2AC2
>   dmi.board.vendor: PEGATRON CORPORATION
>   dmi.board.version: 1.02A
>   dmi.chassis.asset.tag: 2MD1450H90
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.modalias:
> dmi:bvnAMI:bvr7.16:bd10/05/2011:svnHewlett-Packard:pns5-1070t:pvr1.02A:rvnPEGATRONCORPORATION:rn2AC2:rvr1.02A:cvnHewlett-Packard:ct3:cvr:
>   dmi.product.family: 103C_53316J G=D
>   dmi.product.name: s5-1070t
>   dmi.product.sku: LP019AV#ABA
>   dmi.product.version: 1.02A
>   dmi.sys.vendor: Hewlett-Packard
>   modified.conffile..etc.default.chromium-browser: [deleted]
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1934194/+subscriptions
>
>

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

Title:
  package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Just installed and received system unstable messages.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 91.0.4472.101-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  DRM.card0-DVI-I-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 

[Desktop-packages] [Bug 1947606] [NEW] Unmaximizing window results in different number of rows from before maximizing it

[abcdef]

Public bug reported:

When having e.g. a 7 rows high window (with two tabs) and maximizing +
unmaximizing it, the result is a 6 rows high window. Repeat it and it
goes to 5, 4, and finally 3 rows in height. It doesn't shrink past 3
rows.

It is especially noticeable with a long narrow window along the bottom
of the screen, where the distance to the bottom screen edge increases
every time the window height shrinks.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-terminal 3.38.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 18 17:19:44 2021
InstallationDate: Installed on 2020-10-30 (353 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to impish on 2021-09-17 (31 days ago)

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


** Tags: amd64 apport-bug impish wayland-session

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

Title:
  Unmaximizing window results in different number of rows from before
  maximizing it

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When having e.g. a 7 rows high window (with two tabs) and maximizing +
  unmaximizing it, the result is a 6 rows high window. Repeat it and it
  goes to 5, 4, and finally 3 rows in height. It doesn't shrink past 3
  rows.

  It is especially noticeable with a long narrow window along the bottom
  of the screen, where the distance to the bottom screen edge increases
  every time the window height shrinks.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-terminal 3.38.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 17:19:44 2021
  InstallationDate: Installed on 2020-10-30 (353 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to impish on 2021-09-17 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1947606/+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 1820523] Re: OSK Enter, space and backspace keys don't work when typing in Greek

[Konstantinos Tsimperdonis]

The problem exists in Ubuntu 20.04 desktop. I use the default onscreen 
keyboard. I have added a second language (greek) and it works fine on a real 
keyboard, but on the onscreen keyboard, some keys don't work (don't do 
anything) i.e. the backspace and the enter.
Do you know where can I find the onscreen key mapping and correct it?

-- 
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/1820523

Title:
  OSK Enter, space and backspace keys don't work when typing in Greek

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  The enter, space and backspace keys on the Ubuntu On-screen keyboard
  don't work when typing in Greek.

  Applies to Ubuntu 18.10 and 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1820523/+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

Re: [Desktop-packages] [Bug 1947420] Re: Buggish interface @ workstation panels previews when using dual portrait

[Daniel LaSalle]

Furthermore, space 1 and space 2 do not behave the same in terms of size
and UI


17 Oct 2021, 21:45 by 1947...@bugs.launchpad.net:

> Before UG each workspace was about 12mm wide, after UG they are about 6mm 
> wide.
> They appear to have changed, comparatively, from landscape to portrait view.
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1947420
>
> Title:
>  Buggish interface @ workstation panels previews when using dual
>  portrait
>
> Status in MATE Desktop:
>  New
> Status in Ubuntu MATE:
>  Confirmed
> Status in libwnck3 package in Ubuntu:
>  Confirmed
> Status in mate-panel package in Ubuntu:
>  Confirmed
>
> Bug description:
>  ...Freshly upgraded to 21.10 using the same OS that I used to open
>  most of my previous video glitches ever...
>
>  Using 2x monitor in portrait mode, the preview panel/widget(?) located
>  at the bottom right side shows 2 things wrong:
>
>  1. The "Workspace 1" preview is very elongated when compared to not only all 
> of it's previous incarnations (from 14.04 to 21.10) but also has an 
> inconsistent size when compared to it's neighbouring "Workspace 2". 
> Expectation: both 1 and 2 should be sized identically.
>  2. When hovering the mouse cursor on "Workspace 2" only it's left portion 
> will highlight.
>  Expectation: both monitors of "2" should highlight
>
>  See enclosed picture.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mate-desktop/+bug/1947420/+subscriptions
>

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

Title:
  Buggish interface @ workstation panels previews when using dual
  portrait

Status in MATE Desktop:
  New
Status in Ubuntu MATE:
  Confirmed
Status in libwnck3 package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Confirmed

Bug description:
  ...Freshly upgraded to 21.10 using the same OS that I used to open
  most of my previous video glitches ever...

  Using 2x monitor in portrait mode, the preview panel/widget(?) located
  at the bottom right side shows 2 things wrong:

  1. The "Workspace 1" preview is very elongated when compared to not only all 
of it's previous incarnations (from 14.04 to 21.10) but also has an 
inconsistent size when compared to it's neighbouring "Workspace 2". 
Expectation: both 1 and 2 should be sized identically.
  2. When hovering the mouse cursor on "Workspace 2" only it's left portion 
will highlight.
  Expectation: both monitors of "2" should highlight

  See enclosed picture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1947420/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

[Bug Watch Updater]

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

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 2020-08-29T19:14:49+00:00 Eduardo Rojas Rodríguez wrote:

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

Steps to reproduce:

Steps to reproduce:

Use the Firefox Snap build from Ubuntu Snap Store (Ubuntu software).

Install "chrome-gnome-shell" package.

Install Firefox GNOME Shell integration.

Go to "extensions.gnome.org" and choose any extension.


Actual results:

Actual results:

An error report shows that says the native host connector cannot be
detected.

There is no option to install the GNOME extension.


Expected results:

Expected results:

I should be able to install the chosen GNOME extension directly from the
website and manage it afterwards.

The behavior is correct on the current RPM/DEB builds.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1741074/comments/32


On 2020-08-29T19:17:44+00:00 Release-mgmt-account-bot wrote:

[Bugbug](https://github.com/mozilla/bugbug/) thinks this bug should
belong to this component, but please revert this change in case of
error.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1741074/comments/33


On 2021-10-01T14:46:37+00:00 Olivier Tilloy wrote:

The problem is being discussed at https://forum.snapcraft.io/t/native-
messaging-support-in-strictly-confined-browser-snaps/26849.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1741074/comments/44


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

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

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in Mozilla Firefox:
  New
Status in KeePassXC Snap Builds:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  Confirmed
Status in goopg package in Ubuntu:
  Confirmed
Status in kdeconnect package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chrome-gnome-
  shell-does-not-work-with-chromium-snap/3377)

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1741074/+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 1875216] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 1741074 ***
https://bugs.launchpad.net/bugs/1741074

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

** Changed in: firefox (Ubuntu)
   Status: New => Confirmed

-- 
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/1875216

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I am on Ubuntu 20.04 and snap Firefox 75.0-3.

  I keep getting "Although GNOME Shell integration extension is running,
  native host connector is not detected. Refer documentation for
  instructions about installing connector."

  Of course, I have already done "sudo apt-get install chrome-gnome-
  shell" and I am confident that the installation went well because
  Gnome shell integration works just fine if I use it on deb-Chrome.

  The issue should then be related to Firefox snap for Ubuntu. In add-on
  preferences, I get "Your native host connector does not support check
  for GNOME Shell extensions updates. Probably python-requests package
  is missing."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1875216/+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 1934194] Re: package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error e

[Olivier Tilloy]

Carter, are you the original bug reporter, or did you come across this
bug searching for a problem similar to yours?

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

Title:
  package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Just installed and received system unstable messages.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 91.0.4472.101-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  DRM.card0-DVI-I-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBBDAhXAQEBAQAXAQOAZjl4CvntplJQnyQKR0qhCACBwIGAswCpwAEBAQEBAQEBAjqAGHE4LUBYLEUA+jwyAAAeqRoAoFAAFjAwIDcA+jwyAAAa/AAzMlBGTDU3MDgvRjcK/QAXTA9RDwAKICAgICAgAV0CAx9xSQECAwQFByCQBiYJBwcVB1BmAwwAIACA4gAPAjqAGHE4LUBYLEUA+jwyAAAeAR2AGHEcFiBYLCUA+jwyAACeAR0AclHQHiBuKFUA+jwyAAAejArQiiDgLRAQPpYA+jwyAAAYjAqgFFHwFgAmfEMA+jwyAACYzw==
   modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080i 
1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1280x768 1280x720 1280x720 
1280x720 1024x768 1440x480i 800x600 720x480 720x480 720x480 720x480 720x480 
720x480i 720x480i 720x480i 720x480i 640x480 640x480 640x480 720x400
  Date: Wed Jun 30 16:37:28 2021
  Desktop-Session:
   'None'
   'None'
   'None'
  Env:
   'None'
   'None'
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-09-01 (302 days ago)
  InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release amd64 
(20190304.5)
  InstalledPlugins:
   
  Load-Avg-1min: 6.32
  Load-Processes-Running-Percent:   0.2%
  MachineType: Hewlett-Packard s5-1070t
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-77-generic 
root=UUID=a8b4761a-7e53-4c94-9a12-3ace3096a126 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  SourcePackage: chromium-browser
  Title: package chromium-browser 91.0.4472.101-0ubuntu0.18.04.1 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2021-06-30 (0 days ago)
  dmi.bios.date: 10/05/2011
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.16
  dmi.board.name: 2AC2
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.02A
  dmi.chassis.asset.tag: 2MD1450H90
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr7.16:bd10/05/2011:svnHewlett-Packard:pns5-1070t:pvr1.02A:rvnPEGATRONCORPORATION:rn2AC2:rvr1.02A:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: s5-1070t
  dmi.product.sku: LP019AV#ABA
  dmi.product.version: 1.02A
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1934194/+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 1947257] Re: Partial profile loss on upgrade from 21.04 to 21.10

[Olivier Tilloy]

I understand the frustration. It's unlikely that the profile import lost
one of the windows in such a reproducible manner, but just in case, can
you try re-installing the firefox deb (if it was removed: `sudo apt
install firefox`), run it after closing the snap (`/usr/bin/firefox`)
and see if your main window is restored?

-- 
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/1947257

Title:
  Partial profile loss on upgrade from 21.04 to 21.10

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  In the upgrade from 21.04 to 21.10 I noticed it had updated firefox.
  When restarting some of my profile was kept (themes, addons, etc) but
  I've noticed my primary window of 50+ tabs was lost. It opened 3 other
  windows correctly.

  I tried to find it via "recently closed tabs/windows" but it's not
  showing up. I have also confirmed there are no duplicate profiles.

  Silly me assumed it was done correctly and when the upgrade process
  offered to remove old packages I did so I can't seem to retrieve the
  old profile.

  Additional information:

  lsb_release -rd:
  Description:  Ubuntu 21.10
  Release:  21.10

  snap package information:
  snap-id:  3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  tracking: latest/stable/ubuntu-21.10
  refresh-date: today at 09:00 AEST
  channels:
latest/stable:93.0-1   2021-10-08 (631) 157MB -
latest/candidate: 93.0-1   2021-09-28 (631) 157MB -
latest/beta:  94.0b5-1 2021-10-13 (650) 157MB -
latest/edge:  ↑   
esr/stable:   78.15.0esr-1 2021-10-04 (637) 148MB -
esr/candidate:91.2.0esr-1  2021-09-29 (634) 160MB -
esr/beta: ↑   
esr/edge: ↑   
  installed:  93.0-1  (631) 157MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947257/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

[Olivier Tilloy]

** Also affects: firefox (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: firefox (Ubuntu)
   Status: New => Confirmed

** Changed in: firefox (Ubuntu)
   Importance: Undecided => High

** Changed in: firefox (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1661935
   Importance: Unknown
   Status: Unknown

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

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in Mozilla Firefox:
  Unknown
Status in KeePassXC Snap Builds:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  Confirmed
Status in goopg package in Ubuntu:
  Confirmed
Status in kdeconnect package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chrome-gnome-
  shell-does-not-work-with-chromium-snap/3377)

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1741074/+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 1947579] Re: GNOME Shell integration doesn't work with snap version of Firefox

[Olivier Tilloy]

*** This bug is a duplicate of bug 1741074 ***
https://bugs.launchpad.net/bugs/1741074

** This bug has been marked a duplicate of bug 1741074
   [snap] chrome-gnome-shell extension fails to detect native host connector

-- 
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/1947579

Title:
  GNOME Shell integration doesn't work with snap version of Firefox

Status in chrome-gnome-shell package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in snap package in Ubuntu:
  New

Bug description:
  In Ubuntu 21.10, the default installation has been switched from the
  version provided by APT, to the version provided by snap. Users that
  upgrade from Ubuntu 21.04 to 21.10 will be migrated to the snap
  version of Firefox.

  In the snap version of Firefox, it is impossible to install extensions
  from https://extensions.gnome.org . This error message is displayed:

  > Although GNOME Shell integration extension is running, native host
  connector is not detected. Refer documentation for instructions about
  installing connector.

  Installing chrome-gnome-shell does not fix this issue.

  I'm not sure where to file this bug report exactly, but I thought I
  would file it here.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: chrome-gnome-shell 10.1-5
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 12:51:26 2021
  InstallationDate: Installed on 2021-10-16 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: chrome-gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrome-gnome-shell/+bug/1947579/+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 1947597] Re: Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[rhi]

Additional info: If you log out from the Gnome session (you have to know
by heart where to click because there is no text) and log in again,
everything works again. So it's some kind of temporary screen
corruption.

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

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-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..0a.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  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:53:12 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] 
[1458:37c2]
  InstallationDate: Installed on 2021-10-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947597/+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 1947597] Re: Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[rhi]

** Attachment added: "Screenshot of both screens after unlocking (Gnome desktop 
on right screen, the three dots are from the dock)"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947597/+attachment/5533881/+files/Bildschirmfoto%20von%202021-10-18%2015-59-48.png

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

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-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..0a.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  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:53:12 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] 
[1458:37c2]
  InstallationDate: Installed on 2021-10-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947597/+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 1947597] Re: Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[rhi]

Hardware: NVIDIA GeForce RTX 2070, two screens

Attached: screenshots of screen corruption (photo of unlock screen,
screenshot of Gnome UI after unlocking)

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

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-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..0a.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  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:53:12 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] 
[1458:37c2]
  InstallationDate: Installed on 2021-10-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947597/+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 1947597] Re: Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[rhi]

** Attachment added: "Photo of unlock screen after standby ("Ric i" should be 
"Ricki")"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947597/+attachment/5533870/+files/20211018_155933.jpg

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

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-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..0a.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  470.74  Mon Sep 13 23:09:15 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 15:53:12 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] 
[1458:37c2]
  InstallationDate: Installed on 2021-10-15 (3 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947597/+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 1947597] [NEW] Fonts and texts (including Gnome UI) are gone after coming back from Standby (nvidia + Wayland)

[rhi]

Public bug reported:

Steps to reproduce:

1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
2. Log into Gnome with Wayland.
3. Let the PC go into standby.
4. Wake it up again.
5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

(New windows seem to be OK.)

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-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..0a.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  470.74  Mon Sep 13 23:09:15 
UTC 2021
 GCC version:
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 18 15:53:12 2021
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2070] [1458:37c2]
InstallationDate: Installed on 2021-10-15 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=8be6166d-02d4-49e8-a8f7-57020b69fdb6 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F32
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS ULTRA
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570 AORUS ULTRA
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
nvidia-settings:
 ERROR: Unable to find display on any available system
 
 
 ERROR: Unable to find display on any available system
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug corruption impish ubuntu wayland-session

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

Title:
  Fonts and texts (including Gnome UI) are gone after coming back from
  Standby (nvidia + Wayland)

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Perform a clean Ubuntu 21.10 install with nvidia drivers.
  2. Log into Gnome with Wayland.
  3. Let the PC go into standby.
  4. Wake it up again.
  5. All fonts, texts, icons are almost completely gone, including the unlock 
password dialog and the Gnome UI after unlocking.

  (New windows seem to be OK.)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-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..0a.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: 

[Desktop-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)

[Rolf Leggewie]

There is no need for an SRU.  The problem does not affect focal as such. This 
is only an issue when moving from gir1.2-signon-1.0 to 
gir1.2-signon-2.0 which will only occur in groovy2hirsute and focal2jammy.  The 
Replaces-line can be dropped in jammy+1.

** Changed in: libsignon-glib (Ubuntu)
   Status: Incomplete => In Progress

** Summary changed:

- gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)
+ gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute 
and Focal2Jammy)

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

Title:
  gir1.2-signon-2.0 needs to declare replace on older releases
  (Groovy2Hirsute and Focal2Jammy)

Status in libsignon-glib package in Ubuntu:
  In Progress

Bug description:
  gir1.2-signon-1.0 from groovy
  gir1.2-signon-2.0 from hirsute

  above two packages ship the same file /usr/lib/python3/dist-
  packages/gi/overrides/Signon.py without specifying how to resolve the
  conflict.

  Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', 
which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5
  Errors were encountered while processing:
   /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Probably needs a conflicts/replaces dependency added to the newer
  hirsute package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side

[Leon White]

Just posting to update that this still occurs for me in Ubuntu Impish
21.10 (which ships with Mutter 40.5), looks like the fix will arrive in
the next major version of Mutter?

-- 
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/1882291

Title:
  Gnome Shell clock is truncated/corrupt on the right side

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  When clock changes value, it doesn't displaying time properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1882291/+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 1863801] Re: [snap] After deleting the cache, chromium crashes when file picker is called to upload files or folders

[Roman Valov]

I have encountered a similar issue on downgrade of snap package and workaround 
does work.
Previously had chromium 94 installed. Due to issues with top-bar rendering 
downgraded chromium to version 93. Got issues with any attempt to 
upload/download file. Running:

rm ~/snap/chromium/current/.last_revision

fixed the issue

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

Title:
  [snap] After deleting the cache, chromium crashes when file picker is
  called to upload files or folders

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  First noted today, the snap version of Chromium will crash while
  trying to upload files or folders. I've noted this on my personal
  filespace at my email provider, with Google Drive and Apple's iCloud.
  This is on a freshly booted system and I have logged out and back in
  again but I continue to reproduce the crash each time.

  To reproduce
  
  Log on to Google drive: https://drive.google.com/drive/my-drive
  Click on the 'New' button
  Click on either 'File upload' or 'Folder upload'
  Chromium crashes immediately. The file/folder picker isn't displayed.

  I've verified that Google Chrome and Firefox can upload files to
  Google Drive. I don't see this problem when using Xubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.87-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAdZRUCAQAAACoVAQSlNB544gywoldRnycKUFS/zwDRwLMAlQCBgIGKgQCBSgEBAjqAGHE4LUBYLEUACSUhAAAe/wAwMDAwMDAwMQogICAg/QA4Sx5TDwAKICAgICAg/ABFRjIyMGEKICAgICAgAGI=
   modes: 1920x1080 1680x1050 1280x1024 1280x1024 1280x1024 1440x900 1280x960 
1280x800 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wANrsQVACgXAQSVIhN4Au8FkFRSkyklUFQBAQEBAQEBAQEBAQEBAQEBXjWAlnA4FEAsHCQAWMEQAAAY/gBOMTU2SEdFLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTU2SEdFLUVBQgogAB0=
   modes: 1920x1080
  Date: Tue Feb 18 20:49:46 2020
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext473G   17G   53G  24% /home
   tmpfs  tmpfs  3.9G   22M  3.9G   1% /dev/shm
   /dev/sda2  ext473G   17G   53G  24% /home
  InstallationDate: Installed on 2019-05-17 (277 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  MachineType: Novatech N350DW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=35cc812a-75e8-4a5a-83d0-bd336006d2f6 ro quiet splash vt.handoff=7
  Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] 
failed with exit code 1: error: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.100 
(3f00c26d457663a424865bbef1179f72eec1b9fe-refs/branch-heads/3987@{#864})
  Snap.ChromiumVersion: Chromium 80.0.3987.100 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to focal on 2019-11-08 (101 days ago)
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N350DW
  dmi.board.vendor: Novatech
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/10/2017:svnNovatech:pnN350DW:pvrNotApplicable:rvnNovatech:rnN350DW:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N350DW
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Novatech

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863801/+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 1947587] [NEW] Context (right click) menu does not appear on dual-monitor setup when dock is active on all screens

[Michael K]

Public bug reported:

I have a dual monitor setup, primary monitor on the left, secondary
monitor on the right, exactly lined up, on Wayland, Intel graphics
drivers, Ubuntu 21.10 (but issue was already present in 21.04)

I have Ubuntu Dock enabled on all monitors, on the left side of the
screen (which is default) and symbol size 28 (but this size does not
seem to matter).

Independent from the running program, when I try to bring up the context
(right click) menu close to the right side of the left screen, the
context menu will not show up.

I disabled the "dock on all monitors" and _then_ the context menu will
show up, but weirdly on the right monitor stuck to the left side of the
screen - even if the context menu gladly will right-align when not too
close to the border of the screen.

Now the dock and the weird context menu behaviour seem to overlap
somehow and the context menu will not show up at all.

Sounds similar to this:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1783

and while searching I found this:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930567
which sounds very similar or might be even the same.


I will try in X11 and report if the issue is there as well.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.5-1ubuntu2
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: Mon Oct 18 14:38:50 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-06-15 (489 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 40.5-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to impish on 2021-10-15 (2 days ago)

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


** Tags: amd64 apport-bug impish wayland-session

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

Title:
  Context (right click) menu does not appear on dual-monitor setup when
  dock is active on all screens

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup, primary monitor on the left, secondary
  monitor on the right, exactly lined up, on Wayland, Intel graphics
  drivers, Ubuntu 21.10 (but issue was already present in 21.04)

  I have Ubuntu Dock enabled on all monitors, on the left side of the
  screen (which is default) and symbol size 28 (but this size does not
  seem to matter).

  Independent from the running program, when I try to bring up the
  context (right click) menu close to the right side of the left screen,
  the context menu will not show up.

  I disabled the "dock on all monitors" and _then_ the context menu will
  show up, but weirdly on the right monitor stuck to the left side of
  the screen - even if the context menu gladly will right-align when not
  too close to the border of the screen.

  Now the dock and the weird context menu behaviour seem to overlap
  somehow and the context menu will not show up at all.

  Sounds similar to this:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/1783

  and while searching I found this:
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930567
  which sounds very similar or might be even the same.

  
  I will try in X11 and report if the issue is there as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  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: Mon Oct 18 14:38:50 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-15 (489 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-15 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947587/+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 1916640] Re: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed

[Dominique Breton]

I removed xorg-modulepath-fix, and my script works. I don' t know exactly if 
the "xorg-modulepath-fix" will be useful when upgrading kernel, but for now 
everything seems fine !
Many thanks

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

Title:
  Nvidia 340.108 fails to install with kernels 5.11.x - new patches
  needeed

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  As usual I have opened this (no more) new bug report...

  As ALWAYS happened in the past, EVERY TWO MONTHS new patches are
  needed for old Nvidia 340.108 drivers, that is, with each release of a
  new kernel...

  Nvidia 340.108 fails to install with kernels 5.11.x - new patches
  needeed

  Just to inform develepers that a new patch for Nvidia 340.108 and
  kernel 5.11 is not yet available here:

  
https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/

  Anyway thanks for your great contribution to community and hope you
  publish new patched drivers without having to always report the same
  bug...

  Good day to all the developers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+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 1947579] [NEW] GNOME Shell integration doesn't work with snap version of Firefox

[David D Lowe]

Public bug reported:

In Ubuntu 21.10, the default installation has been switched from the
version provided by APT, to the version provided by snap. Users that
upgrade from Ubuntu 21.04 to 21.10 will be migrated to the snap version
of Firefox.

In the snap version of Firefox, it is impossible to install extensions
from https://extensions.gnome.org . This error message is displayed:

> Although GNOME Shell integration extension is running, native host
connector is not detected. Refer documentation for instructions about
installing connector.

Installing chrome-gnome-shell does not fix this issue.

I'm not sure where to file this bug report exactly, but I thought I
would file it here.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: chrome-gnome-shell 10.1-5
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 18 12:51:26 2021
InstallationDate: Installed on 2021-10-16 (2 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
SourcePackage: chrome-gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: firefox (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: snap (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

** Also affects: firefox (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: snap (Ubuntu)
   Importance: Undecided
   Status: 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/1947579

Title:
  GNOME Shell integration doesn't work with snap version of Firefox

Status in chrome-gnome-shell package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in snap package in Ubuntu:
  New

Bug description:
  In Ubuntu 21.10, the default installation has been switched from the
  version provided by APT, to the version provided by snap. Users that
  upgrade from Ubuntu 21.04 to 21.10 will be migrated to the snap
  version of Firefox.

  In the snap version of Firefox, it is impossible to install extensions
  from https://extensions.gnome.org . This error message is displayed:

  > Although GNOME Shell integration extension is running, native host
  connector is not detected. Refer documentation for instructions about
  installing connector.

  Installing chrome-gnome-shell does not fix this issue.

  I'm not sure where to file this bug report exactly, but I thought I
  would file it here.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: chrome-gnome-shell 10.1-5
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 12:51:26 2021
  InstallationDate: Installed on 2021-10-16 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: chrome-gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrome-gnome-shell/+bug/1947579/+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 1947519] Re: Unless gedit is installed, "Appearance" causes control center to crash

[Gunnar Hjalmarsson]

Pushed this commit:

https://salsa.debian.org/gnome-team/gnome-control-
center/-/commit/f685f0a6

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => In Progress

** Changed in: gnome-control-center (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Unless gedit is installed, "Appearance" causes control center to crash

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 21.10. Gedit not installed from deb (I use a Flatpak version).

  Steps to reproduce:

  - sudo apt remove gedit
  - sudo apt autoremove
  - gnome-control-center ubuntu

  Expected: control center opens with Appearance tab shown
  Experienced: nothing happens, log in terminal:

  (gnome-control-center:27462): GLib-GIO-ERROR **: 22:03:20.416:
  Settings schema 'org.gnome.gedit.preferences.editor' is not installed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 17 21:57:23 2021
  InstallationDate: Installed on 2021-06-30 (109 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-15 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947519/+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 1947519] Re: Unless gedit is installed, "Appearance" causes control center to crash

[Gunnar Hjalmarsson]

For the record: Using gedit's schema was introduced recently through
this upload:

https://launchpad.net/ubuntu/+source/gnome-control-
center/1:40.0-1ubuntu4

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

Title:
  Unless gedit is installed, "Appearance" causes control center to crash

Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 21.10. Gedit not installed from deb (I use a Flatpak version).

  Steps to reproduce:

  - sudo apt remove gedit
  - sudo apt autoremove
  - gnome-control-center ubuntu

  Expected: control center opens with Appearance tab shown
  Experienced: nothing happens, log in terminal:

  (gnome-control-center:27462): GLib-GIO-ERROR **: 22:03:20.416:
  Settings schema 'org.gnome.gedit.preferences.editor' is not installed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 17 21:57:23 2021
  InstallationDate: Installed on 2021-06-30 (109 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-15 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947519/+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 1947519] Re: Unless gedit is installed, "Appearance" causes control center to crash

[Gunnar Hjalmarsson]

On 2021-10-18 11:34, Daniel van Vugt wrote:
> Handling missing schemas without crashing is still possible, just
> not elegant, in the gsettings API.

I see. OTOH I suppose we want the UI to work as expected, not only
prevent the crash.

So without changing the patch, it looks to me as if letting g-c-c depend
on gedit-common is a reasonable step. With your blessing I could commit
that change.

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

Title:
  Unless gedit is installed, "Appearance" causes control center to crash

Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 21.10. Gedit not installed from deb (I use a Flatpak version).

  Steps to reproduce:

  - sudo apt remove gedit
  - sudo apt autoremove
  - gnome-control-center ubuntu

  Expected: control center opens with Appearance tab shown
  Experienced: nothing happens, log in terminal:

  (gnome-control-center:27462): GLib-GIO-ERROR **: 22:03:20.416:
  Settings schema 'org.gnome.gedit.preferences.editor' is not installed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 17 21:57:23 2021
  InstallationDate: Installed on 2021-06-30 (109 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-15 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947519/+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 1916640] Re: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed

[Dominique Breton]

Hi
I finally managed to have working 20.04.3 kernel 5.11 with nvidia 340.108 with 
your help, thank you!
I try to ask you something!
With kernel 5.08, I had a script for getting 3D Vision enabled (option stereo 
from "0" to "10"), but with 5.11, and the changes made, the script is no more 
working:

#!/bin/sh
sudo -s 

[Desktop-packages] [Bug 1930937] Re: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop

[Shivani Lalit Changela]

Hi,

I have tried the below steps i.e

1. Install Ubuntu 20.04
2. Enable the universe repository by #sudo add-apt-repository universe (I 
noticed that this was already
enabled)
3. Install cuda drivers using the --no-install-recommendations options i.e apt 
install -y --no-install- 
   recommends cuda
4. Reboot

With this, I do not see the GUI loading.
Can you please help us with the recommended fix for the same? Any thoughts on 
the above method tried?

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

Title:
  SRU: Default dependency resolution in Focal pulls in full GNOME
  Desktop

Status in screen-resolution-extra package in Ubuntu:
  Triaged
Status in screen-resolution-extra source package in Focal:
  Confirmed
Status in screen-resolution-extra source package in Groovy:
  Fix Committed
Status in screen-resolution-extra source package in Hirsute:
  Confirmed

Bug description:
  In Bionic, screen-resolution-extra has a dependency on
  policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a
  dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent.
  As a result, when install screen-resolution-extra (e.g. as a
  dependency of nvidia-settings) on a system that doesn't already have
  GNOME or another polkit auth agent installed, the default dependency
  resolution pulls in a full GNOME desktop in Focal, while it does not
  do so under the same circumstances in Bionic. This can be worked
  around by explicitly installing policykit-1-gnome (or another package
  which provides the polkit-1-auth-agent virtual package), but it would
  be nice to not pull in GNOME by default on a system that doesn't
  already have it.

  [Impact]

  * Installing the nvidia-settings package causes gnome-shell to be
  installed. This is less than ideal on servers.

  [Fix]

  * Moving policykit-1-gnome ahead as the first of the polkit
  dependencies will solve the problem.

  [Test Case]

  * Install screen-resolution-extra from proposed on a system where no
  polkit-1-auth-agent provider is installed, and check that gnome-shell
  is not installed as a dependency.

  [Regression Risk]
  Low, as the change will still allow the dependency to be satisfied.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded

[Daniel van Vugt]

"Report problem..." creates a new bug, as you should for each .crash
file.

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

Title:
  Nvidia 340 Xorg driver is installed but not loaded

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  I tried both nouveau and nvidia-340 drivers. It used to work at least
  by the latter one in Xubuntu 18.04, even with HWE kernel

  When using the nvidia-340 driver:
  $ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200
  default connected 1920x1200+0+0 0mm x 0mm
     1920x1200 77.00*

  A device is connected in HDMI and xrand does not even list the
  connector. When using nouveau, HDMI is listed but it shows as
  disconnected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Oct 13 16:27:00 2021
  DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2019-05-08 (888 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  nvidia-settings:
   ERROR: Unable to load info from any available system

   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+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 1947519] Re: Unless gedit is installed, "Appearance" causes control center to crash

[Gunnar Hjalmarsson]

On 2021-10-18 11:46, Piotr Mitana wrote:
> Actually gedit-common triggers gedit install as well:

Yes, but you can uninstall gedit afterwards. Or:

sudo apt install --no-install-recommends gedit-common

> Still, isn't it a bit weird, that changing the wallpaper requires a
> particular text editor to be installed? Would it be too complicated
> to make the gnome-control-center independent of the gedit's schema?

It's not for the wallpaper stuff, but for the Dock stuff below that.

Can't tell how difficult it would be to change it to not use gedit's
schema.

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

Title:
  Unless gedit is installed, "Appearance" causes control center to crash

Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 21.10. Gedit not installed from deb (I use a Flatpak version).

  Steps to reproduce:

  - sudo apt remove gedit
  - sudo apt autoremove
  - gnome-control-center ubuntu

  Expected: control center opens with Appearance tab shown
  Experienced: nothing happens, log in terminal:

  (gnome-control-center:27462): GLib-GIO-ERROR **: 22:03:20.416:
  Settings schema 'org.gnome.gedit.preferences.editor' is not installed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 17 21:57:23 2021
  InstallationDate: Installed on 2021-06-30 (109 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-15 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947519/+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 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded

[Jarno Suni]

What does the "Report problem..." button in the dialog do, then if I
have to use command line to report the crash files?

I see "sudo nvidia-xconfig" generates some basic /etc/X11/xorg.conf
file.

Regardless, I noted the following:

If I log out from the Xfce session back to the LightDM greeter the HDMI
output is used, too. And if I thereafter log in back to my session, the
HDMI output works there, too. I wonder why it does not work right after
the first login after boot?

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

Title:
  Nvidia 340 Xorg driver is installed but not loaded

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  I tried both nouveau and nvidia-340 drivers. It used to work at least
  by the latter one in Xubuntu 18.04, even with HWE kernel

  When using the nvidia-340 driver:
  $ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200
  default connected 1920x1200+0+0 0mm x 0mm
     1920x1200 77.00*

  A device is connected in HDMI and xrand does not even list the
  connector. When using nouveau, HDMI is listed but it shows as
  disconnected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Oct 13 16:27:00 2021
  DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2019-05-08 (888 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  nvidia-settings:
   ERROR: Unable to load info from any available system

   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+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 1947519] Re: Unless gedit is installed, "Appearance" causes control center to crash

[Piotr Mitana]

Actually gedit-common triggers gedit install as well:


```
The following additional packages will be installed:
  gedit gir1.2-gtksource-4 gir1.2-peas-1.0 libgtksourceview-4-0 
libgtksourceview-4-common libpeas-1.0-0 libpeas-common python3-gi-cairo
Sugerowane pakiety:
  gedit-plugins
Zostaną zainstalowane następujące NOWE pakiety:
  gedit gedit-common gir1.2-gtksource-4 gir1.2-peas-1.0 libgtksourceview-4-0 
libgtksourceview-4-common libpeas-1.0-0 libpeas-common python3-gi-cairo
```

Still, isn't it a bit weird, that changing the wallpaper requires a
particular text editor to be installed? Would it be too complicated to
make the gnome-control-center independent of the gedit's schema?

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

Title:
  Unless gedit is installed, "Appearance" causes control center to crash

Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 21.10. Gedit not installed from deb (I use a Flatpak version).

  Steps to reproduce:

  - sudo apt remove gedit
  - sudo apt autoremove
  - gnome-control-center ubuntu

  Expected: control center opens with Appearance tab shown
  Experienced: nothing happens, log in terminal:

  (gnome-control-center:27462): GLib-GIO-ERROR **: 22:03:20.416:
  Settings schema 'org.gnome.gedit.preferences.editor' is not installed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 17 21:57:23 2021
  InstallationDate: Installed on 2021-06-30 (109 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-15 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947519/+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 1947569] [NEW] gedit doesn't save last cursor postion after upgrade to ubuntu 21.10

[Ajay chaturvedi]

Public bug reported:

I have been using ubuntu 21.04 where I would open a text file with cursor at 
the last viewed position. However post upgrade to ubuntu 21.10 the cursor sits 
at the top of the file every time a text file is opened.
My system specs are 

Operating System: Ubuntu 21.10
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-19-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
-
AjayC

** Affects: gedit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: impish

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

Title:
  gedit doesn't save last cursor postion after upgrade to ubuntu 21.10

Status in gedit package in Ubuntu:
  New

Bug description:
  I have been using ubuntu 21.04 where I would open a text file with cursor at 
the last viewed position. However post upgrade to ubuntu 21.10 the cursor sits 
at the top of the file every time a text file is opened.
  My system specs are 
  
  Operating System: Ubuntu 21.10
  KDE Plasma Version: 5.22.5
  KDE Frameworks Version: 5.86.0
  Qt Version: 5.15.2
  Kernel Version: 5.13.0-19-generic (64-bit)
  Graphics Platform: X11
  Processors: 4 × Intel® Core™ i5-8250U CPU @ 1.60GHz
  Memory: 7.6 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics 620
  -
  AjayC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1947569/+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 1947519] Re: Unless gedit is installed, "Appearance" causes control center to crash

[Daniel van Vugt]

Handling missing schemas without crashing is still possible, just not
elegant, in the gsettings API.

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

Title:
  Unless gedit is installed, "Appearance" causes control center to crash

Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 21.10. Gedit not installed from deb (I use a Flatpak version).

  Steps to reproduce:

  - sudo apt remove gedit
  - sudo apt autoremove
  - gnome-control-center ubuntu

  Expected: control center opens with Appearance tab shown
  Experienced: nothing happens, log in terminal:

  (gnome-control-center:27462): GLib-GIO-ERROR **: 22:03:20.416:
  Settings schema 'org.gnome.gedit.preferences.editor' is not installed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 17 21:57:23 2021
  InstallationDate: Installed on 2021-06-30 (109 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-15 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947519/+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 1946610] Re: Settings won't open after update

[Gunnar Hjalmarsson]

*** This bug is a duplicate of bug 1947519 ***
https://bugs.launchpad.net/bugs/1947519

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

** This bug has been marked a duplicate of bug 1947519
   Unless gedit is installed, "Appearance" causes control center to crash

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

Title:
  Settings won't open after update

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  After a recent update in 21.10, I noticed the Settings app refuses to
  launch.

  (gnome-control-center:9800): GLib-GIO-ERROR **: 17:58:26.797: Settings schema 
'org.gnome.gedit.preferences.editor' is not installed
  Trace/breakpoint trap (core dumped)

  System:

  Ubuntu 21.10
  Gnome version: 40.5
  Arch: amd64

  (idk if this is a securtiy bug)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1946610/+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 1947519] Re: Unless gedit is installed, "Appearance" causes control center to crash

[Gunnar Hjalmarsson]

This is due to Allow-tweaking-some-settings-for-Ubuntu-Dock.patch.
Making g-c-c depend on gedit-common is one way to fix it. (AFAIU gedit
itself does not need to be installed.)

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

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

Title:
  Unless gedit is installed, "Appearance" causes control center to crash

Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 21.10. Gedit not installed from deb (I use a Flatpak version).

  Steps to reproduce:

  - sudo apt remove gedit
  - sudo apt autoremove
  - gnome-control-center ubuntu

  Expected: control center opens with Appearance tab shown
  Experienced: nothing happens, log in terminal:

  (gnome-control-center:27462): GLib-GIO-ERROR **: 22:03:20.416:
  Settings schema 'org.gnome.gedit.preferences.editor' is not installed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-control-center 1:40.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 17 21:57:23 2021
  InstallationDate: Installed on 2021-06-30 (109 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to impish on 2021-10-15 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947519/+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 1947467] Re: GNOME 40 wayland-session exiting fullscreen doesn't restore original size & position

[Daniel van Vugt]

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1973
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1973

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1973
   Importance: Unknown
   Status: Unknown

-- 
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/1947467

Title:
  GNOME 40 wayland-session exiting fullscreen doesn't restore original
  size & position

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Switching applications between normal and fullscreen got slower and also it 
won't remember position and size of the window on exiting fullscreen compared 
to gnome 3.x.
  I can also confirm this on a 20.04 installation with gnome 40 installed, that 
this is a degradation for gnome-shell 40 on wayland sessions. Xorg session is 
working fine.

  I've tested this with
  - firefox (F11 to enter/exit fullscreen)
  - YouTube videos
  - eog

  On going to fullscreen it often looses focus, and on exit the window
  just gets resized to the full monitor resolution.

  
  Rolling back my 20.04 machine to gnome 3.36 will make this work again under 
wayland.
  Considered that gnome 40 is the default for 21.10 and also wayland is the 
default, I hope this get's investigated and a fix is found before 20.04 is EOL.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 21:23:23 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1947467/+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 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

[Daniel Calcoen]

There is a similar bug follow up at
https://bugzilla.mozilla.org/show_bug.cgi?id=1734791

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346/+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 1947185] Re: Conky does not initially display in Wayland sessions

[Bug Watch Updater]

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

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

Title:
  Conky does not initially display in Wayland sessions

Status in Conky:
  New
Status in conky package in Ubuntu:
  Confirmed
Status in xwayland package in Ubuntu:
  Confirmed

Bug description:
  Starting Ubuntu with wayland does not initially display the .conkyrc
  file. Only after a change in that file, conky restarts the display and
  .conkyrc is displayed. Conky has been started according to the system
  monitor. I doubled the time before starting conky, but that did not
  help.

  If I change the display to xorg, .conkyrc displays directly as
  expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libwayland-bin (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 14 12:58:20 2021
  DistUpgraded: 2021-10-14 11:46:37,562 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2021-10-09 (4 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_57vi20@/vmlinuz-5.13.0-19-generic 
root=ZFS=rpool/ROOT/ubuntu_57vi20 ro quiet splash vt.handoff=1
  SourcePackage: wayland
  UpgradeStatus: Upgraded to impish on 2021-10-14 (0 days ago)
  dmi.bios.date: 03/12/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.50
  dmi.board.name: B450M-HDV R4.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.50:bd03/12/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/conky/+bug/1947185/+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 1947194] Re: When using Wayland in 21.04, the display often never wakes up after lock

[Daniel van Vugt]

Please also check for crashes using these steps:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

-- 
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/1947194

Title:
  When using Wayland in 21.04, the display often never wakes up after
  lock

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using Wayland in 21.04, the display often never wakes up after
  lock up. Also, on boot up, desktop icons and most favorites on dash
  are not displayed, even though desktop icons are enabled. I can get
  them to show up only by re-enabling desktop icons. The workaround now
  is to disable Wayland, and the original xorg server works fine. The
  display driver is:

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  The monitor is an HP 22cwa running of of a displayport interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 14 14:32:26 2021
  DistUpgraded: 2021-07-28 16:05:54,589 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:047e]
  InstallationDate: Installed on 2018-12-04 (1044 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. OptiPlex 990
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-07-28 (77 days ago)
  dmi.bios.date: 11/24/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/24/2011:br4.6:svnDellInc.:pnOptiPlex990:pvr01:sku:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+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 1947467] Re: GNOME 40 wayland-session exiting fullscreen doesn't restore original size & position

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4705
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4705

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4705
   Importance: Unknown
   Status: Unknown

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

** Tags added: regression-release

-- 
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/1947467

Title:
  GNOME 40 wayland-session exiting fullscreen doesn't restore original
  size & position

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Switching applications between normal and fullscreen got slower and also it 
won't remember position and size of the window on exiting fullscreen compared 
to gnome 3.x.
  I can also confirm this on a 20.04 installation with gnome 40 installed, that 
this is a degradation for gnome-shell 40 on wayland sessions. Xorg session is 
working fine.

  I've tested this with
  - firefox (F11 to enter/exit fullscreen)
  - YouTube videos
  - eog

  On going to fullscreen it often looses focus, and on exit the window
  just gets resized to the full monitor resolution.

  
  Rolling back my 20.04 machine to gnome 3.36 will make this work again under 
wayland.
  Considered that gnome 40 is the default for 21.10 and also wayland is the 
default, I hope this get's investigated and a fix is found before 20.04 is EOL.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 21:23:23 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1947467/+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 494462] Re: Network manager connection stage icons incomplete, suggestion attached

[Adolfo Jayme]

** Project changed: openoffice.org-human-icons => ubuntu

** No longer affects: ubuntu

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

Title:
  Network manager connection stage icons incomplete, suggestion attached

Status in Humanity:
  Fix Released
Status in humanity-icon-theme package in Ubuntu:
  Fix Released

Bug description:
  When it's connecting, network manager shows three animation stages
  representing three different stages of handshaking. Currently, the
  Humanity theme uses the same animation for all stages, thus throwing
  away information that could be useful for the user.

  Attached is a small modification of the Humanity-Dark nm-applet icons
  that try to solve this issue. Basically, it's the current animation
  for the first stage, addition of a small circle for the second and
  filling of such circle for the third. It's inspired by Karl Lattimer's
  Tango-style icons for network manager [1].

  Making non-dark icons would be trivial. Please let me know what you
  think.

  [1] http://www.mail-archive.com/networkmanager-
  l...@gnome.org/msg10869.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/humanity/+bug/494462/+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 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded

[Daniel van Vugt]

I would try this on the non-working system:

  sudo nvidia-xconfig

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

Title:
  Nvidia 340 Xorg driver is installed but not loaded

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  I tried both nouveau and nvidia-340 drivers. It used to work at least
  by the latter one in Xubuntu 18.04, even with HWE kernel

  When using the nvidia-340 driver:
  $ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200
  default connected 1920x1200+0+0 0mm x 0mm
     1920x1200 77.00*

  A device is connected in HDMI and xrand does not even list the
  connector. When using nouveau, HDMI is listed but it shows as
  disconnected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Oct 13 16:27:00 2021
  DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2019-05-08 (888 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  nvidia-settings:
   ERROR: Unable to load info from any available system

   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+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 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded

[Daniel van Vugt]

Please use the 'ubuntu-bug' tool to report each of those crash files. If
'ubuntu-bug' doesn't work then you can use 'apport-cli'.

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

Title:
  Nvidia 340 Xorg driver is installed but not loaded

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  I tried both nouveau and nvidia-340 drivers. It used to work at least
  by the latter one in Xubuntu 18.04, even with HWE kernel

  When using the nvidia-340 driver:
  $ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200
  default connected 1920x1200+0+0 0mm x 0mm
     1920x1200 77.00*

  A device is connected in HDMI and xrand does not even list the
  connector. When using nouveau, HDMI is listed but it shows as
  disconnected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Oct 13 16:27:00 2021
  DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2019-05-08 (888 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  nvidia-settings:
   ERROR: Unable to load info from any available system

   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+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 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded

[Jarno Suni]

BTW after every boot I see "System program problem detected?" dialog and
every time I choose "Report problem...". I booted today, too.

$ LC_ALL=C ls -l /var/crash/
total 4624
-rw-r- 1 jarnos whoopsie 1416740 Oct 14 11:05 
_usr_bin_xfce4-power-manager.1000.crash
-rw-r- 1 root   whoopsie 3314750 Oct 13 16:03 _usr_lib_xorg_Xorg.0.crash

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

Title:
  Nvidia 340 Xorg driver is installed but not loaded

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  I tried both nouveau and nvidia-340 drivers. It used to work at least
  by the latter one in Xubuntu 18.04, even with HWE kernel

  When using the nvidia-340 driver:
  $ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200
  default connected 1920x1200+0+0 0mm x 0mm
     1920x1200 77.00*

  A device is connected in HDMI and xrand does not even list the
  connector. When using nouveau, HDMI is listed but it shows as
  disconnected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Oct 13 16:27:00 2021
  DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2019-05-08 (888 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  nvidia-settings:
   ERROR: Unable to load info from any available system

   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+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 1947467] Re: GNOME 40 wayland-session exiting fullscreen doesn't restore original size & position

[Launchpad Bug Tracker]

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

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

-- 
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/1947467

Title:
  GNOME 40 wayland-session exiting fullscreen doesn't restore original
  size & position

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Switching applications between normal and fullscreen got slower and also it 
won't remember position and size of the window on exiting fullscreen compared 
to gnome 3.x.
  I can also confirm this on a 20.04 installation with gnome 40 installed, that 
this is a degradation for gnome-shell 40 on wayland sessions. Xorg session is 
working fine.

  I've tested this with
  - firefox (F11 to enter/exit fullscreen)
  - YouTube videos
  - eog

  On going to fullscreen it often looses focus, and on exit the window
  just gets resized to the full monitor resolution.

  
  Rolling back my 20.04 machine to gnome 3.36 will make this work again under 
wayland.
  Considered that gnome 40 is the default for 21.10 and also wayland is the 
default, I hope this get's investigated and a fix is found before 20.04 is EOL.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 21:23:23 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  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/1947467/+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 1947467] Re: GNOME 40 wayland-session exiting fullscreen doesn't restore original size & position

[Daniel van Vugt]

** Summary changed:

- gome 40 wayland-session exiting fullscreen doesn't restore original size & 
position
+ GNOME 40 wayland-session exiting fullscreen doesn't restore original size & 
position

-- 
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/1947467

Title:
  GNOME 40 wayland-session exiting fullscreen doesn't restore original
  size & position

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Switching applications between normal and fullscreen got slower and also it 
won't remember position and size of the window on exiting fullscreen compared 
to gnome 3.x.
  I can also confirm this on a 20.04 installation with gnome 40 installed, that 
this is a degradation for gnome-shell 40 on wayland sessions. Xorg session is 
working fine.

  I've tested this with
  - firefox (F11 to enter/exit fullscreen)
  - YouTube videos
  - eog

  On going to fullscreen it often looses focus, and on exit the window
  just gets resized to the full monitor resolution.

  
  Rolling back my 20.04 machine to gnome 3.36 will make this work again under 
wayland.
  Considered that gnome 40 is the default for 21.10 and also wayland is the 
default, I hope this get's investigated and a fix is found before 20.04 is EOL.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 21:23:23 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  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/1947467/+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 1947545] Re: [nouveau] Ubuntu desktop screen and whole app screen started corrupting the display, I can't see the letters & display properly.

[Daniel van Vugt]

It appears this is a bug in the 'nouveau' driver. In most cases we would
recommend using the proprietary Nvidia driver instead, but for this
particular GPU that requires Nvidia driver version 304 which Ubuntu
doesn't ship anymore (usually because of limited support for particular
kernel versions by Nvidia).

The only suggestions I have are:

  * Use slow software graphics by adding a kernel boot parameter:
'nomodeset'; or

  * Use Ubuntu 16.04 on this machine
(https://releases.ubuntu.com/16.04/), where the nvidia-304 driver is
still supported; or

  * [EXPERT] Install an older kernel like v4.4 and then you should be
able to manually install
https://www.nvidia.com/Download/driverResults.aspx/123709/en-us or

  * Use Windows only.

I suggest the simplest solution for using Ubuntu on this machine is to
install https://releases.ubuntu.com/16.04/

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Summary changed:

- [nouveau] Ubuntu desktop screen and whole app screen started corrupting the 
display, I can't see the letters & display properly.
+ [nouveau] [Nvidia C61] Ubuntu desktop screen and whole app screen started 
corrupting the display, I can't see the letters & display properly.

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

Title:
  [nouveau] [Nvidia C61] Ubuntu desktop screen and whole app screen
  started corrupting the display, I can't see the letters & display
  properly.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (1)Description:   Ubuntu 20.04.3 LTS
 Release:   20.04

  (2)Ubuntu 20.04.3 LTS

  (3)I expected that after dual booting Ubuntu OS will be working
  properly and the display will be amazing.Simultaneously my Windows 10
  OS was working perfectly.

  (4)But what happened is my Ubuntu desktop screen and whole app screen
  started corrupting the display, I cant see the letters & display
  properly.When i am opening the application like Mozilla Firefox,
  terminal window, etc;then there is not corrupting. when I am logging
  into Ubuntu OS the Login Screen also corrupts.

  Please do something about this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 10:06:34 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
  InstallationDate: Installed on 2021-10-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 8086:0808 Intel Corp. USB PnP Sound Device
   Bus 002 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=19032621-4455-41db-85e6-c10e0d5b345e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: M68MT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/15/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68MT-S2:pvr:sku:rvnGigabyteTechnologyCo.,Ltd.:rnM68MT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: M68MT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1947545] Re: Ubuntu desktop screen and whole app screen started corrupting the display, I can't see the letters & display properly.

[Daniel van Vugt]

** Summary changed:

- Actually i had dualbooted ubuntu with windows.From beginning of my usage 
there was so much screen corupted in the OS. I cant able to see the letters 
correctly it was like lot of a hell. I did'nt expected this from ubuntu 
.Simultaneously my Windows 10 OS was working perfectly.PLease do something 
about this issue.
+ Ubuntu desktop screen and whole app screen started corrupting the display, I 
can't see the letters & display properly.

** Tags added: nouveau

** Summary changed:

- Ubuntu desktop screen and whole app screen started corrupting the display, I 
can't see the letters & display properly.
+ [nouveau] Ubuntu desktop screen and whole app screen started corrupting the 
display, I can't see the letters & display properly.

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

Title:
  [nouveau] Ubuntu desktop screen and whole app screen started
  corrupting the display, I can't see the letters & display properly.

Status in xorg package in Ubuntu:
  New

Bug description:
  (1)Description:   Ubuntu 20.04.3 LTS
 Release:   20.04

  (2)Ubuntu 20.04.3 LTS

  (3)I expected that after dual booting Ubuntu OS will be working
  properly and the display will be amazing.Simultaneously my Windows 10
  OS was working perfectly.

  (4)But what happened is my Ubuntu desktop screen and whole app screen
  started corrupting the display, I cant see the letters & display
  properly.When i am opening the application like Mozilla Firefox,
  terminal window, etc;then there is not corrupting. when I am logging
  into Ubuntu OS the Login Screen also corrupts.

  Please do something about this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 10:06:34 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
  InstallationDate: Installed on 2021-10-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 8086:0808 Intel Corp. USB PnP Sound Device
   Bus 002 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=19032621-4455-41db-85e6-c10e0d5b345e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: M68MT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/15/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68MT-S2:pvr:sku:rvnGigabyteTechnologyCo.,Ltd.:rnM68MT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: M68MT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947545/+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 1947476] Re: Clicking the "Trash" entry in the dock shows both Files and Trash icon as open until the dock refreshes

[Daniel van Vugt]

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

-- 
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/1947476

Title:
  Clicking the "Trash" entry in the dock shows both Files and Trash icon
  as open until the dock refreshes

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  If you click the "Trash" icon in the dock, the Trash entry in Files
  opens, but a Files icon also spawns in the dock, and it appears as if
  both the Trash and Files icons associate with the same Trash window in
  Files. This seems to correct itself after 15-30 seconds or whenever
  the dock sees changes.

  (Image of issue attached below)

  ProblemType: Bug
  DistroRelease: 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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 14:14:47 2021
  InstallationDate: Installed on 2021-10-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1947476/+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 1947476] Re: Clicking the "Trash" entry in the dock shows both Files and Trash icon as open until the dock refreshes

[Launchpad Bug Tracker]

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Confirmed

-- 
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/1947476

Title:
  Clicking the "Trash" entry in the dock shows both Files and Trash icon
  as open until the dock refreshes

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  If you click the "Trash" icon in the dock, the Trash entry in Files
  opens, but a Files icon also spawns in the dock, and it appears as if
  both the Trash and Files icons associate with the same Trash window in
  Files. This seems to correct itself after 15-30 seconds or whenever
  the dock sees changes.

  (Image of issue attached below)

  ProblemType: Bug
  DistroRelease: 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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 14:14:47 2021
  InstallationDate: Installed on 2021-10-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1947476/+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