date:20220516

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

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

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

Title:
  Can’t connect to a specific Wi-Fi network with wpa_supplicant

Status in wpa package in Ubuntu:
  Expired

Bug description:
  This is the error I get if I try to connect to a specific Wi-Fi
  network on Ubuntu 20.10 with wpa_supplicant:

  Error: Connection activation failed: (7) Secrets were required, but
  not provided.

  If I use iwd instead, everything works fine.

  I also can connect to other networks with wpa_supplicant.

  I had the same issue with the Live USB.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: wpasupplicant 2:2.9-1ubuntu8
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: i3
  Date: Tue Oct 27 20:55:39 2020
  InstallationDate: Installed on 2020-10-26 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1901752/+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 1965428] Re: package xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2 failed to
  install/upgrade: dpkg-deb --control subprocess returned error exit
  status 2

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  I faced this issue when I tried to install Ubuntu alongside Windows 10

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Thu Mar 17 13:45:42 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DuplicateSignature:
   package:xserver-xorg-legacy:2:1.20.11-1ubuntu1~20.04.2
   Unpacking libnss-systemd:amd64 (245.4-4ubuntu3.15) over (245.4-4ubuntu3.11) 
...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-4gY3X7/01-xserver-common_2%3a1.20.13-1ubuntu1~20.04.2_all.deb'
 is not a Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-4gY3X7/01-xserver-common_2%3a1.20.13-1ubuntu1~20.04.2_all.deb
 (--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) 
[103c:84c1]
 Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1]
  InstallationDate: Installed on 2022-03-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: HP HP Pavilion Laptop 15-cs2xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=de643cef-8a09-4604-9700-75c0ebf6cdeb ro recovery nomodeset 
dis_ucode_ldr
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: xorg-server
  Title: package xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2 failed to 
install/upgrade: dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2020
  dmi.bios.release: 15.23
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84C1
  dmi.board.vendor: HP
  dmi.board.version: 15.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 15.32
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku6MZ82UAR#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs2xxx
  dmi.product.sku: 6MZ82UAR#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1965428/+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 1973604] Re: [nvidia340] display hangs 10s on boot with nvidia-340

2022-05-16 Thread jeremyszu

Hi ysfr,

Would you please help to test this version?
https://launchpad.net/~os369510/+archive/ubuntu/lp1973604

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

Title:
  [nvidia340] display hangs 10s on boot with nvidia-340

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

Bug description:
  Since ubuntu-drivers-common 1:0.9.0~0.20.04.6,
  system running kernel 5.4 & nvidia-340 will experience
  10s useless delay on boot because 
  gpu-manager is waiting for nvidia-drm to load
  & nvidia-drm is not built in with nvidia-340.

  Several legacy nvidia cards are stuck to nvidia-340 & Kernel 5.4 as detailled 
in:
  
https://nvidia.custhelp.com/app/answers/detail/a_id/3142/%7E/support-timeframes-for-unix-legacy-gpu-releases

  See prior investigation in comments of
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1973604/+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 1973638] Re: System very laggy

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

  apport-collect 1973638

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

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

Title:
  System very laggy

Status in Ubuntu:
  Incomplete

Bug description:
  i running wine program and i want doing a lot screenshot. after did it
  and close program. my system very laggy. i see at htop program my ram
  and swap full.

  my system info.

  Host: mantari Kernel: 5.17.7-xanmod1 x86_64 bits: 64 compiler: gcc
  v: 11.2.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.17.7-xanmod1
  root=UUID=1dd447f7-2ae1-47c5-81cc-8584b22766d3 ro mitigations=off quiet
  splash vt.handoff=7
Desktop: GNOME 42.0 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3 42.0
  Distro: Ubuntu 22.04 LTS (Jammy Jellyfish)
  Machine:
Type: Portable System: Dell product: Inspiron 3442 v: N/A
Mobo: Dell model: 0T57PC v: A16 serial:  UEFI: Dell
  v: A16 date: 09/02/2020
  Battery:
ID-1: BAT0 charge: 14.9 Wh (100.0%) condition: 14.9/41.4 Wh (36.0%)
  volts: 16.8 min: 14.8 model: SMP-SDI2.8 DELL FW1MN31 type: Li-ion
  serial: 4862 status: Full
  Memory:
RAM: total: 3.75 GiB 
  Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: 
fbdev,vesa
  gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: AU Optronics built: 2013 res: 1366x768 dpi: 112
  gamma: 1.2 size: 309x173mm (12.2x6.8") diag: 354mm (13.9") ratio: 16:9
  modes: 1366x768
OpenGL: renderer: Mesa Intel HD Graphics (HSW GT1) v: 4.6 Mesa 22.0.1
  compat-v: 3.1 direct render: Yes
  Drives:
Local Storage: total: 1.14 TiB used: 916.19 GiB (78.7%)
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
  model: WD7500BPVX-75JC3T0 size: 698.64 GiB block-size: physical: 4096 B
  logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: WXA1A33W6463
  rev: 1A01 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST500LM012 HN-M500MBB
  size: 465.76 GiB block-size: physical: 4096 B logical: 512 B
  speed: 3.0 Gb/s type: HDD rpm: 5400 serial: S2S7J9DC911744 rev: 0001
  scheme: GPT
  Swap:
Kernel: swappiness: 30 (default 60) cache-pressure: 50 (default 100)
ID-1: swap-1 type: zram size: 2.79 GiB used: 0 KiB (0.0%) priority: 5
  dev: /dev/zram0
ID-2: swap-2 type: zram size: 2.79 GiB used: 0 KiB (0.0%) priority: 5
  dev: /dev/zram1

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 42.0-2ubuntu1
Candidate: 42.0-2ubuntu1
Version table:
   *** 42.0-2ubuntu1 500
  500 https://mirror.internet.asn.au/pub/ubuntu/archive jammy/main 
amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1973638/+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 1973638] Re: gnome-shell memory leak after did 100+ screenshot

The screenshot in comment #1 shows gnome-shell is only 168MB resident.
So no leak there.

Please run:

  ps auxw > psoutput.txt
  free -h > free.txt
  lspci -k > lspci.txt
  journalctl -b0 > journal.txt

and attach the resulting text files here.

I suspect there is no leak here and we should instead investigate
"system very laggy".


** Tags added: gnome-shell-leak jammy

** Tags removed: gnome-shell-leak

** Summary changed:

- gnome-shell memory leak after did 100+ screenshot
+ System very laggy

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

Title:
  System very laggy

Status in Ubuntu:
  Incomplete

Bug description:
  i running wine program and i want doing a lot screenshot. after did it
  and close program. my system very laggy. i see at htop program my ram
  and swap full.

  my system info.

  Host: mantari Kernel: 5.17.7-xanmod1 x86_64 bits: 64 compiler: gcc
  v: 11.2.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.17.7-xanmod1
  root=UUID=1dd447f7-2ae1-47c5-81cc-8584b22766d3 ro mitigations=off quiet
  splash vt.handoff=7
Desktop: GNOME 42.0 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3 42.0
  Distro: Ubuntu 22.04 LTS (Jammy Jellyfish)
  Machine:
Type: Portable System: Dell product: Inspiron 3442 v: N/A
Mobo: Dell model: 0T57PC v: A16 serial:  UEFI: Dell
  v: A16 date: 09/02/2020
  Battery:
ID-1: BAT0 charge: 14.9 Wh (100.0%) condition: 14.9/41.4 Wh (36.0%)
  volts: 16.8 min: 14.8 model: SMP-SDI2.8 DELL FW1MN31 type: Li-ion
  serial: 4862 status: Full
  Memory:
RAM: total: 3.75 GiB 
  Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: 
fbdev,vesa
  gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: AU Optronics built: 2013 res: 1366x768 dpi: 112
  gamma: 1.2 size: 309x173mm (12.2x6.8") diag: 354mm (13.9") ratio: 16:9
  modes: 1366x768
OpenGL: renderer: Mesa Intel HD Graphics (HSW GT1) v: 4.6 Mesa 22.0.1
  compat-v: 3.1 direct render: Yes
  Drives:
Local Storage: total: 1.14 TiB used: 916.19 GiB (78.7%)
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
  model: WD7500BPVX-75JC3T0 size: 698.64 GiB block-size: physical: 4096 B
  logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: WXA1A33W6463
  rev: 1A01 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST500LM012 HN-M500MBB
  size: 465.76 GiB block-size: physical: 4096 B logical: 512 B
  speed: 3.0 Gb/s type: HDD rpm: 5400 serial: S2S7J9DC911744 rev: 0001
  scheme: GPT
  Swap:
Kernel: swappiness: 30 (default 60) cache-pressure: 50 (default 100)
ID-1: swap-1 type: zram size: 2.79 GiB used: 0 KiB (0.0%) priority: 5
  dev: /dev/zram0
ID-2: swap-2 type: zram size: 2.79 GiB used: 0 KiB (0.0%) priority: 5
  dev: /dev/zram1

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 42.0-2ubuntu1
Candidate: 42.0-2ubuntu1
Version table:
   *** 42.0-2ubuntu1 500
  500 https://mirror.internet.asn.au/pub/ubuntu/archive jammy/main 
amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1973638/+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 1973610] Re: Bluetooth will not stay on or connect to devices when on

For the USB dongle there are kernel messages:

[   34.065571] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[   34.065744] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-21e8.hcd'
[   34.065757] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-21e8.hcd'

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

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

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

Title:
  Bluetooth will not stay on or connect to devices when on

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

Bug description:
  Since upgrading from Ubuntu 20.10, my internal bluetooth card as well
  as an external usb dongle will not work.  Bluetooth starts as off, and
  cannot be turned on.  If I use systemctl to turn it on, it is on but
  doesn't find any devices through bluez.  Blueman finds devices but
  cannot connect to them.  The hardware on this machine has remained
  identical; the only difference is the new version of Ubuntu.  Hence
  the problem has to be software.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 09:45:02 2022
  InstallationDate: Installed on 2021-10-22 (205 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago)
  dmi.bios.date: 08/04/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.50
  dmi.board.name: N7 B550
  dmi.board.vendor: NZXT
  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:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr: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.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 5C:F3:70:A8:66:B1  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN INIT RUNNING 
RX bytes:175353 acl:52 sco:0 events:6887 errors:0
TX bytes:18571 acl:52 sco:0 commands:1087 errors:2
  mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973610/+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 1973604] Re: [nvidia340] display hangs 10s on boot with nvidia-340

Sounds like the hang is intentional?

https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.0~0.20.04.6

** Tags added: focal

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

** Tags added: nvidia

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

Title:
  [nvidia340] display hangs 10s on boot with nvidia-340

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

Bug description:
  Since ubuntu-drivers-common 1:0.9.0~0.20.04.6,
  system running kernel 5.4 & nvidia-340 will experience
  10s useless delay on boot because 
  gpu-manager is waiting for nvidia-drm to load
  & nvidia-drm is not built in with nvidia-340.

  Several legacy nvidia cards are stuck to nvidia-340 & Kernel 5.4 as detailled 
in:
  
https://nvidia.custhelp.com/app/answers/detail/a_id/3142/%7E/support-timeframes-for-unix-legacy-gpu-releases

  See prior investigation in comments of
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1973604/+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 1973474] Re: Rename "Pin to Dash" to "Pin to Dock"

I'm not sure I agree with this, but do appreciate the wording is
confusing in a world of dash and dock.

* Regular users are less likely to understand "pinned" as much as "favourites".
* Power users may have no dock, only a dash, and so the existing wording is 
correct.
* It's a patch we would have to maintain.


** Changed in: gnome-shell (Ubuntu)
   Importance: Medium => Wishlist

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

Title:
  Rename "Pin to Dash" to "Pin to Dock"

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  I noticed this commit:

  https://github.com/micheleg/dash-to-dock/commit/8ee55c29

  If I understand it correctly, it means that we will use the label "Pin
  to Dash" instead of "Add to Favorites" as from Ubuntu 22.10. To be
  consistent I suggest that we rename the thing in all contexts, and
  hence replace "Dock" with "Dash" in all affected strings in the
  Appearance section in g-c-c.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1973474/+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 1091926]

2022-05-16 Thread Virtual-q

I'm marking this bug as WONTFIX per bug #1269807.

For more information see -
https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-
firefox/

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

Title:
  firefox java applet fails when the firefox is launched by a java
  program

Status in Mozilla Firefox:
  Won't Fix
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hi Support Team,

  I run a simple Java program (a runnable jar file). The Java program
  code is as following

  import java.io.IOException;
  public class Main {
   public static void main(String args[]) throws IOException {
//this website has a small Java applet inside
Runtime.getRuntime.exec("firefox 
http://javatester.org/version.html;);
System.out.println("hello world");
   }
  }

  My JRE (yes, JRE, not JDK) is Oracle JRE 1.6.0_38.

  What the program does is essentially opening
  http://javatester.org/version.html in Firefox. This website has a
  small Java applet, so performance won't be a problem. What happens
  then is that, Firefox is opened, http://javatester.org/version.html is
  opened, BUT the applet inside the website FAILS to play. The same
  thing happens if my Java program opens any other website which has
  applet.

  However, if I run "firefox http://javatester.org/version.html; from
  command line, everything works perfectly. Similarly, if I open
  Firefox, then I type http://javatester.org/version.html at the URL
  field, everything also works perfectly.

  This problem happens in Firefox, but NOT in Chromium (which I
  installed from your standard repository).

  This problem doesn't happen in Oracle Linux distro. I haven't tried in
  other Linux distros, though.

  Thank you

  Fajrian Yunus

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: firefox 17.0.1+build1-0ubuntu0.12.10.1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anakin 1700 F pulseaudio
  BuildID: 20121129151842
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Channel: Unavailable
  Date: Wed Dec 19 09:46:27 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  IpRoute:
   default via 10.0.2.2 dev eth0  proto static 
   10.0.2.0/24 dev eth0  proto kernel  scope link  src 10.0.2.15  metric 1 
   169.254.0.0/16 dev eth0  scope link  metric 1000
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Plugins: Java(TM) Plug-in 1.6.0_38 - 
/usr/lib/jvm/jre1.6.0_38/lib/amd64/libnpjp2.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=17.0.1/20121129151842 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

2022-05-16 Thread Benjamin Smedberg (Mozilla) [:bs]

Resolving old bugs which are likely not relevant any more, since NPAPI
plugins are deprecated.

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

Title:
  improper mouse hover behavior with links

Status in Mozilla Firefox:
  Expired
Status in X.Org X server:
  Fix Released
Status in firefox-3.0 package in Ubuntu:
  Invalid
Status in firefox-3.1 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox-3.1

  Using Firefox 3.1 on Kubuntu 9.04 Jaunty, if I move the mouse over a
  link, the hover function does not work properly.  If the mouse is
  stopped over a link, it remains as the standard cursor.  If it is
  moving, then it rapidly alternates between the standard cursor and the
  link select cursor.  This only happens if at some point I have moused
  over one of the buttons in the Firefox chrome.  I have tried launching
  Firefox with the -safe-mode switch, but this does not affect the
  problem.

  This problem affects functionality because some websites use menus
  that appear when a link is moused over, and this problem keeps the
  menu from staying on the screen.

  [Testcase]
  open firefox, move into main window, then move up into
  menu bar, back into main window and hover over a link. The cursor immediately
  changes back to the normal cursor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/312353/+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 1967596] Re: On-screen keyboard fails to appear on the unlock screen

gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1973373, LP: #1968911)
  * Drop patches applied in new release

 -- Jeremy Bicha   Fri, 13 May 2022 16:32:49 -0400

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  On-screen keyboard fails to appear on the unlock screen

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  I have upgrade from 21.10 to 22.04 Beta on my Microsoft Surface Go 2
  tablet. I generally use it via the touch screen but I also have a type
  cover I can attach.

  When you lock the tablet and then try to unlock it via the Gnome
  unlock screen, tapping in the password box does bring up the keyboard
  but any keys pressed do not appear in the password box.

  All of the above can be worked around by attaching the Type Cover and
  using the physical keyboard.

  If I an collect any diagnostic data for this please send me the
  instructions and I'll see what I can do.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 07:08:40 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-01 (31 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967596/+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 1965820] Re: Unhandled promise rejection in _loadFile@resource:///org/gnome/shell/ui/background.js

gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1973373, LP: #1968911)
  * Drop patches applied in new release

 -- Jeremy Bicha   Fri, 13 May 2022 16:32:49 -0400

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

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

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

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

** Also affects: gnome-shell (Ubuntu Kinetic)
   Importance: Low
 Assignee: Jeremy Bicha (jbicha)
   Status: Fix Released

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

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

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

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

Title:
  Unhandled promise rejection in
  _loadFile@resource:///org/gnome/shell/ui/background.js

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  In Progress
Status in gnome-shell source package in Kinetic:
  Fix Released

Bug description:
  Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: Unhandled promise 
rejection. To suppress this warning, add an error handler to your promise chain 
with .catch() or a try-catch block around your await expression. Stack trace of 
the failed promise:#012  
_loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012  
_load@resource:///org/gnome/shell/ui/background.js:533:14#012  
_init@resource:///org/gnome/shell/ui/background.js:282:14#012  
Background@resource:///org/gnome/shell/ui/background.js:237:4#012  
getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012  
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012  
BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012  
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012  
_updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34#012  
_monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14
  Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: message repeated 8 times: [ 
Unhandled promise rejection. To suppress this warning, add an error handler to 
your promise chain with .catch() or a try-catch block around your await 
expression. Stack trace of the failed promise:#012  
_loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012  
_load@resource:///org/gnome/shell/ui/background.js:533:14#012  
_init@resource:///org/gnome/shell/ui/background.js:282:14#012  
Background@resource:///org/gnome/shell/ui/background.js:237:4#012  
getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012  
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012  
BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012  
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012  
_updateBackgrounds@resource:///o]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.103.01  Thu Jan  6 
12:10:04 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 20:57:30 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GA104 [GeForce RTX 3070 Lite Hash Rate] [10de:2488] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GA104 [GeForce RTX 3070 Lite Hash 
Rate] [1458:404c]
  InstallationDate: Installed on 2022-03-16 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  MachineType: Gigabyte Technology Co., Ltd. B550 AORUS MASTER
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic

[Desktop-packages] [Bug 1972113] Re: Ubuntu 22.04 screen keyboard shows but does not accept input

gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1973373, LP: #1968911)
  * Drop patches applied in new release

 -- Jeremy Bicha   Fri, 13 May 2022 16:32:49 -0400

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

** Also affects: gnome-shell (Ubuntu Kinetic)
   Importance: High
   Status: Fix Released

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

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

** Changed in: gnome-shell (Ubuntu Jammy)
   Importance: Undecided => High

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

** Changed in: gnome-shell (Ubuntu Kinetic)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

Title:
  Ubuntu 22.04 screen keyboard  shows but does not accept input

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  In Progress
Status in gnome-shell source package in Kinetic:
  Fix Released

Bug description:
  Dell Venue 11 Pro Windows Tablet, (Touchscreen - no keyboard/mouse)

  Screen keyboard works as expected on 21.10, on upgrade to 22.04 (or
  clean install) On screen keyboard works as expected in
  applications,but shows and does not accept input on
  authentication/logon prompts, keyboard does not appear to respond to
  any activity (Uppercase/special characters)

  22.04 does not show screen keyboard at all during install (Can only be
  installed with physical keyboard attached)

  setting WaylandEnable=false  in /etc/gdm3/custom.conf and restarting
  display manager (sudo systemctl restart gdm3) does not help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1972113/+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 1973351] Re: Screenshot tool freezes on Chromium with secondary menu open

gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1973373, LP: #1968911)
  * Drop patches applied in new release

 -- Jeremy Bicha   Fri, 13 May 2022 16:32:49 -0400

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

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

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

** Also affects: gnome-shell (Ubuntu Kinetic)
   Importance: Medium
   Status: Fix Released

** Changed in: gnome-shell (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu Kinetic)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

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

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

Title:
  Screenshot tool freezes on Chromium with secondary menu open

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  In Progress
Status in gnome-shell source package in Kinetic:
  Fix Released

Bug description:
  Hi, I have found a behavior that I'm able to reproduce consistently (I
  have not tried with other browsers).

  Here are the steps to reproduce (should work on a clean Ubuntu 22.04
  installation):

  1. Install Chromium (apt install chromium-browser)
  2. Open chromium
  3. Open a website
  4. Right click on an empty section of the website, so the secondary menu will 
open (the one that contains the "Back", "Reload", "Save as..." options)
  5. Press the PrntScrn key, making the new screenshot UI to appear

  The screenshot UI freezes and cannot be closed neither by pressing Esc
  nor any other key combination.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1973351/+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 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

It looks like you have copied someone else's log from an unrelated bug?
That shows bug 1717170 and bug 1965820. We don't need to discuss those
here.

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+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 1897454] Re: [snap] Chromium has Wayland support disabled

Now you can enable Wayland in chrome://flags with

  Preferred Ozone platform = Wayland

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

Title:
  [snap] Chromium has Wayland support disabled

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Since v87 Chromium ships with support for Ozone/Wayland:
  https://www.phoronix.com/scan.php?page=news_item=Chrome-87-Ozone-Try-Again.

  This build flag is not disabled in dev (edge) channel build, so it should be 
possible to run Chromium with flags
--enable-features=UseOzonePlatform --ozone-platform=wayland.

  This does not work due to environment variable DISABLE_WAYLAND set to 1 here:
  
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=dev#n18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+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 1897454] Re: [snap] Chromium has Wayland support disabled

Or as Olivier mentioned... chrome://flags/#ozone-platform-hint

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

Title:
  [snap] Chromium has Wayland support disabled

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Since v87 Chromium ships with support for Ozone/Wayland:
  https://www.phoronix.com/scan.php?page=news_item=Chrome-87-Ozone-Try-Again.

  This build flag is not disabled in dev (edge) channel build, so it should be 
possible to run Chromium with flags
--enable-features=UseOzonePlatform --ozone-platform=wayland.

  This does not work due to environment variable DISABLE_WAYLAND set to 1 here:
  
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=dev#n18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+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 1973668] Re: /usr/bin/gnome-shell:6:__pthread_kill_implementation:__pthread_kill_internal:GI_pthread_kill:__GI_raise:__GI_abort

This is a duplicate of bug 1962823 which itself is too vague. Although
it seems most reports of it from jammy are bug 1970917.

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

Title:
  /usr/bin/gnome-
  
shell:6:__pthread_kill_implementation:__pthread_kill_internal:__GI___pthread_kill:__GI_raise:__GI_abort

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058 
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/gnome-shell/+bug/1973668/+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 1973615] Re: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()

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

** This bug is no longer a duplicate of bug 1972812
   gnome-shell (X11, nvidia-390) crashes with SIGSEGV when unlocking the screen

** Description changed:

- Could be a duplicate of LP1972812
- 
  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 14 15:23:54 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1649813447
  InstallationDate: Installed on 2022-05-10 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/addyess
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, user)
-  SHELL=/bin/zsh
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, user)
+  SHELL=/bin/zsh
+  XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  meta_window_get_window_type () from /lib/x86_64-linux-gnu/libmutter-10.so.0
-  ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
-  ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
-  meta_display_close () from /lib/x86_64-linux-gnu/libmutter-10.so.0
-  shell_global_reexec_self () from /usr/lib/gnome-shell/libgnome-shell.so
+  meta_window_get_window_type () from /lib/x86_64-linux-gnu/libmutter-10.so.0
+  ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
+  ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
+  meta_display_close () from /lib/x86_64-linux-gnu/libmutter-10.so.0
+  shell_global_reexec_self () from /usr/lib/gnome-shell/libgnome-shell.so
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  mtime.conffile..etc.apport.crashdb.conf: 2022-05-12T08:10:45.865414
  separator:

** This bug has been marked a duplicate of bug 1965897
   gnome-shell crashed with SIGSEGV in meta_window_get_window_type(window=NULL) 
from meta_window_actor_queue_destroy() from 
meta_compositor_real_remove_window() from meta_window_unmanage() from 
meta_display_unmanage_windows()

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_window_type()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 14 15:23:54 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1649813447
  InstallationDate: Installed on 2022-05-10 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/addyess
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_window_type () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   meta_display_close () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   shell_global_reexec_self () from /usr/lib/gnome-shell/libgnome-shell.so
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  mtime.conffile..etc.apport.crashdb.conf: 2022-05-12T08:10:45.865414
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973615/+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 1972812] Re: gnome-shell (X11, nvidia-390) crashes with SIGSEGV when unlocking the screen

Comment #14 is not related to this bug. Please ignore it.

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

Title:
  gnome-shell (X11, nvidia-390) crashes with SIGSEGV when unlocking the
  screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I found a security vulnerability in Ubuntu 22.04 LTS operating system 
(Laptops only) It is reproduced like this (in steps):
  1. I lock the screen Win + L
  2. Close the laptop lid
  3. Then I open the lid of the laptop
  4. I get a vulnerability, the operating system does not ask for a password, 
but immediately shows the desktop without the need to unlock it. that is, 
closing and opening the laptop lid leads to unlocking the screen without asking 
for a password.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 12:20:28 2022
  InstallationDate: Installed on 2022-04-21 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  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/1972812/+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 1973668] [NEW] /usr/bin/gnome-shell:6:__pthread_kill_implementation:__pthread_kill_internal:GI_pthread_kill:__GI_raise:__GI_abort

2022-05-16 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058 
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: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: jammy

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

Title:
  /usr/bin/gnome-
  
shell:6:__pthread_kill_implementation:__pthread_kill_internal:__GI___pthread_kill:__GI_raise:__GI_abort

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058 
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/gnome-shell/+bug/1973668/+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 1968911] Re: assertion failures in cr_parser_new_from_buf and cr_declaration_parse_list_from_buf

This bug was fixed in the package gnome-shell - 42.1-0ubuntu1

---
gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1973373, LP: #1968911)
  * Drop patches applied in new release

 -- Jeremy Bicha   Fri, 13 May 2022 16:32:49 -0400

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

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

Title:
  assertion failures in cr_parser_new_from_buf and
  cr_declaration_parse_list_from_buf

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  gnome-shell is emitting a lot of warnings to the systemd journal

  Test Case
  -
  Install the update
  Restart your computer
  Log in.
  Run this command in a terminal. It should not return any thing.

  journalctl -b | grep cr_

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

  Original Bug Report
  ---

  Hi,

  I see the following assertion failures in the system logs:

  # journalctl | grep cr_
  Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Apr 13 18:22:56 vougeot gnome-shell[3472]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Apr 13 18:22:56 vougeot gnome-shell[3472]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Apr 13 18:22:56 vougeot gnome-shell[3472]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  Uname: Linux 5.17.2-051702-generic x86_64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Apr 13 20:04:54 2022
  DisplayManager: gdm3
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

This bug was fixed in the package gnome-shell - 42.1-0ubuntu1

---
gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1973373, LP: #1968911)
  * Drop patches applied in new release

 -- Jeremy Bicha   Fri, 13 May 2022 16:32:49 -0400

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

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

Title:
  Update gnome-shell to 42.1

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

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

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.1/NEWS

  Test Case 1
  -
  sudo apt install gnome-session gnome-shell-extensions
  Install the update.
  Log out.
  Select your name on the login screen.
  Click the gear button to choose a session to log in to.
  Finish logging in.

  Verify that things continue to work well for all these sessions:
  GNOME
  GNOME Classic
  Ubuntu
  Ubuntu on Xorg

  
  Test Case 2
  ---
  Because a GNOME Shell update years ago broke some GNOME Shell extensions, 
it's also requested that we do a basic test of all the extensions included in 
the Ubuntu repositories.

  https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from-
  universe-and-stop-auto-syncs/18437/9

  Install all the extensions.
  Log out and then log back in.
  Use one of the Extensions apps to enable all the extensions.
  Verify that they can all be enabled without showing an error.

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973373/+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 1972766] Re: Changing default mounting options causes root owner

2022-05-16 Thread bhikkhu subhuti

The problem is, if you want a partition to be auto-mounted, you either must 
edit the fstab or THE INSTRUCTIONS are to turn off the "default" mounting in 
gnome disk utility and it will auto-mount.  However, the auto-mounting is done 
as system root and I don't have access to it.  So I must google and google and 
more google until I find that I put some settings like uuid=1000.  

This is a big problem.  
Why?  
Well I setup my 22.04 with a full wipe, but kept my data partition.
My git was totally broken on my data partition and I thought it was ubuntu 22.04
But then with just git and ubuntu and vscode it worked.. so I installed the 
rest of the apps and it broke (I also setup my data partition to auto-mount)
then I thought it was my proton vpn which was the only ppa
It took a long time to realize it was the auto-mount .. merely changing 
defaults switch.

I had wiped  my system 3 times before I figured this out.
Then I had to do a lot of googling to auto-mount for  myself.  It seems very 
logical that I would want to use a drive that I setup as automount.


If the user is selecting auto-mount, why not automatically allow that user to 
read access?
Instead it defaults to system.

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

Title:
  Changing default mounting options causes root owner

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04
  If I change the default mounting options in Gnome Disk Utility the owner is 
root.  This threw me for a loop when all of my git repos were not working.  I 
thought it was an ubuntu 22.04 problem or a ppa.

  It is directly from Gnome Disk Utility by changing the auto mount
  options.  I don't remember this happening before.

  Reproduce

  **Control:**
  Under default mount options.
  Go to your data partition, right click and look at properties/permissions.
  You will be the owner.

  **Cause the bug.**
  Select a data partition you might have (ntfs) for dual boot machines to share 
data.
  Change the switch from default mounting options (top switch) to manual 
settings.  Change label to human readable. ("Data").  Reboot.

  Go to your data partition, right click and look at
  properties/permissions.

  It will say the owner is root and you are not the owner.

  **Fix For The Problem:**
  It took a long time, but I had to add uid=1000,gid=1000 to the settings.  
This hard to research "mystery setting" is not acceptable for a GUI mounting 
tool.

  Reboot.
  Go to your data partition, right click and look at properties/permissions
  You will be the owner.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1972766/+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 1973642] Re: [REGRESSION] Unable to connect to EAP-TLS networks

2022-05-16 Thread Ubuntu Foundations Team Bug Bot

The attachment "8df79f60d616e183257ae1a2c2b48beaf29e5eec.patch" seems to
be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

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

Title:
  [REGRESSION] Unable to connect to EAP-TLS networks

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 22.04, currently with network-manager
  1.36.4-2ubuntu1

  Attempting to connect to an EAP-TLS network fails with:

  NetworkManager[703]:   [1652732829.9142] device (wlp0s12f0): 
Activation: (wifi) connection 'AP' has security, and secrets exist.  No new 
secrets needed.
  NetworkManager[703]:   [1652732829.9143] Config: added 'ssid' value 'AP'
  NetworkManager[703]:   [1652732829.9143] Config: added 'scan_ssid' 
value '1'
  NetworkManager[703]:   [1652732829.9144] Config: added 'bgscan' value 
'simple:30:-65:300'
  NetworkManager[703]:   [1652732829.9144] Config: added 'key_mgmt' value 
'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
  NetworkManager[703]:   [1652732829.9144] Config: added 'eap' value 'TLS'
  NetworkManager[703]:   [1652732829.9144] Config: added 'fragment_size' 
value '1266'
  NetworkManager[703]:   [1652732829.9144] Config: added 'ca_cert' value 
''
  NetworkManager[703]:   [1652732829.9144] Config: added 
'domain_suffix_match' value ''
  NetworkManager[703]:   [1652732829.9145] Config: added 'private_key' 
value '.key'
  NetworkManager[703]:   [1652732829.9145] Config: added 
'private_key_passwd' value ''
  NetworkManager[703]:   [1652732829.9145] Config: added 'client_cert' 
value '.crt'
  NetworkManager[703]:   [1652732829.9145] Config: added 'identity' value 
''
  NetworkManager[703]:   [1652732829.9146] Config: added 
'proactive_key_caching' value '1'
  NetworkManager[703]:   [1652732829.9178] 
sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to 
add network: invalid message format
  NetworkManager[703]:   [1652732829.9179] device (wlp0s12f0): state 
change: config -> failed (reason 'supplicant-failed', sys-iface-state: 
'managed')

  
  Caused by NM providing an empty domain_suffix_match option

  Upstream commit fixing this (also attached): 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec
  Upstream bug report: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973642/+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 1973642] Re: [REGRESSION] Unable to connect to EAP-TLS networks

2022-05-16 Thread Tobias Heider

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

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

Title:
  [REGRESSION] Unable to connect to EAP-TLS networks

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 22.04, currently with network-manager
  1.36.4-2ubuntu1

  Attempting to connect to an EAP-TLS network fails with:

  NetworkManager[703]:   [1652732829.9142] device (wlp0s12f0): 
Activation: (wifi) connection 'AP' has security, and secrets exist.  No new 
secrets needed.
  NetworkManager[703]:   [1652732829.9143] Config: added 'ssid' value 'AP'
  NetworkManager[703]:   [1652732829.9143] Config: added 'scan_ssid' 
value '1'
  NetworkManager[703]:   [1652732829.9144] Config: added 'bgscan' value 
'simple:30:-65:300'
  NetworkManager[703]:   [1652732829.9144] Config: added 'key_mgmt' value 
'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
  NetworkManager[703]:   [1652732829.9144] Config: added 'eap' value 'TLS'
  NetworkManager[703]:   [1652732829.9144] Config: added 'fragment_size' 
value '1266'
  NetworkManager[703]:   [1652732829.9144] Config: added 'ca_cert' value 
''
  NetworkManager[703]:   [1652732829.9144] Config: added 
'domain_suffix_match' value ''
  NetworkManager[703]:   [1652732829.9145] Config: added 'private_key' 
value '.key'
  NetworkManager[703]:   [1652732829.9145] Config: added 
'private_key_passwd' value ''
  NetworkManager[703]:   [1652732829.9145] Config: added 'client_cert' 
value '.crt'
  NetworkManager[703]:   [1652732829.9145] Config: added 'identity' value 
''
  NetworkManager[703]:   [1652732829.9146] Config: added 
'proactive_key_caching' value '1'
  NetworkManager[703]:   [1652732829.9178] 
sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to 
add network: invalid message format
  NetworkManager[703]:   [1652732829.9179] device (wlp0s12f0): state 
change: config -> failed (reason 'supplicant-failed', sys-iface-state: 
'managed')

  
  Caused by NM providing an empty domain_suffix_match option

  Upstream commit fixing this (also attached): 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec
  Upstream bug report: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973

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


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

[Desktop-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04

2022-05-16 Thread VAN LAETHEM

for  https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1

i'm a bit lost! What do I have to do with the 3 available files?

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

Title:
  wifi connection on hotspot with wpa enterprise on 22.04

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04

2022-05-16 Thread VAN LAETHEM

I already tried to apply 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834
but this doesn't help.

I also tried 
https://ubuntuforums.org/showthread.php?t=2474436
but doesn't help neither

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

Title:
  wifi connection on hotspot with wpa enterprise on 22.04

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

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

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

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

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

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


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

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

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

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

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

Title:
  can no longer open new windows after some time

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

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

  => ps -ef | grep -c firefox
  21

  => /snap/bin/firefox

  => ps -ef | grep -c firefox
  21

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

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

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

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


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

[Desktop-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04

2022-05-16 Thread VAN LAETHEM

here is the result of the journalctl


** Attachment added: "result of the journalctl command"
   
https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+attachment/5590157/+files/journalctl.odt

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

Title:
  wifi connection on hotspot with wpa enterprise on 22.04

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1973642] [NEW] [REGRESSION] Unable to connect to EAP-TLS networks

2022-05-16 Thread Nathan Rennie-Waldock

Public bug reported:

Fresh install of Xubuntu 22.04, currently with network-manager
1.36.4-2ubuntu1

Attempting to connect to an EAP-TLS network fails with:

NetworkManager[703]:   [1652732829.9142] device (wlp0s12f0): Activation: 
(wifi) connection 'AP' has security, and secrets exist.  No new secrets needed.
NetworkManager[703]:   [1652732829.9143] Config: added 'ssid' value 'AP'
NetworkManager[703]:   [1652732829.9143] Config: added 'scan_ssid' value 
'1'
NetworkManager[703]:   [1652732829.9144] Config: added 'bgscan' value 
'simple:30:-65:300'
NetworkManager[703]:   [1652732829.9144] Config: added 'key_mgmt' value 
'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
NetworkManager[703]:   [1652732829.9144] Config: added 'eap' value 'TLS'
NetworkManager[703]:   [1652732829.9144] Config: added 'fragment_size' 
value '1266'
NetworkManager[703]:   [1652732829.9144] Config: added 'ca_cert' value 
''
NetworkManager[703]:   [1652732829.9144] Config: added 
'domain_suffix_match' value ''
NetworkManager[703]:   [1652732829.9145] Config: added 'private_key' 
value '.key'
NetworkManager[703]:   [1652732829.9145] Config: added 
'private_key_passwd' value ''
NetworkManager[703]:   [1652732829.9145] Config: added 'client_cert' 
value '.crt'
NetworkManager[703]:   [1652732829.9145] Config: added 'identity' value 
''
NetworkManager[703]:   [1652732829.9146] Config: added 
'proactive_key_caching' value '1'
NetworkManager[703]:   [1652732829.9178] 
sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to 
add network: invalid message format
NetworkManager[703]:   [1652732829.9179] device (wlp0s12f0): state 
change: config -> failed (reason 'supplicant-failed', sys-iface-state: 
'managed')


Caused by NM providing an empty domain_suffix_match option

Upstream commit fixing this (also attached): 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec
Upstream bug report: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973

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


** Tags: jammy patch

** Patch added: "8df79f60d616e183257ae1a2c2b48beaf29e5eec.patch"
   
https://bugs.launchpad.net/bugs/1973642/+attachment/5590156/+files/8df79f60d616e183257ae1a2c2b48beaf29e5eec.patch

** Tags added: patch

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

Title:
  [REGRESSION] Unable to connect to EAP-TLS networks

Status in network-manager package in Ubuntu:
  New

Bug description:
  Fresh install of Xubuntu 22.04, currently with network-manager
  1.36.4-2ubuntu1

  Attempting to connect to an EAP-TLS network fails with:

  NetworkManager[703]:   [1652732829.9142] device (wlp0s12f0): 
Activation: (wifi) connection 'AP' has security, and secrets exist.  No new 
secrets needed.
  NetworkManager[703]:   [1652732829.9143] Config: added 'ssid' value 'AP'
  NetworkManager[703]:   [1652732829.9143] Config: added 'scan_ssid' 
value '1'
  NetworkManager[703]:   [1652732829.9144] Config: added 'bgscan' value 
'simple:30:-65:300'
  NetworkManager[703]:   [1652732829.9144] Config: added 'key_mgmt' value 
'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
  NetworkManager[703]:   [1652732829.9144] Config: added 'eap' value 'TLS'
  NetworkManager[703]:   [1652732829.9144] Config: added 'fragment_size' 
value '1266'
  NetworkManager[703]:   [1652732829.9144] Config: added 'ca_cert' value 
''
  NetworkManager[703]:   [1652732829.9144] Config: added 
'domain_suffix_match' value ''
  NetworkManager[703]:   [1652732829.9145] Config: added 'private_key' 
value '.key'
  NetworkManager[703]:   [1652732829.9145] Config: added 
'private_key_passwd' value ''
  NetworkManager[703]:   [1652732829.9145] Config: added 'client_cert' 
value '.crt'
  NetworkManager[703]:   [1652732829.9145] Config: added 'identity' value 
''
  NetworkManager[703]:   [1652732829.9146] Config: added 
'proactive_key_caching' value '1'
  NetworkManager[703]:   [1652732829.9178] 
sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to 
add network: invalid message format
  NetworkManager[703]:   [1652732829.9179] device (wlp0s12f0): state 
change: config -> failed (reason 'supplicant-failed', sys-iface-state: 
'managed')

  
  Caused by NM providing an empty domain_suffix_match option

  Upstream commit fixing this (also attached): 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec
  Upstream bug report: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973

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


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

[Desktop-packages] [Bug 1971415] Re: Remote desktop is automatically enabled after login

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1736

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

Title:
Remote desktop is automatically enabled after login

Status in gnome-control-center package in Ubuntu:
Fix Released
Status in gnome-control-center source package in Jammy:
Confirmed

Bug description:
Details:
Turning off RDP Remote Desktop Sharing with gnome-control-center would only
turn off RDP sharing for the current session. Upon logging back in, RDP Sharing
would be enabled again without any additional user interaction or notification.

Other Info:
As mentioned in the comments at
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1825
this issue could have been avoided if Ubuntu's gnome-remote-desktop didn't
keep the systemd user service always running. I do intend to fix that issue
also but it is a more complicated fix. I think it will require a maintainer
script to remove the automatic conffiles added by dh. I will do the
gnome-remote-desktop bugfix as a normal non-security SRU.

Original Bug Report:
If I disable sharing/remote desktop in GNOME Control Center, then log out and
back in, it is automatically enabled again. I report this as a security
vulnerability because remote desktop is enabled without the user's knowledge.

Software versions:
- Ubuntu 22.04
- gnome-remote-desktop 42.0-4ubuntu1
- gnome-control-center 1:41.4-1ubuntu13

Steps to reproduce:
1. Start with Remote Desktop enabled. "systemctl --user status
gnome-remote-desktop.service" reports "active (running)".
2. Disable Remote Desktop in Control Center. systemctl reports "inactive
(dead)".
3. Log out and back in.
4. Open Control Center. Remote Desktop is enabled again. systemctl reports
"active (running)".

Expected behavior:
Remote Desktop should stay disabled upon the new login.

Actual behavior:
Remote Desktop was automatically enabled again.

Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control-
center/-/issues/1775#note_1443319

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1971415/+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 1973028] Re: gnome-remote-desktop user service is always running

** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1736

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

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

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

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

This was a contributing factor for LP: #1971415

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

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

It should show the service as "Active: inactive"

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

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

More details
---
This fix uses a dpkg maintscript to remove
/etc/systemd/user/gnome-session.target.wants/gnome-remote-desktop.service .
(That file is a symlink to the actual service).

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

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

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

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

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

[Desktop-packages] [Bug 1973619] Re: Sane net autodiscovery not working in 22.04

** Changed in: sane-backends (Ubuntu)
   Status: Incomplete => New

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

Title:
  Sane net autodiscovery not working in 22.04

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I have used every Ubuntu version since 16.10 and on all of them my
  network scanner EPSON SX525WD could be discovered out of the box.

  On 22.04 the output of 'scanimage -L' is:

  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).

  
  To double-check if something hadn't changed in my network, I opened a laptop 
which still has Ubuntu 21.10 installed. I ran 'scanimage -L' and it shows:

  device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner
  device `airscan:w0:EPSON Epson Stylus SX525WD' is a WSD EPSON Epson Stylus 
SX525WD ip=192.168.8.8

  
  My current workaround for 22.04 is to append the line:
net 192.168.8.8
  to /etc/sane.d/epson2.conf. The command 'scanimage -L' detects the scanner 
(albeit no 'airscan' result shows up):

  device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner

  NOTE: I filled this bug under the 'sane-backends' package because this
  form gave this error: "sane-utils" does not exist in Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: sane-utils 1.1.1-5
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 15:53:46 2022
  InstallationDate: Installed on 2020-02-02 (833 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: sane-backends
  UpgradeStatus: Upgraded to jammy on 2022-05-06 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1973619/+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 1973440] Re: cheese preview image black/white and striped (no effect selected)

it's weird, maybe the clutter-gst update did fix it but you still had
the old version loaded? closing for now but feel free to reopen if
needed

** Changed in: cheese (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  cheese preview image black/white and striped (no effect selected)

Status in cheese package in Ubuntu:
  Invalid

Bug description:
  When starting cheese I see my picture, but it's without color and with 
stripes.
  It looks like a "bad TV Filter" or something, but I made sure no effect is 
selected at all.

  In the secont test of the bug reporting process, which appears to show
  the "original" camera image via gstreamer, the image is also wrong,
  but in another way. it's completely dark, but looking more closely, it
  seems to be the cam image, but extremely darkened so only a few of the
  most white parts of the actual image visible.

  Taking an actual shot with cheese seems to produce the actual image as
  is without any of both of these problems, so it seems to be the
  preview thats in error.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 5.17.7 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 13:50:43 2022
  InstallationDate: Installed on 2020-04-12 (762 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QV00CEGE
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: cheese
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (16 days ago)
  dmi.bios.date: 12/06/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET55W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QV00CEGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QV00CEGE
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1973440/+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 1973634] Re: part of dialog is obscured, when selecting a compresssion type, in the "compress" dialog or the context menu

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

** This bug has been marked a duplicate of bug 1967480
   GUI error in "compress file". Menu content is wider than menu window.

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

Title:
  part of dialog is obscured, when selecting a compresssion type, in the
  "compress" dialog or the context menu

Status in nautilus package in Ubuntu:
  New

Bug description:
  Used the "compress" function from the context menu of the Nautilus
  browser.  When an attempt is made to select a compression type, part
  of the dialog is obscured...had to guess at it, to get the job done.
  (screenshot is attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.0-1ubuntu2 [modified: 
usr/share/applications/org.gnome.Nautilus.desktop]
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 13:59:40 2022
  InstallationDate: Installed on 2022-02-05 (99 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (15 days ago)
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1973634/+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 1973638] [NEW] gnome-shell memory leak after did 100+ screenshot

2022-05-16 Thread Sugihwaras

Public bug reported:

i running wine program and i want doing a lot screenshot. after did it
and close program. my system very laggy. i see at htop program my ram
and swap full.

my system info.

Host: mantari Kernel: 5.17.7-xanmod1 x86_64 bits: 64 compiler: gcc
v: 11.2.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.17.7-xanmod1
root=UUID=1dd447f7-2ae1-47c5-81cc-8584b22766d3 ro mitigations=off quiet
splash vt.handoff=7
  Desktop: GNOME 42.0 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3 42.0
Distro: Ubuntu 22.04 LTS (Jammy Jellyfish)
Machine:
  Type: Portable System: Dell product: Inspiron 3442 v: N/A
  Mobo: Dell model: 0T57PC v: A16 serial:  UEFI: Dell
v: A16 date: 09/02/2020
Battery:
  ID-1: BAT0 charge: 14.9 Wh (100.0%) condition: 14.9/41.4 Wh (36.0%)
volts: 16.8 min: 14.8 model: SMP-SDI2.8 DELL FW1MN31 type: Li-ion
serial: 4862 status: Full
Memory:
  RAM: total: 3.75 GiB 
Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: AU Optronics built: 2013 res: 1366x768 dpi: 112
gamma: 1.2 size: 309x173mm (12.2x6.8") diag: 354mm (13.9") ratio: 16:9
modes: 1366x768
  OpenGL: renderer: Mesa Intel HD Graphics (HSW GT1) v: 4.6 Mesa 22.0.1
compat-v: 3.1 direct render: Yes
Drives:
  Local Storage: total: 1.14 TiB used: 916.19 GiB (78.7%)
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD7500BPVX-75JC3T0 size: 698.64 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: WXA1A33W6463
rev: 1A01 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST500LM012 HN-M500MBB
size: 465.76 GiB block-size: physical: 4096 B logical: 512 B
speed: 3.0 Gb/s type: HDD rpm: 5400 serial: S2S7J9DC911744 rev: 0001
scheme: GPT
Swap:
  Kernel: swappiness: 30 (default 60) cache-pressure: 50 (default 100)
  ID-1: swap-1 type: zram size: 2.79 GiB used: 0 KiB (0.0%) priority: 5
dev: /dev/zram0
  ID-2: swap-2 type: zram size: 2.79 GiB used: 0 KiB (0.0%) priority: 5
dev: /dev/zram1

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 42.0-2ubuntu1
  Candidate: 42.0-2ubuntu1
  Version table:
 *** 42.0-2ubuntu1 500
500 https://mirror.internet.asn.au/pub/ubuntu/archive jammy/main amd64 
Packages
100 /var/lib/dpkg/status

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

** Attachment added: "htop screenshot after gnome-shell very laggy"
   
https://bugs.launchpad.net/bugs/1973638/+attachment/5590148/+files/gnome-shell.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/1973638

Title:
  gnome-shell memory leak after did 100+ screenshot

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  i running wine program and i want doing a lot screenshot. after did it
  and close program. my system very laggy. i see at htop program my ram
  and swap full.

  my system info.

  Host: mantari Kernel: 5.17.7-xanmod1 x86_64 bits: 64 compiler: gcc
  v: 11.2.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.17.7-xanmod1
  root=UUID=1dd447f7-2ae1-47c5-81cc-8584b22766d3 ro mitigations=off quiet
  splash vt.handoff=7
Desktop: GNOME 42.0 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3 42.0
  Distro: Ubuntu 22.04 LTS (Jammy Jellyfish)
  Machine:
Type: Portable System: Dell product: Inspiron 3442 v: N/A
Mobo: Dell model: 0T57PC v: A16 serial:  UEFI: Dell
  v: A16 date: 09/02/2020
  Battery:
ID-1: BAT0 charge: 14.9 Wh (100.0%) condition: 14.9/41.4 Wh (36.0%)
  volts: 16.8 min: 14.8 model: SMP-SDI2.8 DELL FW1MN31 type: Li-ion
  serial: 4862 status: Full
  Memory:
RAM: total: 3.75 GiB 
  Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: 
fbdev,vesa
  gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: AU Optronics built: 2013 res: 1366x768 dpi: 112
  gamma: 1.2 size: 309x173mm (12.2x6.8") diag: 354mm (13.9") ratio: 16:9
  modes: 1366x768
OpenGL: renderer: Mesa Intel HD Graphics (HSW GT1) v: 4.6 Mesa 22.0.1
  compat-v: 3.1 direct render: Yes
  Drives:
Local Storage: total: 1.14 TiB used: 916.19 GiB (78.7%)
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
  model: WD7500BPVX-75JC3T0 size: 698.64 GiB block-size: physical: 4096 B
  logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: WXA1A33W6463
  rev: 1A01 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST500LM012 HN-M500MBB
  size: 465.76 GiB block-size: physical: 4096 B logical: 512 B
  speed: 3.0 Gb/s type: HDD rpm: 5400 serial: S2S7J9DC911744 rev: 0001
  scheme: GPT
  Swap:
Kernel: swappiness: 30 (default 60) cache-pressure: 50 (default 100)
ID-1: swap-1 type: zram

[Desktop-packages] [Bug 1973619] Re: Sane net autodiscovery not working in 22.04

2022-05-16 Thread Joao Fraga

Yes, it is:

$ dpkg --get-selections *sane*
libsane-common  install
libsane-hpaio:amd64 install
libsane1:amd64  install
sane-airscaninstall
sane-utils  install

The exact same set of packages installed in my Ubuntu 21.10.
The only difference are the versions.

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

Title:
  Sane net autodiscovery not working in 22.04

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  I have used every Ubuntu version since 16.10 and on all of them my
  network scanner EPSON SX525WD could be discovered out of the box.

  On 22.04 the output of 'scanimage -L' is:

  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).

  
  To double-check if something hadn't changed in my network, I opened a laptop 
which still has Ubuntu 21.10 installed. I ran 'scanimage -L' and it shows:

  device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner
  device `airscan:w0:EPSON Epson Stylus SX525WD' is a WSD EPSON Epson Stylus 
SX525WD ip=192.168.8.8

  
  My current workaround for 22.04 is to append the line:
net 192.168.8.8
  to /etc/sane.d/epson2.conf. The command 'scanimage -L' detects the scanner 
(albeit no 'airscan' result shows up):

  device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner

  NOTE: I filled this bug under the 'sane-backends' package because this
  form gave this error: "sane-utils" does not exist in Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: sane-utils 1.1.1-5
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 15:53:46 2022
  InstallationDate: Installed on 2020-02-02 (833 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: sane-backends
  UpgradeStatus: Upgraded to jammy on 2022-05-06 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1973619/+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 1869979] Re: liborc-0.4.so doesn't exist after install

In accordance with Debian Policy, the unversioned .so is available in
the liborc-0.4-dev package.

https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#development-
files

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

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

Title:
  liborc-0.4.so doesn't exist after install

Status in orc package in Ubuntu:
  Invalid

Bug description:
  If you apt install liborc-0.4-0, there is no liborc-0.4.so file in
  /usr/lib/x86_64-linux-gnu/

  There IS a liborc-0.4.so.0 file that is a link to iborc-0.4.so.0.28.0, but 
there is no link with name liborc-0.4.so pointing to that same file. I don't 
know if this is a bug or expected behavior, but it does trigger issues with 
other packages, such as out-of-tree modules for GNURadio:
  https://github.com/bastibl/gr-foo/issues/24#issuecomment-606925453

  Those can be fixed with a simple symlink. If this is a problem with
  the build system of the other project (i.e., it should have picked up
  the so.0 file), my apologies and please close the issue. Thanks.

  System details:
  Description: Ubuntu 18.04.4 LTS
  Release: 18.04
  Version:
  liborc-0.4-0
Installed: 1:0.4.28-1
  Summary:
  I expect there to be a .so file by the name of the library somewhere on the 
system after installing. There is not one, but instead, the name I expect with 
a .so.0 extension exists, but there is no symlink with the expected name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/orc/+bug/1869979/+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 1973028] Re: gnome-remote-desktop user service is always running

2022-05-16 Thread Seth Arnold

Please use CVE-2022-1736 for the gnome-remote-desktop user service being
enabled on Ubuntu.

The Debian packaging, and derivatives of both Ubuntu and Debian, for
gnome-remote-desktop are probably very similar. The Debian policy
strongly encourages services to be running by default after
installation[1]. Ubuntu, however, strongly discourages open ports by
default[2].

So, while there may be identical code in the other distributions, this
may or may not be considered a vulnerability by the other distributions,
based on their own policies.

Thanks

[1]: https://www.debian.org/doc/debian-policy/ch-opersys.html#managing-the-links
"The default behaviour is to enable autostarting your package’s daemon"

[2]: https://wiki.ubuntu.com/Security/Features#ports
"Default installations of Ubuntu must have no listening network services
after initial install. Exceptions to this rule [enumerated exceptions elided]"

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1736

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

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

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

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

This was a contributing factor for LP: #1971415

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

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

It should show the service as "Active: inactive"

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

More details
---
This fix uses a dpkg maintscript to remove
/etc/systemd/user/gnome-session.target.wants/gnome-remote-desktop.service .
(That file is a symlink to the actual service).

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

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

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

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

[Desktop-packages] [Bug 1973440] Re: cheese preview image black/white and striped (no effect selected)

2022-05-16 Thread Henning Sprang

But, I also made a general apt update/upgrade, and after a reboot, this
problem is gone.

But I dont understand which of these updates could have helped there:

Start-Date: 2022-05-16  20:57:58
Commandline: apt upgrade
Requested-By: henning (1000)
Upgrade: libreoffice-calc:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-gnome:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
uno-libs-private:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-base-core:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-pdfimport:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-core:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libxml2-dev:amd64 (2.9.13+dfsg-1build1, 2.9.13+dfsg-1ubuntu0.1), 
libxml2-utils:amd64 (2.9.13+dfsg-1build1, 2.9.13+dfsg-1ubuntu0.1), 
libreoffice-common:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
ure:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), libreoffice-draw:amd64 
(1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), libuno-purpenvhelpergcc3-3:amd64 
(1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), libuno-cppu3:amd64 
(1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), libreoffice-impress:amd64 
(1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), libxml2:amd64 
(2.9.13+dfsg-1build1, 2.9.13+dfsg-1ubuntu0.1), libxml2:i386 
(2.9.13+dfsg-1build1, 2.9.13+dfsg-1ubuntu0.1), libuno-cppuhelpergcc3-3:amd64 
(1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), fonts-opensymbol:amd64 
(2:102.12+LibO7.3.2-0ubuntu2, 2:102.12+LibO7.3.3-0ubuntu0.22.04.1), 
libreoffice-style-colibre:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-writer:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libuno-salhelpergcc3-3:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-style-breeze:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-help-common:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
python3-uno:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libuno-sal3:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-ogltrans:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-style-yaru:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-math:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-gtk3:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-help-en-us:amd64 (1:7.3.2-0ubuntu2, 1:7.3.3-0ubuntu0.22.04.1), 
libreoffice-style-elementary:amd64 (1:7.3.2-0ubuntu2, 
1:7.3.3-0ubuntu0.22.04.1), python3-libxml2:amd64 (2.9.13+dfsg-1build1, 
2.9.13+dfsg-1ubuntu0.1)
End-Date: 2022-05-16  20:58:19


I will continue monitor this and see if this appears again. 
For now it's gone but I dont know why.

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

Title:
  cheese preview image black/white and striped (no effect selected)

Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  When starting cheese I see my picture, but it's without color and with 
stripes.
  It looks like a "bad TV Filter" or something, but I made sure no effect is 
selected at all.

  In the secont test of the bug reporting process, which appears to show
  the "original" camera image via gstreamer, the image is also wrong,
  but in another way. it's completely dark, but looking more closely, it
  seems to be the cam image, but extremely darkened so only a few of the
  most white parts of the actual image visible.

  Taking an actual shot with cheese seems to produce the actual image as
  is without any of both of these problems, so it seems to be the
  preview thats in error.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 5.17.7 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 13:50:43 2022
  InstallationDate: Installed on 2020-04-12 (762 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QV00CEGE
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: cheese
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (16 days ago)
  dmi.bios.date: 12/06/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET55W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QV00CEGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name:

[Desktop-packages] [Bug 1973440] Re: cheese preview image black/white and striped (no effect selected)

2022-05-16 Thread Henning Sprang

Hmm, ok I didnt want to wait for an answer, manually downloaded thze
*build2* versions, but realized I appear to have them already:

$ apt search gst-3.0
Sorting... Done
Full Text Search... Done
gir1.2-clutter-gst-3.0/jammy,now 3.0.27-2build2 amd64 [installed]
  Gobject introspection data for Clutter GStreamer elements

libclutter-gst-3.0-0/jammy,now 3.0.27-2build2 amd64 [installed,automatic]
  Open GL based interactive canvas library GStreamer elements

and also:
$ apt search gstreamer1.0-clutter-3.0
Sorting... Done
Full Text Search... Done
gstreamer1.0-clutter-3.0/jammy,now 3.0.27-2build2 amd64 [installed,automatic]
  Clutter PLugin for GStreamer 1.0


If that is not the right thing to try, please let me know what exactly I
should do - thanks ;)

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

Title:
  cheese preview image black/white and striped (no effect selected)

Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  When starting cheese I see my picture, but it's without color and with 
stripes.
  It looks like a "bad TV Filter" or something, but I made sure no effect is 
selected at all.

  In the secont test of the bug reporting process, which appears to show
  the "original" camera image via gstreamer, the image is also wrong,
  but in another way. it's completely dark, but looking more closely, it
  seems to be the cam image, but extremely darkened so only a few of the
  most white parts of the actual image visible.

  Taking an actual shot with cheese seems to produce the actual image as
  is without any of both of these problems, so it seems to be the
  preview thats in error.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 5.17.7 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 13:50:43 2022
  InstallationDate: Installed on 2020-04-12 (762 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QV00CEGE
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: cheese
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (16 days ago)
  dmi.bios.date: 12/06/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET55W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QV00CEGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QV00CEGE
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1973440/+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 1973634] [NEW] part of dialog is obscured, when selecting a compresssion type, in the "compress" dialog or the context menu

2022-05-16 Thread Reverend Fuzzy

Public bug reported:

Used the "compress" function from the context menu of the Nautilus
browser.  When an attempt is made to select a compression type, part of
the dialog is obscured...had to guess at it, to get the job done.
(screenshot is attached)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42.0-1ubuntu2 [modified: 
usr/share/applications/org.gnome.Nautilus.desktop]
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 16 13:59:40 2022
InstallationDate: Installed on 2022-02-05 (99 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to jammy on 2022-04-30 (15 days ago)
usr_lib_nautilus:
 evince42.1-3
 file-roller   3.42.0-1
 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
 nautilus-share0.7.3-2ubuntu6

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


** Tags: amd64 apport-bug jammy

** Attachment added: "screenshot of issue in progress."
   
https://bugs.launchpad.net/bugs/1973634/+attachment/5590142/+files/Screenshot%20from%202022-05-16%2013-57-40.png

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

Title:
  part of dialog is obscured, when selecting a compresssion type, in the
  "compress" dialog or the context menu

Status in nautilus package in Ubuntu:
  New

Bug description:
  Used the "compress" function from the context menu of the Nautilus
  browser.  When an attempt is made to select a compression type, part
  of the dialog is obscured...had to guess at it, to get the job done.
  (screenshot is attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.0-1ubuntu2 [modified: 
usr/share/applications/org.gnome.Nautilus.desktop]
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 13:59:40 2022
  InstallationDate: Installed on 2022-02-05 (99 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (15 days ago)
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1973634/+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 1973629] [NEW] Wifi hotspot not configured correctly on restart

2022-05-16 Thread constantin budin

Public bug reported:

I have configured the hotspot to automatically start at startup. The
hotspot correctly starts on startup, but it appears to be configured
incorrectly. No device connected to it can reach the internet. When
opening the settings, Wifi is indicated to be disabled, even though the
hotspot is running (see screenshot).

The expectation is that the hotpot to be fully functional on startup
meaning every device connected to it can reach the internet.

Currently the issue can be fixed by activating Wifi and then starting a
hotspot, even though the hotspot is already running. The hotspot started
at startup does not have to be shut down before starting a hotspot in
the settings.

All this leads me to believe that somewhere the configuration of Wifi
goes wrong on startup.


Running Ubuntu 22.04

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: dconf-service 0.40.0-3
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 16 19:59:02 2022
InstallationDate: Installed on 2021-12-08 (159 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: dconf
UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago)

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


** Tags: amd64 apport-bug jammy

** Attachment added: "Wifi disabled while hotspot is running"
   
https://bugs.launchpad.net/bugs/1973629/+attachment/5590114/+files/screen1.png

** Attachment removed: "Wifi disabled while hotspot is running"
   
https://bugs.launchpad.net/ubuntu/+source/dconf/+bug/1973629/+attachment/5590114/+files/screen1.png

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

Title:
  Wifi hotspot not configured correctly on restart

Status in dconf package in Ubuntu:
  New

Bug description:
  I have configured the hotspot to automatically start at startup. The
  hotspot correctly starts on startup, but it appears to be configured
  incorrectly. No device connected to it can reach the internet. When
  opening the settings, Wifi is indicated to be disabled, even though
  the hotspot is running (see screenshot).

  The expectation is that the hotpot to be fully functional on startup
  meaning every device connected to it can reach the internet.

  Currently the issue can be fixed by activating Wifi and then starting
  a hotspot, even though the hotspot is already running. The hotspot
  started at startup does not have to be shut down before starting a
  hotspot in the settings.

  All this leads me to believe that somewhere the configuration of Wifi
  goes wrong on startup.

  
  Running Ubuntu 22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dconf-service 0.40.0-3
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 19:59:02 2022
  InstallationDate: Installed on 2021-12-08 (159 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: dconf
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dconf/+bug/1973629/+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 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04

2022-05-16 Thread Ted Gould

The way that I'm testing this is with the candidate release for
Inkscape. Which is 1.2, you can grab as a snap with: snap install
--candidate inkscape.

In Inkscape if you just draw on the canvas and hit save a save dialog
will appear. There is a selector at the bottom right that adjust which
files you see, but also which format you want to save in. So if you make
your file "test.pdf" and select "Portable Document Format (*.pdf)" in
the selector you should get a PDF file. Before these patches you will
get a file "test.pdf" which is actually an SVG file. After the patches
you'll get a "test.pdf" that is actually a PDF.

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.04

Status in xdg-desktop-portal package in Ubuntu:
  New
Status in xdg-desktop-portal-gtk package in Ubuntu:
  New
Status in xdg-desktop-portal source package in Focal:
  New
Status in xdg-desktop-portal-gtk source package in Focal:
  New

Bug description:
  The file dialog implementation doesn't return the current filter. It
  is in the spec and it is fixed in newer versions of the portals. But
  the 1.6.0 version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+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 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04

2022-05-16 Thread Ted Gould

Okay, so it turns out that the implementation wrapper also doesn't pass
the value.

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

** Patch added: "xdg-desktop-portal-1.6.0-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+attachment/5590110/+files/xdg-desktop-portal-1.6.0-1ubuntu1.debdiff

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.04

Status in xdg-desktop-portal package in Ubuntu:
  New
Status in xdg-desktop-portal-gtk package in Ubuntu:
  New
Status in xdg-desktop-portal source package in Focal:
  New
Status in xdg-desktop-portal-gtk source package in Focal:
  New

Bug description:
  The file dialog implementation doesn't return the current filter. It
  is in the spec and it is fixed in newer versions of the portals. But
  the 1.6.0 version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+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 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER

2022-05-16 Thread Erik Meitner

Any solution needs to work with multiple home folder locations that can
be located anywhere. We've got 540 users spread among four different
folders: /fac/, /grad/, /staff/, /visitor/.

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

Title:
  Unable to start snap applications if user's home directory is not
  /home/$USER

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  Users with home directories in /home/$USER can run snap application,
  but users in /home/users/$USER can't.

  nate@WorkstationC:~$ snap --version
  snap2.32.8+18.04
  snapd   2.32.8+18.04
  series  16
  ubuntu  18.04
  kernel  4.15.0-22-generic
  nate@WorkstationC:~$ echo $HOME
  /home/users/nate
  nate@WorkstationC:~$ which hello-world
  /snap/bin/hello-world
  nate@WorkstationC:~$ hello-world
  cannot create nate data directory: /home/users/nate/snap/hello-world/27: 
Permission denied

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


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

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

2022-05-16 Thread Krister Swenson

https://bugzilla.mozilla.org/show_bug.cgi?id=1769594

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

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

Title:
  can no longer open new windows after some time

Status in firefox package in Ubuntu:
  Incomplete

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

  => ps -ef | grep -c firefox
  21

  => /snap/bin/firefox

  => ps -ef | grep -c firefox
  21

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

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

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

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


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

[Desktop-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2022-05-16 Thread Ubucolors

Good news for Belgians who connect tot the government site with there id
card.

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions


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

Re: [Desktop-packages] [Bug 1973440] Re: cheese preview image black/white and striped (no effect selected)

2022-05-16 Thread Henning Sprang

yes i can test that, no problem!
But which of the debs do I need to install - one, some or all? and is
there a "simple" command to do it or should I click through to the
debs and manually download them?
(just started to look into and found there are some debs after a few
clicks, but now sure which to chose, some have also multiple builds...

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

Title:
  cheese preview image black/white and striped (no effect selected)

Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  When starting cheese I see my picture, but it's without color and with 
stripes.
  It looks like a "bad TV Filter" or something, but I made sure no effect is 
selected at all.

  In the secont test of the bug reporting process, which appears to show
  the "original" camera image via gstreamer, the image is also wrong,
  but in another way. it's completely dark, but looking more closely, it
  seems to be the cam image, but extremely darkened so only a few of the
  most white parts of the actual image visible.

  Taking an actual shot with cheese seems to produce the actual image as
  is without any of both of these problems, so it seems to be the
  preview thats in error.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 5.17.7 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 13:50:43 2022
  InstallationDate: Installed on 2020-04-12 (762 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QV00CEGE
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: cheese
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (16 days ago)
  dmi.bios.date: 12/06/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET55W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QV00CEGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QV00CEGE
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO

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


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

Re: [Desktop-packages] [Bug 1973464] Re: Firefox does not supply name when it asks to open default keyring in Lubuntu 20.04

2022-05-16 Thread sem

Please see attached the ubuntu-bug attachment, and let me know if I still
need to do this again.

Thanks!

On Sun, May 15, 2022 at 10:05 PM Chris Guiver <1973...@bugs.launchpad.net>
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please execute the following command only once, as it
> will automatically gather debugging information, in a terminal:
>
> apport-collect 1973464
>
> When reporting bugs in the future please use apport by using 'ubuntu-
> bug' and the name of the package affected. You can learn more about this
> functionality at https://wiki.ubuntu.com/ReportingBugs.
>
>
> (please run it on the impacted box; so details can be correctly populated
> allowing exploration using tools)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1973464
>
> Title:
>   Firefox does not supply name when it asks to open default keyring in
>   Lubuntu 20.04
>
> Status in firefox package in Ubuntu:
>   New
>
> Bug description:
>   When using auto-login in Lubuntu 20.04 LTS, browsing firefox causes
>   firefox to send a request to the default keyring to unlock.
>
>   The problem is, it doesn't provide any information about what
>   application is making the request. This can be disorienting to the
>   user, especially since the security prompt locks out the system until
>   you enter the password or press cancel, with no hints about why you're
>   getting the message.
>
>   Image: application asking to unlock default keyring.
>   https://i.ibb.co/4K36pqT/48cce3e1-abfc-4b12-9561-acb2a78da7bd.jpg
>
>   I have verified that it is firefox, by removing
>   ~/.local/share/keyrings directory, and restarting the system. When
>   firefox is opened again, you get a new message asking you to create a
>   new password for the default keyring.
>
>   Image: Opening firefox prompts the creation of a new password for the
> default keyring.
>   https://i.ibb.co/RpSJ8L6/4fda479e-4603-4330-80cf-e2bc20643a61.jpg
>
>   I am not sure what program is handling the default keyring on lubuntu.
>   Would it be possible for firefox to supply its name when interacting
>   with the default keyring?
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973464/+subscriptions
>
>

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

Title:
  Firefox does not supply name when it asks to open default keyring in
  Lubuntu 20.04

Status in firefox package in Ubuntu:
  New

Bug description:
  When using auto-login in Lubuntu 20.04 LTS, browsing firefox causes
  firefox to send a request to the default keyring to unlock.

  The problem is, it doesn't provide any information about what
  application is making the request. This can be disorienting to the
  user, especially since the security prompt locks out the system until
  you enter the password or press cancel, with no hints about why you're
  getting the message.

  Image: application asking to unlock default keyring.
  https://i.ibb.co/4K36pqT/48cce3e1-abfc-4b12-9561-acb2a78da7bd.jpg

  I have verified that it is firefox, by removing
  ~/.local/share/keyrings directory, and restarting the system. When
  firefox is opened again, you get a new message asking you to create a
  new password for the default keyring.

  Image: Opening firefox prompts the creation of a new password for the default 
keyring.
  https://i.ibb.co/RpSJ8L6/4fda479e-4603-4330-80cf-e2bc20643a61.jpg

  I am not sure what program is handling the default keyring on lubuntu.
  Would it be possible for firefox to supply its name when interacting
  with the default keyring?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973464/+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 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER

2022-05-16 Thread C. Jeffery Small

Just to make sure the note is here, my home directory is not in /home at
all, but located under /u which is a mount point for an external volume
on another disk.  I experienced the same problem trying to run a snap.
Whatever the solution, it should be generalized to any $HOME location.

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

Title:
  Unable to start snap applications if user's home directory is not
  /home/$USER

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  Users with home directories in /home/$USER can run snap application,
  but users in /home/users/$USER can't.

  nate@WorkstationC:~$ snap --version
  snap2.32.8+18.04
  snapd   2.32.8+18.04
  series  16
  ubuntu  18.04
  kernel  4.15.0-22-generic
  nate@WorkstationC:~$ echo $HOME
  /home/users/nate
  nate@WorkstationC:~$ which hello-world
  /snap/bin/hello-world
  nate@WorkstationC:~$ hello-world
  cannot create nate data directory: /home/users/nate/snap/hello-world/27: 
Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776800/+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 1973619] Re: Sane net autodiscovery not working in 22.04

Thanks for your report.

Question: Is sane-airscan installed? (It ought to be, since libsane1
recommends it.)

** Changed in: sane-backends (Ubuntu)
   Status: New => Incomplete

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

Title:
  Sane net autodiscovery not working in 22.04

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  I have used every Ubuntu version since 16.10 and on all of them my
  network scanner EPSON SX525WD could be discovered out of the box.

  On 22.04 the output of 'scanimage -L' is:

  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).

  
  To double-check if something hadn't changed in my network, I opened a laptop 
which still has Ubuntu 21.10 installed. I ran 'scanimage -L' and it shows:

  device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner
  device `airscan:w0:EPSON Epson Stylus SX525WD' is a WSD EPSON Epson Stylus 
SX525WD ip=192.168.8.8

  
  My current workaround for 22.04 is to append the line:
net 192.168.8.8
  to /etc/sane.d/epson2.conf. The command 'scanimage -L' detects the scanner 
(albeit no 'airscan' result shows up):

  device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner

  NOTE: I filled this bug under the 'sane-backends' package because this
  form gave this error: "sane-utils" does not exist in Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: sane-utils 1.1.1-5
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 15:53:46 2022
  InstallationDate: Installed on 2020-02-02 (833 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: sane-backends
  UpgradeStatus: Upgraded to jammy on 2022-05-06 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1973619/+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 1960014] Re: Missing Dutch language interface for LibreOffice in Snap installation

2022-05-16 Thread Peter Roelofsen

That works, thanks!

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

Title:
  Missing Dutch language interface for LibreOffice in Snap installation

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Hi. My native language is Dutch, I live in the Netherlands, but when I
  get the LibreOffice packages from Ubuntu Linux (Snap), I can choose
  from only 15 interface languages, and Dutch is not one of them. Even
  though Dutch is available as interface language on the generic
  LibreOffice that can be downloaded from the LibreOffice website, but
  that isn’t automatically updated. For Dutch people who aren’t very
  good at English, or are good at it but still want the Dutch interface
  language, this is a bit of a problem, especially because it isn’t at
  all obvious how you can download & install a separate language pack.
  This topic in Ask LibreOffice is about the same problem (warning: text
  in Dutch): https://ask.libreoffice.org/t/kan-de-user-interface-taal-
  niet-veranderen/73301/5 Can this be fixed?

  Currently on: Version: 7.2.5.2.0+ / LibreOffice Community Build ID:
  711f8d38e9451cd2fd39b6963d2a3fc166f04cb1 CPU threads: 4; OS: Linux
  5.4; UI render: default; VCL: gtk3 Locale: nl-NL (nl_NL.UTF-8); UI:
  en-US Calc: threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1960014/+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 1931603] Re: [apparmor] Unable to show Downloads with apparmor enabled

Fix committed:

https://bazaar.launchpad.net/~mozillateam/firefox/firefox.focal/revision/1552

https://bazaar.launchpad.net/~mozillateam/firefox/firefox.impish/revision/1585

The update will make its way to the security and updates pockets with
the next stable update of firefox.

** Changed in: firefox (Ubuntu Focal)
   Status: Confirmed => Fix Committed

** Changed in: firefox (Ubuntu Impish)
   Status: Confirmed => Fix Committed

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

Title:
  [apparmor] Unable to show Downloads with apparmor enabled

Status in firefox package in Ubuntu:
  Invalid
Status in firefox source package in Focal:
  Fix Committed
Status in firefox source package in Hirsute:
  Won't Fix
Status in firefox source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * After a finished download (or opening the downloads list) it is
  impossible to "Open Containing Folder" for a downloaded file -
  pressing the button does nothing visible.

  [Test Plan]

   * sudo aa-enforce /etc/apparmor.d/usr.bin.firefox

   * launch Firefox

   * Download a file.

   * Go to downloads list.

   * Press the "Open Containing Folder" button next to the downloaded
  file on the list.

  [Where problems could occur]

  Unlocking the possibility of launching file browser from Firefox, that
  was not working before may result in windows popping up where they
  have not earlier (e.g. from the Downloads window, downloads list).

  [Other Info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931603/+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 1931603] Re: [apparmor] Unable to show Downloads with apparmor enabled

** Branch linked: lp:~mozillateam/firefox/firefox.bionic

** Branch linked: lp:~mozillateam/firefox/firefox.focal

** Branch linked: lp:~mozillateam/firefox/firefox.impish

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

Title:
  [apparmor] Unable to show Downloads with apparmor enabled

Status in firefox package in Ubuntu:
  Invalid
Status in firefox source package in Focal:
  Fix Committed
Status in firefox source package in Hirsute:
  Won't Fix
Status in firefox source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * After a finished download (or opening the downloads list) it is
  impossible to "Open Containing Folder" for a downloaded file -
  pressing the button does nothing visible.

  [Test Plan]

   * sudo aa-enforce /etc/apparmor.d/usr.bin.firefox

   * launch Firefox

   * Download a file.

   * Go to downloads list.

   * Press the "Open Containing Folder" button next to the downloaded
  file on the list.

  [Where problems could occur]

  Unlocking the possibility of launching file browser from Firefox, that
  was not working before may result in windows popping up where they
  have not earlier (e.g. from the Downloads window, downloads list).

  [Other Info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931603/+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 1973619] [NEW] Sane net autodiscovery not working in 22.04

2022-05-16 Thread Joao Fraga

Public bug reported:

I have used every Ubuntu version since 16.10 and on all of them my
network scanner EPSON SX525WD could be discovered out of the box.

On 22.04 the output of 'scanimage -L' is:

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).


To double-check if something hadn't changed in my network, I opened a laptop 
which still has Ubuntu 21.10 installed. I ran 'scanimage -L' and it shows:

device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner
device `airscan:w0:EPSON Epson Stylus SX525WD' is a WSD EPSON Epson Stylus 
SX525WD ip=192.168.8.8


My current workaround for 22.04 is to append the line:
  net 192.168.8.8
to /etc/sane.d/epson2.conf. The command 'scanimage -L' detects the scanner 
(albeit no 'airscan' result shows up):

device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner

NOTE: I filled this bug under the 'sane-backends' package because this
form gave this error: "sane-utils" does not exist in Ubuntu

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: sane-utils 1.1.1-5
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon May 16 15:53:46 2022
InstallationDate: Installed on 2020-02-02 (833 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: sane-backends
UpgradeStatus: Upgraded to jammy on 2022-05-06 (9 days ago)

** Affects: sane-backends (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 sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1973619

Title:
  Sane net autodiscovery not working in 22.04

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I have used every Ubuntu version since 16.10 and on all of them my
  network scanner EPSON SX525WD could be discovered out of the box.

  On 22.04 the output of 'scanimage -L' is:

  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).

  
  To double-check if something hadn't changed in my network, I opened a laptop 
which still has Ubuntu 21.10 installed. I ran 'scanimage -L' and it shows:

  device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner
  device `airscan:w0:EPSON Epson Stylus SX525WD' is a WSD EPSON Epson Stylus 
SX525WD ip=192.168.8.8

  
  My current workaround for 22.04 is to append the line:
net 192.168.8.8
  to /etc/sane.d/epson2.conf. The command 'scanimage -L' detects the scanner 
(albeit no 'airscan' result shows up):

  device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner

  NOTE: I filled this bug under the 'sane-backends' package because this
  form gave this error: "sane-utils" does not exist in Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: sane-utils 1.1.1-5
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 15:53:46 2022
  InstallationDate: Installed on 2020-02-02 (833 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: sane-backends
  UpgradeStatus: Upgraded to jammy on 2022-05-06 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1973619/+subscriptions


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

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

2022-05-16 Thread Erich Eickmeyer 

Thank you for taking the time to report this bug and help make Ubuntu
better. Firefox is provided by a snap published by Mozilla, and they may
not be aware of this issue. Please contact them via
https://support.mozilla.org/kb/file-bug-report-or-feature-request-
mozilla and link the bug report here so it can be further tracked. Thank
you!

** 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/1973618

Title:
  can no longer open new windows after some time

Status in firefox package in Ubuntu:
  Incomplete

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

  => ps -ef | grep -c firefox
  21

  => /snap/bin/firefox

  => ps -ef | grep -c firefox
  21

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

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

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

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


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

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

2022-05-16 Thread Krister Swenson

Public bug reported:

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

=> ps -ef | grep -c firefox
21

=> /snap/bin/firefox

=> ps -ef | grep -c firefox
21

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

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

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

** Affects: firefox (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 firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1973618

Title:
  can no longer open new windows after some time

Status in firefox package in Ubuntu:
  New

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

  => ps -ef | grep -c firefox
  21

  => /snap/bin/firefox

  => ps -ef | grep -c firefox
  21

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

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

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

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


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

[Desktop-packages] [Bug 1973615] Re: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()

2022-05-16 Thread Apport retracing service

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

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 #1965897, 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/1973615/+attachment/5590073/+files/CoreDump.gz

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

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

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

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

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

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

** 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1973615

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_window_type()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Could be a duplicate of LP1972812

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 14 15:23:54 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1649813447
  InstallationDate: Installed on 2022-05-10 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/addyess
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_window_type () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   meta_display_close () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   shell_global_reexec_self () from /usr/lib/gnome-shell/libgnome-shell.so
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  mtime.conffile..etc.apport.crashdb.conf: 2022-05-12T08:10:45.865414
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973615/+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 1972812] Re: gnome-shell (X11, nvidia-390) crashes with SIGSEGV when unlocking the screen

2022-05-16 Thread Adam Dyess

Finally got the crashdump uploaded but had to add all the details to a
new ticket: LP#1973615

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

Title:
  gnome-shell (X11, nvidia-390) crashes with SIGSEGV when unlocking the
  screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I found a security vulnerability in Ubuntu 22.04 LTS operating system 
(Laptops only) It is reproduced like this (in steps):
  1. I lock the screen Win + L
  2. Close the laptop lid
  3. Then I open the lid of the laptop
  4. I get a vulnerability, the operating system does not ask for a password, 
but immediately shows the desktop without the need to unlock it. that is, 
closing and opening the laptop lid leads to unlocking the screen without asking 
for a password.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 12:20:28 2022
  InstallationDate: Installed on 2022-04-21 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  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/1972812/+subscriptions


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

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

Using 70~ubuntu3.21.10.1 there is no visble delay and the icons are
still right

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

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

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

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

Bug description:
  [ Impact ]

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

  [ Test case ]

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

  [ Regression potential ]

  Mounted devices will have wrong or no icon.

  

  I just upgraded from Ubuntu 18.04 to 20.04.

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

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

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


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

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

Using 70~ubuntu3.21.10.1 there is no freeze and the previews are correct

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

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

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

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

Bug description:
  [ Impact ]

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

  [ Test case ]

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

  [ Regression potential]

  No windows previews are showing in the application menu

  ---

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

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


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

[Desktop-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

2022-05-16 Thread Robert C Jennings

Promotion from -proposed sure would be nice.  I see verification has
been done but a update excuses shows an netplan.io regression[1].  I'm
not sure if the test is flaky but I see that seb retried it a few
times[2] last week and it failed consistently, so maybe not.

I'm just curious if there's any status on the test failure.

(Also, I started writing this thinking it had been a month but it's been
less than a week and I can't tell time.  I know it wouldn't be promoted
with less than a week in -proposed anyway.)

[1] 
https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#wpa
[2] https://autopkgtest.ubuntu.com/packages/netplan.io/jammy/arm64

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

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

Bug description:
  * Impact

  Connecting to some PEAP wifi doesn't work anymore since the openssl3
  transition

  Details on the issue can be found on
  http://lists.infradead.org/pipermail/hostap/2022-May/040511.html

  * Test case

  Try using a PEAP wifi not implementing RFC5746, it should be able to
  connect

  * Regression potential

  The change allows to connect to less secure WiFis the same way that
  wpa allowed before openssl3, lower security enforcement isn't ideal
  but still better than non working hardware.

  

  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.release-upgrades:
  2022-02-27T21:07:16.553410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1972766] Re: Changing default mounting options causes root owner

Thank you for your bug report. That's probably worth reporting upstream
on https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues

Unsure it is changing the mount option, when selecting as an user it can
map to the user who did the action but for a system mount that's not
possible. The UI could provide easier way to set those options though

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

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

Title:
  Changing default mounting options causes root owner

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04
  If I change the default mounting options in Gnome Disk Utility the owner is 
root.  This threw me for a loop when all of my git repos were not working.  I 
thought it was an ubuntu 22.04 problem or a ppa.

  It is directly from Gnome Disk Utility by changing the auto mount
  options.  I don't remember this happening before.

  Reproduce

  **Control:**
  Under default mount options.
  Go to your data partition, right click and look at properties/permissions.
  You will be the owner.

  **Cause the bug.**
  Select a data partition you might have (ntfs) for dual boot machines to share 
data.
  Change the switch from default mounting options (top switch) to manual 
settings.  Change label to human readable. ("Data").  Reboot.

  Go to your data partition, right click and look at
  properties/permissions.

  It will say the owner is root and you are not the owner.

  **Fix For The Problem:**
  It took a long time, but I had to add uid=1000,gid=1000 to the settings.  
This hard to research "mystery setting" is not acceptable for a GUI mounting 
tool.

  Reboot.
  Go to your data partition, right click and look at properties/permissions
  You will be the owner.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1972766/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

2022-05-16 Thread Robert C Jennings

Thank you Seb, I had the issue reported in this bug in a WeWork today
(first time connecting since updating to Jammy) and the package in
-proposed resolved the issue for me as well.

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

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

Bug description:
  * Impact

  Connecting to some PEAP wifi doesn't work anymore since the openssl3
  transition

  Details on the issue can be found on
  http://lists.infradead.org/pipermail/hostap/2022-May/040511.html

  * Test case

  Try using a PEAP wifi not implementing RFC5746, it should be able to
  connect

  * Regression potential

  The change allows to connect to less secure WiFis the same way that
  wpa allowed before openssl3, lower security enforcement isn't ideal
  but still better than non working hardware.

  

  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.release-upgrades:
  2022-02-27T21:07:16.553410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1973394] Re: Can't find integrated camera in Ubuntu 22.04 on Lenovo

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

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

Title:
  Can't find integrated camera in Ubuntu 22.04 on Lenovo

Status in linux package in Ubuntu:
  New

Bug description:
  Dual boot, Win 10 & Ubuntu 22.04.
  Camera works on Win but not discoverable on Ubuntu 22.04
  Never any image or video in cheese
  F6 does not turn it on in Cheese.
  Used synaptic, nothing broken.
  Checked for driver, nothing available.

  Boot from USB (ie install iso) Cheese does not work in "try Ubuntu"
  mode, ie cheese cannot find camera.

  I have tried other programs that use the camera & none work.
  Looks like a driver is missing to me but I can't find one to add. 

  I know the camera is there & working in Windows. 
  Something is missing for it to work in Ubuntu 22.04

  1)Ubuntu 22.04 LTS
  2)Cheese
  3)expected camera to open
  4)Message "there was an error playing video from the webcam"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973394/+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 1973425] Re: 22.04 file chooser automatically resizing in snap apps

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

** This bug has been marked a duplicate of bug 1971112
   File picker gets bigger more and more each time!

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

Title:
  22.04 file chooser automatically resizing in snap apps

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

Bug description:
  The open and save file dialog popup in Firefox or Brave enlarge
  themselves in approximately 1 second intervals until they take up the
  entire screen and do not respond correctly to input, with the window
  automatically reopening. It is possible to close the misbehaving app
  from the dock. Setting org.gtk.gtk4.Settings.FileChooser window-size
  to (-1, -1) only loops back to a new file chooser dialog being the
  correct size for the first second. Deb/apt pacakged apps like Evince
  don't have this issue, same for snaps using Qt (VLC). It is possible
  that I unplugged a docking station while a dialog was open.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal 1.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 14 08:39:01 2022
  InstallationDate: Installed on 2022-04-22 (22 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1973425/+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 1973468] Re: New Windows from favorites often not working

Thank you for your bug report? Could you do

$ journalctl -f

then try to trigger the bug and copy the log section once you get the
issue?

** 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/1973468

Title:
  New Windows from favorites often not working

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Running Ubuntu 22.04 jammy, firefox 100 from snap.

  First time launch from the left launcher (favorites) normally works
  fine.  Open a second window using the context menu "New Window" or
  "Open a New Windows" (what is the difference?) often just gives the
  rotating Ubuntu cursor and no Firefox window is opened.   Sometimes
  works though, so you have to try a few times.

  ^N in an open firefox window work fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973468/+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 1973610] [NEW] Bluetooth will not stay on or connect to devices when on

2022-05-16 Thread wolfgang rumpf

Public bug reported:

Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as
an external usb dongle will not work.  Bluetooth starts as off, and
cannot be turned on.  If I use systemctl to turn it on, it is on but
doesn't find any devices through bluez.  Blueman finds devices but
cannot connect to them.  The hardware on this machine has remained
identical; the only difference is the new version of Ubuntu.  Hence the
problem has to be software.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 16 09:45:02 2022
InstallationDate: Installed on 2021-10-22 (205 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago)
dmi.bios.date: 08/04/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P1.50
dmi.board.name: N7 B550
dmi.board.vendor: NZXT
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:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr: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.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 5C:F3:70:A8:66:B1  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN INIT RUNNING 
RX bytes:175353 acl:52 sco:0 events:6887 errors:0
TX bytes:18571 acl:52 sco:0 commands:1087 errors:2
mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340

** Affects: bluez (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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1973610

Title:
  Bluetooth will not stay on or connect to devices when on

Status in bluez package in Ubuntu:
  New

Bug description:
  Since upgrading from Ubuntu 20.10, my internal bluetooth card as well
  as an external usb dongle will not work.  Bluetooth starts as off, and
  cannot be turned on.  If I use systemctl to turn it on, it is on but
  doesn't find any devices through bluez.  Blueman finds devices but
  cannot connect to them.  The hardware on this machine has remained
  identical; the only difference is the new version of Ubuntu.  Hence
  the problem has to be software.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 09:45:02 2022
  InstallationDate: Installed on 2021-10-22 (205 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago)
  dmi.bios.date: 08/04/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P1.50
  dmi.board.name: N7 B550
  dmi.board.vendor: NZXT
  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:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr: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.

[Desktop-packages] [Bug 1973474] Re: Rename "Pin to Dash" to "Pin to Dock"

If we go this route, we'll need yet another conditional in dash-to-dock.
Adding gnome-shell-extension-ubuntu-dock as affected package.

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Rename "Pin to Dash" to "Pin to Dock"

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  I noticed this commit:

  https://github.com/micheleg/dash-to-dock/commit/8ee55c29

  If I understand it correctly, it means that we will use the label "Pin
  to Dash" instead of "Add to Favorites" as from Ubuntu 22.10. To be
  consistent I suggest that we rename the thing in all contexts, and
  hence replace "Dock" with "Dash" in all affected strings in the
  Appearance section in g-c-c.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1973474/+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 1784774] Re: snapd is not autofs aware and fails with nfs home dir

2022-05-16 Thread Andrew Conway

Thanks Alberto. I tried running "hello" in a different directory, and
you were correct:

arc@andrewfairfield:~$ hello
cannot open path of the current working directory: Permission denied
arc@andrewfairfield:~$ cd /
arc@andrewfairfield:/$ hello
Hello, world!
arc@andrewfairfield:/$ 

[ This is in 20.04, not 22.04 ]

Yay! that is the first time I have seen a snap actually work with my
normal user account.

This feels like significant progress in working out what is going on!

Of course firefox needs access to the home directory to load the profile
and store downloads. Is the whole process run as some other user (a la
sudo) or is there just some starting stub running as some other user
doing something that returns to the actual user after doing something
that thinks it needs access to the current directory but could get by
without it?

Actually, I can sort of answer that - I tried running "musescore" as a snap, 
starting from /
It successfully ran. I tried saving something, and it sort of did... but in a 
new, empty "home" directory in a /home/arc/snap/musescore/216/ that the save 
file dialog went to when I pressed the home button. Is this normal behaviour 
for a snap? Regardless of the inconvenience of the subdirectory, that is 
running over nfs successfully. I can close Musescore and load it again. But not 
with cwd=/home/arc.

So that is fairly strong evidence supporting your idea that it is the
same root cause as https://bugs.launchpad.net/bugs/1973321 . I will add
a comment there.

Thanks for the insight Alberto!

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

Title:
  snapd is not autofs aware and fails with nfs home dir

Status in snapd:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  This is similar to bugs 1662552 and 1782873. In 1782873, jdstrand
  asked me to open a new bug for this specific issue.

  In 1662552, snapd fails for nfs mounted home directories as network
  permissions are not enabled. A work around was implemented that works
  if the mount is done via a /home mount at boot. However this does not
  work if people mount home directories via autofs. This is probably the
  fundamental problem for 1782873 although there may be other issues.

  [ Why use autofs? If some but not all of users want to use nfs homes.
  In particular, I have a local user on all my accounts that does not
  require the nfs server to be up or the kerberos server to be up, or
  kerberos working on the client machines, etc. It is very useful when
  something goes wrong. It means I mount /home/user rather than /home
  (for several users). ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1784774/+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 1778082] Re: Language Support Is Incomplete dialog must show package list to install

2022-05-16 Thread Little Girl

This is still an issue in Kubuntu 22.04 LTS. The QApt Batch Installer
will pop up a notification letting you know that additional packages are
required, but won't tell you what they are.

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

Title:
  Language Support Is Incomplete dialog must show package list to
  install

Status in kde-runtime package in Ubuntu:
  Confirmed
Status in language-selector package in Ubuntu:
  Confirmed

Bug description:
  When Ubuntu have missing language packages, it shows in tray System
  Notification Helper message with text "Language support is incomplete,
  additional packages are required".

  But when user do one simple mouse click on this notification - Ubuntu
  immediately asks user password with "Authentication Required" popup
  window, without describing what is planned to do, which packages are
  missing and will be installed.

  After typing password - user will not see any useful info too - only
  small window with unnamed progress bar and standard text phrases.

  After process finished - there are also zero useful info, only that
  process is finished.

  
  Please show more information about this process, before ask user password!

  Very useful info will be:

  - How this missed packages are detected?

  - Why those packages are missed?

  - What packages will planned to install/upgrade (package names,
  versions)?

  - Total size of planned downloads.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: language-selector-common 0.188.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jun 21 17:51:49 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1778082/+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 1973604] Re: [nvidia340] display hangs 10s on boot with nvidia-340

2022-05-16 Thread ysfr

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

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

Title:
  [nvidia340] display hangs 10s on boot with nvidia-340

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

Bug description:
  Since ubuntu-drivers-common 1:0.9.0~0.20.04.6,
  system running kernel 5.4 & nvidia-340 will experience
  10s useless delay on boot because 
  gpu-manager is waiting for nvidia-drm to load
  & nvidia-drm is not built in with nvidia-340.

  Several legacy nvidia cards are stuck to nvidia-340 & Kernel 5.4 as detailled 
in:
  
https://nvidia.custhelp.com/app/answers/detail/a_id/3142/%7E/support-timeframes-for-unix-legacy-gpu-releases

  See prior investigation in comments of
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1973604/+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 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe

2022-05-16 Thread ysfr

Thanks, just opened a separate bug:
[nvidia340] display hangs 10s on boot with nvidia-340
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1973604

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

Title:
  [nvidia][xorg] display hangs on boot LOGO due to race of gdm and
  nvidia driver probe

Status in OEM Priority Project:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Focal:
  Triaged
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in gdm3 source package in Impish:
  Triaged
Status in ubuntu-drivers-common source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg 
with proprietary nvidia driver), in some cases, the nvidia driver will probe 
later than launching gdm.
   * If above race condition happens in iGPU + nvidia cases and monitor 
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg. 
Which may lead the monitor stuck in black-screen or boot LOGO.

  [Test Plan]

   * The environment:
    1. A desktop or workstation which containing an iGPU.
    2. Plug a nvidia graphic card to the system and installing proprietary
    nvidia driver (470 in my case)
    3. Attach a monitor to dGPU and leave iGPU connect to nothing.
    (in my test environment, there is the other ethernet card and TBT4 cards)
   * Setup a cronjob,
     e.g. @reboot /home/u/test.sh
   * Have a test script in something like /home/u/test.sh as

  #!/bin/bash

  sleep 20
  count="$(cat /home/ubuntu/count)"
  count=$((count+1))
  echo $count | tee /home/ubuntu/count
  journalctl -b | grep -q -i wayland || sudo reboot

   * the system will probably stuck in black-screen or boot LOGO.
   * Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
   * After applying the fix, it got pass within 1000+ reboot cycles.
   * Test PPA can be found here 
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488

  [Fix]
   * The patch makes gpu-manager to probe nvidia (if needed) first and waiting 
for the /run/u-d-c-nvidia-drm-was-loaded be touched by 
71-u-d-c-gpu-detection.rules.
   * Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking 
the nvidia driver presents or not.
   * gpu-manager is before display-manager. Thus, gpu-manager will wait for 
nvidia uevent be processed and then continue to work. When gdm be launched, the 
targeted nvidia uevent has been processed already. 
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）

  [Where problems could occur]
   * there is not potential regression from my mind but it will lead the boot 
time be longer.
   * In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms. 
Worst case, over 1 s in 8xx runs (of 1000).
   * I think the stability is important than performance in this case.

  [Other Info]
   * For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm 
will meet this issue still. The other potential fix (from either gdm or logind) 
is under discussion in 
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
   * u-d-c upstream fix: 
https://github.com/tseliot/ubuntu-drivers-common/pull/67

  ---

  Test environment/steps:
  1. A desktop or workstation which containing an iGPU.
  2. Plug a nvidia graphic card to the system and installing proprietary nvidia 
driver (470 in my case)
  3. Attach a monitor to dGPU and leave iGPU connect to nothing.
  (in my test environment, there is the other ethernet card and TBT4 cards)
  4. Reboot system.

  Based on:
  $ cat /lib/udev/rules.d/61-gdm.rules
  # disable Wayland on Hi1710 chipsets
  ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711", 
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
  # disable Wayland when using the proprietary nvidia driver
  DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

  It will disable wayland by default if proprietary nvidia driver load.
  But in some race condition cases, the nvidia probe is later than gnome 
launches. (The fail rate is 6/24.)
  Thus, ubuntu-gdm has a fix for Bug#1794280 to add 
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".

  The gdm-wait-for-drm is intend to make sure all drm udev devices
  enumerated before launching gdm.

  It rely on at least one "master-of-seat" graphic card for gdm but it's not 
rigorous enough.
  Since most of graphic cards are own "master-of-seat"[1].

  In my case, it detects the iGPU is probed but dGPU.
  However, the display is attached to dGPU.

  We need to make sure the targeted gpu (connecting to monitor) is probe
  before launching gdm.

  debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
  upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/763

  [1]

[Desktop-packages] [Bug 1973604] [NEW] [nvidia340] display hangs 10s on boot with nvidia-340

2022-05-16 Thread ysfr

Public bug reported:

Since ubuntu-drivers-common 1:0.9.0~0.20.04.6,
system running kernel 5.4 & nvidia-340 will experience
10s useless delay on boot because 
gpu-manager is waiting for nvidia-drm to load
& nvidia-drm is not built in with nvidia-340.

Several legacy nvidia cards are stuck to nvidia-340 & Kernel 5.4 as detailled 
in:
https://nvidia.custhelp.com/app/answers/detail/a_id/3142/%7E/support-timeframes-for-unix-legacy-gpu-releases

See prior investigation in comments of
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488

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

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

Title:
  [nvidia340] display hangs 10s on boot with nvidia-340

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Since ubuntu-drivers-common 1:0.9.0~0.20.04.6,
  system running kernel 5.4 & nvidia-340 will experience
  10s useless delay on boot because 
  gpu-manager is waiting for nvidia-drm to load
  & nvidia-drm is not built in with nvidia-340.

  Several legacy nvidia cards are stuck to nvidia-340 & Kernel 5.4 as detailled 
in:
  
https://nvidia.custhelp.com/app/answers/detail/a_id/3142/%7E/support-timeframes-for-unix-legacy-gpu-releases

  See prior investigation in comments of
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1973604/+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 1968911] Re: assertion failures in cr_parser_new_from_buf and cr_declaration_parse_list_from_buf

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

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

Title:
  assertion failures in cr_parser_new_from_buf and
  cr_declaration_parse_list_from_buf

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  gnome-shell is emitting a lot of warnings to the systemd journal

  Test Case
  -
  Install the update
  Restart your computer
  Log in.
  Run this command in a terminal. It should not return any thing.

  journalctl -b | grep cr_

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

  Original Bug Report
  ---

  Hi,

  I see the following assertion failures in the system logs:

  # journalctl | grep cr_
  Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Apr 13 18:22:56 vougeot gnome-shell[3472]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Apr 13 18:22:56 vougeot gnome-shell[3472]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Apr 13 18:22:56 vougeot gnome-shell[3472]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  Uname: Linux 5.17.2-051702-generic x86_64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Apr 13 20:04:54 2022
  DisplayManager: gdm3
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

Title:
  Update gnome-shell to 42.1

Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Jammy:
  In Progress

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

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.1/NEWS

  Test Case 1
  -
  sudo apt install gnome-session gnome-shell-extensions
  Install the update.
  Log out.
  Select your name on the login screen.
  Click the gear button to choose a session to log in to.
  Finish logging in.

  Verify that things continue to work well for all these sessions:
  GNOME
  GNOME Classic
  Ubuntu
  Ubuntu on Xorg

  
  Test Case 2
  ---
  Because a GNOME Shell update years ago broke some GNOME Shell extensions, 
it's also requested that we do a basic test of all the extensions included in 
the Ubuntu repositories.

  https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from-
  universe-and-stop-auto-syncs/18437/9

  Install all the extensions.
  Log out and then log back in.
  Use one of the Extensions apps to enable all the extensions.
  Verify that they can all be enabled without showing an error.

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

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

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


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

[Desktop-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04

Thank you for your bug report. Could you edit
/lib/systemd/system/wpa_supplicant.service to add a '-d' to the
ExecStart cmd, restart, try to connect and share the 'journalctl -b 0'
log from the system?

It would also be worth trying if
https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 makes a
difference for you, could be the same issue with legacy server

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

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

Title:
  wifi connection on hotspot with wpa enterprise on 22.04

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

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

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

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

Bug description:
  * Impact

  Connecting to some PEAP wifi doesn't work anymore since the openssl3
  transition

  Details on the issue can be found on
  http://lists.infradead.org/pipermail/hostap/2022-May/040511.html

  * Test case

  Try using a PEAP wifi not implementing RFC5746, it should be able to
  connect

  * Regression potential

  The change allows to connect to less secure WiFis the same way that
  wpa allowed before openssl3, lower security enforcement isn't ideal
  but still better than non working hardware.

  

  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.release-upgrades:
  2022-02-27T21:07:16.553410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [snap] apparmor denials on /etc/chromium-browser/policies/

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  [1565519.440403] audit: type=1400 audit(1504185084.568:68574811):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/managed/" pid=19433
  comm="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  [1565519.440527] audit: type=1400 audit(1504185084.568:68574812):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/recommended/" pid=19433
  comm="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  Those denials don't appear to prevent the app from running. Still,
  they should be investigated and fixed if possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+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 1897454] Re: [snap] Chromium has Wayland support disabled

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [snap] Chromium has Wayland support disabled

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Since v87 Chromium ships with support for Ozone/Wayland:
  https://www.phoronix.com/scan.php?page=news_item=Chrome-87-Ozone-Try-Again.

  This build flag is not disabled in dev (edge) channel build, so it should be 
possible to run Chromium with flags
--enable-features=UseOzonePlatform --ozone-platform=wayland.

  This does not work due to environment variable DISABLE_WAYLAND set to 1 here:
  
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=dev#n18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+subscriptions


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

[Desktop-packages] [Bug 1958019]

2022-05-16 Thread cam

Looking at the model number, there's a chance it's compatible with the 
verbs of the 15IMHG05, or another model from around that time.

Do you know how to build and run your own kernel?

Also, please provide a URL to your alsa-info.

On 5/15/2022 12:12 PM, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #599 from Andrei Miculita (andreimiculita+k...@gmail.com) ---
> Lenovo Legion S7 15IMH5
>
> Has anyone managed to get their sound working on it? Would appreciate a
> tutorial or some tips (the more specific, the better, as this thread is full
> of
> other devices as well and it'd take a long time to try everything)
>

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Desktop-packages] [Bug 1958019]

2022-05-16 Thread andreimiculita+kern

Lenovo Legion S7 15IMH5

Has anyone managed to get their sound working on it? Would appreciate a
tutorial or some tips (the more specific, the better, as this thread is
full of other devices as well and it'd take a long time to try
everything)

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

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

2022-05-16 Thread Alex Murray

I am not sure I agree with the statement that this is "harmless" for the
user service to be running if remote desktop sharing is not enabled - on
my jammy system I can see the RDP port open thanks to gnome-remote-
desktop:

$ ss -tlp | grep gnome-remote
LISTEN 0 10*:ms-wbt-server*:*
users:(("gnome-remote-de",pid=5851,fd=13))

And I have not manually enabled this - so I feel like this is
potentially a security issue and should be prioritised as such for
jammy.

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

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

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

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

This was a contributing factor for LP: #1971415

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

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

It should show the service as "Active: inactive"

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

More details
---
This fix uses a dpkg maintscript to remove
/etc/systemd/user/gnome-session.target.wants/gnome-remote-desktop.service .
(That file is a symlink to the actual service).

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

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

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

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

[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-05-16 Thread Douglas E Engert

Initial problem of:

Initial problem of "[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"

can be solved by adding to  
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox something like:
-- DEE.snap.firefox.firefox 2022-05-15 00:51:38.010651530 -0500
+++ snap.firefox.firefox2022-05-15 21:18:39.445523027 -0500
@@ -312,6 +312,9 @@
   /tmp/   r,
   /tmp/** mrwlkix,
 
+  #DEE
+  /run/user/[0-9]*/** mrwlkix,
+
   # App-specific access to files and directories in /dev/shm. We allow file
   # access in /dev/shm for shm_open() and files in subdirectories for open()
   # bind mount *not* used here (see 'parallel installs', above)

This adds the "m" mask to the  "/run/user/1000/doc/e0bac853/" directory
but does allow the module to be loaded. This is overkill, for the
directory. For a PKCS11 module "mr" maybe all that is needed.

It is not clear why the choice was made to copy the pkcs11 modules to the doc 
directory in the first place.
Ubuntu appears to install PKCS11 modules (at least some in) in  
/usr/lib/x86_64-linux-gnu/pkcs11 so why can't this be used without copying?

The above only show how to get around the first of many possible
problems.

Not all Ubuntu installed PKCS11 modules are installed in the above
directory. p11-kit-client.so is but opensc-pkcs11.so and onepin-opensc-
pkcs11.so are not, just symlinks.

Trying to use the apparmor aa-complain to get more info does not work
with the way the snap apparmor profiles are named. It appears the
profile uses "." inplace of "/" and there is no "snap/firefox/firefox"


Pkcs11 modules may load other PKCS11 modules, i.e. that is what p11-kit does. 
Each of these modules may have config files with system and user versions. 
apparmor needs to address how these config files can be read.

 
Until it can be shown that PKCS11 modules can be easily be used, I would 
suggest that firefox not be installed by snap. 

Also see:
https://github.com/OpenSC/OpenSC/issues/2552






** Bug watch added: OpenSC Issues #2552
   https://github.com/OpenSC/OpenSC/issues/2552

-- 
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 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/ubuntu/+source/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 1973474] Re: Rename "Pin to Dash" to "Pin to Dock"

The reason why I bring up this early is that we are about to document
Ubuntu differences in the desktop guide. So for both docs and
translation reasons: Let's do this soon, and avoid some last minute UIF
break.

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Rename "Pin to Dash" to "Pin to Dock"

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  I noticed this commit:

  https://github.com/micheleg/dash-to-dock/commit/8ee55c29

  If I understand it correctly, it means that we will use the label "Pin
  to Dash" instead of "Add to Favorites" as from Ubuntu 22.10. To be
  consistent I suggest that we rename the thing in all contexts, and
  hence replace "Dock" with "Dash" in all affected strings in the
  Appearance section in g-c-c.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1973474/+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 1973474] Re: Rename "Dock" to "Dash" in Appearance

Hmm.. Using "Pin to Dock" (via a gnome-shell patch I suppose) may be
better. Doing so probably lets us keep the established "Dock" and still
be consistent.

Changing this bug accordingly.

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

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

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

** Summary changed:

- Rename "Dock" to "Dash" in Appearance
+ Rename "Pin to Dash" to "Pin to Dock"

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

Title:
  Rename "Pin to Dash" to "Pin to Dock"

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  I noticed this commit:

  https://github.com/micheleg/dash-to-dock/commit/8ee55c29

  If I understand it correctly, it means that we will use the label "Pin
  to Dash" instead of "Add to Favorites" as from Ubuntu 22.10. To be
  consistent I suggest that we rename the thing in all contexts, and
  hence replace "Dock" with "Dash" in all affected strings in the
  Appearance section in g-c-c.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1973474/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2022-05-16 Thread Martin Schmitt

We're seeing this same issue. The postinst script in the 22.04 package
seems to be missing a few lines that were still there in 21.10, one of
which would be the one that executes systemctl enable pcscd.socket.

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

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

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Confirmed

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1973596] [NEW] SRU 1.14.3-0ubuntu3 to jammy

Public bug reported:

[Impact]

When testing native messaging support with the firefox snap (not yet
released, see https://github.com/flatpak/xdg-desktop-portal/pull/705),
gnome-shell won't prompt the user for permission to authorize a given
extension to access the portal, because the app id being passed to the
authorization request isn't what gnome-shell expects. This is
https://github.com/flatpak/xdg-desktop-portal/issues/769.

As a consequence, access is always denied, and native messaging just
doesn't work.

The patch that fixes this issue was discussed with the author of the
native messaging portal (James Henstridge) and approved by him, and is
now being cherry-picked here.


[Test Plan]

On jammy, fetch and install the latest test snap from 
https://launchpad.net/~osomon/+snap/firefox-native-messaging (manual 
installation requires the --dangerous flag).
Install the chrome-gnome-shell native connector (`sudo apt install 
chrome-gnome-shell`).
Open firefox and browse to 
https://addons.mozilla.org/firefox/addon/gnome-shell-integration/.
Click the "Add to Firefox" button on the page.
Accept the authorization request that appears as a popup to install the GNOME 
Shell integration extension.
Browse to https://extensions.gnome.org/local/.

You should be getting a GNOME Shell modal dialog that prompts you whether to 
allow Firefox to make use of the WebExtensions portal to launch the 
org.gnome.chrome_gnome_shell native connector.
Without this patch, GNOME Shell silently rejects the authorization request, and 
you won't see any prompt.

Note that if you've tested the functionality before installing the
patched version of xdg-desktop-portal, you'll need to delete the
database that stores the permissions on disk
(~/.local/share/flatpak/db/webextensions) and restart the portal.


[Where problems could occur]

This patch affects a portal that is not being used anywhere yet (the
implementation in the Firefox snap is work in progress and serves as a
proof of concept). So there is no risk of affecting existing
functionality or other portals.

At worst, the patch doesn't fix the issue it claims it resolves.

** Affects: xdg-desktop-portal (Ubuntu)
 Importance: Medium
 Assignee: Olivier Tilloy (osomon)
 Status: Fix Released

** Affects: xdg-desktop-portal (Ubuntu Jammy)
 Importance: Medium
 Assignee: Olivier Tilloy (osomon)
 Status: In Progress

** Changed in: xdg-desktop-portal (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: xdg-desktop-portal (Ubuntu)
   Importance: Undecided => Medium

** Changed in: xdg-desktop-portal (Ubuntu)
   Status: New => Fix Released

** Also affects: xdg-desktop-portal (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: xdg-desktop-portal (Ubuntu Jammy)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: xdg-desktop-portal (Ubuntu Jammy)
   Importance: Undecided => Medium

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

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

Title:
  SRU 1.14.3-0ubuntu3 to jammy

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Jammy:
  In Progress

Bug description:
  [Impact]

  When testing native messaging support with the firefox snap (not yet
  released, see https://github.com/flatpak/xdg-desktop-portal/pull/705),
  gnome-shell won't prompt the user for permission to authorize a given
  extension to access the portal, because the app id being passed to the
  authorization request isn't what gnome-shell expects. This is
  https://github.com/flatpak/xdg-desktop-portal/issues/769.

  As a consequence, access is always denied, and native messaging just
  doesn't work.

  The patch that fixes this issue was discussed with the author of the
  native messaging portal (James Henstridge) and approved by him, and is
  now being cherry-picked here.

  
  [Test Plan]

  On jammy, fetch and install the latest test snap from 
https://launchpad.net/~osomon/+snap/firefox-native-messaging (manual 
installation requires the --dangerous flag).
  Install the chrome-gnome-shell native connector (`sudo apt install 
chrome-gnome-shell`).
  Open firefox and browse to 
https://addons.mozilla.org/firefox/addon/gnome-shell-integration/.
  Click the "Add to Firefox" button on the page.
  Accept the authorization request that appears as a popup to install the GNOME 
Shell integration extension.
  Browse to https://extensions.gnome.org/local/.

  You should be getting a GNOME Shell modal dialog that prompts you whether to 
allow Firefox to make use of the WebExtensions portal to launch the 
org.gnome.chrome_gnome_shell native connector.
  Without this patch, GNOME Shell silently rejects the authorization request, 
and you won't see any prompt.

  Note

[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts

This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4

---
linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium

  * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584)

  * Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md

  * alsa: enable the cirrus-logic side-codec to make the speaker output sound
(LP: #1965496)
- spi: Make spi_alloc_device and spi_add_device public again
- spi: Create helper API to lookup ACPI info for spi device
- spi: Support selection of the index of the ACPI Spi Resource before alloc
- spi: Add API to count spi acpi resources
- platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver
  name
- platform/x86: serial-multi-instantiate: Reorganize I2C functions
- platform/x86: serial-multi-instantiate: Add SPI support
- ACPI / scan: Create platform device for CS35L41
- [Config]: enable SERIAL_MULTI_INSTANTIATE

  * Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry DROM reads for more failure scenarios
- thunderbolt: Do not resume routers if UID is not set
- thunderbolt: Do not make DROM read success compulsory
- PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3

  * DMCUB hangs if a PSR unsupported set version command is sent on AMD
Rembrandt platform (LP: #1969407)
- drm/amd/display: Only set PSR version when valid

  * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892)
- ALSA: hda/realtek: Add support for HP Laptops
- ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9

  * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain
- SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD
- SAUCE: vmd: fixup bridge ASPM by driver name instead

  * Support AMD P-State cpufreq control mechanism (LP: #1956509)
- [Config] enable X86_AMD_PSTATE as built-in on amd64

  * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016)
- [Debian] Use kernel-testing repo from launchpad

  * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771)
- SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout

  * alsa/sdw: Fix the audio issue on a Dell machine without internal mic
(LP: #1966841)
- ASoC: Intel: soc-acpi: add entries in ADL match table

  * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices

  * Miscellaneous Ubuntu changes
- [Config] update configs and annotations after stable updates

  [ Ubuntu: 5.17.0-8.8~22.04.2 ]

  * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219)
  * Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update update.conf

  [ Ubuntu: 5.17.0-8.8~22.04.1 ]

  * Empty entry

  [ Ubuntu: 5.17.0-8.8 ]

  * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016)
  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/master)

  [ Ubuntu: 5.17.0-7.7 ]

  * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988)
  * zfcpdump-kernel update to v5.15 (LP: #1965766)
- SAUCE: Audit: Fix incorrect static inline function declration.
  * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16
(LP: #1958004)
- SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs
  * Jammy update: v5.17.3 upstream stable release (LP: #1968986)
- lib/logic_iomem: correct fallback config references
- um: fix and optimize xor select template for CONFIG64 and timetravel mode
- rtc: wm8350: Handle error for wm8350_register_irq
- net: dsa: felix: fix possible NULL pointer dereference
- mm: kfence: fix objcgs vector allocation
- KVM: x86/pmu: Use different raw event masks for AMD and Intel
- KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode()
- KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs
- KVM: x86/pmu: Fix and isolate TSX-specific performance event logic
- KVM: x86/emulator: Emulate RDPID only if it is enabled in guest
- drm: Add orientation quirk for GPD Win Max
- Bluetooth: hci_sync: Fix compilation warning
- ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111
- Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt
- drm/amd/display: Add signal type check when verify stream backends same
- drm/amdkfd: enable heavy-weight TLB flush on Arcturus
- drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800.
- drm/edid: improve non-desktop quirk logging
- Bluetooth: hci_event: Ignore multiple conn complete events
- drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj
- drm/amd/display: Fix memory leak
- drm/amd/display: Use PSR version selected during set_psr_caps
- usb: gadget:

[Desktop-packages] [Bug 1973594] Re: [BPO] libreoffice 7.2.7 for focal

2022-05-16 Thread Rico Tzschichholz

** Also affects: libreoffice (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: libreoffice (Ubuntu Focal)
   Status: New => In Progress

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

** Changed in: libreoffice (Ubuntu Focal)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

** Description changed:

  [Impact]
  
-  * LibreOffice 7.2.6 is in its seventh (and last) bugfix release of the 7.2 
line:
-  https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.7_release
+  * LibreOffice 7.2.7 is in its seventh (and last) bugfix release of the 7.2 
line:
+  https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.7_release
  
-  * This source packages matches the proposed SRU for impish handled at
-  https://bugs.launchpad.net/ubuntu/impish/+source/libreoffice/+bug/1972155
-and its backport is currently provided by the LibreOffice Still PPA at
-  
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages
+  * This source packages matches the proposed SRU for impish handled at
+  https://bugs.launchpad.net/ubuntu/impish/+source/libreoffice/+bug/1972155
+    and its backport is currently provided by the LibreOffice Still PPA at
+  
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages
  
-  * Previous backport of 7.2.6 handled at
-  https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969808
+  * Previous backport of 7.2.6 handled at
+  https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969808
  
-  * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released
+  * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released
  in focal.
  
-  * Given the nature of the project, the complexity of the codebase and
+  * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU a
  minor release rather than cherry-pick selected bug fixes.
  
  [Scope]
  
-  * Backport of
+  * Backport of
  https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.7-0ubuntu0.21.10.1
  
-  * Backport target is Focal/20.04 LTS only to provide an official build
+  * Backport target is Focal/20.04 LTS only to provide an official build
  of a more recent upstream version of LibreOffice
  
  [Testing]
  
-  * Upstream testing. Bugs fixed upstream typically include
+  * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).
  
-   * A recent set of upstream's automated jenkins testing can be found here:
- https://ci.libreoffice.org/job/gerrit_72/1617/
+   * A recent set of upstream's automated jenkins testing can be found here:
+ https://ci.libreoffice.org/job/gerrit_72/1617/
  
-   * More information about the upstream QA testing can be found here:
- * Automated tests
-   https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
- * Automated UI tests
-   https://wiki.documentfoundation.org/Development/UITests
- * Regression tests
-   https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
- * Feature tests
-   https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
+   * More information about the upstream QA testing can be found here:
+ * Automated tests
+   https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
+ * Automated UI tests
+   https://wiki.documentfoundation.org/Development/UITests
+ * Regression tests
+   https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
+ * Feature tests
+   https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
  
-  * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
- * [amd64] ...
- * [arm64] ...
- * [armhf] ...
- * [ppc64el] ...
- * [s390x] ...
+  * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
+ * [amd64] ...
+ * [arm64] ...
+ * [armhf] ...
+ * [ppc64el] ...
+ * [s390x] ...
  
-  * General smoke testing of all the applications in the office suite
+  * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented by:
  https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice
  
  [Regression Potential]
  
-  * A minor release with a total of 44+ bug fixes always carries the
+  * A minor release with a total of 44+ bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.
  
-  * A combination of autopkgtests and careful smoke testing as described
+  * A combination of autopkgtests and careful smoke testing as described
  above should provide reasonable

[Desktop-packages] [Bug 1944113]

2022-05-16 Thread Michael Weghorn

*** Bug 148765 has been marked as a duplicate of this bug. ***

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

Title:
  Many UI elements (list box, drop down) don't work at all in kf5
  environment

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Many UI elements (list box, drop down) don't work at all in kf5 environment. 
This makes LO unusable.
  For example, try to insert a table from standard toolbar in LO Writer – 
nothing inserted.
  Same happens with other drop down elements (styles, font family, font size, 
font color, font highlight, etc).

  Bug reports at LO's bug tracker:
  https://bugs.documentfoundation.org/show_bug.cgi?id=144037
  https://bugs.documentfoundation.org/show_bug.cgi?id=144562
  https://gerrit.libreoffice.org/c/core/+/122116

  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.5
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.11.0-34-generic
  OS Type: 64-bit
  Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz
  Memory: 7,7 GiB

  Version: 7.2.1.2 / LibreOffice Community
  Build ID: 20(Build:2)
  CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb)
  Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU
  Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3
  Calc: threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+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 1973594] [NEW] [BPO] libreoffice 7.2.7 for focal

2022-05-16 Thread Rico Tzschichholz

Public bug reported:

[Impact]

 * LibreOffice 7.2.6 is in its seventh (and last) bugfix release of the 7.2 
line:
 https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.7_release

 * This source packages matches the proposed SRU for impish handled at
 https://bugs.launchpad.net/ubuntu/impish/+source/libreoffice/+bug/1972155
   and its backport is currently provided by the LibreOffice Still PPA at
 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages

 * Previous backport of 7.2.6 handled at
 https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969808

 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released
in focal.

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

[Scope]

 * Backport of
https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.7-0ubuntu0.21.10.1

 * Backport target is Focal/20.04 LTS only to provide an official build
of a more recent upstream version of LibreOffice

[Testing]

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

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

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

 * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
* [amd64] ...
* [arm64] ...
* [armhf] ...
* [ppc64el] ...
* [s390x] ...

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

[Regression Potential]

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

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

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

** Affects: libreoffice (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

Title:
   [BPO] libreoffice 7.2.7 for focal

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice source package in Focal:
  New

Bug description:
  [Impact]

   * LibreOffice 7.2.6 is in its seventh (and last) bugfix release of the 7.2 
line:
   https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.7_release

   * This source packages matches the proposed SRU for impish handled at
   https://bugs.launchpad.net/ubuntu/impish/+source/libreoffice/+bug/1972155
 and its backport is currently provided by the LibreOffice Still PPA at
   
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages

   * Previous backport of 7.2.6 handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969808

   * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently
  released in focal.

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

  [Scope]

   * Backport of
  https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.7-0ubuntu0.21.10.1

   * Backport target is Focal/20.04 LTS only to provide an official
  build of a more recent upstream version of LibreOffice

  [Testing]

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

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

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

[Desktop-packages] [Bug 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

2022-05-16 Thread hidaris

This looks like a related question https://github.com/micheleg/dash-to-
dock/issues/1705

** Bug watch added: github.com/micheleg/dash-to-dock/issues #1705
   https://github.com/micheleg/dash-to-dock/issues/1705

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+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 1971001] Re: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and Jammy

2022-05-16 Thread David Fernandez Gonzalez

Packages patched for CVE-2020-35522, CVE-2022-0561, CVE-2022-0562,
CVE-2022-0865 and CVE-2022-0891 are now released and available.
(https://ubuntu.com/security/notices/USN-5421-1).

Jammy is currently at version 4.3.0-6 which includes the patch for
CVE-2022-0865 as it was introduced in 4.3.0-5.

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

Title:
  Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and
  Jammy

Status in tiff package in Ubuntu:
  In Progress

Bug description:
  The versions in Trusty, Xenial, Bionic, Focal and Impish may be
  vulnerable to all CVEs below.

  The version in Jammy is vulnerable to CVE-2022-0865.

  Debian released an advisory on March 24.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1971001/+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 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock