[Desktop-packages] [Bug 1954742] [NEW] Sound starts delayed (4sec) when using HDMI audio

[DarkTrick]

Public bug reported:

Reproduce:
- Connect notebook to external monitor via HDMI
- Start random video in youtube / vlc player

Actual:
- Sound starts with about 4secs of delay

Reproducible: 
always


Misc:
The package is just a guess.


lsb_release -rd
Description:Ubuntu 21.10
Release:21.10

apt-cache policy pulseaudio
pulseaudio:
  Installed: 1:15.0+dfsg1-1ubuntu2.2
  Candidate: 1:15.0+dfsg1-1ubuntu2.2
  Version table:
 *** 1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%)
500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:15.0+dfsg1-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
Uname: Linux 5.13.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nimono 2373 F pulseaudio
 /dev/snd/pcmC0D3p:   nimono 2373 F...m pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Tue Dec 14 15:20:56 2021
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to impish on 2021-12-08 (6 days ago)
dmi.bios.date: 01/23/2018
dmi.bios.release: 1.7
dmi.bios.vendor: FUJITSU // Insyde Software Corp.
dmi.bios.version: Version 1.07
dmi.board.name: FJNB2BB
dmi.board.vendor: FUJITSU
dmi.board.version: A2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:sku:
dmi.product.family: LIFEBOOK-JR
dmi.product.name: FMVWB3U27
dmi.sys.vendor: FUJITSU
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2021-12-08T10:02:48.239277

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


** Tags: amd64 apport-bug impish

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

Title:
  Sound starts delayed (4sec) when using HDMI audio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Reproduce:
  - Connect notebook to external monitor via HDMI
  - Start random video in youtube / vlc player

  Actual:
  - Sound starts with about 4secs of delay

  Reproducible: 
  always

  
  Misc:
  The package is just a guess.

  
  lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10

  apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:15.0+dfsg1-1ubuntu2.2
Candidate: 1:15.0+dfsg1-1ubuntu2.2
Version table:
   *** 1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%)
  500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:15.0+dfsg1-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nimono 2373 F pulseaudio
   /dev/snd/pcmC0D3p:   nimono 2373 F...m pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Dec 14 15:20:56 2021
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to impish on 2021-12-08 (6 days ago)
  dmi.bios.date: 01/23/2018
  dmi.bios.release: 1.7
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: Version 1.07
  dmi.board.name: FJNB2BB
  dmi.board.vendor: FUJITSU
  dmi.board.version: A2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:sku:
  dmi.product.family: LIFEBOOK-JR
  dmi.product.name: FMVWB3U27
  dmi.sys.vendor: FUJITSU
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2021-12-08T10:02:48.239277

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


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

[Desktop-packages] [Bug 1954587] Re: Thunderbird: Mail preview is cropped

[Olivier Tilloy]

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

** Tags added: upstream

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

Title:
  Thunderbird: Mail preview is cropped

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  New

Bug description:
  The mail preview in Thunderbird crops away 50% of the UI (see
  screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.3.1+build1-0ubuntu0.21.10.2
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BuildID: 2022203138
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sun Dec 12 20:17:51 2021
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to impish on 2021-12-08 (4 days ago)

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


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

[Desktop-packages] [Bug 1946970] Re: Memory leak in gnome-shell after lock and unlock the screen

[Launchpad Bug Tracker]

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

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

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

Title:
  Memory leak in gnome-shell after lock and unlock the screen

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  When the screen is locked and unlocked extra ~100MB memory remains in
  use and never freed up. After each lock/unlock action additional
  10-20MB will be used, and the memory consumption of gnome-shell grows
  and grows.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-18.18-generic 5.13.14
  Uname: Linux 5.13.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 13 14:06:17 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-10-06 (7 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1954724] Re: Removing unattended-upgrades removes ubuntu-server-minimal

[Matthew Ruffell]

** Description changed:

  On Impish and later, removing unattended-upgrades also removes ubuntu-
  server-minimal due to ubuntu-server-minimal depending on unattended-
  upgrades
  
  $ sudo apt remove unattended-upgrades
  ...
  The following packages will be REMOVED:
-   ubuntu-server-minimal unattended-upgrades
+   ubuntu-server-minimal unattended-upgrades
  0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
  
  This behaviour has changed since ubuntu-meta 1.471 [1] when the ubuntu-
  server-minimal metapackage was introduced, declaring unattended-upgrades
  as Depends.
  
  [1] https://launchpadlibrarian.net/550345392/ubuntu-
  meta_1.470_1.471.diff.gz
  
  On Focal, there was no such behaviour on a fresh ubuntu-server install:
  
  $ sudo apt remove unattended-upgrades
  ...
  The following packages will be REMOVED:
-   unattended-upgrades
+   unattended-upgrades
  0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded.
  
  Removing unattended-upgrades is quite popular amongst our users, and
  they should be allowed to remove the package without removing the
  ubuntu-server-minimal metapackage.
  
  Looking at the source package for ubuntu-meta, unattended-upgrades is
  only Depends for ubuntu-server-minimal, maybe we should simply remove
- it?
+ it, or instead, change to recommends?
  
  $ grep -Rin "unattended-upgrades" .
  ./server-minimal-armhf:23:unattended-upgrades
  ./server-minimal-riscv64:23:unattended-upgrades
  ./server-minimal-arm64:23:unattended-upgrades
  ./server-minimal-ppc64el:23:unattended-upgrades
  ./server-minimal-s390x:24:unattended-upgrades
  ./server-minimal-amd64:23:unattended-upgrades
  
  $ sudo apt rdepends unattended-upgrades
  unattended-upgrades
  Reverse Depends:
-   Recommends: python3-software-properties
-   Recommends: ubuntu-mate-desktop
-   Recommends: ubuntu-mate-core
-   Depends: freedombox
-   Recommends: fbx-all
-   Depends: ubuntu-server-minimal
+   Recommends: python3-software-properties
+   Recommends: ubuntu-mate-desktop
+   Recommends: ubuntu-mate-core
+   Depends: freedombox
+   Recommends: fbx-all
+   Depends: ubuntu-server-minimal

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

Title:
  Removing unattended-upgrades removes ubuntu-server-minimal

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Impish:
  New
Status in ubuntu-meta source package in Jammy:
  New

Bug description:
  On Impish and later, removing unattended-upgrades also removes ubuntu-
  server-minimal due to ubuntu-server-minimal depending on unattended-
  upgrades

  $ sudo apt remove unattended-upgrades
  ...
  The following packages will be REMOVED:
    ubuntu-server-minimal unattended-upgrades
  0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.

  This behaviour has changed since ubuntu-meta 1.471 [1] when the
  ubuntu-server-minimal metapackage was introduced, declaring
  unattended-upgrades as Depends.

  [1] https://launchpadlibrarian.net/550345392/ubuntu-
  meta_1.470_1.471.diff.gz

  On Focal, there was no such behaviour on a fresh ubuntu-server
  install:

  $ sudo apt remove unattended-upgrades
  ...
  The following packages will be REMOVED:
    unattended-upgrades
  0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded.

  Removing unattended-upgrades is quite popular amongst our users, and
  they should be allowed to remove the package without removing the
  ubuntu-server-minimal metapackage.

  Looking at the source package for ubuntu-meta, unattended-upgrades is
  only Depends for ubuntu-server-minimal, maybe we should simply remove
  it, or instead, change to recommends?

  $ grep -Rin "unattended-upgrades" .
  ./server-minimal-armhf:23:unattended-upgrades
  ./server-minimal-riscv64:23:unattended-upgrades
  ./server-minimal-arm64:23:unattended-upgrades
  ./server-minimal-ppc64el:23:unattended-upgrades
  ./server-minimal-s390x:24:unattended-upgrades
  ./server-minimal-amd64:23:unattended-upgrades

  $ sudo apt rdepends unattended-upgrades
  unattended-upgrades
  Reverse Depends:
    Recommends: python3-software-properties
    Recommends: ubuntu-mate-desktop
    Recommends: ubuntu-mate-core
    Depends: freedombox
    Recommends: fbx-all
    Depends: ubuntu-server-minimal

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


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

[Desktop-packages] [Bug 1954724] [NEW] Removing unattended-upgrades removes ubuntu-server-minimal

[Matthew Ruffell]

Public bug reported:

On Impish and later, removing unattended-upgrades also removes ubuntu-
server-minimal due to ubuntu-server-minimal depending on unattended-
upgrades

$ sudo apt remove unattended-upgrades
...
The following packages will be REMOVED:
  ubuntu-server-minimal unattended-upgrades
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.

This behaviour has changed since ubuntu-meta 1.471 [1] when the ubuntu-
server-minimal metapackage was introduced, declaring unattended-upgrades
as Depends.

[1] https://launchpadlibrarian.net/550345392/ubuntu-
meta_1.470_1.471.diff.gz

On Focal, there was no such behaviour on a fresh ubuntu-server install:

$ sudo apt remove unattended-upgrades
...
The following packages will be REMOVED:
  unattended-upgrades
0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded.

Removing unattended-upgrades is quite popular amongst our users, and
they should be allowed to remove the package without removing the
ubuntu-server-minimal metapackage.

Looking at the source package for ubuntu-meta, unattended-upgrades is
only Depends for ubuntu-server-minimal, maybe we should simply remove
it?

$ grep -Rin "unattended-upgrades" .
./server-minimal-armhf:23:unattended-upgrades
./server-minimal-riscv64:23:unattended-upgrades
./server-minimal-arm64:23:unattended-upgrades
./server-minimal-ppc64el:23:unattended-upgrades
./server-minimal-s390x:24:unattended-upgrades
./server-minimal-amd64:23:unattended-upgrades

$ sudo apt rdepends unattended-upgrades
unattended-upgrades
Reverse Depends:
  Recommends: python3-software-properties
  Recommends: ubuntu-mate-desktop
  Recommends: ubuntu-mate-core
  Depends: freedombox
  Recommends: fbx-all
  Depends: ubuntu-server-minimal

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-meta (Ubuntu Impish)
 Importance: Undecided
 Status: New

** Affects: ubuntu-meta (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-meta (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-meta (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

Title:
  Removing unattended-upgrades removes ubuntu-server-minimal

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Impish:
  New
Status in ubuntu-meta source package in Jammy:
  New

Bug description:
  On Impish and later, removing unattended-upgrades also removes ubuntu-
  server-minimal due to ubuntu-server-minimal depending on unattended-
  upgrades

  $ sudo apt remove unattended-upgrades
  ...
  The following packages will be REMOVED:
ubuntu-server-minimal unattended-upgrades
  0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.

  This behaviour has changed since ubuntu-meta 1.471 [1] when the
  ubuntu-server-minimal metapackage was introduced, declaring
  unattended-upgrades as Depends.

  [1] https://launchpadlibrarian.net/550345392/ubuntu-
  meta_1.470_1.471.diff.gz

  On Focal, there was no such behaviour on a fresh ubuntu-server
  install:

  $ sudo apt remove unattended-upgrades
  ...
  The following packages will be REMOVED:
unattended-upgrades
  0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded.

  Removing unattended-upgrades is quite popular amongst our users, and
  they should be allowed to remove the package without removing the
  ubuntu-server-minimal metapackage.

  Looking at the source package for ubuntu-meta, unattended-upgrades is
  only Depends for ubuntu-server-minimal, maybe we should simply remove
  it?

  $ grep -Rin "unattended-upgrades" .
  ./server-minimal-armhf:23:unattended-upgrades
  ./server-minimal-riscv64:23:unattended-upgrades
  ./server-minimal-arm64:23:unattended-upgrades
  ./server-minimal-ppc64el:23:unattended-upgrades
  ./server-minimal-s390x:24:unattended-upgrades
  ./server-minimal-amd64:23:unattended-upgrades

  $ sudo apt rdepends unattended-upgrades
  unattended-upgrades
  Reverse Depends:
Recommends: python3-software-properties
Recommends: ubuntu-mate-desktop
Recommends: ubuntu-mate-core
Depends: freedombox
Recommends: fbx-all
Depends: ubuntu-server-minimal

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


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

[Desktop-packages] [Bug 1916469] Re: Apps don't use Wayland by default

[Daniel van Vugt]

Most Ubuntu users stick to the default session type which is now
Wayland. And most Ubuntu users probably never open Thunderbird. So the
subset of users affected by bug 1932328 is small compared to the overall
set size (millions?). A fix is committed for bug 1932328 and coming in
the next update.

We've been focussed on and discussing this issue for several years now,
waiting for the right time to default to Wayland. We waited longer than
other distros and made the switch in the April 2021 release. Asking to
change it back for one Thunderbird bug makes no sense.

Aside from anything else, you can just choose Xorg on the login screen
if you don't like the Wayland session. Change it once and your choice is
remembered. You will never see Wayland again.

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

Title:
  Apps don't use Wayland by default

Status in firefox package in Ubuntu:
  Fix Released
Status in qdirstat package in Ubuntu:
  Confirmed
Status in telegram-desktop package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu universe has a big Wayland problem!

  What does that mean?

  So a lot of packages in the Universe repository are not compiled with
  Wayland support which is really bad and would lead to bad performance
  after 21.04 comes out.

  Here are the following packages that I detected with wrong
  compilation:

  telegram-desktop (Wayland support work with snap version)
  kiwix
  firefox (everything works fine with this env variable 
set:"MOZ_ENABLE_WAYLAND=1")

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


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

[Desktop-packages] [Bug 1954587] Re: Thunderbird: Mail preview is cropped

[DarkTrick]

Thank you! 
Did so here: https://bugzilla.mozilla.org/show_bug.cgi?id=1745857

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

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

Title:
  Thunderbird: Mail preview is cropped

Status in thunderbird package in Ubuntu:
  New

Bug description:
  The mail preview in Thunderbird crops away 50% of the UI (see
  screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.3.1+build1-0ubuntu0.21.10.2
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BuildID: 2022203138
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sun Dec 12 20:17:51 2021
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to impish on 2021-12-08 (4 days ago)

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


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

[Desktop-packages] [Bug 1861598] Re: lightdm assumes pam-kwallet to be always installed

[Launchpad Bug Tracker]

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

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

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

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

Title:
  lightdm assumes pam-kwallet to be always installed

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  During boot, I see this error:

  > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: 
pam_kwallet.so
  > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to 
dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared 
object file: No such file or directory
  > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: 
pam_kwallet5.so

  which I guess it's caused by this:

  > # grep kwallet /etc/pam.d/lightd*
  > /etc/pam.d/lightdm:authoptionalpam_kwallet.so
  > /etc/pam.d/lightdm:authoptionalpam_kwallet5.so
  > /etc/pam.d/lightdm:session optionalpam_kwallet.so auto_start
  > /etc/pam.d/lightdm:session optionalpam_kwallet5.so auto_start
  > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet.so
  > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet5.so
  > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet.so auto_start
  > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet5.so 
auto_start

  kwallet is a KDE program, which is not installed on MATE (and I think
  it shouldn't be), so I guess that such modules should not be
  [attempted to be] loaded.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Sun Feb  2 11:03:53 2020
  InstallationDate: Installed on 2020-01-20 (12 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported

[Bug Watch Updater]

** Changed in: supysonic (Debian)
   Status: Unknown => New

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

Title:
  autopkgtest regressions with python3.10 as supported

Status in ipywidgets package in Ubuntu:
  New
Status in pygobject package in Ubuntu:
  New
Status in pytest-twisted package in Ubuntu:
  New
Status in python-b2sdk package in Ubuntu:
  New
Status in python-hypothesis package in Ubuntu:
  New
Status in python-taskflow package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in skimage package in Ubuntu:
  Invalid
Status in supysonic package in Ubuntu:
  New
Status in vorta package in Ubuntu:
  New
Status in ipywidgets package in Debian:
  New
Status in pygobject package in Debian:
  New
Status in pytest-twisted package in Debian:
  New
Status in python-b2sdk package in Debian:
  New
Status in python-hypothesis package in Debian:
  Unknown
Status in supysonic package in Debian:
  New
Status in vorta package in Debian:
  Unknown

Bug description:
  This bug is for tracking the packages having autopkgtest regressions
  with python3.10 as a supported version, blocking migration of
  python3-defaults/3.9.7-4.

  All packages are in universe except pygobject and python-taskflow in
  main.

  All packages have RC bugs in Debian except python-taskflow which is
  based on a newer upstream version.

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


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

[Desktop-packages] [Bug 1936647]

[B-emilio]

*** Bug 1721154 has been marked as a duplicate of this bug. ***

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

Title:
  right-click popups transparent after upgrade to Firefox 90

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Upon upgrade to Firefox 90, right-click popups appear transparent.
  I am using the Blackbird gtk theme. If I switch to Adwaita-dark, the problem 
goes away.
  I encountered this issue on another system with the direct download from 
Mozilla, so this is likely an upstream issue, but I'm not sure where to begin 
filing that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 90.0+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjotte 1155 F pulseaudio
   /dev/snd/controlC0:  kjotte 1155 F pulseaudio
   /dev/snd/controlC1:  kjotte 1155 F pulseaudio
  BuildID: 20210705185941
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Fri Jul 16 08:35:02 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-07-07 (373 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=90.0/20210705185941 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2021
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET27W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UAS0P200
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET27W(1.17):bd03/29/2021:svnLENOVO:pn20UAS0P200:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20UAS0P200:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20UAS0P200
  dmi.product.sku: LENOVO_MT_20UA_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1953172] Re: Find a better handling of /etc/localtime symlink on Ubuntu Core

[Olivier Tilloy]

** No longer affects: firefox (Ubuntu)

** No longer affects: firefox-launchpad-plugin (Ubuntu)

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

Title:
  Find a better handling of /etc/localtime symlink on Ubuntu Core

Status in Snappy:
  New

Bug description:
  Ubuntu Core uses a symlink for `/etc/localtime` to
  `/etc/writable/localtime`. But systemd's timesyncd does not like that.
  For Ubuntu Core it has been patched, but fix is fragile. Since having
  a read-only `/etc` is not uncommon in embedded, there should be value
  in finding a proper solution which could be accepted upstream so we do
  not need to maintain patches for it.

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


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

[Desktop-packages] [Bug 1954587] Re: Thunderbird: Mail preview is cropped

[Olivier Tilloy]

This looks like it could be an upstream issue. Could you please file a
bug at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CThunderbird
and share the link to it here? Thanks!

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

Title:
  Thunderbird: Mail preview is cropped

Status in thunderbird package in Ubuntu:
  New

Bug description:
  The mail preview in Thunderbird crops away 50% of the UI (see
  screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.3.1+build1-0ubuntu0.21.10.2
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BuildID: 2022203138
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sun Dec 12 20:17:51 2021
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to impish on 2021-12-08 (4 days ago)

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


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

[Desktop-packages] [Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else

[Olivier Tilloy]

Indeed, and this appears to be a GTK bug
(https://gitlab.gnome.org/GNOME/gtk/-/issues/4340), for which a fix was
merged a week ago.

For reference, the upstream firefox bug was
https://bugzilla.mozilla.org/show_bug.cgi?id=1722369.

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4340
   https://gitlab.gnome.org/GNOME/gtk/-/issues/4340

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

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

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

** Tags added: rls-jj-incoming

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

Title:
  Copy from Firefox Wayland fails to be pasted anywhere else

Status in GTK+:
  Unknown
Status in firefox package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS,
  on Wayland native

  Version   84.0.2
  Build ID  20210105180113

  Window Protocol   wayland
  Desktop Environment   gnome

  DESCRIPTION OF THE PROBLEM:

  If I copy text from a web page and try to paste it into another
  Firefox page, the text is pasted correctly.

  If I copy text from a web page and try to paste it in [gedit,
  libreoffice, thunderbird, terminal, slack (electron)] nothing happens.
  The Gnome Clipboard extension stays empty when content is copied from
  Firefox Wayland.

  Pasting *from* another app *to* Firefox works fine.

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


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

[Desktop-packages] [Bug 1953694] Re: wayland clipboard handing locks up in certain corner cases

[Olivier Tilloy]

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

** This bug has been marked a duplicate of bug 1913775
   Copy from Firefox Wayland fails to be pasted anywhere else

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

Title:
  wayland clipboard handing locks up in certain corner cases

Status in evince package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  There are a number of cases in gtk+-3.0 3.24.30 on wayland where copy
  paste from/to various apps fails based on something related to type
  handling.

  I've run into this on Ubuntu 21.10, with multiple apps under the
  ubuntu wayland session.

  I have not found a matching bug in the Debian BTS, but there is a
  matching upstream bug and merged fix in upstream gtk+-3 from GNOME as
  of 20211206.

  References:
  https://gitlab.gnome.org/GNOME/gtk/-/issues/4340
  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4058

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


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

[Desktop-packages] [Bug 1954637] Re: package thunderbird-locale-en 1:78.14.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

[Olivier Tilloy]

Relevant output from DpkgTerminalLog.txt:

dpkg-deb: error: 
'/tmp/apt-dpkg-install-Ki3zHj/29-thunderbird-locale-en_1%3a78.14.0+build1-0ubuntu0.20.04.2_amd64.deb'
 is not a Debian format archive
dpkg: error processing archive 
/tmp/apt-dpkg-install-Ki3zHj/29-thunderbird-locale-en_1%3a78.14.0+build1-0ubuntu0.20.04.2_amd64.deb
 (--unpack):
 dpkg-deb --control subprocess returned error exit status 2

It looks like the download of the package failed and resulted in a
corrupted file. Try running:

sudo apt reinstall thunderbird thunderbird-locale-en

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

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

Title:
  package thunderbird-locale-en 1:78.14.0+build1-0ubuntu0.20.04.1 failed
  to install/upgrade: dpkg-deb --control subprocess returned error exit
  status 2

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  udo apt-get install openssh-server
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   openssh-server : Depends: openssh-sftp-server
Recommends: ncurses-term but it is not going to be installed
Recommends: ssh-import-id but it is not going to be 
installed
   thunderbird-locale-en : Depends: thunderbird (< 
1:78.14.0+build1-0ubuntu0.20.04.1.1~) but 1:78.14.0+build1-0ubuntu0.20.04.2 is 
to be installed
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: thunderbird-locale-en 1:78.14.0+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sathish1019 F pulseaudio
  BuildID: 20210901192859
  CasperMD5CheckResult: skip
  Channel: Unavailable
  Date: Mon Dec 13 14:57:39 2021
  DuplicateSignature:
   package:thunderbird-locale-en:1:78.14.0+build1-0ubuntu0.20.04.1
   Unpacking libglapi-mesa:amd64 (21.0.3-0ubuntu0.3~20.04.5) over 
(21.0.3-0ubuntu0.3~20.04.4) ...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-Ki3zHj/24-libnss3_2%3a3.49.1-1ubuntu1.6_amd64.deb' is 
not a Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-Ki3zHj/24-libnss3_2%3a3.49.1-1ubuntu1.6_amd64.deb 
(--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  ForcedLayersAccel: False
  IpRoute:
   default via 172.16.76.2 dev ens33 proto dhcp metric 100 
   169.254.0.0/16 dev ens33 scope link metric 1000 
   172.16.76.0/24 dev ens33 proto kernel scope link src 172.16.76.128 metric 100
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Title: package thunderbird-locale-en 1:78.14.0+build1-0ubuntu0.20.04.1 failed 
to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:sku:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

[Desktop-packages] [Bug 1954592] Re: gnome-control-center crashed with SIGSEGV in gdk_x11_window_get_xid()

[Sebastien Bacher]

** Information type changed from Private to Public

** Changed in: gnome-control-center (Ubuntu)
   Importance: Medium => Low

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

Title:
  gnome-control-center crashed with SIGSEGV in gdk_x11_window_get_xid()

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

Bug description:
  Gnome control center crashes during printer setup.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 12 09:05:56 2021
  ExecutablePath: /usr/bin/gnome-control-center
  ProcCmdline: gnome-control-center
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7efcb124765d :cmp
0xf8(%rdi),%rdi
   PC (0x7efcb124765d) ok
   source "0xf8(%rdi)" (0x00f8) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   gdk_x11_window_get_xid () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   pp_new_printer_dialog_get_new_printer ()
   ?? ()
   ?? ()
   ?? ()
  Title: gnome-control-center crashed with SIGSEGV in gdk_x11_window_get_xid()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported

[Bug Watch Updater]

** Changed in: python-b2sdk (Debian)
   Status: Unknown => New

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

Title:
  autopkgtest regressions with python3.10 as supported

Status in ipywidgets package in Ubuntu:
  New
Status in pygobject package in Ubuntu:
  New
Status in pytest-twisted package in Ubuntu:
  New
Status in python-b2sdk package in Ubuntu:
  New
Status in python-hypothesis package in Ubuntu:
  New
Status in python-taskflow package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in skimage package in Ubuntu:
  Invalid
Status in supysonic package in Ubuntu:
  New
Status in vorta package in Ubuntu:
  New
Status in ipywidgets package in Debian:
  New
Status in pygobject package in Debian:
  New
Status in pytest-twisted package in Debian:
  New
Status in python-b2sdk package in Debian:
  New
Status in python-hypothesis package in Debian:
  Unknown
Status in supysonic package in Debian:
  Unknown
Status in vorta package in Debian:
  Unknown

Bug description:
  This bug is for tracking the packages having autopkgtest regressions
  with python3.10 as a supported version, blocking migration of
  python3-defaults/3.9.7-4.

  All packages are in universe except pygobject and python-taskflow in
  main.

  All packages have RC bugs in Debian except python-taskflow which is
  based on a newer upstream version.

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


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

[Desktop-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported

[Graham Inggs]

skimage/s390x was OOM, added to big_packages

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

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

Title:
  autopkgtest regressions with python3.10 as supported

Status in ipywidgets package in Ubuntu:
  New
Status in pygobject package in Ubuntu:
  New
Status in pytest-twisted package in Ubuntu:
  New
Status in python-b2sdk package in Ubuntu:
  New
Status in python-hypothesis package in Ubuntu:
  New
Status in python-taskflow package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in skimage package in Ubuntu:
  Invalid
Status in supysonic package in Ubuntu:
  New
Status in vorta package in Ubuntu:
  New
Status in ipywidgets package in Debian:
  New
Status in pygobject package in Debian:
  New
Status in pytest-twisted package in Debian:
  New
Status in python-b2sdk package in Debian:
  Unknown
Status in python-hypothesis package in Debian:
  Unknown
Status in supysonic package in Debian:
  Unknown
Status in vorta package in Debian:
  Unknown

Bug description:
  This bug is for tracking the packages having autopkgtest regressions
  with python3.10 as a supported version, blocking migration of
  python3-defaults/3.9.7-4.

  All packages are in universe except pygobject and python-taskflow in
  main.

  All packages have RC bugs in Debian except python-taskflow which is
  based on a newer upstream version.

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


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

[Desktop-packages] [Bug 1954647] Re: Only one Icon at a time can be relocated

[Paul White]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1886322, so it is being marked as such.

Please look at the other bug report to see if there is any missing
information that you can provide, or to see if there is a workaround for
the bug. Additionally, any further discussion regarding the bug should
occur in the other report.

Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1886322
   Unable to move all selected files on desktop

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

Title:
  Only one Icon at a time can be relocated

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  If I select more than one icon (using ctrl) and drag to a new desktop
  location, only one icon moves.

  Version: 20.04.03

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450.2
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 13 06:33:50 2021
  InstallationDate: Installed on 2021-12-07 (5 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported

[Steve Langasek]

skimage on s390x is also regressed.

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

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

Title:
  autopkgtest regressions with python3.10 as supported

Status in ipywidgets package in Ubuntu:
  New
Status in pygobject package in Ubuntu:
  New
Status in pytest-twisted package in Ubuntu:
  New
Status in python-b2sdk package in Ubuntu:
  New
Status in python-hypothesis package in Ubuntu:
  New
Status in python-taskflow package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in skimage package in Ubuntu:
  New
Status in supysonic package in Ubuntu:
  New
Status in vorta package in Ubuntu:
  New
Status in ipywidgets package in Debian:
  New
Status in pygobject package in Debian:
  New
Status in pytest-twisted package in Debian:
  New
Status in python-b2sdk package in Debian:
  Unknown
Status in python-hypothesis package in Debian:
  Unknown
Status in supysonic package in Debian:
  Unknown
Status in vorta package in Debian:
  Unknown

Bug description:
  This bug is for tracking the packages having autopkgtest regressions
  with python3.10 as a supported version, blocking migration of
  python3-defaults/3.9.7-4.

  All packages are in universe except pygobject and python-taskflow in
  main.

  All packages have RC bugs in Debian except python-taskflow which is
  based on a newer upstream version.

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


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

[Desktop-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.

[Launchpad Bug Tracker]

This bug was fixed in the package modemmanager - 1.16.6-2~20.04.1

---
modemmanager (1.16.6-2~20.04.1) focal; urgency=medium

  * Support manual firmware upgrading for Foxconn and Quectel modems.
(LP: #1946096)

 -- Jerry Lee   Thu, 21 Oct 2021 10:29:18 +0800

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

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

Title:
  Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Focal:
  Fix Released
Status in modemmanager source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  The modem certification requires that different modem firmware is used for 
different network carrier.
  This needs the firmware upgrading capability during the modem certification 
process.

  The modem manufacture vendors (Foxconn and Quectel) provided utilities to do 
modem's firmware upgrading manually.(LP#1943774, LP#1943780)
  These utilities are verified to be working when the recent versions(> v 
1.18.2) of ModemManager are used with.

  To support manual firmware upgrading on the current Focal release which is 
using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2.
  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
  * for Foxconn T99W175
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9
    
**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154

  The firmware upgrading was verified using the patched ModemManager v 1.16.6 
with the following 2 modems:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Verify if the modem is working
  4. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  5. Using the firmware upgrading application to upgrade the modem’s firmware
  6. Verify if the modem’s firmware upgrading is successful
  7. Reboot
  8. Verify if the upgraded modem firmware is still working

  --- Regression test ---

  Verify if one USB modem are still working with these patches for PCIe
  modems.

  [Where problems could occur]

  The requested update has 2 parts:

  1. Informative
     1.1 Provide more information about modems whose drivers use WWAN subsystem 
in kernel 5.13
     1.2 Modem manufacture's private utilities can use this information to do 
modem's FW upgrading manually

  2. Changes are specific to Foxconn and Quectel modems
     2.1 Modified code are only used by Foxconn and Quectel modems during their 
FW upgrading. (matched by vendor_id and product_id)

  In current Ubuntu's certification records for modem:
  * No other modem uses WWAN subsystem in kernel 5.13
  * Modem's FW update is not supported via ModemManager ( < v1.18 )

  There is no certificated modems can do the firmware upgrading flow for the 
regression test.
  This update should not affect existing modems.

  The problem would be limited to these two mentioned modems.
  Each carrier mapping .conf file is for a specific modem.
  ModemManager will load one of the carrier mapping conf files via the modem 
manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.)
  We cannot verify if the carrier mapping is correct. This relies on the 
manufacturer to provide the correct mapping.

  The carrier mapping .conf files is verified by modem’s manufacture according 
to the tested SIM card published by different countries.
  Modem manufacturer confirmed that the content in the .conf file is absolutely 
correct.

  [Other Info]

  The firmware and the upgrading utilities can be downloaded from the following 
link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

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


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

[Desktop-packages] [Bug 1639531] Re: GCC compiles programs to shared object instead of executable, preventing GUI file managers from executing programs

[Chai T. Rex]

The problem is not that it's impossible to work around the incorrect
default. The problem is the incorrect default itself.

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

Title:
  GCC compiles programs to shared object instead of executable,
  preventing GUI file managers from executing programs

Status in gcc-defaults:
  Unknown
Status in shared-mime-info:
  Unknown
Status in shared-mime-info package in Ubuntu:
  Triaged

Bug description:
  Release of Ubuntu being used
  

  Description:Ubuntu 16.10
  Release:16.10

  Version of the package being used
  =

  gcc:
    Installed: 4:6.1.1-1ubuntu2
    Candidate: 4:6.1.1-1ubuntu2
    Version table:
   *** 4:6.1.1-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  What was expected
  =

  Programs compiled using `gcc -o program program.c` should be runnable
  by double-clicking them from a GUI file manager.

  Compiling a simple program (`void main() { }`) using Xubuntu 16.04's
  current version of `gcc` (`gcc version 5.4.0 20160609 (Ubuntu
  5.4.0-6ubuntu1~16.04.2)`) produces the following output from
  `/usr/bin/file program`:

  program: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
  dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
  GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped

  This is correct behavior, allowing the executables to run from
  Nautilus and Thunar.

  What happened instead
  =

  Programs compiled using `gcc -o program program.c` are not runnable by
  double-clicking them from a GUI file manager, even though they are
  runnable from the terminal.

  Compiling a simple program (`void main() { }`) using the current
  version of `gcc` (`6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)`) produces
  the following output from `/usr/bin/file program`:

  program: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
  dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
  GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped

  The program is also identified as a "shared library" instead of an
  "executable" in Thunar, causing it to not be runnable from the GUI.
  Others are unable to run such programs from Nautilus.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-defaults/+bug/1639531/+subscriptions


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

[Desktop-packages] [Bug 1946096] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for modemmanager has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Focal:
  Fix Released
Status in modemmanager source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  The modem certification requires that different modem firmware is used for 
different network carrier.
  This needs the firmware upgrading capability during the modem certification 
process.

  The modem manufacture vendors (Foxconn and Quectel) provided utilities to do 
modem's firmware upgrading manually.(LP#1943774, LP#1943780)
  These utilities are verified to be working when the recent versions(> v 
1.18.2) of ModemManager are used with.

  To support manual firmware upgrading on the current Focal release which is 
using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2.
  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
  * for Foxconn T99W175
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9
    
**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154

  The firmware upgrading was verified using the patched ModemManager v 1.16.6 
with the following 2 modems:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Verify if the modem is working
  4. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  5. Using the firmware upgrading application to upgrade the modem’s firmware
  6. Verify if the modem’s firmware upgrading is successful
  7. Reboot
  8. Verify if the upgraded modem firmware is still working

  --- Regression test ---

  Verify if one USB modem are still working with these patches for PCIe
  modems.

  [Where problems could occur]

  The requested update has 2 parts:

  1. Informative
     1.1 Provide more information about modems whose drivers use WWAN subsystem 
in kernel 5.13
     1.2 Modem manufacture's private utilities can use this information to do 
modem's FW upgrading manually

  2. Changes are specific to Foxconn and Quectel modems
     2.1 Modified code are only used by Foxconn and Quectel modems during their 
FW upgrading. (matched by vendor_id and product_id)

  In current Ubuntu's certification records for modem:
  * No other modem uses WWAN subsystem in kernel 5.13
  * Modem's FW update is not supported via ModemManager ( < v1.18 )

  There is no certificated modems can do the firmware upgrading flow for the 
regression test.
  This update should not affect existing modems.

  The problem would be limited to these two mentioned modems.
  Each carrier mapping .conf file is for a specific modem.
  ModemManager will load one of the carrier mapping conf files via the modem 
manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.)
  We cannot verify if the carrier mapping is correct. This relies on the 
manufacturer to provide the correct mapping.

  The carrier mapping .conf files is verified by modem’s manufacture according 
to the tested SIM card published by different countries.
  Modem manufacturer confirmed that the content in the .conf file is absolutely 
correct.

  [Other Info]

  The firmware and the upgrading utilities can be downloaded from the following 
link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

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


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

[Desktop-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.

[Launchpad Bug Tracker]

This bug was fixed in the package modemmanager - 1.16.6-2~21.04.1

---
modemmanager (1.16.6-2~21.04.1) hirsute; urgency=medium

  * Support manual firmware upgrading for Foxconn and Quectel modems.
(LP: #1946096)

 -- Jerry Lee   Thu, 21 Oct 2021 10:43:42 +0800

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

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

Title:
  Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Focal:
  Fix Released
Status in modemmanager source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  The modem certification requires that different modem firmware is used for 
different network carrier.
  This needs the firmware upgrading capability during the modem certification 
process.

  The modem manufacture vendors (Foxconn and Quectel) provided utilities to do 
modem's firmware upgrading manually.(LP#1943774, LP#1943780)
  These utilities are verified to be working when the recent versions(> v 
1.18.2) of ModemManager are used with.

  To support manual firmware upgrading on the current Focal release which is 
using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2.
  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
  * for Foxconn T99W175
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9
    
**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154

  The firmware upgrading was verified using the patched ModemManager v 1.16.6 
with the following 2 modems:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Verify if the modem is working
  4. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  5. Using the firmware upgrading application to upgrade the modem’s firmware
  6. Verify if the modem’s firmware upgrading is successful
  7. Reboot
  8. Verify if the upgraded modem firmware is still working

  --- Regression test ---

  Verify if one USB modem are still working with these patches for PCIe
  modems.

  [Where problems could occur]

  The requested update has 2 parts:

  1. Informative
     1.1 Provide more information about modems whose drivers use WWAN subsystem 
in kernel 5.13
     1.2 Modem manufacture's private utilities can use this information to do 
modem's FW upgrading manually

  2. Changes are specific to Foxconn and Quectel modems
     2.1 Modified code are only used by Foxconn and Quectel modems during their 
FW upgrading. (matched by vendor_id and product_id)

  In current Ubuntu's certification records for modem:
  * No other modem uses WWAN subsystem in kernel 5.13
  * Modem's FW update is not supported via ModemManager ( < v1.18 )

  There is no certificated modems can do the firmware upgrading flow for the 
regression test.
  This update should not affect existing modems.

  The problem would be limited to these two mentioned modems.
  Each carrier mapping .conf file is for a specific modem.
  ModemManager will load one of the carrier mapping conf files via the modem 
manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.)
  We cannot verify if the carrier mapping is correct. This relies on the 
manufacturer to provide the correct mapping.

  The carrier mapping .conf files is verified by modem’s manufacture according 
to the tested SIM card published by different countries.
  Modem manufacturer confirmed that the content in the .conf file is absolutely 
correct.

  [Other Info]

  The firmware and the upgrading utilities can be downloaded from the following 
link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

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


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

[Desktop-packages] [Bug 1954675] [NEW] gnome-screenshot produced a blank white image

[harsh]

Public bug reported:

It happened once, thought I'd report it. This is what showed up in the
terminal (I used the command "gnome-screenshot --interactive")

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on _pixman_log_error to debug


(gnome-screenshot:45182): Gtk-WARNING **: 
20:44:44.438: Drawing a gadget with negative 
dimensions. Did you forget to allocate a size? (node border owner 
GtkAspectFrame)

(gnome-screenshot:45182): Gdk-CRITICAL **: 20:44:44.438:
gdk_cairo_surface_create_from_pixbuf: assertion GDK_IS_PIXBUF
(pixbuf) failed

(gnome-screenshot:45182): Gtk-CRITICAL **: 20:44:44.438: gtk_css_style_render_icon_surface:
assertion surface != NULL failed

(gnome-screenshot:45182): Gtk-WARNING **: 20:44:44.470: Drawing a gadget with negative
dimensions. Did you forget to allocate a size? (node border owner
GtkAspectFrame)

(gnome-screenshot:45182): Gdk-CRITICAL **: 20:44:44.470:
gdk_cairo_surface_create_from_pixbuf: assertion GDK_IS_PIXBUF
(pixbuf) failed

(gnome-screenshot:45182): Gtk-CRITICAL **: 20:44:44.470: gtk_css_style_render_icon_surface:
assertion surface != NULL failed

(gnome-screenshot:45182): Gtk-WARNING **: 20:44:44.667: Drawing a gadget with negative
dimensions. Did you forget to allocate a size? (node border owner
GtkAspectFrame)

(gnome-screenshot:45182): Gdk-CRITICAL **: 20:44:44.667:
gdk_cairo_surface_create_from_pixbuf: assertion GDK_IS_PIXBUF
(pixbuf) failed

(gnome-screenshot:45182): Gtk-CRITICAL **: 20:44:44.667: gtk_css_style_render_icon_surface:
assertion surface != NULL failed

(gnome-screenshot:45182): Gtk-WARNING **: 20:44:47.512: Drawing a gadget with negative
dimensions. Did you forget to allocate a size? (node border owner
GtkAspectFrame)

(gnome-screenshot:45182): Gdk-CRITICAL **: 20:44:47.512:
gdk_cairo_surface_create_from_pixbuf: assertion GDK_IS_PIXBUF
(pixbuf) failed

(gnome-screenshot:45182): Gtk-CRITICAL **: 20:44:47.512: gtk_css_style_render_icon_surface:
assertion surface != NULL failed

(gnome-screenshot:45182): Gtk-WARNING **: 20:44:47.536: Drawing a gadget with negative
dimensions. Did you forget to allocate a size? (node border owner
GtkAspectFrame)

(gnome-screenshot:45182): Gdk-CRITICAL **: 20:44:47.536:
gdk_cairo_surface_create_from_pixbuf: assertion GDK_IS_PIXBUF
(pixbuf) failed

(gnome-screenshot:45182): Gtk-CRITICAL **: 20:44:47.537: gtk_css_style_render_icon_surface:
assertion surface != NULL failed

(gnome-screenshot:45182): Gtk-WARNING **: 20:44:47.552: Drawing a gadget with negative
dimensions. Did you forget to allocate a size? (node border owner
GtkAspectFrame)

(gnome-screenshot:45182): Gdk-CRITICAL **: 20:44:47.552:
gdk_cairo_surface_create_from_pixbuf: assertion GDK_IS_PIXBUF
(pixbuf) failed

(gnome-screenshot:45182): Gtk-CRITICAL **: 20:44:47.553: gtk_css_style_render_icon_surface:
assertion surface != NULL failed

(gnome-screenshot:45182): Gtk-WARNING **: 20:44:47.568: Drawing a gadget with negative
dimensions. Did you forget to allocate a size? (node border owner
GtkAspectFrame)

(gnome-screenshot:45182): Gdk-CRITICAL **: 20:44:47.568:
gdk_cairo_surface_create_from_pixbuf: assertion GDK_IS_PIXBUF
(pixbuf) failed

(gnome-screenshot:45182): Gtk-CRITICAL **: 20:44:47.568: gtk_css_style_render_icon_surface:
assertion surface != NULL failed

(gnome-screenshot:45182): Gtk-WARNING **: 20:44:47.583: Drawing a gadget with negative
dimensions. Did you forget to allocate a size? (node border owner
GtkAspectFrame)

(gnome-screenshot:45182): Gdk-CRITICAL **: 20:44:47.583:
gdk_cairo_surface_create_from_pixbuf: assertion GDK_IS_PIXBUF
(pixbuf) failed

(gnome-screenshot:45182): Gtk-CRITICAL **: 20:44:47.583: gtk_css_style_render_icon_surface:
assertion surface != NULL failed

(gnome-screenshot:45182): Gtk-WARNING **: 20:44:47.600: Drawing a gadget with negative
dimensions. Did you forget to allocate a size? (node border owner
GtkAspectFrame)

(gnome-screenshot:45182): Gdk-CRITICAL **: 20:44:47.600:
gdk_cairo_surface_create_from_pixbuf: assertion GDK_IS_PIXBUF
(pixbuf) failed

(gnome-screenshot:45182): Gtk-CRITICAL **: 20:44:47.600: gtk_css_style_render_icon_surface:
assertion surface != NULL failed

(gnome-screenshot:45182): Gtk-WARNING **: 20:44:47.616: Drawing a gadget with negative
dimensions. Did you forget to allocate a size? (node border owner
GtkAspectFrame)

(gnome-screenshot:45182): Gdk-CRITICAL **: 20:44:47.616:
gdk_cairo_surface_create_from_pixbuf: assertion GDK_IS_PIXBUF
(pixbuf) failed

(gnome-screenshot:45182): Gtk-CRITICAL **: 20:44:47.616: gtk_css_style_render_icon_surface:
assertion surface != NULL failed

(gnome-screenshot:45182): Gtk-WARNING **: 20:44:47.634: Drawing a gadget with negative
dimensions. Did you forget to allocate a size? (node border owner
GtkAspectFrame)

(gnome-screenshot:45182): Gdk-CRITICAL **: 20:44:47.634:
gdk_cairo_surface_create_from_pixbuf: assertion GDK_IS_PIXBUF
(pixbuf) failed

(gnome-screenshot:45182): Gtk-CRITICAL **: 20:44:47.634: gtk_css_style_render_icon_surface:

[Desktop-packages] [Bug 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken

[Treviño]

** Tags added: fixed-upstream

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

Title:
  Click actions "previews" and "minimize-or-previews" are broken

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

Bug description:
  Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or-
  previews" options no longer work as expected.

  For "previews":
  No previews are shown when clicking on the app icon.

  For "minimize-or-previews":
  When multiple windows of the same application are open and I click on the app 
icon, no previews are shown anymore.

  
  Schema: org.gnome.shell.extensions.dash-to-dock
  Name: click-action
  Value: "minimize-or-previews"
  Value: "previews"

  
  Description:  Ubuntu 21.10
  Release:  21.10

  gnome-shell-extension-ubuntu-dock:
Installed: 70~ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 11:32:51 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-21 (1090 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago)

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


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

[Desktop-packages] [Bug 1916469] Re: Apps don't use Wayland by default

[Andrea]

I disagree with #21. Ubuntu should disable WAYLAND for thunderbird until
it is ready to be used.

The problem has existed for a log time and nobody seems to "own" it
(Ubuntu? Gnome? Thunderbird?), redirecting users to some other bug
report, and nothing changes.

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

Title:
  Apps don't use Wayland by default

Status in firefox package in Ubuntu:
  Fix Released
Status in qdirstat package in Ubuntu:
  Confirmed
Status in telegram-desktop package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu universe has a big Wayland problem!

  What does that mean?

  So a lot of packages in the Universe repository are not compiled with
  Wayland support which is really bad and would lead to bad performance
  after 21.04 comes out.

  Here are the following packages that I detected with wrong
  compilation:

  telegram-desktop (Wayland support work with snap version)
  kiwix
  firefox (everything works fine with this env variable 
set:"MOZ_ENABLE_WAYLAND=1")

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


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

[Desktop-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported

[Bug Watch Updater]

** Changed in: ipywidgets (Debian)
   Status: Unknown => New

** Changed in: pygobject (Debian)
   Status: Unknown => New

** Changed in: pytest-twisted (Debian)
   Status: Unknown => New

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

Title:
  autopkgtest regressions with python3.10 as supported

Status in ipywidgets package in Ubuntu:
  New
Status in pygobject package in Ubuntu:
  New
Status in pytest-twisted package in Ubuntu:
  New
Status in python-b2sdk package in Ubuntu:
  New
Status in python-hypothesis package in Ubuntu:
  New
Status in python-taskflow package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in supysonic package in Ubuntu:
  New
Status in vorta package in Ubuntu:
  New
Status in ipywidgets package in Debian:
  New
Status in pygobject package in Debian:
  New
Status in pytest-twisted package in Debian:
  New
Status in python-b2sdk package in Debian:
  Unknown
Status in python-hypothesis package in Debian:
  Unknown
Status in supysonic package in Debian:
  Unknown
Status in vorta package in Debian:
  Unknown

Bug description:
  This bug is for tracking the packages having autopkgtest regressions
  with python3.10 as a supported version, blocking migration of
  python3-defaults/3.9.7-4.

  All packages are in universe except pygobject and python-taskflow in
  main.

  All packages have RC bugs in Debian except python-taskflow which is
  based on a newer upstream version.

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


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

[Desktop-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported

[Graham Inggs]

** Description changed:

  This bug is for tracking the packages having autopkgtest regressions
  with python3.10 as a supported version, blocking migration of
  python3-defaults/3.9.7-4.
+ 
+ All packages are in universe except pygobject and python-taskflow in
+ main.
+ 
+ All packages have RC bugs in Debian except python-taskflow which is
+ based on a newer upstream version.

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

Title:
  autopkgtest regressions with python3.10 as supported

Status in ipywidgets package in Ubuntu:
  New
Status in pygobject package in Ubuntu:
  New
Status in pytest-twisted package in Ubuntu:
  New
Status in python-b2sdk package in Ubuntu:
  New
Status in python-hypothesis package in Ubuntu:
  New
Status in python-taskflow package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in supysonic package in Ubuntu:
  New
Status in vorta package in Ubuntu:
  New
Status in ipywidgets package in Debian:
  Unknown
Status in pygobject package in Debian:
  Unknown
Status in pytest-twisted package in Debian:
  Unknown
Status in python-b2sdk package in Debian:
  Unknown
Status in python-hypothesis package in Debian:
  Unknown
Status in supysonic package in Debian:
  Unknown
Status in vorta package in Debian:
  Unknown

Bug description:
  This bug is for tracking the packages having autopkgtest regressions
  with python3.10 as a supported version, blocking migration of
  python3-defaults/3.9.7-4.

  All packages are in universe except pygobject and python-taskflow in
  main.

  All packages have RC bugs in Debian except python-taskflow which is
  based on a newer upstream version.

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


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

[Desktop-packages] [Bug 1954649] [NEW] autopkgtest regressions with python3.10 as supported

[Graham Inggs]

Public bug reported:

This bug is for tracking the packages having autopkgtest regressions
with python3.10 as a supported version, blocking migration of
python3-defaults/3.9.7-4.

All packages are in universe except pygobject and python-taskflow in
main.

All packages have RC bugs in Debian except python-taskflow which is
based on a newer upstream version.

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

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

** Affects: pytest-twisted (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: python-b2sdk (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: python-hypothesis (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: python-taskflow (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Affects: ipywidgets (Debian)
 Importance: Unknown
 Status: Unknown

** Affects: pygobject (Debian)
 Importance: Unknown
 Status: Unknown

** Affects: pytest-twisted (Debian)
 Importance: Unknown
 Status: Unknown

** Affects: python-b2sdk (Debian)
 Importance: Unknown
 Status: Unknown

** Affects: python-hypothesis (Debian)
 Importance: Unknown
 Status: Unknown

** Affects: supysonic (Debian)
 Importance: Unknown
 Status: Unknown

** Affects: vorta (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: update-excuse

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

** Also affects: python3-defaults (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: pytest-twisted (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: python-b2sdk (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: python-hypothesis (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Bug watch added: Debian Bug tracker #1001343
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001343

** Also affects: ipywidgets (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001343
   Importance: Unknown
   Status: Unknown

** Bug watch added: Debian Bug tracker #1001368
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001368

** Also affects: pygobject (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001368
   Importance: Unknown
   Status: Unknown

** Bug watch added: Debian Bug tracker #1001371
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001371

** Also affects: pytest-twisted (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001371
   Importance: Unknown
   Status: Unknown

** Bug watch added: Debian Bug tracker #1001393
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001393

** Also affects: python-b2sdk (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001393
   Importance: Unknown
   Status: Unknown

** Bug watch added: Debian Bug tracker #1001538
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001538

** Also affects: python-hypothesis (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001538
   Importance: Unknown
   Status: Unknown

** Bug watch added: Debian Bug tracker #1000717
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000717

** Also affects: supysonic (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000717
   Importance: Unknown
   Status: Unknown

** Bug watch added: Debian Bug tracker #1001490
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001490

** Also affects: vorta (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001490
   Importance: Unknown
   Status: Unknown

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

Title:
  autopkgtest regressions with python3.10 as supported

Status in ipywidgets package in Ubuntu:
  New
Status in pygobject package in Ubuntu:
  New
Status in pytest-twisted package in Ubuntu:
  New
Status in python-b2sdk package in Ubuntu:
  New
Status in python-hypothesis package in Ubuntu:
  New
Status in python-taskflow package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in supysonic package in Ubuntu:
  New
Status in vorta package in Ubuntu:
  New
Status in ipywidgets package in Debian:
  Unknown
Status in pygobject package in Debian:
  Unknown
Status in pytest-twisted 

[Desktop-packages] [Bug 1954647] [NEW] Only one Icon at a time can be relocated

[Michael Lentz]

Public bug reported:

If I select more than one icon (using ctrl) and drag to a new desktop
location, only one icon moves.

Version: 20.04.03

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-desktop 1.450.2
ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 13 06:33:50 2021
InstallationDate: Installed on 2021-12-07 (5 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Only one Icon at a time can be relocated

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  If I select more than one icon (using ctrl) and drag to a new desktop
  location, only one icon moves.

  Version: 20.04.03

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450.2
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 13 06:33:50 2021
  InstallationDate: Installed on 2021-12-07 (5 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1954637] [NEW] package thunderbird-locale-en 1:78.14.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

[sathish]

Public bug reported:

udo apt-get install openssh-server
Reading package lists... Done
Building dependency tree   
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 openssh-server : Depends: openssh-sftp-server
  Recommends: ncurses-term but it is not going to be installed
  Recommends: ssh-import-id but it is not going to be installed
 thunderbird-locale-en : Depends: thunderbird (< 
1:78.14.0+build1-0ubuntu0.20.04.1.1~) but 1:78.14.0+build1-0ubuntu0.20.04.2 is 
to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: thunderbird-locale-en 1:78.14.0+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-41-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sathish1019 F pulseaudio
BuildID: 20210901192859
CasperMD5CheckResult: skip
Channel: Unavailable
Date: Mon Dec 13 14:57:39 2021
DuplicateSignature:
 package:thunderbird-locale-en:1:78.14.0+build1-0ubuntu0.20.04.1
 Unpacking libglapi-mesa:amd64 (21.0.3-0ubuntu0.3~20.04.5) over 
(21.0.3-0ubuntu0.3~20.04.4) ...
 dpkg-deb: error: 
'/tmp/apt-dpkg-install-Ki3zHj/24-libnss3_2%3a3.49.1-1ubuntu1.6_amd64.deb' is 
not a Debian format archive
 dpkg: error processing archive 
/tmp/apt-dpkg-install-Ki3zHj/24-libnss3_2%3a3.49.1-1ubuntu1.6_amd64.deb 
(--unpack):
  dpkg-deb --control subprocess returned error exit status 2
ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
ForcedLayersAccel: False
IpRoute:
 default via 172.16.76.2 dev ens33 proto dhcp metric 100 
 169.254.0.0/16 dev ens33 scope link metric 1000 
 172.16.76.0/24 dev ens33 proto kernel scope link src 172.16.76.128 metric 100
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Title: package thunderbird-locale-en 1:78.14.0+build1-0ubuntu0.20.04.1 failed 
to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/12/2020
dmi.bios.release: 4.6
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 0.0
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:sku:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


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

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

Title:
  package thunderbird-locale-en 1:78.14.0+build1-0ubuntu0.20.04.1 failed
  to install/upgrade: dpkg-deb --control subprocess returned error exit
  status 2

Status in thunderbird package in Ubuntu:
  New

Bug description:
  udo apt-get install openssh-server
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   openssh-server : Depends: openssh-sftp-server
Recommends: ncurses-term but it is not going to be installed
Recommends: ssh-import-id but it is not going to be 
installed
   thunderbird-locale-en : Depends: thunderbird (< 
1:78.14.0+build1-0ubuntu0.20.04.1.1~) but 1:78.14.0+build1-0ubuntu0.20.04.2 is 
to be installed
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: thunderbird-locale-en 1:78.14.0+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sathish1019 F pulseaudio
  BuildID: 

[Desktop-packages] [Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else

[Kain]

I believe this is the same as this wayland/gtk+-3 bug:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1953694

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

Title:
  Copy from Firefox Wayland fails to be pasted anywhere else

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS,
  on Wayland native

  Version   84.0.2
  Build ID  20210105180113

  Window Protocol   wayland
  Desktop Environment   gnome

  DESCRIPTION OF THE PROBLEM:

  If I copy text from a web page and try to paste it into another
  Firefox page, the text is pasted correctly.

  If I copy text from a web page and try to paste it in [gedit,
  libreoffice, thunderbird, terminal, slack (electron)] nothing happens.
  The Gnome Clipboard extension stays empty when content is copied from
  Firefox Wayland.

  Pasting *from* another app *to* Firefox works fine.

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


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

[Desktop-packages] [Bug 1953694] Re: wayland clipboard handing locks up in certain corner cases

[Kain]

My first search was a miss, I think this is the bug referred to here:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1913775

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

Title:
  wayland clipboard handing locks up in certain corner cases

Status in evince package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  There are a number of cases in gtk+-3.0 3.24.30 on wayland where copy
  paste from/to various apps fails based on something related to type
  handling.

  I've run into this on Ubuntu 21.10, with multiple apps under the
  ubuntu wayland session.

  I have not found a matching bug in the Debian BTS, but there is a
  matching upstream bug and merged fix in upstream gtk+-3 from GNOME as
  of 20211206.

  References:
  https://gitlab.gnome.org/GNOME/gtk/-/issues/4340
  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4058

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


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

[Desktop-packages] [Bug 1954628] [NEW] [USB-Audio - USB Audio, playback] Headphone output mapped incorrectly

[Gijs Peskens]

Public bug reported:

I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard
'Starship/Matisse HD Audio Controller' controller that has a weird
mapping via USB audio (see bug:
https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar
configuration).

Sound via line-out works fine without any interventions.

Headphone output however does not, while Ubuntu correctly detects the
headphones as being plugged in when selected sound is still output via
line-out, instead of via the front panel headphone jack-out.

After some debugging I figured the headphones are connected to a seperate Alsa 
device on the same card as the line-out. 
Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working 
audio output that plays just via the headphone out. 

I guess a quirk needs to be written for the configuration.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Uname: Linux 5.13.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  gijs   2129 F pulseaudio
 /dev/snd/pcmC2D1p:   gijs   2129 F...m pulseaudio
 /dev/snd/controlC0:  gijs   2129 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 13 09:28:19 2021
InstallationDate: Installed on 2020-12-06 (371 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful
Symptom_Card: USB Audio - USB Audio
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Only some of outputs are working
Title: [USB-Audio - USB Audio, playback] Playback problem
UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago)
dmi.bios.date: 07/09/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.00
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7D54
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

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

Title:
  [USB-Audio - USB Audio, playback] Headphone output mapped incorrectly

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard
  'Starship/Matisse HD Audio Controller' controller that has a weird
  mapping via USB audio (see bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar
  configuration).

  Sound via line-out works fine without any interventions.

  Headphone output however does not, while Ubuntu correctly detects the
  headphones as being plugged in when selected sound is still output via
  line-out, instead of via the front panel headphone jack-out.

  After some debugging I figured the headphones are connected to a seperate 
Alsa device on the same card as the line-out. 
  Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working 
audio output that plays just via the headphone out. 

  I guess a quirk needs to be written for the configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gijs   2129 F pulseaudio
   /dev/snd/pcmC2D1p:   gijs   2129 F...m pulseaudio
   /dev/snd/controlC0:  gijs   2129 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 13 09:28:19 2021
  InstallationDate: Installed on 2020-12-06 (371 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful
  Symptom_Card: