[Desktop-packages] [Bug 1993573]

2022-11-15 Thread bachfreak15
Any news on that issue? Just updated to F37 and this behaviour still
exists.

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

Title:
  Blurry Ubuntu logo and name in about tab

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-control-center package in Fedora:
  Confirmed

Bug description:
  I have a 4K display running on 1440p and I noticed the Ubuntu's logo and name 
are not sharp in the about page (see attached picture)
  ---
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-11-26 (326 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-control-center 1:43.0-1ubuntu2
  PackageArchitecture: amd64
  Tags: third-party-packages kinetic
  Uname: Linux 6.1.0-060100rc1-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-06-14 (126 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1993573/+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 1989937] Re: Nautilus crash when opening an aes file

2022-11-15 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Nautilus crash when opening an aes file

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When clicking on an aes file, nautilus crash (without opening
  anything)

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 16 08:40:43 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'captions' b"['size', 'none', 'none']"
   b'org.gnome.nautilus.preferences' b'fts-enabled' b'false'
   b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1501, 899)'
  InstallationDate: Installed on 2020-11-19 (665 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  JournalErrors: sept. 16 08:40:43 username-xps-13 org.gnome.Nautilus[1687693]: 
free(): invalid pointer
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  Signal: 6
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-09-02 (13 days ago)
  UserGroups: adm audio cdrom dialout dip docker i2c input lpadmin lxd microk8s 
plugdev sambashare sudo uucp
  usr_lib_nautilus:
   file-roller   43~alpha-1
   nautilus-extension-gnome-terminal 3.45.90-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1989937/+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 1988644] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()

2022-11-15 Thread Launchpad Bug Tracker
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.39.90-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  Date: Fri Sep  2 15:34:33 2022
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  IpRoute:
   default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 
20600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 
metric 600
  JournalErrors: -- No entries --
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: network-manager
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: N/A
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.39.90  connected  started  full  enabled enabled  
enabled  missing  enabled
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1989953] Re: to update media key session

2022-11-15 Thread Launchpad Bug Tracker
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  to update media key session

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  the chromium needs to update the media key session cause it rejected
  the Binge website by playing the movie

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989953/+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 1987631] Re: Screencast only records one second

2022-11-15 Thread Matthew D. Mower
I took the time to figure out how ubuntu packages are built and managed
to test the patch in my previous comment (#15) on Jammy. My tests showed
great results; it would be great to get additional confirmation.

Sorry for the verbosity here, but this is new to me:
1. sudo apt-get source gstreamer1.0 gst-plugins-base1.0
2. sudo apt-get build-dep gstreamer1.0 gst-plugins-base1.0
3. apply patches from my previous comment (in gists) to respective source
4. add symbol '_gst_meta_tag_memory_reference@Base 1.20.1' to 
gstreamer1.0/debian/libgstreamer1.0-0.symbols
5. build gstreamer: dpkg-buildpackage -rfakeroot -b
6. install the built libgstreamer1.0-dev deb package so that the new symbol is 
available when building plugins
7. build gst-plugins-base: dpkg-buildpackage -rfakeroot -b
8. install all produced .deb packages

Video attached after gstreamer update to show the effect. I subsequently
reinstalled stock gstreamer and confirmed the broken video recording
happened again.

** Attachment added: "Screencast from 11-15-2022 05:39:43 PM.webm"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5630900/+files/Screencast%20from%2011-15-2022%2005%3A39%3A43%20PM.webm

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

Title:
  Screencast only records one second

Status in GNOME Shell:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Released
Status in pipewire source package in Jammy:
  New

Bug description:
  When recording a screencast with gnome on kinetic the resulting video
  will play for one second and then freeze. It looks like the same bug
  was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-
  shell/-/issues/5585

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

2022-11-15 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-desktop - 42.5-0ubuntu1

---
gnome-desktop (42.5-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1992852)

 -- Zoe Spellman   Thu, 13 Oct 2022 13:21:18
-0700

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

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

Title:
  Update gnome-desktop to 42.5

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

Bug description:
  Impact
  --
  The only thing this update does is update the GNOME version number shown in 
the GNOME Settings > About dialog from 42.4 to 42.5

  That's desired because in general we are running 42.5.

  This update also adds a Croatian (hr) translation. Because we use
  Ubuntu language packs, the new translation won't actually be used
  until the next language pack update, which is expected shortly before
  the Ubuntu 22.04.2 LTS release.

  Test Case
  -
  Install the updated packages
  Open the Settings app.
  Scroll down in the left sidebar and click About
  The GNOME Version should be 42.5

  What Could Go Wrong
  ---
  Because this is part of core GNOME, it falls under the
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  GNOME 43 will use gnome-shell to display the version number so that's one 
less SRU required for future Ubuntu releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1992852/+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 1993785] Update Released

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

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

Title:
  Wrong loader path defined in pkgconfig

Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Jammy:
  Fix Released

Bug description:
  * Impact

  The .pc references to a wrong location for the loaders binary. That's
  because the file is moved from the packaging .install which the build
  system doesn't know about.

  
  * Testcase

  $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0

  should return '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-
  query-loaders' matching where the file is installed

  
  * What could go wrong

  The change is only patching the .pc there is no code change. If the
  patch was wrong the path returned could still not match the actual
  binary location

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1993785/+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 1993785] Re: Wrong loader path defined in pkgconfig

2022-11-15 Thread Launchpad Bug Tracker
This bug was fixed in the package gdk-pixbuf - 2.42.8+dfsg-1ubuntu0.2

---
gdk-pixbuf (2.42.8+dfsg-1ubuntu0.2) jammy; urgency=medium

  * debian/patches/debian_queryloader_dir.patch:
- fix the directory referenced for gdk-pixbuf-query-loaders
  in the .pc since that file is moved by the packaging (lp: #1993785)

 -- Sebastien Bacher   Fri, 21 Oct 2022 09:26:30
+0200

** Changed in: gdk-pixbuf (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Wrong loader path defined in pkgconfig

Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Jammy:
  Fix Released

Bug description:
  * Impact

  The .pc references to a wrong location for the loaders binary. That's
  because the file is moved from the packaging .install which the build
  system doesn't know about.

  
  * Testcase

  $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0

  should return '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-
  query-loaders' matching where the file is installed

  
  * What could go wrong

  The change is only patching the .pc there is no code change. If the
  patch was wrong the path returned could still not match the actual
  binary location

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1993785/+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 72415] Re: cacert.org root certificate inclusion

2022-11-15 Thread Paul Bryan
Why is this bug being resurrected after 19 years of inactivity?

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

Title:
  cacert.org root certificate inclusion

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

Bug description:
  Binary package hint: firefox

  i'd have thought that, for sure, this bug would exist.  after much
  searching, i am unable to find it.

  the long and the short of it is that firefox (and epiphany!) packages
  on ubuntu should have the cacert.org root certificate included.

  the reasons for doing
  so are explained in this well-written mozilla bug report and many of its
  comments:

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

  in comment #20 of that bug report, Frank Hacker , who
  claims to be "the person tasked with developing the mozilla.org policy on
  inclusion of root CA certs" approves the inclusion (2 and a half years ago!)
  but there has been considerable foot-dragging and objections from the person
  who would actually implement the change.

  before this comment, however (Frank was a bit slow with a reply) Chris
  Hoffman  (mozilla engineering director) notes that
  "Distributors can add or delete certs and modify trust bits on certs
  in the default db.".

  i believe this to be a valid interim solution while upstream gets
  their stuff sorted out.  there's a question of if the modified firefox
  will still be able to be branded as "mozilla firefox" but this is
  nothing that ubuntu isn't already dealing with.

  in any case, this does not affect epiphany.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/72415/+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 28048] Re: “firefox crash on exit if client certificates used for ssl auth”

2022-11-15 Thread Bug Watch Updater
** Changed in: firefox
   Importance: Wishlist => Medium

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

Title:
  “firefox crash on exit if client certificates used for ssl auth”

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Tested on both windows and Linux, firefox 1.0.7 on lin/win and firefox
  1.5 on Win.

  Using CACert.org, the free certificate provider as the root CA, and 
installing a
  client certificate into firefox.  Then going to a website that authenticates 
me
  using that certificate and exiting firefox will result in a crash.

  1. Start firefox
  2. Go to website that uses client certificate for auth
  3. Quit firefox.
  4. Crash results.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/28048/+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 72415] Re: cacert.org root certificate inclusion

2022-11-15 Thread Bug Watch Updater
** Changed in: firefox
   Importance: Wishlist => Medium

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

Title:
  cacert.org root certificate inclusion

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

Bug description:
  Binary package hint: firefox

  i'd have thought that, for sure, this bug would exist.  after much
  searching, i am unable to find it.

  the long and the short of it is that firefox (and epiphany!) packages
  on ubuntu should have the cacert.org root certificate included.

  the reasons for doing
  so are explained in this well-written mozilla bug report and many of its
  comments:

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

  in comment #20 of that bug report, Frank Hacker , who
  claims to be "the person tasked with developing the mozilla.org policy on
  inclusion of root CA certs" approves the inclusion (2 and a half years ago!)
  but there has been considerable foot-dragging and objections from the person
  who would actually implement the change.

  before this comment, however (Frank was a bit slow with a reply) Chris
  Hoffman  (mozilla engineering director) notes that
  "Distributors can add or delete certs and modify trust bits on certs
  in the default db.".

  i believe this to be a valid interim solution while upstream gets
  their stuff sorted out.  there's a question of if the modified firefox
  will still be able to be branded as "mozilla firefox" but this is
  nothing that ubuntu isn't already dealing with.

  in any case, this does not affect epiphany.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/72415/+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 232340] Re: CaCert Certificates not installed

2022-11-15 Thread Bug Watch Updater
** Changed in: thunderbird
   Importance: Wishlist => Medium

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

Title:
  CaCert Certificates not installed

Status in Evolution:
  Fix Released
Status in Mozilla Thunderbird:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: evolution

  Although CaCert.org certificates are part of the ca-certificates packages and 
installted on the system by default, evolution does not have them installed by 
default. One has to manually import them from either web or 
/usr/share/ca-certificates/...
  They should be known to evolution by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/232340/+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 1996652] [NEW] Nautilus search is slow and jumbles keyboard input on 22.10

2022-11-15 Thread Ryan Beisner
Public bug reported:

Since my upgrade to 22.10, I've found the search box in Nautilus (files)
essentially unusable.  It is notably sluggish to launch and browse in
general.  But most detrimental to the usability is this:

The characters do not appear in real time as I type. When they do
appear, they are sometimes jumbled or in reverse (consistently
reproducible).  As I type in the file search box, the circular cursor
spins intermittently, then the UI catches up and it's not what I typed.

For example, I just typed "umbrella" into the search box, and Nautilus searched 
for:
"umballer"

Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut"
... you can't make this up. :-)

Test #3, typed Launchpad, ended up with a search for "Laudaphcn".

Keyboard input everywhere else on the system is otherwise normal and
snappy.  No pun intended, really.

FWIW Nautilus files preferences are as default (Search in subfolders,
Show thumbnails, File count == This computer only).



$ apt-cache policy nautilus
nautilus:
  Installed: 1:43.0-1ubuntu1
  Candidate: 1:43.0-1ubuntu1
  Version table:
 *** 1:43.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
100 /var/lib/dpkg/status

$ uname -r
5.19.0-23-generic

$ lsb_release -rd
Description:Ubuntu 22.10
Release:22.10

$ snap list
Name   Version   RevTracking Publisher  
Notes
bare   1.0   5  latest/stablecanonical✓ 
base
core   16-2.57.2 13886  latest/stablecanonical✓ 
core
core18 20221027  2620   latest/stablecanonical✓ 
base
core20 20221027  1695   latest/stablecanonical✓ 
base
gnome-3-34-18040+git.3556cb3 77 latest/stable/…  canonical✓ 
-
gnome-3-38-20040+git.6f39565 119latest/stablecanonical✓ 
-
google-cloud-sdk   409.0.0   298latest/stable
google-cloud-sdk✓  classic
gtk-common-themes  0.1-81-g442e511   1535   latest/stable/…  canonical✓ 
-
snap-store 41.3-64-g512c0ff  599latest/stable/…  canonical✓ 
-
snapd  2.57.417336  latest/stablecanonical✓ 
snapd
snapd-desktop-integration  0.1   14 latest/stable/…  canonical✓ 
-


Side question:  Since this system has transitioned across several upgrades from 
20.04 to 22.10, do I really need all of these core* and gnome* snaps?

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


** Tags: kinetic

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

Title:
  Nautilus search is slow and jumbles keyboard input on 22.10

Status in nautilus package in Ubuntu:
  New

Bug description:
  Since my upgrade to 22.10, I've found the search box in Nautilus
  (files) essentially unusable.  It is notably sluggish to launch and
  browse in general.  But most detrimental to the usability is this:

  The characters do not appear in real time as I type. When they do
  appear, they are sometimes jumbled or in reverse (consistently
  reproducible).  As I type in the file search box, the circular cursor
  spins intermittently, then the UI catches up and it's not what I
  typed.

  For example, I just typed "umbrella" into the search box, and Nautilus 
searched for:
  "umballer"

  Off-the-cuff test #2, searched for "Ubuntu" and I ended up with
  "Ubunut" ... you can't make this up. :-)

  Test #3, typed Launchpad, ended up with a search for "Laudaphcn".

  Keyboard input everywhere else on the system is otherwise normal and
  snappy.  No pun intended, really.

  FWIW Nautilus files preferences are as default (Search in subfolders,
  Show thumbnails, File count == This computer only).

  

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:43.0-1ubuntu1
Candidate: 1:43.0-1ubuntu1
Version table:
   *** 1:43.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ uname -r
  5.19.0-23-generic

  $ lsb_release -rd
  Description:Ubuntu 22.10
  Release:22.10

  $ snap list
  Name   Version   RevTracking 
Publisher  Notes
  bare   1.0   5  latest/stable
canonical✓ base
  core   16-2.57.2 13886  latest/stable
canonical✓ core
  core18 20221027  2620   latest/stable
canonical✓ base
  core20 20221027  1695   latest/stable
canonical✓ base
  gnome-3-34-18040+git.3556cb3 77 latest/stable/…  
canonical✓ 

[Desktop-packages] [Bug 1975823] Re: pipewire alsa missing configurations on multi output systems

2022-11-15 Thread Bug Watch Updater
** Changed in: pipewire (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  pipewire alsa missing configurations on multi output systems

Status in pipewire package in Ubuntu:
  Triaged
Status in pipewire package in Debian:
  Fix Released

Bug description:
  I have this bug also if I install pipewire manaully on focal and
  jammy.

  I use a Java Application using the javax.sound package to get a output to the 
AudioSystem.
  I have an own Java library using the same and I poked around a bit:

  It uses Alsa as Output. The line object Java provides has the
  possibility to ask for the available bytes in the buffer. Normally
  with pulseaudio you can see the buffer getting filled and then, as the
  audio get's played back, recovering by the played back bytes amount.

  With pipewire-pulse on the other hand it just fills the buffer and
  reporting no more available bytes. But it plays back the bytes
  successfully written to the buffer. Meaning its unable to write more,
  as the available buffer size never recovers, even though the already
  written ones have been played just fine.

  I have checked the behavior also on Debain-testing, Manjaro and Fedora. 
Fedora is the only distro without this problem.
  Fedora has the package pipewire-alsa in its repositories and installed, which 
is not available on the other distros. If I have understood it correctly, the 
alsa functionality should be included into the default pipewire-pulse now, but 
for some reason fedora decided to keep the extra package?

  So I'd really like to see pipewire-pulse being the default in the
  future, but this has to be fixed somehow.

  For reference, here's an issue on the pipewire gitlab I've filed already 
about this:
  https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2255

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire-pulse 0.3.48-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 26 14:58:40 2022
  InstallationDate: Installed on 2022-05-26 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1975823/+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 1993308] Re: Update gnome-calendar to 43.1

2022-11-15 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-calendar - 43.1-0ubuntu1

---
gnome-calendar (43.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1993308)
- Fixes multiple issues with recurring events

 -- Jeremy Bicha   Tue, 18 Oct 2022 10:09:27 -0400

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

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

Title:
  Update gnome-calendar to 43.1

Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Kinetic:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 43 series.
  https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/43.1/NEWS

  This includes several fixes for recurring calendar events. These bugs
  were considered a release blocker for Fedora 37.

  https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar

  What Could Go Wrong
  ---
  GNOME Calendar is included by default only in the Ubuntu Desktop flavor.

  If there are bugs in GNOME Calendar, Evolution (not installed by
  default) could be used instead.

  GNOME Calendar can sync with Google or Microsoft online calendars.
  Therefore, bugs in editing calendar events can by synced to those
  services.

  GNOME Calendar is part of GNOME Core and is included in the GNOME
  micro release exception

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1993308/+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 1993308] Update Released

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

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

Title:
  Update gnome-calendar to 43.1

Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Kinetic:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 43 series.
  https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/43.1/NEWS

  This includes several fixes for recurring calendar events. These bugs
  were considered a release blocker for Fedora 37.

  https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar

  What Could Go Wrong
  ---
  GNOME Calendar is included by default only in the Ubuntu Desktop flavor.

  If there are bugs in GNOME Calendar, Evolution (not installed by
  default) could be used instead.

  GNOME Calendar can sync with Google or Microsoft online calendars.
  Therefore, bugs in editing calendar events can by synced to those
  services.

  GNOME Calendar is part of GNOME Core and is included in the GNOME
  micro release exception

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1993308/+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 1996067] Re: [SRU] Enable support for Antelope Cloud Archive

2022-11-15 Thread Corey Bryant
** Also affects: software-properties (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
   [SRU] Enable support for Antelope Cloud Archive

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Jammy:
  New

Bug description:
  Please add support for:

 cloud-archive:antelope
 cloud-archive:antelope-proposed

  This will also need to be SRU'd back to jammy.

  [Impact]
  End users have to manually enable the antelope cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:antelope
  sudo add-apt-repository cloud-archive:antelope-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1996067/+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 1992225] Re: Under Wayland Thunderbird crashes every time after resume from suspend to RAM

2022-11-15 Thread Andrei Borzenkov
Thunderbird crashed when there were two monitors connected on resume.
This is apparently fixed in
https://bugzilla.mozilla.org/show_bug.cgi?id=1793922. I rebuilt Ubuntu
22.04 package with patch from this bug (no other changes) and this seems
to have fixed it. Patch applied to Thunderbird 102 with minimal fuzz.

Patch: https://phabricator.services.mozilla.com/D158747
My bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1800364

My modified package:
https://build.opensuse.org/package/show/home:arvidjaar:Ubuntu:22.04/thunderbird

Because Ubuntu forces Thunderbird in Wayland mode by default, I kindly
request official update with this patch included.

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

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

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

Title:
  Under Wayland Thunderbird crashes every time after resume from suspend
  to RAM

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04, GNOME desktop in Wayland mode, Tunderbird
  102.2.2+build1-0ubuntu0.22.04.1. Ubuntu forces Thunderbird in Wayland.
  From /usr/bin/thunderbird

  # Enable native Wayland support (https://launchpad.net/bugs/1916469)
  export MOZ_ENABLE_WAYLAND=1

  After update to 102 Thunderbird crashes every time system is resumed
  from suspend to RAM. When removing MOZ_ENABLE_WAYLAND and tunning
  Thunderbird under Xwayland there is no crash. Previous version did not
  crash either.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thunderbird 1:102.2.2+build1-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-lowlatency 5.15.53
  Uname: Linux 5.15.0-48-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BuildID: 20220906224751
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  8 10:42:37 2022
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  Extensions: extensions.sqlite corrupt or missing
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-07-02 (2654 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:306
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=102.2.2/20220906224751 (In use)
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to jammy on 2022-06-16 (113 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1992225/+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 1992225] Re: Under Wayland Thunderbird crashes every time after resume from suspend to RAM

2022-11-15 Thread Andrei Borzenkov
** Changed in: thunderbird (Ubuntu)
   Status: Invalid => 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/1992225

Title:
  Under Wayland Thunderbird crashes every time after resume from suspend
  to RAM

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04, GNOME desktop in Wayland mode, Tunderbird
  102.2.2+build1-0ubuntu0.22.04.1. Ubuntu forces Thunderbird in Wayland.
  From /usr/bin/thunderbird

  # Enable native Wayland support (https://launchpad.net/bugs/1916469)
  export MOZ_ENABLE_WAYLAND=1

  After update to 102 Thunderbird crashes every time system is resumed
  from suspend to RAM. When removing MOZ_ENABLE_WAYLAND and tunning
  Thunderbird under Xwayland there is no crash. Previous version did not
  crash either.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thunderbird 1:102.2.2+build1-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-lowlatency 5.15.53
  Uname: Linux 5.15.0-48-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BuildID: 20220906224751
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  8 10:42:37 2022
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  Extensions: extensions.sqlite corrupt or missing
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-07-02 (2654 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:306
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=102.2.2/20220906224751 (In use)
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to jammy on 2022-06-16 (113 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1992225/+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 1996634] [NEW] xdg-email fails to execute thunderbird.desktop properly

2022-11-15 Thread rick beldin
Public bug reported:

Kubuntu users who use thunderbird as their default mailer will not be
able to open mailto: links in html pages.   This appears to be a KDE-
specific bug from the notes upstream.

This issue has been fixed upstream, but the fixes are not yet in:

  ii  xdg-utils  1.1.3-4.1ubuntu3~22.04.1 all  desktop
integration utilities from freedesktop.org

The upstream commit is:

https://gitlab.freedesktop.org/xdg/xdg-utils/-/issues/187

I verified that the changes in the /usr/bin/xdg-email script listed
above address the issue.

After applying the code changes, chrome is now able to open mailto links
to launch thunderbird.

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


** Tags: kde kubuntu

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

Title:
  xdg-email fails to execute thunderbird.desktop properly

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Kubuntu users who use thunderbird as their default mailer will not be
  able to open mailto: links in html pages.   This appears to be a KDE-
  specific bug from the notes upstream.

  This issue has been fixed upstream, but the fixes are not yet in:

ii  xdg-utils  1.1.3-4.1ubuntu3~22.04.1 all  desktop
  integration utilities from freedesktop.org

  The upstream commit is:

  https://gitlab.freedesktop.org/xdg/xdg-utils/-/issues/187

  I verified that the changes in the /usr/bin/xdg-email script listed
  above address the issue.

  After applying the code changes, chrome is now able to open mailto
  links to launch thunderbird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1996634/+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 1996633] [NEW] Broken link in manpage for notify-send

2022-11-15 Thread rabbitflyer
Public bug reported:

Currently, the manpage for notify-send provides a see-also link to
"http://www.galago-project.org/specs/notification/";, which returns a 404
error when followed.

User "Pablo A B" suggested
"https://specifications.freedesktop.org/notification-spec/notification-
spec-latest.html" as a replacement link on the Debian bug report logs.
Original discussion is at https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=869277#44


Detailed info:

 Package: libnotify-bin
 Version: 0.7.9-3ubuntu5.22.04.1
 APT-Sources: https://nyc.mirrors.clouvider.net/ubuntu jammy-updates/main amd64 
Packages

  OS: Linux Mint 21
  Kernel: Linux 5.15.0-53-generic
Architecture: x86-64

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


** Tags: manpage

** Patch added: "libnotify-0.7.9.diff"
   
https://bugs.launchpad.net/bugs/1996633/+attachment/5630878/+files/libnotify-0.7.9.diff

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

Title:
  Broken link in manpage for notify-send

Status in libnotify package in Ubuntu:
  New

Bug description:
  Currently, the manpage for notify-send provides a see-also link to
  "http://www.galago-project.org/specs/notification/";, which returns a
  404 error when followed.

  User "Pablo A B" suggested
  "https://specifications.freedesktop.org/notification-
  spec/notification-spec-latest.html" as a replacement link on the
  Debian bug report logs. Original discussion is at
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869277#44


  Detailed info:

   Package: libnotify-bin
   Version: 0.7.9-3ubuntu5.22.04.1
   APT-Sources: https://nyc.mirrors.clouvider.net/ubuntu jammy-updates/main 
amd64 Packages

OS: Linux Mint 21
Kernel: Linux 5.15.0-53-generic
  Architecture: x86-64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1996633/+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 1995054] Update Released

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

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

Title:
  [SRU] libreoffice 7.3.7 for jammy

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release

   * Version 7.3.6 is currently released in jammy. For a list of fixed bugs 
compared to 7.3.6 see the list of bugs fixed in the release candidates of 7.3.7 
(that's a total of 28 bugs):
   https://wiki.documentfoundation.org/Releases/7.3.7/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.3.7/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_73/2020/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20221027_233324_4fa91@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20221028_084007_5ae64@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/armhf/libr/libreoffice/20221028_023850_ff210@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20221027_233859_894f7@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20221027_225956_efc56@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 28 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054/+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 1995054] Re: [SRU] libreoffice 7.3.7 for jammy

2022-11-15 Thread Launchpad Bug Tracker
This bug was fixed in the package libreoffice - 1:7.3.7-0ubuntu0.22.04.1

---
libreoffice (1:7.3.7-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #1995054)

  [ Rico Tzschichholz ]
  * Bump yaru source to "2022-09-04"

  [ Rene Engelhard ]
  * debian/rules:
- add missing >&3 to ufcq calls in bug scripts
- fix build-depends-on-obsolete-package
  (s/libfreetype6-dev/libfreetype-dev/,
  s/libfontconfig1-dev/libfontconfig-dev/)
- don't add Graphics; to draws .desktop, it's already there

 -- Rico Tzschichholz   Thu, 27 Oct 2022 12:34:13
+0200

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

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

Title:
  [SRU] libreoffice 7.3.7 for jammy

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release

   * Version 7.3.6 is currently released in jammy. For a list of fixed bugs 
compared to 7.3.6 see the list of bugs fixed in the release candidates of 7.3.7 
(that's a total of 28 bugs):
   https://wiki.documentfoundation.org/Releases/7.3.7/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.3.7/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_73/2020/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20221027_233324_4fa91@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20221028_084007_5ae64@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/armhf/libr/libreoffice/20221028_023850_ff210@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20221027_233859_894f7@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20221027_225956_efc56@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 28 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054/+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 1892559] Re: [MIR] ccid opensc pcsc-lite

2022-11-15 Thread Christian Ehrhardt 
** Changed in: pcsc-lite (Ubuntu)
   Status: New => Incomplete

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

Title:
  [MIR] ccid opensc pcsc-lite

Status in ccid package in Ubuntu:
  In Progress
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  Invalid
Status in pcsc-lite package in Ubuntu:
  Incomplete
Status in pcsc-perl package in Ubuntu:
  Invalid
Status in pcsc-tools package in Ubuntu:
  Invalid

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.  https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465

  Has a debian/watch file.
  Quilt packaging.

  P: ccid source: no-dep5-copyright
  P: ccid source: package-uses-experimental-debhelper-compat-version 13

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  ccid provides drivers to interact with usb-connected smart card readers.

  ==> libpam-pkcs11 <==
  [Availability]
  Source package pam-pkcs11 is in universe and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs in our database.
  Doesn't appear to bind to sockets.
  No privileged executables (but is a PAM module).
  As a PAM module this will require a security review.

  [Quality assurance]
  The package does not call pam-auth-update in its postinst #1650366
  Does not ask questions during install.
  One Ubuntu bug claims very poor behaviour if a card isn't plugged in.
  No Debian bugs.
  Occasional updates in Debian by long-term maintainer.
  Does require odd hardware that we'll probably need to buy.
  Does not appear to run tests during build.
  Has scary warnings in the build logs.
  Has a debian/watch file.

  Ancient standards version; other smaller lintian messages, mostly
  documentation problems.

  Quilt packaging.

  [Dependencies]
  Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1
  All are in main.

  [Standards compliance]
  The package does not call pam-auth-update in its postinst #1650366
  Otherwise looks to conform to FHS and Debian policies

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  This PAM module can use CRLs and full-chain verification of certificates.
  It can also do LDAP, AD, and Kerberos username mapping.

  ==> libpcsc-perl <==
  [Availability]
  Source package pcsc-perl is in universe, builds for all architectures,
  plus i386

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  There are no cves for pcsc-perl in our database.
  No privileged executables.
  Doesn't appear to bind to sockets.
  Probably needs a security review.

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Tests exist, not run during the build; probably can't run during the build.
  Includes debian/watch file.
  A handful of lintian issues
  Quilt packaging.

  [Dependencies]
  libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0.
  All are in main.

  [Standards compliance]
  One oddity, Card.pod is stored in 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/
  Many other perl packages have .pod files in these directory trees so maybe
  it's fine, but it seems funny all the same.

  Otherwise appears to satisfy FHS and Debian policy.

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  Dependency of pcsc-tools; this library pr

[Desktop-packages] [Bug 1992128] Re: thunderbird hangs on start

2022-11-15 Thread Olivier Tilloy
** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  thunderbird hangs on start

Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  On startup, even with safe-mode, thunderbird hangs before you can click 
anything, you get the pop-up "Thunderbird does not answer" with the options 
exit and wait. I have two IMAP accounts and 10 calendars configured.
  This is on Ubuntu 22.04.1 LTS with thunderbird 
102.2.2+build1-0ubuntu0.22.04.1.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thunderbird 1:102.2.2+build1-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21
  Uname: Linux 5.14.0-1051-oem x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  waschk 5091 F pulseaudio
  BuildID: 20220906224751
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  7 07:52:52 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  Extensions: extensions.sqlite corrupt or missing
  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: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2021-08-20 (412 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IpRoute:
   default via 192.168.0.1 dev wlp0s20f3 proto dhcp metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.0.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.0.102 
metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-05b3964b-1b71-4de2-ad4b-a1e9a0220718
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:306
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  Profiles: Profile0 (Default) - LastVersion=102.2.2/20220906224751
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to jammy on 2022-09-10 (26 days ago)
  dmi.bios.date: 08/29/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.2
  dmi.board.name: 0H2KK6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: pcx38465
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd08/29/2022:br1.19:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn0H2KK6:rvrA01:cvnDellInc.:ct10:cvr:sku0A34:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7320
  dmi.product.sku: 0A34
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1992128/+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 1790608] Re: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp)

2022-11-15 Thread Tom Chiverton
Same, it must surely be a common use case to download files to /tmp
because you do not expect (or want) them to persist. That's what /tmp is
for...

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

Title:
  [snap] Libreoffice/Firefox do not open files from thunderbird (more
  general: from /tmp)

Status in snapd:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I received a document via e-mail in Thunderbird. I have the
  Libreoffice snap package installed. When I want to open the document
  from Thunderbird, I see the Libreoffice splash screen, and then a
  dialog stating "/tmp/mozilla_0/.docx does not exist."

  The same dialog appears when I navigate to the folder in Files and
  want to open it.

  When I copy the file to my desktop, however, I can open it without
  problems.

  I guess the source of the issue is confinement, that the Libreoffice
  snap can only access files from $HOME. But this breaks the case where
  thunderbird creates a temporary copy in /tmp.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1790608/+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 1686333] Re: e7440 Latitude / Dell Dock Fails to detect extra Display ports

2022-11-15 Thread Rostislav
e7440 Latitude has two CRTCs (some piece of hardware, needed one per
screen), so only two screens can work at a time. Not a bug.

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

Title:
  e7440 Latitude / Dell Dock Fails to detect extra Display ports

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  e7440 Latitude / Dell Dock

  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  xserver-xorg-video-intel  2:2.99.917+git20160325-1ubuntu1.2

  The docking station maps DP1 port of the laptop to two outputs at the
  back panel mirroring the picture.

  Earlier (in 14.04) it used to be two separate outputs DP2 and DP3,
  which could not work at the same time with eDP(laptop screen) or
  DP1(laptop's port).

  The problem is very similar to described here:
  
https://01.org/linuxgraphics/forum/graphics-power-users/e7440-latitude/dell-dock-dual-monitors-ubuntu-14.04-fixed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1686333/+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 1992128] Re: thunderbird hangs on start

2022-11-15 Thread Götz Waschk
It is fixed in the latest official update on Ubuntu 18.04:
102.4.2+build2-0ubuntu0.18.04.1

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

Title:
  thunderbird hangs on start

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  On startup, even with safe-mode, thunderbird hangs before you can click 
anything, you get the pop-up "Thunderbird does not answer" with the options 
exit and wait. I have two IMAP accounts and 10 calendars configured.
  This is on Ubuntu 22.04.1 LTS with thunderbird 
102.2.2+build1-0ubuntu0.22.04.1.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thunderbird 1:102.2.2+build1-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21
  Uname: Linux 5.14.0-1051-oem x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  waschk 5091 F pulseaudio
  BuildID: 20220906224751
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  7 07:52:52 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  Extensions: extensions.sqlite corrupt or missing
  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: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2021-08-20 (412 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IpRoute:
   default via 192.168.0.1 dev wlp0s20f3 proto dhcp metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.0.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.0.102 
metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-05b3964b-1b71-4de2-ad4b-a1e9a0220718
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:306
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  Profiles: Profile0 (Default) - LastVersion=102.2.2/20220906224751
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to jammy on 2022-09-10 (26 days ago)
  dmi.bios.date: 08/29/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.2
  dmi.board.name: 0H2KK6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: pcx38465
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd08/29/2022:br1.19:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn0H2KK6:rvrA01:cvnDellInc.:ct10:cvr:sku0A34:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7320
  dmi.product.sku: 0A34
  dmi.sys.vendor: Dell Inc.

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