[Desktop-packages] [Bug 1946733] Re: gnome-terminal max_size and resize looses 1 row and 1 colomn

[Bernhard Riegler]

I assume an "integer division" cut down
my HW monitor has a screen resolution of 1920 x 1200 pixel.

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

Title:
  gnome-terminal max_size and resize looses 1 row and 1 colomn

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I installed "xterm" to get utility "resize" and have a comparison between 2 
terminal programs.
  xterm works. between the "resize" commands is double click on top bar 
(max.size, restore)
  bernie@prod:~$ resize
  COLUMNS=80;
  LINES=24;
  export COLUMNS LINES;
  bernie@prod:~$ resize
  COLUMNS=80;
  LINES=24;
  export COLUMNS LINES;
  bernie@prod:~$ resize
  COLUMNS=80;
  LINES=24;
  export COLUMNS LINES;
   stable columns,lines with xterm
  gnome-terminal has a bug. again (max.size, restore) with double-click on top 
bar.
  bernie@prod:~$ resize
  COLUMNS=80;
  LINES=24;
  export COLUMNS LINES;
  bernie@prod:~$ resize
  COLUMNS=79;
  LINES=23;
  export COLUMNS LINES;
  bernie@prod:~$ resize
  COLUMNS=78;
  LINES=22;
  export COLUMNS LINES;
  with every cycle the gnome-terminal looses 1 row and 1 column
  gnome-terminal info reports version 3.36.2
  platform is ubuntu 20.04 LTS
  bernie@prod:~$ lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  bernie@prod:~$ apt-cache policy gnome-terminal
  gnome-terminal:
Installiert:   3.36.2-1ubuntu1~20.04
Installationskandidat: 3.36.2-1ubuntu1~20.04
Versionstabelle:
   *** 3.36.2-1ubuntu1~20.04 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.1.1-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  please fix the gnome-terminal size shrinking and restore the same size as 
before
  thanks

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


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

[Desktop-packages] [Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume

[Hui Wang]

This is the debdiff for focal.

thx.


** Patch added: "pulseaudio_13.99.1-1ubuntu3.13.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1951667/+attachment/5542199/+files/pulseaudio_13.99.1-1ubuntu3.13.debdiff

** Tags added: oem-priority originate-from-1946429 somerville

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

Title:
  [SRU] pulseaudio: restore hdmi audio be active output after resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Hirsute:
  In Progress
Status in pulseaudio source package in Impish:
  In Progress
Status in pulseaudio source package in Jammy:
  In Progress

Bug description:
  [Impact]
  On the machines with legacy HDA audio driver, when users plug a hdmi/dp 
monitor, the active output device is still speaker, need users to manually 
select the hdmi, then the hdmi audio will be the users' preference, once it is 
plugged, it should become the active output automatically. But with the current 
PA, after reboot and suspend/resume, the hdmi can't change to be active output 
automatically anymore.

  [Fix]
  Backport an upstream fix, this will fix the issue of "preferred ports being 
cleaned by a mistake"

  [Test]
  On a machine with legacy HDA audio driver, install the patched pulseaudio, 
then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi 
audio to be active, with the hdmi monitor plugged and reboot, suspend and 
resume, check what is the active output, it is still the hdmi audio.

  [Where problems could occur]
  This patch is in the card-restore.c, if it could introduce regression, it 
will be on the default active input/output devices, for example, users select a 
input or output device to be active, after reboot, if those devices are 
available, they should be active, but they could be replaced by other devices 
if a regression is introduced. But this possibility is very low since we tested 
the patch on a couple of desktop and laptop machines.

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


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

[Desktop-packages] [Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume

[Hui Wang]

This is the debdiff for impish.

thx.


** Patch added: "pulseaudio_15.0+dfsg1-1ubuntu2.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1951667/+attachment/5542197/+files/pulseaudio_15.0+dfsg1-1ubuntu2.2.debdiff

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

Title:
  [SRU] pulseaudio: restore hdmi audio be active output after resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Hirsute:
  In Progress
Status in pulseaudio source package in Impish:
  In Progress
Status in pulseaudio source package in Jammy:
  In Progress

Bug description:
  [Impact]
  On the machines with legacy HDA audio driver, when users plug a hdmi/dp 
monitor, the active output device is still speaker, need users to manually 
select the hdmi, then the hdmi audio will be the users' preference, once it is 
plugged, it should become the active output automatically. But with the current 
PA, after reboot and suspend/resume, the hdmi can't change to be active output 
automatically anymore.

  [Fix]
  Backport an upstream fix, this will fix the issue of "preferred ports being 
cleaned by a mistake"

  [Test]
  On a machine with legacy HDA audio driver, install the patched pulseaudio, 
then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi 
audio to be active, with the hdmi monitor plugged and reboot, suspend and 
resume, check what is the active output, it is still the hdmi audio.

  [Where problems could occur]
  This patch is in the card-restore.c, if it could introduce regression, it 
will be on the default active input/output devices, for example, users select a 
input or output device to be active, after reboot, if those devices are 
available, they should be active, but they could be replaced by other devices 
if a regression is introduced. But this possibility is very low since we tested 
the patch on a couple of desktop and laptop machines.

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


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

[Desktop-packages] [Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume

[Hui Wang]

This is the debdiff for hirsute.

thx.


** Patch added: "pulseaudio_14.2-1ubuntu1.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1951667/+attachment/5542198/+files/pulseaudio_14.2-1ubuntu1.3.debdiff

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

Title:
  [SRU] pulseaudio: restore hdmi audio be active output after resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Hirsute:
  In Progress
Status in pulseaudio source package in Impish:
  In Progress
Status in pulseaudio source package in Jammy:
  In Progress

Bug description:
  [Impact]
  On the machines with legacy HDA audio driver, when users plug a hdmi/dp 
monitor, the active output device is still speaker, need users to manually 
select the hdmi, then the hdmi audio will be the users' preference, once it is 
plugged, it should become the active output automatically. But with the current 
PA, after reboot and suspend/resume, the hdmi can't change to be active output 
automatically anymore.

  [Fix]
  Backport an upstream fix, this will fix the issue of "preferred ports being 
cleaned by a mistake"

  [Test]
  On a machine with legacy HDA audio driver, install the patched pulseaudio, 
then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi 
audio to be active, with the hdmi monitor plugged and reboot, suspend and 
resume, check what is the active output, it is still the hdmi audio.

  [Where problems could occur]
  This patch is in the card-restore.c, if it could introduce regression, it 
will be on the default active input/output devices, for example, users select a 
input or output device to be active, after reboot, if those devices are 
available, they should be active, but they could be replaced by other devices 
if a regression is introduced. But this possibility is very low since we tested 
the patch on a couple of desktop and laptop machines.

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


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

[Desktop-packages] [Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume

[Hui Wang]

This is the debdiff for jammy

thx.


** Description changed:

- this bug is for tracking purpose.
+ [Impact]
+ On the machines with legacy HDA audio driver, when users plug a hdmi/dp 
monitor, the active output device is still speaker, need users to manually 
select the hdmi, then the hdmi audio will be the users' preference, once it is 
plugged, it should become the active output automatically. But with the current 
PA, after reboot and suspend/resume, the hdmi can't change to be active output 
automatically anymore.
+ 
+ [Fix]
+ Backport an upstream fix, this will fix the issue of "preferred ports being 
cleaned by a mistake"
+ 
+ [Test]
+ On a machine with legacy HDA audio driver, install the patched pulseaudio, 
then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi 
audio to be active, with the hdmi monitor plugged and reboot, suspend and 
resume, check what is the active output, it is still the hdmi audio.
+ 
+ [Where problems could occur]
+ This patch is in the card-restore.c, if it could introduce regression, it 
will be on the default active input/output devices, for example, users select a 
input or output device to be active, after reboot, if those devices are 
available, they should be active, but they could be replaced by other devices 
if a regression is introduced. But this possibility is very low since we tested 
the patch on a couple of desktop and laptop machines.

** Patch added: "pulseaudio_15.0+dfsg1-1ubuntu4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1951667/+attachment/5542196/+files/pulseaudio_15.0+dfsg1-1ubuntu4.debdiff

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

Title:
  [SRU] pulseaudio: restore hdmi audio be active output after resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Hirsute:
  In Progress
Status in pulseaudio source package in Impish:
  In Progress
Status in pulseaudio source package in Jammy:
  In Progress

Bug description:
  [Impact]
  On the machines with legacy HDA audio driver, when users plug a hdmi/dp 
monitor, the active output device is still speaker, need users to manually 
select the hdmi, then the hdmi audio will be the users' preference, once it is 
plugged, it should become the active output automatically. But with the current 
PA, after reboot and suspend/resume, the hdmi can't change to be active output 
automatically anymore.

  [Fix]
  Backport an upstream fix, this will fix the issue of "preferred ports being 
cleaned by a mistake"

  [Test]
  On a machine with legacy HDA audio driver, install the patched pulseaudio, 
then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi 
audio to be active, with the hdmi monitor plugged and reboot, suspend and 
resume, check what is the active output, it is still the hdmi audio.

  [Where problems could occur]
  This patch is in the card-restore.c, if it could introduce regression, it 
will be on the default active input/output devices, for example, users select a 
input or output device to be active, after reboot, if those devices are 
available, they should be active, but they could be replaced by other devices 
if a regression is introduced. But this possibility is very low since we tested 
the patch on a couple of desktop and laptop machines.

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


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

[Desktop-packages] [Bug 1951667] [NEW] [SRU] pulseaudio: restore hdmi audio be active output after resume

[Hui Wang]

Public bug reported:

this bug is for tracking purpose.

** Affects: pulseaudio (Ubuntu)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: In Progress

** Affects: pulseaudio (Ubuntu Focal)
 Importance: High
 Status: In Progress

** Affects: pulseaudio (Ubuntu Hirsute)
 Importance: High
 Status: In Progress

** Affects: pulseaudio (Ubuntu Impish)
 Importance: High
 Status: In Progress

** Affects: pulseaudio (Ubuntu Jammy)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: In Progress

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

** Also affects: pulseaudio (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: pulseaudio (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: pulseaudio (Ubuntu Jammy)
   Importance: High
 Assignee: Hui Wang (hui.wang)
   Status: New

** Also affects: pulseaudio (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: pulseaudio (Ubuntu Focal)
   Status: New => In Progress

** Changed in: pulseaudio (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: pulseaudio (Ubuntu Impish)
   Status: New => In Progress

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

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

Title:
  [SRU] pulseaudio: restore hdmi audio be active output after resume

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Hirsute:
  In Progress
Status in pulseaudio source package in Impish:
  In Progress
Status in pulseaudio source package in Jammy:
  In Progress

Bug description:
  this bug is for tracking purpose.

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


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

[Desktop-packages] [Bug 1950912] Re: Drop-down Calendar menus unreadable in Thunderbird

[Gordon Lack]

Bug report submitted at Mozilla.

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

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

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

Title:
  Drop-down Calendar menus unreadable in Thunderbird

Status in thunderbird package in Ubuntu:
  New

Bug description:
  I'm using Thunderbird 91.2.1 in Impish with the Dark Theme.

  The drop-down menus for editing Calendar events (such as options for
  Repeat: and Reminder:) have light text on a light background, and are
  hence unreadable.

  This only started with the move to Impish.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gml44103277 F pulseaudio
  BuildID: 20211020014537
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Nov 14 18:03:28 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-08-13 (458 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IpRoute:
   default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp64s0 scope link metric 1000
   192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago)
  dmi.bios.date: 11/15/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TPCS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N151CU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N150CU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist LTD

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


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

[Desktop-packages] [Bug 342584] Re: 'open' should be a link to 'xdg-open'

[Launchpad Bug Tracker]

This bug was fixed in the package xdg-utils - 1.1.3-4.1ubuntu1

---
xdg-utils (1.1.3-4.1ubuntu1) jammy-proposed; urgency=low

  * SECURITY REGRESSION: simple-scan email functionality break
- debian/patches/CVE-2020-27748.patch: was reverted/delete in
  scripts/xdg-email.in.
  * Sync with Debian. Remaining change:
- Add debian/xdg-utils.links:
  + Symlink /usr/bin/xdg-open to /usr/bin/browse (LP: #1624022)

xdg-utils (1.1.3-4.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Simplified handling for ttyon and ttyoff, with thanks to
Nicolas Boulenguez . (closes: 981422)

xdg-utils (1.1.3-4) unstable; urgency=medium

  * Set executable bit of the "ttyon" and the "ttyoff" utilities right before
running tests, not in the "patch" target of debian/rules. This fixes
architecture independent build with "dpkg-buildpackage -A".

xdg-utils (1.1.3-3) unstable; urgency=medium

  [ Debian Janitor ]
  * Remove obsolete field Name from debian/upstream/metadata (already present
in machine-readable debian/copyright).

  [ Reuben Thomas ]
  * xdg-screensaver: fix suspending using window without a WM_NAME property
Closes: #970203, Upstream: #98.

  [ KARBOWSKI Piotr ]
  * xdg-open: Exit also on non-zero exit status from 'Exec' .desktop entry.
Upstream: !13.

  [ Nicholas Guriev ]
  * t-xdg-open.sh: Fix quoting issues. Closes: #975228, Upstream: !32.
  * xdg-open: Open terminal window in generic mode if .desktop file requires so
Closes: #964877, Upstream: #84.
  * desktop_file_to_binary: fix "unexpected operator" bug. Closes: #809877,
Upstream: #182.
  * Remove Per Olofsson from Uploaders list. Thank you for your previous work!
Closes: #847164.
  * Link to /usr/bin/open through alternatives mechanism. LP: #342584.
  * New autopkgtests with Bash and Dash.
  * Bump Standards-Version to 4.5.1, no required changes.

 -- Ken VanDine   Fri, 19 Nov 2021 20:43:54
+

** Changed in: xdg-utils (Ubuntu)
   Status: Confirmed => Fix Released

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

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

Title:
  'open' should be a link to 'xdg-open'

Status in xdg-utils package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: xdg-utils

  Currently, /bin/open is taken by the kbd package. However, I filed a
  bug on that package seeing if that symlink (to /bin/openvt) could be
  released. As it is, /usr/bin/open -> /usr/bin/xdg-open seems a much
  more logical choice.

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


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

[Desktop-packages] [Bug 1927100] Re: Slow file dialogs, open and save

[Brian Murray]

I would have used a version number of 1.44.1-1ubuntu2~ppa1 as this is
greater than 1.44.1-1ubuntu1 and less than 1.44.1-1ubuntu2.

$ dpkg --compare-versions 1.44.1-1ubuntu2~ppa1 lt 1.44.1-1ubuntu2; echo $?  
  
0

$ dpkg --compare-versions 1.44.1-1ubuntu2~ppa1 gt 1.44.1-1ubuntu1; echo $?
0

This is easy for a sponsor (me) to change though, so you don't need to
go through the effort of creating a new debdiff.

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

Title:
  Slow file dialogs, open and save

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Focal:
  Incomplete

Bug description:
  On Ubuntu Mate 20.04.

  Sometime the Open and Save dialogs in GTK applications will over 20
  seconds to display.

  I found https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 , which
  suggested this due to gvfsd-trash, and running `killall gvfsd-trash`
  which does temporary solve the problem.

  The issue is apparently fixed in gvfs 1.46.2

  Please could 1.46.2 or the fix
  https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 be backported
  to Ubuntu 20.04

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


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

[Desktop-packages] [Bug 1951653] [NEW] can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'

[Steve Langasek]

Public bug reported:

I have tried to tell netplan to let my ethernet device be managed by
NetworkManager, so that I can then configure a pppoe connection on top
of this device.

This fails with:

# nmcli c up netplan-wan
Error: Connection activation failed: No suitable device found for this 
connection (device lo not available because device is strictly unmanaged).
#

I don't know why it mentions 'lo' in that message, but the wan interface
is unmanaged (as are all devices on the system, but this one is supposed
to be managed):

# nmcli d status | grep wan
wan   ethernet  unmanaged  -- 
#

After much searching, I've figured out that this comes from
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf:

keyfile]
unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma

Even though I've told netplan to use the NM renderer for this device,
the configuration emitted by netplan is insufficient to override this.

Using the workaround from https://askubuntu.com/questions/71159/network-
manager-says-device-not-managed (sudo touch
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) doesn't
work, but if I set NetworkManager as the toplevel renderer in
/etc/netplan, /run/NetworkManager/conf.d/10-globally-managed-
devices.conf is emitted, which evidently DOES work.  But I only have one
device that I want rendered by NM, so I shouldn't have to declare NM at
the top level of the yaml with a lot of duplication in order to get this
result.

I would argue that the 10-globally-managed-devices.conf should not be
there at all.  But if it is going to be, then netplan needs to
consistently override it whenever there is any use of the NetworkManager
backend.

** Affects: netplan.io (Ubuntu)
 Importance: High
 Status: New

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

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  can't use NM for ethernet device on 20.04 LTS because it is 'strictly
  unmanaged'

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

Bug description:
  I have tried to tell netplan to let my ethernet device be managed by
  NetworkManager, so that I can then configure a pppoe connection on top
  of this device.

  This fails with:

  # nmcli c up netplan-wan
  Error: Connection activation failed: No suitable device found for this 
connection (device lo not available because device is strictly unmanaged).
  #

  I don't know why it mentions 'lo' in that message, but the wan
  interface is unmanaged (as are all devices on the system, but this one
  is supposed to be managed):

  # nmcli d status | grep wan
  wan   ethernet  unmanaged  -- 
  #

  After much searching, I've figured out that this comes from
  /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf:

  keyfile]
  unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma

  Even though I've told netplan to use the NM renderer for this device,
  the configuration emitted by netplan is insufficient to override this.

  Using the workaround from
  https://askubuntu.com/questions/71159/network-manager-says-device-not-
  managed (sudo touch /etc/NetworkManager/conf.d/10-globally-managed-
  devices.conf) doesn't work, but if I set NetworkManager as the
  toplevel renderer in /etc/netplan,
  /run/NetworkManager/conf.d/10-globally-managed-devices.conf is
  emitted, which evidently DOES work.  But I only have one device that I
  want rendered by NM, so I shouldn't have to declare NM at the top
  level of the yaml with a lot of duplication in order to get this
  result.

  I would argue that the 10-globally-managed-devices.conf should not be
  there at all.  But if it is going to be, then netplan needs to
  consistently override it whenever there is any use of the
  NetworkManager backend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1951653/+subscriptions


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

[Desktop-packages] [Bug 1927100] Re: Slow file dialogs, open and save

[buck2202]

Sure, I'll try to take care of that soon.

I was also a little unclear on what to do about the version number--I
forced something non-standard (1.44.1-1ubuntu1-test) so that it would
locally supersede the current ubuntu version but not block updates.
Should the debdiff reflect what would be the next appropriately numbered
package version? Or is that taken care of later?

Sorry for the probably-trivial question, I haven't done this before

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

Title:
  Slow file dialogs, open and save

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Focal:
  Incomplete

Bug description:
  On Ubuntu Mate 20.04.

  Sometime the Open and Save dialogs in GTK applications will over 20
  seconds to display.

  I found https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 , which
  suggested this due to gvfsd-trash, and running `killall gvfsd-trash`
  which does temporary solve the problem.

  The issue is apparently fixed in gvfs 1.46.2

  Please could 1.46.2 or the fix
  https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 be backported
  to Ubuntu 20.04

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


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

[Desktop-packages] [Bug 1883174] Re: [SRU]Some (or all) desktop icons are missing

[Brian Murray]

I've uploaded this for Focal and Hirsute.

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

Title:
  [SRU]Some (or all) desktop icons are missing

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Focal:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * When user edit and save a file in Desktop, the file icon will disappear, 
and the file is still there, it's bad experience for user.
   * Sometimes, some icons in my Desktop folder just don't appear on the 
desktop. The missing icons aren't invisible, it's like they're not in the 
folder. Clicking on the empty space where they should be does nothing. Mousing 
over the empty space does nothing. See attached screenshot. As you can see, 
there are many missing.

  Not consistently reproducible, but frequent.

  [Test Plan]

   * Edit and save a file in Desktop.
 $ echo "abc" > ~/a.log
 $ gedit ~/a.log

  [Where problems could occur]

   * It is low risk, cause I just check the fileItem in source code
  before call it, or else it prompt 'fileItem is undefined'.

  
  [Other Info]
   
  OS: Ubuntu 20.04.3
  gnome-shell: 3.36.9
  gnome-shell-extension-desktop-icons: 20.04.0-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions


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

[Desktop-packages] [Bug 1950809] Re: Budgie 22.04 installer crashed within virtualbox VM

[Norbert]

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

** This bug has been marked a duplicate of bug 1951399
   Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install

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

Title:
  Budgie 22.04 installer crashed within virtualbox VM

Status in mutter package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New

Bug description:
  Installer crashed within virtualbox VM:

  I've run an installation of Ubuntu Budgie 22.04 nightly (2022)
  within a virtualbox VM (Ubuntu Budgie 21.10 host), left the
  installation unattended for a while and after coming back found the
  installer has crashed. Then the bug report page opened automatically
  (I am writing this from within the live system).

  Not sure if this is relevant to the crash, but I've set up hard drive
  encryption within the storage configuration section.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity 21.10.10
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  Date: Fri Nov 12 19:38:41 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-budgie.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(2022)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1883174] Re: [SRU]Some (or all) desktop icons are missing

[Brian Murray]

Actually, I'll just upload this for hirsute too.

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

Title:
  [SRU]Some (or all) desktop icons are missing

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Focal:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * When user edit and save a file in Desktop, the file icon will disappear, 
and the file is still there, it's bad experience for user.
   * Sometimes, some icons in my Desktop folder just don't appear on the 
desktop. The missing icons aren't invisible, it's like they're not in the 
folder. Clicking on the empty space where they should be does nothing. Mousing 
over the empty space does nothing. See attached screenshot. As you can see, 
there are many missing.

  Not consistently reproducible, but frequent.

  [Test Plan]

   * Edit and save a file in Desktop.
 $ echo "abc" > ~/a.log
 $ gedit ~/a.log

  [Where problems could occur]

   * It is low risk, cause I just check the fileItem in source code
  before call it, or else it prompt 'fileItem is undefined'.

  
  [Other Info]
   
  OS: Ubuntu 20.04.3
  gnome-shell: 3.36.9
  gnome-shell-extension-desktop-icons: 20.04.0-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions


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

[Desktop-packages] [Bug 1883174] Re: [SRU]Some (or all) desktop icons are missing

[Brian Murray]

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal)
   Status: New => In Progress

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal)
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute)
 Assignee: (unassigned) => Bin Li (binli)

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

Title:
  [SRU]Some (or all) desktop icons are missing

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Focal:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * When user edit and save a file in Desktop, the file icon will disappear, 
and the file is still there, it's bad experience for user.
   * Sometimes, some icons in my Desktop folder just don't appear on the 
desktop. The missing icons aren't invisible, it's like they're not in the 
folder. Clicking on the empty space where they should be does nothing. Mousing 
over the empty space does nothing. See attached screenshot. As you can see, 
there are many missing.

  Not consistently reproducible, but frequent.

  [Test Plan]

   * Edit and save a file in Desktop.
 $ echo "abc" > ~/a.log
 $ gedit ~/a.log

  [Where problems could occur]

   * It is low risk, cause I just check the fileItem in source code
  before call it, or else it prompt 'fileItem is undefined'.

  
  [Other Info]
   
  OS: Ubuntu 20.04.3
  gnome-shell: 3.36.9
  gnome-shell-extension-desktop-icons: 20.04.0-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions


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

[Desktop-packages] [Bug 1883174] Re: [SRU]Some (or all) desktop icons are missing

[William Wilson]

This bug appears to also exist in hirsute. Could you prepare a debdiff
for hirsute as well?

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

Title:
  [SRU]Some (or all) desktop icons are missing

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Focal:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * When user edit and save a file in Desktop, the file icon will disappear, 
and the file is still there, it's bad experience for user.
   * Sometimes, some icons in my Desktop folder just don't appear on the 
desktop. The missing icons aren't invisible, it's like they're not in the 
folder. Clicking on the empty space where they should be does nothing. Mousing 
over the empty space does nothing. See attached screenshot. As you can see, 
there are many missing.

  Not consistently reproducible, but frequent.

  [Test Plan]

   * Edit and save a file in Desktop.
 $ echo "abc" > ~/a.log
 $ gedit ~/a.log

  [Where problems could occur]

   * It is low risk, cause I just check the fileItem in source code
  before call it, or else it prompt 'fileItem is undefined'.

  
  [Other Info]
   
  OS: Ubuntu 20.04.3
  gnome-shell: 3.36.9
  gnome-shell-extension-desktop-icons: 20.04.0-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions


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

[Desktop-packages] [Bug 1883174] Re: [SRU]Some (or all) desktop icons are missing

[Brian Murray]

** Also affects: gnome-shell-extension-desktop-icons (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell-extension-desktop-icons (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

Title:
  [SRU]Some (or all) desktop icons are missing

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Focal:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * When user edit and save a file in Desktop, the file icon will disappear, 
and the file is still there, it's bad experience for user.
   * Sometimes, some icons in my Desktop folder just don't appear on the 
desktop. The missing icons aren't invisible, it's like they're not in the 
folder. Clicking on the empty space where they should be does nothing. Mousing 
over the empty space does nothing. See attached screenshot. As you can see, 
there are many missing.

  Not consistently reproducible, but frequent.

  [Test Plan]

   * Edit and save a file in Desktop.
 $ echo "abc" > ~/a.log
 $ gedit ~/a.log

  [Where problems could occur]

   * It is low risk, cause I just check the fileItem in source code
  before call it, or else it prompt 'fileItem is undefined'.

  
  [Other Info]
   
  OS: Ubuntu 20.04.3
  gnome-shell: 3.36.9
  gnome-shell-extension-desktop-icons: 20.04.0-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions


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

[Desktop-packages] [Bug 1927100] Re: Slow file dialogs, open and save

[Brian Murray]

The debdiff here looks fine, although the debian/changelog should
reference this bug report using the syntax (LP: #1927100). Because this
fix is for a stable release of Ubuntu we need to follow the Stable
Release Update policy (https://wiki.ubuntu.com/StableReleaseUpdates).
Could you please add SRU information to the bug description? Thanks in
advance!

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

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

Title:
  Slow file dialogs, open and save

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Focal:
  Incomplete

Bug description:
  On Ubuntu Mate 20.04.

  Sometime the Open and Save dialogs in GTK applications will over 20
  seconds to display.

  I found https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 , which
  suggested this due to gvfsd-trash, and running `killall gvfsd-trash`
  which does temporary solve the problem.

  The issue is apparently fixed in gvfs 1.46.2

  Please could 1.46.2 or the fix
  https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 be backported
  to Ubuntu 20.04

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


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

[Desktop-packages] [Bug 1951646] [NEW] [snap] Firefox unable to load Security Device "p11-kit-trust.so" defined in /etc/firefox/policies/policies.json

[Marcos Simental]

Public bug reported:

Environment:
Ubuntu 21.10 with default Firefox (v93.0) snap install.

Having defined a policy in /etc/firefox/policies/policies.json with the 
following:
$ cat /etc/firefox/policies/policies.json 
{
"policies": {
"Authentication": {
"Delegated": [
"example.com"
],
"NTLM": [
"example.com"
],
"SPNEGO": [
"example.com"
],
"Locked": false
},
"Homepage": {
"URL": "https://example.com;,
"Locked": false
},
"Proxy": {
"Mode": "system",
"Passthrough": ",.example.com,
"Locked": false
},
"SecurityDevices": {
"p11-kit-trust.so for Internal certificate chain": 
"/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so"
}
}
}

I got an error when looking over about:policies:
"Unable to load security device p11-kit-trust.so"
However, all other policies are active and applied correctly (meaning that snap 
firefox can load /etc/firefox/policies/policies.json file).

After enabling debug for policies I get the following error:
Policies.jsm: 
Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure 
code: 0x80004005 (NS_ERROR_FAILURE) [nsIPKCS11ModuleDB.addModule]", result: 
2147500037, filename: "resource:///modules/policies/Policies.jsm", lineNumber: 
1995, columnNumber: 0, data: null, stack: 
"onProfileAfterChange@resource:///modules/policies/Policies.jsm:1995:20\n_runPoliciesCallbacks@resource://gre/modules/EnterprisePoliciesParent.jsm:238:9\nBG_observe@resource://gre/modules/EnterprisePoliciesParent.jsm:291:14\n",
 location: XPCWrappedNative_NoHelper }
Policies.jsm:1998


I tried to reproduce with the firefox.deb package without success, so the 
problem might be around snap.

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

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

Title:
  [snap] Firefox unable to load Security Device "p11-kit-trust.so"
  defined in /etc/firefox/policies/policies.json

Status in firefox package in Ubuntu:
  New

Bug description:
  Environment:
  Ubuntu 21.10 with default Firefox (v93.0) snap install.

  Having defined a policy in /etc/firefox/policies/policies.json with the 
following:
  $ cat /etc/firefox/policies/policies.json 
  {
  "policies": {
  "Authentication": {
  "Delegated": [
  "example.com"
  ],
  "NTLM": [
  "example.com"
  ],
  "SPNEGO": [
  "example.com"
  ],
  "Locked": false
  },
  "Homepage": {
  "URL": "https://example.com;,
  "Locked": false
  },
  "Proxy": {
  "Mode": "system",
  "Passthrough": ",.example.com,
  "Locked": false
  },
  "SecurityDevices": {
  "p11-kit-trust.so for Internal certificate chain": 
"/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so"
  }
  }
  }

  I got an error when looking over about:policies:
  "Unable to load security device p11-kit-trust.so"
  However, all other policies are active and applied correctly (meaning that 
snap firefox can load /etc/firefox/policies/policies.json file).

  After enabling debug for policies I get the following error:
  Policies.jsm: 
  Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure 
code: 0x80004005 (NS_ERROR_FAILURE) [nsIPKCS11ModuleDB.addModule]", result: 
2147500037, filename: "resource:///modules/policies/Policies.jsm", lineNumber: 
1995, columnNumber: 0, data: null, stack: 
"onProfileAfterChange@resource:///modules/policies/Policies.jsm:1995:20\n_runPoliciesCallbacks@resource://gre/modules/EnterprisePoliciesParent.jsm:238:9\nBG_observe@resource://gre/modules/EnterprisePoliciesParent.jsm:291:14\n",
 location: XPCWrappedNative_NoHelper }
  Policies.jsm:1998

  
  I tried to reproduce with the firefox.deb package without success, so the 
problem might be around snap.

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


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

[Desktop-packages] [Bug 1945741]

[Wls220spring]

(In reply to BOB from comment #33)
> I just upgraded to 91.3.1  from 91.3.0 and when composing an email I still 
> can't open an attached PDF file to confirm I am sending the correct 
> attachment. I thought I read that acknowledged bug was fixed in 91.3.1 ?
> 
> Error message is: C:\Users\BOB MAIN\Documents\BELMOON-RPT-1.PDF could not be 
> opened, because the associated helper application does not exist. Change the 
> association in your preferences.
> 
> Thank you.

Your helper application is "Preview in Thunderbird" for "Portable
Document Type (PDF)"?

That is what this bug report is about, and verified again using the
91.3.1 release on Windows 10 and Fedora Linux.

Your issue is bug 1698140.

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

Title:
  [upstream] PDF attachment opens in Firefox instead of the built-in
  viewer when opened from the compose window

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  In Thunderbird 78, you could double click on an attachment you've just
  attached when composing an email. This was very useful, so that you
  could double check that you attached the correct file. In Thunderbird
  91, this doesn't seem to work. When you double click on the
  attachment, nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.1.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   2076 F pulseaudio
  BuildID: 20210916142849
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Oct  1 08:44:34 2021
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-07-14 (443 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 172.30.3.254 dev wlp0s20f3 proto dhcp metric 600 
   10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 
   169.254.0.0/16 dev wg0 scope link metric 1000 
   172.30.0.0/22 dev wlp0s20f3 proto kernel scope link src 172.30.0.92 metric 
600
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.1.1/20210916142849 (In use)
  RebootRequiredPkgs: Error: path contained symlinks.
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to impish on 2021-09-24 (6 days ago)
  dmi.bios.date: 06/21/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET29W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET29W(1.19):bd06/21/2021:br1.19:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_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/thunderbird/+bug/1945741/+subscriptions


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

[Desktop-packages] [Bug 1945741]

[Infobob]

I just upgraded to 91.3.1  from 91.3.0 and when composing an email I
still can't open an attached PDF file to confirm I am sending the
correct attachment. I thought I read that acknowledged bug was fixed in
91.3.1 ?

Error message is: C:\Users\BOB MAIN\Documents\BELMOON-RPT-1.PDF could
not be opened, because the associated helper application does not exist.
Change the association in your preferences.

Thank you.

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

Title:
  [upstream] PDF attachment opens in Firefox instead of the built-in
  viewer when opened from the compose window

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  In Thunderbird 78, you could double click on an attachment you've just
  attached when composing an email. This was very useful, so that you
  could double check that you attached the correct file. In Thunderbird
  91, this doesn't seem to work. When you double click on the
  attachment, nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.1.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   2076 F pulseaudio
  BuildID: 20210916142849
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Oct  1 08:44:34 2021
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-07-14 (443 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 172.30.3.254 dev wlp0s20f3 proto dhcp metric 600 
   10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 
   169.254.0.0/16 dev wg0 scope link metric 1000 
   172.30.0.0/22 dev wlp0s20f3 proto kernel scope link src 172.30.0.92 metric 
600
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.1.1/20210916142849 (In use)
  RebootRequiredPkgs: Error: path contained symlinks.
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to impish on 2021-09-24 (6 days ago)
  dmi.bios.date: 06/21/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET29W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET29W(1.19):bd06/21/2021:br1.19:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_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/thunderbird/+bug/1945741/+subscriptions


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

[Desktop-packages] [Bug 1945741]

[Wls220spring]

Also verified testing the 91.3.1 rc on Windows 10.

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

Title:
  [upstream] PDF attachment opens in Firefox instead of the built-in
  viewer when opened from the compose window

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  In Thunderbird 78, you could double click on an attachment you've just
  attached when composing an email. This was very useful, so that you
  could double check that you attached the correct file. In Thunderbird
  91, this doesn't seem to work. When you double click on the
  attachment, nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.1.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   2076 F pulseaudio
  BuildID: 20210916142849
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Oct  1 08:44:34 2021
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-07-14 (443 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 172.30.3.254 dev wlp0s20f3 proto dhcp metric 600 
   10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 
   169.254.0.0/16 dev wg0 scope link metric 1000 
   172.30.0.0/22 dev wlp0s20f3 proto kernel scope link src 172.30.0.92 metric 
600
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.1.1/20210916142849 (In use)
  RebootRequiredPkgs: Error: path contained symlinks.
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to impish on 2021-09-24 (6 days ago)
  dmi.bios.date: 06/21/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET29W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET29W(1.19):bd06/21/2021:br1.19:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_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/thunderbird/+bug/1945741/+subscriptions


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

[Desktop-packages] [Bug 1733301] Re: indicator-applet-complete 1.18.0 icon scaling

[Brian Murray]

I went ahead and uploaded this for Impish after making a few changes to
the debdiff.

1) Fixed the package version number to 0.8.4-1ubuntu1
2) Fixed debian/control and XSBC-Original-Maintainer (using update-maintainer 
would have done this properly)
3) Removing unused patch tagging guideline info from that patch

This bug still needs SRU information added to the bug description for
this to be accepted by the Ubuntu SRU team. See
https://wiki.ubuntu.com/StableReleaseUpdates for details.

** Also affects: libayatana-indicator (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

Title:
  indicator-applet-complete 1.18.0 icon scaling

Status in libayatana-indicator package in Ubuntu:
  Fix Released
Status in libayatana-indicator source package in Impish:
  New

Bug description:
  System: Ubuntu MATE 17.10 64bit
  Kernel: 4.13.0-16-generic
  indicator-applet-complete: 1.18.0

  It appears that some icons on the indicator applet complete cannot scale 
well. 
  I tried this on multiple computers and fresh installations, and I can 
reproduce it 100% of the times. Icon on attached screenshot is from synology 
cloudstation drive.  

  As a side note, same icon scales well on Ubuntu 17.10 (gnome session),
  Kubuntu 17.10, and Ubuntu-Mate 16.04.

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


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

[Desktop-packages] [Bug 1733301] Re: indicator-applet-complete 1.18.0 icon scaling

[Brian Murray]

libayatana-indicator (0.8.4-2) unstable; urgency=medium

  [ Martin Wimpress ]
  * debian/patches:
+ Add 0001_scale-icons-when-loading-from-filename.patch (LP: #1733301)

  [ Mike Gabriel ]
  * debian/patches:
+ Fix file path in 0001_scale-icons-when-loading-from-filename.patch.

 -- Mike Gabriel   Tue, 19 Oct 2021 10:26:27 +0200


** Package changed: mate-indicator-applet (Ubuntu) => libayatana-indicator 
(Ubuntu)

** Changed in: libayatana-indicator (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  indicator-applet-complete 1.18.0 icon scaling

Status in libayatana-indicator package in Ubuntu:
  Fix Released

Bug description:
  System: Ubuntu MATE 17.10 64bit
  Kernel: 4.13.0-16-generic
  indicator-applet-complete: 1.18.0

  It appears that some icons on the indicator applet complete cannot scale 
well. 
  I tried this on multiple computers and fresh installations, and I can 
reproduce it 100% of the times. Icon on attached screenshot is from synology 
cloudstation drive.  

  As a side note, same icon scales well on Ubuntu 17.10 (gnome session),
  Kubuntu 17.10, and Ubuntu-Mate 16.04.

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


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

[Desktop-packages] [Bug 1733301] [NEW] indicator-applet-complete 1.18.0 icon scaling

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

System: Ubuntu MATE 17.10 64bit
Kernel: 4.13.0-16-generic
indicator-applet-complete: 1.18.0

It appears that some icons on the indicator applet complete cannot scale well. 
I tried this on multiple computers and fresh installations, and I can reproduce 
it 100% of the times. Icon on attached screenshot is from synology cloudstation 
drive.  

As a side note, same icon scales well on Ubuntu 17.10 (gnome session),
Kubuntu 17.10, and Ubuntu-Mate 16.04.

** Affects: libayatana-indicator (Ubuntu)
 Importance: Low
 Status: Confirmed


** Tags: bionic focal impish patch
-- 
indicator-applet-complete 1.18.0 icon scaling
https://bugs.launchpad.net/bugs/1733301
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libayatana-indicator in Ubuntu.

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

[Desktop-packages] [Bug 1943769] Re: Update impish to 1.10.3 microrelease

[Brian Murray]

I'm sorry we didn't get to this before the release of Impish. This would
now need to follow the Stable Release Update process
(http://wiki.ubuntu.com/StableReleaseUpdate). Would you mind filling out
the SRU template paying attention to including information about
upstream testing of microreleases?  Thanks in advance!

** Changed in: flatpak (Ubuntu)
   Status: In Progress => Fix Released

** Also affects: flatpak (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Update impish to 1.10.3 microrelease

Status in flatpak package in Ubuntu:
  Fix Released
Status in flatpak source package in Impish:
  Incomplete

Bug description:
  There is an upstream update to the 1.10 series, this allows us to drop
  all patches as they are applied upstream.

  Note we cannot sync from Debian as they have moved unstable to the
  pre-release 1.11 series temporarily.

  [Upstream changes]
  This is a maintenance update with various bug fixes backported from 1.11.x.

  Don't inherit an unusual $XDG_RUNTIME_DIR setting into the sandbox, 
fixing a regression introduced when CVE-2021-21261 was fixed in 1.8.5 and 1.10.0
  Fix various memory and file descriptor leaks, in particular with 
flatpak-spawn --env=...
  Fix fd confusion in flatpak-spawn --env=... --forward-fd=..., resolving a 
regression introduced in 1.8.5 and 1.10.0
  Fix deploys of local remotes in system-helper, possibly involving newer 
GLib versions
  Fix test failures on non-x86_64 systems
  create-usb: Skip copying extra-data flatpaks
  Improve test coverage on Debian derivatives by ensuring /sbin is in 
tests' PATH

  https://github.com/flatpak/flatpak/releases/tag/1.10.3

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


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

[Desktop-packages] [Bug 1951625] [NEW] thunderbird does not restart after minimizing (red dot left of icon)

[Jürgen Iversen]

Public bug reported:

After interrupting a Thunderbird session by minimizing (using "-" in the
top right corner) I can't reopen the minimized Thunderbird window as all
other program icons do (and Thunderbird also did until about half a year
ago!) I can not say exactly if an update caused this defect. Maybe
Ubuntu 21.04 which I installed in April 21. Ubuntu 21.10 update did not
eliminate this. Kernel updates either (now running kernel 5.14.15.)

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

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

Title:
  thunderbird does not restart after minimizing (red dot left of icon)

Status in thunderbird package in Ubuntu:
  New

Bug description:
  After interrupting a Thunderbird session by minimizing (using "-" in
  the top right corner) I can't reopen the minimized Thunderbird window
  as all other program icons do (and Thunderbird also did until about
  half a year ago!) I can not say exactly if an update caused this
  defect. Maybe Ubuntu 21.04 which I installed in April 21. Ubuntu 21.10
  update did not eliminate this. Kernel updates either (now running
  kernel 5.14.15.)

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


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

[Desktop-packages] [Bug 1851385] Re: ubuntu 19.10 / print bug : requires authentication

[Don Carlson]

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

I realize the last post here was almost two years ago, but I am new to
Ubuntu, having recently wiped my drive to completely remove Windows from
my laptop.

Funny enough, my reason for getting rid of Windows was that they kept
re-installing an update that interfered with printing to a shared
printer.  Now, with Ubuntu, I'm happy to be done with Windows and vow
never to go back...but I'm still having problems printing.

I found this post because I'm experiencing these exact symptoms, but the
suggested solution does not work.  Is anybody working on a fix?  Is
there a work-around?

I have a very stable Windows 7 desktop that is always on...connected via
USB to an old HP Laserjet IV Plus that is a workhorse.  The printer
works great locally, and until a few weeks ago it was working flawlessly
as a shared printer, as well.

When I installed Ubuntu and ran into this problem, I tried every
suggestion I was able to find on the web, but nothing works.  I continue
to see this same behavior with the "credentials required" error.

Please help

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

Title:
  ubuntu 19.10 / print bug : requires authentication

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 2 computers(one laptop and one desktop) which have a dual boot
  Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a
  USB port from my modem on which my computers are connected using Wi-
  Fi.

  Since the upgrade of Ubuntu to version 19.10, I cannot print. On both
  computers I get the same message : [The printer] requires
  authentication / credentials required in order to print.

  With Ubuntu 19.04, I had absolutely no problem. I tried with a live
  USB with Ubuntu 19.04, there is no problem, the printer works. With a
  Ubuntu live 19.10, it doesn't work.

  If I plug the printer directly on a USB port on my computer, I get the
  same error message : [The printer] requires authentication /
  credentials required in order to print.

  It's the same behaviour on both computers, no I guess it must be a
  bug. Anyway I don't know which authentication I could do, with which
  ID and password ?

  Thank you very much

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:12:07 2019
  Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: 
smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B
  MachineType: Acer Aspire V5-571
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: Aspire V5-571
  dmi.product.name: Aspire V5-571
  dmi.product.sku: Aspire V5-571_072A_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

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


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

[Desktop-packages] [Bug 1951624] [NEW] OpenSSL 3.0 transition might lead to unsupported protocols

[Simon Chopin]

Public bug reported:

OpenSSL 3.0, which is planned to land in the archive Very Soon™, has
moved quite a few algorithms to its "legacy" provider, which isn't
loaded by default. Some of those algorithms are used in various
protocols implemented by wpa_supplicant, so it's likely that the package
will be broken in this regard.

Sadly, this isn't caught by either the build-time tests nor the
autopkgtests.

A first good step would be to patch wpa_supplicant to load the "legacy"
provider (and the default one too, cf
https://www.openssl.org/docs/manmaster/man7/crypto.html , look for
"legacy").

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


** Tags: fr-1881 transition-openssl3-jj

** Tags added: fr-1881

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

Title:
  OpenSSL 3.0 transition might lead to unsupported protocols

Status in wpa package in Ubuntu:
  New

Bug description:
  OpenSSL 3.0, which is planned to land in the archive Very Soon™, has
  moved quite a few algorithms to its "legacy" provider, which isn't
  loaded by default. Some of those algorithms are used in various
  protocols implemented by wpa_supplicant, so it's likely that the
  package will be broken in this regard.

  Sadly, this isn't caught by either the build-time tests nor the
  autopkgtests.

  A first good step would be to patch wpa_supplicant to load the
  "legacy" provider (and the default one too, cf
  https://www.openssl.org/docs/manmaster/man7/crypto.html , look for
  "legacy").

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


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

[Desktop-packages] [Bug 1945770] Re: firefox: Fail to build against OpenSSL 3.0

[Olivier Tilloy]

** Changed in: firefox (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  firefox: Fail to build against OpenSSL 3.0

Status in firefox package in Ubuntu:
  New

Bug description:
  Hello,

  As part of a rebuild against OpenSSL3, this package failed to build on one or
  several architectures. You can find the details of the rebuild at 

  https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html

  or for the amd64 failed build, directly at
  
https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22098525/+files/buildlog_ubuntu-impish-amd64.firefox_92.0+build3-0ubuntu2.0~ssl3ppa1.1_BUILDING.txt.gz

  We're planning to transition to OpenSSL 3.0 for the 22.04 release, and 
consider
  this issue as blocking for this transition.

  You can find general migration informations at
  https://www.openssl.org/docs/manmaster/man7/migration_guide.html
  For your tests, you can build against libssl-dev as found in the PPA
  schopin/openssl-3.0.0

  Looking at the build failure, the problem lies in the openssl-sys crate.
  It seems the version 0.9.64 of this crate should fix the failure:
  
https://github.com/sfackler/rust-openssl/blob/master/openssl-sys/CHANGELOG.md#v0964---2021-06-18

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


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

[Desktop-packages] [Bug 1950912] Re: Drop-down Calendar menus unreadable in Thunderbird

[Olivier Tilloy]

These sound like upstream issues, really. The changelog for 91.3.2
mentions a bugfix related to the use of a dark theme, so maybe your
problem is fixed there too?

In any case, I'd suggest filing a bug at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CThunderbird, and
once you've done that, please share the link to it here.

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

Title:
  Drop-down Calendar menus unreadable in Thunderbird

Status in thunderbird package in Ubuntu:
  New

Bug description:
  I'm using Thunderbird 91.2.1 in Impish with the Dark Theme.

  The drop-down menus for editing Calendar events (such as options for
  Repeat: and Reminder:) have light text on a light background, and are
  hence unreadable.

  This only started with the move to Impish.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gml44103277 F pulseaudio
  BuildID: 20211020014537
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Nov 14 18:03:28 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-08-13 (458 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IpRoute:
   default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp64s0 scope link metric 1000
   192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago)
  dmi.bios.date: 11/15/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TPCS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N151CU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N150CU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist LTD

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


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

[Desktop-packages] [Bug 1951583] Re: bbswitch dkms build failure with 5.15 on armhf and ppc64el

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  bbswitch dkms build failure with 5.15 on armhf and ppc64el

Status in bbswitch package in Ubuntu:
  New
Status in bbswitch source package in Jammy:
  New

Bug description:
  It looks like bbswitch is using acpi_bus_get_device() on any
  architectures, but this function is not available on armhf or ppc64el:

CC [M]  /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit 
declaration of function ‘acpi_bus_get_device’; did you mean 
‘acpi_get_gpe_device’? [-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of 
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
|   ^~
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of 
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
|   ^~

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


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

[Desktop-packages] [Bug 1951571] Re: Profile menu doesn't allow you to sign in

[Olivier Tilloy]

Google revoked access to the sync functionality to anything that's not
Chrome on March 15th this year. This was discussed at length here:
https://discourse.ubuntu.com/t/future-of-chromium-in-ubuntu-with-google-
blocking-sync/20567.

Patching the UI to make this clearer is out of the packaging scope I'm
afraid. You could try suggesting this as an upstream bug
(https://bugs.chromium.org/p/chromium/issues/entry).

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Profile menu doesn't allow you to sign in

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  The profile menu in Chromium apparently has had the sign in
  functionality disabled. When clicking "Add", Chrome takes you to a
  sign in page. Chromium has you create/modify profile locally.

  I presume this is Google specific code that can't be open sourced. If
  that's the case, the UI should make it clear that the sync
  functionality isn't available in Chromium - otherwise it looks like a
  bug to anybody vaguely familiar with Chrome's sync (which after all is
  typically used once in the lifetime of a browser install).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Nov 19 04:58:01 2021
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda8  ext422G   15G  6.2G  71% /home
   tmpfs  tmpfs   16G  153M   16G   1% /dev/shm
   /dev/sda8  ext422G   15G  6.2G  71% /home
  InstallationDate: Installed on 2021-06-23 (148 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: MSI MS-7978
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=eae448fb-97c0-4bd7-bf3a-83836cf4b78a ro quiet splash vt.handoff=7
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   20   Done2021-11-18T09:37:12-06:00  2021-11-18T09:38:08-06:00  Install 
"chromium" snap
   21   Done2021-11-18T17:52:22-06:00  2021-11-18T17:53:09-06:00  
Auto-refresh snaps "chromium", "core18"
  Snap.ChromeDriverVersion: ChromeDriver 96.0.4664.45 
(76e4c1bb2ab4671b8beba3444e61c0f17584b2fc-refs/branch-heads/4664@{#947})
  Snap.ChromiumVersion:
   /home/rfirmin/Downloads was removed, reassigning DOWNLOAD to homedir
   /home/rfirmin/Documents was removed, reassigning DOCUMENTS to homedir
   Chromium 96.0.4664.45 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to impish on 2021-10-21 (28 days ago)
  dmi.bios.date: 07/04/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.E0
  dmi.board.asset.tag: Default string
  dmi.board.name: H170A GAMING PRO (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.E0:bd07/04/2018:br5.12:svnMSI:pnMS-7978:pvr1.0:rvnMSI:rnH170AGAMINGPRO(MS-7978):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7978
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


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

[Desktop-packages] [Bug 885086] Re: XDG "Desktop" item not translated on Live CD

[Brian Murray]

I'm unsubscribing the sponsors team as there seems to be an active
discussion regarding the merge proposal and that should be resolved
before anything is uploaded.

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

Title:
  XDG "Desktop" item not translated on Live CD

Status in Ubuntu Translations:
  Triaged
Status in casper package in Ubuntu:
  In Progress
Status in xdg-user-dirs package in Ubuntu:
  Opinion

Bug description:
  When I switch the language on my Oneiric Live CD, other XDG
  directories are translated except the "Desktop" item. When I have a
  look inside ~/.config/user-dirs.dirs, the string is untranslated
  (other strings in the file are translated all right). If I run xdg-
  user-dirs-update, ~/.config/user-dirs.dirs is updated to the correct
  translation. So I suppose that the default Live CD user is created by
  some not-localized hackish solution.

  If this seems not so important, since installed systems have the
  "Desktop" directory translated all right (at least I hope so, because
  my system has), it certainly affects all Ubuntu localized Live-CDs and
  makes them fail the basic "translated or not surface check".

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


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

[Desktop-packages] [Bug 1951583] Re: bbswitch dkms build failure with 5.15 on armhf and ppc64el

[Andrea Righi]

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

** No longer affects: linux (Ubuntu Jammy)

** No longer affects: linux (Ubuntu)

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

Title:
  bbswitch dkms build failure with 5.15 on armhf and ppc64el

Status in bbswitch package in Ubuntu:
  New
Status in bbswitch source package in Jammy:
  New

Bug description:
  It looks like bbswitch is using acpi_bus_get_device() on any
  architectures, but this function is not available on armhf or ppc64el:

CC [M]  /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit 
declaration of function ‘acpi_bus_get_device’; did you mean 
‘acpi_get_gpe_device’? [-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of 
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
|   ^~
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of 
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
|   ^~

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


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

[Desktop-packages] [Bug 1951599] [NEW] gnome-shell will crash when eject SDCard

[Bin Li]

Public bug reported:

When I click eject SD card in Files(nautilus), I found the gnome-shell
reported some crash logs.

Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack 
trace for context 0x55a9d8a00120 ==
Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0   
7ffc0b63cc20 b   resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 
@ 149)
Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1   
55a9d8f150b0 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 
69)
Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2   
55a9d8f15018 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 
25)
Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3   
7ffc0b63d8c0 b   self-hosted:850 (1ec3f0b2a650 @ 454)

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

** Attachment added: "gs.log"
   https://bugs.launchpad.net/bugs/1951599/+attachment/5542101/+files/gs.log

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

Title:
  gnome-shell will crash when eject SDCard

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I click eject SD card in Files(nautilus), I found the gnome-shell
  reported some crash logs.

  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack 
trace for context 0x55a9d8a00120 ==
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0   
7ffc0b63cc20 b   resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 
@ 149)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1   
55a9d8f150b0 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 
69)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2   
55a9d8f15018 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 
25)
  Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3   
7ffc0b63d8c0 b   self-hosted:850 (1ec3f0b2a650 @ 454)

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


-- 
Mailing list: https://launchpad.net/~desktop-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

[Tim Passingham]

This is still buggy.

Every time there's a new ubuntu release of Thunderbird  (now on 91.3.1)
I have to repatch /usr/lib/thunderbird/thunderbird.sh and comment out
"export MOZ_ENABLE_WAYLAND=1"


See https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328

-- 
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 1942788] Re: Nvidia doesn't support RTD3 on non-laptops

[Timo Aaltonen]

** Also affects: nvidia-prime (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Nvidia doesn't support RTD3 on non-laptops

Status in OEM Priority Project:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  New
Status in ubuntu-drivers-common source package in Focal:
  Incomplete
Status in nvidia-prime source package in Hirsute:
  New
Status in ubuntu-drivers-common source package in Hirsute:
  Fix Released

Bug description:
  According to Nvidia README, the RTD3 doesn't support on non-laptop
  machine.

  https://github.com/tseliot/ubuntu-drivers-common/issues/55

  We need to check chassis type before enabling RTD3.

  ---

  [Impact]

   * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on 
non-laptop machine
   * Patch make system not enable RTD3 unless it's a laptop

  [Test Plan]

   * Install Ubuntu on machine
   * Install GPU driver via 'ubuntu-drivers install'
   * On laptop with Nvidia RTD3 supported GPU. The configuration file 
'/run/nvidia_runtimepm_supported' will be created

  [Where problems could occur]

   * With non-laptop machine use RTD3 supported GPU may use more power

  [Other Info]

  Information for Focal, refer to
  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816

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


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

[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated

[Timo Aaltonen]

But if you have hw that drivers newer than -390 don't support, you're
stuck with -390. What would happen on such system?

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

Title:
  On-demand and RTD3 need to be separated

Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in nvidia-prime source package in Focal:
  Incomplete
Status in ubuntu-drivers-common source package in Focal:
  New
Status in nvidia-prime source package in Hirsute:
  New
Status in ubuntu-drivers-common source package in Hirsute:
  New

Bug description:
  RTD3 is a nvidia GPU feature to support runtime suspend.

  On-demand would be a X offloading feature.

  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.

  Some parts need to be adjusted, e.g.

  ```
  # If we are dealing with NVIDIA PRIME, and runtimepm
  # is supported, enable it
  if (os.path.isfile('/run/nvidia_runtimepm_supported') and
  os.path.isfile('/usr/bin/prime-select')):
  print('Trying to select the on-demand PRIME profile')
  try:
  subprocess.call(['prime-select', 'on-demand'])
  except:
  pass

  # Create the override file for gpu-manager
  with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
  f.write('# File created by ubuntu-drivers\n')
  ```

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.

  [Other Info]

  X-HWE-Bug: Bug #1946434

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
  - Catch BrokenPipeError.
  - Use bootvga detection when last_gfx_boot is
    not available.

  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).

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


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

[Desktop-packages] [Bug 1951570] [NEW] package xcursor-themes 1.0.6-0ubuntu1 failed to install/upgrade: el subproceso instalado paquete xcursor-themes script post-installation devolvió el código de sa

[migl]

Public bug reported:

Appears almost each time I boot, I sent it this time bc the computer was
suddenly turned off

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: xcursor-themes 1.0.6-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
Uname: Linux 5.4.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
AptOrdering:
 libtalloc2:amd64: Install
 python3-talloc:amd64: Install
 libtevent0:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Nov 19 11:55:11 2021
Dependencies:
 
DistUpgraded: 2020-10-06 12:48:27,511 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: el subproceso instalado paquete xcursor-themes script 
post-installation devolvió el código de salida de error 2
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Pegatron HD Graphics 620 [1b0a:22c4]
InstallationDate: Installed on 2018-09-17 (1158 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 004: ID 0bda:58d4 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MEDION S3409 MD60705
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=5f7c7307-d441-44a9-b5f5-6374d0fdc108 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: xcursor-themes
Title: package xcursor-themes 1.0.6-0ubuntu1 failed to install/upgrade: el 
subproceso instalado paquete xcursor-themes script post-installation devolvió 
el código de salida de error 2
UpgradeStatus: Upgraded to focal on 2020-10-06 (409 days ago)
dmi.bios.date: 02/06/2017
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 215
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: F13K
dmi.board.vendor: MEDION
dmi.board.version: 1.0
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: MEDION
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr215:bd02/06/2017:svnMEDION:pnS3409MD60705:pvr1.0:rvnMEDION:rnF13K:rvr1.0:cvnMEDION:ct10:cvrChassisVersion:
dmi.product.family: Mobile
dmi.product.name: S3409 MD60705
dmi.product.sku: ML-230006 30023072
dmi.product.version: 1.0
dmi.sys.vendor: MEDION
modified.conffile..etc.X11.cursors.core.theme: [deleted]
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xcursor-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal ubuntu

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

Title:
  package xcursor-themes 1.0.6-0ubuntu1 failed to install/upgrade: el
  subproceso instalado paquete xcursor-themes script post-installation
  devolvió el código de salida de error 2

Status in xcursor-themes package in Ubuntu:
  New

Bug description:
  Appears almost each time I boot, I sent it this time bc the computer
  was suddenly turned off

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: xcursor-themes 1.0.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  AptOrdering:
   libtalloc2:amd64: Install
   python3-talloc:amd64: Install
   libtevent0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Nov 19 11:55:11 2021
  Dependencies:
   
  DistUpgraded: 2020-10-06 12:48:27,511 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: 

[Desktop-packages] [Bug 1951571] [NEW] Profile menu doesn't allow you to sign in

[Reuben Firmin]

Public bug reported:

The profile menu in Chromium apparently has had the sign in
functionality disabled. When clicking "Add", Chrome takes you to a sign
in page. Chromium has you create/modify profile locally.

I presume this is Google specific code that can't be open sourced. If
that's the case, the UI should make it clear that the sync functionality
isn't available in Chromium - otherwise it looks like a bug to anybody
vaguely familiar with Chrome's sync (which after all is typically used
once in the lifetime of a browser install).

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Nov 19 04:58:01 2021
DiskUsage:
 Filesystem Type   Size  Used Avail Use% Mounted on
 /dev/sda8  ext422G   15G  6.2G  71% /home
 tmpfs  tmpfs   16G  153M   16G   1% /dev/shm
 /dev/sda8  ext422G   15G  6.2G  71% /home
InstallationDate: Installed on 2021-06-23 (148 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: MSI MS-7978
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=eae448fb-97c0-4bd7-bf3a-83836cf4b78a ro quiet splash vt.handoff=7
Snap.Changes:
 ID   Status  Spawn  Ready  Summary
 20   Done2021-11-18T09:37:12-06:00  2021-11-18T09:38:08-06:00  Install 
"chromium" snap
 21   Done2021-11-18T17:52:22-06:00  2021-11-18T17:53:09-06:00  
Auto-refresh snaps "chromium", "core18"
Snap.ChromeDriverVersion: ChromeDriver 96.0.4664.45 
(76e4c1bb2ab4671b8beba3444e61c0f17584b2fc-refs/branch-heads/4664@{#947})
Snap.ChromiumVersion:
 /home/rfirmin/Downloads was removed, reassigning DOWNLOAD to homedir
 /home/rfirmin/Documents was removed, reassigning DOCUMENTS to homedir
 Chromium 96.0.4664.45 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to impish on 2021-10-21 (28 days ago)
dmi.bios.date: 07/04/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.E0
dmi.board.asset.tag: Default string
dmi.board.name: H170A GAMING PRO (MS-7978)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.E0:bd07/04/2018:br5.12:svnMSI:pnMS-7978:pvr1.0:rvnMSI:rnH170AGAMINGPRO(MS-7978):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7978
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish snap

** Attachment added: "2021-11-18_09-39.png"
   
https://bugs.launchpad.net/bugs/1951571/+attachment/5542051/+files/2021-11-18_09-39.png

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

Title:
  Profile menu doesn't allow you to sign in

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The profile menu in Chromium apparently has had the sign in
  functionality disabled. When clicking "Add", Chrome takes you to a
  sign in page. Chromium has you create/modify profile locally.

  I presume this is Google specific code that can't be open sourced. If
  that's the case, the UI should make it clear that the sync
  functionality isn't available in Chromium - otherwise it looks like a
  bug to anybody vaguely familiar with Chrome's sync (which after all is
  typically used once in the lifetime of a browser install).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Nov 19 04:58:01 2021
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda8  ext422G   15G  6.2G  71% /home
   tmpfs  tmpfs   16G  153M   16G   1% /dev/shm
   /dev/sda8  ext422G   15G  6.2G  71% /home
  InstallationDate: Installed on 2021-06-23 (148 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: MSI MS-7978
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=eae448fb-97c0-4bd7-bf3a-83836cf4b78a ro quiet splash vt.handoff=7
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   20   Done2021-11-18T09:37:12-06:00  2021-11-18T09:38:08-06:00  Install 
"chromium" 

[Desktop-packages] [Bug 1951543] [NEW] Error during package upgrade: Failed to byte-compile extendedsourceslist.py

[zapyon]

Public bug reported:

During a regular update of updatable packages I got this message for the
software-properties package in the shell:


8<
python3-software-properties (0.99.13.1) wird eingerichtet ...
Failed to byte-compile 
/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py:   
File 
"/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", 
line 436
def __init__(self, sourceslist=None, /, files=None):
 ^
SyntaxError: invalid syntax (expected ')')
>8

After the installation process is finished the package is marked as
installed, not as corrupted in aptitude.


Regards

Andreas

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: python3-software-properties 0.99.13.1
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Fri Nov 19 09:10:00 2021
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: software-properties
UpgradeStatus: Upgraded to impish on 2021-10-18 (31 days ago)

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

Title:
  Error during package upgrade: Failed to byte-compile
  extendedsourceslist.py

Status in software-properties package in Ubuntu:
  New

Bug description:
  During a regular update of updatable packages I got this message for
  the software-properties package in the shell:

  
  8<
  python3-software-properties (0.99.13.1) wird eingerichtet ...
  Failed to byte-compile 
/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py:   
File 
"/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", 
line 436
  def __init__(self, sourceslist=None, /, files=None):
   ^
  SyntaxError: invalid syntax (expected ')')
  >8

  After the installation process is finished the package is marked as
  installed, not as corrupted in aptitude.

  
  Regards

  Andreas

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: python3-software-properties 0.99.13.1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Nov 19 09:10:00 2021
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to impish on 2021-10-18 (31 days ago)

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


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