[Desktop-packages] [Bug 1975454] [NEW] Cannot resume after suspend

2022-05-23 Thread fcole90
Public bug reported:

For some weeks I notice that my laptop cannot resume after suspend. When
I try to resume it, instead of the usual password prompt, I'm greeted by
a black screen with the following text:

```
Bluetooth hcio: Timed out waiting for suspend events
Bluetooth hcio: Suspend timeout bit: 6
Bluetooth hcio: Suspend notifier action (3) failed: -110
```
(There might be typos, I retyped it from a photo)

Then, I don't seem able to do anything, not even change virtual
terminal. So I need to reboot and lose my previous session.

I noticed it seemed to happen since 22.04 came out of beta, but the
timing also coincides with me starting using a Bluetooth mouse, so that
might be connected.

Let me know if you need more information or digging into the logs

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.129.06  Thu May 12 
22:52:02 UTC 2022
 GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon May 23 08:44:30 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed
 nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed
 virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
 virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 
[VGA controller])
   Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905]
   Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905]
InstallationDate: Installed on 2020-04-03 (779 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
MachineType: Dell Inc. XPS 15 7590
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 0VYV0G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905:
dmi.product.family: XPS
dmi.product.name: XPS 15 7590
dmi.product.sku: 0905
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze jammy ubuntu

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

Title:
  Cannot resume after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  For some weeks I notice that my laptop cannot resume after suspend.
  When I try to resume it, instead of the usual password prompt, I'm
  greeted by a black screen with the following text:

  ```
  Bluetooth hcio: Timed out waiting for suspend events
  Bluetooth hcio: Suspend timeout bit: 6
  Bluetooth hcio: Suspend notifier action (3) failed: -110
  ```
  (There might be typos, I retyped it from a photo)

  Then, I don't seem able to do anything, not even change virtual
  terminal. So I need to reboot and lose my previous session.

  I

[Desktop-packages] [Bug 1974427] Re: window redraw wrong size when plug in hdmi

2022-05-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1972151 ***
https://bugs.launchpad.net/bugs/1972151

Sounds like bug 1972151.

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** This bug has been marked a duplicate of bug 1972151
   App window starts overlapping two (vertical) monitors (under the panel of 
the bottom monitor)

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

Title:
  window redraw wrong size when plug in hdmi

Status in mutter package in Ubuntu:
  New

Bug description:
  If I have a window open on the primary display (laptop) and plug in an
  HDMI monitor (secondary) the window (primary) redraws without
  accounting for the top status bar.

  In other words, the window status bar is COVERING UP the top of the
  application window (no min, max close).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 20 06:40:06 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:38ef]
  InstallationDate: Installed on 2022-05-14 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 81D2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=ff8cc35c-2ad1-4b44-b02e-649148be44fa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2018
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7VCN24WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15ARR
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvr7VCN24WW:bd06/15/2018:br1.24:efr1.24:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:skuLENOVO_MT_81D2_BU_idea_FM_ideapad330-15ARR:
  dmi.product.family: ideapad 330-15ARR
  dmi.product.name: 81D2
  dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR
  dmi.product.version: Lenovo ideapad 330-15ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1974427/+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 1972151] Re: App window starts overlapping two (vertical) monitors (under the panel of the bottom monitor)

2022-05-23 Thread Daniel van Vugt
** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Low

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

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

Title:
  App window starts overlapping two (vertical) monitors (under the panel
  of the bottom monitor)

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

Bug description:
  When opening a file dialog, it's dimensions are not displayed within the 
screen range.
  It happens randomly but frequently.

  Not sure if it's related to multiple displays.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gedit 41.0-3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 09:10:14 2022
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2022-02-03 (94 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1972151/+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 1974471] Re: mouse becomes laggy when fractional scaling is enabled

2022-05-23 Thread Daniel van Vugt
Is this with Xorg fractional scaling? Can you try Wayland?

** Tags added: xrandr-scaling

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

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

Title:
  mouse becomes laggy when fractional scaling is enabled

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Distribution: Ubuntu Budgie 22.04 LTS
  Kernel: 5.15.0-1007-raspi
  Package: libmutter-10-0
  Architecture: arm64
  Version: 42.0-3ubuntu2 5.15.0-1007-raspi

  
  On Ubuntu Budgie 22.04 LTS raspberry PI, turning on fractional scaling causes 
an issue where mouse movement becomes laggy and hard to control. This persists 
even if a reboot is performed after changing scaling settings.

  This was tested on Raspberry PI 4 8GB with 3 different mice. 2 USB wired, and 
one wireless with USB dongle. Same results with 3 mice.
  Disabling fractional scaling immediately solved the problem.

  Same tests were performed on Ubuntu Budgie 22.04 on amd64 laptop, with
  Intel CPU  and Nvidia+Intel GPU. There was no issue with mouse
  performance on amd64 laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libmutter-10-0 42.0-3ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-1007.7-raspi 5.15.35
  Uname: Linux 5.15.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Sat May 21 00:48:09 2022
  ImageMediaBuild: 20210416
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1974471/+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 1974471] Re: mouse becomes laggy when fractional scaling is enabled

2022-05-23 Thread Daniel van Vugt
Also do you mean input becomes obviously broken, or just half speed (bug
1902436)?

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

Title:
  mouse becomes laggy when fractional scaling is enabled

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Distribution: Ubuntu Budgie 22.04 LTS
  Kernel: 5.15.0-1007-raspi
  Package: libmutter-10-0
  Architecture: arm64
  Version: 42.0-3ubuntu2 5.15.0-1007-raspi

  
  On Ubuntu Budgie 22.04 LTS raspberry PI, turning on fractional scaling causes 
an issue where mouse movement becomes laggy and hard to control. This persists 
even if a reboot is performed after changing scaling settings.

  This was tested on Raspberry PI 4 8GB with 3 different mice. 2 USB wired, and 
one wireless with USB dongle. Same results with 3 mice.
  Disabling fractional scaling immediately solved the problem.

  Same tests were performed on Ubuntu Budgie 22.04 on amd64 laptop, with
  Intel CPU  and Nvidia+Intel GPU. There was no issue with mouse
  performance on amd64 laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libmutter-10-0 42.0-3ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-1007.7-raspi 5.15.35
  Uname: Linux 5.15.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Sat May 21 00:48:09 2022
  ImageMediaBuild: 20210416
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1974471/+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 1975371] Re: Plugging / unplugging external monitor rearranges desktop icons differently

2022-05-23 Thread Daniel van Vugt
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
desktop-icons-ng (Ubuntu)

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
   Importance: Undecided => Low

** Tags added: multimonitor

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

Title:
  Plugging / unplugging external monitor rearranges desktop icons
  differently

Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New

Bug description:
  Desktop icons were arranged and looking normally but after unplugging the 
external monitor, they looks like the screenshot.
  When I re-plugged the external monitor again, they were restored to the 
normal view.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat May 21 14:24:12 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-02-03 (106 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1975371/+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 1975369] Re: conky is not visible - Ubuntu 22.04

2022-05-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1947185 ***
https://bugs.launchpad.net/bugs/1947185

Thanks for the bug report. It appears 'conky' is an X11 app but you are
using Wayland. Wayland sessions do not support the 'dock' X11 window
type. You will either need a version of conky that supports Wayland
natively, or a gnome-shell extension to replace it.

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  conky is not visible - Ubuntu 22.04

Status in Ubuntu:
  Invalid

Bug description:
  conky is running from terminal but does not show on the desktop:

  conky: desktop window (800015) is subwindow of root window (96)
  conky: window type - dock
  conky: drawing to create window (0xa02)
  conky: drawing to double buffer

  This is only happening in Ubuntu 22.04!

  conky is visible in Ubuntu 18.04 20.04, Kubuntu 20.04, Kubuntu 22.04,
  and KDE Neon

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 21 03:27:48 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  InstallationDate: Installed on 2022-04-22 (28 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=5c6021ec-5923-467d-b2f9-d0a62f8823b2 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2011
  dmi.bios.release: 18.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd12/07/2011:br18.0:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:sku:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1975369/+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 1972790] Re: Can't connect to hotspot created on ubuntu

2022-05-23 Thread Dustin Utecht
As written in the bug report before i can't connect with "WPA & WPA2 Personal" 
with the message "Failed to connect to the network".
With "WPA3 Personal" i always got the error message that the password is wrong.

After the update "WPA & WPA2 Personal" still don't work (same error
message), but "WPA3 Personal" works now.

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1975400] Re: Unable to change Display resolution to its full capacity

2022-05-23 Thread Daniel van Vugt
Thanks for the bug report. I am guessing this is caused by the kernel
graphics driver. Please run:

  grep . /sys/class/drm/*/modes > modes.txt

and attach the resulting text file here.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  Unable to change Display resolution to its full capacity

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It's showing 'unknown display'.
  Running this 'ubuntu-drivers devices' showed no output.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 22 11:22:50 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4th Generation Core Processor 
Family Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2022-05-21 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Gigabyte Technology Co., Ltd. H81M-S
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=963a4763-1838-41e9-ab01-dff1efefa136 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-S
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/19/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81M-S
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975400/+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 1975454] Re: Cannot resume after suspend

2022-05-23 Thread Daniel van Vugt
Thanks for the bug report. Next time the problem happens, after
rebooting run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.


** Tags added: nvidia

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Cannot resume after suspend

Status in Ubuntu:
  Incomplete

Bug description:
  For some weeks I notice that my laptop cannot resume after suspend.
  When I try to resume it, instead of the usual password prompt, I'm
  greeted by a black screen with the following text:

  ```
  Bluetooth hcio: Timed out waiting for suspend events
  Bluetooth hcio: Suspend timeout bit: 6
  Bluetooth hcio: Suspend notifier action (3) failed: -110
  ```
  (There might be typos, I retyped it from a photo)

  Then, I don't seem able to do anything, not even change virtual
  terminal. So I need to reboot and lose my previous session.

  I noticed it seemed to happen since 22.04 came out of beta, but the
  timing also coincides with me starting using a Bluetooth mouse, so
  that might be connected.

  Let me know if you need more information or digging into the logs

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.129.06  Thu May 12 
22:52:02 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 08:44:30 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed
   nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905]
 Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905]
  InstallationDate: Installed on 2020-04-03 (779 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1975410] Re: Maximized window border under status bar in Wayland / Mutter

2022-05-23 Thread Daniel van Vugt
Please provide a screenshot or photo of the problem. It sounds like bug
1972151.

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

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

Title:
  Maximized window border under status bar in Wayland / Mutter

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Cf. https://gitlab.gnome.org/GNOME/mutter/-/issues/1627

  This is still present in Jammy (as it was in Impish). Were the
  upstream patches included the corresponding builds?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun May 22 12:50:48 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (1724 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2021-04-25T10:10:15.799073

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975410/+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 1974471] Re: mouse becomes laggy when fractional scaling is enabled

2022-05-23 Thread Mauro Gaspari
Daniel,

This is with Xorg fractional scaling on Ubuntu Budgie ARM64. We don't
have Wayland on Budgie DE, but I can flash Ubuntu 22.04 ARM64 on a spare
microSD and test. Give me a few hours and I will follow up on that.

Regarding input, yes I believe same issue as described on
https://bugs.launchpad.net/bugs/1902436 . Mouse movements feel slower
and also delayed around one second from the moment I move my hand to
when I see the cursor moving.

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

Title:
  mouse becomes laggy when fractional scaling is enabled

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Distribution: Ubuntu Budgie 22.04 LTS
  Kernel: 5.15.0-1007-raspi
  Package: libmutter-10-0
  Architecture: arm64
  Version: 42.0-3ubuntu2 5.15.0-1007-raspi

  
  On Ubuntu Budgie 22.04 LTS raspberry PI, turning on fractional scaling causes 
an issue where mouse movement becomes laggy and hard to control. This persists 
even if a reboot is performed after changing scaling settings.

  This was tested on Raspberry PI 4 8GB with 3 different mice. 2 USB wired, and 
one wireless with USB dongle. Same results with 3 mice.
  Disabling fractional scaling immediately solved the problem.

  Same tests were performed on Ubuntu Budgie 22.04 on amd64 laptop, with
  Intel CPU  and Nvidia+Intel GPU. There was no issue with mouse
  performance on amd64 laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libmutter-10-0 42.0-3ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-1007.7-raspi 5.15.35
  Uname: Linux 5.15.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Sat May 21 00:48:09 2022
  ImageMediaBuild: 20210416
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1974471/+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 1975445] Re: Crash back to login screen when connecting external monitor in 22.04 LTS

2022-05-23 Thread Daniel van Vugt
Thanks for the bug report.

Firstly, you are using the (low quality) open source 'nouveau' graphics
driver. It is known to cause such problems so please start by using the
'Additional Drivers' app to install an official Nvidia driver.

After installing the driver and rebooting, if the problem still occurs
then please follow the steps in
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

** Tags added: multimonitor nouveau

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

Title:
  Crash back to login screen when connecting external monitor in 22.04
  LTS

Status in Ubuntu:
  Incomplete

Bug description:
  I upgraded my Ubuntu 20.04 LTS to 22.04 LTS using do-release-upgrade -d 
command on 2022/05/20
  And then my external monitor, who worked well before on 20.04 LTS, was never 
able to connect.
  Everytime I try to connect it, set Joint Displays and press apply on the 
setting panel, the system crashes and goes back to login screen.
  When I switch to Windows on the same computer, external monitor is able to 
connect. Bug only appears on the new 22.04 LTS.

  System info:
  Device: Dell Inc. Precision 7750
  Processor: Intel W-10855M
  Graphics: Intel UHD Graphics P630 / NVIDIA Quadro RTX 3000
  Built-in Display: 1920 X 1080, 60.00 HZ
  External monitor where the bug appears: PHL 230B8Q (1920 X 1200, 59.950 HZ)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 11:42:00 2022
  DistUpgraded: 2022-05-20 18:00:09,901 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9bf6] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:09c4]
   NVIDIA Corporation TU106GLM [Quadro RTX 3000 Mobile / Max-Q] [10de:1f36] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Dell TU106GLM [Quadro RTX 3000 Mobile / Max-Q] [1028:09c4]
  InstallationDate: Installed on 2021-06-18 (338 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Precision 7750
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=4f247525-7971-47a5-b2b2-8f3a0282b3c7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to jammy on 2022-05-20 (2 days ago)
  dmi.bios.date: 03/30/2022
  dmi.bios.release: 1.14
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.2
  dmi.board.name: 0KT0MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.2:bd03/30/2022:br1.14:svnDellInc.:pnPrecision7750:pvr:rvnDellInc.:rn0KT0MH:rvrA01:cvnDellInc.:ct10:cvr:sku09C4:
  dmi.product.family: Precision
  dmi.product.name: Precision 7750
  dmi.product.sku: 09C4
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1975445/+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 1972080] Re: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)

2022-05-23 Thread Daniel van Vugt
Please tell us what you see when you run the above commands.

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

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

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

Title:
  GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white
  square (missing adwaita-icon-theme-full)

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

Bug description:
  Do not think this is hardware dependent, but I'm using an HPE
  MicroServer Gen10 Plus.

  I installed the server edition of 22.04.  Post-Installation, I added
  some desktop environments.  After logging in, these are working fine.

  However on the gdm login entry and password entry screens I had no
  mouse pointer icon.  A semi-opaque white square tracked the mouse
  movements.  My reading suggested that gdm defaults to using the cursor
  icon theme provided by the adwaita-icon-theme package.  I discovered
  this theme comes in two sizes, a basic, smaller package installed
  automatically and a larger "full" package.

  $ apt list 'adwaita-icon-theme*'
  Listing... Done
  adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic]
  adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed]
  $

  The gdm mouse pointer appears and disappears with installation and
  removal of the package "adwaita-icon-theme-full".  Either gdm's
  dependencies should include the "full" package OR the appropriate
  mouse pointer icons should be moved from the full to the basic
  "adwaita-icon-theme" package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1972080/+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 1975408] Re: Performance is much worse than expected (Normal friendly behaviors)

2022-05-23 Thread Daniel van Vugt
Thanks for the bug report.

You seem to have gotten your graphics packages from the 'oibaf' PPA.
That is known to be frequently broken and is UNSUPPORTED.

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  Performance is much worse than expected (Normal friendly behaviors)

Status in Ubuntu:
  Invalid

Bug description:
  Operating System: Ubuntu 22.04
  Life cycle: LTS
  Architecture: AMD64
  Kernel version (uname -a): 5.15.0-30-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 22 12:10:30 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: sysdig/0.27.1, 5.15.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:17f4]
  MachineType: Hewlett-Packard HP ProBook 4540s
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic 
root=UUID=cf164159-2e29-4cee-aef2-f8d16c319f1a ro snapd_recovery_mode snap_core 
quiet splash crashkernel=512M-:192M vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2019
  dmi.bios.release: 15.104
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.68
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 88.33
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.68:bd04/11/2019:br15.104:efr88.33:svnHewlett-Packard:pnHPProBook4540s:pvrA1008C11:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.21:cvnHewlett-Packard:ct10:cvr:skuB7A48EA#ABV:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 4540s
  dmi.product.sku: B7A48EA#ABV
  dmi.product.version: A1008C11
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.14.1+22.04.20211217-0ubuntu2
  version.libdrm2: libdrm2 2.4.110+git2205140500.3f266e~oibaf~j
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2~git2205160600.3c0f34~oibaf~j
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2~git2205170600.fffafa~oibaf~j
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1975408/+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 1974471] Re: mouse becomes laggy when fractional scaling is enabled

2022-05-23 Thread Daniel van Vugt
Hmm one second delay is a bigger and different issue to bug 1902436.

I've never seen anyone use Xorg fractional scaling on Raspberry Pi
before but I would expect it to be super slow. Because Xorg fractional
scaling effectively requires 4x the GPU power and it's only a Raspberry
Pi... I would suggest just not using fractional scaling in Xorg sessions
on low-power hardware.

You may find GNOME Shell in a Wayland session performs much better if
fractional scaling is a requirement.

** Tags added: raspi

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Low

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

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  mouse becomes laggy when fractional scaling is enabled

Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  Distribution: Ubuntu Budgie 22.04 LTS
  Kernel: 5.15.0-1007-raspi
  Package: libmutter-10-0
  Architecture: arm64
  Version: 42.0-3ubuntu2 5.15.0-1007-raspi

  
  On Ubuntu Budgie 22.04 LTS raspberry PI, turning on fractional scaling causes 
an issue where mouse movement becomes laggy and hard to control. This persists 
even if a reboot is performed after changing scaling settings.

  This was tested on Raspberry PI 4 8GB with 3 different mice. 2 USB wired, and 
one wireless with USB dongle. Same results with 3 mice.
  Disabling fractional scaling immediately solved the problem.

  Same tests were performed on Ubuntu Budgie 22.04 on amd64 laptop, with
  Intel CPU  and Nvidia+Intel GPU. There was no issue with mouse
  performance on amd64 laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libmutter-10-0 42.0-3ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-1007.7-raspi 5.15.35
  Uname: Linux 5.15.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Sat May 21 00:48:09 2022
  ImageMediaBuild: 20210416
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1974471/+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 1965208] Re: Ubuntu dock is visible too early during the login animation in Xorg sessions

2022-05-23 Thread Daniel van Vugt
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

** Changed in: gnome-shell (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Triaged

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

Title:
  Ubuntu dock is visible too early during the login animation in Xorg
  sessions

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  Ubuntu dock is visible too early during the login animation in Xorg
  sessions.

  It appears immediately, disappears, then appears again.

  This also explains why the login animation is so stuttery in Xorg
  compared to Wayland.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965208/+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 1968390] Re: JS ERROR: TypeError: this.window_container is null

2022-05-23 Thread Daniel van Vugt
Now tracking in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5512

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5512
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5512

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5512
   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/1968390

Title:
  JS ERROR: TypeError: this.window_container is null

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

Bug description:
  Ubuntu 22.04 Development

  A 3 finger touchpad swipe up/down gesture with 1 application open
  outputs a lot of JS errors and stacks to the journal. This issue may
  be the same or related to
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 but
  the output is somewhat different when you have more than 1 app open.

  This also happens with all extensions disabled, does not happen in
  Fedora 36.

  To reproduce

  1. login and open terminal and watch the journal
  2. perform the 3 finger swipe up gesture until the app grid displays then 
swipe down to go back to the desktop.
  3. See journal
  4. If nothing happens try opening an app, closing it and try again.

  
  Apr 08 21:18:49 x1c gnome-shell[21675]: JS ERROR: TypeError: 
this.window_container is null
  
hideOverlay@resource:///org/gnome/shell/ui/windowPreview.js:373:9
  
vfunc_leave_event/this._idleHideOverlayId<@resource:///org/gnome/shell/ui/windowPreview.js:571:26

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968390/+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 1975460] [NEW] iwlwifi cannot load firmware, wifi card does not work Intel Corporation Wireless 7260

2022-05-23 Thread SZ
Public bug reported:

With ubuntu 20.04, it worked.
After upgrading to 22.04, stopped working.
I have 2 pcs. of HP zbook G2, they both have the same error after upgrade.
Can't work!!
Booting back to old linux kernel 5.13.x wifi works again!
No windows installed, not a dual boot.

I have other older hp laptop which has a different wifi card, that works
well with the new kernel.

Please fix this bug.
Thank you!

Full ubuntu-bug report has been sent also.

Error msg:
[   23.227024] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0 
7260-17.ucode op_mode iwlmvm
[   23.309876] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless N 
7260, REV=0x144
[   28.356103] iwlwifi :3d:00.0: Failed to load firmware chunk!
[   28.356123] iwlwifi :3d:00.0: iwlwifi transaction failed, dumping 
registers
[   28.356140] iwlwifi :3d:00.0: iwlwifi device config registers:
[   28.356415] iwlwifi :3d:00.0: : 08b18086 00100406 0280006b 
0010 d014   
[   28.356437] iwlwifi :3d:00.0: 0020:    
c0608086  00c8  0100
[   28.356459] iwlwifi :3d:00.0: 0040: 00020010 10008ec0 00130c10 
0106ec11 101100ca   
[   28.356480] iwlwifi :3d:00.0: 0060:  00080812 0405 
 00010001   
[   28.356523] iwlwifi :3d:00.0: 0080:    
    
[   28.356566] iwlwifi :3d:00.0: 00a0:    
    
[   28.356607] iwlwifi :3d:00.0: 00c0:   c823d001 
0d00 00814005 fee003f8  
[   28.356649] iwlwifi :3d:00.0: 00e0:    
    
[   28.356691] iwlwifi :3d:00.0: 0100: 14010001 4000  
00462031 2000 2000 000e 
[   28.356732] iwlwifi :3d:00.0: 0120:    
    
[   28.356774] iwlwifi :3d:00.0: 0140: 14c10003 ff64778d e8b1fcff 
15410018 08460846 0001000b 0141cafe 00f01e1f
[   28.356815] iwlwifi :3d:00.0: iwlwifi device memory mapped registers:
[   28.356891] iwlwifi :3d:00.0: : 00489204 8040 2000 
0800    
[   28.356933] iwlwifi :3d:00.0: 0020: 0009 080003c5 0144 
 8000 803a 80008040 00080046
[   28.356978] iwlwifi :3d:00.0: iwlwifi device AER capability structure:
[   28.357034] iwlwifi :3d:00.0: : 14010001 4000  
00462031 2000 2000 000e 
[   28.357075] iwlwifi :3d:00.0: 0020:   
[   28.357100] iwlwifi :3d:00.0: iwlwifi parent port (:3c:01.0) config 
registers:
[   28.357274] iwlwifi :3c:01.0: : 240412d8 00180407 06040005 
00010010   003d3d3c 01f1
[   28.357316] iwlwifi :3c:01.0: 0020: d010d010 0001fff1  
  0040  0002010a
[   28.357357] iwlwifi :3c:01.0: 0040: ffc34c01 0008  
00816405 fee002d8   
[   28.357399] iwlwifi :3c:01.0: 0060:  0034b009 04001060 
04000800 8000 0a730100 76b50080 21901d27
[   28.357440] iwlwifi :3c:01.0: 0080: 000f  3308 
00790010 8000 116b 000f0022 
[   28.357482] iwlwifi :3c:01.0: 00a0:    
 c00d 240412d8  
[   28.357524] iwlwifi :3c:01.0: 00c0: 00620010 8001 0010 
01203c11 10110042  014803c0 
[   28.357565] iwlwifi :3c:01.0: 00e0:  00040800 0400 
 00010042   
[   28.357607] iwlwifi :3c:01.0: 0100: 14010001   
00062011  2000 00a0 
[   28.357648] iwlwifi :3c:01.0: 0120:    
    
[   28.357690] iwlwifi :3c:01.0: 0140: 20c10002 0800  
 047f0009 8001  
[   28.357739] iwlwifi :3c:01.0: 0160:    
    
[   28.357780] iwlwifi :3c:01.0: 0180:    
    
[   28.357821] iwlwifi :3c:01.0: 01a0:    
    
[   28.357861] iwlwifi :3c:01.0: 01c0:    
    
[   28.357902] iwlwifi :3c:01.0: 01e0:    
    
[   28.357943] iwlwifi :3c:01.0: 0200:   
[   28.357969] iwlwifi :3d:00.0: Could not load the [0] uCode section
[   28.358001] iwlwifi :3d:00.0: Fai

[Desktop-packages] [Bug 1975460] Re: iwlwifi cannot load firmware, wifi card does not work Intel Corporation Wireless 7260

2022-05-23 Thread Daniel van Vugt
** Tags added: jammy

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Also affects: linux-firmware (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/1975460

Title:
  iwlwifi cannot load firmware, wifi card does not work Intel
  Corporation Wireless 7260

Status in linux package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  With ubuntu 20.04, it worked.
  After upgrading to 22.04, stopped working.
  I have 2 pcs. of HP zbook G2, they both have the same error after upgrade.
  Can't work!!
  Booting back to old linux kernel 5.13.x wifi works again!
  No windows installed, not a dual boot.

  I have other older hp laptop which has a different wifi card, that
  works well with the new kernel.

  Please fix this bug.
  Thank you!

  Full ubuntu-bug report has been sent also.

  Error msg:
  [   23.227024] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0 
7260-17.ucode op_mode iwlmvm
  [   23.309876] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless N 
7260, REV=0x144
  [   28.356103] iwlwifi :3d:00.0: Failed to load firmware chunk!
  [   28.356123] iwlwifi :3d:00.0: iwlwifi transaction failed, dumping 
registers
  [   28.356140] iwlwifi :3d:00.0: iwlwifi device config registers:
  [   28.356415] iwlwifi :3d:00.0: : 08b18086 00100406 0280006b 
0010 d014   
  [   28.356437] iwlwifi :3d:00.0: 0020:    
c0608086  00c8  0100
  [   28.356459] iwlwifi :3d:00.0: 0040: 00020010 10008ec0 00130c10 
0106ec11 101100ca   
  [   28.356480] iwlwifi :3d:00.0: 0060:  00080812 0405 
 00010001   
  [   28.356523] iwlwifi :3d:00.0: 0080:    
    
  [   28.356566] iwlwifi :3d:00.0: 00a0:    
    
  [   28.356607] iwlwifi :3d:00.0: 00c0:   c823d001 
0d00 00814005 fee003f8  
  [   28.356649] iwlwifi :3d:00.0: 00e0:    
    
  [   28.356691] iwlwifi :3d:00.0: 0100: 14010001 4000  
00462031 2000 2000 000e 
  [   28.356732] iwlwifi :3d:00.0: 0120:    
    
  [   28.356774] iwlwifi :3d:00.0: 0140: 14c10003 ff64778d e8b1fcff 
15410018 08460846 0001000b 0141cafe 00f01e1f
  [   28.356815] iwlwifi :3d:00.0: iwlwifi device memory mapped registers:
  [   28.356891] iwlwifi :3d:00.0: : 00489204 8040 2000 
0800    
  [   28.356933] iwlwifi :3d:00.0: 0020: 0009 080003c5 0144 
 8000 803a 80008040 00080046
  [   28.356978] iwlwifi :3d:00.0: iwlwifi device AER capability structure:
  [   28.357034] iwlwifi :3d:00.0: : 14010001 4000  
00462031 2000 2000 000e 
  [   28.357075] iwlwifi :3d:00.0: 0020:   
  [   28.357100] iwlwifi :3d:00.0: iwlwifi parent port (:3c:01.0) 
config registers:
  [   28.357274] iwlwifi :3c:01.0: : 240412d8 00180407 06040005 
00010010   003d3d3c 01f1
  [   28.357316] iwlwifi :3c:01.0: 0020: d010d010 0001fff1  
  0040  0002010a
  [   28.357357] iwlwifi :3c:01.0: 0040: ffc34c01 0008  
00816405 fee002d8   
  [   28.357399] iwlwifi :3c:01.0: 0060:  0034b009 04001060 
04000800 8000 0a730100 76b50080 21901d27
  [   28.357440] iwlwifi :3c:01.0: 0080: 000f  3308 
00790010 8000 116b 000f0022 
  [   28.357482] iwlwifi :3c:01.0: 00a0:    
 c00d 240412d8  
  [   28.357524] iwlwifi :3c:01.0: 00c0: 00620010 8001 0010 
01203c11 10110042  014803c0 
  [   28.357565] iwlwifi :3c:01.0: 00e0:  00040800 0400 
 00010042   
  [   28.357607] iwlwifi :3c:01.0: 0100: 14010001   
00062011  2000 00a0 
  [   28.357648] iwlwifi :3c:01.0: 0120:    
    
  [   28.357690] iwlwifi :3c:01.0: 0140: 20c10002 0800  
 047f0009 8001  
  [   28.357739] iwlwifi :3c:01.0: 0160:    
    
  [   28.357780] iwlwifi :3c:01.0: 0180:  0

[Desktop-packages] [Bug 1974471] Re: mouse becomes laggy when fractional scaling is enabled

2022-05-23 Thread Mauro Gaspari
Daniel,

Thank you. This actually makes a lot of sense. Also, even if there is no fix, 
at least we will know what to tell our users if and when issues like this are 
reported.
I am still going to test on Ubuntu on both Gnome and Wayland, and report if 
there is any difference, so we can keep it all for the record under same bug 
report.

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

Title:
  mouse becomes laggy when fractional scaling is enabled

Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  Distribution: Ubuntu Budgie 22.04 LTS
  Kernel: 5.15.0-1007-raspi
  Package: libmutter-10-0
  Architecture: arm64
  Version: 42.0-3ubuntu2 5.15.0-1007-raspi

  
  On Ubuntu Budgie 22.04 LTS raspberry PI, turning on fractional scaling causes 
an issue where mouse movement becomes laggy and hard to control. This persists 
even if a reboot is performed after changing scaling settings.

  This was tested on Raspberry PI 4 8GB with 3 different mice. 2 USB wired, and 
one wireless with USB dongle. Same results with 3 mice.
  Disabling fractional scaling immediately solved the problem.

  Same tests were performed on Ubuntu Budgie 22.04 on amd64 laptop, with
  Intel CPU  and Nvidia+Intel GPU. There was no issue with mouse
  performance on amd64 laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libmutter-10-0 42.0-3ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-1007.7-raspi 5.15.35
  Uname: Linux 5.15.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Sat May 21 00:48:09 2022
  ImageMediaBuild: 20210416
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1974471/+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 1968390] Re: JS ERROR: TypeError: this.window_container is null

2022-05-23 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => 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/1968390

Title:
  JS ERROR: TypeError: this.window_container is null

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 Development

  A 3 finger touchpad swipe up/down gesture with 1 application open
  outputs a lot of JS errors and stacks to the journal. This issue may
  be the same or related to
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 but
  the output is somewhat different when you have more than 1 app open.

  This also happens with all extensions disabled, does not happen in
  Fedora 36.

  To reproduce

  1. login and open terminal and watch the journal
  2. perform the 3 finger swipe up gesture until the app grid displays then 
swipe down to go back to the desktop.
  3. See journal
  4. If nothing happens try opening an app, closing it and try again.

  
  Apr 08 21:18:49 x1c gnome-shell[21675]: JS ERROR: TypeError: 
this.window_container is null
  
hideOverlay@resource:///org/gnome/shell/ui/windowPreview.js:373:9
  
vfunc_leave_event/this._idleHideOverlayId<@resource:///org/gnome/shell/ui/windowPreview.js:571:26

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968390/+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 1975459] [NEW] Prints blank pages

2022-05-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When printing using a wireless printer from Ubuntu it only prints blank
pages. Occasinally, but not reproducable, it prints 1 job after boot and
then fails. Printing from ipad and android devies to the same printer
always works.

This problem has persisted for several years, different versions of
ubuntu on different networks and computers and several different
printers.

The attached file contains the cups debug log.

The machine was booted 24 hours earlier. 
The first print job succeeded, the second failed with printer busy. 
I then tried to log out and back in, and only got blank pages. When that 
happens, the printer will continue to print blank pages until the tray is empty 
or removed.

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


** Tags: bot-comment
-- 
Prints blank pages
https://bugs.launchpad.net/bugs/1975459
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to cups 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 1975459] Re: Prints blank pages

2022-05-23 Thread Baard
** Package changed: ubuntu => cups (Ubuntu)

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

Title:
  Prints blank pages

Status in cups package in Ubuntu:
  New

Bug description:
  When printing using a wireless printer from Ubuntu it only prints
  blank pages. Occasinally, but not reproducable, it prints 1 job after
  boot and then fails. Printing from ipad and android devies to the same
  printer always works.

  This problem has persisted for several years, different versions of
  ubuntu on different networks and computers and several different
  printers.

  The attached file contains the cups debug log.

  The machine was booted 24 hours earlier. 
  The first print job succeeded, the second failed with printer busy. 
  I then tried to log out and back in, and only got blank pages. When that 
happens, the printer will continue to print blank pages until the tray is empty 
or removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1975459/+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 1975435] Re: cannot choose item from right-click menu with touch

2022-05-23 Thread Sebastien Bacher
Thank you for your bug report. Is that in list or icon view? In which
version was it working?

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

Title:
  cannot choose item from right-click menu with touch

Status in nautilus package in Ubuntu:
  New

Bug description:
  1. open nautilus
  2. navigate to a directory with a non-directory file
  3. long hold your finger on the file
  4. try to choose something from the menu

  The menu disappears but the chosen menu item is not activated, and
  nothing happens.

  This is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 22 17:38:28 2022
  InstallationDate: Installed on 2021-10-12 (222 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (30 days ago)
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1975435/+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 1968907] Re: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed

2022-05-23 Thread KILA Fabrice
Hi,

I have the same failure in syslog.

I have upgrade to 22.04, and thats two week i am unable to use my
computer. Does the fix it txo uses an older version of ubuntu ?

When my computer display the login screen, if i click on my login name
or anirher place in my screen. The computer display a black screen and
go back to the login screen.

I have try all the solution from the web and never help me.

Thanks for your help.

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

Title:
  GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error
  == NULL' failed

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I see the following errors in the system logs:

  # journalctl | grep gnome-session-binary
  Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: 
GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' 
failed
  Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: 
GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' 
failed
  Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: 
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
  Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: 
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-session-bin 42.0-1ubuntu2
  Uname: Linux 5.17.2-051702-generic x86_64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Apr 13 19:48:49 2022
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


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

2022-05-23 Thread Gaber Terseglav
Thanks for the support.

Will change the grub config and reboot later today. I had to add
nomodeset parameter a while ago using command line access, because
computer didn't boot into graphic environment (I found this workaround
on the internet). I will report how it goes.

Also adding the screenshot for additional drivers screen.

** Attachment added: "AdditionalDrivers.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973397/+attachment/5592224/+files/AdditionalDrivers.png

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

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

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

  echo $XDG_SESSION_TYPE
  x11

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

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


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


[Desktop-packages] [Bug 1975459] Re: Prints blank pages

2022-05-23 Thread Till Kamppeter
The bug itself is that the implicitclass CUPS backend used by cups-
browsed is not able to determine the correct parameters to generate
Apple Raster from the PDF input. Your printer needs 600 dpi and for some
reason 1200 dpi got sent.

In cups-filters 2.x (to appear in Ubuntu 22.10) this is fixed.

For the time being, please create an explicit print queue for your
printer (instead of letting cups-browsed auto-creating one):

lpadmin -p Brother -E -v 'ipp://Brother%20HL-L2357DW._ipp._tcp.local/'
-m everywhere

Try to print on this queue. Does it work?

** Changed in: cups (Ubuntu)
   Status: New => Incomplete

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

Title:
  Prints blank pages

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  When printing using a wireless printer from Ubuntu it only prints
  blank pages. Occasinally, but not reproducable, it prints 1 job after
  boot and then fails. Printing from ipad and android devies to the same
  printer always works.

  This problem has persisted for several years, different versions of
  ubuntu on different networks and computers and several different
  printers.

  The attached file contains the cups debug log.

  The machine was booted 24 hours earlier. 
  The first print job succeeded, the second failed with printer busy. 
  I then tried to log out and back in, and only got blank pages. When that 
happens, the printer will continue to print blank pages until the tray is empty 
or removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1975459/+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 1968907] Re: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed

2022-05-23 Thread Sebastien Bacher
Thanks, it sounds similar to https://gitlab.gnome.org/GNOME/gnome-
session/-/issues/105

** Bug watch added: gitlab.gnome.org/GNOME/gnome-session/-/issues #105
   https://gitlab.gnome.org/GNOME/gnome-session/-/issues/105

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided => Low

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

Title:
  GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error
  == NULL' failed

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I see the following errors in the system logs:

  # journalctl | grep gnome-session-binary
  Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: 
GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' 
failed
  Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: 
GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' 
failed
  Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: 
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
  Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: 
g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-session-bin 42.0-1ubuntu2
  Uname: Linux 5.17.2-051702-generic x86_64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Apr 13 19:48:49 2022
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1968907/+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 1972790] Re: Can't connect to hotspot created on ubuntu

2022-05-23 Thread Sebastien Bacher
Thanks, it means at least we can get the WPA3 case out of this report
and focus on the other issue

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1962630] Re: Video playback crashes with SIGSEGV in KernelDll_AllocateStates (intel-media-driver)

2022-05-23 Thread Sebastien Bacher
** Tags added: desktop-lts-wishlist rls-jj-incoming

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

Title:
  Video playback crashes with SIGSEGV in KernelDll_AllocateStates
  (intel-media-driver)

Status in Libva:
  New
Status in intel-media-driver package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/a09f9aa6132a1f12a9e44103be3ca0a859abfa2d

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libgstreamer1.0-0 1.20.0-1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 27 15:56:18 2022
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-10 (1177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7fd4c2239ccf:cmpl   $0x1,(%rbx)
   PC (0x7fd4c2239ccf) ok
   source "$0x1" ok
   destination "(%rbx)" (0x7fd57824ec90) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
   () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
   () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
   () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
   () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  Title: totem crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/libva/+bug/1962630/+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 1975434] Re: Nautilus refuses to save files in directories I open by double clicking!

2022-05-23 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1971516 ***
https://bugs.launchpad.net/bugs/1971516

** This bug has been marked a duplicate of bug 1971516
   Entering fileselector subdir disables the save button until filename is 
edited

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

Title:
  Nautilus refuses to save files in directories I open by double
  clicking!

Status in nautilus package in Ubuntu:
  New

Bug description:
  Hi, When I try to save anything, if I navigate into the folder via double 
clicking, the save button becomes disabled . If I make a folder inside of it 
and then come back, the save button becomes active again. This makes no sense.
  I've also attached the video to this bug report.

  My neofetch output:

  OS: Ubuntu 22.04 LTS x86_64 
  Kernel: 5.15.0-27-generic 
  Uptime: 9 hours, 41 mins 
  Packages: 1983 (dpkg), 14 (snap) 
  Shell: bash 5.1.16 
  Resolution: 1440x900, 1920x1080 
  DE: GNOME 42.0 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru-viridian-dark [GTK2/3] 
  Icons: Yaru-viridian [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-8700K (12) @ 4.700GHz 
  GPU: NVIDIA GeForce GTX 1060 3GB 
  Memory: 3550MiB / 15936MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1975434/+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 1975407] Re: pulseaudio is getting crashed

2022-05-23 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

** Changed in: pulseaudio (Ubuntu)
   Status: New => Incomplete

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

Title:
  pulseaudio is getting crashed

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Operating System: Ubuntu 22.04
  Life cycle: LTS
  Architecture: AMD64
  Kernel version (uname -a): 5.15.0-30-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johnm  3822 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 22 12:08:58 2022
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2019
  dmi.bios.release: 15.104
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.68
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 88.33
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.68:bd04/11/2019:br15.104:efr88.33:svnHewlett-Packard:pnHPProBook4540s:pvrA1008C11:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.21:cvnHewlett-Packard:ct10:cvr:skuB7A48EA#ABV:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 4540s
  dmi.product.sku: B7A48EA#ABV
  dmi.product.version: A1008C11
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2022-01-28T22:42:20.933634

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1975407/+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 1975425] Re: Using a Wacom Intuos 4, middle-click and secondary-click are sometimes swapped

2022-05-23 Thread Sebastien Bacher
Thank you for your bug report, if that's working with some software and
not other then it might be a toolkit issue. Do you get the problem with
any GTK software?

** Changed in: libwacom (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Using a Wacom Intuos 4, middle-click and secondary-click are sometimes
  swapped

Status in libwacom package in Ubuntu:
  New

Bug description:
  Using a Wacom Intuos 4:
  In Files and text-editors like Geany, secondary-clicks and middle-clicks are 
swapped.  Dragging is not possible.
  On a web browser, and in Blender 3D, secondary-clicks, middle-clicks and 
dragging work normally.
  Trying to go into the settings to swap middle-clicks and secondary-clicks so 
that they work properly, causes them to be swapped in other apps where they 
would normally work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libwacom-common 2.2.0-1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 22 10:59:16 2022
  Dependencies:
   
  DistUpgraded: 2022-04-28 11:06:16,704 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.5, 5.15.0-27-generic, x86_64: installed
   v4l2loopback/0.12.5, 5.15.0-30-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU117 [GeForce GTX 1650] 
[1458:4016]
  InstallationDate: Installed on 2020-04-03 (779 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3H
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=104a5f38-4e8e-43b9-9a28-665dad0b019d ro quiet splash vt.handoff=7
  SourcePackage: libwacom
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (23 days ago)
  dmi.bios.date: 09/19/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F14
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF14:bd09/19/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3H
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1975425/+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 1975480] [NEW] package firefox 100.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-05-23 Thread Chiu Szeto
Public bug reported:

Not sure. Upgrade to 22.04 succeeded with errors. May be due to docker.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 100.0.2+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181
Uname: Linux 5.4.0-110-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  chiu  33661 F pulseaudio
BuildID: 20220519220738
CasperMD5CheckResult: unknown
Channel: Unavailable
Date: Mon May 23 06:11:18 2022
ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-03-21 (1158 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
IpRoute:
 default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.102 metric 600
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2
 apt  2.4.5
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox 100.0.2+build1-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A18
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd04/28/2016:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.sku: 05CB
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package firefox 100.0.2+build1-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  New

Bug description:
  Not sure. Upgrade to 22.04 succeeded with errors. May be due to
  docker.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 100.0.2+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181
  Uname: Linux 5.4.0-110-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chiu  33661 F pulseaudio
  BuildID: 20220519220738
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Mon May 23 06:11:18 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-03-21 (1158 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.102 metric 
600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 100.0.2+build1-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/28/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd04/28/2016:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.sku: 05CB
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/19754

[Desktop-packages] [Bug 1975402] Re: GJS returns wrong session mode

2022-05-23 Thread Sebastien Bacher
Thank you for your bug report. Do you have an example of extension
impacted?

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

Title:
  GJS returns wrong session mode

Status in gjs package in Ubuntu:
  New

Bug description:
  As stated in the documentation
  (https://gjs.guide/extensions/topics/session-modes.html#example-
  usage), when a user is logged in, the Shell is in the `user` mode. I
  checked it on Fedora 36, and that's how it works.

  But in Ubuntu, for some reason, `imports.ui.main.currentMode` returns
  the login name of the current user instead of the `user` constant,
  which breaks extensions that use it.

  ---
  ProblemType: Bug
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  Package: gjs 1.72.0-3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags: jammy
  Uname: Linux 5.15.0-30-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1975402/+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 1971693] Re: Alt+Tab is broken for Java (AWT/Swing) apps in Wayland session

2022-05-23 Thread Dmitry Batrak
I believe, libmutter package (libmutter-10-0 to be exact) should be
upgraded to fix the problem, as mutter binary by itself isn't used by
gnome-shell.

I couldn't upgrade libmutter-10-0 selectively as per
https://wiki.ubuntu.com/Testing/EnableProposed due to some errors. I'm
not experienced enough in Ubuntu package management system to resolve
them.

I can confirm though, that a 'full' upgrade from -proposed does fix the
issue for me.

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

Title:
  Alt+Tab is broken for Java (AWT/Swing) apps in Wayland session

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  When switching to a Java UI application using Alt+Tab, very often 
application's window is raised, but it doesn't get keyboard focus - it stays in 
the previous application, and that application continues to process keyboard 
events. When the problem occurs, hovering mouse over Java app's window gets the 
focus transferred to it.
  This problem only happens in Wayland session, not in X.Org session. It can be 
reproduced in Ubuntu 22.04, but not in 20.04.4 version.

  The problem seems to affect all Java versions - reproduced for
  different OpenJDK builds (8, 11, 17, 18). It can also be observed for
  Java version provided by Ubuntu's 'default-jre' package
  (11.0.15+10-Ubuntu-0ubuntu0.22.04.1).

  Test Case
  -
  1. sudo apt install default-jre
  2. Download the minimal test case app from comment #1
  3. From a terminal run the app
  java Downloads/JTextFieldTest.java
  4. Click on the terminal window (instead of the Java app)
  5. Press Alt-Tab to switch focus back to the Java app
  6. Type a few characters.

  The characters should show in the Java app's text field instead of in
  the terminal window.

  What Could Go Wrong
  ---
  See the master bug for this update at LP: #1972726

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971693/+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 1975402] Re: GJS returns wrong session mode

2022-05-23 Thread Treviño
The value of imports.ui.main.sessionMode.currentMode (ubuntu) is not the
login name, but the name of the ubuntu session.

I'm sorry to say it but the gjs guide is wrong in assuming that's always
the case as further sessions can be added.

However, you can definitely check whether the used session is an user
one by just ensuring:

imports.ui.main.sessionMode.currentMode === 'user' ||
imports.ui.main.sessionMode.parentMode === 'user'

As any custom session that is still an user session will have the
parentMode set.

** Changed in: gjs (Ubuntu)
   Status: New => Won't Fix

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

Title:
  GJS returns wrong session mode

Status in gjs package in Ubuntu:
  Won't Fix

Bug description:
  As stated in the documentation
  (https://gjs.guide/extensions/topics/session-modes.html#example-
  usage), when a user is logged in, the Shell is in the `user` mode. I
  checked it on Fedora 36, and that's how it works.

  But in Ubuntu, for some reason, `imports.ui.main.currentMode` returns
  the login name of the current user instead of the `user` constant,
  which breaks extensions that use it.

  ---
  ProblemType: Bug
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  Package: gjs 1.72.0-3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags: jammy
  Uname: Linux 5.15.0-30-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1975402/+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 1975487] [NEW] zsys not installed during Kinetic ISO install with ZFS option

2022-05-23 Thread Mark Smith
Public bug reported:

After following the instructions at:
http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248685/testcases/1716/results
 
on the 20220523 daily build of Kinetic, I used the command

zsysctl show

and was met with the message:

~$ zsysctl show
Command 'zsysctl' not found, but can be installed with:
sudo apt install zsys

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: zsys (not installed)
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 23 12:33:24 2022
InstallationDate: Installed on 2022-05-23 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220522)
SourcePackage: zsys
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1975487/+attachment/5592259/+files/Screenshot%20from%202022-05-23%2012-39-43.png

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

Title:
  zsys not installed during Kinetic ISO install with ZFS option

Status in zsys package in Ubuntu:
  New

Bug description:
  After following the instructions at:
  
http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248685/testcases/1716/results
 
  on the 20220523 daily build of Kinetic, I used the command

  zsysctl show

  and was met with the message:

  ~$ zsysctl show
  Command 'zsysctl' not found, but can be installed with:
  sudo apt install zsys

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: zsys (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 12:33:24 2022
  InstallationDate: Installed on 2022-05-23 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220522)
  SourcePackage: zsys
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1975487/+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 1975385] Re: connection editor does not preserve ignore-auto-dns=true flag

2022-05-23 Thread Sebastien Bacher
Thank you for your bug report, could you try if that's still an issue
with the current version of Ubuntu?

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => Low

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

Title:
  connection editor does not preserve ignore-auto-dns=true flag

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

Bug description:
  I want to avoid using the DHCP server provided DNS. To achieve this, I
  tried using ignore-auto-dns=true flag in NM configuration. However,
  subsequent editing of the network configuration through the applet
  remove the flag. At the same time the applet does not allow me to
  specify this flag in any way.

  The applet should either preserve flags it does not understand or it
  should know about this flag and let me edit it in the applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager-gnome 1.24.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-41.46-lowlatency 5.13.19
  Uname: Linux 5.13.0-41-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu71.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sat May 21 19:55:35 2022
  ExecutablePath: /usr/bin/nm-connection-editor
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2011-11-13 (3842 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IpRoute:
   default via 192.168.0.1 dev enp6s0 proto dhcp metric 100 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev enp6s0 proto kernel scope link src 192.168.0.71 metric 
100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: Upgraded to impish on 2021-10-15 (218 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2019-03-27T00:07:10.128435
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.32.12  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975385/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04

2022-05-23 Thread Oibaf
Just update your Ubuntu and make sure to have wpasupplicant version
2.10-6ubuntu1.

In a shell you should see:

$ dpkg -l | grep wpasupplicant
ii  wpasupplicant2:2.10-6ubuntu1

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

Title:
  wifi connection on hotspot with wpa enterprise on 22.04

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  With 20.04 I used a wifi connection with a hotspot Telenet with following 
parametres:
  security : WPA2 entreprise
  authentification : tunneled TLS
  no AC certificat drequired
  inner authentication : MSCHAPV2(non EAP)
  user name: my id
  password : my pswd

  with 22.04 it doesn’t work anymore nor with the internal broadcom wifi
  nor with dongles (nor my Dlink 140 nor TP-link WN7200)

  This problem is only present with hotspot requesting an identification
  (user+pswd) awith hotspots without identification everything is OK

  in appendice some infos
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michelvlt   1725 F pulseaudio
   /dev/snd/pcmC0D0p:   michelvlt   1725 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source /etc/network/interfaces.d/*
  InstallationDate: Installed on 2022-04-21 (7 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IpRoute:
   default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 
   10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 
   169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 
   192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 
600
  MachineType: Apple Inc. MacBookPro8,1
  NonfreeKernelModules: wl
  Package: wpa
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 87.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245B3640C91C81
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245B3640C91C81
  dmi.modalias: 
dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro8,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1975459] Re: Prints blank pages

2022-05-23 Thread Baard
Yes, that worked.

Thank you.

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

Title:
  Prints blank pages

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  When printing using a wireless printer from Ubuntu it only prints
  blank pages. Occasinally, but not reproducable, it prints 1 job after
  boot and then fails. Printing from ipad and android devies to the same
  printer always works.

  This problem has persisted for several years, different versions of
  ubuntu on different networks and computers and several different
  printers.

  The attached file contains the cups debug log.

  The machine was booted 24 hours earlier. 
  The first print job succeeded, the second failed with printer busy. 
  I then tried to log out and back in, and only got blank pages. When that 
happens, the printer will continue to print blank pages until the tray is empty 
or removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1975459/+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 1975489] [NEW] Update evince to 42.3

2022-05-23 Thread Jeremy Bicha
Public bug reported:

Impact
--
There is a new upstream release in the GNOME 42 stable series.

I had previously cherry-picked all the code changes from 42.2.

https://gitlab.gnome.org/GNOME/evince/-/blob/gnome-42/NEWS

Test Case
-
Install the update.
Open a variety of files with evince

What Could Go Wrong
---
evince is the default PDF viewer for Ubuntu and Ubuntu Budgie. But Firefox 
could also open PDFs.

evince is part of core GNOME and therefore has a microrelease exception
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

** Affects: evince (Ubuntu)
 Importance: Medium
 Status: Fix Committed

** Affects: evince (Ubuntu Jammy)
 Importance: Medium
 Status: In Progress


** Tags: jammy upgrade-software-version

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

** Changed in: evince (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: evince (Ubuntu Jammy)
   Importance: Undecided => Medium

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

Title:
  Update evince to 42.3

Status in evince package in Ubuntu:
  Fix Committed
Status in evince source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  There is a new upstream release in the GNOME 42 stable series.

  I had previously cherry-picked all the code changes from 42.2.

  https://gitlab.gnome.org/GNOME/evince/-/blob/gnome-42/NEWS

  Test Case
  -
  Install the update.
  Open a variety of files with evince

  What Could Go Wrong
  ---
  evince is the default PDF viewer for Ubuntu and Ubuntu Budgie. But Firefox 
could also open PDFs.

  evince is part of core GNOME and therefore has a microrelease exception
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1975489/+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 1971693] Re: Alt+Tab is broken for Java (AWT/Swing) apps in Wayland session

2022-05-23 Thread trespasserw
Thanks, upgrading `libmutter-10-0` along with a couple of dependencies
did help.

There is weird caret blinking on switching from Terminal to IDEA (as if
the former briefly regains the focus between ultimately relinquish it),
but I can live with it.

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

Title:
  Alt+Tab is broken for Java (AWT/Swing) apps in Wayland session

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  When switching to a Java UI application using Alt+Tab, very often 
application's window is raised, but it doesn't get keyboard focus - it stays in 
the previous application, and that application continues to process keyboard 
events. When the problem occurs, hovering mouse over Java app's window gets the 
focus transferred to it.
  This problem only happens in Wayland session, not in X.Org session. It can be 
reproduced in Ubuntu 22.04, but not in 20.04.4 version.

  The problem seems to affect all Java versions - reproduced for
  different OpenJDK builds (8, 11, 17, 18). It can also be observed for
  Java version provided by Ubuntu's 'default-jre' package
  (11.0.15+10-Ubuntu-0ubuntu0.22.04.1).

  Test Case
  -
  1. sudo apt install default-jre
  2. Download the minimal test case app from comment #1
  3. From a terminal run the app
  java Downloads/JTextFieldTest.java
  4. Click on the terminal window (instead of the Java app)
  5. Press Alt-Tab to switch focus back to the Java app
  6. Type a few characters.

  The characters should show in the Java app's text field instead of in
  the terminal window.

  What Could Go Wrong
  ---
  See the master bug for this update at LP: #1972726

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971693/+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 1975459] Re: Prints blank pages

2022-05-23 Thread Till Kamppeter
Thank you very much.

As this bug can easily get worked around and as it is also fixed in
cups-filters 2.x, I will not provide a fix here. Closing ...

** Changed in: cups (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Prints blank pages

Status in cups package in Ubuntu:
  Won't Fix

Bug description:
  When printing using a wireless printer from Ubuntu it only prints
  blank pages. Occasinally, but not reproducable, it prints 1 job after
  boot and then fails. Printing from ipad and android devies to the same
  printer always works.

  This problem has persisted for several years, different versions of
  ubuntu on different networks and computers and several different
  printers.

  The attached file contains the cups debug log.

  The machine was booted 24 hours earlier. 
  The first print job succeeded, the second failed with printer busy. 
  I then tried to log out and back in, and only got blank pages. When that 
happens, the printer will continue to print blank pages until the tray is empty 
or removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1975459/+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 1975402] Re: GJS returns wrong session mode

2022-05-23 Thread popov895
Now it's clear, thanks! It's strange that it's not in the gjs guide.

Anyway, I've found that it's better to use the
imports.ui.main.sessionMode.isPrimary/isLocked properties for this
purpose.

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

Title:
  GJS returns wrong session mode

Status in gjs package in Ubuntu:
  Won't Fix

Bug description:
  As stated in the documentation
  (https://gjs.guide/extensions/topics/session-modes.html#example-
  usage), when a user is logged in, the Shell is in the `user` mode. I
  checked it on Fedora 36, and that's how it works.

  But in Ubuntu, for some reason, `imports.ui.main.currentMode` returns
  the login name of the current user instead of the `user` constant,
  which breaks extensions that use it.

  ---
  ProblemType: Bug
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  Package: gjs 1.72.0-3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags: jammy
  Uname: Linux 5.15.0-30-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1975402/+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 1875671] Re: wayland: desktop folder missing in Nautilus sidebar

2022-05-23 Thread Santiago Fernández Núñez
As long as I can tell, there isn't any fix released in GTK. The bug I
opened is still, well, open:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1985

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

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

Title:
  wayland: desktop folder missing in Nautilus sidebar

Status in GNOME Shell:
  Unknown
Status in GTK+:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Using Wayland session nautilus home window does not show Desktop folder in 
sidebar while is dispayed using X11 session.
  see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  Uname: Linux 5.7.0-050700rc3-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 17:24:45 2020
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 
852)'
  InstallationDate: Installed on 2020-04-23 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1875671/+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 1975489] Re: Update evince to 42.3

2022-05-23 Thread Jeremy Bicha
** Changed in: evince (Ubuntu Jammy)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

Title:
  Update evince to 42.3

Status in evince package in Ubuntu:
  Fix Committed
Status in evince source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  There is a new upstream release in the GNOME 42 stable series.

  I had previously cherry-picked all the code changes from 42.2.

  https://gitlab.gnome.org/GNOME/evince/-/blob/gnome-42/NEWS

  Test Case
  -
  Install the update.
  Open a variety of files with evince

  What Could Go Wrong
  ---
  evince is the default PDF viewer for Ubuntu and Ubuntu Budgie. But Firefox 
could also open PDFs.

  evince is part of core GNOME and therefore has a microrelease exception
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


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


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

2022-05-23 Thread Gaber Terseglav
Report after removing nomodeset from /etc/default/grub:
* grub update and restart,
* login screen shown,
* gear shown in the lower right corner,
* two options available: 1) Ubuntu 2) Ubuntu on X.org,
* successfull login with first option (Ubuntu) selected,
* echo $XDG_SESSION_TYPE
wayland

All good! This was configuration issue. I had to introduce nomodeset
into grub config, because of some problem on earlier Ubuntu version, but
it works as it should on as-is 22.04 version.

Thanks for all your support!

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

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

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

  echo $XDG_SESSION_TYPE
  x11

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

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


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


[Desktop-packages] [Bug 1975435] Re: cannot choose item from right-click menu with touch

2022-05-23 Thread Krister Swenson
This is in both list and icon view.  It was working before I updated to 22.04 
from 21.10.
I see that you marked this a low importance, but it makes it extremely 
difficult to use the computer, as I have to keep my keyboard nearby and 
reattach it the tablet just to open a file, copy, paste, etc.

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

Title:
  cannot choose item from right-click menu with touch

Status in nautilus package in Ubuntu:
  New

Bug description:
  1. open nautilus
  2. navigate to a directory with a non-directory file
  3. long hold your finger on the file
  4. try to choose something from the menu

  The menu disappears but the chosen menu item is not activated, and
  nothing happens.

  This is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 22 17:38:28 2022
  InstallationDate: Installed on 2021-10-12 (222 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (30 days ago)
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1975435/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

2022-05-23 Thread Dee
still present in 22.04

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in WebKit:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in webkit2gtk source package in Xenial:
  Fix Released
Status in webkit2gtk source package in Yakkety:
  Fix Released
Status in webkit2gtk source package in Zesty:
  Fix Released
Status in webkit2gtk source package in Focal:
  Fix Released
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  Impact
  -
  Users will be unable to log in to a Google account using GNOME Online Account 
which is used by default in Ubuntu GNOME and Ubuntu Budgie.

  Any other browser or service that uses webkit2gtk is similarly broken,
  such as the Epiphany browser.

  The second issue fixed here is that any user who opted in to the new
  YouTube will only get a white screen when they attempt to visit
  YouTube. The new YouTube is still opt-in now but will eventually
  become the default for everyone.

  Test Case
  -
  1. Install the updated webkit2gtk on Ubuntu GNOME.
  2. Restart your computer (this may be necessary because of LP: #1610944)
  3. Log in. Open Settings>Online Accounts. Remove any Google accounts already 
configured. Add your Google account.
  4. Install Evolution if it's not already installed and verify that your Gmail 
account loads.

  Optional, because the beta is closed to new entrants:
  5. Install epiphany-browser
  6. Open the Web app (epiphany-browser) and log in to your Google account.
  7. Visit https://www.google.com/new to make sure that your browser is set to 
use the "new YouTube."
  8. If the new YouTube only shows a white screen, this part of the bug is not 
fixed.

  Regression Potential
  
  The regression potential was limited by only cherry-picking the commits to 
fix these 2 high-profile issues. 2.16.2 is being rolled out to most distros now.

  Other Info
  --
  Fixed in 17.10 Alpha "artful" by updating to 2.16.2

  Original Bug Report
  ---
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I 
cannot add a Google account using Online-Accounts. If I choose to add a new 
Google account in Online Accounts, a window appears where I can enter my Google 
email. After entering my email and pressing the Next button, a window appears 
where I can enter my Google password. After entering the password and pressing 
the Next button, an empty window appears and nothing else happens. I expected 
this to show something useful, and actually add the Google account to my Gnome 
environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04

2022-05-23 Thread VAN LAETHEM
Dear,

my ubuntu is already uptodate and the result of the command is :

$ dpkg -l | grep wpasupplicant
ii  wpasupplicant2:2.10-6ubuntu1
 amd64client support for WPA and WPA2 (IEEE 802.11i)

for the moment I use a 18.04.6 version when i need to be connected to this 
hotspot
(all other recent efi Linux version I have tested present the same problem 
(fedora 35; debian 11.3; freeBSD)  

thanks for your support

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

Title:
  wifi connection on hotspot with wpa enterprise on 22.04

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  With 20.04 I used a wifi connection with a hotspot Telenet with following 
parametres:
  security : WPA2 entreprise
  authentification : tunneled TLS
  no AC certificat drequired
  inner authentication : MSCHAPV2(non EAP)
  user name: my id
  password : my pswd

  with 22.04 it doesn’t work anymore nor with the internal broadcom wifi
  nor with dongles (nor my Dlink 140 nor TP-link WN7200)

  This problem is only present with hotspot requesting an identification
  (user+pswd) awith hotspots without identification everything is OK

  in appendice some infos
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michelvlt   1725 F pulseaudio
   /dev/snd/pcmC0D0p:   michelvlt   1725 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source /etc/network/interfaces.d/*
  InstallationDate: Installed on 2022-04-21 (7 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IpRoute:
   default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 
   10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 
   169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 
   192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 
600
  MachineType: Apple Inc. MacBookPro8,1
  NonfreeKernelModules: wl
  Package: wpa
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 87.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245B3640C91C81
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245B3640C91C81
  dmi.modalias: 
dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro8,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1975435] Re: cannot choose item from right-click menu with touch

2022-05-23 Thread Sebastien Bacher
Bug settings are a bit tricky, touch only configurations represent a low
percentage of the configurations but ineeded it is annoying for those
setup, I'm changing to High

** Changed in: nautilus (Ubuntu)
   Importance: Low => High

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

Title:
  cannot choose item from right-click menu with touch

Status in nautilus package in Ubuntu:
  New

Bug description:
  1. open nautilus
  2. navigate to a directory with a non-directory file
  3. long hold your finger on the file
  4. try to choose something from the menu

  The menu disappears but the chosen menu item is not activated, and
  nothing happens.

  This is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 22 17:38:28 2022
  InstallationDate: Installed on 2021-10-12 (222 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (30 days ago)
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1975435/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04

2022-05-23 Thread Sebastien Bacher
The update on bug #1974428 fixed an issue where only WPA3 compatible
devices would be able to connect to the hotspot,
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6a82dd18,
could you try if the update is improving things for you? bug #1972790 is
another similar report

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

Title:
  wifi connection on hotspot with wpa enterprise on 22.04

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  With 20.04 I used a wifi connection with a hotspot Telenet with following 
parametres:
  security : WPA2 entreprise
  authentification : tunneled TLS
  no AC certificat drequired
  inner authentication : MSCHAPV2(non EAP)
  user name: my id
  password : my pswd

  with 22.04 it doesn’t work anymore nor with the internal broadcom wifi
  nor with dongles (nor my Dlink 140 nor TP-link WN7200)

  This problem is only present with hotspot requesting an identification
  (user+pswd) awith hotspots without identification everything is OK

  in appendice some infos
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michelvlt   1725 F pulseaudio
   /dev/snd/pcmC0D0p:   michelvlt   1725 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source /etc/network/interfaces.d/*
  InstallationDate: Installed on 2022-04-21 (7 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IpRoute:
   default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 
   10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 
   169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 
   192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 
600
  MachineType: Apple Inc. MacBookPro8,1
  NonfreeKernelModules: wl
  Package: wpa
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 87.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245B3640C91C81
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245B3640C91C81
  dmi.modalias: 
dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro8,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1972790] Re: Can't connect to hotspot created on ubuntu

2022-05-23 Thread Sebastien Bacher
** Changed in: wpa (Ubuntu)
   Importance: Undecided => High

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1975430] Re: I can select the Xorg Nouveau server, but not click on "apply"

2022-05-23 Thread Sebastien Bacher
Thanks for the debugging details, retitling and changing the component
according

** Package changed: software-properties (Ubuntu) => ubuntu-drivers-
common (Ubuntu)

** Summary changed:

- I can select the Xorg Nouveau server, but not click on "apply" 
+ kerneldetection except when custom kernel installed

** Summary changed:

- kerneldetection except when custom kernel installed
+ kerneldetection exception when a custom kernel installed

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

Title:
  kerneldetection exception when a custom kernel installed

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  I want to switch back from the nvidia driver to nouveau.

  In the dialog the last row lets me select the Nouveau driver, but the
  "apply" button is inactive and doesnt let me apply the change.

  There is also no message or anything that would allow me to
  understand, why this is the case, and what i could do about it.

  heres also the outout of ubuntu-drivers debug that I learned in anothe
  bug can be important:

  
  === log messages from detection ===
  DEBUG:root:Skipping check for rtl8812au-dkms since it does not depend on 
video abi
  DEBUG:root:Skipping check for open-vm-tools-desktop since it does not depend 
on video abi
  DEBUG:root:Skipping check for rtl8821ce-dkms since it does not depend on 
video abi
  DEBUG:root:Skipping check for bcmwl-kernel-source since it does not depend on 
video abi
  DEBUG:root:Skipping check for oem-qemu-meta since it does not depend on video 
abi
  DEBUG:root:_get_db_name: output
  ID_PCI_CLASS_FROM_DATABASE=Display controller
  ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller
  ID_PCI_INTERFACE_FROM_DATABASE=VGA controller
  ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
  ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q]

  
  DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, 
pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA 
Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]"
  DEBUG:root:_get_db_name: output
  ID_PCI_CLASS_FROM_DATABASE=Display controller
  ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller
  ID_PCI_INTERFACE_FROM_DATABASE=VGA controller
  ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
  ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q]

  
  DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, 
pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA 
Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]"
  DEBUG:root:_get_db_name: output
  ID_PCI_CLASS_FROM_DATABASE=Display controller
  ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller
  ID_PCI_INTERFACE_FROM_DATABASE=VGA controller
  ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
  ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q]

  
  DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, 
pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA 
Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]"
  DEBUG:root:_get_db_name: output
  ID_PCI_CLASS_FROM_DATABASE=Display controller
  ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller
  ID_PCI_INTERFACE_FROM_DATABASE=VGA controller
  ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
  ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q]

  
  DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, 
pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA 
Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]"
  DEBUG:root:_get_db_name: output
  ID_PCI_CLASS_FROM_DATABASE=Display controller
  ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller
  ID_PCI_INTERFACE_FROM_DATABASE=VGA controller
  ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
  ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q]

  
  DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, 
pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA 
Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]"
  DEBUG:root:_get_db_name: output
  ID_PCI_CLASS_FROM_DATABASE=Display controller
  ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller
  ID_PCI_INTERFACE_FROM_DATABASE=VGA controller
  ID_VENDOR_FROM_DATABASE=NVIDIA Corporation
  ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q]

  
  DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, 
pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA 
Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]"
  DEBUG:root:Skipping check for rtl8812au-dkms since it does not depend on 
video abi
  DEBUG:root:Skipping check for open-vm-tools-desktop since it does not depend 
on video abi
  DEBUG:root:Skipping check for rtl8821ce-dkms si

[Desktop-packages] [Bug 1973229] Re: Update freerdp2 to 2.7.0

2022-05-23 Thread Robie Basak
> The final change is backporting another patch set (from the stable
branch after the 2.7.0 release).

Where is this change in the upload please? I haven't managed to spot it.

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

Title:
  Update freerdp2 to 2.7.0

Status in freerdp2 package in Ubuntu:
  Fix Released
Status in freerdp2 source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  Ubuntu 22.04 LTS includes basically a git snapshot of freerdp2 as of April 
11. freerdp 2.7.0 was released April 25 with a few more bug fixes.

  
https://github.com/FreeRDP/FreeRDP/commits/stable-2.0?after=f8a4c6a9fed51cacd7b75ca95e2fcb018f4ac5b8+46&branch=stable-2.0

  From the NEWS file, the changes are
  * Backported OpenSSL3 gateway support (#7822)
  * Backported #7733: Support 10bit X11 color (BGRX32 only)
  * Backported #7808: Disable websockets with /gt:rpc
  * Backported #7815: RAIL expect LOGON_MSG_SESSION_CONTINUE

  Also, this includes patches that the upstream gnome-remote-desktop
  maintainers believe fix LP: #1970994 I am not mentioning that bug
  number in the debian/changelog because I don't have a clear test case
  to reproduce that bug, which is needed for SRU verification to go
  smoothly.

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

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

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

  So something like:
  RDP jeremy@192.168.1.1

  Ensure that the connection works.

  Then repeat the test after updating the second computer to use the
  updated freerdp2 since Remmina itself uses freerdp2. Basically we want
  to make sure things keep working after the update but also continue to
  work for connections between systems that aren't using the same
  version of freerdp2.

  What Could Go Wrong
  ---
  RDP Sharing using freerdp2 is a new feature for Ubuntu 22.04 LTS as part of 
GNOME 42.

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

  freerdp2 is also used by the Remmina and GNOME Connections apps as the
  "client" app for RDP Sharing. (The GNOME feature is the "server"
  side.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+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 1973229] Re: Update freerdp2 to 2.7.0

2022-05-23 Thread Robie Basak
Oh I see them now. Sorry for the noise. I'll delete this and the last
comment in a bit to try and keep the noise in the bug down.

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

Title:
  Update freerdp2 to 2.7.0

Status in freerdp2 package in Ubuntu:
  Fix Released
Status in freerdp2 source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  Ubuntu 22.04 LTS includes basically a git snapshot of freerdp2 as of April 
11. freerdp 2.7.0 was released April 25 with a few more bug fixes.

  
https://github.com/FreeRDP/FreeRDP/commits/stable-2.0?after=f8a4c6a9fed51cacd7b75ca95e2fcb018f4ac5b8+46&branch=stable-2.0

  From the NEWS file, the changes are
  * Backported OpenSSL3 gateway support (#7822)
  * Backported #7733: Support 10bit X11 color (BGRX32 only)
  * Backported #7808: Disable websockets with /gt:rpc
  * Backported #7815: RAIL expect LOGON_MSG_SESSION_CONTINUE

  Also, this includes patches that the upstream gnome-remote-desktop
  maintainers believe fix LP: #1970994 I am not mentioning that bug
  number in the debian/changelog because I don't have a clear test case
  to reproduce that bug, which is needed for SRU verification to go
  smoothly.

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

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

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

  So something like:
  RDP jeremy@192.168.1.1

  Ensure that the connection works.

  Then repeat the test after updating the second computer to use the
  updated freerdp2 since Remmina itself uses freerdp2. Basically we want
  to make sure things keep working after the update but also continue to
  work for connections between systems that aren't using the same
  version of freerdp2.

  What Could Go Wrong
  ---
  RDP Sharing using freerdp2 is a new feature for Ubuntu 22.04 LTS as part of 
GNOME 42.

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

  freerdp2 is also used by the Remmina and GNOME Connections apps as the
  "client" app for RDP Sharing. (The GNOME feature is the "server"
  side.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+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 1973229] Re: Update freerdp2 to 2.7.0

2022-05-23 Thread Robie Basak
For reference, here's what I see with some of the noise removed:

1001_keep-symbol-DumpThreadHandles-if-debugging-is-disabled.patch is
carried forward. The change to winpr/libwinpr/thread/thread.c is now
gone. The change to winpr/include/winpr/thread.h remains.

All other patches previously present are adopted in the new upstream
version exactly.

The new upstream version brings in the following 13 additional changes:

 -:  - > 27:  572c63a9f Supports 10bit X11 color (BGRX32 only)
 -:  - > 28:  62937807e Changelog
 -:  - > 29:  0f9efe197 Fixed /gt:xxx settings
 -:  - > 30:  0a6b999c5 Updated Changelog
 -:  - > 31:  f773d9759 Update header with missing flag
 -:  - > 32:  66ff8cf2a Added support for AUDIO_PLAYBACK_DVC
 -:  - > 33:  4308d8e91 fix x11 black RAIL window when connect to 
server 2019
 -:  - > 34:  e8010231c Changelog
 -:  - > 35:  70bd7f010 Update default android build config
 -:  - > 36:  52f3e5139 Cleaned up ntlm_fetch_ntlm_v2_hash
 -:  - > 38:  c263ff19e Updated changelog
 -:  - > 39:  32b8db302 Added missing WINPR_API
 -:  - > 40:  40ee5d3bc Updated for 2.7.0 release

Of these, the changes mentioning the changelog can be discounted from
concern as they definitely don't contain any functional changes. Also
the final change "Updated for 2.7.0 release" contains only the metadata
change for the version number. That leaves 8 commits being brought in
here.

Also there is the new patchset being cherry-picked from upstream commit
after they tagged 2.7.0:

0001-Refactor-thread-condition-logic.patch
0002-Do-not-mark-WinPR-implementation-of-ExitThread-as-no.patch
0003-Fixed-leak-in-TestPipeCreateNamedPipeOverlapped.patch
0004-Cleaned-up-NamedPipeOverlapped-test.patch

On the packaging side, some new symbols are added against 2.7.0+dfsg1.

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

Title:
  Update freerdp2 to 2.7.0

Status in freerdp2 package in Ubuntu:
  Fix Released
Status in freerdp2 source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  Ubuntu 22.04 LTS includes basically a git snapshot of freerdp2 as of April 
11. freerdp 2.7.0 was released April 25 with a few more bug fixes.

  
https://github.com/FreeRDP/FreeRDP/commits/stable-2.0?after=f8a4c6a9fed51cacd7b75ca95e2fcb018f4ac5b8+46&branch=stable-2.0

  From the NEWS file, the changes are
  * Backported OpenSSL3 gateway support (#7822)
  * Backported #7733: Support 10bit X11 color (BGRX32 only)
  * Backported #7808: Disable websockets with /gt:rpc
  * Backported #7815: RAIL expect LOGON_MSG_SESSION_CONTINUE

  Also, this includes patches that the upstream gnome-remote-desktop
  maintainers believe fix LP: #1970994 I am not mentioning that bug
  number in the debian/changelog because I don't have a clear test case
  to reproduce that bug, which is needed for SRU verification to go
  smoothly.

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

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

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

  So something like:
  RDP jeremy@192.168.1.1

  Ensure that the connection works.

  Then repeat the test after updating the second computer to use the
  updated freerdp2 since Remmina itself uses freerdp2. Basically we want
  to make sure things keep working after the update but also continue to
  work for connections between systems that aren't using the same
  version of freerdp2.

  What Could Go Wrong
  ---
  RDP Sharing using freerdp2 is a new feature for Ubuntu 22.04 LTS as part of 
GNOME 42.

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

  freerdp2 is also used by the Remmina and GNOME Connections apps as the
  "client" app for RDP Sharing. (The GNOME feature is the "server"
  side.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+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 1974471] Re: mouse becomes laggy when fractional scaling is enabled

2022-05-23 Thread Mauro Gaspari
Quick follow up.

I installed Ubuntu 22.04 on same RaspberryPI, and I noticed a huge performance 
difference with fractional scaling on Wayland.
On Wayland I was unable to find any lag or delay or performance hit. On Xorg 
though, even Ubuntu 22.04 had the same performance issues as Ubuntu Budgie 
22.04.

Thanks a lot for your expertise, Daniel. Much appreciated. We will make
a note on our readme for Ubuntu Budgie ARM.

I hope this helps someone down the line.

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

Title:
  mouse becomes laggy when fractional scaling is enabled

Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  Distribution: Ubuntu Budgie 22.04 LTS
  Kernel: 5.15.0-1007-raspi
  Package: libmutter-10-0
  Architecture: arm64
  Version: 42.0-3ubuntu2 5.15.0-1007-raspi

  
  On Ubuntu Budgie 22.04 LTS raspberry PI, turning on fractional scaling causes 
an issue where mouse movement becomes laggy and hard to control. This persists 
even if a reboot is performed after changing scaling settings.

  This was tested on Raspberry PI 4 8GB with 3 different mice. 2 USB wired, and 
one wireless with USB dongle. Same results with 3 mice.
  Disabling fractional scaling immediately solved the problem.

  Same tests were performed on Ubuntu Budgie 22.04 on amd64 laptop, with
  Intel CPU  and Nvidia+Intel GPU. There was no issue with mouse
  performance on amd64 laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libmutter-10-0 42.0-3ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-1007.7-raspi 5.15.35
  Uname: Linux 5.15.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Sat May 21 00:48:09 2022
  ImageMediaBuild: 20210416
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1974471/+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 1975512] [NEW] Incorrect instructions for "Screenshots and screencasts"

2022-05-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Release version: Ubuntu 22.04 LTS
Package version: 22.04.5

The descriptions for the keyboard shortcuts seem to be wrong or inaccurate at 
best.
This help page can be found at 
https://help.ubuntu.com/stable/ubuntu-help/screen-shot-record.html

Format description:
  First line: key shortcut (between angle brackets)
  Second line: official description
  Third line: actual behavior


Take a screenshot of the desktop.
Open widget in screenshot mode.


Take a screenshot of a window.
Take a screenshot of the currently focused window.


Take a screenshot of an area you select.
Take a screenshot of the full screen.


Start/Stop recording what is on your screen.
Open widget in screencast mode (second press does not stop recording).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-docs 22.04.5
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 23 18:12:41 2022
InstallationDate: Installed on 2022-05-21 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: ubuntu-docs
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session
-- 
Incorrect instructions for "Screenshots and screencasts"
https://bugs.launchpad.net/bugs/1975512
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 1973229] Re: Update freerdp2 to 2.7.0

2022-05-23 Thread Robie Basak
Thank you for the further details Jeremy.

Seb, Jeremy and I discussed this more out of band, with me wearing my TB
hat as this request matches "other cases where such upstream automatic
testing is not available, exceptions must still be approved by at least
one member of the Ubuntu Technical Board" according to
https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases.

IMHO, I think we need to work on the test plan to meet the spirit of the
requirements set by the TB previously in that paragraph, so Jeremy will
work on that with me and then we'll update the bug.

** Changed in: freerdp2 (Ubuntu Jammy)
   Status: In Progress => Incomplete

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

Title:
  Update freerdp2 to 2.7.0

Status in freerdp2 package in Ubuntu:
  Fix Released
Status in freerdp2 source package in Jammy:
  Incomplete

Bug description:
  Impact
  --
  Ubuntu 22.04 LTS includes basically a git snapshot of freerdp2 as of April 
11. freerdp 2.7.0 was released April 25 with a few more bug fixes.

  
https://github.com/FreeRDP/FreeRDP/commits/stable-2.0?after=f8a4c6a9fed51cacd7b75ca95e2fcb018f4ac5b8+46&branch=stable-2.0

  From the NEWS file, the changes are
  * Backported OpenSSL3 gateway support (#7822)
  * Backported #7733: Support 10bit X11 color (BGRX32 only)
  * Backported #7808: Disable websockets with /gt:rpc
  * Backported #7815: RAIL expect LOGON_MSG_SESSION_CONTINUE

  Also, this includes patches that the upstream gnome-remote-desktop
  maintainers believe fix LP: #1970994 I am not mentioning that bug
  number in the debian/changelog because I don't have a clear test case
  to reproduce that bug, which is needed for SRU verification to go
  smoothly.

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

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

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

  So something like:
  RDP jeremy@192.168.1.1

  Ensure that the connection works.

  Then repeat the test after updating the second computer to use the
  updated freerdp2 since Remmina itself uses freerdp2. Basically we want
  to make sure things keep working after the update but also continue to
  work for connections between systems that aren't using the same
  version of freerdp2.

  What Could Go Wrong
  ---
  RDP Sharing using freerdp2 is a new feature for Ubuntu 22.04 LTS as part of 
GNOME 42.

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

  freerdp2 is also used by the Remmina and GNOME Connections apps as the
  "client" app for RDP Sharing. (The GNOME feature is the "server"
  side.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+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 1975512] Re: Incorrect instructions for "Screenshots and screencasts"

2022-05-23 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1970588 ***
https://bugs.launchpad.net/bugs/1970588

Thanks for your report.

This has been reported previously, so I mark this bug as a duplicate.

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

** This bug has been marked a duplicate of bug 1970588
   screen-shot-record.html doesn't reflect surprisingly swapped print screen 
key behaviour

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

Title:
  Incorrect instructions for "Screenshots and screencasts"

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

Bug description:
  Release version: Ubuntu 22.04 LTS
  Package version: 22.04.5

  The descriptions for the keyboard shortcuts seem to be wrong or inaccurate at 
best.
  This help page can be found at 
https://help.ubuntu.com/stable/ubuntu-help/screen-shot-record.html

  Format description:
    First line: key shortcut (between angle brackets)
    Second line: official description
    Third line: actual behavior

  
  Take a screenshot of the desktop.
  Open widget in screenshot mode.

  
  Take a screenshot of a window.
  Take a screenshot of the currently focused window.

  
  Take a screenshot of an area you select.
  Take a screenshot of the full screen.

  
  Start/Stop recording what is on your screen.
  Open widget in screencast mode (second press does not stop recording).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-docs 22.04.5
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 18:12:41 2022
  InstallationDate: Installed on 2022-05-21 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1975512/+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 1975521] [NEW] Please merge shotwell 0.30.16-1 (main) from Debian unstable

2022-05-23 Thread Nathan Teodosio
Public bug reported:

Following is a breakdown of the latest Ubuntu changes (in 0.30.14) and if
they are still or no longer needed.

Where "Debian diff" is mentioned below, I mean the diff between the Debian
package 0.30.34-1 and 0.30.36-1, attached as deb-deb.diff.

__

* debian/build-_LIB-is-expected-to-be-a-relative-path.patch:
  - fix an incorrect path handling making plugins not found (LP: #1969439)

No longer needed: Incorporated into Debian (line 3090 of Debian diff).

__

* Cherry-pick patch to also set dark wallpaper (LP: #1965812)

No longer needed: Incorporated into Debian (line 21688 of Debian diff).

__

* debian/patches/build_new_valac.patch:
  - fix the build with the new valac version

No longer needed: Addressed in Debian (lines 22055 and 22364 of Debian
diff)

__

* Use the correct name for the unity build option
* debian/rules:
  - enable unity and apport build options

No longer needed: Addressed in lines 128-140 of Debian diff.

__

* debian/control.in:
  - Build-Depends on libunity-dev

No longer needed: Incorporated (line 57 of Debian diff).

__

* debian/debian/replace_thumbnailer.sh, 
  debian/shotwell-common.README.Debian, debian/shotwell.examples, 
  debian/shotwell.postrm, shotwell.README.Debian:
  - clean out thumbnailer hacks, that's not user friendly and not
something we should recommend

Still needed.

__

I tested the resulting package (generated by applying deb-ubu.debdiff)
with pbuilder, and verified no regressions concerning the aforementioned
LP: #1969439 and LP: #1965812.

** Affects: shotwell (Ubuntu)
 Importance: Wishlist
 Status: Confirmed

** Patch added: "deb-ubu.debdiff"
   
https://bugs.launchpad.net/bugs/1975521/+attachment/5592346/+files/deb-ubu.debdiff

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

Title:
  Please merge shotwell 0.30.16-1 (main) from Debian unstable

Status in shotwell package in Ubuntu:
  Confirmed

Bug description:
  Following is a breakdown of the latest Ubuntu changes (in 0.30.14) and if
  they are still or no longer needed.

  Where "Debian diff" is mentioned below, I mean the diff between the Debian
  package 0.30.34-1 and 0.30.36-1, attached as deb-deb.diff.

  __

  * debian/build-_LIB-is-expected-to-be-a-relative-path.patch:
- fix an incorrect path handling making plugins not found (LP: #1969439)

  No longer needed: Incorporated into Debian (line 3090 of Debian diff).

  __

  * Cherry-pick patch to also set dark wallpaper (LP: #1965812)

  No longer needed: Incorporated into Debian (line 21688 of Debian
  diff).

  __

  * debian/patches/build_new_valac.patch:
- fix the build with the new valac version

  No longer needed: Addressed in Debian (lines 22055 and 22364 of Debian
  diff)

  __

  * Use the correct name for the unity build option
  * debian/rules:
- enable unity and apport build options

  No longer needed: Addressed in lines 128-140 of Debian diff.

  __

  * debian/control.in:
- Build-Depends on libunity-dev

  No longer needed: Incorporated (line 57 of Debian diff).

  __

  * debian/debian/replace_thumbnailer.sh, 
debian/shotwell-common.README.Debian, debian/shotwell.examples, 
debian/shotwell.postrm, shotwell.README.Debian:
- clean out thumbnailer hacks, that's not user friendly and not
  something we should recommend

  Still needed.

  __

  I tested the resulting package (generated by applying deb-ubu.debdiff)
  with pbuilder, and verified no regressions concerning the aforementioned
  LP: #1969439 and LP: #1965812.

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


-- 
Mailing list: https://launchpad.net/~de

[Desktop-packages] [Bug 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf

2022-05-23 Thread Alex N.
I can confirm #14

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

Title:
  Brave & Chrome browsers freezes on download and print to pdf

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Whenever any file is downloaded, the browser will freeze. Download
  files, from any page does not work. Same issue with Firefox.

  Similarly, the browser will freeze when a page is printed to pdf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1975512] Re: Incorrect instructions for "Screenshots and screencasts"

2022-05-23 Thread Johnny Gérard
*** This bug is a duplicate of bug 1970588 ***
https://bugs.launchpad.net/bugs/1970588

Thank you!

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

Title:
  Incorrect instructions for "Screenshots and screencasts"

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

Bug description:
  Release version: Ubuntu 22.04 LTS
  Package version: 22.04.5

  The descriptions for the keyboard shortcuts seem to be wrong or inaccurate at 
best.
  This help page can be found at 
https://help.ubuntu.com/stable/ubuntu-help/screen-shot-record.html

  Format description:
    First line: key shortcut (between angle brackets)
    Second line: official description
    Third line: actual behavior

  
  Take a screenshot of the desktop.
  Open widget in screenshot mode.

  
  Take a screenshot of a window.
  Take a screenshot of the currently focused window.

  
  Take a screenshot of an area you select.
  Take a screenshot of the full screen.

  
  Start/Stop recording what is on your screen.
  Open widget in screencast mode (second press does not stop recording).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-docs 22.04.5
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 18:12:41 2022
  InstallationDate: Installed on 2022-05-21 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1975512/+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 1970588] Re: screen-shot-record.html doesn't reflect surprisingly swapped print screen key behaviour

2022-05-23 Thread Johnny Gérard
Is it possible to view the updated page?

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

Title:
  screen-shot-record.html doesn't reflect surprisingly swapped print
  screen key behaviour

Status in Gnome Documentation:
  Fix Released
Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  
https://help.ubuntu.com/stable/ubuntu-help/screen-shot-record.html.en#keyboard-shortcuts
  doesn't reflect recent changes in ubuntu 22.04 where the behaviour of "print 
screen" key functionality got swapped:

  
  Print Screen to take a screenshot of the desktop.
  Alt+Print Screen to take a screenshot of a window.
  Shift+Print Screen to take a screenshot of an area you select.

  should change to:

  Print to open an HUD with an area selector. Then click in the small white 
cicle to fullfill the screenshot.
  Alt+Print Screen to take a screenshot of a window.
  Shift+Print Screen Screen to take a screenshot of the desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-user-docs/+bug/1970588/+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 1970588] Re: screen-shot-record.html doesn't reflect surprisingly swapped print screen key behaviour

2022-05-23 Thread Gunnar Hjalmarsson
@Johnny: It's possible, but there is no easy way yet. Please be patient.
;)

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

Title:
  screen-shot-record.html doesn't reflect surprisingly swapped print
  screen key behaviour

Status in Gnome Documentation:
  Fix Released
Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  
https://help.ubuntu.com/stable/ubuntu-help/screen-shot-record.html.en#keyboard-shortcuts
  doesn't reflect recent changes in ubuntu 22.04 where the behaviour of "print 
screen" key functionality got swapped:

  
  Print Screen to take a screenshot of the desktop.
  Alt+Print Screen to take a screenshot of a window.
  Shift+Print Screen to take a screenshot of an area you select.

  should change to:

  Print to open an HUD with an area selector. Then click in the small white 
cicle to fullfill the screenshot.
  Alt+Print Screen to take a screenshot of a window.
  Shift+Print Screen Screen to take a screenshot of the desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-user-docs/+bug/1970588/+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 1975525] Re: nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push()

2022-05-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1961472 ***
https://bugs.launchpad.net/bugs/1961472

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1975525/+attachment/5592355/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1975525/+attachment/5592357/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1975525/+attachment/5592361/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1975525/+attachment/5592362/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1975525/+attachment/5592363/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1975525/+attachment/5592364/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1975525/+attachment/5592365/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1961472
   nautilus crashed with SIGSEGV in delete_outdated_error_traps() from 
gdk_x11_display_error_trap_push()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Crashed while opening folders

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 21:35:40 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1131, 1005)'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
  InstallationDate: Installed on 2022-05-01 (22 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7fa3e503252f:mov0x8(%rbp),%rax
   PC (0x7fa3e503252f) ok
   source "0x8(%rbp)" (0x5009c) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_x11_display_error_trap_push () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_x11_screen_supports_net_wm_hint () from 
/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  mtime.conffile..etc.apport.crashdb.conf: 2022-05-17T00:40:19.420743
  separator:
   
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1975525/+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 1975531] [NEW] Congelamiento de laptop abriendo pestaña de Firefox

2022-05-23 Thread Carlos Molina
Public bug reported:

En varias ocasiones tratando de abrir una pestaña de Firefox mi laptop
se congela y el led de uso del disco queda encendido. He esperado varias
horas y no pasa nada. Pensndo que se trata de que está archivando algo
en el disco. Sólo se puede restaurar apagando la laptop. Uso Firefox
instalado desde su  página oficial y he eliminado la versión snap.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 101.0~b9+build1-0ubuntu0.22.04.1 [origin: 
LP-PPA-mozillateam-firefox-next]
ProcVersionSignature: Ubuntu 5.15.0-30.31-lowlatency 5.15.30
Uname: Linux 5.15.0-30-lowlatency x86_64
NonfreeKernelModules: wl
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  carlosm1995 F pulseaudio
 /dev/snd/controlC0:  carlosm1995 F pulseaudio
BuildID: 20220519220322
CasperMD5CheckResult: unknown
Channel: beta
CurrentDesktop: KDE
Date: Mon May 23 13:07:44 2022
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
DefaultProfilePrefSources:
 /usr/lib/firefox/defaults/pref/vendor-gre.js
 /usr/lib/firefox/defaults/pref/channel-prefs.js
DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2022-04-25 (28 days ago)
InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
IpRoute:
 default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
 169.254.0.0/16 dev wlo1 scope link metric 1000 
 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.18 metric 600
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:365
Profile0PrefSources:
 /usr/lib/firefox/defaults/pref/vendor-gre.js
 /usr/lib/firefox/defaults/pref/channel-prefs.js
 prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=101.0/20220519220322 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/29/2014
dmi.bios.release: 1.5
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L77 Ver. 01.05
dmi.board.name: 1993
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 16.38
dmi.chassis.asset.tag: 5CG43711DX
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.ec.firmware.release: 22.56
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL77Ver.01.05:bd04/29/2014:br1.5:efr22.56:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.38:cvnHewlett-Packard:ct10:cvr:skuF2Q86LT#ABM:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP ProBook 640 G1
dmi.product.sku: F2Q86LT#ABM
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug beta-channel jammy third-party-packages

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

Title:
  Congelamiento de laptop abriendo pestaña de Firefox

Status in firefox package in Ubuntu:
  New

Bug description:
  En varias ocasiones tratando de abrir una pestaña de Firefox mi laptop
  se congela y el led de uso del disco queda encendido. He esperado
  varias horas y no pasa nada. Pensndo que se trata de que está
  archivando algo en el disco. Sólo se puede restaurar apagando la
  laptop. Uso Firefox instalado desde su  página oficial y he eliminado
  la versión snap.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 101.0~b9+build1-0ubuntu0.22.04.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.15.0-30.31-lowlatency 5.15.30
  Uname: Linux 5.15.0-30-lowlatency x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carlosm1995 F pulseaudio
   /dev/snd/controlC0:  carlosm1995 F pulseaudio
  BuildID: 20220519220322
  CasperMD5CheckResult: unknown
  Channel: beta
  CurrentDesktop: KDE
  Date: Mon May 23 13:07:44 2022
  DefaultProfileExtensions

[Desktop-packages] [Bug 1970588] Re: screen-shot-record.html doesn't reflect surprisingly swapped print screen key behaviour

2022-05-23 Thread Doug Smythies
I thought the gnome version might be available to view, but I couldn't
find it. I couldn't remember their development directory name, but,
after many failed attempts, finally found the "unstable" directory:

https://help.gnome.org/users/gnome-help/unstable/screen-shot-
record.html.en#keyboard-shortcuts

but it seems to be the old version.

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

Title:
  screen-shot-record.html doesn't reflect surprisingly swapped print
  screen key behaviour

Status in Gnome Documentation:
  Fix Released
Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  
https://help.ubuntu.com/stable/ubuntu-help/screen-shot-record.html.en#keyboard-shortcuts
  doesn't reflect recent changes in ubuntu 22.04 where the behaviour of "print 
screen" key functionality got swapped:

  
  Print Screen to take a screenshot of the desktop.
  Alt+Print Screen to take a screenshot of a window.
  Shift+Print Screen to take a screenshot of an area you select.

  should change to:

  Print to open an HUD with an area selector. Then click in the small white 
cicle to fullfill the screenshot.
  Alt+Print Screen to take a screenshot of a window.
  Shift+Print Screen Screen to take a screenshot of the desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-user-docs/+bug/1970588/+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 1793124]

2022-05-23 Thread Ilmari-lauhakangas
(In reply to Jan Nekvasil from comment #36)
> As akkad...@gmail.com asked more than a year ago in comment #29: Will a
> donation make a difference? I need the smooth scrolling to use OO Calc on a
> touch display by elderly people in my business, so I'm financially
> interested into this feature.

Donation will not make a difference, but any group of individuals can
pool their money and hire a C++ freelancer to fix any bug in
LibreOffice.

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

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04

2022-05-23 Thread VAN LAETHEM
I read 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6a82dd18
and identified the 4 files that must be adapted but . there is not 
directory /src/core or supplicant on my disk and so no files that i can adapt.

I don't identify what i have to do, sorry!

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

Title:
  wifi connection on hotspot with wpa enterprise on 22.04

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  With 20.04 I used a wifi connection with a hotspot Telenet with following 
parametres:
  security : WPA2 entreprise
  authentification : tunneled TLS
  no AC certificat drequired
  inner authentication : MSCHAPV2(non EAP)
  user name: my id
  password : my pswd

  with 22.04 it doesn’t work anymore nor with the internal broadcom wifi
  nor with dongles (nor my Dlink 140 nor TP-link WN7200)

  This problem is only present with hotspot requesting an identification
  (user+pswd) awith hotspots without identification everything is OK

  in appendice some infos
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michelvlt   1725 F pulseaudio
   /dev/snd/pcmC0D0p:   michelvlt   1725 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source /etc/network/interfaces.d/*
  InstallationDate: Installed on 2022-04-21 (7 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IpRoute:
   default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 
   10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 
   169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 
   192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 
600
  MachineType: Apple Inc. MacBookPro8,1
  NonfreeKernelModules: wl
  Package: wpa
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 87.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245B3640C91C81
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245B3640C91C81
  dmi.modalias: 
dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro8,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29

2022-05-23 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-33.34~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

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

Title:
  network-manager/1.36.4-2ubuntu1 ADT test failure with
  linux/5.15.0-28.29

Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in urfkill package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in network-manager source package in Jammy:
  Invalid
Status in urfkill source package in Jammy:
  New

Bug description:
  This is a scripted bug report about ADT failures while running
  network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is
  caused by the dep8 tests of the tested source or the kernel has yet to
  be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz

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

2022-05-23 Thread sheryl
Thanks for the quick responses. I followed the instructions to install
the latest version. Is it supposed to work if I installed 5.18 too? It's
not working and it stopped recognising my external monitors too.

(In reply to Cameron Berkenpas from comment #608)
> Seems like this is the best way to do it (but if someone knows of a better
> way for Ubuntu, let us know):
> https://sleeplessbeastie.eu/2021/11/01/how-to-install-mainline-linux-kernel-
> on-ubuntu-based-distribution/
> 
> Seems this gets you a tool that allows you to manage and install mainline
> kernels. You'll need a 5.17 (which is the latest stable mainline release) to
> get your sound working.
> 
> Keep us posted.
> 
> 
> (In reply to Cameron Berkenpas from comment #607)
> 
> > There should be a repo you can add on your system to be able to pull the 
> > latest mainline kernels. I don't have it handy at the moment as I've 
> > been building/installing kernels myself since the 90's, but I'll try 
> > find it and post it in a little bit.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2022-05-23 Thread hnsinan.ta
Hello everyone,

I really appreciate this thread and all of the solutions that have been
produced for this issue. Thanks to everyone contributing, especially
Cameron Berkenpas who has been very helpful to a number of users and the
main driving force for fixes:)

Now to my issue: I own a Lenovo Yoga 7i 15ITL05 82AC with the ALC287.
Currently it runs Ubuntu 22.04. LTS  with the included 5.15 Kernel.
Before I have run Pop_OS 21.04. and 22.04. With all these distros, the
sound worked partially but never fully. The experience is the same as
many other users here, where there would only be sound coming out the
from the downward firing speakers, but not from the soundbar above the
keyboard, which are the bass speakers judging by the tinny sound I get
now. The sound works beautifully in Windows, since the lower end
frequencies can be replayed.

Quite honestly, I've lost the overview over this thread and am not so
sure which patch I should apply. I've tried manually update my Ubuntu
22.04. to the mainline 5.17 Kernel, which worked OS-wise but didn't
change sound. My hope was that the sound patches have been included in
that Kernel, but it seems they're only working for the Legion 7.

Could someone point me to the right patch or verbs that have to be
applied for my Lenovo model in order for the bass speakers to work?
Maybe someone has figured it out for this particular case?

Much thanks in advance.

Here's my alsa-info:

http://alsa-project.org/db/?f=ad3990bed59a24417ea6429250275012611a0302

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2022-05-23 Thread cam
I would try try 5.17. 5.18 only came out yesterday, and therefore
doesn't even have any point releases so chances are reasonably high
you'll run into bugs.

Additionally, I don't have the ACHg6. It's possible you'll need to
specify which modules to load. In the likely event that 5.17 doesn't
work, perhaps someone can provide information on what's needed there.

Possibly these steps will work:
sudo modprobe snd-hda-codec-cs35l41-i2c
sudo modeprobe snd_soc_cs35l41_i2c
sudo modeprobe i2c-multi-instantiate

(In reply to she...@liang.at from comment #609)
> Thanks for the quick responses. I followed the instructions to install the
> latest version. Is it supposed to work if I installed 5.18 too? It's not
> working and it stopped recognising my external monitors too.
>

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2022-05-23 Thread hnsinan.ta
Hello everyone,

I really appreciate this thread and all of the solutions that have been
produced for this issue. Thanks to everyone contributing, especially
Cameron Berkenpas who has been very helpful to a number of users and the
main driving force for fixes:)

Now to my issue: I own a Lenovo Yoga 7i 15ITL05 82AC with the ALC287.
Currently it runs Ubuntu 22.04. LTS  with the included 5.15 Kernel.
Before I have run Pop_OS 21.04. and 22.04. With all these distros, the
sound worked partially but never fully. The experience is the same as
many other users here, where there would only be sound coming out the
from the downward firing speakers, but not from the soundbar above the
keyboard, which are the bass speakers judging by the tinny sound I get
now. The sound works beautifully in Windows, since the lower end
frequencies can be replayed.

Quite honestly, I've lost the overview over this thread and am not so
sure which patch I should apply. I've tried manually update my Ubuntu
22.04. to the mainline 5.17 Kernel, which worked OS-wise but didn't
change sound. My hope was that the sound patches have been included in
that Kernel, but it seems they're only working for the Legion 7.

Could someone point me to the right patch or verbs that have to be
applied for my Lenovo model in order for the bass speakers to work?
Maybe someone has figured it out for this particular case?

Much thanks in advance.

Here's my alsa-info:

http://alsa-project.org/db/?f=ad3990bed59a24417ea6429250275012611a0302

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2022-05-23 Thread cam
There's no patch for your laptop yet.

Assuming your sound bar is initialized through verbs (I suspect it is), 
you'll need to find the verb sequence yourself:
https://github.com/thiagotei/linux-realtek-alc287/tree/cameron

Once there's a working verb sequence, a patch can be created.

On 5/23/22 04:50, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #611 from singo (hnsinan...@gmail.com) ---
> Hello everyone,
>
> I really appreciate this thread and all of the solutions that have been
> produced for this issue. Thanks to everyone contributing, especially Cameron
> Berkenpas who has been very helpful to a number of users and the main driving
> force for fixes:)
>
> Now to my issue: I own a Lenovo Yoga 7i 15ITL05 82AC with the ALC287.
> Currently
> it runs Ubuntu 22.04. LTS  with the included 5.15 Kernel. Before I have run
> Pop_OS 21.04. and 22.04. With all these distros, the sound worked partially
> but
> never fully. The experience is the same as many other users here, where there
> would only be sound coming out the from the downward firing speakers, but not
> from the soundbar above the keyboard, which are the bass speakers judging by
> the tinny sound I get now. The sound works beautifully in Windows, since the
> lower end frequencies can be replayed.
>
> Quite honestly, I've lost the overview over this thread and am not so sure
> which patch I should apply. I've tried manually update my Ubuntu 22.04. to
> the
> mainline 5.17 Kernel, which worked OS-wise but didn't change sound. My hope
> was
> that the sound patches have been included in that Kernel, but it seems
> they're
> only working for the Legion 7.
>
> Could someone point me to the right patch or verbs that have to be applied
> for
> my Lenovo model in order for the bass speakers to work? Maybe someone has
> figured it out for this particular case?
>
> Much thanks in advance.
>
> Here's my alsa-info:
>
> http://alsa-project.org/db/?f=ad3990bed59a24417ea6429250275012611a0302
>

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://b

[Desktop-packages] [Bug 1958019]

2022-05-23 Thread sheryl
The first two modprobe commands returned
`
modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory 
/lib/modules/5.13.0-051300-generic
`
The third one returns nothing.

I tried reinstalling my nvidia driver too but even after purging all it
doesn't seem to work :\

I tried following these instructions:
https://forums.developer.nvidia.com/t/nvidia-smi-has-failed-because-it-
couldnt-communicate-with-the-nvidia-driver-make-sure-that-the-latest-
nvidia-driver-is-installed-and-running/197141/6

(In reply to Cameron Berkenpas from comment #612)
> I would try try 5.17. 5.18 only came out yesterday, and therefore doesn't
> even have any point releases so chances are reasonably high you'll run into
> bugs.
> 
> Additionally, I don't have the ACHg6. It's possible you'll need to specify
> which modules to load. In the likely event that 5.17 doesn't work, perhaps
> someone can provide information on what's needed there.
> 
> Possibly these steps will work:
> sudo modprobe snd-hda-codec-cs35l41-i2c
> sudo modeprobe snd_soc_cs35l41_i2c
> sudo modeprobe i2c-multi-instantiate
> 
> (In reply to she...@liang.at from comment #609)
> > Thanks for the quick responses. I followed the instructions to install the
> > latest version. Is it supposed to work if I installed 5.18 too? It's not
> > working and it stopped recognising my external monitors too.
> >

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2022-05-23 Thread cam
Your error message shows you're 5.13, which definitely doesn't have
support.


On 5/23/22 08:46, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #614 from she...@liang.at (she...@liang.at) ---
> The first two modprobe commands returned
> `
> modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory
> /lib/modules/5.13.0-051300-generic
> `
> The third one returns nothing.
>
> I tried reinstalling my nvidia driver too but even after purging all it
> doesn't
> seem to work :\
>
> I tried following these instructions:
>
> https://forums.developer.nvidia.com/t/nvidia-smi-has-failed-because-it-couldnt-communicate-with-the-nvidia-driver-make-sure-that-the-latest-nvidia-driver-is-installed-and-running/197141/6
>
> (In reply to Cameron Berkenpas from comment #612)
>> I would try try 5.17. 5.18 only came out yesterday, and therefore doesn't
>> even have any point releases so chances are reasonably high you'll run into
>> bugs.
>>
>> Additionally, I don't have the ACHg6. It's possible you'll need to specify
>> which modules to load. In the likely event that 5.17 doesn't work, perhaps
>> someone can provide information on what's needed there.
>>
>> Possibly these steps will work:
>> sudo modprobe snd-hda-codec-cs35l41-i2c
>> sudo modeprobe snd_soc_cs35l41_i2c
>> sudo modeprobe i2c-multi-instantiate
>>
>> (In reply to she...@liang.at from comment #609)
>>> Thanks for the quick responses. I followed the instructions to install the
>>> latest version. Is it supposed to work if I installed 5.18 too? It's not
>>> working and it stopped recognising my external monitors too.
>>>

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1975544] [NEW] Gtk4 EventController GestureClick returns incorrect state- Gdk.ModifierType on mouse button press in X11

2022-05-23 Thread Sundeep
Public bug reported:

Getting modifier state from event controller gesture click gives an
error in Ubuntu 22.04 on X11.

It seems it returns with the 4 bit set, which is not legal?

The entire bug is reported in Gnome Discourse here-
https://discourse.gnome.org/t/gtk4-eventcontroller-gestureclick-returns-
incorrect-state-gdk-modifiertype-on-mouse-button-press-in-x11/9710 with
an example program that triggers the bug.

This bug does not exist in the latest version of Manjaro, and I presume
archlinux. Fedora also seems to have the same bug.

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

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

Title:
  Gtk4 EventController GestureClick returns incorrect state-
  Gdk.ModifierType on mouse button press in X11

Status in gjs package in Ubuntu:
  New

Bug description:
  Getting modifier state from event controller gesture click gives an
  error in Ubuntu 22.04 on X11.

  It seems it returns with the 4 bit set, which is not legal?

  The entire bug is reported in Gnome Discourse here-
  https://discourse.gnome.org/t/gtk4-eventcontroller-gestureclick-
  returns-incorrect-state-gdk-modifiertype-on-mouse-button-press-
  in-x11/9710 with an example program that triggers the bug.

  This bug does not exist in the latest version of Manjaro, and I
  presume archlinux. Fedora also seems to have the same bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1975544/+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 1975545] [NEW] firefox on xwayland unusable after gnome autostart

2022-05-23 Thread Birgit Edel
Public bug reported:

Early starts of firefox on gnome on wayland on Ubuntu 20.04.4 are
unusable. Early meaning directly after session start from gdm.

If I put firefox.desktop into ~/.config/autostart/, firefox will start
as expected, successfully load my homepage (as evidenced in server
logs), but fail to display windows decoration or contents or react on
input. The space occupied by the window will be either black, matching
last shown pixels in the place (background, other windows) or alternate
between such with varying flicker frequency.

For avoidance of ambiguity, the mode affected by the bug is
windowProtocol=xwayland (as in about:support)

The bug can be worked around, either method is sufficient on its own:
a) forcing windowProtocol=wayland through environment MOZ_ENABLE_WAYLAND=1
b) starting firefox later, through a prepended sleep 10 call

Mostly for documenting the workarounds, I understand that this might not
be worth fixing as firefox snap approaches similar quality, see also
#1970884

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


** Tags: wayland

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

Title:
  firefox on xwayland unusable after gnome autostart

Status in firefox package in Ubuntu:
  New

Bug description:
  Early starts of firefox on gnome on wayland on Ubuntu 20.04.4 are
  unusable. Early meaning directly after session start from gdm.

  If I put firefox.desktop into ~/.config/autostart/, firefox will start
  as expected, successfully load my homepage (as evidenced in server
  logs), but fail to display windows decoration or contents or react on
  input. The space occupied by the window will be either black, matching
  last shown pixels in the place (background, other windows) or
  alternate between such with varying flicker frequency.

  For avoidance of ambiguity, the mode affected by the bug is
  windowProtocol=xwayland (as in about:support)

  The bug can be worked around, either method is sufficient on its own:
  a) forcing windowProtocol=wayland through environment MOZ_ENABLE_WAYLAND=1
  b) starting firefox later, through a prepended sleep 10 call

  Mostly for documenting the workarounds, I understand that this might
  not be worth fixing as firefox snap approaches similar quality, see
  also #1970884

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1975545/+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 1975549] [NEW] NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection

2022-05-23 Thread Jeffrey Walton
Public bug reported:

I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.

I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.

I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It literally
calls the connection "ethernet", as if it was using the network adapter.
This is new behavior over the last week or two.

This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called "ethernet"
instead of something more meaningful like "USB" or "Android" or "wired
hotspot".

The third item ("ethernet" name when using Android phone) was misleading
enough to waste a lot of time troubleshooting the issue. I thought I had
an odd firewall issue or a mDNS issue.

The reason I was having so many troubles, like printing and ssh, is the
Android phone uses Wifi and it is on a different VLAN and subnet to keep
traffic segregated from my trusted internal network.

-

It looks like I am running network-manager via systemd:

# service systemd-networkd status
● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
 Active: inactive (dead)
   Docs: man:systemd-networkd.service(8)
# service network-manager  status
● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
 Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
   Docs: man:NetworkManager(8)
   Main PID: 928 (NetworkManager)
  Tasks: 3 (limit: 76693)
 Memory: 12.0M
 CGroup: /system.slice/NetworkManager.service
 └─928 /usr/sbin/NetworkManager --no-daemon
  ...

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

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

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...

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

[Desktop-packages] [Bug 1875671] Re: wayland: desktop folder missing in Nautilus sidebar

2022-05-23 Thread Daniel van Vugt
** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1985
   Importance: Unknown
   Status: Unknown

** Project changed: gtk => ubuntu

** No longer affects: ubuntu

** No longer affects: gnome-shell

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

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Low

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

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

Title:
  wayland: desktop folder missing in Nautilus sidebar

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

Bug description:
  Using Wayland session nautilus home window does not show Desktop folder in 
sidebar while is dispayed using X11 session.
  see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  Uname: Linux 5.7.0-050700rc3-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 17:24:45 2020
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 
852)'
  InstallationDate: Installed on 2020-04-23 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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


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


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

2022-05-23 Thread Daniel van Vugt
Great!

I had tested 'nomodeset' when this bug was first reported but was unable
to reproduce the problem myself.

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

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

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

** Summary changed:

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

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

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

Status in Ubuntu:
  Won't Fix

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

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

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

  echo $XDG_SESSION_TYPE
  x11

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

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


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


[Desktop-packages] [Bug 1969598] Re: Desktop Icons NG steals keyboard focus from apps after workspace switch

2022-05-23 Thread Daniel van Vugt
** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5517
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5517

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

** 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/1969598

Title:
  Desktop Icons NG steals keyboard focus from apps after workspace
  switch

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1) Setup at least two workspaces.

  2) open at least one GUI application on one of them. Another one is
  focused and no application opened.

  3) switch workspaces from 'empty' to 'with application'

  
  Expected result: last focused GUI application from the new focused workspace 
will be auto-focused again. And all shortcuts right after the switch will be 
applicable to a given application.

  Actual result: application is not focused, all shortcuts are
  applicable to desktop only.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 12:17:48 2022
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1969598/+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 1969598] Re: Desktop Icons NG steals keyboard focus from apps after workspace switch

2022-05-23 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => 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/1969598

Title:
  Desktop Icons NG steals keyboard focus from apps after workspace
  switch

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1) Setup at least two workspaces.

  2) open at least one GUI application on one of them. Another one is
  focused and no application opened.

  3) switch workspaces from 'empty' to 'with application'

  
  Expected result: last focused GUI application from the new focused workspace 
will be auto-focused again. And all shortcuts right after the switch will be 
applicable to a given application.

  Actual result: application is not focused, all shortcuts are
  applicable to desktop only.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 12:17:48 2022
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1969598/+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