[Desktop-packages] [Bug 1969294] Re: Ubuntu 22.04 gdm3 freezes with Nvidia GPU

2022-08-26 Thread Launchpad Bug Tracker
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu 22.04 gdm3 freezes with Nvidia GPU

Status in gdm3 package in Ubuntu:
  Expired

Bug description:
  I have Ubuntu 22.04 installed and keep updating everyday. After
  Friday's update (04/15/2022), Ubuntu 22.04 booting will freeze very
  likely at gdm3.

  I am able to confirm: uninstalling Nvidia driver could solve the issue
  but gave me a slow GUI.

  I am also able to reproduce the issue by: 1> fresh install Ubuntu
  22.04 beta; 2> switch to Nvidia 510 driver and reboot and it worked
  fine; 3> apt update & apt upgrade and reboot; 4> Ubuntu freeze.

  I am able to reproduce the issue on both my NV GTX1080 and Quadro
  P620.

  It is unbelievable a bug surfaces at this stage (I guess RC?).

  I hope I was able to upload a syslog later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969294/+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 1979540] Re: Screen sharing via RDP is mostly broken

2022-08-26 Thread Launchpad Bug Tracker
[Expired for gnome-remote-desktop (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  Screen sharing via RDP is mostly broken

Status in gnome-remote-desktop package in Ubuntu:
  Expired

Bug description:
  I set up screen sharing on one computer, then via LAN I have connected
  via multiple clients (android using official MS remote desktop client,
  windows using official MS remote desktop client, and another ubuntu
  22.04 machine using remmina 1.4.25)

  On all clients the connection is a blank screen, however, mouse click
  and scroll events are successfully forwarded to the server machine...

  the gnome-remote-deskop service does log to systemd journal that a
  connection has succeeded and I see the yellow indicator icon in the
  top right

  42.1.1-0ubuntu1 of gnome-remote-desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-remote-desktop 42.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Jun 22 14:03:02 2022
  InstallationDate: Installed on 2019-07-15 (1072 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-remote-desktop
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1979540/+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 1983794] Re: Evolution not deleting autosave files

2022-08-26 Thread Lindsay
It looks as if the source of this problem has been identified. How long
should it take to get the fix pushed into Ubuntu updates? I assume that
it will be.

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

Title:
  Evolution not deleting autosave files

Status in Evolution:
  Unknown
Status in evolution package in Ubuntu:
  In Progress
Status in libcanberra package in Ubuntu:
  Triaged

Bug description:
  Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
  was installed with the distribution on a new system and received
  settings imported from an earlier version on another computer.

  When composing an email, if the process takes long enough an autosave
  file is created as ~/.local/share/evolution/.evolution-
  composer.autosave-xx ("xx" is a random 6 character string).
  When the email is successfully sent, the autosave file SHOULD be
  deleted. It's not. When evolution is shut down and restarted I'm asked
  if I want to recover an unfinished email. Answering No to this will
  delete the autosave file, but otherwise it persists and the recovery
  query recurs the next time I open evolution.

  Other people are having the same issue, see
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
  people aren't dealing with it, perhaps considering it a distro-
  specific bug.

  On a system used by many people this is a potential security issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1987933] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-08-26 Thread Apport retracing service
** Package changed: ubuntu => firefox (Ubuntu)

** Tags removed: 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/1987933

Title:
  package firefox 104.0+build3-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

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  home   1370 F pulseaudio
   /dev/snd/controlC1:  home   1370 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Fri Aug 26 15:16:30 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-08-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IpRoute:
   default via 192.168.43.1 dev wlx20e41702fe19 proto dhcp metric 600 
   169.254.0.0/16 dev wlx20e41702fe19 scope link metric 1000 
   192.168.43.0/24 dev wlx20e41702fe19 proto kernel scope link src 
192.168.43.250 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.1
   apt  2.4.7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-08-26 (0 days ago)
  dmi.bios.date: 07/26/2021
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/26/2021:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

2022-08-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

NOT SURE

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 104.0+build3-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  home   1370 F pulseaudio
 /dev/snd/controlC1:  home   1370 F pulseaudio
BuildID: 20220818191623
CasperMD5CheckResult: unknown
Channel: Unavailable
Date: Fri Aug 26 15:16:30 2022
ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
ForcedLayersAccel: False
InstallationDate: Installed on 2022-08-25 (1 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
IpRoute:
 default via 192.168.43.1 dev wlx20e41702fe19 proto dhcp metric 600 
 169.254.0.0/16 dev wlx20e41702fe19 scope link metric 1000 
 192.168.43.0/24 dev wlx20e41702fe19 proto kernel scope link src 192.168.43.250 
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.1
 apt  2.4.7
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: 
new firefox package pre-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to jammy on 2022-08-26 (0 days ago)
dmi.bios.date: 07/26/2021
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61
dmi.board.vendor: INTEL Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/26/2021:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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


** Tags: amd64 apport-package jammy need-duplicate-check
-- 
package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new 
firefox package pre-installation script subprocess returned error exit status 1
https://bugs.launchpad.net/bugs/1987933
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to firefox 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 1672465] Re: Onboard doesn't work in Wayland

2022-08-26 Thread Evan
I created an account just to squeak a little at this wheel.

Whatever is being used in Ubuntu 22 is far inferior to Onboard.

X11 is being deprecated.

I imagine that devs knew that Wayland would replace X11 in Ubuntu LTS

Time to decide what you will all do.

in 4 years Will Onboard be abandoned or will it support wayland?

this took8 minutes to type in ubuntu 22 lts keyboard

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

Title:
  Onboard doesn't work in Wayland

Status in Onboard:
  Won't Fix
Status in OnboardOSK:
  Confirmed
Status in onboard package in Ubuntu:
  Confirmed

Bug description:
  Onboard 1.4.1 on Ubuntu GNOME 17.04

  Onboard at least shows the keyboard now in GNOME on Wayland. But it
  doesn't send key presses to gedit or other native Wayland apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1672465/+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 1987134] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver

2022-08-26 Thread Jesse Johnson
> 1. Look in /var/crash for crash files ...

I did and could not find any recent ones - most recent was over a week
ago.


> 2.  If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID 
> is the content of file /var/lib/whoopsie/whoopsie-id on the machine.

Nothing there that is recent from a time I tried to suspend.

FWIW when I reach the blank screen I am able to restart using
Alt+PrntScreen REISUB, so the machine is at least waking enough to allow
access to the Linux kernel, but it seems nothing is being logged in
journalctl during wake.

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

** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
   Status: Incomplete => New

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

Title:
  Black screen after wake from S3 suspend on Nvidia proprietary driver

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New

Bug description:
  An Nvidia driver upgrade in Ubuntu 20.04 caused waking from S3 suspend
  to lead to a black screen.

  Upgrading to Ubuntu 22.04 using latest stable Nvidia driver 515.65.01
  did not resolve the issue.

  There are several Nvidia sleep tickets that at first seem related, but
  mention dmesg entries that I am not seeing which makes me suspect I
  have a different issue:

  * 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970088
  * 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303

  Workaround dhenry mentions in 1970088 of disabling the nvidia suspend
  and hibernate systemd services makes no difference for me.

  Currrently running Ubuntu 22.04, Nvidia GTX 970 on driver 515.65.01,
  AMD Ryzen 7 5800X.

  Here are journalctl excerpts during the reboot process, with and
  without nvidia systemd suspend services. dmesg and /var/log/kern.log
  show no errors as are mentioned in the above tickets.

  With disabled nvidia suspend systemd services:

  Aug 19 12:42:37 uf-panacea ModemManager[2731]:   [sleep-monitor] system 
is about to suspend
  Aug 19 12:42:37 uf-panacea NetworkManager[2617]:   [1660938157.8491] 
manager: NetworkManager state>
  Aug 19 12:42:37 uf-panacea systemd[1]: Reached target Sleep.
  Aug 19 12:42:37 uf-panacea systemd[1]: Starting Record successful boot for 
GRUB...
  Aug 19 12:42:37 uf-panacea systemd[1]: Starting System Suspend...
  Aug 19 12:42:37 uf-panacea systemd-sleep[13048]: Entering sleep state 
'suspend'...
  Aug 19 12:42:37 uf-panacea systemd[1]: grub-common.service: Deactivated 
successfully.
  Aug 19 12:42:37 uf-panacea systemd[1]: Finished Record successful boot for 
GRUB.

  With enabled nvidia suspend systemd services:

  Aug 19 12:12:25 uf-panacea systemd[1]: Starting NVIDIA system suspend 
actions...
  Aug 19 12:12:25 uf-panacea suspend[15998]: nvidia-suspend.service
  Aug 19 12:12:25 uf-panacea logger[15998]: <13>Aug 19 12:12:25 suspend: 
nvidia-suspend.service
  Aug 19 12:12:25 uf-panacea systemd[1]: grub-common.service: Deactivated 
successfully.
  Aug 19 12:12:25 uf-panacea systemd[1]: Finished Record successful boot for 
GRUB.
  Aug 19 12:12:25 uf-panacea systemd[1]: Starting GRUB failed boot detection...
  Aug 19 12:12:25 uf-panacea systemd[1]: grub-initrd-fallback.service: 
Deactivated successfully.
  Aug 19 12:12:25 uf-panacea systemd[1]: Finished GRUB failed boot detection.
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"40"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event1  - 
Power Button: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"43"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event0  - 
Power Button: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"44"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event4  - 
USB Mouse OKLIC: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"45"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event5  - 
USB Mouse OKLIC Mouse: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"46"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event6  - 
USB Mouse OKLIC System Control: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"47"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event7  - 
USB Mouse OKLIC Consumer Control: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"53"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"53"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event11 - 
Valve Software Steam 

[Desktop-packages] [Bug 1987134] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver

2022-08-26 Thread Jesse Johnson
Here is the output of `journalctl -b-1 | tail` after waiting over a
minute on the blank screen and restarting. (In this case the screen
wasn't completely blank but had a non-flashing cursor in the top left
corner. It doesn't appear every time, only ~1/3 of wake from sleep
attempts.)

** Attachment added: "journalctl -b-1 | tail"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987134/+attachment/5611972/+files/prevboot.txt

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

Title:
  Black screen after wake from S3 suspend on Nvidia proprietary driver

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New

Bug description:
  An Nvidia driver upgrade in Ubuntu 20.04 caused waking from S3 suspend
  to lead to a black screen.

  Upgrading to Ubuntu 22.04 using latest stable Nvidia driver 515.65.01
  did not resolve the issue.

  There are several Nvidia sleep tickets that at first seem related, but
  mention dmesg entries that I am not seeing which makes me suspect I
  have a different issue:

  * 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970088
  * 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303

  Workaround dhenry mentions in 1970088 of disabling the nvidia suspend
  and hibernate systemd services makes no difference for me.

  Currrently running Ubuntu 22.04, Nvidia GTX 970 on driver 515.65.01,
  AMD Ryzen 7 5800X.

  Here are journalctl excerpts during the reboot process, with and
  without nvidia systemd suspend services. dmesg and /var/log/kern.log
  show no errors as are mentioned in the above tickets.

  With disabled nvidia suspend systemd services:

  Aug 19 12:42:37 uf-panacea ModemManager[2731]:   [sleep-monitor] system 
is about to suspend
  Aug 19 12:42:37 uf-panacea NetworkManager[2617]:   [1660938157.8491] 
manager: NetworkManager state>
  Aug 19 12:42:37 uf-panacea systemd[1]: Reached target Sleep.
  Aug 19 12:42:37 uf-panacea systemd[1]: Starting Record successful boot for 
GRUB...
  Aug 19 12:42:37 uf-panacea systemd[1]: Starting System Suspend...
  Aug 19 12:42:37 uf-panacea systemd-sleep[13048]: Entering sleep state 
'suspend'...
  Aug 19 12:42:37 uf-panacea systemd[1]: grub-common.service: Deactivated 
successfully.
  Aug 19 12:42:37 uf-panacea systemd[1]: Finished Record successful boot for 
GRUB.

  With enabled nvidia suspend systemd services:

  Aug 19 12:12:25 uf-panacea systemd[1]: Starting NVIDIA system suspend 
actions...
  Aug 19 12:12:25 uf-panacea suspend[15998]: nvidia-suspend.service
  Aug 19 12:12:25 uf-panacea logger[15998]: <13>Aug 19 12:12:25 suspend: 
nvidia-suspend.service
  Aug 19 12:12:25 uf-panacea systemd[1]: grub-common.service: Deactivated 
successfully.
  Aug 19 12:12:25 uf-panacea systemd[1]: Finished Record successful boot for 
GRUB.
  Aug 19 12:12:25 uf-panacea systemd[1]: Starting GRUB failed boot detection...
  Aug 19 12:12:25 uf-panacea systemd[1]: grub-initrd-fallback.service: 
Deactivated successfully.
  Aug 19 12:12:25 uf-panacea systemd[1]: Finished GRUB failed boot detection.
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"40"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event1  - 
Power Button: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"43"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event0  - 
Power Button: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"44"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event4  - 
USB Mouse OKLIC: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"45"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event5  - 
USB Mouse OKLIC Mouse: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"46"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event6  - 
USB Mouse OKLIC System Control: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"47"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event7  - 
USB Mouse OKLIC Consumer Control: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"53"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"53"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event11 - 
Valve Software Steam Controller: device removed
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"50"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" 
"50"
  Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event9  - 

[Desktop-packages] [Bug 1838008] Re: [snap] cursor theme isn't respected

2022-08-26 Thread xexz
-- 
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/1838008

Title:
  [snap] cursor theme isn't respected

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in xubuntu-default-settings package in Ubuntu:
  Fix Released

Bug description:
  (initially reported at https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/85)

  When changing the cursor theme with gnome-tweaks, I can observe that
  some themes aren't respected in the chromium snap. This appears to be
  specific to chromium, other snaps like evince or gimp use the correct
  cursors.

  Yaru and Adwaita are fine, but Redglass or Whiteglass aren't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838008/+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 1073372] Re: Xorg produces high CPU usage, slow gnome-terminal

2022-08-26 Thread ELMX
Hi,

I'm on xubuntu 22.04.1 nvidia driver 515.65.01, nvidia on-demand profile
lags ...

I saw xauth list defaults to display :0 , and according to nvidia-
settings, nvidia on-demamd profile uses screen 256, not screen 0. So i
tried this:

$ xauth add localhost:256 . $(xxd -l 16 -p /dev/urandom)

after above command:

xauth list, and the hexkey is there

But, i noticed no diff without these commands

Any idea??

Thank you

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

Title:
  Xorg produces high CPU usage, slow gnome-terminal

Status in cairo package in Ubuntu:
  Invalid

Bug description:
  Thinkpad X220 (Intel video, chipsets, etc)

  After a few days of uptime and usage on this laptop, the xorg process
  will start randomly (but consistently over time) producing high CPU
  usage, even with all applications closed.  CPU according to top will
  vary between about 10% and 90%, and at high CPU times, the system fans
  will be running rather high.  Also, the UIs will slow down and there
  will be a lot of latency on keypresses (sometimes up to 1 second),
  with the occasional loss of keypresses.  In gnome-terminal, this has
  the effect of feeling like you're over a cellular modem, even on a
  local terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,move,gnomecompat,compiztoolbox,imgpng,mousepoll,regex,place,snap,unitymtgrabhandles,resize,grid,session,animation,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  Date: Tue Oct 30 16:30:09 2012
  DistUpgraded: 2012-09-15 22:41:29,902 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.1.18, 3.5.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  Lsusb:
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. Bluetooth Controller
  MachineType: LENOVO 4286CTO
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to quantal on 2012-09-16 (44 days ago)
  dmi.bios.date: 04/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET61WW (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4286CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET61WW(1.31):bd04/25/2012:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4286CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.8.4-0ubuntu3
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1073372/+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 1987528] Re: Since upgrade from 20.04 → 22.04 ; unable to print in color, only black and white

2022-08-26 Thread Coeur Noir
** Tags added: jammy

** Tags added: regression

** Tags removed: regression

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

Title:
  Since upgrade from 20.04 → 22.04 ; unable to print in color, only
  black and white

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Hi,

  Printer ( in my context ) is Ricoh Aficio mpc 3002 and most Ricoh's
  drivers are open-source (
  https://www.openprinting.org/printer/Ricoh/Ricoh-Aficio_MP_C3002 )

  Since I « upgraded » my installation from 20.04 → 22.04, I'm unable to
  print in colors, only black and white, whatever I set in driver.

  I tried what's suggested in
  ⋅ 
https://askubuntu.com/questions/1410583/upgrading-to-22-04-printer-doesnt-works-in-color
  ⋅ 
https://discourse.ubuntubudgie.org/t/22-04-unable-to-add-printer-which-perfectly-worked-in-20-04/6209

  I might go wrong somewhere cause I still can't manage to print in color.
  → the snap thing ( Gutenprint Printer Application ) does not detect my ( 
network ) printer,
  → I'm not sure of the name for PRINTER I should input in command « lpadmin -p 
PRINTER -o print-color-mode-default=color » ( and is this as normal user or 
sudo ? )

  It seems related to
  ⋅ https://github.com/OpenPrinting/cups/issues/421

  It's a regression ( as it used to work out of the box before 22.04 ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1987528/+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 1987624] Re: Temporarily hold evolution-data-server in -proposed

2022-08-26 Thread Jeremy Bicha
** Changed in: evolution-data-server (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Temporarily hold evolution-data-server in -proposed

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

Bug description:
  Maybe I needed to add more explicit Breaks in the packaging?

  But if evolution-data-server smoothly migrates, I fear that several
  packages including key ones like gnome-shell won't run because apps
  can't use both libsoup2 and libsoup3 in the same process.

  So I'm filing a blocker bug for now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1987624/+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 1987304] Re: gtk3 fails to build from source in kinetic

2022-08-26 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.24.34-3ubuntu2

---
gtk+3.0 (3.24.34-3ubuntu2) kinetic; urgency=medium

  * Re-enable and adapt reftest-known-fail.patch (lp: #1987304)

 -- Nathan Pratta Teodosio   Wed, 24 Aug
2022 10:11:03 -0300

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

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

Title:
  gtk3 fails to build from source in kinetic

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  gtk3 has build test failures in kinetic but not in Debian Unstable.

  (It built on riscv64 because we skip the build tests there).

  My initial impression is that this is a reftest issue. The reftests
  are frustrating because dependency changes can lead to images that
  vary by as little as one pixel and fail the test. And upstream doesn't
  provide a precise list of dependency versions they are using either.

  https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.34-3ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1987304/+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 1987928] [NEW] gnome-control-center closes with Gtk Gio Error when trying to access keyboard shortcut details

2022-08-26 Thread Olivier Dierick
Public bug reported:

Hello,

I report this issue on behalf of someone else, I can't use the bug
reporter on the Ubuntu machine.

The same issue has been reported by other people on other places:

Bug report for GNOME:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1728

Bug report for Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008493

--- lsb_release -rd ---
Description:Ubuntu 22.04.1 LTS
Release:22.04
--- end lsb_release -rd ---

--- apt-cache policy gnome-control-center ---
gnome-control-center:
  Installé : 1:41.7-0ubuntu0.22.04.4
  Candidat : 1:41.7-0ubuntu0.22.04.4
 Table de version :
 *** 1:41.7-0ubuntu0.22.04.4 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:41.4-1ubuntu13.2 500
500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 1:41.4-1ubuntu12 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
--- end apt-cache policy gnome-control-center ---

Issue started after update of gnome-control-center on 24 August 2022
(1:41.7-0ubuntu0.22.04.1 → 1:41.7-0ubuntu0.22.04.4)

--- Snippet from /var/log/apt/history.log ---
Start-Date: 2022-08-24  16:56:32
Commandline: /usr/sbin/synaptic
Requested-By: michel (1003)
Upgrade: gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubun
tu0.22.04.4), thunderbird:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.
0+build1-0ubuntu0.22.04.1), libpam-fprintd:amd64 (1.94.2-1, 1.94.2-1ubuntu0.22.0
4.1), isc-dhcp-common:amd64 (4.4.1-2.3ubuntu2.1, 4.4.1-2.3ubuntu2.2), thunderbir
d-locale-en:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+build1-0ubun
tu0.22.04.1), thunderbird-locale-fr:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1
, 1:91.13.0+build1-0ubuntu0.22.04.1), isc-dhcp-client:amd64 (4.4.1-2.3ubuntu2.1,
 4.4.1-2.3ubuntu2.2), fprintd:amd64 (1.94.2-1, 1.94.2-1ubuntu0.22.04.1), gnome-c
ontrol-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.4), gno
me-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.4), thun
derbird-locale-en-gb:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+bui
ld1-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 (1:91.12.0+build1-0ubuntu0
.22.04.1~mt1, 1:91.13.0+build1-0ubuntu0.22.04.1), thunderbird-gnome-support:amd6
4 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+build1-0ubuntu0.22.04.1)
End-Date: 2022-08-24  16:57:15
--- end /var/log/apt/history.log ---

The user opens gnome-control-center, the main window appears.
The user selects the keyboard tab and click on the arrow to open the keyboard 
shortcut binding interface.

The user expects the interface for binding keyboard shortcuts to open.

Instead, the main gnome-control-center window closes and outputs the
following error in the terminal:

--- output of gnome-control-center ---

(gnome-control-center: 647357): GLib-GIO-ERROR **: 00:31:19.451: Settings 
schema 'org.gnome.settin
gs-daemon.plugins.media-keys' does not contain a key named 'screenshot'
Trappe pour point d'arrêt et de trace (core dumped)
--- end output of gnome-control-center ---

It was working some time before the update to 1:41.7-0ubuntu0.22.04.4.

Downgrading the package to 1:41.4-1ubuntu13.2 doesn't fix the issue.

Regards.

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

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

Title:
  gnome-control-center closes with Gtk Gio Error when trying to access
  keyboard shortcut details

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

Bug description:
  Hello,

  I report this issue on behalf of someone else, I can't use the bug
  reporter on the Ubuntu machine.

  The same issue has been reported by other people on other places:

  Bug report for GNOME:
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1728

  Bug report for Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008493

  --- lsb_release -rd ---
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  --- end lsb_release -rd ---

  --- apt-cache policy gnome-control-center ---
  gnome-control-center:
Installé : 1:41.7-0ubuntu0.22.04.4
Candidat : 1:41.7-0ubuntu0.22.04.4
   Table de version :
   *** 1:41.7-0ubuntu0.22.04.4 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:41.4-1ubuntu13.2 500
  500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:41.4-1ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  --- end apt-cache policy gnome-control-center ---

  Issue started after update of gnome-control-center on 24 August 2022
  (1:41.7-0ubuntu0.22.04.1 → 1:41.7-0ubuntu0.22.04.4)

  --- Snippet from /var/log/apt/history.log ---

[Desktop-packages] [Bug 1987624] Re: Temporarily hold evolution-data-server in -proposed

2022-08-26 Thread Jeremy Bicha
** No longer affects: gnome-online-accounts (Ubuntu)

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

Title:
  Temporarily hold evolution-data-server in -proposed

Status in evolution-data-server package in Ubuntu:
  Triaged

Bug description:
  Maybe I needed to add more explicit Breaks in the packaging?

  But if evolution-data-server smoothly migrates, I fear that several
  packages including key ones like gnome-shell won't run because apps
  can't use both libsoup2 and libsoup3 in the same process.

  So I'm filing a blocker bug for now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1987624/+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 1987926] Re: Hot corner doesn't work, also can't invoke hidden dock with the mouse

2022-08-26 Thread Jeremy Bicha
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2394
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2394

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

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

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

** Summary changed:

- Hot corner doesn't work, also can't invoke hidden dock with the mouse
+ 43: Hot corner doesn't work, also can't invoke hidden dock with the mouse

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

Title:
  43: Hot corner doesn't work, also can't invoke hidden dock with the
  mouse

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

Bug description:
  Ubuntu, gnome, nvidia with proprietary drivers.
  After updating mutter to 43 beta, my top corner stopped functioning as a 
mouse hotspot even though it is defined as such in "Multitasking" settings: I 
need to click "Activities" manually to invoke the window picker. Also, when 
choosing to auto-hide the dock on "Ubuntu Desktop" settings, the dock is 
permanently hidden and cannot be display by moving the mouse to its screen edge.

  This was also reported upstream:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2394

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 27 00:51:49 2022
  InstallationDate: Installed on 2022-01-31 (207 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to kinetic on 2022-06-29 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1987926/+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 1987926] [NEW] Hot corner doesn't work, also can't invoke hidden dock with the mouse

2022-08-26 Thread Yotam Benshalom
Public bug reported:

Ubuntu, gnome, nvidia with proprietary drivers.
After updating mutter to 43 beta, my top corner stopped functioning as a mouse 
hotspot even though it is defined as such in "Multitasking" settings: I need to 
click "Activities" manually to invoke the window picker. Also, when choosing to 
auto-hide the dock on "Ubuntu Desktop" settings, the dock is permanently hidden 
and cannot be display by moving the mouse to its screen edge.

This was also reported upstream:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2394

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: mutter (not installed)
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 27 00:51:49 2022
InstallationDate: Installed on 2022-01-31 (207 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
SourcePackage: mutter
UpgradeStatus: Upgraded to kinetic on 2022-06-29 (58 days ago)

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


** Tags: amd64 apport-bug kinetic regression-release

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

Title:
  Hot corner doesn't work, also can't invoke hidden dock with the mouse

Status in mutter package in Ubuntu:
  New

Bug description:
  Ubuntu, gnome, nvidia with proprietary drivers.
  After updating mutter to 43 beta, my top corner stopped functioning as a 
mouse hotspot even though it is defined as such in "Multitasking" settings: I 
need to click "Activities" manually to invoke the window picker. Also, when 
choosing to auto-hide the dock on "Ubuntu Desktop" settings, the dock is 
permanently hidden and cannot be display by moving the mouse to its screen edge.

  This was also reported upstream:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2394

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 27 00:51:49 2022
  InstallationDate: Installed on 2022-01-31 (207 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to kinetic on 2022-06-29 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987926/+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 1987925] [NEW] /usr/libexec/boltd:6:__GI___poll:g_main_context_poll:g_main_context_iterate:g_main_loop_run:main

2022-08-26 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bolt.  This problem was most recently seen with package version 0.9.2-1, the 
problem page at 
https://errors.ubuntu.com/problem/ece50fad74eb7b73e5a77df971e6830839fd0ca6 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: focal hirsute impish jammy

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

Title:
  
/usr/libexec/boltd:6:__GI___poll:g_main_context_poll:g_main_context_iterate:g_main_loop_run:main

Status in bolt package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bolt.  This problem was most recently seen with package version 0.9.2-1, the 
problem page at 
https://errors.ubuntu.com/problem/ece50fad74eb7b73e5a77df971e6830839fd0ca6 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1987925/+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 1987711] Re: Ubuntu display get shifted after some time.

2022-08-26 Thread Ivan Krasicenko
I restarted pc, and this error occured again today at 1AM. i.e. 26.8.2022 
01:18:34 +- 1second. 
logs should be in attachment. 

** Attachment added: "errLog.zip"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1987711/+attachment/5611969/+files/errLog.zip

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

Title:
  Ubuntu display get shifted after some time.

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  It is continuation of this bug:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583
  where advised fix was applied. 

  Summay: After ubuntu is turned on, after some time screen gets shifted
  to side. (and starts to overlap)

  I setup webcamera to record screen, and video below shows what it looked 
like. 
  after fix were applied.
  www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4
  (video was cropped, and slowed down 2x)

  before fix was applied shift looked somehow like this:
  www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4
  (video is also cropped, and slowed down 2x)

  During shift no one was present on computer.

  Is there any idea how to enable some more detailed log or something? I 
probably can pinpoint exact moment in time when shift happened. 
  i tried to read log journalctl, but I found nothing interesting.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  Date: Fri Aug 26 02:31:10 2022
  DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015]
  InstallationDate: Installed on 2022-02-17 (189 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen
   Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Default string Default string
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago)
  dmi.bios.date: 10/07/2021
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GSKU0504.V54
  dmi.board.asset.tag: Default string
  dmi.board.name: SKYBAY
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/xorg-server/+bug/1987711/+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 1987711] Re: Ubuntu display get shifted after some time.

2022-08-26 Thread Ivan Krasicenko
-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1987711

Title:
  Ubuntu display get shifted after some time.

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  It is continuation of this bug:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583
  where advised fix was applied. 

  Summay: After ubuntu is turned on, after some time screen gets shifted
  to side. (and starts to overlap)

  I setup webcamera to record screen, and video below shows what it looked 
like. 
  after fix were applied.
  www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4
  (video was cropped, and slowed down 2x)

  before fix was applied shift looked somehow like this:
  www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4
  (video is also cropped, and slowed down 2x)

  During shift no one was present on computer.

  Is there any idea how to enable some more detailed log or something? I 
probably can pinpoint exact moment in time when shift happened. 
  i tried to read log journalctl, but I found nothing interesting.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  Date: Fri Aug 26 02:31:10 2022
  DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015]
  InstallationDate: Installed on 2022-02-17 (189 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen
   Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Default string Default string
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago)
  dmi.bios.date: 10/07/2021
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GSKU0504.V54
  dmi.board.asset.tag: Default string
  dmi.board.name: SKYBAY
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/xorg-server/+bug/1987711/+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 1987919] [NEW] Cannot open gnome-extension in ubuntu 22.04

2022-08-26 Thread Gaurav Pandey
Public bug reported:

I've installed nvidia-driver-515 and getting this error
Gdk-Message: 02:08:03.792: Error reading events from display: Protocol error

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: 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/1987919

Title:
  Cannot open gnome-extension in ubuntu 22.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I've installed nvidia-driver-515 and getting this error
  Gdk-Message: 02:08:03.792: Error reading events from display: Protocol error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987919/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

2022-08-26 Thread Dominic Parry
I bare good news, On 22.10 current build for desktop, this issue no
longer is valid as it will be resolved! No more garbled mess. I have
been looking about but perhaps the fixes there can be applied to jammy.

Been testing 22.10 :D

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  On the jammy Pi desktop, under a wayland session, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 1978988] Re: [USB-Audio - USB Audio, recording] Recording problem

2022-08-26 Thread WHK
For Alsa UCM related issuse:

- https://github.com/alsa-project/alsa-ucm-conf/issues/172
- https://github.com/alsa-project/alsa-ucm-conf/issues/186
- https://github.com/alsa-project/alsa-ucm-conf/issues/189

** Bug watch added: github.com/alsa-project/alsa-ucm-conf/issues #172
   https://github.com/alsa-project/alsa-ucm-conf/issues/172

** Bug watch added: github.com/alsa-project/alsa-ucm-conf/issues #186
   https://github.com/alsa-project/alsa-ucm-conf/issues/186

** Bug watch added: github.com/alsa-project/alsa-ucm-conf/issues #189
   https://github.com/alsa-project/alsa-ucm-conf/issues/189

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

Title:
  [USB-Audio - USB Audio, recording] Recording problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  My Motherboard is MSI X570S and output audio works fine but:

  - Motherboard microphone plug is not work.
  - Frontal microphone plug is not work.
  - When change output from gnome settings to hdmi audio does not work, the 
audio continues to play in the plug and not in the monitor.
  - When I change the input or output from digital to analog or sinput it does 
not change at all.
  - The strangest thing is that the microphone input captures the audio that is 
heard in the system as if it were the output, audacious records the audio from 
the desktop when it tries to monitor the microphone.
  - When plugging or unplugging the microphone, the system detects this change 
and tries to change the audio input automatically, but it does not capture the 
microphone and the desktop continues to be heard.

  My alsa data: http://alsa-
  project.org/db/?f=df4d1f6c126260eabc5f159e64cff37efa064a38

  MSI have not audio drivers for linux. I can't stream with this
  motherboard because the microphone doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whk1940 F pulseaudio
   /dev/snd/pcmC1D0c:   whk1940 F...m pulseaudio
   /dev/snd/pcmC1D0p:   whk1940 F...m pulseaudio
   /dev/snd/controlC0:  whk1940 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 16 13:13:20 2022
  InstallationDate: Installed on 2022-06-13 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed
  Symptom_Card: HDA-Intel - HD-Audio Generic
  Symptom_Type: Only some of inputs are working
  Title: [USB-Audio - USB Audio, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.31
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MPG X570S EDGE MAX WIFI (MS-7D53)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.31:bd05/19/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D53:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570SEDGEMAXWIFI(MS-7D53):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7D53
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1978988/+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 1978988] Re: [USB-Audio - USB Audio, recording] Recording problem

2022-08-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [USB-Audio - USB Audio, recording] Recording problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  My Motherboard is MSI X570S and output audio works fine but:

  - Motherboard microphone plug is not work.
  - Frontal microphone plug is not work.
  - When change output from gnome settings to hdmi audio does not work, the 
audio continues to play in the plug and not in the monitor.
  - When I change the input or output from digital to analog or sinput it does 
not change at all.
  - The strangest thing is that the microphone input captures the audio that is 
heard in the system as if it were the output, audacious records the audio from 
the desktop when it tries to monitor the microphone.
  - When plugging or unplugging the microphone, the system detects this change 
and tries to change the audio input automatically, but it does not capture the 
microphone and the desktop continues to be heard.

  My alsa data: http://alsa-
  project.org/db/?f=df4d1f6c126260eabc5f159e64cff37efa064a38

  MSI have not audio drivers for linux. I can't stream with this
  motherboard because the microphone doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whk1940 F pulseaudio
   /dev/snd/pcmC1D0c:   whk1940 F...m pulseaudio
   /dev/snd/pcmC1D0p:   whk1940 F...m pulseaudio
   /dev/snd/controlC0:  whk1940 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 16 13:13:20 2022
  InstallationDate: Installed on 2022-06-13 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed
  Symptom_Card: HDA-Intel - HD-Audio Generic
  Symptom_Type: Only some of inputs are working
  Title: [USB-Audio - USB Audio, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.31
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MPG X570S EDGE MAX WIFI (MS-7D53)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.31:bd05/19/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D53:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570SEDGEMAXWIFI(MS-7D53):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7D53
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1978988/+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 1987409] Re: All open applications close after "screen blank" in Ubuntu 22.04 using Wayland

2022-08-26 Thread Daren Swasey
@vanvugt The first option you gave me didn't work, so I included the
links to the errors in the main body of my original bug description as
per the second option you listed.

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

Title:
  All open applications close after "screen blank" in Ubuntu 22.04 using
  Wayland

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Version: 22.04
  gnome-shell Version: 42.2-0ubuntu0.2

  
  What I Expected to Happen:
  After user inactivity, computer goes into a locked state. When I log back in 
after user inactivity, all my previously opened applications are still running.

  
  What Actually Happened:
  After user inactivity, all my applications in my session are closed after 
logging back in.

  
  Details:
  This occurred on a workstation that was wiped of its previous data and Ubuntu 
22.04 installed from a flashdrive. I am getting very similar results to a bug 
in:
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987209

  
  About my system (from About menu in Settings)

  - Dell OptiPlex 3050
  - 32 GB RAM
  - Intel® Core™ i7-7700 CPU @ 3.60GHz × 8
  - AMD® Radeon rx 550 / 550 series / Mesa Intel® HD Graphics 630 (KBL GT2)
  - GNOME Version: 42.2

  Monitors being used:
  - Dell U2211Ht 22"
  - Acer G226HQL 22"
  - LG 32MA68HY 27"

  I have reproduced this error by setting the 'Screen Blank' setting to
  1 minute (just so I don't have to wait very long), then waiting for
  the system to enter the screen blank state. The following then
  happens.

  1. Everything seems to be fading out as normal
  2. Screens no longer have data that needs to be displayed, they go into sleep 
mode
  3. After a brief period, screens are forced back on (where when this problem 
isn't happening, screens will remain in sleep mode until input provided by user)
  4. System displays the dark login screen as if I was never logged in.
  5. After signing in, all my open applications have been closed.

  I have managed to circumvent this issue by choosing the option
  'Ubuntu on xorg' before signing in, or by uncommenting the line

  #WaylandEnable=false

  in /etc/gdm3/custom.conf. I then repeat the test described above after
  using either of these methods and my session is saved, no issues.

  I have attached my own results that I found after a 'journalctl -b0'.
  The text in the file are some of the lines before and after the line:

  gnome-shell[]: segfault at 

  
  Links to error reports (I got a bunch trying to replicate the issue):
  - https://errors.ubuntu.com/oops/f429c99a-2262-11ed-978c-fa163e993415
  - https://errors.ubuntu.com/oops/a07c3a5c-225e-11ed-978c-fa163e993415
  - https://errors.ubuntu.com/oops/4b027458-225c-11ed-978c-fa163e993415
  - https://errors.ubuntu.com/oops/d1cc8831-225a-11ed-978c-fa163e993415
  - https://errors.ubuntu.com/oops/cd660830-225a-11ed-b154-fa163ef35206

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 23 08:36:52 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-08-16 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987409/+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 1987330] Re: Dock click action "previews" focuses instead

2022-08-26 Thread John Barrett
Thanks for your comment, but I think I might not have explained myself
clearly in the initial bug report.

The behaviour you describe in your second paragraph (focus if one
window, preview if multiple) is what I want and what the code implies
should happen, but isn't what's happening. Rather, (on my system at
least) click-action previews ALWAYS focuses first regardless of the
number of windows.

This can be seen in the video I attached, where the first click focuses
one of the terminal windows even though there are two open, and the
previews only show up on the second click.

Basically previews mode seems to be acting exactly the same as focus-or-
previews, which doesn't seem right.

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

Title:
  Dock click action "previews" focuses instead

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

Bug description:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.1
Candidate: 72~ubuntu5.22.04.1
Version table:
   *** 72~ubuntu5.22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

  With the Ubuntu dock click-action set to previews, focusing on one
  program then clicking on the icon of a different program with multiple
  windows focuses the most recently used window from that program
  instead of showing the previews.

  Steps to reproduce:-

  1) Open multiple Terminal windows (or any program I guess, but I used 
Terminal and Firefox for testing)
  2) Open Firefox
  3) Click on the Terminal icon in the dock

  Expected behaviour:

  Previews for all the Terminal windows are shown

  Actual behaviour:

  The most recent Terminal window is focused.

  Additional info:

  Appears to be a regression of #1947445, which was supposedly fixed in
  version 70 but I'm on version 72. I've tried setting the click-action
  via gsettings and by editing /usr/share/glib-2.0/schemas/10_ubuntu-
  dock.gschema.override (as per #1770405) but neither has any effect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1987330/+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 1975884] Re: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added"

2022-08-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Temporary screen freeze when gnome-shell logs "Removing a network
  device that was not added"

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1769981/comments/25 , I've been observing an issue when
  unlocking my computer (usually from a screen lock state, not
  hibernation/sleep) where after entering the first few characters of my
  password the screen freezes for 10-20 seconds before I can do any type
  of input (mouse, touch, keyboard).

  I've also seen it happen when having touch / gesture input switch
  between displaying the user name and the password field - where the
  screen can get stuck in the animation in an interstitial state for a
  number of seconds.

  I've largely been noticing this since upgrading from Ubuntu 21.10 to
  22.04. It doesn't happen all the time, but often enough to file an
  issue for.

  So far I've tried:
  - Disabling the 'blur my shell' extension - still encountered the issue again 
eventually.
  - Looking for anything associated with this in /var/crash - couldn't find 
anything.
  - Looking for anything associated at errors.ubuntu.com for my id.

  What I may eventually try:
  - Seeing if this may depend on having too many browser tabs / apps open. 
Currently not in a position to do this.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 26 19:19:28 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-07-15 (315 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/+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 1987737] Re: firefox from snap disabled save button in subfolders

2022-08-26 Thread Olivier Tilloy
Can you share the output of the following command:

LANG=C dpkg -l xdg-desktop-portal*

Can you also run the following commands in separate terminals:

/usr/libexec/xdg-desktop-portal-gtk -rv

journalctl -f | grep DEN

and reproduce the problem, then attach the output of both commands here?
Thanks!

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

Title:
  firefox from snap disabled save button in subfolders

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 22.04 fully updated
  2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  3) I expect being able to save a file to folders in my home folder or in a 
usb drive
  4) When selecting a plugged-in USB drive or the home folder I can save, once 
I enter a subfolder the "save" button in the save dialog gets greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop:
   
  Date: Fri Aug 26 10:11:37 2022
  InstallationDate: Installed on 2021-07-14 (407 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987737/+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 1987330] Re: Dock click action "previews" focuses instead

2022-08-26 Thread Treviño
According to the comment in the upstream code this is not what is
expected to happen.

Basically the previews mode is only meant to ALWAYS show the previews
when multiple windows are available, without focusing one first. While
if one window is there, there's no need for the preview.

The behavior you want can be easy achivied by patching the code with:

diff --git a/appIcons.js b/appIcons.js
index d5bcbf2..3cbbd6c 100644
--- a/appIcons.js
+++ b/appIcons.js
@@ -575,7 +575,7 @@ var DockAbstractAppIcon = GObject.registerClass({
 if (!Main.overview.visible) {
 // If only one windows is present just switch to it, but 
only when trigggered with the
 // simple click action (no modifiers, no middle click).
-if (singleOrUrgentWindows && !modifiers && button == 1) {
+if (hasUrgentWindows && !modifiers && button == 1) {
 let w = windows[0];
 Main.activateWindow(w);
 } else


However I'm not sure it should be the default, while you can open a bug 
upstream or request for a further mode that always shows the previews.

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

Title:
  Dock click action "previews" focuses instead

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

Bug description:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.1
Candidate: 72~ubuntu5.22.04.1
Version table:
   *** 72~ubuntu5.22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

  With the Ubuntu dock click-action set to previews, focusing on one
  program then clicking on the icon of a different program with multiple
  windows focuses the most recently used window from that program
  instead of showing the previews.

  Steps to reproduce:-

  1) Open multiple Terminal windows (or any program I guess, but I used 
Terminal and Firefox for testing)
  2) Open Firefox
  3) Click on the Terminal icon in the dock

  Expected behaviour:

  Previews for all the Terminal windows are shown

  Actual behaviour:

  The most recent Terminal window is focused.

  Additional info:

  Appears to be a regression of #1947445, which was supposedly fixed in
  version 70 but I'm on version 72. I've tried setting the click-action
  via gsettings and by editing /usr/share/glib-2.0/schemas/10_ubuntu-
  dock.gschema.override (as per #1770405) but neither has any effect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1987330/+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 1983456] Re: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04

2022-08-26 Thread Treviño
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Context menu options are shown under dock panel and can not be chosen
  on Ubuntu 22.04

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix

Bug description:
  1. Ubuntu 22.04.1 LTS
  2. Installed packeges:
  ...
  gnome-shell-common/jammy-updates,jammy-updates,now 42.2-0ubuntu0.2 all 
[installed,automatic]
  gnome-shell-extension-appindicator/jammy,jammy,now 42-2~fakesync1 all 
[installed,automatic]
  gnome-shell-extension-desktop-icons-ng/jammy-updates,jammy-updates,now 
43-2ubuntu1 all [installed,automatic]
  gnome-shell-extension-ubuntu-dock/jammy-updates,jammy-updates,now 
72~ubuntu5.22.04.1 all [installed,automatic]
  gnome-shell/jammy-updates,now 42.2-0ubuntu0.2 amd64 [installed,automatic]

  3. Expected to choose "Property" option in right-click context menu of a 
folder in file manager.
  4. In some position of file manager's window near middle to bottom of the 
screen, the context menu was shown under dock panel without possibility to 
choose options, the dock hides menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1983456/+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 1987330] Re: Dock click action "previews" focuses instead

2022-08-26 Thread Treviño
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Dock click action "previews" focuses instead

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

Bug description:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.1
Candidate: 72~ubuntu5.22.04.1
Version table:
   *** 72~ubuntu5.22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

  With the Ubuntu dock click-action set to previews, focusing on one
  program then clicking on the icon of a different program with multiple
  windows focuses the most recently used window from that program
  instead of showing the previews.

  Steps to reproduce:-

  1) Open multiple Terminal windows (or any program I guess, but I used 
Terminal and Firefox for testing)
  2) Open Firefox
  3) Click on the Terminal icon in the dock

  Expected behaviour:

  Previews for all the Terminal windows are shown

  Actual behaviour:

  The most recent Terminal window is focused.

  Additional info:

  Appears to be a regression of #1947445, which was supposedly fixed in
  version 70 but I'm on version 72. I've tried setting the click-action
  via gsettings and by editing /usr/share/glib-2.0/schemas/10_ubuntu-
  dock.gschema.override (as per #1770405) but neither has any effect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1987330/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

2022-08-26 Thread David Fontenot
I forgot to add SYSTEM INFO:

$ cat /proc/version
Linux version 5.15.0-46-generic (buildd@lcy02-amd64-115) (gcc (Ubuntu 
11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #49-Ubuntu SMP 
Thu Aug 4 18:03:25 UTC 2022

$ uname -r
5.15.0-46-generic

$ hostnamectl | grep Kernel
Kernel: Linux 5.15.0-46-generic

$ sudo lscpu
Architecture:x86_64
  CPU op-mode(s):32-bit, 64-bit
  Address sizes: 39 bits physical, 48 bits virtual
  Byte Order:Little Endian
CPU(s):  8
  On-line CPU(s) list:   0-7
Vendor ID:   GenuineIntel
  Model name:Intel(R) Core(TM) i7-7700T CPU @ 2.90GHz

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04

2022-08-26 Thread David Fontenot
*** This bug is a duplicate of bug 1949340 ***
https://bugs.launchpad.net/bugs/1949340

I upgraded to Ubuntu 22.04 yesterday and this bug now affects me.

Also, I have Mint Linux (20.3) Cinnamon (5.2.7) on another machine and
it's been like that since day 1 of the installation.

In both versions of the operating system, when using a program (Firefox,
VSCode, and Typora) that generates a Dialogue box, it does not get
focused. This means, you can't just type to use the Dialogue box, you
have to force focus on the window to use it by clicking it.


SYSTEM INFO:
$ cat /proc/version
Linux version 5.15.0-46-generic (buildd@lcy02-amd64-115) (gcc (Ubuntu 
11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #49-Ubuntu SMP 
Thu Aug 4 18:03:25 UTC 2022

$ uname -r
5.15.0-46-generic

$ hostnamectl | grep Kernel
Kernel: Linux 5.15.0-46-generic

$ sudo lscpu
Architecture:x86_64
  CPU op-mode(s):32-bit, 64-bit
  Address sizes: 39 bits physical, 48 bits virtual
  Byte Order:Little Endian
CPU(s):  8
  On-line CPU(s) list:   0-7
Vendor ID:   GenuineIntel
  Model name:Intel(R) Core(TM) i7-7700T CPU @ 2.90GHz

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

Title:
  Save As Dialog Box does not get focus in Ubuntu 22.04

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When using a browser to right click a file and save as, the save as
  window does not get focus, which means you can't just type the name of
  the file you want, you have to force focus onto the window to use it
  by clicking it.

  This defeats the entire purpose of 2 built in features, 1 being the
  pre-selected original file name (since you can't rename until you re-
  aquire focus for that window, thereby undoing the pre-selection
  programmed in) and 2, the ability to quickly save the file with a
  keystroke.

  A side note to this, ubuntu-bug should have an option to report bugs
  with other WITHOUT having to specify a package. This is a bug in
  ubuntu-bug. Not a feature. Because we don't always know what
  package(s) are involved. This needs to be addressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.8
  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-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 13 07:55:24 2022
  InstallationDate: Installed on 2022-03-31 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968887/+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 1987706] Re: [FFe] Should preinstall network-manager-openconnect-gnome

2022-08-26 Thread Luís Cunha dos Reis Infante da Câmara
** Description changed:

  The ubuntu-desktop package should recommend network-manager-openconnect-
  gnome, that is undergoing a main inclusion review (MIR) at bug #1986592.
  
- I believe this deserves a feature freeze exception because it adds support to 
UBuntu for several types of 
- enterprise VPNs in wide use.
+ I believe this deserves a feature freeze exception because it adds
+ support to Ubuntu for several types of enterprise VPNs in wide use.

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

Title:
  [FFe] Should preinstall network-manager-openconnect-gnome

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  The ubuntu-desktop package should recommend network-manager-
  openconnect-gnome, that is undergoing a main inclusion review (MIR) at
  bug #1986592.

  I believe this deserves a feature freeze exception because it adds
  support to Ubuntu for several types of enterprise VPNs in wide use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1987706/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

2022-08-26 Thread David Fontenot
I upgraded to Ubuntu 22.04 yesterday and this bug now affects me.

Also, I have Mint Linux (20.3) Cinnamon (5.2.7) on another machine and
its been like that since day 1 of the install.

In both versions of the operating system, when using a browser to right-
click a file and "save as", the Save As Dialogue box does not get focus.
This means, you can't just type the name of the file you want, you have
to force focus on the Save As Dialogue box to use it by clicking it.

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1987835] Re: gjs-console crashed with SIGABRT in g_assertion_message_expr()

2022-08-26 Thread Apport retracing service
*** This bug is a duplicate of bug 1986455 ***
https://bugs.launchpad.net/bugs/1986455

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 #1986455, 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/1987835/+attachment/5611860/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1986455

** 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 gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1987835

Title:
  gjs-console crashed with SIGABRT in g_assertion_message_expr()

Status in gjs package in Ubuntu:
  New

Bug description:
  N?A

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gjs 1.73.1-2
  Uname: Linux 5.19.2-051902-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 26 08:45:16 2022
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2021-10-01 (329 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  ProcCmdline: /usr/bin/gjs /usr/bin/gnome-characters --gapplication-service
  ProcEnviron:
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: gjs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
  Title: gjs-console crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to kinetic on 2022-05-14 (104 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1987835/+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 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-26 Thread Douglas E Engert
This maybe the biggest problem:
"- /usr inside the snap is a bind-mount from /usr in the base snap, not on the 
host system, which explains why your addition of `/usr/lib/x86_64-linux-gnu/** 
rm,` to the apparmor profile doesn't work as you'd expect (see 
https://github.com/snapcore/snapd/pull/11025#issuecomment-1225787194 for 
details)"

Are both of you saying that the location of the PKCS11 module makes a 
difference?
And if the normal location is in /usr/lib/x86_64-linux-gnu is part of the FF 
snap package and 
their is no way to include files from the local system's 
/usr/lib/x86_64-linux-gnu.
So is that what the copying to the /usr/run//doc is trying to overcome? 

There are many PKCS11 modules out there, some provided by smartcard vendors and 
not part of a distro.
OpenSC is distributed Ubuntu and most other distros. How will you handle these 
other modules?


What package has the /usr/lib/bit4id/libbit4xpki.so? 

can you run "ldd /usr/lib/bit4id/libbit4xpki.so" to see what other libs are 
required?
Does it use a socket to pcscd?

Is it possible some other libs must also be included?

Can you try to install opensc-pkcs11 (which also installs opensc) to
your system and see you can get FF to load it?

opensc-pkcs11-0.22.0-1ubuntu2 installs opensc-pkcs11.so in two places: 
/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so and 
/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so (which is were p11-kit would 
load it)
and depends on libopensc.so.8  and /usr/lib/x86_64-linux-gnu/libcrypto.so.3 
from libssl3-3.0.2-0ubuntu1.6


 $ ls -l /usr/lib/x86_64-linux-gnu/*opensc*
lrwxrwxrwx 1 root root  18 Mar 10 11:00 
/usr/lib/x86_64-linux-gnu/libopensc.so.8 -> libopensc.so.8.0.0
-rw-r--r-- 1 root root 2040208 Mar 10 11:00 
/usr/lib/x86_64-linux-gnu/libopensc.so.8.0.0
-rw-r--r-- 1 root root  234704 Mar 10 11:00 
/usr/lib/x86_64-linux-gnu/onepin-opensc-pkcs11.so
-rw-r--r-- 1 root root  234704 Mar 10 11:00 
/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
$ ldd /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
linux-vdso.so.1 (0x7ffcbbdfe000)
libopensc.so.8 => /lib/x86_64-linux-gnu/libopensc.so.8 
(0x7efd3cd14000)
libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 
(0x7efd3c8d2000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7efd3c6aa000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7efd3c68e000)
libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7efd3c4b6000)
libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7efd3c456000)
/lib64/ld-linux-x86-64.so.2 (0x7efd3cf58000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7efd3c31a000)
libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7efd3c313000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 
(0x7efd3c2cf000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7efd3c2a3000)
libffi.so.8 => /lib/x86_64-linux-gnu/libffi.so.8 (0x7efd3c296000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7efd3c21e000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7efd3c137000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 
(0x7efd3c10)
libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 
(0x7efd3c069000)

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 

[Desktop-packages] [Bug 1987001] Re: netplan.io autopkgtest failures with NetworkManager 1.39.90

2022-08-26 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.39.90-1ubuntu3

---
network-manager (1.39.90-1ubuntu3) kinetic; urgency=medium

  * Cherry-pick 2 patches to fix bonding regressions discovered
with failing netplan autopkgtests. Thanks Lukas Märdian.
(LP: #1987001)

 -- Jeremy Bicha   Thu, 25 Aug 2022 13:26:02 -0400

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  netplan.io autopkgtest failures with NetworkManager 1.39.90

Status in NetworkManager:
  Unknown
Status in netplan.io package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  netplan.io's autopkgtests are failing with NetworkManager 1.40 RC1
  (1.39.90).

  https://autopkgtest.ubuntu.com/packages/n/netplan.io/kinetic/amd64

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-40/NEWS

  log excerpt:

  ==
  FAIL: test_bond_mode_8023ad_adselect (__main__.TestNetworkManager)
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", 
line 147, in test_bond_mode_8023ad_adselect
  self.assertEqual(f.read().strip(), 'bandwidth 1')
  AssertionError: 'stable 0' != 'bandwidth 1'
  - stable 0
  + bandwidth 1

  
  ==
  FAIL: test_bond_mode_balance_tlb_learn_interval (__main__.TestNetworkManager)
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", 
line 670, in test_bond_mode_balance_tlb_learn_interval
  self.assertEqual(f.read().strip(), '15')
  AssertionError: '1' != '15'
  - 1
  + 15
  ?  +

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1987001/+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 1987833] [NEW] xdg-desktop-portal bails if DISPLAY is not set

2022-08-26 Thread Michał Sawicz
Public bug reported:

When DISPLAY is not set (which would be the case for a Wayland-only
session), xdg-desktop-portal bails with:

> xdg-desktop-portal[500395]: Error: no DISPLAY environment variable
specified

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-desktop-portal 1.14.4-1ubuntu2~22.04.1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Aug 26 13:09:33 2022
InstallationDate: Installed on 2022-04-29 (118 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: xdg-desktop-portal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xdg-desktop-portal (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  xdg-desktop-portal bails if DISPLAY is not set

Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  When DISPLAY is not set (which would be the case for a Wayland-only
  session), xdg-desktop-portal bails with:

  > xdg-desktop-portal[500395]: Error: no DISPLAY environment variable
  specified

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal 1.14.4-1ubuntu2~22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Aug 26 13:09:33 2022
  InstallationDate: Installed on 2022-04-29 (118 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: xdg-desktop-portal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1987833/+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 1987737] Re: firefox from snap disabled save button in subfolders

2022-08-26 Thread Alejandro R. Mosteo
Yes, it happens with any folder under my home folder, including the
'Downloads' one.

I'm using stock Ubuntu with the default Gnome shell.

This is an upgraded system since at least 18.04, via 20.04.

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

Title:
  firefox from snap disabled save button in subfolders

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 22.04 fully updated
  2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  3) I expect being able to save a file to folders in my home folder or in a 
usb drive
  4) When selecting a plugged-in USB drive or the home folder I can save, once 
I enter a subfolder the "save" button in the save dialog gets greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop:
   
  Date: Fri Aug 26 10:11:37 2022
  InstallationDate: Installed on 2021-07-14 (407 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987737/+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 1987737] Re: firefox from snap disabled save button in subfolders

2022-08-26 Thread Olivier Tilloy
Can you observe the problem also for subfolders of your $HOME ?
What's your desktop environment?

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

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

Title:
  firefox from snap disabled save button in subfolders

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 22.04 fully updated
  2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  3) I expect being able to save a file to folders in my home folder or in a 
usb drive
  4) When selecting a plugged-in USB drive or the home folder I can save, once 
I enter a subfolder the "save" button in the save dialog gets greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop:
   
  Date: Fri Aug 26 10:11:37 2022
  InstallationDate: Installed on 2021-07-14 (407 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987737/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

2022-08-26 Thread Dominic Parry
I think this is to do with the hardware (probably 3D) acceleration under
OpenGL since the effect is reproducable by installing virt-manager,
setting the type to SPICE instead of VNC and then enabling OpenGL
hadware accelerated rendering (3d acceleration as it might be called.)

Thus, I believe that this is not limited to just webkit. You may also
need to make sure that your MESA_GL_VERSION_OVERRIDE environment
variable is set to 3.2 of you are experiancing issues related to "failed
to create a GL context" as totem and other apps will experiance this
issue.

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  On the jammy Pi desktop, under a wayland session, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 1882880] Re: FP Auth enroll screen issue: Max limit not defined

2022-08-26 Thread Sebastien Bacher
thanks, closing

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

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

Title:
  FP Auth enroll screen issue: Max limit not defined

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  We are able to enroll FP's even after Max limit is reached (10). (No
  error like 'Max limit is reached' is observed). So we are able to
  enroll the same fingers again and again with any number of times.

  The release of Ubuntu : Ubuntu 20.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882880/+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 1882880] Re: FP Auth enroll screen issue: Max limit not defined

2022-08-26 Thread prafulla chandra kota
Verified on Jammy 22.04, duplicate finger functionality is implemented,
defect can be closed.

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

Title:
  FP Auth enroll screen issue: Max limit not defined

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

Bug description:
  We are able to enroll FP's even after Max limit is reached (10). (No
  error like 'Max limit is reached' is observed). So we are able to
  enroll the same fingers again and again with any number of times.

  The release of Ubuntu : Ubuntu 20.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882880/+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 1987792] [NEW] Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers

2022-08-26 Thread Michel-Ekimia
Public bug reported:

Sony laptop with AMD RV710

Try to play a DVD with Vaapi mesa drivers installed

ALl players crash , example with VLC (  Works great without VAAPI )

libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
[7fd5d8085d50] main generic debug: using glconv module "glconv_vaapi_drm"
[7fd5d8001610] main vout display debug: using vout display module "gl"
[7fd5d4039c20] main window debug: resized to 768x576
[7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576
[7fd5d4028010] main video output debug: original format sz 720x576, of 
(0,0), vsz 720x576, 4cc VAOP, sar 16:15, msk r0x0 g0x0 b0x0
[7fd5d4029610] main spu text debug: removing module "freetype"
[7fd5d4072b40] main spu text debug: looking for text renderer module 
matching "any": 2 candidates
[7fd5d4072b40] freetype spu text debug: Building font databases.
[5601ed37aed0] qt interface debug: Logical video size: 768x576
[7fd5d4039c20] main window debug: resized to 768x576
[7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576
[7fd5d4072b40] freetype spu text debug: Took -23713 microseconds
[7fd5d4072b40] main spu text debug: using text renderer module "freetype"
[7fd5d409d080] main generic debug: looking for hw decoder module matching 
"vaapi": 3 candidates
[7fd5d409d080] main generic debug: using hw decoder module "vaapi"
[7fd5d004efb0] avcodec decoder: Using Mesa Gallium driver 22.0.5 for AMD 
RV710 (DRM 2.50.0 / 5.15.0-46-generic, LLVM 13.0.1) for hardware decoding
[mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld chosen by get_format().
[mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld requires hwaccel initialisation.
[mpeg2video @ 0x7fd5d4087d80] Using deprecated struct vaapi_context in decode.
[mpeg2video @ 0x7fd5d4087d80] Using user-supplied decoder context: 0x15/0x16.
[mpeg2video @ 0x7fd5d4087d80] Param buffer (type 0, 40 bytes) is 0x17.
[mpeg2video @ 0x7fd5d4087d80] Param buffer (type 1, 288 bytes) is 0x18.
[mpeg2video @ 0x7fd5d4087d80] Slice 0 param buffer (48 bytes) is 0x19.
[mpeg2video @ 0x7fd5d4087d80] Slice 0 data buffer (176 bytes) is 0x1a.
[mpeg2video @ 0x7fd5d4087d80] Slice 1 param buffer (48 bytes) is 0x1b.
[mpeg2video @ 0x7fd5d4087d80] Slice 1 data buffer (175 bytes) is 0x1c.
[mpeg2video @ 0x7fd5d4087d80] Slice 2 param buffer (48 bytes) is 0x1d.
[mpeg2video @ 0x7fd5d4087d80] Slice 2 data buffer (175 bytes) is 0x1e.
[mpeg2video @ 0x7fd5d4087d80] Slice 3 param buffer (48 bytes) is 0x1f.
[mpeg2video @ 0x7fd5d4087d80] Slice 3 data buffer (175 bytes) is 0x20.
[mpeg2video @ 0x7fd5d4087d80] Slice 4 param buffer (48 bytes) is 0x21.
[mpeg2video @ 0x7fd5d4087d80] Slice 4 data buffer (175 bytes) is 0x22.
[mpeg2video @ 0x7fd5d4087d80] Slice 5 param buffer (48 bytes) is 0x23.
[mpeg2video @ 0x7fd5d4087d80] Slice 5 data buffer (175 bytes) is 0x24.
[mpeg2video @ 0x7fd5d4087d80] Slice 6 param buffer (48 bytes) is 0x25.
[mpeg2video @ 0x7fd5d4087d80] Slice 6 data buffer (175 bytes) is 0x26.
[mpeg2video @ 0x7fd5d4087d80] Slice 7 param buffer (48 bytes) is 0x27.
[mpeg2video @ 0x7fd5d4087d80] Slice 7 data buffer (175 bytes) is 0x28.
[mpeg2video @ 0x7fd5d4087d80] Slice 8 param buffer (48 bytes) is 0x29.
[mpeg2video @ 0x7fd5d4087d80] Slice 8 data buffer (175 bytes) is 0x2a.
[mpeg2video @ 0x7fd5d4087d80] Slice 9 param buffer (48 bytes) is 0x2b.
[mpeg2video @ 0x7fd5d4087d80] Slice 9 data buffer (175 bytes) is 0x2c.
[mpeg2video @ 0x7fd5d4087d80] Slice 10 param buffer (48 bytes) is 0x2d.
[mpeg2video @ 0x7fd5d4087d80] Slice 10 data buffer (175 bytes) is 0x2e.
[mpeg2video @ 0x7fd5d4087d80] Slice 11 param buffer (48 bytes) is 0x2f.
[mpeg2video @ 0x7fd5d4087d80] Slice 11 data buffer (175 bytes) is 0x30.
[mpeg2video @ 0x7fd5d4087d80] Slice 12 param buffer (48 bytes) is 0x31.
[mpeg2video @ 0x7fd5d4087d80] Slice 12 data buffer (175 bytes) is 0x32.
[mpeg2video @ 0x7fd5d4087d80] Slice 13 param buffer (48 bytes) is 0x33.
[mpeg2video @ 0x7fd5d4087d80] Slice 13 data buffer (175 bytes) is 0x34.
[mpeg2video @ 0x7fd5d4087d80] Slice 14 param buffer (48 bytes) is 0x35.
[mpeg2video @ 0x7fd5d4087d80] Slice 14 data buffer (175 bytes) is 0x36.
[mpeg2video @ 0x7fd5d4087d80] Slice 15 param buffer (48 bytes) is 0x37.
[mpeg2video @ 0x7fd5d4087d80] Slice 15 data buffer (571 bytes) is 0x38.
[mpeg2video @ 0x7fd5d4087d80] Slice 16 param buffer (48 bytes) is 0x39.
[mpeg2video @ 0x7fd5d4087d80] Slice 16 data buffer (7664 bytes) is 0x3a.
[mpeg2video @ 0x7fd5d4087d80] Slice 17 param buffer (48 bytes) is 0x3b.
[mpeg2video @ 0x7fd5d4087d80] Slice 17 data buffer (1387 bytes) is 0x3c.
[mpeg2video @ 0x7fd5d4087d80] Slice 18 param buffer (48 bytes) is 0x3d.
[mpeg2video @ 0x7fd5d4087d80] Slice 18 data buffer (7428 bytes) is 0x3e.
[mpeg2video @ 0x7fd5d4087d80] Slice 19 param buffer (48 bytes) is 0x3f.
[mpeg2video @ 0x7fd5d4087d80] Slice 19 data 

[Desktop-packages] [Bug 1987737] [NEW] firefox from snap disabled save button in subfolders

2022-08-26 Thread Alejandro R. Mosteo
Public bug reported:

1) Ubuntu 22.04 fully updated
2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
3) I expect being able to save a file to folders in my home folder or in a usb 
drive
4) When selecting a plugged-in USB drive or the home folder I can save, once I 
enter a subfolder the "save" button in the save dialog gets greyed out.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop:
 
Date: Fri Aug 26 10:11:37 2022
InstallationDate: Installed on 2021-07-14 (407 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
SourcePackage: firefox
UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

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


** Tags: amd64 apport-bug jammy

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

Title:
  firefox from snap disabled save button in subfolders

Status in firefox package in Ubuntu:
  New

Bug description:
  1) Ubuntu 22.04 fully updated
  2) Firefox snap id 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  3) I expect being able to save a file to folders in my home folder or in a 
usb drive
  4) When selecting a plugged-in USB drive or the home folder I can save, once 
I enter a subfolder the "save" button in the save dialog gets greyed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop:
   
  Date: Fri Aug 26 10:11:37 2022
  InstallationDate: Installed on 2021-07-14 (407 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (1 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-07-14T15:11:35.001074

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987737/+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 1887296] Re: Moving popup windows drags the application's main window behind it

2022-08-26 Thread Daniel van Vugt
** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/443
   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/1887296

Title:
  Moving popup windows drags the application's main window behind it

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

Bug description:
  Sometimes programs open a "popup" or a "secondary", "child" window, I
  don't know what the word is.

  For example, in Chrome, if I right-click on an image in a web page and
  choose "Save As", this will open a new file browser window that allows
  me to browse for a directory to save the image to.

  Until Ubuntu 16.04, I could move that child window around by dragging
  it by its title bar, and that would not move around the parent window
  behind it.

  Now, it does. That is, the "parent" window greyes out, and moving the
  "child" window (i.e. the popup) on the foreground causes the parent
  window in the background to move as if they were glued together.

  In the above example, if I drag around the "Save As" window, the
  Chrome window behind it moves too. Even worse, if the parent window is
  maximized, it will "oppose resistance" to the dragging of the popup
  window, and if I drag far enough, the parent window will unmaximize
  and unblock the movement of both windows.

  It's pure madness.

  
  I can't imagine a scenario where this is the unavoidable consequence of some 
improvement. It looks like it is by design.

  Why?

  What were you thinking? Why do you ACTIVELY work to degrade usability
  and make the users' life miserable??

  
  Here's a very real-life example:

  As mentioned above, I right-click on something in the browser (like an
  image or a video) and do Save As. When the file browser window opens,
  it covers the content of the web page from which I was saving the
  content. Maybe I want to move the child window in order to reveal the
  web page that I was visiting in the first place, because the context
  (which I haven't memorized in full in my brain just yet) helps me
  choose a file name for the very file I'm saving.

  
  Another example: I am browsing some folder in Nautilus. I right-click on a 
file or folder inside it, and open Properties. That opens in a popup. Now I 
want to have another look at the name of the file I selected (of which I'm now 
seeing the properties), and those around it, because I'm wondering if I chose 
the wrong file, or for whatever other reason. I can't do taht without closing 
the Properties window.

  The everyday examples are countless.

  
  This is idiotic. Seriously, what are you doing?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 18:11:28 2020
  DistUpgraded: 2020-07-12 15:56:23,368 INFO cache.commit()
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.108: added
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (2465 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 

[Desktop-packages] [Bug 1887296] Re: Moving popup windows drags the application's main window behind it

2022-08-26 Thread Mitch Curtis
Here's the Gnome task for this, by the way:

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/443

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

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

Title:
  Moving popup windows drags the application's main window behind it

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

Bug description:
  Sometimes programs open a "popup" or a "secondary", "child" window, I
  don't know what the word is.

  For example, in Chrome, if I right-click on an image in a web page and
  choose "Save As", this will open a new file browser window that allows
  me to browse for a directory to save the image to.

  Until Ubuntu 16.04, I could move that child window around by dragging
  it by its title bar, and that would not move around the parent window
  behind it.

  Now, it does. That is, the "parent" window greyes out, and moving the
  "child" window (i.e. the popup) on the foreground causes the parent
  window in the background to move as if they were glued together.

  In the above example, if I drag around the "Save As" window, the
  Chrome window behind it moves too. Even worse, if the parent window is
  maximized, it will "oppose resistance" to the dragging of the popup
  window, and if I drag far enough, the parent window will unmaximize
  and unblock the movement of both windows.

  It's pure madness.

  
  I can't imagine a scenario where this is the unavoidable consequence of some 
improvement. It looks like it is by design.

  Why?

  What were you thinking? Why do you ACTIVELY work to degrade usability
  and make the users' life miserable??

  
  Here's a very real-life example:

  As mentioned above, I right-click on something in the browser (like an
  image or a video) and do Save As. When the file browser window opens,
  it covers the content of the web page from which I was saving the
  content. Maybe I want to move the child window in order to reveal the
  web page that I was visiting in the first place, because the context
  (which I haven't memorized in full in my brain just yet) helps me
  choose a file name for the very file I'm saving.

  
  Another example: I am browsing some folder in Nautilus. I right-click on a 
file or folder inside it, and open Properties. That opens in a popup. Now I 
want to have another look at the name of the file I selected (of which I'm now 
seeing the properties), and those around it, because I'm wondering if I chose 
the wrong file, or for whatever other reason. I can't do taht without closing 
the Properties window.

  The everyday examples are countless.

  
  This is idiotic. Seriously, what are you doing?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 18:11:28 2020
  DistUpgraded: 2020-07-12 15:56:23,368 INFO cache.commit()
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.108: added
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (2465 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  

[Desktop-packages] [Bug 1987734] Re: Icon grid is too narrow when Ubuntu Dock is enabled

2022-08-26 Thread Daniel van Vugt
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5791
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5791

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

Title:
  Icon grid is too narrow when Ubuntu Dock is enabled

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

Bug description:
  Icon grid is too narrow (in gnome-shell 43 on kinetic) when Ubuntu
  Dock is enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1987734/+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 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-26 Thread Olivier Tilloy
Thank you very much for documenting thoroughly your findings. These will
be useful to design and implement a proper solution to the problem.

In the meantime, a couple of comments:

 - the apparmor profile will be overwritten every time the snap is
updated, so you will have to re-apply the changes

 - /usr inside the snap is a bind-mount from /usr in the base snap, not
on the host system, which explains why your addition of
`/usr/lib/x86_64-linux-gnu/** rm,` to the apparmor profile doesn't work
as you'd expect (see
https://github.com/snapcore/snapd/pull/11025#issuecomment-1225787194 for
details)

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1967632/+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 1987734] [NEW] Icon grid is too narrow when Ubuntu Dock is enabled

2022-08-26 Thread Daniel van Vugt
Public bug reported:

Icon grid is too narrow (in gnome-shell 43 on kinetic) when Ubuntu Dock
is enabled.

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


** Tags: kinetic visual-quality

** Attachment added: "Screenshot from 2022-08-26 15-18-44.png"
   
https://bugs.launchpad.net/bugs/1987734/+attachment/5611771/+files/Screenshot%20from%202022-08-26%2015-18-44.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/1987734

Title:
  Icon grid is too narrow when Ubuntu Dock is enabled

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Icon grid is too narrow (in gnome-shell 43 on kinetic) when Ubuntu
  Dock is enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987734/+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 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-26 Thread Luca Ferroni
Guys, it works for me!
It's weird but somehow it works :-)

More than my previous not working comment 
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967632/comments/9
I have added:

- the libacsccid1 package
- rw access to the unix socket /run/pcscd/pcscd.comm in the apparmor profile


Summarizing the solution again:

# apt install libacsccid1 pcscd
# mkdir /etc/apparmor.d/abstractions/p11-kit.d/
# echo "/run/user/[0-9]*/** mr," > /etc/apparmor.d/abstractions/p11-kit.d/snap
# echo "/run/pcscd/pcscd.comm rw," >> 
/etc/apparmor.d/abstractions/p11-kit.d/snap

add "#include " in
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox after #include


# apparmor_parser -v -C -r
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox

Then in Firefox -> Settings -> Privacy and Security -> Security devices
Load -> name: ACS ACR38U in my case, but can be anything you want, module: 
/usr/share/bit4id/x/libbit4xpki.so

That's for my card, my reader and my module. And note: my FF is in
Italian, translation may differ a bit in English.

Further weird notes:

1. The first time I try to access after a reboot, I go to the webpage
https://dichiarazioneprecompilata.agenziaentrate.gov.it and FF ask me
for the PIN (with a system dialog). I insert the PIN and FF ask me again
for the PIN in an infinite cycle, I have to kill FF. But the second time
and following times I access the page it works like a charm even in
Incognito mode. Weird, but I can live with it. I seldom use smart card.

2. Another strange thing that happened while I was trying to isolate the
right steps to publish here is that I removed rw access to pcscd.comm
socket in apparmor profile and FF kept working! Even after a restart,
and even in Incognito mode. So I have rebooted the system in order to be
sure that rw access to the socket would be a requirement, and that's it.

3. I don't know why Firefox does not let me load the 
/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so module. It complains with the 
message "Unable to add module" :-(
even if I add `/usr/lib/x86_64-linux-gnu/** rm,` in 
/etc/apparmor.d/abstractions/p11-kit.d/snap apparmor profile.


Differences between opensc-pkcs11.so and libbit4xpki.so

file /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
/usr/lib/bit4id/libbit4xpki.so

/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so: ELF 64-bit LSB shared
object, x86-64, version 1 (SYSV), dynamically linked,
BuildID[sha1]=de5eb51ea9145d2bfd9428110736825895bb56f4, stripped

/usr/lib/bit4id/libbit4xpki.so: ELF 64-bit LSB shared
object, x86-64, version 1 (SYSV), dynamically linked,
BuildID[sha1]=825713056df8eb66f78817284b4ec2c7a2d8c26b, not stripped


My environment is:

Ubuntu 22.04.1 LTS
Codename:   jammy
Mozilla Firefox 104.0


I think that's all my story, if there is something else or attempts I can make 
in my environment, please ask, I remain here available.

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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