[Desktop-packages] [Bug 1987524] Re: plasma-discover fails to build from source with snapd-glib 1.62

2022-08-24 Thread Jeremy Bicha
** Changed in: snapd-glib (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  plasma-discover fails to build from source with snapd-glib 1.62

Status in snapd-glib:
  Unknown
Status in plasma-discover package in Ubuntu:
  Invalid
Status in snapd-glib package in Ubuntu:
  Fix Released

Bug description:
  We will be pushing snapd-glib 1.62 to Kinetic very soon as part of a
  large GNOME 43 transition.

  The new packaging switches to libsoup3. Out of an abundance of
  caution, the headers are installed to a new location and the soname
  was bumped.

  I tried building plasma-discover with the new version and it fails to
  build. Could you look into this issue? I'm not familiar with the Qt
  libraries.

  It does look like it builds successfully on current Kinetic so the
  problem was triggered by the library change.

  You can find the snapd-glib packages at
  https://launchpad.net/~jbicha/+archive/ubuntu/gnome43-staging-2/

  If you find a bug in snapd-glib itself, please report it at
  https://github.com/snapcore/snapd-glib/issues

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


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


[Desktop-packages] [Bug 1920643] Re: Notification popup before login -> app started w/o login

2022-08-24 Thread Daniel van Vugt
The only relevant upstream bug I can find is:

  https://gitlab.gnome.org/GNOME/gdm/-/issues/685

so maybe use that or open a new one to discuss the security
implications:

  https://gitlab.gnome.org/GNOME/gdm/-/issues

** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #685
   https://gitlab.gnome.org/GNOME/gdm/-/issues/685

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

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

Title:
  Notification popup before login -> app started w/o login

Status in gdm:
  Unknown
Status in gdm3 package in Ubuntu:
  Confirmed

Bug description:
  == General pattern ==

  In gdm login screen, while no one is logged in, notification popups
  are shown. An unauthenticated person at the keyboard can interact with
  these popups to start applications.

  == Concrete Example ==

  I've got a separate storage disk that is nearly full (just /storage
  with photos etc., / is on another device and has plenty of space). I
  get a notification popup 'Disk space is low on /storage.' with options
  to either 'ignore' or to 'examine' it (it's silly to notify me about
  shortage on this disk, but that's another topic). When I click
  'examine' baobab is started as user gdm, as I can see in 'ps' on a
  console terminal'. It's not visible on screen, it's supposedly
  somewhere 'behind' the gdm screen.

  == Expected behaviour ==

  As long nobody is logged in, gdm doesn't start any applications.

  I don't see much use for popups before login at all (imagine a popup
  'New file
  Surprise_birthday_party_for_your_spouse_in_Wonderland_park.odt has
  been successfully synchronised'), but at least it should not be
  possible to start processes from these.

  == Security implications ==

  Even though the application is not visible in this case, the behaviour
  does not provide any use to the user. Contrarily, a popup targeting
  logged in users could unintentionally compromise security. Imagine
  e.g. a case where a popup allows the not-logged-in person in front of
  the machine to specify actions beyond starting a specific application
  (something like 'Problem with flux capacitor detected. Click here to
  run flux-fix, or here, to specify a custom command in popup input
  field').

  This is just a light hint that there *might* be a security issue.
  There might be countermeasures (namely popups' general abilities) to
  prevent such a scenario. Please feel free to re-classify accordingly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.36.3-0ubuntu0.20.04.3
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sat Mar 20 22:57:15 2021
  InstallationDate: Installed on 2020-04-24 (329 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1987582] Re: package libgles2 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] failed to install/upgrade: unable to make backup link of './usr/l

2022-08-24 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libgles2 1.3.2-1~ubuntu0.20.04.2 [modified:
  usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] failed to
  install/upgrade: unable to make backup link of
  './usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0' before installing new
  version: Invalid cross-device link

Status in libglvnd package in Ubuntu:
  New

Bug description:
  Reported while upgrading from 20.04 to 22.04.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libgles2 1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0]
  Uname: Linux 4.19.219-odroid-arm64 aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Wed Aug 24 21:41:07 2022
  DistUpgraded: 2022-08-24 22:10:29,326 WARNING no activity on terminal for 300 
seconds (Installed libreoffice-script-provider-python (arm64))
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed
   rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed
  DuplicateSignature:
   package:libgles2:1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0]
   Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) 
...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack):
unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' 
before installing new version: Invalid cross-device link
  ErrorMessage: unable to make backup link of 
'./usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0' before installing new version: 
Invalid cross-device link
  GraphicsCard:
   
  Lspci-vt:
   -+-[0002:20]---00.0-[21]00.0  Sandisk Corp WD Blue SN570 NVMe SSD
\-[:00]-
  ProcKernelCmdLine: storagemedia=mtd androidboot.storagemedia=mtd 
androidboot.mode=normal  root=UUID=ea5041c4-93df-4890-895c-cc4f02c13672 quiet 
splash plymouth.ignore-serial-consoles earlycon=uart8250,mmio32,0xfe66 
pci=nomsi fsck.mode=force fsck.repair=yes 
mtdparts=sfc_nor:0x2@0xe(env),0x20@0x10(uboot),0x10@0x30(splash),0xc0@0x40(firmware)
 console=tty1
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: libglvnd
  Title: package libgles2 1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] failed to install/upgrade: unable 
to make backup link of './usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0' before 
installing new version: Invalid cross-device link
  UpgradeStatus: Upgraded to jammy on 2022-08-25 (0 days ago)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 1987583] Re: package libgbm1 21.2.6-0ubuntu0.1~20.04.2 [modified: usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0] failed to install/upgrade: unable to make backup link of './usr/lib

2022-08-24 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libgbm1 21.2.6-0ubuntu0.1~20.04.2 [modified:
  usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0] failed to install/upgrade:
  unable to make backup link of './usr/lib/aarch64-linux-
  gnu/libgbm.so.1.0.0' before installing new version: Invalid cross-
  device link

Status in mesa package in Ubuntu:
  New

Bug description:
  Reported while upgrading 20.04 to 22.04

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libgbm1 22.0.5-0ubuntu0.1
  Uname: Linux 4.19.219-odroid-arm64 aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Wed Aug 24 21:40:57 2022
  DistUpgraded: 2022-08-24 22:04:11,462 DEBUG got a conffile-prompt from dpkg 
for file: '/etc/pulse/default.pa'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed
   rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed
  DuplicateSignature:
   package:libgbm1:21.2.6-0ubuntu0.1~20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0]
   Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) 
...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack):
unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' 
before installing new version: Invalid cross-device link
  ErrorMessage: unable to make backup link of 
'./usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before installing new version: 
Invalid cross-device link
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   
  Lspci-vt:
   -+-[0002:20]---00.0-[21]00.0  Sandisk Corp WD Blue SN570 NVMe SSD
\-[:00]-
  ProcKernelCmdLine: storagemedia=mtd androidboot.storagemedia=mtd 
androidboot.mode=normal  root=UUID=ea5041c4-93df-4890-895c-cc4f02c13672 quiet 
splash plymouth.ignore-serial-consoles earlycon=uart8250,mmio32,0xfe66 
pci=nomsi fsck.mode=force fsck.repair=yes 
mtdparts=sfc_nor:0x2@0xe(env),0x20@0x10(uboot),0x10@0x30(splash),0xc0@0x40(firmware)
 console=tty1
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: mesa
  Title: package libgbm1 21.2.6-0ubuntu0.1~20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0] failed to install/upgrade: unable to 
make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before 
installing new version: Invalid cross-device link
  UpgradeStatus: Upgraded to jammy on 2022-08-25 (0 days ago)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 1987583] [NEW] package libgbm1 21.2.6-0ubuntu0.1~20.04.2 [modified: usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0] failed to install/upgrade: unable to make backup link of './usr/l

2022-08-24 Thread Darrin W. Root
Public bug reported:

Reported while upgrading 20.04 to 22.04

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libgbm1 22.0.5-0ubuntu0.1
Uname: Linux 4.19.219-odroid-arm64 aarch64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: arm64
CasperMD5CheckResult: unknown
CompositorRunning: None
Date: Wed Aug 24 21:40:57 2022
DistUpgraded: 2022-08-24 22:04:11,462 DEBUG got a conffile-prompt from dpkg for 
file: '/etc/pulse/default.pa'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed
 rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed
DuplicateSignature:
 package:libgbm1:21.2.6-0ubuntu0.1~20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0]
 Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) 
...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack):
  unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' 
before installing new version: Invalid cross-device link
ErrorMessage: unable to make backup link of 
'./usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before installing new version: 
Invalid cross-device link
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 
Lspci-vt:
 -+-[0002:20]---00.0-[21]00.0  Sandisk Corp WD Blue SN570 NVMe SSD
  \-[:00]-
ProcKernelCmdLine: storagemedia=mtd androidboot.storagemedia=mtd 
androidboot.mode=normal  root=UUID=ea5041c4-93df-4890-895c-cc4f02c13672 quiet 
splash plymouth.ignore-serial-consoles earlycon=uart8250,mmio32,0xfe66 
pci=nomsi fsck.mode=force fsck.repair=yes 
mtdparts=sfc_nor:0x2@0xe(env),0x20@0x10(uboot),0x10@0x30(splash),0xc0@0x40(firmware)
 console=tty1
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
SourcePackage: mesa
Title: package libgbm1 21.2.6-0ubuntu0.1~20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0] failed to install/upgrade: unable to 
make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before 
installing new version: Invalid cross-device link
UpgradeStatus: Upgraded to jammy on 2022-08-25 (0 days ago)
acpidump:
 
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: apport-package arm64 jammy ubuntu

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

Title:
  package libgbm1 21.2.6-0ubuntu0.1~20.04.2 [modified:
  usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0] failed to install/upgrade:
  unable to make backup link of './usr/lib/aarch64-linux-
  gnu/libgbm.so.1.0.0' before installing new version: Invalid cross-
  device link

Status in mesa package in Ubuntu:
  New

Bug description:
  Reported while upgrading 20.04 to 22.04

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libgbm1 22.0.5-0ubuntu0.1
  Uname: Linux 4.19.219-odroid-arm64 aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Wed Aug 24 21:40:57 2022
  DistUpgraded: 2022-08-24 22:04:11,462 DEBUG got a conffile-prompt from dpkg 
for file: '/etc/pulse/default.pa'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed
   rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed
  DuplicateSignature:
   package:libgbm1:21.2.6-0ubuntu0.1~20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0]
   Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) 
...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack):
unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' 
before installing new version: Invalid cross-device link
  ErrorMessage: unable to make backup link of 
'./usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before installing new version: 
Invalid cross-device link
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   
  Lspci-vt:
   -+-[0002:20]---00.0-[21]00.0  Sandisk Corp WD Blue SN570 NVMe SSD
\-[:00]-
  ProcKernelCmdLine: storagemedia=mtd androidboot.storagemedia=mtd 
androidboot.mode=normal  

[Desktop-packages] [Bug 1987582] [NEW] package libgles2 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] failed to install/upgrade: unable to make backup link of './usr

2022-08-24 Thread Darrin W. Root
Public bug reported:

Reported while upgrading from 20.04 to 22.04.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libgles2 1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0]
Uname: Linux 4.19.219-odroid-arm64 aarch64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: arm64
CasperMD5CheckResult: unknown
CompositorRunning: None
Date: Wed Aug 24 21:41:07 2022
DistUpgraded: 2022-08-24 22:10:29,326 WARNING no activity on terminal for 300 
seconds (Installed libreoffice-script-provider-python (arm64))
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed
 rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed
DuplicateSignature:
 package:libgles2:1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0]
 Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) 
...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack):
  unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' 
before installing new version: Invalid cross-device link
ErrorMessage: unable to make backup link of 
'./usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0' before installing new version: 
Invalid cross-device link
GraphicsCard:
 
Lspci-vt:
 -+-[0002:20]---00.0-[21]00.0  Sandisk Corp WD Blue SN570 NVMe SSD
  \-[:00]-
ProcKernelCmdLine: storagemedia=mtd androidboot.storagemedia=mtd 
androidboot.mode=normal  root=UUID=ea5041c4-93df-4890-895c-cc4f02c13672 quiet 
splash plymouth.ignore-serial-consoles earlycon=uart8250,mmio32,0xfe66 
pci=nomsi fsck.mode=force fsck.repair=yes 
mtdparts=sfc_nor:0x2@0xe(env),0x20@0x10(uboot),0x10@0x30(splash),0xc0@0x40(firmware)
 console=tty1
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
SourcePackage: libglvnd
Title: package libgles2 1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] failed to install/upgrade: unable 
to make backup link of './usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0' before 
installing new version: Invalid cross-device link
UpgradeStatus: Upgraded to jammy on 2022-08-25 (0 days ago)
acpidump:
 
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: apport-package arm64 jammy ubuntu

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

Title:
  package libgles2 1.3.2-1~ubuntu0.20.04.2 [modified:
  usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] failed to
  install/upgrade: unable to make backup link of
  './usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0' before installing new
  version: Invalid cross-device link

Status in libglvnd package in Ubuntu:
  New

Bug description:
  Reported while upgrading from 20.04 to 22.04.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libgles2 1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0]
  Uname: Linux 4.19.219-odroid-arm64 aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Wed Aug 24 21:41:07 2022
  DistUpgraded: 2022-08-24 22:10:29,326 WARNING no activity on terminal for 300 
seconds (Installed libreoffice-script-provider-python (arm64))
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed
   rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed
  DuplicateSignature:
   package:libgles2:1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0]
   Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) 
...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack):
unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' 
before installing new version: Invalid cross-device link
  ErrorMessage: unable to make backup link of 
'./usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0' before installing new version: 
Invalid cross-device link
  GraphicsCard:
   
  Lspci-vt:
   -+-[0002:20]---00.0-[21]00.0  Sandisk Corp 

[Desktop-packages] [Bug 1987580] Re: package libegl1 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] failed to install/upgrade: unable to make backup link of './usr/lib/a

2022-08-24 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libegl1 1.3.2-1~ubuntu0.20.04.2 [modified:
  usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] failed to install/upgrade:
  unable to make backup link of './usr/lib/aarch64-linux-
  gnu/libEGL.so.1.1.0' before installing new version: Invalid cross-
  device link

Status in libglvnd package in Ubuntu:
  New

Bug description:
  Reported when upgrading from 20.04 to 22.04.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libegl1 1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0]
  Uname: Linux 4.19.219-odroid-arm64 aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Wed Aug 24 21:41:07 2022
  DistUpgraded: 2022-08-24 22:04:11,462 DEBUG got a conffile-prompt from dpkg 
for file: '/etc/pulse/default.pa'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed
   rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed
  DuplicateSignature:
   package:libegl1:1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0]
   Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) 
...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack):
unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' 
before installing new version: Invalid cross-device link
  ErrorMessage: unable to make backup link of 
'./usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0' before installing new version: 
Invalid cross-device link
  GraphicsCard:
   
  Lspci-vt:
   -+-[0002:20]---00.0-[21]00.0  Sandisk Corp WD Blue SN570 NVMe SSD
\-[:00]-
  ProcKernelCmdLine: storagemedia=mtd androidboot.storagemedia=mtd 
androidboot.mode=normal  root=UUID=ea5041c4-93df-4890-895c-cc4f02c13672 quiet 
splash plymouth.ignore-serial-consoles earlycon=uart8250,mmio32,0xfe66 
pci=nomsi fsck.mode=force fsck.repair=yes 
mtdparts=sfc_nor:0x2@0xe(env),0x20@0x10(uboot),0x10@0x30(splash),0xc0@0x40(firmware)
 console=tty1
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: libglvnd
  Title: package libegl1 1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] failed to install/upgrade: unable to 
make backup link of './usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0' before 
installing new version: Invalid cross-device link
  UpgradeStatus: Upgraded to jammy on 2022-08-25 (0 days ago)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 1987580] [NEW] package libegl1 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] failed to install/upgrade: unable to make backup link of './usr/lib

2022-08-24 Thread Darrin W. Root
Public bug reported:

Reported when upgrading from 20.04 to 22.04.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libegl1 1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0]
Uname: Linux 4.19.219-odroid-arm64 aarch64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: arm64
CasperMD5CheckResult: unknown
CompositorRunning: None
Date: Wed Aug 24 21:41:07 2022
DistUpgraded: 2022-08-24 22:04:11,462 DEBUG got a conffile-prompt from dpkg for 
file: '/etc/pulse/default.pa'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed
 rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed
DuplicateSignature:
 package:libegl1:1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0]
 Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) 
...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack):
  unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' 
before installing new version: Invalid cross-device link
ErrorMessage: unable to make backup link of 
'./usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0' before installing new version: 
Invalid cross-device link
GraphicsCard:
 
Lspci-vt:
 -+-[0002:20]---00.0-[21]00.0  Sandisk Corp WD Blue SN570 NVMe SSD
  \-[:00]-
ProcKernelCmdLine: storagemedia=mtd androidboot.storagemedia=mtd 
androidboot.mode=normal  root=UUID=ea5041c4-93df-4890-895c-cc4f02c13672 quiet 
splash plymouth.ignore-serial-consoles earlycon=uart8250,mmio32,0xfe66 
pci=nomsi fsck.mode=force fsck.repair=yes 
mtdparts=sfc_nor:0x2@0xe(env),0x20@0x10(uboot),0x10@0x30(splash),0xc0@0x40(firmware)
 console=tty1
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
SourcePackage: libglvnd
Title: package libegl1 1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] failed to install/upgrade: unable to 
make backup link of './usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0' before 
installing new version: Invalid cross-device link
UpgradeStatus: Upgraded to jammy on 2022-08-25 (0 days ago)
acpidump:
 
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: apport-package arm64 jammy ubuntu

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

Title:
  package libegl1 1.3.2-1~ubuntu0.20.04.2 [modified:
  usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] failed to install/upgrade:
  unable to make backup link of './usr/lib/aarch64-linux-
  gnu/libEGL.so.1.1.0' before installing new version: Invalid cross-
  device link

Status in libglvnd package in Ubuntu:
  New

Bug description:
  Reported when upgrading from 20.04 to 22.04.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libegl1 1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0]
  Uname: Linux 4.19.219-odroid-arm64 aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Wed Aug 24 21:41:07 2022
  DistUpgraded: 2022-08-24 22:04:11,462 DEBUG got a conffile-prompt from dpkg 
for file: '/etc/pulse/default.pa'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed
   rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed
  DuplicateSignature:
   package:libegl1:1.3.2-1~ubuntu0.20.04.2 [modified: 
usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0]
   Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) 
...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack):
unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' 
before installing new version: Invalid cross-device link
  ErrorMessage: unable to make backup link of 
'./usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0' before installing new version: 
Invalid cross-device link
  GraphicsCard:
   
  Lspci-vt:
   -+-[0002:20]---00.0-[21]00.0  Sandisk Corp WD Blue SN570 NVMe SSD
\-[:00]-
  ProcKernelCmdLine: storagemedia=mtd 

[Desktop-packages] [Bug 1987579] [NEW] "Remove Hyperlink" feature causes text duplication and corruption when removing email hyperlinks inside angle brackets

2022-08-24 Thread Aaron Rainbolt
Public bug reported:

This may be the single weirdest bug report I've ever made.

Steps to Reproduce:
1: Open LibreOffice Calc.
2: In any cell of the spreadsheet, type:

   

   The email address placed inside the angle brackets can be whatever you want, 
but the angle brackets are necessary for the bug to surface (at least usually).
3: Press Enter. The email address will automatically be turned into a hyperlink.
4: Right-click the automatically created hyperlink, and click "Remove 
Hyperlink".

Expected result:
The actual text of the cell should remain unchanged, but the hyperlink itself 
should be removed.

Actual result:
The text within the cell morphs into the following:


 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  "Remove Hyperlink" feature causes text duplication and corruption when
  removing email hyperlinks inside angle brackets

Status in libreoffice package in Ubuntu:
  New

Bug description:
  This may be the single weirdest bug report I've ever made.

  Steps to Reproduce:
  1: Open LibreOffice Calc.
  2: In any cell of the spreadsheet, type:

 

 The email address placed inside the angle brackets can be whatever you 
want, but the angle brackets are necessary for the bug to surface (at least 
usually).
  3: Press Enter. The email address will automatically be turned into a 
hyperlink.
  4: Right-click the automatically created hyperlink, and click "Remove 
Hyperlink".

  Expected result:
  The actual text of the cell should remain unchanged, but the hyperlink itself 
should be removed.

  Actual result:
  The text within the cell morphs into the following:

  
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1987572] Re: Segfault due to libpython3.10

2022-08-24 Thread Freaky Fee
** Attachment added: "valgrind log"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1987572/+attachment/5611400/+files/valgrind.log

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

Title:
  Segfault due to libpython3.10

Status in nautilus package in Ubuntu:
  New

Bug description:
  ```
  $ lsb_release -rd

  Description:  Pop!_OS 22.04 LTS
  Release:  22.04
  ```

  ```
  $ apt-cache policy nautilus

  nautilus:
Installed: 1:42.2-0ubuntu1
Candidate: 1:42.2-0ubuntu1
Version table:
   *** 1:42.2-0ubuntu1 500
  500 http://apt.pop-os.org/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:42.0-1ubuntu2 500
  500 http://apt.pop-os.org/ubuntu jammy/main amd64 Packages
  ```

  I expected Nautilus to open properly, but got a segfault instead when running:
  ```
  $ nautilus
  ```

  It seems related to LibPython (output for `journalctl -q | grep -i
  nautilus`):

  ```
  Aug 25 00:12:59 pop-os kernel: nautilus[15964]: segfault at 58 ip 
7fe281475052 sp 7ffd24384d48 error 4 in 
libpython3.10.so.1.0[7fe28145f000+22d000]
  Aug 25 00:15:23 pop-os kernel: nautilus[16160]: segfault at 10 ip 
7f90d352e68f sp 7ffdcba0d3c0 error 4 in 
libpython3.10.so.1.0[7f90d346d000+2b5000]
  Aug 25 00:17:26 pop-os kernel: nautilus[17395]: segfault at 58 ip 
7f5e34675052 sp 7fff94fc3d18 error 4 in 
libpython3.10.so.1.0[7f5e3465f000+22d000]
  Aug 25 00:26:32 pop-os sudo[22071]:  fee : TTY=pts/1 ; PWD=/home/fee ; 
USER=root ; COMMAND=/usr/bin/apt install --reinstall nautilus
  Aug 25 00:26:35 pop-os tracker-extract[22122]: Could not get mimetype, Error 
when getting information for file 
“/usr/share/applications/nautilus-autorun-software.desktop.dpkg-new”: No such 
file or directory
  Aug 25 00:26:35 pop-os tracker-extract[22122]: Task for 
'file:///usr/share/applications/nautilus-autorun-software.desktop.dpkg-new' 
finished with error: Error when getting information for file 
“/usr/share/applications/nautilus-autorun-software.desktop.dpkg-new”: No such 
file or directory
  Aug 25 00:26:35 pop-os tracker-extract[22122]: Could not get mimetype, Error 
when getting information for file 
“/usr/share/applications/nautilus-autorun-software.desktop.dpkg-tmp”: No such 
file or directory
  Aug 25 00:26:35 pop-os tracker-extract[22122]: Task for 
'file:///usr/share/applications/nautilus-autorun-software.desktop.dpkg-tmp' 
finished with error: Error when getting information for file 
“/usr/share/applications/nautilus-autorun-software.desktop.dpkg-tmp”: No such 
file or directory
  Aug 25 00:26:35 pop-os tracker-extract[22122]: Could not get mimetype, Error 
when getting information for file 
“/usr/share/applications/org.gnome.Nautilus.desktop.dpkg-new”: No such file or 
directory
  Aug 25 00:26:35 pop-os tracker-extract[22122]: Task for 
'file:///usr/share/applications/org.gnome.Nautilus.desktop.dpkg-new' finished 
with error: Error when getting information for file 
“/usr/share/applications/org.gnome.Nautilus.desktop.dpkg-new”: No such file or 
directory
  Aug 25 00:26:35 pop-os tracker-extract[22122]: Could not get mimetype, Error 
when getting information for file 
“/usr/share/applications/org.gnome.Nautilus.desktop.dpkg-tmp”: No such file or 
directory
  Aug 25 00:26:35 pop-os tracker-extract[22122]: Task for 
'file:///usr/share/applications/org.gnome.Nautilus.desktop.dpkg-tmp' finished 
with error: Error when getting information for file 
“/usr/share/applications/org.gnome.Nautilus.desktop.dpkg-tmp”: No such file or 
directory
  Aug 25 00:33:04 pop-os kernel: nautilus[28293]: segfault at 58 ip 
7f357c875052 sp 7ffeefa99f58 error 4 in 
libpython3.10.so.1.0[7f357c85f000+22d000]
  ```

  The segfaults are when running `$ nautilus` and "Error when getting
  information for file..." when running `sudo apt install --reinstall
  nautilus`

  help very much appreciated :)

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


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


[Desktop-packages] [Bug 1987572] [NEW] Segfault due to libpython3.10

2022-08-24 Thread Freaky Fee
Public bug reported:

```
$ lsb_release -rd

Description:Pop!_OS 22.04 LTS
Release:22.04
```

```
$ apt-cache policy nautilus

nautilus:
  Installed: 1:42.2-0ubuntu1
  Candidate: 1:42.2-0ubuntu1
  Version table:
 *** 1:42.2-0ubuntu1 500
500 http://apt.pop-os.org/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:42.0-1ubuntu2 500
500 http://apt.pop-os.org/ubuntu jammy/main amd64 Packages
```

I expected Nautilus to open properly, but got a segfault instead when running:
```
$ nautilus
```

It seems related to LibPython (output for `journalctl -q | grep -i
nautilus`):

```
Aug 25 00:12:59 pop-os kernel: nautilus[15964]: segfault at 58 ip 
7fe281475052 sp 7ffd24384d48 error 4 in 
libpython3.10.so.1.0[7fe28145f000+22d000]
Aug 25 00:15:23 pop-os kernel: nautilus[16160]: segfault at 10 ip 
7f90d352e68f sp 7ffdcba0d3c0 error 4 in 
libpython3.10.so.1.0[7f90d346d000+2b5000]
Aug 25 00:17:26 pop-os kernel: nautilus[17395]: segfault at 58 ip 
7f5e34675052 sp 7fff94fc3d18 error 4 in 
libpython3.10.so.1.0[7f5e3465f000+22d000]
Aug 25 00:26:32 pop-os sudo[22071]:  fee : TTY=pts/1 ; PWD=/home/fee ; 
USER=root ; COMMAND=/usr/bin/apt install --reinstall nautilus
Aug 25 00:26:35 pop-os tracker-extract[22122]: Could not get mimetype, Error 
when getting information for file 
“/usr/share/applications/nautilus-autorun-software.desktop.dpkg-new”: No such 
file or directory
Aug 25 00:26:35 pop-os tracker-extract[22122]: Task for 
'file:///usr/share/applications/nautilus-autorun-software.desktop.dpkg-new' 
finished with error: Error when getting information for file 
“/usr/share/applications/nautilus-autorun-software.desktop.dpkg-new”: No such 
file or directory
Aug 25 00:26:35 pop-os tracker-extract[22122]: Could not get mimetype, Error 
when getting information for file 
“/usr/share/applications/nautilus-autorun-software.desktop.dpkg-tmp”: No such 
file or directory
Aug 25 00:26:35 pop-os tracker-extract[22122]: Task for 
'file:///usr/share/applications/nautilus-autorun-software.desktop.dpkg-tmp' 
finished with error: Error when getting information for file 
“/usr/share/applications/nautilus-autorun-software.desktop.dpkg-tmp”: No such 
file or directory
Aug 25 00:26:35 pop-os tracker-extract[22122]: Could not get mimetype, Error 
when getting information for file 
“/usr/share/applications/org.gnome.Nautilus.desktop.dpkg-new”: No such file or 
directory
Aug 25 00:26:35 pop-os tracker-extract[22122]: Task for 
'file:///usr/share/applications/org.gnome.Nautilus.desktop.dpkg-new' finished 
with error: Error when getting information for file 
“/usr/share/applications/org.gnome.Nautilus.desktop.dpkg-new”: No such file or 
directory
Aug 25 00:26:35 pop-os tracker-extract[22122]: Could not get mimetype, Error 
when getting information for file 
“/usr/share/applications/org.gnome.Nautilus.desktop.dpkg-tmp”: No such file or 
directory
Aug 25 00:26:35 pop-os tracker-extract[22122]: Task for 
'file:///usr/share/applications/org.gnome.Nautilus.desktop.dpkg-tmp' finished 
with error: Error when getting information for file 
“/usr/share/applications/org.gnome.Nautilus.desktop.dpkg-tmp”: No such file or 
directory
Aug 25 00:33:04 pop-os kernel: nautilus[28293]: segfault at 58 ip 
7f357c875052 sp 7ffeefa99f58 error 4 in 
libpython3.10.so.1.0[7f357c85f000+22d000]
```

The segfaults are when running `$ nautilus` and "Error when getting
information for file..." when running `sudo apt install --reinstall
nautilus`

help very much appreciated :)

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


** Tags: segfault

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

Title:
  Segfault due to libpython3.10

Status in nautilus package in Ubuntu:
  New

Bug description:
  ```
  $ lsb_release -rd

  Description:  Pop!_OS 22.04 LTS
  Release:  22.04
  ```

  ```
  $ apt-cache policy nautilus

  nautilus:
Installed: 1:42.2-0ubuntu1
Candidate: 1:42.2-0ubuntu1
Version table:
   *** 1:42.2-0ubuntu1 500
  500 http://apt.pop-os.org/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:42.0-1ubuntu2 500
  500 http://apt.pop-os.org/ubuntu jammy/main amd64 Packages
  ```

  I expected Nautilus to open properly, but got a segfault instead when running:
  ```
  $ nautilus
  ```

  It seems related to LibPython (output for `journalctl -q | grep -i
  nautilus`):

  ```
  Aug 25 00:12:59 pop-os kernel: nautilus[15964]: segfault at 58 ip 
7fe281475052 sp 7ffd24384d48 error 4 in 
libpython3.10.so.1.0[7fe28145f000+22d000]
  Aug 25 00:15:23 pop-os kernel: nautilus[16160]: segfault at 10 ip 
7f90d352e68f sp 7ffdcba0d3c0 error 4 in 
libpython3.10.so.1.0[7f90d346d000+2b5000]
  Aug 25 00:17:26 pop-os kernel: nautilus[17395]: segfault at 58 ip 
7f5e34675052 sp 

[Desktop-packages] [Bug 1987524] Re: plasma-discover fails to build from source with snapd-glib 1.62

2022-08-24 Thread Jeremy Bicha
** Changed in: snapd-glib (Ubuntu)
   Status: New => Triaged

** Changed in: snapd-glib (Ubuntu)
   Importance: Undecided => High

** Also affects: snapd-glib via
   https://github.com/snapcore/snapd-glib/issues/125
   Importance: Unknown
   Status: Unknown

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

Title:
  plasma-discover fails to build from source with snapd-glib 1.62

Status in snapd-glib:
  Unknown
Status in plasma-discover package in Ubuntu:
  Invalid
Status in snapd-glib package in Ubuntu:
  Triaged

Bug description:
  We will be pushing snapd-glib 1.62 to Kinetic very soon as part of a
  large GNOME 43 transition.

  The new packaging switches to libsoup3. Out of an abundance of
  caution, the headers are installed to a new location and the soname
  was bumped.

  I tried building plasma-discover with the new version and it fails to
  build. Could you look into this issue? I'm not familiar with the Qt
  libraries.

  It does look like it builds successfully on current Kinetic so the
  problem was triggered by the library change.

  You can find the snapd-glib packages at
  https://launchpad.net/~jbicha/+archive/ubuntu/gnome43-staging-2/

  If you find a bug in snapd-glib itself, please report it at
  https://github.com/snapcore/snapd-glib/issues

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


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


[Desktop-packages] [Bug 1985057] Re: Camera output freeze when using pipewiresrc

2022-08-24 Thread Andreas Hasenack
** Also affects: pipewire (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

Title:
  Camera output freeze when using pipewiresrc

Status in OEM Priority Project:
  Confirmed
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Jammy:
  In Progress

Bug description:
  [Impact]
  On Dell platform with Microdia Integrated webcam, the Cheese preview is stuck 
on jammy.

  [Test Plan]
  1. Install Jammy on Dell platform with Microdia Integrated webcam
  2. Check the Cheese preview is stuck
  3. Install the updated pipewire packages by $ sudo apt dist-upgrade
  4. Open Cheese to check preview should work normally

  [Where problems could occur]
  The patches try to dequeue the shared buffer, instead of pool buffer to 
prevent the pool buffer being corrupted. it might cause some camera preview 
failed if shared buffer is corrupted.
  It is in upstream from 0.3.52 to 0.3.56, and there is no regression found,
  so the risk is low.

  [Other Info]
  Upstream commits:
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f

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


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


[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-24 Thread Douglas E Engert
https://launchpad.net/~liuck can you give some more information:

 What PKCS11 module are you using?

 What version of Ubuntu?

From my testing with a fresh copy install of XUbuntu-22.04.1 as guest of
VirtualBox, the "/run/user/[0-9]*/** mr," appears to allow access to any
file in my /usr/run/1000 directory.

When I use firefox's "Security Devices... Load" and browse for a module,
I give the path to the system version of the module(s) I have tried:
both /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-client.so and
/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so. Both get a "Unable to
add module" and the location shown in
/run/user/1000/doc/48e09223/p11-kit-client.so
/run/user/1000/doc/e3261d9/opensc-pkcs11.so

So it looks like it find the files and copies to /run/user/1000/doc/*.

But both of these modules need access to other libs and also need to use
pcscd to access the smartcard readers.

https://launchpad.net/~tnetter 
Can you give some more information about "/usr/local/lib/libcvP11.so"
It is not clear why this works with:  
https://forums.epo.org/new-version-of-the-cryptovision-software-12191#p40162

It may be that this is a simple library and does not use pcscd.

-- 
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 1974449] Re: No filepicker in Firefox with enforced AppArmor profile

2022-08-24 Thread Launchpad Bug Tracker
This bug was fixed in the package firefox -
104.0+build3-0ubuntu0.18.04.1

---
firefox (104.0+build3-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (104.0+build3)

firefox (104.0+build2-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (104.0+build2)

firefox (104.0+build1-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (104.0+build1)

  [ Olivier Tilloy ]
  * Update the apparmor profile to allow access to xdg-desktop-portal
and xdg-document-portal (LP: #1974449)
- debian/usr.bin.firefox.apparmor.14.10

  [ Rico Tzschichholz ]
  * Bump build-dep on nodejs(-mozilla) >= 12.22.1
- debian/control{,.in}

 -- Olivier Tilloy   Fri, 19 Aug 2022
07:23:58 +0200

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

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

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

Title:
  No filepicker in Firefox with enforced AppArmor profile

Status in firefox package in Ubuntu:
  Invalid
Status in firefox source package in Bionic:
  Fix Released
Status in firefox source package in Focal:
  Fix Released

Bug description:
  # System
  Ubuntu 22.04 LTS (Jammy Jellyfish) {kubuntu-ppa/backports/ubuntu jammy main | 
mozillateam/ppa/ubuntu/ jammy main}
  Package: firefox
  Version: 100.0.1+build1-0ubuntu0.22.04.1~mt1
  ---
  # Description
  I’m using Firefox stand-alone package (not the mainline Ubuntu Snap version) 
under KDE (native KDE filepicker) with enforced `usr.bin.firefox AppArmor` 
profile (included in `firefox` package) and when I try to open a file, save a 
screenshot or print to file, no filepicker shown.
  ---
  # Error message
  Can't open portal file chooser: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy 
prevents this sender from sending this message to this recipient; 
type="method_call", […] interface="org.freedesktop.portal.FileChooser" 
member="OpenFile" […] destination="org.freedesktop.portal.Desktop" […])
  ---
  # Suggested fix
  Please see commit:
  
https://github.com/snapcore/snapd/pull/8793/files/ec7f01e8c15bf9303cfb30354470d2a7b3783f25

  # Fix result
  Implementing the part for `org.freedesktop.portal.Desktop` from the above 
commit resolves the filepicker issue.

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


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


[Desktop-packages] [Bug 1974449] Re: No filepicker in Firefox with enforced AppArmor profile

2022-08-24 Thread Launchpad Bug Tracker
This bug was fixed in the package firefox -
104.0+build3-0ubuntu0.20.04.1

---
firefox (104.0+build3-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (104.0+build3)

firefox (104.0+build2-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (104.0+build2)

firefox (104.0+build1-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (104.0+build1)

  [ Olivier Tilloy ]
  * Update the apparmor profile to allow access to xdg-desktop-portal
and xdg-document-portal (LP: #1974449)
- debian/usr.bin.firefox.apparmor.14.10

  [ Rico Tzschichholz ]
  * Bump build-dep on nodejs(-mozilla) >= 12.22.1
- debian/control{,.in}

 -- Olivier Tilloy   Fri, 19 Aug 2022
07:25:17 +0200

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

Title:
  No filepicker in Firefox with enforced AppArmor profile

Status in firefox package in Ubuntu:
  Invalid
Status in firefox source package in Bionic:
  Fix Released
Status in firefox source package in Focal:
  Fix Released

Bug description:
  # System
  Ubuntu 22.04 LTS (Jammy Jellyfish) {kubuntu-ppa/backports/ubuntu jammy main | 
mozillateam/ppa/ubuntu/ jammy main}
  Package: firefox
  Version: 100.0.1+build1-0ubuntu0.22.04.1~mt1
  ---
  # Description
  I’m using Firefox stand-alone package (not the mainline Ubuntu Snap version) 
under KDE (native KDE filepicker) with enforced `usr.bin.firefox AppArmor` 
profile (included in `firefox` package) and when I try to open a file, save a 
screenshot or print to file, no filepicker shown.
  ---
  # Error message
  Can't open portal file chooser: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy 
prevents this sender from sending this message to this recipient; 
type="method_call", […] interface="org.freedesktop.portal.FileChooser" 
member="OpenFile" […] destination="org.freedesktop.portal.Desktop" […])
  ---
  # Suggested fix
  Please see commit:
  
https://github.com/snapcore/snapd/pull/8793/files/ec7f01e8c15bf9303cfb30354470d2a7b3783f25

  # Fix result
  Implementing the part for `org.freedesktop.portal.Desktop` from the above 
commit resolves the filepicker issue.

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


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


[Desktop-packages] [Bug 1987556] Re: Add a short alias (eg "gted") for gnome-text-editor

2022-08-24 Thread Jeremy Bicha
** Bug watch added: gitlab.gnome.org/GNOME/gnome-text-editor/-/issues #319
   https://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/319

** Also affects: gnome-text-editor via
   https://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/319
   Importance: Unknown
   Status: Unknown

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

Title:
  Add a short alias (eg "gted") for gnome-text-editor

Status in GNOME Text Editor:
  Unknown
Status in gnome-text-editor package in Ubuntu:
  New

Bug description:
  Unix pro users on the terminal emulator probably use vi, emacs or nano
  to edit plain text files. Those editors have all short binary names
  because it is a practical common UNIX practice to use short binary
  names for common usage patterns.

  With Ubuntu 22.10 gnome-text-editor is going to be the new default
  text editor instead of gedit. I used gedit quite often for editing
  files and "gedit" was as easy and fast to type as "vi" or "nano".

  gnome-text-editor is certainly not written for being invoked from the
  terminal but like gedit before it will be used a lot by Linux
  beginners for its ease of use (like notepad on Windows).

  Having a short alias name like e.g. "gted" by default would make it
  easy to invoke gnome-text-editor for those who don't know how to set
  aliases or edit the .bashrc. And having it set by default would help
  seeing it used in Ubuntu tutorials.

  Upstream is not willing to discuss the clunky binary name (tried to
  file a bug there to no avail) thus this would be a non intrusive
  downstream workaround.

  As Debian is more of a power user distribution and Ubuntu more
  beginner-centric, I decided to file the bug for Ubuntu only. I
  proposed "gted" because the full term doesn't seem to be commonly used
  in a UNIX context yet and the "ed" part is often used in a UNIX
  context to indicate a text editor ("ED", "sED", gEDit,...).

  1) System: Ubuntu 22.10 development version

  2) Package: gnome-text-editor 42.2

  3) What I expected to happen: a fast way to open the text editor that
  I am used to in gnome-terminal

  4) what happened instead: "gnome-text-editor filename"

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-text-editor/+bug/1987556/+subscriptions


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


[Desktop-packages] [Bug 1987556] [NEW] Add a short alias (eg "gted") for gnome-text-editor

2022-08-24 Thread amano
Public bug reported:

Unix pro users on the terminal emulator probably use vi, emacs or nano
to edit plain text files. Those have all short binary names because it
is a practical common UNIX practice to use short binary names for common
usage.

With Ubuntu 22.10 gnome-text-editor is the new default text editor
instead of gedit. I used gedit quite often for editing files and "gedit"
was like "vi" or "nano" easy to type.

gnome-text-editor is not certainly not written for being invoked from
the terminal but like gedit before it will be used by Linux beginners
for it's ease of use (like notepad on Windows).

Having a short alias like e.g. "gted" by default would make it easy to
invoke gnome-text-editor for those who don't know how to set aliases or
edit the .bashrc. And having it set by default would help having seeing
it used in Ubuntu tutorials.

Upstream is not willing to discuss the clunky binary Name thus this
would be a non intrusive downstream workaround.

As Debian is more of a power user distribution and Ubuntu more beginner-
centric, I decided to file the bug for Ubuntu only.

1) System: Ubuntu 22.10

2) Package: gnome-text-editor 42.2

3) What I expected to happen: a fast way to open the text editor that I
am used to in gnome-terminal

4) what happened instead: "gnome-text-editor filename"

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

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

Title:
  Add a short alias (eg "gted") for gnome-text-editor

Status in gnome-text-editor package in Ubuntu:
  New

Bug description:
  Unix pro users on the terminal emulator probably use vi, emacs or nano
  to edit plain text files. Those have all short binary names because it
  is a practical common UNIX practice to use short binary names for
  common usage.

  With Ubuntu 22.10 gnome-text-editor is the new default text editor
  instead of gedit. I used gedit quite often for editing files and
  "gedit" was like "vi" or "nano" easy to type.

  gnome-text-editor is not certainly not written for being invoked from
  the terminal but like gedit before it will be used by Linux beginners
  for it's ease of use (like notepad on Windows).

  Having a short alias like e.g. "gted" by default would make it easy to
  invoke gnome-text-editor for those who don't know how to set aliases
  or edit the .bashrc. And having it set by default would help having
  seeing it used in Ubuntu tutorials.

  Upstream is not willing to discuss the clunky binary Name thus this
  would be a non intrusive downstream workaround.

  As Debian is more of a power user distribution and Ubuntu more
  beginner-centric, I decided to file the bug for Ubuntu only.

  1) System: Ubuntu 22.10

  2) Package: gnome-text-editor 42.2

  3) What I expected to happen: a fast way to open the text editor that
  I am used to in gnome-terminal

  4) what happened instead: "gnome-text-editor filename"

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


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


[Desktop-packages] [Bug 1930140] Re: GUI "Extract Here" bug - loop until disk is full

2022-08-24 Thread Marc Deslauriers
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Public Security to Public

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

Title:
  GUI "Extract Here"  bug - loop until disk is full

Status in file-roller package in Ubuntu:
  New

Bug description:
  What happened
  -
  When .rar file is extracted using GUI by right clicking the file and 
selecting "Extract Here", the process continued until the disk is full.

  What I expected
  ---
  Extracting the .rar file without consuming my whole disk. Actual file size 
after extraction is 22-23MB. 

  
  How it got resolved
  ---
  So I installed unrar package using "sudo apt-get install unrar" and the 
problem got resolved. Seems like a bug since the unrar package was not there by 
default and without unrar the process consumes the whole disk.

  OS details are as follows
  
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1930140/+subscriptions


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


[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2022-08-24 Thread Marc Deslauriers
** Changed in: openafs (Ubuntu)
   Status: New => Confirmed

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

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Fix Released
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  Confirmed
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions


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


[Desktop-packages] [Bug 1962214] Re: The documentation around NM's 10-globally-managed-devices.conf is inadequate

2022-08-24 Thread Lukas Märdian
I agree, done!

** This bug is no longer a duplicate of bug 1951653
   can't use NM for ethernet device on 20.04 LTS because it is 'strictly 
unmanaged'

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

Title:
  The documentation around NM's 10-globally-managed-devices.conf is
  inadequate

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

Bug description:
  So, we're UBports, porting Ubuntu Touch stack to Ubuntu 20.04. While
  debugging why NM won't manage the phone's USB network interface, I
  stumbled upon /usr/lib/NetworkManager/conf.d/10-globally-managed-
  devices.conf. This file prevents NM from managing ethernet connection,
  which confuses me since this file also exists on my laptop, yet NM
  happily manages its ethernet port.

  This file exists at part of NetworkManager package in Ubuntu without
  any documentation. And the reason given in the commit that add it [1]
  does not mention any specific reason why it's added. Only when looking
  in the log on my laptop do I see that something places the file with
  the same name in /run/NetworkManager/conf.d/, and requires greping in
  /usr/lib to find out that the thing is Netplan's generator binary.

  Now, that file in /run is empty, which requires another round of
  searching to find out that Netplan places this file when it's
  configured to use NM as a renderer. With that in mind, I discovered
  that /etc/netplan/01-network-manager-all.yaml exists on my laptop but
  not the phone. Now, because 'dpkg -S' returns empty result, I need to
  search again what places this file, with no avail. Luckily, I happen
  to have a clone of livecd-rootfs on my laptop, which leads me to this
  commit [2] which finally reveals the reason why this is done: to
  prevent systems which installs NM after-the-fact to have NM conflicts
  with e.g. systemd-networkd.

  All of these knowledge should not require this much searching plus
  grepping through _binary_ file. If either my laptop was not running
  Ubuntu or I didn't have livecd-rootfs cloned, it would be much harder
  to figure this out. They should be more properly documented, probably
  both in the /usr/lib/ and /run/ files. Thus, this issue is filled
  against both Netplan and NetworkManager packages.

  [1] 
https://git.launchpad.net/network-manager/commit?id=1ab4db73c1f0db30f3af1845a9c41e3c3952dea1
  [2] 
https://git.launchpad.net/livecd-rootfs/commit/?id=d9ce44d73a0a6d91156bb94e03063d541b0f7579

  P.S. Arguably, this behavior might be even wrong. According to
  https://netplan.io:

  > Obviously, without configuration, netplan will not do anything.

  This is not really the expected "not do anything". IMO the NM's
  behavior should be left at the default, unless e.g. the networkd
  renderer is used, in which case Netplan will disable NetworkManager to
  not manage interfaces configured by Netplan. However the reason above
  of preventing conflict with networkd is a valid one, and my proposal
  doesn't help with that particular case.

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


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


[Desktop-packages] [Bug 1987524] Re: plasma-discover fails to build from source with snapd-glib 1.62

2022-08-24 Thread Rik Mills
https://github.com/snapcore/snapd-glib/issues/125

** Bug watch added: github.com/snapcore/snapd-glib/issues #125
   https://github.com/snapcore/snapd-glib/issues/125

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

Title:
  plasma-discover fails to build from source with snapd-glib 1.62

Status in plasma-discover package in Ubuntu:
  Invalid
Status in snapd-glib package in Ubuntu:
  New

Bug description:
  We will be pushing snapd-glib 1.62 to Kinetic very soon as part of a
  large GNOME 43 transition.

  The new packaging switches to libsoup3. Out of an abundance of
  caution, the headers are installed to a new location and the soname
  was bumped.

  I tried building plasma-discover with the new version and it fails to
  build. Could you look into this issue? I'm not familiar with the Qt
  libraries.

  It does look like it builds successfully on current Kinetic so the
  problem was triggered by the library change.

  You can find the snapd-glib packages at
  https://launchpad.net/~jbicha/+archive/ubuntu/gnome43-staging-2/

  If you find a bug in snapd-glib itself, please report it at
  https://github.com/snapcore/snapd-glib/issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1987524/+subscriptions


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


[Desktop-packages] [Bug 1987524] Re: plasma-discover fails to build from source with snapd-glib 1.62

2022-08-24 Thread Rik Mills
** Also affects: snapd-glib (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  plasma-discover fails to build from source with snapd-glib 1.62

Status in plasma-discover package in Ubuntu:
  Invalid
Status in snapd-glib package in Ubuntu:
  New

Bug description:
  We will be pushing snapd-glib 1.62 to Kinetic very soon as part of a
  large GNOME 43 transition.

  The new packaging switches to libsoup3. Out of an abundance of
  caution, the headers are installed to a new location and the soname
  was bumped.

  I tried building plasma-discover with the new version and it fails to
  build. Could you look into this issue? I'm not familiar with the Qt
  libraries.

  It does look like it builds successfully on current Kinetic so the
  problem was triggered by the library change.

  You can find the snapd-glib packages at
  https://launchpad.net/~jbicha/+archive/ubuntu/gnome43-staging-2/

  If you find a bug in snapd-glib itself, please report it at
  https://github.com/snapcore/snapd-glib/issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1987524/+subscriptions


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


[Desktop-packages] [Bug 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid

2022-08-24 Thread Richard Ayotte
Glad I found this bug report. Deleting the cert fixed the problem for me
as well. I'm not sure why the cert changed and it would be nice to be
notified that it changed and to be offered the option to have it
replaced.

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

Title:
  Printing does not work on Ubuntu 22.04 - cups-pki-invalid

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 22.04 printing did not work. There is cups-pki-
  invalid error and printer goes to paused state.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  Uname: Linux 5.17.7-051707-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 15:34:47 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-10-12 (214 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010)
  Lpstat: device for HP_Color_LaserJet_M552_5F80BF: 
implicitclass://HP_Color_LaserJet_M552_5F80BF/
  MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic 
root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago)
  dmi.bios.date: 03/29/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: G513QY.318
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G513QY
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.81
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G513QY_G513QY
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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


[Desktop-packages] [Bug 1987038] Re: Fix slow refresh rate when AMD GPU screen in reverse prime mode

2022-08-24 Thread Kai-Heng Feng
debdiff for Focal.

** Patch added: "xserver-xorg-video-amdgpu_19.1.0-1ubuntu0.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1987038/+attachment/5611345/+files/xserver-xorg-video-amdgpu_19.1.0-1ubuntu0.1.debdiff

** Also affects: xserver-xorg-video-amdgpu (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal)
   Importance: Undecided => Medium

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

Title:
  Fix slow refresh rate when AMD GPU screen in reverse prime mode

Status in HWE Next:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Focal:
  Confirmed
Status in xserver-xorg-video-amdgpu source package in Jammy:
  Confirmed
Status in xserver-xorg-video-amdgpu source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  When AMD GPU is a GPU screen using reverse prime and its the only display, 
the fresh rate is very slow.

  [Fix]
  Enable present extension for GPU screen so it can be a viable CRTC to be 
selected.

  [Test]
  On a I+A laptop and external displays are routed to AMDGPU, disable internal 
display like closing lid can observe the issue.

  With the fix applied, the external display becomes very smooth.

  [Where problems could occur]
  I personally don't see why GPU screen can't use present extension, but this 
is Xorg so there might be some arcane reasons I didn't think of.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1987038/+subscriptions


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


[Desktop-packages] [Bug 1954970] Re: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"

2022-08-24 Thread Patryk "LeadMan" Benderz
runnuni as suggested didnt help:

$ remmina --set-option tls-seclevel=0

Any time frame when 1.27 will be available in Ubuntu's repo?

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

Title:
  remmina "Cannot connect to the RDP server ... via TLS. Check that the
  client and server support a common TLS version"

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

Bug description:
  Xubuntu Jammy (21.04)
  after upgrade
 libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1)
 libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1)
  Remmina can't connect to any RDP server (Win2008 R2) with error:
  "Cannot connect to the RDP server ... via TLS. Check that the client and 
server support a common TLS version"

  Rollback to Impish version of libs
 libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2
 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2
  makes it work normal.

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


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


[Desktop-packages] [Bug 1699942] Re: network-manager fails to deprecate addresses

2022-08-24 Thread Nick Rosbrook
For the systemd-networkd case, can you set `SYSTEMD_LOG_LEVEL=debug` on
systemd-networkd.service to see if it yields useful information?

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

Title:
  network-manager fails to deprecate addresses

Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  network manager does not properly deprecate autoconfigured temporary IP 
addresses when ValidLifetime for a prefix is 0 in router advertisements. This 
behaviour is non-compliant with RFC 4861 § 6.3.4, which reads:
  If the prefix is already present in the host's Prefix List as
  the result of a previously received advertisement, reset its
  invalidation timer to the Valid Lifetime value in the Prefix
  Information option.  If the new Lifetime value is zero, time-out
  the prefix immediately.

  The hosts instead continued to use temporary addresses configured
  until they reached their timeout, rather than immediately dropping the
  addresses. It further appears that it is generating new temporary
  addresses when the previous ones expire, but I have not been
  monitoring hosts closely enough to tell for sure---I will update on
  this when I have further information.

  This problem was discovered on Ubuntu Studio 16.04.2; it is not
  present on Ubuntu Server (which uses Debian networking scripts).

  Additional Info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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


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


[Desktop-packages] [Bug 1987296] Re: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-08-24 Thread Olivier Tilloy
It looks like squashfs support was added to this custom kernel:
https://github.com/ophub/amlogic-s9xxx-armbian/issues/511.

** Bug watch added: github.com/ophub/amlogic-s9xxx-armbian/issues #511
   https://github.com/ophub/amlogic-s9xxx-armbian/issues/511

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

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

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

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Update

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 103.0+build1-0ubuntu0.20.04.1
  Uname: Linux 5.15.60-flippy-75+o aarch64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed 
with exit code 1:
  BuildID: 20220718155818
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Mon Aug 22 16:12:32 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  IpRoute:
   default via 10.42.0.1 dev eth0 
   default via 10.42.0.1 dev eth0 proto dhcp metric 100 
   10.42.0.0/24 dev eth0 proto kernel scope link src 10.42.0.141 
   10.42.0.0/24 dev eth0 proto kernel scope link src 10.42.0.142 metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000
  Lspci:
   
  NoProfiles: True
  PciNetwork:
   
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Нет 
запущенного демона PulseAudio, либо он не запущен в качестве сеансового демона.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-08-22 (0 days ago)
  mtime.conffile..etc.firefox.syspref.js: 2021-02-15T01:04:48
  mtime.conffile..etc.logrotate.d.apport: 2022-08-21T11:18:31.143342

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


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


[Desktop-packages] [Bug 1987527] Re: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-08-24 Thread Olivier Tilloy
Relevant debug output from DpkgTerminalLog.txt:

==> Installing the firefox snap
error: cannot perform the following tasks:
- Download snap "firefox" (1670) from channel "stable" (Get 
https://canonical-bos01.cdn.snapcraftcontent.com/download-origin/canonical-lgw01/3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk_1670.snap?interactive=1=1660662000_3c8f8666e822bd3b6d08cba113fce9ffe5d7eb53:
 dial tcp: lookup canonical-bos01.cdn.snapcraftcontent.com on 127.0.0.53:53: 
read udp 127.0.0.1:52884->127.0.0.53:53: i/o timeout)

This looks like a transient network failure. Can you try reinstalling?

sudo apt reinstall firefox

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

Title:
  package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new
  firefox package pre-installation script subprocess returned error exit
  status 1

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  After upgrade from Ubuntu 20.04 to 22.04, the Firefox browser could
  not open.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Aug 16 12:05:53 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2018-03-08 (1629 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  Snap: firefox 104.0-3 (latest/stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   603  Done2022-08-23T16:40:48+01:00  2022-08-23T16:42:16+01:00  Refresh 
"firefox" snap from "esr/edge" channel
   604  Done2022-08-23T16:42:39+01:00  2022-08-23T16:44:13+01:00  Refresh 
"firefox" snap from "latest/stable" channel
  SourcePackage: firefox
  Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new 
firefox package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1987527] Re: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-08-24 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new
  firefox package pre-installation script subprocess returned error exit
  status 1

Status in firefox package in Ubuntu:
  New

Bug description:
  After upgrade from Ubuntu 20.04 to 22.04, the Firefox browser could
  not open.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Aug 16 12:05:53 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2018-03-08 (1629 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  Snap: firefox 104.0-3 (latest/stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   603  Done2022-08-23T16:40:48+01:00  2022-08-23T16:42:16+01:00  Refresh 
"firefox" snap from "esr/edge" channel
   604  Done2022-08-23T16:42:39+01:00  2022-08-23T16:44:13+01:00  Refresh 
"firefox" snap from "latest/stable" channel
  SourcePackage: firefox
  Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new 
firefox package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1987527] [NEW] package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

2022-08-24 Thread Bashir
Public bug reported:

After upgrade from Ubuntu 20.04 to 22.04, the Firefox browser could not
open.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Aug 16 12:05:53 2022
ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
InstallationDate: Installed on 2018-03-08 (1629 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
Snap: firefox 104.0-3 (latest/stable)
Snap.Changes:
 ID   Status  Spawn  Ready  Summary
 603  Done2022-08-23T16:40:48+01:00  2022-08-23T16:42:16+01:00  Refresh 
"firefox" snap from "esr/edge" channel
 604  Done2022-08-23T16:42:39+01:00  2022-08-23T16:44:13+01:00  Refresh 
"firefox" snap from "latest/stable" channel
SourcePackage: firefox
Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new firefox 
package pre-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new
  firefox package pre-installation script subprocess returned error exit
  status 1

Status in firefox package in Ubuntu:
  New

Bug description:
  After upgrade from Ubuntu 20.04 to 22.04, the Firefox browser could
  not open.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Aug 16 12:05:53 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2018-03-08 (1629 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  Snap: firefox 104.0-3 (latest/stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   603  Done2022-08-23T16:40:48+01:00  2022-08-23T16:42:16+01:00  Refresh 
"firefox" snap from "esr/edge" channel
   604  Done2022-08-23T16:42:39+01:00  2022-08-23T16:44:13+01:00  Refresh 
"firefox" snap from "latest/stable" channel
  SourcePackage: firefox
  Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: new 
firefox package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1987528] [NEW] Since upgrade from 20.04 → 22.04 ; unable to print in color, only black and white

2022-08-24 Thread Coeur Noir
Public bug reported:

Hi,

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

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

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

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

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

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

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

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

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

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Hi,

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

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

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

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

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

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

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


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


[Desktop-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

2022-08-24 Thread Coeur Noir
Hi.

It's not « limited » to pdf.

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

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  New
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

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


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


[Desktop-packages] [Bug 1699942] Re: network-manager fails to deprecate addresses

2022-08-24 Thread Julian Andres Klode
With systemd-networkd on the 20.04 server, the /64 prefix does not
bounce between 0s and 1s, but stays at 0s, but is not removed (nor is
the /128).

** Tags added: rls-kk-incoming

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

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

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

Title:
  network-manager fails to deprecate addresses

Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  network manager does not properly deprecate autoconfigured temporary IP 
addresses when ValidLifetime for a prefix is 0 in router advertisements. This 
behaviour is non-compliant with RFC 4861 § 6.3.4, which reads:
  If the prefix is already present in the host's Prefix List as
  the result of a previously received advertisement, reset its
  invalidation timer to the Valid Lifetime value in the Prefix
  Information option.  If the new Lifetime value is zero, time-out
  the prefix immediately.

  The hosts instead continued to use temporary addresses configured
  until they reached their timeout, rather than immediately dropping the
  addresses. It further appears that it is generating new temporary
  addresses when the previous ones expire, but I have not been
  monitoring hosts closely enough to tell for sure---I will update on
  this when I have further information.

  This problem was discovered on Ubuntu Studio 16.04.2; it is not
  present on Ubuntu Server (which uses Debian networking scripts).

  Additional Info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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


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


[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-24 Thread ThomasN
Many thanks to Luca Ferroni for summarizing a solution.
For users of European Patent Office smart cards seeing 
Secure Connection Failed... Error code: SSL_ERROR_HANDSHAKE_FAILURE_ALERT

please see instructions posted by thomasip on Wed Aug 24, 2022 2:29 pm at:
https://forums.epo.org/new-version-of-the-cryptovision-software-12191#p40162

-- 
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 1699942] Re: network-manager fails to deprecate addresses

2022-08-24 Thread Julian Andres Klode
I can reproduce this on kinetic. I get sent a 2a02:908:2812:7d20::/64
prefix via RA with "valid lifetime" and ""preferred lifetime" set to 0,
every 3s. Instead of the prefix being deleted from the interface, it's
lifetime is set to 1s and then expires every second, causing regular
"connection changed" type of errors in Chrome, it looks like this:


inet6 2a02:908:2812:7d20::e9eb/128 scope global dynamic noprefixroute 
   valid_lft 42961sec preferred_lft 42961sec
inet6 2a02:908:2812:7d20:55e8:17dd:e766:a872/64 scope global deprecated 
dynamic noprefixroute 
   valid_lft 6603sec preferred_lft 0sec

Reconnecting the WiFi gets rid of the /64 prefix.

I think my router is broken though, as it does not advertise any valid
prefix, so you end up with *only* the /64 prefix until the router
receives a new prefix from the ISP or reconfirms it or whatever, but
still this is broken regardless.

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

Title:
  network-manager fails to deprecate addresses

Status in network-manager package in Ubuntu:
  New

Bug description:
  network manager does not properly deprecate autoconfigured temporary IP 
addresses when ValidLifetime for a prefix is 0 in router advertisements. This 
behaviour is non-compliant with RFC 4861 § 6.3.4, which reads:
  If the prefix is already present in the host's Prefix List as
  the result of a previously received advertisement, reset its
  invalidation timer to the Valid Lifetime value in the Prefix
  Information option.  If the new Lifetime value is zero, time-out
  the prefix immediately.

  The hosts instead continued to use temporary addresses configured
  until they reached their timeout, rather than immediately dropping the
  addresses. It further appears that it is generating new temporary
  addresses when the previous ones expire, but I have not been
  monitoring hosts closely enough to tell for sure---I will update on
  this when I have further information.

  This problem was discovered on Ubuntu Studio 16.04.2; it is not
  present on Ubuntu Server (which uses Debian networking scripts).

  Additional Info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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


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


[Desktop-packages] [Bug 1987523] Re: Pulsaudio crashes once BT microphone is connected

2022-08-24 Thread Ante Karamatić
** Description changed:

- When I connect my BT headset with microphone, Pulsaudio crashes,
- sometimes even crashing Gnome itself. Syslog reports:
+ When I connect my BT headset with microphone and change profile to HFP,
+ Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports:
  
  Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX 
(AVRCP) as /devices/virtual/input/input37
  Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80%
  Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked
  Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data 
descriptor : 0x1 terminating
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of 
process 50808 owned by '1000' RT at priority 5.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source
  Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: 
[51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!
  Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at 
../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). 
Aborting.
  Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash 
report...
  Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie
  Aug 24 13:44:24 p14s systemd[1]: Started crash report submission.
  Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: 
/var/lock/whoopsie/lock
  Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully.
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk
  
  I've identified the upstream fix for this:
  
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e
  
  I've built packages with the fix and can confirm that it does solve the
  problem. Packages are available at:
  
  https://launchpad.net/~ivoks/+archive/ubuntu/pulse

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

Title:
  Pulsaudio crashes once BT microphone is connected

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my BT headset with microphone and change profile to
  HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog
  reports:

  Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX 
(AVRCP) as /devices/virtual/input/input37
  Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80%
  Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked
  Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data 
descriptor : 0x1 terminating
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of 
process 50808 owned by '1000' RT at priority 5.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source
  Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: 
[51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!
  Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at 
../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). 
Aborting.
  Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash 
report...
  Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie
  Aug 24 13:44:24 p14s systemd[1]: Started crash report submission.
  Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: 
/var/lock/whoopsie/lock
  Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully.
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk

  I've identified the upstream fix for this:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e

  I've built packages with the fix and can confirm that it does solve
  the problem. Packages are available at:

  https://launchpad.net/~ivoks/+archive/ubuntu/pulse

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


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

[Desktop-packages] [Bug 1987523] [NEW] Pulsaudio crashes once BT microphone is connected

2022-08-24 Thread Ante Karamatić
Public bug reported:

When I connect my BT headset with microphone and change profile to HFP,
Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports:

Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX (AVRCP) 
as /devices/virtual/input/input37
Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80%
Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked
Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data 
descriptor : 0x1 terminating
Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes 
of 1 users.
Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of 
process 50808 owned by '1000' RT at priority 5.
Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes 
of 1 users.
Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink
Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source
Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: 
[51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!
Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at 
../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). 
Aborting.
Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash 
report...
Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie
Aug 24 13:44:24 p14s systemd[1]: Started crash report submission.
Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: 
/var/lock/whoopsie/lock
Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully.
Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell
Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk

I've identified the upstream fix for this:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e

I've built packages with the fix and can confirm that it does solve the
problem. Packages are available at:

https://launchpad.net/~ivoks/+archive/ubuntu/pulse

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

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

Title:
  Pulsaudio crashes once BT microphone is connected

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my BT headset with microphone and change profile to
  HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog
  reports:

  Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX 
(AVRCP) as /devices/virtual/input/input37
  Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80%
  Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked
  Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data 
descriptor : 0x1 terminating
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of 
process 50808 owned by '1000' RT at priority 5.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source
  Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: 
[51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!
  Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at 
../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). 
Aborting.
  Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash 
report...
  Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie
  Aug 24 13:44:24 p14s systemd[1]: Started crash report submission.
  Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: 
/var/lock/whoopsie/lock
  Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully.
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk

  I've identified the upstream fix for this:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e

  I've built packages with the fix and can confirm that it does solve
  the problem. Packages are available at:

  https://launchpad.net/~ivoks/+archive/ubuntu/pulse

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


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


[Desktop-packages] [Bug 1601971] Re: update fails, "AppStream cache update failed."

2022-08-24 Thread Matthias Klumpp
Is this still an issue in Ubuntu 22.04 (Jammy)? (Pretty much none of the
code used in Xenial exists anymore in its previous form)

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

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

Title:
  update fails, "AppStream cache update failed."

Status in appstream package in Ubuntu:
  Incomplete

Bug description:
  Booted 16.04 amd64 from DVD, opened a gnome-terminal and ran,

  ubuntu@ubuntu:~$ sudo apt-get update
  Ign:1 cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) 
xenial InRelease
  Hit:2 cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) 
xenial Release
  Get:4 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB]  
 
  Get:5 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]   
 
  Get:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:7 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 
[119 kB]
  Get:8 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1,201 kB]
  Get:9 http://archive.ubuntu.com/ubuntu xenial/main Translation-en [568 kB]
   
  Get:10 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en 
[45.3 kB]
  Get:11 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 
Metadata [44.0 kB]
  Get:12 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 
Icons [50.8 kB]
  Get:13 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 
DEP-11 Metadata [158 B]
  Get:14 http://archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 Metadata 
[733 kB]
  Get:15 http://archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons [409 
kB]
  Get:16 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 
[252 kB]
  Get:17 http://archive.ubuntu.com/ubuntu xenial-updates/main Translation-en 
[99.8 kB]
  Get:18 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 
Metadata [186 kB]
  Get:19 http://archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 
Icons [150 kB]
  Get:20 http://archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 
DEP-11 Metadata [157 B]
  Fetched 4,293 kB in 1s (2,360 kB/s) 

  ** (appstreamcli:2593): CRITICAL **: Error while moving old database out of 
the way.
  AppStream cache update failed.
  Reading package lists... Done

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Mon Jul 11 19:24:40 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1710209] Re: package libappstream3 0.9.4-1ubuntu3 [modified: usr/share/doc/libappstream3/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/

2022-08-24 Thread Matthias Klumpp
Is this still an issue?

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

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

Title:
  package libappstream3 0.9.4-1ubuntu3 [modified:
  usr/share/doc/libappstream3/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libappstream3/changelog.Debian.gz', which is different
  from other instances of package libappstream3:i386

Status in appstream package in Ubuntu:
  Incomplete

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libappstream3 0.9.4-1ubuntu3 [modified: 
usr/share/doc/libappstream3/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Aug 11 07:58:41 2017
  DpkgHistoryLog:
   Start-Date: 2017-08-11  07:58:37
   Commandline: apt-get -f install
   Requested-By: mike (1000)
   Upgrade: libappstream3:i386 (0.9.4-1ubuntu1, 0.9.4-1ubuntu3)
  DpkgTerminalLog:
   Preparing to unpack .../libappstream3_0.9.4-1ubuntu3_i386.deb ...
   Unpacking libappstream3:i386 (0.9.4-1ubuntu3) over (0.9.4-1ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libappstream3_0.9.4-1ubuntu3_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from 
other instances of package libappstream3:i386
  DuplicateSignature:
   package:libappstream3:0.9.4-1ubuntu3 [modified: 
usr/share/doc/libappstream3/changelog.Debian.gz]
   Unpacking libappstream3:i386 (0.9.4-1ubuntu3) over (0.9.4-1ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libappstream3_0.9.4-1ubuntu3_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from 
other instances of package libappstream3:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libappstream3/changelog.Debian.gz', which is different from 
other instances of package libappstream3:i386
  InstallationDate: Installed on 2017-02-20 (171 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: appstream
  Title: package libappstream3 0.9.4-1ubuntu3 [modified: 
usr/share/doc/libappstream3/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libappstream3/changelog.Debian.gz', 
which is different from other instances of package libappstream3:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1987520] [NEW] package libxslt1.1 1.1.34-4ubuntu0.22.04.1 failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2

2022-08-24 Thread Luis Gomez
Public bug reported:

I dont know anything about this error

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libxslt1.1 1.1.34-4ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
AptOrdering:
 perl-modules-5.30:amd64: Remove
 libxslt1.1:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Aug 22 18:07:00 2022
ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de 
salida de error 2
InstallationDate: Installed on 2021-10-02 (325 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
SourcePackage: libxslt
Title: package libxslt1.1 1.1.34-4ubuntu0.22.04.1 failed to install/upgrade: el 
subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
UpgradeStatus: Upgraded to jammy on 2022-08-14 (9 days ago)

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


** Tags: amd64 apport-package jammy

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

Title:
  package libxslt1.1 1.1.34-4ubuntu0.22.04.1 failed to install/upgrade:
  el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de
  error 2

Status in libxslt package in Ubuntu:
  New

Bug description:
  I dont know anything about this error

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libxslt1.1 1.1.34-4ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   perl-modules-5.30:amd64: Remove
   libxslt1.1:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Aug 22 18:07:00 2022
  ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de 
salida de error 2
  InstallationDate: Installed on 2021-10-02 (325 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: libxslt
  Title: package libxslt1.1 1.1.34-4ubuntu0.22.04.1 failed to install/upgrade: 
el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
  UpgradeStatus: Upgraded to jammy on 2022-08-14 (9 days ago)

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


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


[Desktop-packages] [Bug 1967963] Re: Firefox snap cannot be set as default browser under KDE

2022-08-24 Thread Olivier Tilloy
I ran the test plan ("xdg-settings check default-web-browser
firefox_firefox.desktop") in a fully up-to-date Kubuntu 22.04 VM, first
without the update from jammy-proposed (xdg-utils
1.1.3-4.1ubuntu3~22.04.1), and then with it.

I can confirm that with the update, the extraneous output on stderr is
gone. The functionality itself isn't impacted.

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

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

Title:
  Firefox snap cannot be set as default browser under KDE

Status in firefox package in Ubuntu:
  Invalid
Status in xdg-utils package in Ubuntu:
  Fix Released
Status in firefox source package in Jammy:
  Invalid
Status in xdg-utils source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Minor.
  This is a follow-up to bug #1970594. The original upstream merge request did 
fix the problem, but a misleading error message would be printed on stderr 
(which wasn't impacting firefox's ability to check whether it is the default 
browser). The upstream merge request has been updated to address this problem, 
and this SRU updates the corresponding patch to match the upstream MR (and 
what's in kinetic).

  
  [Test Plan]

  In Kubuntu 22.04, run the following command:

  xdg-settings check default-web-browser firefox_firefox.desktop

  The only output should be "yes" (or "no" depending on your default browser 
setting) on stdout, and nothing on stderr. One can redirect stderr to a file to 
verify that.
  The exit code of the command should be 0.

  
  [Where problems could occur]

  The patch is changing KDE-specific functions (check_browser_kde and
  check_url_scheme_handler_kde), so in theory it shouldn't affect
  running xdg-utils in any other desktop environment.

  If the proposed patch is incorrect, it would affect the functionality
  of `xdg-settings check default-web-browser` and `xdg-settings check
  default-url-scheme-handler`, so this is what needs to be thoroughly
  tested in KDE.

  
  [Original description]

  I was unable to set Firefox as the default browser by going to
  Settings -> Applications -> Default Applications -> Web browser. It
  was set to Other... and web links opened in Kate.

  In addition, I was unable to report a bug against Firefox because "it
  is provided by a snap provided by Mozilla."

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Apr  5 19:54:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2022-03-30 (6 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20L50067US
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 1.41
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET66W (1.41 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L50067US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET66W(1.41):bd10/20/2021:br1.41:efr1.22:svnLENOVO:pn20L50067US:pvrThinkPadT480:rvnLENOVO:rn20L50067US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L50067US
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
  version.libgl1-mesa-glx: 

[Desktop-packages] [Bug 1967963] Re: Firefox snap cannot be set as default browser under KDE

2022-08-24 Thread Olivier Tilloy
** Changed in: xdg-utils (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: xdg-utils (Ubuntu Jammy)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: xdg-utils (Ubuntu)
   Importance: Undecided => Low

** Changed in: xdg-utils (Ubuntu Jammy)
   Importance: Undecided => Low

** Changed in: xdg-utils (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Firefox snap cannot be set as default browser under KDE

Status in firefox package in Ubuntu:
  Invalid
Status in xdg-utils package in Ubuntu:
  Fix Released
Status in firefox source package in Jammy:
  Invalid
Status in xdg-utils source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Minor.
  This is a follow-up to bug #1970594. The original upstream merge request did 
fix the problem, but a misleading error message would be printed on stderr 
(which wasn't impacting firefox's ability to check whether it is the default 
browser). The upstream merge request has been updated to address this problem, 
and this SRU updates the corresponding patch to match the upstream MR (and 
what's in kinetic).

  
  [Test Plan]

  In Kubuntu 22.04, run the following command:

  xdg-settings check default-web-browser firefox_firefox.desktop

  The only output should be "yes" (or "no" depending on your default browser 
setting) on stdout, and nothing on stderr. One can redirect stderr to a file to 
verify that.
  The exit code of the command should be 0.

  
  [Where problems could occur]

  The patch is changing KDE-specific functions (check_browser_kde and
  check_url_scheme_handler_kde), so in theory it shouldn't affect
  running xdg-utils in any other desktop environment.

  If the proposed patch is incorrect, it would affect the functionality
  of `xdg-settings check default-web-browser` and `xdg-settings check
  default-url-scheme-handler`, so this is what needs to be thoroughly
  tested in KDE.

  
  [Original description]

  I was unable to set Firefox as the default browser by going to
  Settings -> Applications -> Default Applications -> Web browser. It
  was set to Other... and web links opened in Kate.

  In addition, I was unable to report a bug against Firefox because "it
  is provided by a snap provided by Mozilla."

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Apr  5 19:54:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2022-03-30 (6 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20L50067US
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 1.41
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET66W (1.41 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L50067US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET66W(1.41):bd10/20/2021:br1.41:efr1.22:svnLENOVO:pn20L50067US:pvrThinkPadT480:rvnLENOVO:rn20L50067US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L50067US
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  

[Desktop-packages] [Bug 1318327] Re: Can't open .webp files

2022-08-24 Thread Launchpad Bug Tracker
This bug was fixed in the package eog - 43~beta-1ubuntu2

---
eog (43~beta-1ubuntu2) kinetic; urgency=medium

  * Revert changes temporarily disabling webp support (LP: #1318327)
(LP: #1979121)

 -- Jeremy Bicha   Mon, 22 Aug 2022 10:03:25 -0400

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

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

Title:
  Can't open .webp files

Status in Eye of GNOME:
  Confirmed
Status in eog package in Ubuntu:
  Fix Released

Bug description:
  Please, add webp support.

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


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


[Desktop-packages] [Bug 1983645] Re: Can't find 5G option in Network Mode under Mobile Network

2022-08-24 Thread Sebastien Bacher
The fix has been merged upstream and is in kinetic as part of the 43
update

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

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

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

Title:
  Can't find 5G option in Network Mode under Mobile Network

Status in OEM Priority Project:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Jammy:
  New

Bug description:
  [Impact]
  There is no 5G related option in Network Mode under Mobile Network

  [Test case]
  1. System should have 5G capable hardware (SIM and WWAN module) and 5G 
enabled Modem Manager (>=1.19.1)
  2. Enable mobile network
  3. Check network mode
  4. There should be 5G related option

  [Where problems could occur]
  gnome-control-center interact with Modem Manager to get current network mode 
and set preferred network mode. Modem Manager will filter the unsupported mode. 
The risk will be low.

  [Other info]
  This patch is from upstream gnome-control-center. For more information 
  refer to 
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1388

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


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


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

2022-08-24 Thread Sebastien Bacher
40.7-0ubuntu2 is working as expected, allowing backup to google drive

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

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

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

Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Focal:
  Fix Committed
Status in deja-dup source package in Jammy:
  Fix Released
Status in deja-dup package in Debian:
  New

Bug description:
  * Impact

  The method Deja-Dup is using to authentificate to google account will
  stop working in september.

  * Test case

  Configure deja-dup to do backups on a google drive account. After
  confirming the authorization through the web browser it should be
  possible to start the backup.

  Check on the webview that the files are correctly added.

  Restore some data and ensure that's working.

  * Regression potential

  The codepath is used for oauth authentification and integration with
  the system mimetype. Check that the webbrowser auth workflow works as
  expected, testing deb and snap based browsers

  --

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

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

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

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

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

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

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

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


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


[Desktop-packages] [Bug 1982551] Re: Print is failed via USB

2022-08-24 Thread Jiang
Can anyone analyze the cause of this problem?

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

Title:
  Print is failed via USB

Status in cups package in Ubuntu:
  New

Bug description:
  Phenomenon:
  After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it 
can be printed at the first time, but after the second or multiple times, the 
job will be canceled.

  Comment:
  1.Wait a few minutes and the job still won't be printed.
  2.After unplugging in and plugging in the USB cable, the job can be printed
  3.The problem does not occur via network printing.
  4.Other systems (such as Windows, Mac OS) do not have this problem.

  Our analysis:
  1.We think that part of the data was lost via USB transmission

  2.In CUPS ErrorLog, the job has been delivered completely.
  (refer to error_log->[Job 313])
  D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting renderer with command: 
\"printf \"%%!PS-Adobe-3.0
  D [21/Jul/2022:15:21:17 +0800] [Job 313] Title: 
(/home/rits/文档/17540黑白-2017.doc)
  D [21/Jul/2022:15:21:17 +0800] [Job 313] %%
  D [21/Jul/2022:15:21:17 +0800] [Job 313] 
%%\\n/lppswd()def\\n/usrcode()def\\n/sppswd()def\\nmark\\n/usrcode 
where{pop}{/usrcode()def}ifelse\\n(rits) usrcode (20`date +%y%m%d%R | sed 
\'s/://\'`) {setuserinfo} stopped\\ncleartomark\\nmark {\\n<<\\n /JobType 0\\n 
/JobInfo <<\\n /UserID (rits)\\n /Time (20`date +%y%m%d%R | sed \'s/://\'`)\\n 
/HostLoginName (rits)\\n /HostName (rits-OptiPlex-3010)\\n >>\\n>> 
/RDeviceProcSet /ProcSet findresource /SetJobType get exec\\n}stopped 
cleartomark\\nmark{\\nuserdict /RPS_BPdict 2 dict put\\nuserdict /RPS_BPdict 
get begin /RPS_BP_MEDIAPOSITION null def end\\n} stopped 
cleartomark\\nmark{\\nuserdict /RPS_BPdict get begin\\n/RPS_BP_MEDIATYPE (Auto) 
def end\\n} stopped cleartomark\\nmark{\\n<<\\n/BannerPageMode 
false\\n/MediaPosition null\\n/MediaType null\\n>>\\n/RDeviceProcSet\\n/ProcSet 
findresource\\n/SetBannerPage get exec\\n} stopped cleartomark\\n\"; cat;\"
  D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid3\" 
(generation 1)
  D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid4\" 
(generation 2)
  D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"renderer\" 
(generation 2)
  D [21/Jul/2022:15:21:17 +0800] [Job 313] JCL: \033%-12345X@PJL
  D [21/Jul/2022:15:21:17 +0800] [Job 313] 
  
  I [21/Jul/2022:15:21:25 +0800] [Job 313] Job completed.

  3.However, I found an error on USB Request Block (URB) with Wireshark on 
Ubuntu 18.04
  [Error: undefined; Off fendingCommand: BPdict Flushing: rest of job (to end 
of file) will be ignored] appeared at [URB BULK IN]
  (refer to usb2.pcapng, snapshot.pn)

  4.We extracted the accepted data on the printer side, the data is really lost.
  (refer to prt00016.prn,
  prt00013.prn is the data of normal print)

  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04
  CUPS 2.2.7

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.9
  ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192
  Uname: Linux 5.4.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 22 15:43:30 2022
  InstallationDate: Installed on 2022-07-05 (16 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: Dell Inc. OptiPlex 3010
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic 
root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 042P49
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 3010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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


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


[Desktop-packages] [Bug 1977551] Re: [MIR] lerc

2022-08-24 Thread Sebastien Bacher
Override component to main
lerc 3.0+ds-1ubuntu1 in kinetic: universe/misc -> main
liblerc-dev 3.0+ds-1ubuntu1 in kinetic amd64: universe/libdevel/optional/100% 
-> main
liblerc-dev 3.0+ds-1ubuntu1 in kinetic arm64: universe/libdevel/optional/100% 
-> main
liblerc-dev 3.0+ds-1ubuntu1 in kinetic armhf: universe/libdevel/optional/100% 
-> main
liblerc-dev 3.0+ds-1ubuntu1 in kinetic ppc64el: universe/libdevel/optional/100% 
-> main
liblerc-dev 3.0+ds-1ubuntu1 in kinetic riscv64: universe/libdevel/optional/100% 
-> main
liblerc3 3.0+ds-1ubuntu1 in kinetic amd64: universe/libs/optional/100% -> main
liblerc3 3.0+ds-1ubuntu1 in kinetic arm64: universe/libs/optional/100% -> main
liblerc3 3.0+ds-1ubuntu1 in kinetic armhf: universe/libs/optional/100% -> main
liblerc3 3.0+ds-1ubuntu1 in kinetic ppc64el: universe/libs/optional/100% -> main
liblerc3 3.0+ds-1ubuntu1 in kinetic riscv64: universe/libs/optional/100% -> main
Override [y|N]? y


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

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

Title:
  [MIR] lerc

Status in lerc package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  The package lerc is already in Ubuntu universe.
  The package lerc build for the architectures it is designed to work on.
  It currently builds and works for architetcures: amd64 arm64 armhf ppc64el 
riscv64
  s390x fails since upstream doesn't support big endian architecture
  https://github.com/Esri/lerc/blob/master/src/LercLib/Defines.h#L56
  which was discussed on in Debian
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990789

  Debian is built tiff without lerc support to workaround that issue.
  Ideally it would be available on every architecture but it's probably not 
important for s390x users so we think the current solution is acceptable.
  Link to package https://launchpad.net/ubuntu/+source/lerc

  [Rationale]
  - The package lerc is required in Ubuntu main as a new depends of tiff.

  - The package lerc is required in Ubuntu main no later than aug 25 due
  to feature freeze

  [Security]
  - No CVEs/security issues in this software in the past

  - no `suid` or `sgid` binaries
  - no executables in `/sbin` and `/usr/sbin`
  - Package does not install services, timers or recurring jobs
  - Packages does not open privileged ports (ports < 1024)
  - Packages does not contain extensions to security-sensitive software

  [Quality assurance - function/usage]
  - The package works well right after install

  [Quality assurance - maintenance]
  The package is rather now but seems well maintained in Debian/Ubuntu and has 
no open bug reports
  - The package does not deal with exotic hardware we cannot support

  [Quality assurance - testing]
  - The package runs a test suite on build time, if it fails
it makes the build fail, link to build log 
https://launchpadlibrarian.net/573017632/buildlog_ubuntu-jammy-amd64.lerc_3.0+ds-1_BUILDING.txt.gz

  - The package runs an autopkgtest, and is currently passing on
this amd64 arm64 armhf ppc64el list of architectures, link to test logs 
https://autopkgtest.ubuntu.com/packages/l/lerc

  The i386 failure is due to python3 packages installability issues on
  that architecture. The s390x one is due to the fact that the library
  isn't build on that architecture as explained earlier. This is ok
  because neither of those are sign of problems with the library.

  [Quality assurance - packaging]
  - debian/watch is present and works

  # lintian --pedantic
  running with root privileges is not recommended!
  P: lerc source: package-uses-old-debhelper-compat-version 12
  P: lerc source: very-long-line-length-in-source-file CHANGELOG.md line 23 is 
567 characters long (>512)
  P: lerc source: very-long-line-length-in-source-file README.md line 23 is 620 
characters long (>512)

  those are only minor warnings

  - Lintian overrides are not present

  - This package does not rely on obsolete or about to be demoted packages.
  - This package has no python2 or GTK2 dependencies

  - The package will be installed by default, but does not ask debconf
  questions higher than medium

  - Packaging and build is easy, link to d/rules
  https://salsa.debian.org/debian-gis-
  team/lerc/-/blob/master/debian/rules

  [UI standards]
  - Application is not end-user facing (does not need translation)

  [Dependencies]
  - No further depends or recommends dependencies that are not yet in main

  [Standards compliance]
  - This package correctly follows FHS and Debian Policy

  [Maintenance/Owner]
  - Owning Team will be desktop-packages
  - Team is not yet, but will subscribe to the package before promotion

  - The package successfully built during the most recent test rebuild

  [Background information]
  The Package description explains the package well
  Upstream Name is lerc
  Link to upstream project 

[Desktop-packages] [Bug 1979121] Re: [MIR] webp-pixbuf-loader

2022-08-24 Thread Sebastien Bacher
Override component to main
webp-pixbuf-loader 0.0.5-5 in kinetic: universe/misc -> main
webp-pixbuf-loader 0.0.5-5 in kinetic amd64: universe/gnome/optional/100% -> 
main
webp-pixbuf-loader 0.0.5-5 in kinetic arm64: universe/gnome/optional/100% -> 
main
webp-pixbuf-loader 0.0.5-5 in kinetic armhf: universe/gnome/optional/100% -> 
main
webp-pixbuf-loader 0.0.5-5 in kinetic ppc64el: universe/gnome/optional/100% -> 
main
webp-pixbuf-loader 0.0.5-5 in kinetic riscv64: universe/gnome/optional/100% -> 
main
webp-pixbuf-loader 0.0.5-5 in kinetic s390x: universe/gnome/optional/100% -> 
main
Override [y|N]? y
7 publications overridden.


** Changed in: webp-pixbuf-loader (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] webp-pixbuf-loader

Status in webp-pixbuf-loader package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  The package webp-pixbuf-loader is already in Ubuntu universe.
  The package webp-pixbuf-loader build for the architectures it is designed to 
work on.
  It currently builds and works for architetcures: amd64 arm64 armhf ppc64el 
riscv64 
  s390x is failing tests in which seems a big endian issue, reported upstream 
https://github.com/aruiz/webp-pixbuf-loader/issues/39
  Link to package https://launchpad.net/ubuntu/+source/webp-pixbuf-loader

  [Rationale]
  - The package webp-pixbuf-loader is required in Ubuntu main to be able to 
open webp image from the standard viewer (eog) and get thumbnails in the 
filemanage
  - The package webp-pixbuf-loader will generally be useful for a large part of 
our user base

  - The package webp-pixbuf-loader is required in Ubuntu main no later
  than aug 25 due to feature freeze

  [Security]
  - No CVEs/security issues in this software in the past

  - no executables in `/sbin` and `/usr/sbin`
  - Package does not install services, timers or recurring jobs
  - Packages does not open privileged ports (ports < 1024)
  - Packages does not contain extensions to security-sensitive software

  [Quality assurance - function/usage]
  - The package works well right after install

  [Quality assurance - maintenance]
  - The package is new in Debian/Ubuntu and has currently no bug reported
  - The package does not deal with exotic hardware we cannot support

  [Quality assurance - testing]
  - The package runs a test suite on build time, if it fails
    it makes the build fail, link to build log 
https://launchpadlibrarian.net/607631911/buildlog_ubuntu-kinetic-amd64.webp-pixbuf-loader_0.0.5-2_BUILDING.txt.gz

  - The package does not run an autopkgtest because image loaders aren't
  easy to verify in that setup, but we will open example webp files as a
  manual testcase before doing package updates.

  [Quality assurance - packaging]
  - debian/watch is present and works

  - the package is in sync with Debian and has a valid maintainer
  definition

  - The package displays no lintian warnings
  - Please link to a recent build log of the package 
https://launchpadlibrarian.net/607631911/buildlog_ubuntu-kinetic-amd64.webp-pixbuf-loader_0.0.5-2_BUILDING.txt.gz
  - Lintian overrides are not present

  [Maintenance/Owner]
  - Owning Team will be desktop-packages
  - Team is already subscribed to the package

  - This does not use static builds
  - This does not use vendored code

  - The package has been built in the archive more recently than the
  last test rebuild

  [Background information]
  The Package description explains the package well
  Upstream Name is webp-pixbuf-loader
  Link to upstream project https://github.com/aruiz/webp-pixbuf-loader/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webp-pixbuf-loader/+bug/1979121/+subscriptions


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


[Desktop-packages] [Bug 1987038] Re: Fix slow refresh rate when AMD GPU screen in reverse prime mode

2022-08-24 Thread Timo Aaltonen
sru uploaded

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

Title:
  Fix slow refresh rate when AMD GPU screen in reverse prime mode

Status in HWE Next:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Jammy:
  Confirmed
Status in xserver-xorg-video-amdgpu source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  When AMD GPU is a GPU screen using reverse prime and its the only display, 
the fresh rate is very slow.

  [Fix]
  Enable present extension for GPU screen so it can be a viable CRTC to be 
selected.

  [Test]
  On a I+A laptop and external displays are routed to AMDGPU, disable internal 
display like closing lid can observe the issue.

  With the fix applied, the external display becomes very smooth.

  [Where problems could occur]
  I personally don't see why GPU screen can't use present extension, but this 
is Xorg so there might be some arcane reasons I didn't think of.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1987038/+subscriptions


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


[Desktop-packages] [Bug 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end

2022-08-24 Thread Daniel van Vugt
** Tags added: fixed-in-22.1.5

** Changed in: mesa (Ubuntu)
   Status: Triaged => Fix Released

** Tags added: rls-jj-incoming

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Fix Released

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/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
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/mesa/+bug/1972977/+subscriptions


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


[Desktop-packages] [Bug 1983788] Re: Update gnome-remote-desktop to 42.4

2022-08-24 Thread Chris Halse Rogers
Hello Jeremy, or anyone else affected,

Accepted gnome-remote-desktop into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-remote-desktop/42.4-0ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-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/1983788

Title:
  Update gnome-remote-desktop to 42.4

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

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

  It fixes some crashes reported to errors.ubuntu.com

  https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/commit/4998bdf4ef58d4a384c93fd7543bedb7411e5854

  https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/commit/665f734ab7cdd52b9b2340e00f42f91a919baca7

  https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/compare/42.3...42.4

  Test Cases
  --
  Complete all the test cases from
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop

  except for the "New Audio Forwarding Feature" test case.

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

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

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

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

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


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