[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Birk Bremer]

Seems to be a gtk4 issue. The package maintainer of gtk4 would have to update 
his package... 
https://gitlab.gnome.org/GNOME/gtk/-/issues/4798


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1949340

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

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


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

[Touch-packages] [Bug 1992930] Re: chromium won't launch at menu when installed; lubuntu kinetic

[Chris Guiver]

I zsync'd the latest Xubuntu kinetic; repeated the instructions as per
this bug report and no issue with Xubuntu either..

so not Ubuntu Budgie (#5) & not Xubuntu

issue maybe is Lubuntu only?  if so why?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1992930

Title:
  chromium won't launch at menu when installed; lubuntu kinetic

Status in apparmor package in Ubuntu:
  New

Bug description:
  Lubuntu kinetic live test

  `chromium` snap once installed; will not open from menu, but will open
  if started from terminal.  This maybe filed against incorrect package
  sorry.

  Originally reported here - https://discourse.lubuntu.me/t/lubuntu-
  kinetic-after-5-19-update-chromium-only-start-from-terminal/3685 where
  it was reported as an issue on the 5.19.0-19-generic kernel update

  ** to re-create

  - boot currently lubuntu kinetic daily
  - snap install chromium
  - using menu, attempt to run chromium from internet apps

  ** expected outcome

  chromium starts

  ** actual outcome

  menu just closes; no messages.

  ** further notes

  u/FossFreedom (Ubuntu Budgie) reports no issues with Ubuntu Budgie
  kinetic starting Chromium.

  On Lubuntu's discourse; u/neblaz (OP for issue) also reported issues starting 
Opera; with that package being the snap (loaded from discover) and reported as 
(using `snap list`)
  opera   91.0.4516.77202
latest/stable

  
  ** in `dmesg` I note the following (this may be unrelated or unhelpful sorry)

  [ 1510.255228] loop7: detected capacity change from 0 to 293648
  [ 1510.739240] audit: type=1400 audit(1665727470.633:54): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap-update-ns.chromium" 
pid=3359 comm="apparmor_parser"
  [ 1510.820094] audit: type=1400 audit(1665727470.713:55): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap.chromium.chromedriver" 
pid=3360 comm="apparmor_parser"
  [ 1511.014103] audit: type=1400 audit(1665727470.909:56): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap.chromium.chromium" 
pid=3361 comm="apparmor_parser"
  [ 1511.071575] audit: type=1400 audit(1665727470.965:57): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="snap.chromium.hook.configure" pid=3362 comm="apparmor_parser"
  [ 1515.313383] audit: type=1400 audit(1665727475.206:58): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="/snap/snapd/17029/usr/lib/snapd/snap-confine" 
pid=3496 comm="apparmor_parser"
  [ 1515.313401] audit: type=1400 audit(1665727475.206:59): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" 
name="/snap/snapd/17029/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
 pid=3496 comm="apparmor_parser"
  [ 1516.817149] audit: type=1400 audit(1665727476.710:60): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap-update-ns.chromium" 
pid=3498 comm="apparmor_parser"
  [ 1518.067335] audit: type=1400 audit(1665727477.962:61): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="snap.chromium.chromedriver" pid=3499 comm="apparmor_parser"
  [ 1518.568962] audit: type=1400 audit(1665727478.462:62): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="snap.chromium.hook.configure" pid=3501 comm="apparmor_parser"
  [ 1519.485025] audit: type=1400 audit(1665727479.378:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.chromium.chromium" 
pid=3500 comm="apparmor_parser"
  [ 1520.203518] audit: type=1400 audit(1665727480.098:64): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/meta/snap.yaml" pid=3518 comm="6" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  [ 1520.245234] audit: type=1400 audit(1665727480.142:65): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/fonts/" pid=3518 comm="6" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 1520.245256] audit: type=1400 audit(1665727480.142:66): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/" pid=3518 comm="6" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  [ 1520.246876] audit: type=1400 audit(1665727480.142:67): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/var/lib/snapd/hostfs/usr/share/doc/" pid=3518 comm="6" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 1520.246933] audit: type=1400 audit(1665727480.142:68): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/var/lib/snapd/hostfs/usr/share/fonts/" pid=3518 comm="6" 
requested_mask="r" denie

[Touch-packages] [Bug 1977630] Re: machinectl pull-tar/pull-raw Operation not permitted

[murmel]

this seems to be still bugged, are any more logs required to get this
fixed?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1977630

Title:
  machinectl pull-tar/pull-raw Operation not permitted

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Triaged

Bug description:
  [impact]

  machinectl pull-tar does not work, ever

  [test case]

  see comment 2

  [regression potential]

  problems/failures during pull-tar operation

  [scope]

  needed only in j

  fixed (indirectly) by upstream commit referenced in original
  description, which is included in v250, so fixed already in k

  pull-tar does not fail on f; no fix needed there

  [original description]

  There is a bug in systemd 249, where one can't pull any images. This
  was fixed in version 250, and never got backported. (FIX:
  
https://github.com/systemd/systemd/commit/c40d82abf7b23803aa7394a7a7e24c40c32af851)

  Hopefully this can be addressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd-container 249.11-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  Uname: Linux 5.15.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  4 04:51:42 2022
  InstallationDate: Installed on 2022-06-01 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1992688] Re: firefox deb not installed

[Brian Murray]

** Changed in: ubuntu-meta (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: ubuntu-meta (Ubuntu Jammy)
Milestone: None => ubuntu-22.04.2

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

Title:
  firefox deb not installed

Status in firefox package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in firefox source package in Jammy:
  New
Status in ubuntu-meta source package in Jammy:
  Triaged

Bug description:
  Bug 1964036 leads me to believe that the firefox deb provides some
  important functionality (the firefox favourite icon in the gnome shell
  dock) but there is nothing that would require the deb to be installed
  (it is not seeded nor has an rdep) and the package description
  indicates that it can be safely removed. Is there some important
  functionality that it provides?

  ProblemType: BugDistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 11:30:46 2022
  InstallationDate: Installed on 2022-04-27 (167 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago)
  VarLogDistupgradeTermlog:

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


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

[Touch-packages] [Bug 1992701] Re: Issue with opening module dependency file

[Michal Dziczkowski]

The system id started up as a LiveCD from a burned out ISO.nl After
upgrading thr kernel, there was no 4eboot

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1992701

Title:
  Issue with opening module dependency file

Status in kmod package in Ubuntu:
  Incomplete

Bug description:
  Tested on: Trusty, Xenial (used as recovery system)

  I'm unable to manage (modprobe, insmod) modules due following error:

  "modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could
  not open moddep file '/lib/modules/3.13.0-24-generic/modules.dep.bin'"

  I don't know why, but it seem like in the libkmod.c was a bug that
  attempt to load an old kernel after it got upgraded (replaced with) a
  newer one.

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


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

[Touch-packages] [Bug 1980386] Re: `radeonsi_dri.so` driver missing on riscv64

[Michał Sawicz]

Can confirm this works fine on kinetic:

>  GLRenderer: GL vendor: AMD
>  GLRenderer: GL renderer: AMD Radeon RX 480 Graphics (polaris10, 
> LLVM 15.0.2, DRM 3.47, 5.19.0-1002-generic)
>  GLRenderer: GL version: OpenGL ES 3.2 Mesa 22.2.1
>  GLRenderer: GLSL version: OpenGL ES GLSL ES 3.20

Vs. jammy:

> MESA-LOADER: failed to open radeonsi: /usr/lib/dri/radeonsi_dri.so: cannot 
> open shared object file: No such file or directory (search paths 
> /usr/lib/riscv64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
> failed to load driver: radeonsi
>  GLRenderer: GL vendor: Mesa/X.org   
>   
>
>  GLRenderer: GL renderer: softpipe   
>   
>
>  GLRenderer: GL version: OpenGL ES 3.1 Mesa 22.0.5   
>   
>
>  GLRenderer: GLSL version: OpenGL ES GLSL ES 3.10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1980386

Title:
  `radeonsi_dri.so` driver missing on riscv64

Status in llvm-toolchain-15 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in llvm-toolchain-15 source package in Jammy:
  In Progress
Status in mesa source package in Jammy:
  Confirmed
Status in llvm-toolchain-15 source package in Kinetic:
  Fix Released
Status in mesa source package in Kinetic:
  Fix Released

Bug description:
  The package is missing the `radeonsi` driver, with the reasoning that
  LLVM is not implemented on the architecture:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618

  That said, it works just fine on focal, where it is still enabled.
  Without this driver there's no way to use AMD graphics cards on
  RISC-V.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.1-1ubuntu2
  ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30
  Uname: Linux 5.15.0-1007-generic riscv64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  Date: Thu Jun 30 15:48:11 2022
  ProcCpuinfoMinimal:
   processor: 3
   hart : 4
   isa  : rv64imafdc
   mmu  : sv39
   uarch: sifive,u74-mc
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1980386/+subscriptions


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

[Touch-packages] [Bug 1988548] Re: Missing fix for CVE-2022-37434 in zlib1g in focal and jammy

[Rodrigo Figueiredo Zaiden]

** Changed in: zlib (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1988548

Title:
  Missing fix for CVE-2022-37434 in zlib1g in focal and jammy

Status in zlib package in Ubuntu:
  In Progress

Bug description:
  There is a crictical security issue with zlib tracked here [1]

  The newest version in bionic [2] already has a security patch for it
  but the one in the focal [3] (and jammy) does not. As can be seen from
  their respective changelogs in the right hand side panel.

  Since zlib is loaded by lots of software, e.g. the apache weg server,
  this could be a problem. It seems that focal, jammy and bionic use the
  same base zlib version (1.2.11), so maybe the patch there could be
  recycled?

  I was asked to create a bug here after asking it as question here [4].
  Thank you very much for your hard work!

  [1] CVE: https://nvd.nist.gov/vuln/detail/CVE-2022-37434
  [2] Bionic Package: https://packages.ubuntu.com/bionic/zlib1g
  [3] Focal Package: https://packages.ubuntu.com/focal/zlib1g
  [4] Original Question: 
https://answers.launchpad.net/ubuntu/+source/zlib/+question/703010

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


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

[Touch-packages] [Bug 1981794] Re: Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~lvoytek/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/431606

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1981794

Title:
  Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  In Progress
Status in dnsmasq source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  When a DNS query fails to complete and the system retries it,
  subsequent copies of the query will be refused by dnsmasq. The client
  will automatically receive the REFUSED return value without a retry
  attempt.

  Adding this fix will stop dnsmasq from unnecessarily breaking
  connections, especially for situations where an internet connection is
  flaky.

  This bug is fixed by patching in an upstream commit -
  https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be
  - which allows retried DNS requests through rather than refusing them.

  [Test Plan]

  To test the error with lxd, run the following:

  # lxc launch images:ubuntu/jammy test-dnsmasq
  # lxc exec test-dnsmasq bash

  # apt update && apt dist-upgrade -y
  # systemctl disable systemd-resolved
  # systemctl stop systemd-resolved
  # unlink /etc/resolv.conf
  # echo nameserver 8.8.8.8 | tee /etc/resolv.conf
  # apt install dnsutils dnsmasq -y
  # systemctl enable dnsmasq

  Access internet through dnsmasq, flaky internet can be modeled by
  disconnecting from router, etc. This will lead to denial of DNS query
  retries.

  [Where problems could occur]

  This change was added upstream in version 2.87, which means it has not
  been tested in many situations alongside 2.86. Allowing the retries
  could lead to a flood of requests to remote DNS servers if the replies
  are unable to make it back through dnsmasq to the user.

  [Other Info]
   
  This bug was fixed in Kinetic in version 2.86-1.1ubuntu2.

  [Original Description]

  Duplicate or retried DNS queries will return REFUSED for one of the
  queries causing intermittent failures in clients.

  This probably breaks lots of things, but for me is causing 22.04's
  internet connection sharing to be unstable. It's particularly bad for
  my Xbox which seems to like sending duplicate queries.

  Here's an example capture:
  22:37:25.308212 IP 10.42.0.16.54248 > 10.42.0.1.53: 22442+ A? 
title.auth.xboxlive.com. (41)
  22:37:25.332711 IP 10.42.0.16.54248 > 10.42.0.1.53: 22442+ A? 
title.auth.xboxlive.com. (41)
  22:37:25.332740 IP 10.42.0.1.53 > 10.42.0.16.54248: 22442 Refused 0/0/0 (41)
  22:37:25.353003 IP 10.42.0.1.53 > 10.42.0.16.54248: 22442 2/0/0 CNAME 
title.auth.xboxlive.com.akadns.net., A 40.64.90.82 (105)

  This has been fixed in upstream as of Sept 2021 in the unreleased 2.87
  version. It's apparently a regression in version 2.86 (also released
  in Sept 2021). Ubuntu 22.04 and later all use the broken 2.86 version.

  Upstream fix:
  
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be1df48da1e2bd3d3feaa138c2

  Upstream bug thread:
  
https://www.mail-archive.com/search?l=dnsmasq-discuss%40lists.thekelleys.org.uk&q=subject:%22%5C%5BDnsmasq%5C-discuss%5C%5D+REFUSED+after+dropped+packets%22&o=oldest&f=1

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


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

[Touch-packages] [Bug 1981794] Re: Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)

[Lena Voytek]

** Description changed:

+ [Impact]
+ 
+ When a DNS query fails to complete and the system retries it, subsequent
+ copies of the query will be refused by dnsmasq. The client will
+ automatically receive the REFUSED return value without a retry attempt.
+ 
+ Adding this fix will stop dnsmasq from unnecessarily breaking
+ connections, especially for situations where an internet connection is
+ flaky.
+ 
+ This bug is fixed by patching in an upstream commit -
+ https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be
+ - which allows retried DNS requests through rather than refusing them.
+ 
+ [Test Plan]
+ 
+ To test the error with lxd, run the following:
+ 
+ # lxc launch images:ubuntu/jammy test-dnsmasq
+ # lxc exec test-dnsmasq bash
+ 
+ # apt update && apt dist-upgrade -y
+ # systemctl disable systemd-resolved
+ # systemctl stop systemd-resolved
+ # unlink /etc/resolv.conf
+ # echo nameserver 8.8.8.8 | tee /etc/resolv.conf
+ # apt install dnsutils dnsmasq -y
+ # systemctl enable dnsmasq
+ 
+ Access internet through dnsmasq, flaky internet can be modeled by
+ disconnecting from router, etc. This will lead to denial of DNS query
+ retries.
+ 
+ [Where problems could occur]
+ 
+ This change was added upstream in version 2.87, which means it has not
+ been tested in many situations alongside 2.86. Allowing the retries
+ could lead to a flood of requests to remote DNS servers if the replies
+ are unable to make it back through dnsmasq to the user.
+ 
+ [Other Info]
+  
+ This bug was fixed in Kinetic in version 2.86-1.1ubuntu2.
+ 
+ [Original Description]
+ 
  Duplicate or retried DNS queries will return REFUSED for one of the
  queries causing intermittent failures in clients.
  
  This probably breaks lots of things, but for me is causing 22.04's
  internet connection sharing to be unstable. It's particularly bad for my
  Xbox which seems to like sending duplicate queries.
  
  Here's an example capture:
  22:37:25.308212 IP 10.42.0.16.54248 > 10.42.0.1.53: 22442+ A? 
title.auth.xboxlive.com. (41)
  22:37:25.332711 IP 10.42.0.16.54248 > 10.42.0.1.53: 22442+ A? 
title.auth.xboxlive.com. (41)
  22:37:25.332740 IP 10.42.0.1.53 > 10.42.0.16.54248: 22442 Refused 0/0/0 (41)
  22:37:25.353003 IP 10.42.0.1.53 > 10.42.0.16.54248: 22442 2/0/0 CNAME 
title.auth.xboxlive.com.akadns.net., A 40.64.90.82 (105)
  
  This has been fixed in upstream as of Sept 2021 in the unreleased 2.87
  version. It's apparently a regression in version 2.86 (also released in
  Sept 2021). Ubuntu 22.04 and later all use the broken 2.86 version.
  
  Upstream fix:
  
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be1df48da1e2bd3d3feaa138c2
  
  Upstream bug thread:
  
https://www.mail-archive.com/search?l=dnsmasq-discuss%40lists.thekelleys.org.uk&q=subject:%22%5C%5BDnsmasq%5C-discuss%5C%5D+REFUSED+after+dropped+packets%22&o=oldest&f=1

** Changed in: dnsmasq (Ubuntu Jammy)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1981794

Title:
  Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  In Progress
Status in dnsmasq source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  When a DNS query fails to complete and the system retries it,
  subsequent copies of the query will be refused by dnsmasq. The client
  will automatically receive the REFUSED return value without a retry
  attempt.

  Adding this fix will stop dnsmasq from unnecessarily breaking
  connections, especially for situations where an internet connection is
  flaky.

  This bug is fixed by patching in an upstream commit -
  https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be
  - which allows retried DNS requests through rather than refusing them.

  [Test Plan]

  To test the error with lxd, run the following:

  # lxc launch images:ubuntu/jammy test-dnsmasq
  # lxc exec test-dnsmasq bash

  # apt update && apt dist-upgrade -y
  # systemctl disable systemd-resolved
  # systemctl stop systemd-resolved
  # unlink /etc/resolv.conf
  # echo nameserver 8.8.8.8 | tee /etc/resolv.conf
  # apt install dnsutils dnsmasq -y
  # systemctl enable dnsmasq

  Access internet through dnsmasq, flaky internet can be modeled by
  disconnecting from router, etc. This will lead to denial of DNS query
  retries.

  [Where problems could occur]

  This change was added upstream in version 2.87, which means it has not
  been tested in many situations alongside 2.86. Allowing the retries
  could lead to a flood of requests to remote DNS servers if the replies
  are unable to make it back through dnsmasq to the user.

  [Other Info]
   
  This bug was fixed in Kinetic in version 2.86-1.1ubuntu2.

  [Original Description]

  Duplicate or retried D

[Touch-packages] [Bug 1959832] Re: new version available upstream: 11.2

[themusicgod1]

** Changed in: gdb (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1959832

Title:
  new version available upstream: 11.2

Status in gdb package in Ubuntu:
  Fix Committed

Bug description:
  Release 11.2 of GDB, the GNU Debugger, is now available

  You can download GDB from the GNU FTP server in the directory:

  ftp://ftp.gnu.org/gnu/gdb

  GDB announcement https://www.sourceware.org/gdb/download/ANNOUNCEMENT

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdb 9.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  2 10:39:47 2022
  InstallationDate: Installed on 2017-04-18 (1750 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to focal on 2020-04-25 (648 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Touch-packages] [Bug 1993008] [NEW] ftbfs: E: fontconfig: alien-tag fc-cache-used-in-maintainer-script

[themusicgod1]

Public bug reported:

When trying to build from source using

debuild -us -uc -b

the result errors out with

Now running lintian fontconfig_2.13.1-4.4ubuntu1_amd64.changes ...
E: fontconfig: alien-tag fc-cache-used-in-maintainer-script 
[usr/share/lintian/overrides/fontconfig:1]
W: libfontconfig-doc: bad-whatis-entry 
[usr/share/man/man3/FcPatternIterNext.3.gz]

from:
https://www.mit.edu/afs.new/sipb/project/debathena/lintian/www/tags/fc-cache-used-in-maintainer-script.html

"This script apparently runs fc-cache. Updating of the fontconfig cache files 
is now handled automatically by triggers, so running fc-cache from maintainer 
scripts is no longer necessary."
  
 
ubuntu: kinetic kudu

libfontconfig1-dev:
  Installed: 2.13.1-4.4ubuntu1
  Candidate: 2.13.1-4.4ubuntu1
  Version table:
 *** 2.13.1-4.4ubuntu1 500
500 http://ubuntu.hysing.is/ubuntu kinetic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: libfontconfig-dev 2.13.1-4.4ubuntu1
Uname: Linux 6.0.1-gnulibre x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Oct 14 21:07:42 2022
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: fontconfig
UpgradeStatus: Upgraded to kinetic on 2022-10-14 (0 days ago)

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


** Tags: amd64 apport-bug ftbfs kinetic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1993008

Title:
  ftbfs: E: fontconfig: alien-tag fc-cache-used-in-maintainer-script

Status in fontconfig package in Ubuntu:
  New

Bug description:
  When trying to build from source using

  debuild -us -uc -b

  the result errors out with

  Now running lintian fontconfig_2.13.1-4.4ubuntu1_amd64.changes ...
  E: fontconfig: alien-tag fc-cache-used-in-maintainer-script 
[usr/share/lintian/overrides/fontconfig:1]
  W: libfontconfig-doc: bad-whatis-entry 
[usr/share/man/man3/FcPatternIterNext.3.gz]

  from:
  
https://www.mit.edu/afs.new/sipb/project/debathena/lintian/www/tags/fc-cache-used-in-maintainer-script.html

  "This script apparently runs fc-cache. Updating of the fontconfig cache files 
is now handled automatically by triggers, so running fc-cache from maintainer 
scripts is no longer necessary."

   
  ubuntu: kinetic kudu

  libfontconfig1-dev:
Installed: 2.13.1-4.4ubuntu1
Candidate: 2.13.1-4.4ubuntu1
Version table:
   *** 2.13.1-4.4ubuntu1 500
  500 http://ubuntu.hysing.is/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libfontconfig-dev 2.13.1-4.4ubuntu1
  Uname: Linux 6.0.1-gnulibre x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Oct 14 21:07:42 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to kinetic on 2022-10-14 (0 days ago)

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


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

[Touch-packages] [Bug 1979352] Re: system frozen after sleep

[Nick Rosbrook]

Please run apport-collect 1979352 so that the appropriate logs are
attached to the bug. Without proper logs, we will not be able to
investigate this issue.

** Changed in: ubuntu-mate
   Status: Confirmed => Incomplete

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1979352

Title:
  system frozen after sleep

Status in Ubuntu MATE:
  Incomplete
Status in acpid package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC
  2022 x86_64 x86_64 x86_64 GNU/Linux

  This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly 
but, at that time it was only apparent when I was using video ripping software 
on separate laptops and only when the machines became idle once the ripping 
program had finished.
  I don't think this bug was ever fixed and so I'm returning to it because I 
left my laptop in sleep mode over meal time to come back to a frozen system. I 
was not using the video ripping program this time, just surfing the Net. No 
other program was open.

  I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has
  happened when using an old Dell 1530 laptop.

  I do not believe I am unique in having this bug as someone has a
  similar bug when they have minimised Google Chrome and their system
  had went to sleep. I was also using Chrome this time but, as I have
  already said I was having this happen using another program and not
  using Chrome.

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


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

[Touch-packages] [Bug 1689381] Re: FTBFS cp: cannot stat 'doc/fontconfig-user.html'

[themusicgod1]

no longer fails on this in kinetic...( still ftbfs tho )

** Changed in: fontconfig (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1689381

Title:
  FTBFS cp: cannot stat 'doc/fontconfig-user.html'

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  while attempting to build with debuild:

  debuild -us -uc -b
  ...
  Adding cdbs dependencies to debian/libfontconfig1-dbg.substvars
  dh_installdirs -plibfontconfig1-dbg \

  dh_installdocs -pfontconfig ./README ./NEWS ./AUTHORS
  cp: cannot stat 'doc/fontconfig-user.html': No such file or directory
  dh_installdocs: cp --reflink=auto -a doc/fontconfig-user.html 
debian/fontconfig/usr/share/doc/fontconfig returned exit code 1
  /usr/share/cdbs/1/rules/debhelper.mk:235: recipe for target 
'binary-install/fontconfig' failed
  make: *** [binary-install/fontconfig] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
2
  debuild: fatal error at line 1116:
  dpkg-buildpackage -rfakeroot -us -uc -b failed
  z@aisha:~/fontconfig/fontconfig-2.11.94/debian$ 

  ubuntu: 17.10 artful
  libfontconfig1-dev:  2.11.94-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libfontconfig1-dev (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May  8 19:23:10 2017
  InstallationDate: Installed on 2016-05-07 (366 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to artful on 2017-05-08 (0 days ago)

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


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

[Touch-packages] [Bug 1992844] Re: apt download retries do not start at the 'root' but the redirect

[Nick Rosbrook]

It looks like you're running Raspbian, not Ubuntu. Please open a bug
with Raspbian instead.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1992844

Title:
  apt download retries do not start at the 'root' but the redirect

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I am running apt with exactly one source and with the retries=3 option
  that became standard.

  
  ~ $ cat /etc/apt/sources.list.d/raspi.list 
  deb http://raspbian.raspberrypi.org/raspbian bullseye main

  ~ $ apt --version
  apt 2.2.4 (arm64)

  $ sudo apt-get -oAcquire::ForceIPv6=true -oAcquire::Retries=3 install
  --reinstall adduser

  
  Now the host of the repo will reply with a mirror selection (i.e. http 302 
redirect). It so happens that the mirror selected is a ipv4 mirror and my 
machine is a ipv6 only machine, so there is no possible dns resolution. (force 
ipv6 was a trial, has no effect on my machine which is ipv6 only)

  Apt tries again 3 times, but only at the location of the redirect.

  For my understanding it should start at the original source, so it has
  a chance of getting a _different_ 302 redirect.


  Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
  Ign:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf 
adduser all 3.118
  Ign:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf 
adduser all 3.118
  Ign:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf 
adduser all 3.118
  Fehl:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian bullseye/main armhf 
adduser all 3.118
Beim Auflösen von »ftp.agdsn.de:http« ist etwas Schlimmes passiert (-5 - Zu 
diesem Hostnamen gehört keine Adresse).
  E: Fehlschlag beim Holen von 
http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian/pool/main/a/adduser/adduser_3.118_all.deb
 Beim Auflösen von »ftp.agdsn.de:http« ist etwas Schlimmes passiert (-5 - Zu 
diesem Hostnamen gehört keine Adresse). [ something wicked happened, no address 
for this hostname ]
  E: Einige Archive konnten nicht heruntergeladen werden; vielleicht »apt-get 
update« ausführen oder mit »--fix-missing« probieren?

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


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

[Touch-packages] [Bug 1269840] Re: ubuntu-bug ubuntu-bug doesn't work

[themusicgod1]

** Tags added: kinetic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1269840

Title:
  ubuntu-bug ubuntu-bug doesn't work

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-bug doesn't make program lookup when package lookup failed.
  This is inconvenient for users, who don't know about `which` command.
  Is it possible to automate lookup and continue search until something
  matches?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport 2.12.5-0ubuntu2.2
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  CrashReports:
   640:1000:122:1423125:2014-01-09 20:22:25.104739665 +0300:2014-01-09 
20:22:26.104739665 
+0300:/var/crash/_usr_lib_i386-linux-gnu_bamf_bamfdaemon.1000.crash
   640:1000:122:157297300:2014-01-09 20:56:44.036795854 +0300:2014-01-09 
20:56:45.036795854 +0300:/var/crash/_usr_bin_compiz.1000.crash
   640:0:122:4884804:2014-01-10 13:10:06.891414880 +0300:2014-01-10 
13:10:07.891414880 +0300:/var/crash/_usr_bin_Xorg.0.crash
  Date: Thu Jan 16 18:10:59 2014
  InstallationDate: Installed on 2012-03-12 (675 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (87 days ago)

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


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

[Touch-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Benjamin Gilbert]

Yup, the test program fails without the packages from the PPA and
succeeds once they're installed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pixman in Ubuntu.
https://bugs.launchpad.net/bugs/1988796

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  Fix Released
Status in pixman source package in Focal:
  Triaged

Bug description:
  [ Impact ]

  OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering
  backend, always with CAIRO_OPERATOR_SATURATE and sometimes with
  subpixel positioning (when reading certain file formats), and Cairo in
  turn invokes this code. As a result, some slides incorrectly render
  with large blank spaces and with some pixels rendered on top of other
  pixels. This effectively makes OpenSlide unusable for several of the
  file formats it supports. No workaround is believed possible within
  the OpenSlide codebase.

  [ Test Plan ]

  Compile and run the pixman.c test program uploaded to this bug. It
  should report "OK".

  [ Where problems could occur ]

  Problems would show up as incorrect pixel output from software that
  renders via Cairo or pixman.

  [ Other Info ]

  While I'm not a pixman expert, it appears that the change should only
  affect the broken code path, and it seems unlikely that anything else
  depends on the incorrect math fixed by this patch. This bug hasn't
  previously been reported in Ubuntu, which may imply that this code
  path is not exercised by other packages in the distro.

  The affected source file has had no further commits upstream since
  this patch was applied in April 2019, and some basic commit grepping
  didn't turn up any followup fixes elsewhere in the tree.

  [ Original message ]

  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

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


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

[Touch-packages] [Bug 1992731] Re: The cursor can be freely moved around and used to erase characters on the TTY while at the login prompt

[Nick Rosbrook]

I also confirmed this by testing a 22.04 VM with QEMU/KVM. I agree with
Alkis that this is agetty, so util-linux would be the appropriate
package.

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

** Changed in: util-linux (Ubuntu)
   Status: New => Confirmed

** Changed in: util-linux (Ubuntu)
   Importance: Undecided => Low

** Tags added: foundations-triage-discuss

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1992731

Title:
  The cursor can be freely moved around and used to erase characters on
  the TTY while at the login prompt

Status in shadow package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Welp, this is a weird one. Known to affect Ubuntu Server and multiple
  flavors of Ubuntu.

  Steps to reproduce:

  1: If you are shown a graphical login prompt (e.g. GDM or SDDM), switch to a 
TTY.
  2. At the login prompt, press the up arrow key twice.
  3: Press Backspace twice.
  4: Press Enter.

  Expected result: Nothing should happen, or possibly key codes should
  appear when the arrow keys are pressed, and those key codes should be
  erased when backspace is pressed.

  Actual result: The cursor moves up two lines when the up arrow key is
  pressed twice, and the "." and "4" of "22.04.1" are erased when
  Backspace is pressed twice. Upon pressing Enter, the TTY seems to
  freeze (no user input causes anything to happen), then the login
  prompt reverts back to its original state and the cursor assumes its
  proper location.

  Notes:
  This bug was first reported by a user named Liver_K on IRC as happening on 
Ubuntu Server 22.04 after upgrading from 20.04. alkisg then confirmed it on 
Ubuntu MATE 22.04, and I confirmed it on Kubuntu Focus Suite 22.04.

  Yes, you can indeed use this to erase everything in the TTY screen and
  leave the cursor in the upper-left corner as if the system was stuck.
  Pressing Enter resolves it after a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: login 1:4.8.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.17.0-1017.18-oem 5.17.15
  Uname: Linux 5.17.0-1017-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 13 00:44:03 2022
  InstallationDate: Installed on 2022-10-04 (8 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" (20220916)
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1992688] Re: firefox deb not installed

[Brian Murray]

I tested an upgrade from Jammy to Kinetic today (after the ubuntu-meta
change) and I saw that firefox was in the list of packages to be
installed during the upgrade.

Remove (was auto installed) gir1.2-mutter-10 gnome-bluetooth 
  gnome-todo-common libevent-2.1-7 libfwupdplugin5 libgnome-bg-4-1 
  libgnome-desktop-3-19 libgnome-desktop-4-1 libmutter-10-0 
  pipewire-media-session 


Install: at-spi2-common attr cpp-12 dbus-bin dbus-daemon 
  dbus-session-bus-common dbus-system-bus-common endeavour 
  endeavour-common firefox g++-12 gcc-12 gir1.2-gnomedesktop-4.0 
  gir1.2-gweather-4.0 gir1.2-javascriptcoregtk-4.1 gir1.2-mutter-11 

So no changes in ubuntu-release-upgrader are necessary to make this
work.

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

Title:
  firefox deb not installed

Status in firefox package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in firefox source package in Jammy:
  New
Status in ubuntu-meta source package in Jammy:
  New

Bug description:
  Bug 1964036 leads me to believe that the firefox deb provides some
  important functionality (the firefox favourite icon in the gnome shell
  dock) but there is nothing that would require the deb to be installed
  (it is not seeded nor has an rdep) and the package description
  indicates that it can be safely removed. Is there some important
  functionality that it provides?

  ProblemType: BugDistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 11:30:46 2022
  InstallationDate: Installed on 2022-04-27 (167 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago)
  VarLogDistupgradeTermlog:

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


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

[Touch-packages] [Bug 1992995] [NEW] Graphics

[Malak Diab]

Public bug reported:

I am trying to use MATLAB plots but no graphics are showing.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-128.144-generic 5.4.210
Uname: Linux 5.4.0-128-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 14 19:23:11 2022
DistUpgraded: 2020-11-09 21:29:05,838 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
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:081c]
InstallationDate: Installed on 2019-06-20 (1212 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Dell Inc. Latitude 7490
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-128-generic 
root=UUID=38ffaac9-4782-4848-b6e2-86ba57246327 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-11-09 (703 days ago)
dmi.bios.date: 01/07/2021
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 0KP0FT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd01/07/2021:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 7490
dmi.product.sku: 081C
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3
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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1992995

Title:
  Graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  I am trying to use MATLAB plots but no graphics are showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-128.144-generic 5.4.210
  Uname: Linux 5.4.0-128-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 14 19:23:11 2022
  DistUpgraded: 2020-11-09 21:29:05,838 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
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:081c]
  InstallationDate: Installed on 2019-06-20 (1212 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Latitude 7490
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-128-generic 
root=UUID=38ffaac9-4782-4848-b6e2-86ba57246327 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-09 (703 days ago)
  dmi.bios.date: 01/07/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd01/07/2021:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3
  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 

[Touch-packages] [Bug 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Colin Ian King]

Getting the same issue on the kinetic server daily image during the
install phase, see attached

** Attachment added: "issue during install"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992979/+attachment/5624145/+files/Screenshot%20from%202022-10-14%2018-01-37.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1992979

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

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


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

[Touch-packages] [Bug 1991829] Re: machinectl read-only does not work

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 251.4-1ubuntu7

---
systemd (251.4-1ubuntu7) kinetic; urgency=medium

  [ Nick Rosbrook ]
  * autopkgtest: do not allow qemu to be used on ppc64el (LP: #1992178)
Almost every run on ppc64el takes 12 to 24 hours, so do this as a last
resort to relieve pressure on autopkgtest infrastructure.
File: debian/tests/upstream

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5ab2b8ad13a3d7441935d6f43bb81fbd540e2c33

  [ Dan Streetman ]
  * make machinectl read-only work (LP: #1991829)
Author: Dan Streetman
File: 
debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a8a41b11d712c8cfbf595d34f39d95096f23e202

 -- Nick Rosbrook   Tue, 11 Oct 2022
11:51:25 -0400

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1991829

Title:
  machinectl read-only does not work

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Triaged
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [impact]

  machinectl read-only does not work

  [test case]

  On a system where the systemd machines dir is *not* on a btrfs volume
  (e.g. it's on a normal ext4 fs), create an image 'test' and then:

  $ sudo machinectl image-status test
  test
  Type: directory
  Path: /var/lib/machines/test
  Hostname: ubuntu
OS: Ubuntu 20.04.5 LTS
RO: writable
   Created: Wed 2022-10-05 13:41:15 EDT; 34s ago

  $ sudo machinectl read-only test
  Could not mark image read-only: Access denied

  [regression potential]

  failure marking images ro or rw

  [scope]

  this is needed in all releases that include machinectl

  this is fixed upstream by 137d162c42ed858613afc3d7493d08d4ae6d5c1b

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


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

[Touch-packages] [Bug 1992178] Re: autopkgtest: upstream tests that run in qemu hang on ppc64el

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 251.4-1ubuntu7

---
systemd (251.4-1ubuntu7) kinetic; urgency=medium

  [ Nick Rosbrook ]
  * autopkgtest: do not allow qemu to be used on ppc64el (LP: #1992178)
Almost every run on ppc64el takes 12 to 24 hours, so do this as a last
resort to relieve pressure on autopkgtest infrastructure.
File: debian/tests/upstream

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5ab2b8ad13a3d7441935d6f43bb81fbd540e2c33

  [ Dan Streetman ]
  * make machinectl read-only work (LP: #1991829)
Author: Dan Streetman
File: 
debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a8a41b11d712c8cfbf595d34f39d95096f23e202

 -- Nick Rosbrook   Tue, 11 Oct 2022
11:51:25 -0400

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1992178

Title:
  autopkgtest: upstream tests that run in qemu hang on ppc64el

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I believe this started early in the kinetic cycle, cf.
  https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs
  https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el.
  Timeouts in the upstream tests have been an issue for a while, but
  kinetic on ppc64el consistently times out with upstream tests that run
  in QEMU.

  Skipping individual tests does not help, because *which* tests time
  out appears to change with each build. For example, in 251.4-1ubuntu4
  the TEST-36-NUMAPOLICY test was consistently the culprit, but now in
  251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out.

  I have not been able to identify a root cause for this, but it seems
  that running tests in QEMU is very fragile on ppc64el, where as the
  tests that run in nspawn are more consistent.

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


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

[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information

[Michał Małoszewski]

First of all, I have changed the SRU description in 'Test Plan' section a bit, 
to be more precisely. We could assume the fix didn't work if I would leave it 
as it did before.
I've added information that we should look for the changes within the specific 
area in the manpage, so the steps are obvious now.

Fix works, package 1:8.2p1-4ubuntu0.6 fixes the bug.

I've created the focal container using steps from the [Test Plan]
section listed above in the Bug Description and inside that container I
typed in:

$ apt policy openssh-server

The output:

Installed: 1:8.2p1-4ubuntu0.5
  Candidate: 1:8.2p1-4ubuntu0.6
  Version table:
 1:8.2p1-4ubuntu0.6 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
 *** 1:8.2p1-4ubuntu0.5 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:8.2p1-4ubuntu0.2 500
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 1:8.2p1-4 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages


Then I have typed in:

$ man sshd_config 
and
$ man ssh_config

I've noticed that nothing has changed there. So the problem still
existed, because as we could see in the output, the package version was
not the one where the fix is.

Then I've upgraded both openssh-server and openssh-client using:
$ apt install openssh-server=1:8.2p1-4ubuntu0.6
$ apt install openssh-client=1:8.2p1-4ubuntu0.6

Later I've typed in:

$ apt policy openssh-server
to check if installed version is changed and we see that we have new version 
installed (with fix)

 Installed: 1:8.2p1-4ubuntu0.6
  Candidate: 1:8.2p1-4ubuntu0.6
  Version table:
 *** 1:8.2p1-4ubuntu0.6 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:8.2p1-4ubuntu0.5 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
 1:8.2p1-4ubuntu0.2 500
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 1:8.2p1-4 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages


Finally when I opened the manpage, typing:
$ man ssh_config

the problem did not exist, so the fix works.



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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1871465

Title:
  ssh_config(5) contains outdated information

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Hirsute:
  Won't Fix
Status in openssh source package in Impish:
  Won't Fix

Bug description:
  [Impact]

  The problem here is straightforward.
  The case is to fix manpages. They need to reflect a change done to the code 
some time ago. That problem might be annoying for users before being fixed.

  Backport upstream fix to Focal
  Origin:
  
https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636

  [Test Plan]

  Make a container for testing:

  First option:
  $ lxc launch ubuntu:focal focal-test
  $ lxc shell focal-test

  Simply install the openssh package using ‘apt install’ and check
  ssh_config and sshd_config.

  Acutal results:

  1. Create a container using steps from above.
  2. Type in man ssh_config and check that as well as the sshd_config.
  3. You should spot the ssh-rsa entries in the manpage within the 
CASignatureAlgorithms section.

  Expected results:

  1. Create a container using steps from above.
  2. Type in man ssh_config and check that as well as the sshd_config.
  3. You shouldn't spot the ssh-rsa entries in the manpage within the 
CASignatureAlgorithms section.

  [Where problems could occur]

  Any code change might change the behavior of the package in a specific
  situation and cause other errors.

  Next things which might cause regression are new dependencies which
  might not align and it is obvious the dependencies are upgraded and it
  might be a problem, but it is really unlikely.

  Even none of the rather generic cases above does apply here as we only
  change non-functional content in the form of the man page; Therefore
  the only risk is out of re-building the package which could pick up
  something from e.g. a changed toolchain.

  [Other Info]

  Fixing this is nice for the users, but OTOH very low severity and
  would cause a package download and update on almost every Ubuntu in
  the world. Therefore we will mark this as block-proposed and keep it
  in focal-proposed so that a later real update (security or functional)
  will pick this up from -proposed and then fix it in the field for
  real.

  original
  report---

  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list

[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information

[Michał Małoszewski]

** Description changed:

  [Impact]
  
  The problem here is straightforward.
  The case is to fix manpages. They need to reflect a change done to the code 
some time ago. That problem might be annoying for users before being fixed.
  
  Backport upstream fix to Focal
  Origin:
  
https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636
  
  [Test Plan]
  
  Make a container for testing:
  
  First option:
- $ lxc launch images:ubuntu/focal focal-test
+ $ lxc launch ubuntu:focal focal-test
  $ lxc shell focal-test
  
  Simply install the openssh package using ‘apt install’ and check
  ssh_config and sshd_config.
  
  Acutal results:
  
  1. Create a container using steps from above.
  2. Type in man ssh_config and check that as well as the sshd_config.
  3. You should spot the ssh-rsa entries in the manpage within the 
CASignatureAlgorithms section.
  
  Expected results:
  
  1. Create a container using steps from above.
  2. Type in man ssh_config and check that as well as the sshd_config.
  3. You shouldn't spot the ssh-rsa entries in the manpage within the 
CASignatureAlgorithms section.
  
  [Where problems could occur]
  
  Any code change might change the behavior of the package in a specific
  situation and cause other errors.
  
  Next things which might cause regression are new dependencies which
  might not align and it is obvious the dependencies are upgraded and it
  might be a problem, but it is really unlikely.
  
  Even none of the rather generic cases above does apply here as we only
  change non-functional content in the form of the man page; Therefore the
  only risk is out of re-building the package which could pick up
  something from e.g. a changed toolchain.
  
  [Other Info]
  
  Fixing this is nice for the users, but OTOH very low severity and would
  cause a package download and update on almost every Ubuntu in the world.
  Therefore we will mark this as block-proposed and keep it in focal-
  proposed so that a later real update (security or functional) will pick
  this up from -proposed and then fix it in the field for real.
  
  original
  report---
  
  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:
  
   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates
   by certificate authorities (CAs).  The default is:
  
     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  
   ssh(1) will not accept host certificates signed using algorithms
   other than those specified.
  
  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1871465

Title:
  ssh_config(5) contains outdated information

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Hirsute:
  Won't Fix
Status in openssh source package in Impish:
  Won't Fix

Bug description:
  [Impact]

  The problem here is straightforward.
  The case is to fix manpages. They need to reflect a change done to the code 
some time ago. That problem might be annoying for users before being fixed.

  Backport upstream fix to Focal
  Origin:
  
https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636

  [Test Plan]

  Make a container for testing:

  First option:
  $ lxc launch ubuntu:focal focal-test
  $ lxc shell focal-test

  Simply install the openssh package using ‘apt install’ and check
  ssh_config and sshd_config.

  Acutal results:

  1. Create a container using steps from above.
  2. Type in man ssh_config and check that as well as the sshd_config.
  3. You should spot the ssh-rsa entries in the manpage within the 
CASignatureAlgorithms section.

  Expected results:

  1. Create a container using steps from above.
  2. Type in man ssh_config and check that as well as the sshd_config.
  3. You shouldn't spot the ssh-rsa entries in the manpage within the 
CASignatureAlgorithms section.

  [Where problems could occur]

  Any code change might change the behavior of the package in a specific
  situation and cause other errors.

  Next things which might cause regression are new dependencies which
  might not align and it is obvious the dependencies are upgraded and it
  might be a problem, but it is really unlikely.

  Even none of the rather generic cases above does apply here as we only
  change non-functional content in the form of the 

[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information

[Michał Małoszewski]

** Description changed:

  [Impact]
  
  The problem here is straightforward.
  The case is to fix manpages. They need to reflect a change done to the code 
some time ago. That problem might be annoying for users before being fixed.
  
  Backport upstream fix to Focal
  Origin:
  
https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636
  
  [Test Plan]
  
  Make a container for testing:
  
  First option:
- $ lxc launch images:ubuntu/bionic focal-test
+ $ lxc launch images:ubuntu/focal focal-test
  $ lxc shell focal-test
  
- Simply install the openssh package using ‘apt install’ and check both
- ssh_config.5 and sshd_config.5 files.
+ Simply install the openssh package using ‘apt install’ and check
+ ssh_config and sshd_config.
  
  Acutal results:
  
  1. Create a container using steps from above.
- 2. Type in man sshd_config.
- 3. You should spot the ssh-rsa entries in the manpage.
+ 2. Type in man ssh_config and check that as well as the sshd_config.
+ 3. You should spot the ssh-rsa entries in the manpage within the 
CASignatureAlgorithms section.
  
  Expected results:
  
  1. Create a container using steps from above.
- 2. Type in man sshd_config.
- 3. You shouldn't spot the ssh-rsa entries in the manpage.
+ 2. Type in man ssh_config and check that as well as the sshd_config.
+ 3. You shouldn't spot the ssh-rsa entries in the manpage within the 
CASignatureAlgorithms section.
  
  [Where problems could occur]
  
  Any code change might change the behavior of the package in a specific
  situation and cause other errors.
  
  Next things which might cause regression are new dependencies which
  might not align and it is obvious the dependencies are upgraded and it
  might be a problem, but it is really unlikely.
  
  Even none of the rather generic cases above does apply here as we only
  change non-functional content in the form of the man page; Therefore the
  only risk is out of re-building the package which could pick up
  something from e.g. a changed toolchain.
  
  [Other Info]
  
  Fixing this is nice for the users, but OTOH very low severity and would
  cause a package download and update on almost every Ubuntu in the world.
  Therefore we will mark this as block-proposed and keep it in focal-
  proposed so that a later real update (security or functional) will pick
  this up from -proposed and then fix it in the field for real.
  
  original
  report---
  
  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:
  
   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates
   by certificate authorities (CAs).  The default is:
  
     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  
   ssh(1) will not accept host certificates signed using algorithms
   other than those specified.
  
  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1871465

Title:
  ssh_config(5) contains outdated information

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Hirsute:
  Won't Fix
Status in openssh source package in Impish:
  Won't Fix

Bug description:
  [Impact]

  The problem here is straightforward.
  The case is to fix manpages. They need to reflect a change done to the code 
some time ago. That problem might be annoying for users before being fixed.

  Backport upstream fix to Focal
  Origin:
  
https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636

  [Test Plan]

  Make a container for testing:

  First option:
  $ lxc launch images:ubuntu/focal focal-test
  $ lxc shell focal-test

  Simply install the openssh package using ‘apt install’ and check
  ssh_config and sshd_config.

  Acutal results:

  1. Create a container using steps from above.
  2. Type in man ssh_config and check that as well as the sshd_config.
  3. You should spot the ssh-rsa entries in the manpage within the 
CASignatureAlgorithms section.

  Expected results:

  1. Create a container using steps from above.
  2. Type in man ssh_config and check that as well as the sshd_config.
  3. You shouldn't spot the ssh-rsa entries in the manpage within the 
CASignatureAlgorithms section.

  [Where problems could occur]

  Any code change might change the behavior of the package in a specific
  situation and cause other errors.

  Next things

[Touch-packages] [Bug 1980386] Re: `radeonsi_dri.so` driver missing on riscv64

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 22.2.1-1ubuntu1

---
mesa (22.2.1-1ubuntu1) kinetic; urgency=medium

  * Merge from Debian. (LP: #1992656)

 -- Timo Aaltonen   Wed, 12 Oct 2022 17:10:22 +0300

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1980386

Title:
  `radeonsi_dri.so` driver missing on riscv64

Status in llvm-toolchain-15 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in llvm-toolchain-15 source package in Jammy:
  In Progress
Status in mesa source package in Jammy:
  Confirmed
Status in llvm-toolchain-15 source package in Kinetic:
  Fix Released
Status in mesa source package in Kinetic:
  Fix Released

Bug description:
  The package is missing the `radeonsi` driver, with the reasoning that
  LLVM is not implemented on the architecture:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618

  That said, it works just fine on focal, where it is still enabled.
  Without this driver there's no way to use AMD graphics cards on
  RISC-V.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.1-1ubuntu2
  ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30
  Uname: Linux 5.15.0-1007-generic riscv64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  Date: Thu Jun 30 15:48:11 2022
  ProcCpuinfoMinimal:
   processor: 3
   hart : 4
   isa  : rv64imafdc
   mmu  : sv39
   uarch: sifive,u74-mc
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1980386/+subscriptions


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

[Touch-packages] [Bug 1992656] Re: FFE: Mesa 22.2.1

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 22.2.1-1ubuntu1

---
mesa (22.2.1-1ubuntu1) kinetic; urgency=medium

  * Merge from Debian. (LP: #1992656)

 -- Timo Aaltonen   Wed, 12 Oct 2022 17:10:22 +0300

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1992656

Title:
  FFE: Mesa 22.2.1

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  This is a minor bugfix release, and also enables llvm for riscv64 (LP:
  #1980386).

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


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

[Touch-packages] [Bug 1992690] Re: Fix large thumbnails with Nautilus

[Launchpad Bug Tracker]

This bug was fixed in the package glib2.0 - 2.74.0-3

---
glib2.0 (2.74.0-3) unstable; urgency=medium

  * Cherry-pick 2 patches to fix large thumbnails with Nautilus
(Closes: #1021588) (LP: #1992690)

 -- Jeremy Bicha   Wed, 12 Oct 2022 14:43:19 -0400

** Changed in: glib2.0 (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1992690

Title:
  Fix large thumbnails with Nautilus

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  Impact
  --

  Copying this report from Debian.

  I have a 4K monitor with 175% fractional scaling.

  Nautilus 43 broke hi-dpi thumbnailing [1], and goes into an infinite
  loop trying to create x-large and xx-large thumbnails, consuming CPU
  forever.

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


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

[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information

[Michał Małoszewski]

** Description changed:

  [Impact]
  
- The problem here is straightforward. 
- The case is to fix manpages. They need to reflect a change done to the code 
some time ago. That problem might be annoying for users before being fixed. 
+ The problem here is straightforward.
+ The case is to fix manpages. They need to reflect a change done to the code 
some time ago. That problem might be annoying for users before being fixed.
  
  Backport upstream fix to Focal
- Origin: 
+ Origin:
  
https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636
- 
  
  [Test Plan]
  
  Make a container for testing:
  
  First option:
  $ lxc launch images:ubuntu/bionic focal-test
  $ lxc shell focal-test
  
- Simply install the openssh package using ‘apt install’ and check both 
ssh_config.5 and sshd_config.5 files. You should be able to spot the ‘ssh_rsa’ 
in these files.
-  
+ Simply install the openssh package using ‘apt install’ and check both
+ ssh_config.5 and sshd_config.5 files.
  
+ Acutal results:
+ 
+ 1. Create a container using steps from above.
+ 2. Type in man sshd_config.
+ 3. You should spot the ssh-rsa entries in the manpage.
+ 
+ Expected results:
+ 
+ 1. Create a container using steps from above.
+ 2. Type in man sshd_config.
+ 3. You shouldn't spot the ssh-rsa entries in the manpage.
  
  [Where problems could occur]
  
  Any code change might change the behavior of the package in a specific
  situation and cause other errors.
  
  Next things which might cause regression are new dependencies which
  might not align and it is obvious the dependencies are upgraded and it
  might be a problem, but it is really unlikely.
  
  Even none of the rather generic cases above does apply here as we only
  change non-functional content in the form of the man page; Therefore the
  only risk is out of re-building the package which could pick up
  something from e.g. a changed toolchain.
  
- 
  [Other Info]
  
- 
- Fixing this is nice for the users, but OTOH very low severity and would cause 
a package download and update on almost every Ubuntu in the world. Therefore we 
will mark this as block-proposed and keep it in focal-proposed so that a later 
real update (security or functional) will pick this up from -proposed and then 
fix it in the field for real.
+ Fixing this is nice for the users, but OTOH very low severity and would
+ cause a package download and update on almost every Ubuntu in the world.
+ Therefore we will mark this as block-proposed and keep it in focal-
+ proposed so that a later real update (security or functional) will pick
+ this up from -proposed and then fix it in the field for real.
  
  original
  report---
  
  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:
  
   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates
   by certificate authorities (CAs).  The default is:
  
     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  
   ssh(1) will not accept host certificates signed using algorithms
   other than those specified.
  
  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1871465

Title:
  ssh_config(5) contains outdated information

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Focal:
  Fix Committed
Status in openssh source package in Hirsute:
  Won't Fix
Status in openssh source package in Impish:
  Won't Fix

Bug description:
  [Impact]

  The problem here is straightforward.
  The case is to fix manpages. They need to reflect a change done to the code 
some time ago. That problem might be annoying for users before being fixed.

  Backport upstream fix to Focal
  Origin:
  
https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636

  [Test Plan]

  Make a container for testing:

  First option:
  $ lxc launch images:ubuntu/bionic focal-test
  $ lxc shell focal-test

  Simply install the openssh package using ‘apt install’ and check both
  ssh_config.5 and sshd_config.5 files.

  Acutal results:

  1. Create a container using steps from above.
  2. Type in man sshd_config.
  3. You should spot the ssh-rsa entries in the manpage.

  Expected results:

  1. Create a container using steps from above.
  2. Type in man sshd_config.
  3. You shouldn't spot the ssh-rsa entries in the manpage.

  [Where problems could occur]

  Any code change 

[Touch-packages] [Bug 1992206] Re: bash: non existent locale crashes bash

[Nick Rosbrook]

This was fixed in Ubuntu
(https://launchpad.net/ubuntu/+source/bash/5.2-1ubuntu2):

bash (5.2-1ubuntu2) kinetic; urgency=medium

  * debian/patches: Import two upstream patches to fix crashes:
  - Bash-5.2-patch-1-fix-crash-with-unset-arrays-in-arit.diff
  - Bash-5.2-patch-2-fix-crash-in-readline-when-started-.diff (LP:#1992206)

 -- Nick Rosbrook   Fri, 07 Oct 2022
17:03:05 -0400

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

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

** Tags removed: foundations-todo

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1992206

Title:
  bash: non existent locale crashes bash

Status in bash package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bash package in Debian:
  Confirmed

Bug description:
  Imported from Debian bug http://bugs.debian.org/1021109:

  Package: libc6
  Version: 2.35-1
  Severity: grave
  Justification: renders package unusable
  X-Debbugs-Cc: kos...@debian.org

  Dear maintainer,

  After upgrading to libc6 2.35-1 (or 2.36-1 in experimental), nonexistent 
locale setting
  starts to crash the system.

  This is dangerous because a remote system might not always have the same 
locale installed.
  An auto update will soft-brick the system unless the sysadmin knows to set 
their LC_ALL=POSIX
  before attempting to ssh.

  Steps to reproduce:

  From a clean installed Debian sid, upgrade to libc6 2.35-1.
  Only install C locale and en_US.UTF-8.

  $ LC_ALL=ja_JP.UTF-8 bash
  bash: warning: setlocale: LC_ALL: cannot change locale (ja_JP.UTF-8)
  Segmentation fault (core dumped)

  $ LC_ALL=ja_JP.UTF-8 gdb bash

  Fatal signal: Segmentation fault
  - Backtrace -
  0x55ed3e1e8dcf ???
  0x55ed3e2df312 ???
  0x55ed3e2df488 ???
  0x7f0b4a39ba9f ???
  0x7f0b4b412204 _rl_init_locale
  0x7f0b4b4122f1 _rl_init_eightbit
  0x7f0b4b3f10f2 rl_initialize
  ... snip ...

  Downgrade to 2.34-8 seems also don't fix the issue, probably some locale
  state was invalidated when upgrading.

  Thanks,
  Kan-Ru

  
  -- System Information:
  Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
  Architecture: amd64 (x86_64)

  Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  Versions of packages libc6 depends on:
  ii  libgcc-s1  12.2.0-3

  Versions of packages libc6 recommends:
  ii  libidn2-0  2.3.3-1+b1

  Versions of packages libc6 suggests:
  ii  debconf [debconf-2.0]  1.5.79
  pn  glibc-doc  
  ii  libc-l10n  2.35-1
  pn  libnss-nis 
  pn  libnss-nisplus 
  ii  locales2.35-1

  -- debconf information:
glibc/kernel-too-old:
glibc/restart-failed:
glibc/disable-screensaver:
glibc/upgrade: true
  * libraries/restart-without-asking: false
  * glibc/restart-services: cron
glibc/kernel-not-supported:

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


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

[Touch-packages] [Bug 1992947] Re: gdb fails in Ubuntu-22.04

[Brian Murray]

** Package changed: ubuntu => gdb (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1992947

Title:
  gdb fails in Ubuntu-22.04

Status in gdb package in Ubuntu:
  New

Bug description:
  In Jammy 5.15.0-1014 when i try to debug an application with gdb got
  below error,

  Log:
  root@kria:/home/ubuntu/swetha_bins/v2xpfm# gdb threshold
  Could not find platform independent libraries 
  Could not find platform dependent libraries 
  Consider setting $PYTHONHOME to [:]
  Python path configuration:
PYTHONHOME = (not set)
PYTHONPATH = (not set)
program name = '/usr/bin/python'
isolated = 0
environment = 1
user site = 1
import site = 1
sys._base_executable = '/usr/bin/python'
sys.base_prefix = '/usr'
sys.base_exec_prefix = '/usr'
sys.platlibdir = 'lib'
sys.executable = '/usr/bin/python'
sys.prefix = '/usr'
sys.exec_prefix = '/usr'
sys.path = [
  '/usr/lib/python39.zip',
  '/usr/lib/python3.9',
  '/usr/lib/lib-dynload',
]
  Fatal Python error: init_fs_encoding: failed to get the Python codec of the 
filesystem encoding
  Python runtime state: core initialized
  ModuleNotFoundError: No module named 'encodings'

  Current thread 0xa057f020 (most recent call first):
  
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#
  root@kria:/home/ubuntu/swetha_bins/v2xpfm# uname -a
  Linux kria 5.15.0-1014-xilinx-zynqmp #15-Ubuntu SMP Tue Aug 30 07:56:28 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#
  root@kria:/home/ubuntu/swetha_bins/v2xpfm# file threshold
  threshold: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (GNU/Linux), 
dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, 
BuildID[sha1]=ae073c5ee47a3663ef3a06861c5df9bf62147ecd, for GNU/Linux 3.14.0, 
with debug_info, not stripped
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#
  root@kria:/home/ubuntu/swetha_bins/v2xpfm#

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


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

[Touch-packages] [Bug 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Andrea Righi]

It could be related to #1991691 if you're using the kernel currently in
release.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1992979

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

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


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

[Touch-packages] [Bug 1992979] [NEW] kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Colin Ian King]

Public bug reported:

Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU, single
CPU, 1GB memory, rebooted, can NO longer login. Stuck in systems boot
phase.

Attached is an image of the hang

** Affects: systemd (Ubuntu)
 Importance: Critical
 Status: New

** Attachment added: "jpg of hang in boot"
   
https://bugs.launchpad.net/bugs/1992979/+attachment/5624126/+files/Screenshot%20from%202022-10-14%2014-47-42.png

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1992979

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

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


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

[Touch-packages] [Bug 1992947] [NEW] gdb fails in Ubuntu-22.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In Jammy 5.15.0-1014 when i try to debug an application with gdb got
below error,

Log:
root@kria:/home/ubuntu/swetha_bins/v2xpfm# gdb threshold
Could not find platform independent libraries 
Could not find platform dependent libraries 
Consider setting $PYTHONHOME to [:]
Python path configuration:
  PYTHONHOME = (not set)
  PYTHONPATH = (not set)
  program name = '/usr/bin/python'
  isolated = 0
  environment = 1
  user site = 1
  import site = 1
  sys._base_executable = '/usr/bin/python'
  sys.base_prefix = '/usr'
  sys.base_exec_prefix = '/usr'
  sys.platlibdir = 'lib'
  sys.executable = '/usr/bin/python'
  sys.prefix = '/usr'
  sys.exec_prefix = '/usr'
  sys.path = [
'/usr/lib/python39.zip',
'/usr/lib/python3.9',
'/usr/lib/lib-dynload',
  ]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the 
filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0xa057f020 (most recent call first):

root@kria:/home/ubuntu/swetha_bins/v2xpfm#
root@kria:/home/ubuntu/swetha_bins/v2xpfm#
root@kria:/home/ubuntu/swetha_bins/v2xpfm# uname -a
Linux kria 5.15.0-1014-xilinx-zynqmp #15-Ubuntu SMP Tue Aug 30 07:56:28 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux
root@kria:/home/ubuntu/swetha_bins/v2xpfm#
root@kria:/home/ubuntu/swetha_bins/v2xpfm#
root@kria:/home/ubuntu/swetha_bins/v2xpfm# file threshold
threshold: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (GNU/Linux), 
dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, 
BuildID[sha1]=ae073c5ee47a3663ef3a06861c5df9bf62147ecd, for GNU/Linux 3.14.0, 
with debug_info, not stripped
root@kria:/home/ubuntu/swetha_bins/v2xpfm#
root@kria:/home/ubuntu/swetha_bins/v2xpfm#
root@kria:/home/ubuntu/swetha_bins/v2xpfm#

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


** Tags: bot-comment
-- 
gdb fails in Ubuntu-22.04
https://bugs.launchpad.net/bugs/1992947
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gdb in Ubuntu.

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

[Touch-packages] [Bug 1992930] Re: chromium won't launch at menu when installed; lubuntu kinetic

[Chris Guiver]

** Description changed:

  Lubuntu kinetic live test
  
  `chromium` snap once installed; will not open from menu, but will open
  if started from terminal.  This maybe filed against incorrect package
  sorry.
  
  Originally reported here - https://discourse.lubuntu.me/t/lubuntu-
  kinetic-after-5-19-update-chromium-only-start-from-terminal/3685 where
  it was reported as an issue on the 5.19.0-19-generic kernel update
  
  ** to re-create
  
  - boot currently lubuntu kinetic daily
  - snap install chromium
  - using menu, attempt to run chromium from internet apps
  
  ** expected outcome
  
  chromium starts
  
  ** actual outcome
  
  menu just closes; no messages.
  
  ** further notes
  
  u/FossFreedom (Ubuntu Budgie) reports no issues with Ubuntu Budgie
  kinetic starting Chromium.
  
- On Lubuntu's discourse; u/neblaz (OP for issue) also reported issues
- starting Opera; I've asked what package type & from where.
+ On Lubuntu's discourse; u/neblaz (OP for issue) also reported issues starting 
Opera; with that package being the snap (loaded from discover) and reported as 
(using `snap list`)
+ opera   91.0.4516.77202
latest/stable
  
  
  ** in `dmesg` I note the following (this may be unrelated or unhelpful sorry)
  
  [ 1510.255228] loop7: detected capacity change from 0 to 293648
  [ 1510.739240] audit: type=1400 audit(1665727470.633:54): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap-update-ns.chromium" 
pid=3359 comm="apparmor_parser"
  [ 1510.820094] audit: type=1400 audit(1665727470.713:55): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap.chromium.chromedriver" 
pid=3360 comm="apparmor_parser"
  [ 1511.014103] audit: type=1400 audit(1665727470.909:56): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap.chromium.chromium" 
pid=3361 comm="apparmor_parser"
  [ 1511.071575] audit: type=1400 audit(1665727470.965:57): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="snap.chromium.hook.configure" pid=3362 comm="apparmor_parser"
  [ 1515.313383] audit: type=1400 audit(1665727475.206:58): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="/snap/snapd/17029/usr/lib/snapd/snap-confine" 
pid=3496 comm="apparmor_parser"
  [ 1515.313401] audit: type=1400 audit(1665727475.206:59): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" 
name="/snap/snapd/17029/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
 pid=3496 comm="apparmor_parser"
  [ 1516.817149] audit: type=1400 audit(1665727476.710:60): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap-update-ns.chromium" 
pid=3498 comm="apparmor_parser"
  [ 1518.067335] audit: type=1400 audit(1665727477.962:61): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="snap.chromium.chromedriver" pid=3499 comm="apparmor_parser"
  [ 1518.568962] audit: type=1400 audit(1665727478.462:62): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="snap.chromium.hook.configure" pid=3501 comm="apparmor_parser"
  [ 1519.485025] audit: type=1400 audit(1665727479.378:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.chromium.chromium" 
pid=3500 comm="apparmor_parser"
  [ 1520.203518] audit: type=1400 audit(1665727480.098:64): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/meta/snap.yaml" pid=3518 comm="6" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  [ 1520.245234] audit: type=1400 audit(1665727480.142:65): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/fonts/" pid=3518 comm="6" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 1520.245256] audit: type=1400 audit(1665727480.142:66): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/" pid=3518 comm="6" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  [ 1520.246876] audit: type=1400 audit(1665727480.142:67): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/var/lib/snapd/hostfs/usr/share/doc/" pid=3518 comm="6" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 1520.246933] audit: type=1400 audit(1665727480.142:68): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/var/lib/snapd/hostfs/usr/share/fonts/" pid=3518 comm="6" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 1520.349971] audit: type=1400 audit(1665727480.246:69): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/fonts/" pid=3518 comm="6" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 1628.635260] kauditd_printk_skb: 6 callbacks suppressed
  [ 1

[Touch-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Athos Ribeiro]

Thanks, Benjamin!

I uploaded a patched package to the following PPA:
https://launchpad.net/~athos-ribeiro/+archive/ubuntu/lp1988796-pixman

Please, test it to ensure everything works as expected before we proceed
with the SRU process here.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pixman in Ubuntu.
https://bugs.launchpad.net/bugs/1988796

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  Fix Released
Status in pixman source package in Focal:
  Triaged

Bug description:
  [ Impact ]

  OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering
  backend, always with CAIRO_OPERATOR_SATURATE and sometimes with
  subpixel positioning (when reading certain file formats), and Cairo in
  turn invokes this code. As a result, some slides incorrectly render
  with large blank spaces and with some pixels rendered on top of other
  pixels. This effectively makes OpenSlide unusable for several of the
  file formats it supports. No workaround is believed possible within
  the OpenSlide codebase.

  [ Test Plan ]

  Compile and run the pixman.c test program uploaded to this bug. It
  should report "OK".

  [ Where problems could occur ]

  Problems would show up as incorrect pixel output from software that
  renders via Cairo or pixman.

  [ Other Info ]

  While I'm not a pixman expert, it appears that the change should only
  affect the broken code path, and it seems unlikely that anything else
  depends on the incorrect math fixed by this patch. This bug hasn't
  previously been reported in Ubuntu, which may imply that this code
  path is not exercised by other packages in the distro.

  The affected source file has had no further commits upstream since
  this patch was applied in April 2019, and some basic commit grepping
  didn't turn up any followup fixes elsewhere in the tree.

  [ Original message ]

  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

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


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

[Touch-packages] [Bug 1992968] nmcli-dev.txt

[Heinrich Schuchardt]

apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1992968/+attachment/5624111/+files/nmcli-dev.txt

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

Title:
  nmcli disconnect leads to segmentation fault

Status in network-manager package in Ubuntu:
  New

Bug description:
  Disconnecting the WLAN on riscv64 (LicheeRV with driver licheerv-
  rtl8723ds-dkms) leads to a segmentation fault:

  $ sudo nmcli -a d  disconnect
  Interface(s): wlan0
  Segmentation fault

  Oct 14 12:17:48 ubuntu kernel: [ 5672.571893] nmcli[6918]: unhandled signal 
11 code 0x1 at 0x002af65cb856 in libc.so.6[3f80746000+126000]
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571971] CPU: 0 PID: 6918 Comm: nmcli 
Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571988] Hardware name: Sipeed Lichee RV 
Dock (DT)
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571997] epc : 003f807bca18 ra : 
003f809221e4 sp : 003feebe7550
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572011]  gp : 002ac9a46b48 tp : 
003f8004d780 t0 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572024]  t1 : 003f808dc74c t2 : 
001a s0 : 002af4f3e420
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572036]  s1 : 002af4f3e410 a0 : 
002af65cb85e a1 : 002af4eac010
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572047]  a2 : 002af4f3f760 a3 : 
0002 a4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572059]  a5 :  a6 : 
002af4f3e410 a7 : fc164803c80b4e4b
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572070]  s2 : 002af4f14290 s3 : 
0001 s4 : 003feebe75a4
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572082]  s5 : 002af4f1fb00 s6 : 
002af4f02e80 s7 : 0001
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572093]  s8 : 002ac99fefe8 s9 : 
002af4f3e410 s10: 003f80c73d30
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572105]  s11: 003f809b4368 t3 : 
003f807bca14 t4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572117]  t5 : 0020 t6 : 
000a
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572126] status: 80026020 
badaddr: 002af65cb856 cause: 000d
  Oct 14 12:20:19 ubuntu wpa_supplicant[661]: wlan0: WPA: Group rekeying 
completed with 2c:91:ab:91:c5:77 [GTK=CCMP]
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: riscv64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IpRoute:
   default via 192.168.123.254 dev enx00e04d680306 proto dhcp src 
192.168.123.75 metric 100 
   default via 192.168.123.254 dev wlan0 proto dhcp src 192.168.123.76 metric 
600 
   192.168.123.0/24 dev enx00e04d680306 proto kernel scope link src 
192.168.123.75 metric 100 
   192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.76 metric 
600 
   192.168.123.254 dev enx00e04d680306 proto dhcp scope link src 192.168.123.75 
metric 100
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Package: network-manager 1.40.0-1ubuntu2
  PackageArchitecture: riscv64
  PciNetwork:
   
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15
  RebootRequiredPkgs: Error: path contained symlinks.
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic uec-images
  Uname: Linux 5.17.0-1003-allwinner riscv64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-10-14T12:28:44.227533
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   rxuZdtJmykLvLBiu  29060cbf-0727-4904-813c-5a7e54055c80  wifi  1665749804  
Fri Oct 14 12:16:44 2022  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/rxuZdtJmykLvLBiu.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug

[Touch-packages] [Bug 1992968] NetDevice.enx00e04d680306.txt

[Heinrich Schuchardt]

apport information

** Attachment added: "NetDevice.enx00e04d680306.txt"
   
https://bugs.launchpad.net/bugs/1992968/+attachment/5624105/+files/NetDevice.enx00e04d680306.txt

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

Title:
  nmcli disconnect leads to segmentation fault

Status in network-manager package in Ubuntu:
  New

Bug description:
  Disconnecting the WLAN on riscv64 (LicheeRV with driver licheerv-
  rtl8723ds-dkms) leads to a segmentation fault:

  $ sudo nmcli -a d  disconnect
  Interface(s): wlan0
  Segmentation fault

  Oct 14 12:17:48 ubuntu kernel: [ 5672.571893] nmcli[6918]: unhandled signal 
11 code 0x1 at 0x002af65cb856 in libc.so.6[3f80746000+126000]
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571971] CPU: 0 PID: 6918 Comm: nmcli 
Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571988] Hardware name: Sipeed Lichee RV 
Dock (DT)
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571997] epc : 003f807bca18 ra : 
003f809221e4 sp : 003feebe7550
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572011]  gp : 002ac9a46b48 tp : 
003f8004d780 t0 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572024]  t1 : 003f808dc74c t2 : 
001a s0 : 002af4f3e420
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572036]  s1 : 002af4f3e410 a0 : 
002af65cb85e a1 : 002af4eac010
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572047]  a2 : 002af4f3f760 a3 : 
0002 a4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572059]  a5 :  a6 : 
002af4f3e410 a7 : fc164803c80b4e4b
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572070]  s2 : 002af4f14290 s3 : 
0001 s4 : 003feebe75a4
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572082]  s5 : 002af4f1fb00 s6 : 
002af4f02e80 s7 : 0001
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572093]  s8 : 002ac99fefe8 s9 : 
002af4f3e410 s10: 003f80c73d30
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572105]  s11: 003f809b4368 t3 : 
003f807bca14 t4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572117]  t5 : 0020 t6 : 
000a
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572126] status: 80026020 
badaddr: 002af65cb856 cause: 000d
  Oct 14 12:20:19 ubuntu wpa_supplicant[661]: wlan0: WPA: Group rekeying 
completed with 2c:91:ab:91:c5:77 [GTK=CCMP]
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: riscv64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IpRoute:
   default via 192.168.123.254 dev enx00e04d680306 proto dhcp src 
192.168.123.75 metric 100 
   default via 192.168.123.254 dev wlan0 proto dhcp src 192.168.123.76 metric 
600 
   192.168.123.0/24 dev enx00e04d680306 proto kernel scope link src 
192.168.123.75 metric 100 
   192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.76 metric 
600 
   192.168.123.254 dev enx00e04d680306 proto dhcp scope link src 192.168.123.75 
metric 100
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Package: network-manager 1.40.0-1ubuntu2
  PackageArchitecture: riscv64
  PciNetwork:
   
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15
  RebootRequiredPkgs: Error: path contained symlinks.
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic uec-images
  Uname: Linux 5.17.0-1003-allwinner riscv64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-10-14T12:28:44.227533
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   rxuZdtJmykLvLBiu  29060cbf-0727-4904-813c-5a7e54055c80  wifi  1665749804  
Fri Oct 14 12:16:44 2022  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/rxuZdtJmykLvLBiu.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To man

[Touch-packages] [Bug 1992968] WifiSyslog.txt

[Heinrich Schuchardt]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1992968/+attachment/5624110/+files/WifiSyslog.txt

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

Title:
  nmcli disconnect leads to segmentation fault

Status in network-manager package in Ubuntu:
  New

Bug description:
  Disconnecting the WLAN on riscv64 (LicheeRV with driver licheerv-
  rtl8723ds-dkms) leads to a segmentation fault:

  $ sudo nmcli -a d  disconnect
  Interface(s): wlan0
  Segmentation fault

  Oct 14 12:17:48 ubuntu kernel: [ 5672.571893] nmcli[6918]: unhandled signal 
11 code 0x1 at 0x002af65cb856 in libc.so.6[3f80746000+126000]
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571971] CPU: 0 PID: 6918 Comm: nmcli 
Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571988] Hardware name: Sipeed Lichee RV 
Dock (DT)
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571997] epc : 003f807bca18 ra : 
003f809221e4 sp : 003feebe7550
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572011]  gp : 002ac9a46b48 tp : 
003f8004d780 t0 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572024]  t1 : 003f808dc74c t2 : 
001a s0 : 002af4f3e420
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572036]  s1 : 002af4f3e410 a0 : 
002af65cb85e a1 : 002af4eac010
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572047]  a2 : 002af4f3f760 a3 : 
0002 a4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572059]  a5 :  a6 : 
002af4f3e410 a7 : fc164803c80b4e4b
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572070]  s2 : 002af4f14290 s3 : 
0001 s4 : 003feebe75a4
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572082]  s5 : 002af4f1fb00 s6 : 
002af4f02e80 s7 : 0001
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572093]  s8 : 002ac99fefe8 s9 : 
002af4f3e410 s10: 003f80c73d30
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572105]  s11: 003f809b4368 t3 : 
003f807bca14 t4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572117]  t5 : 0020 t6 : 
000a
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572126] status: 80026020 
badaddr: 002af65cb856 cause: 000d
  Oct 14 12:20:19 ubuntu wpa_supplicant[661]: wlan0: WPA: Group rekeying 
completed with 2c:91:ab:91:c5:77 [GTK=CCMP]
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: riscv64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IpRoute:
   default via 192.168.123.254 dev enx00e04d680306 proto dhcp src 
192.168.123.75 metric 100 
   default via 192.168.123.254 dev wlan0 proto dhcp src 192.168.123.76 metric 
600 
   192.168.123.0/24 dev enx00e04d680306 proto kernel scope link src 
192.168.123.75 metric 100 
   192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.76 metric 
600 
   192.168.123.254 dev enx00e04d680306 proto dhcp scope link src 192.168.123.75 
metric 100
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Package: network-manager 1.40.0-1ubuntu2
  PackageArchitecture: riscv64
  PciNetwork:
   
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15
  RebootRequiredPkgs: Error: path contained symlinks.
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic uec-images
  Uname: Linux 5.17.0-1003-allwinner riscv64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-10-14T12:28:44.227533
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   rxuZdtJmykLvLBiu  29060cbf-0727-4904-813c-5a7e54055c80  wifi  1665749804  
Fri Oct 14 12:16:44 2022  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/rxuZdtJmykLvLBiu.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this b

[Touch-packages] [Bug 1992968] NetworkManager.conf.txt

[Heinrich Schuchardt]

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1992968/+attachment/5624109/+files/NetworkManager.conf.txt

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

Title:
  nmcli disconnect leads to segmentation fault

Status in network-manager package in Ubuntu:
  New

Bug description:
  Disconnecting the WLAN on riscv64 (LicheeRV with driver licheerv-
  rtl8723ds-dkms) leads to a segmentation fault:

  $ sudo nmcli -a d  disconnect
  Interface(s): wlan0
  Segmentation fault

  Oct 14 12:17:48 ubuntu kernel: [ 5672.571893] nmcli[6918]: unhandled signal 
11 code 0x1 at 0x002af65cb856 in libc.so.6[3f80746000+126000]
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571971] CPU: 0 PID: 6918 Comm: nmcli 
Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571988] Hardware name: Sipeed Lichee RV 
Dock (DT)
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571997] epc : 003f807bca18 ra : 
003f809221e4 sp : 003feebe7550
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572011]  gp : 002ac9a46b48 tp : 
003f8004d780 t0 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572024]  t1 : 003f808dc74c t2 : 
001a s0 : 002af4f3e420
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572036]  s1 : 002af4f3e410 a0 : 
002af65cb85e a1 : 002af4eac010
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572047]  a2 : 002af4f3f760 a3 : 
0002 a4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572059]  a5 :  a6 : 
002af4f3e410 a7 : fc164803c80b4e4b
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572070]  s2 : 002af4f14290 s3 : 
0001 s4 : 003feebe75a4
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572082]  s5 : 002af4f1fb00 s6 : 
002af4f02e80 s7 : 0001
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572093]  s8 : 002ac99fefe8 s9 : 
002af4f3e410 s10: 003f80c73d30
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572105]  s11: 003f809b4368 t3 : 
003f807bca14 t4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572117]  t5 : 0020 t6 : 
000a
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572126] status: 80026020 
badaddr: 002af65cb856 cause: 000d
  Oct 14 12:20:19 ubuntu wpa_supplicant[661]: wlan0: WPA: Group rekeying 
completed with 2c:91:ab:91:c5:77 [GTK=CCMP]
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: riscv64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IpRoute:
   default via 192.168.123.254 dev enx00e04d680306 proto dhcp src 
192.168.123.75 metric 100 
   default via 192.168.123.254 dev wlan0 proto dhcp src 192.168.123.76 metric 
600 
   192.168.123.0/24 dev enx00e04d680306 proto kernel scope link src 
192.168.123.75 metric 100 
   192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.76 metric 
600 
   192.168.123.254 dev enx00e04d680306 proto dhcp scope link src 192.168.123.75 
metric 100
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Package: network-manager 1.40.0-1ubuntu2
  PackageArchitecture: riscv64
  PciNetwork:
   
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15
  RebootRequiredPkgs: Error: path contained symlinks.
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic uec-images
  Uname: Linux 5.17.0-1003-allwinner riscv64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-10-14T12:28:44.227533
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   rxuZdtJmykLvLBiu  29060cbf-0727-4904-813c-5a7e54055c80  wifi  1665749804  
Fri Oct 14 12:16:44 2022  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/rxuZdtJmykLvLBiu.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifica

[Touch-packages] [Bug 1992968] NetDevice.lo.txt

[Heinrich Schuchardt]

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1992968/+attachment/5624106/+files/NetDevice.lo.txt

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

Title:
  nmcli disconnect leads to segmentation fault

Status in network-manager package in Ubuntu:
  New

Bug description:
  Disconnecting the WLAN on riscv64 (LicheeRV with driver licheerv-
  rtl8723ds-dkms) leads to a segmentation fault:

  $ sudo nmcli -a d  disconnect
  Interface(s): wlan0
  Segmentation fault

  Oct 14 12:17:48 ubuntu kernel: [ 5672.571893] nmcli[6918]: unhandled signal 
11 code 0x1 at 0x002af65cb856 in libc.so.6[3f80746000+126000]
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571971] CPU: 0 PID: 6918 Comm: nmcli 
Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571988] Hardware name: Sipeed Lichee RV 
Dock (DT)
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571997] epc : 003f807bca18 ra : 
003f809221e4 sp : 003feebe7550
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572011]  gp : 002ac9a46b48 tp : 
003f8004d780 t0 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572024]  t1 : 003f808dc74c t2 : 
001a s0 : 002af4f3e420
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572036]  s1 : 002af4f3e410 a0 : 
002af65cb85e a1 : 002af4eac010
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572047]  a2 : 002af4f3f760 a3 : 
0002 a4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572059]  a5 :  a6 : 
002af4f3e410 a7 : fc164803c80b4e4b
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572070]  s2 : 002af4f14290 s3 : 
0001 s4 : 003feebe75a4
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572082]  s5 : 002af4f1fb00 s6 : 
002af4f02e80 s7 : 0001
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572093]  s8 : 002ac99fefe8 s9 : 
002af4f3e410 s10: 003f80c73d30
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572105]  s11: 003f809b4368 t3 : 
003f807bca14 t4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572117]  t5 : 0020 t6 : 
000a
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572126] status: 80026020 
badaddr: 002af65cb856 cause: 000d
  Oct 14 12:20:19 ubuntu wpa_supplicant[661]: wlan0: WPA: Group rekeying 
completed with 2c:91:ab:91:c5:77 [GTK=CCMP]
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: riscv64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IpRoute:
   default via 192.168.123.254 dev enx00e04d680306 proto dhcp src 
192.168.123.75 metric 100 
   default via 192.168.123.254 dev wlan0 proto dhcp src 192.168.123.76 metric 
600 
   192.168.123.0/24 dev enx00e04d680306 proto kernel scope link src 
192.168.123.75 metric 100 
   192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.76 metric 
600 
   192.168.123.254 dev enx00e04d680306 proto dhcp scope link src 192.168.123.75 
metric 100
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Package: network-manager 1.40.0-1ubuntu2
  PackageArchitecture: riscv64
  PciNetwork:
   
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15
  RebootRequiredPkgs: Error: path contained symlinks.
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic uec-images
  Uname: Linux 5.17.0-1003-allwinner riscv64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-10-14T12:28:44.227533
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   rxuZdtJmykLvLBiu  29060cbf-0727-4904-813c-5a7e54055c80  wifi  1665749804  
Fri Oct 14 12:16:44 2022  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/rxuZdtJmykLvLBiu.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about th

[Touch-packages] [Bug 1992968] NetDevice.wlan0.txt

[Heinrich Schuchardt]

apport information

** Attachment added: "NetDevice.wlan0.txt"
   
https://bugs.launchpad.net/bugs/1992968/+attachment/5624108/+files/NetDevice.wlan0.txt

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

Title:
  nmcli disconnect leads to segmentation fault

Status in network-manager package in Ubuntu:
  New

Bug description:
  Disconnecting the WLAN on riscv64 (LicheeRV with driver licheerv-
  rtl8723ds-dkms) leads to a segmentation fault:

  $ sudo nmcli -a d  disconnect
  Interface(s): wlan0
  Segmentation fault

  Oct 14 12:17:48 ubuntu kernel: [ 5672.571893] nmcli[6918]: unhandled signal 
11 code 0x1 at 0x002af65cb856 in libc.so.6[3f80746000+126000]
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571971] CPU: 0 PID: 6918 Comm: nmcli 
Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571988] Hardware name: Sipeed Lichee RV 
Dock (DT)
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571997] epc : 003f807bca18 ra : 
003f809221e4 sp : 003feebe7550
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572011]  gp : 002ac9a46b48 tp : 
003f8004d780 t0 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572024]  t1 : 003f808dc74c t2 : 
001a s0 : 002af4f3e420
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572036]  s1 : 002af4f3e410 a0 : 
002af65cb85e a1 : 002af4eac010
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572047]  a2 : 002af4f3f760 a3 : 
0002 a4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572059]  a5 :  a6 : 
002af4f3e410 a7 : fc164803c80b4e4b
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572070]  s2 : 002af4f14290 s3 : 
0001 s4 : 003feebe75a4
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572082]  s5 : 002af4f1fb00 s6 : 
002af4f02e80 s7 : 0001
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572093]  s8 : 002ac99fefe8 s9 : 
002af4f3e410 s10: 003f80c73d30
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572105]  s11: 003f809b4368 t3 : 
003f807bca14 t4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572117]  t5 : 0020 t6 : 
000a
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572126] status: 80026020 
badaddr: 002af65cb856 cause: 000d
  Oct 14 12:20:19 ubuntu wpa_supplicant[661]: wlan0: WPA: Group rekeying 
completed with 2c:91:ab:91:c5:77 [GTK=CCMP]
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: riscv64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IpRoute:
   default via 192.168.123.254 dev enx00e04d680306 proto dhcp src 
192.168.123.75 metric 100 
   default via 192.168.123.254 dev wlan0 proto dhcp src 192.168.123.76 metric 
600 
   192.168.123.0/24 dev enx00e04d680306 proto kernel scope link src 
192.168.123.75 metric 100 
   192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.76 metric 
600 
   192.168.123.254 dev enx00e04d680306 proto dhcp scope link src 192.168.123.75 
metric 100
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Package: network-manager 1.40.0-1ubuntu2
  PackageArchitecture: riscv64
  PciNetwork:
   
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15
  RebootRequiredPkgs: Error: path contained symlinks.
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic uec-images
  Uname: Linux 5.17.0-1003-allwinner riscv64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-10-14T12:28:44.227533
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   rxuZdtJmykLvLBiu  29060cbf-0727-4904-813c-5a7e54055c80  wifi  1665749804  
Fri Oct 14 12:16:44 2022  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/rxuZdtJmykLvLBiu.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications ab

[Touch-packages] [Bug 1992968] NetDevice.usb0.txt

[Heinrich Schuchardt]

apport information

** Attachment added: "NetDevice.usb0.txt"
   
https://bugs.launchpad.net/bugs/1992968/+attachment/5624107/+files/NetDevice.usb0.txt

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

Title:
  nmcli disconnect leads to segmentation fault

Status in network-manager package in Ubuntu:
  New

Bug description:
  Disconnecting the WLAN on riscv64 (LicheeRV with driver licheerv-
  rtl8723ds-dkms) leads to a segmentation fault:

  $ sudo nmcli -a d  disconnect
  Interface(s): wlan0
  Segmentation fault

  Oct 14 12:17:48 ubuntu kernel: [ 5672.571893] nmcli[6918]: unhandled signal 
11 code 0x1 at 0x002af65cb856 in libc.so.6[3f80746000+126000]
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571971] CPU: 0 PID: 6918 Comm: nmcli 
Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571988] Hardware name: Sipeed Lichee RV 
Dock (DT)
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571997] epc : 003f807bca18 ra : 
003f809221e4 sp : 003feebe7550
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572011]  gp : 002ac9a46b48 tp : 
003f8004d780 t0 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572024]  t1 : 003f808dc74c t2 : 
001a s0 : 002af4f3e420
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572036]  s1 : 002af4f3e410 a0 : 
002af65cb85e a1 : 002af4eac010
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572047]  a2 : 002af4f3f760 a3 : 
0002 a4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572059]  a5 :  a6 : 
002af4f3e410 a7 : fc164803c80b4e4b
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572070]  s2 : 002af4f14290 s3 : 
0001 s4 : 003feebe75a4
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572082]  s5 : 002af4f1fb00 s6 : 
002af4f02e80 s7 : 0001
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572093]  s8 : 002ac99fefe8 s9 : 
002af4f3e410 s10: 003f80c73d30
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572105]  s11: 003f809b4368 t3 : 
003f807bca14 t4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572117]  t5 : 0020 t6 : 
000a
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572126] status: 80026020 
badaddr: 002af65cb856 cause: 000d
  Oct 14 12:20:19 ubuntu wpa_supplicant[661]: wlan0: WPA: Group rekeying 
completed with 2c:91:ab:91:c5:77 [GTK=CCMP]
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: riscv64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IpRoute:
   default via 192.168.123.254 dev enx00e04d680306 proto dhcp src 
192.168.123.75 metric 100 
   default via 192.168.123.254 dev wlan0 proto dhcp src 192.168.123.76 metric 
600 
   192.168.123.0/24 dev enx00e04d680306 proto kernel scope link src 
192.168.123.75 metric 100 
   192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.76 metric 
600 
   192.168.123.254 dev enx00e04d680306 proto dhcp scope link src 192.168.123.75 
metric 100
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Package: network-manager 1.40.0-1ubuntu2
  PackageArchitecture: riscv64
  PciNetwork:
   
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15
  RebootRequiredPkgs: Error: path contained symlinks.
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic uec-images
  Uname: Linux 5.17.0-1003-allwinner riscv64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-10-14T12:28:44.227533
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   rxuZdtJmykLvLBiu  29060cbf-0727-4904-813c-5a7e54055c80  wifi  1665749804  
Fri Oct 14 12:16:44 2022  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/rxuZdtJmykLvLBiu.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications abou

[Touch-packages] [Bug 1992968] IpAddr.txt

[Heinrich Schuchardt]

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1992968/+attachment/5624104/+files/IpAddr.txt

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

Title:
  nmcli disconnect leads to segmentation fault

Status in network-manager package in Ubuntu:
  New

Bug description:
  Disconnecting the WLAN on riscv64 (LicheeRV with driver licheerv-
  rtl8723ds-dkms) leads to a segmentation fault:

  $ sudo nmcli -a d  disconnect
  Interface(s): wlan0
  Segmentation fault

  Oct 14 12:17:48 ubuntu kernel: [ 5672.571893] nmcli[6918]: unhandled signal 
11 code 0x1 at 0x002af65cb856 in libc.so.6[3f80746000+126000]
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571971] CPU: 0 PID: 6918 Comm: nmcli 
Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571988] Hardware name: Sipeed Lichee RV 
Dock (DT)
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571997] epc : 003f807bca18 ra : 
003f809221e4 sp : 003feebe7550
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572011]  gp : 002ac9a46b48 tp : 
003f8004d780 t0 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572024]  t1 : 003f808dc74c t2 : 
001a s0 : 002af4f3e420
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572036]  s1 : 002af4f3e410 a0 : 
002af65cb85e a1 : 002af4eac010
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572047]  a2 : 002af4f3f760 a3 : 
0002 a4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572059]  a5 :  a6 : 
002af4f3e410 a7 : fc164803c80b4e4b
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572070]  s2 : 002af4f14290 s3 : 
0001 s4 : 003feebe75a4
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572082]  s5 : 002af4f1fb00 s6 : 
002af4f02e80 s7 : 0001
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572093]  s8 : 002ac99fefe8 s9 : 
002af4f3e410 s10: 003f80c73d30
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572105]  s11: 003f809b4368 t3 : 
003f807bca14 t4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572117]  t5 : 0020 t6 : 
000a
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572126] status: 80026020 
badaddr: 002af65cb856 cause: 000d
  Oct 14 12:20:19 ubuntu wpa_supplicant[661]: wlan0: WPA: Group rekeying 
completed with 2c:91:ab:91:c5:77 [GTK=CCMP]
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: riscv64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IpRoute:
   default via 192.168.123.254 dev enx00e04d680306 proto dhcp src 
192.168.123.75 metric 100 
   default via 192.168.123.254 dev wlan0 proto dhcp src 192.168.123.76 metric 
600 
   192.168.123.0/24 dev enx00e04d680306 proto kernel scope link src 
192.168.123.75 metric 100 
   192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.76 metric 
600 
   192.168.123.254 dev enx00e04d680306 proto dhcp scope link src 192.168.123.75 
metric 100
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Package: network-manager 1.40.0-1ubuntu2
  PackageArchitecture: riscv64
  PciNetwork:
   
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15
  RebootRequiredPkgs: Error: path contained symlinks.
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic uec-images
  Uname: Linux 5.17.0-1003-allwinner riscv64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-10-14T12:28:44.227533
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   rxuZdtJmykLvLBiu  29060cbf-0727-4904-813c-5a7e54055c80  wifi  1665749804  
Fri Oct 14 12:16:44 2022  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/rxuZdtJmykLvLBiu.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:

[Touch-packages] [Bug 1992968] Re: nmcli disconnect leads to segmentation fault

[Heinrich Schuchardt]

apport information

** Tags added: apport-collected kinetic uec-images

** Description changed:

  Disconnecting the WLAN on riscv64 (LicheeRV with driver licheerv-
  rtl8723ds-dkms) leads to a segmentation fault:
  
  $ sudo nmcli -a d  disconnect
  Interface(s): wlan0
  Segmentation fault
  
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571893] nmcli[6918]: unhandled signal 
11 code 0x1 at 0x002af65cb856 in libc.so.6[3f80746000+126000]
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571971] CPU: 0 PID: 6918 Comm: nmcli 
Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571988] Hardware name: Sipeed Lichee RV 
Dock (DT)
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571997] epc : 003f807bca18 ra : 
003f809221e4 sp : 003feebe7550
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572011]  gp : 002ac9a46b48 tp : 
003f8004d780 t0 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572024]  t1 : 003f808dc74c t2 : 
001a s0 : 002af4f3e420
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572036]  s1 : 002af4f3e410 a0 : 
002af65cb85e a1 : 002af4eac010
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572047]  a2 : 002af4f3f760 a3 : 
0002 a4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572059]  a5 :  a6 : 
002af4f3e410 a7 : fc164803c80b4e4b
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572070]  s2 : 002af4f14290 s3 : 
0001 s4 : 003feebe75a4
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572082]  s5 : 002af4f1fb00 s6 : 
002af4f02e80 s7 : 0001
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572093]  s8 : 002ac99fefe8 s9 : 
002af4f3e410 s10: 003f80c73d30
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572105]  s11: 003f809b4368 t3 : 
003f807bca14 t4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572117]  t5 : 0020 t6 : 
000a
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572126] status: 80026020 
badaddr: 002af65cb856 cause: 000d
  Oct 14 12:20:19 ubuntu wpa_supplicant[661]: wlan0: WPA: Group rekeying 
completed with 2c:91:ab:91:c5:77 [GTK=CCMP]
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.23.1-0ubuntu3
+ Architecture: riscv64
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 22.10
+ IpRoute:
+  default via 192.168.123.254 dev enx00e04d680306 proto dhcp src 
192.168.123.75 metric 100 
+  default via 192.168.123.254 dev wlan0 proto dhcp src 192.168.123.76 metric 
600 
+  192.168.123.0/24 dev enx00e04d680306 proto kernel scope link src 
192.168.123.75 metric 100 
+  192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.76 metric 
600 
+  192.168.123.254 dev enx00e04d680306 proto dhcp scope link src 192.168.123.75 
metric 100
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Package: network-manager 1.40.0-1ubuntu2
+ PackageArchitecture: riscv64
+ PciNetwork:
+  
+ ProcCpuinfoMinimal:
+  processor: 0
+  hart : 0
+  isa  : rv64imafdc
+  mmu  : sv39
+  uarch: thead,c906
+ ProcEnviron:
+  TERM=vt220
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15
+ RebootRequiredPkgs: Error: path contained symlinks.
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags:  kinetic uec-images
+ Uname: Linux 5.17.0-1003-allwinner riscv64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ modified.conffile..etc.apport.crashdb.conf: [modified]
+ mtime.conffile..etc.apport.crashdb.conf: 2022-10-14T12:28:44.227533
+ nmcli-con:
+  NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

+  rxuZdtJmykLvLBiu  29060cbf-0727-4904-813c-5a7e54055c80  wifi  1665749804  
Fri Oct 14 12:16:44 2022  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/rxuZdtJmykLvLBiu.nmconnection
+ nmcli-nm:
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1992968/+attachment/5624103/+files/Dependencies.txt

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

Title:
  nmcli disconnect leads to segmentation fault

Status in network-ma

[Touch-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Athos Ribeiro]

** Description changed:

+ [ Impact ]
+ 
+ OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering backend,
+ always with CAIRO_OPERATOR_SATURATE and sometimes with subpixel
+ positioning (when reading certain file formats), and Cairo in turn
+ invokes this code. As a result, some slides incorrectly render with
+ large blank spaces and with some pixels rendered on top of other pixels.
+ This effectively makes OpenSlide unusable for several of the file
+ formats it supports. No workaround is believed possible within the
+ OpenSlide codebase.
+ 
+ [ Test Plan ]
+ 
+ Compile and run the pixman.c test program uploaded to this bug. It
+ should report "OK".
+ 
+ [ Where problems could occur ]
+ 
+ Problems would show up as incorrect pixel output from software that
+ renders via Cairo or pixman.
+ 
+ [ Other Info ]
+ 
+ While I'm not a pixman expert, it appears that the change should only
+ affect the broken code path, and it seems unlikely that anything else
+ depends on the incorrect math fixed by this patch. This bug hasn't
+ previously been reported in Ubuntu, which may imply that this code path
+ is not exercised by other packages in the distro.
+ 
+ The affected source file has had no further commits upstream since this
+ patch was applied in April 2019, and some basic commit grepping didn't
+ turn up any followup fixes elsewhere in the tree.
+ 
+ [ Original message ]
+ 
  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some circumstances.
  This can be triggered by the use of cairo with CAIRO_OPERATOR_SATURATE
  and subpixel positioning, and causes OpenSlide 
  to produce incorrect output.
  
  The attached test program will print "Failed" if the bug exists, or "OK"
  if it doesn't.
  
  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which is
  in pixman 0.40.0.
  
  See https://github.com/openslide/openslide/issues/278 for more context.

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

** Changed in: pixman (Ubuntu)
   Status: New => Fix Released

** Changed in: pixman (Ubuntu Focal)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pixman in Ubuntu.
https://bugs.launchpad.net/bugs/1988796

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  Fix Released
Status in pixman source package in Focal:
  Triaged

Bug description:
  [ Impact ]

  OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering
  backend, always with CAIRO_OPERATOR_SATURATE and sometimes with
  subpixel positioning (when reading certain file formats), and Cairo in
  turn invokes this code. As a result, some slides incorrectly render
  with large blank spaces and with some pixels rendered on top of other
  pixels. This effectively makes OpenSlide unusable for several of the
  file formats it supports. No workaround is believed possible within
  the OpenSlide codebase.

  [ Test Plan ]

  Compile and run the pixman.c test program uploaded to this bug. It
  should report "OK".

  [ Where problems could occur ]

  Problems would show up as incorrect pixel output from software that
  renders via Cairo or pixman.

  [ Other Info ]

  While I'm not a pixman expert, it appears that the change should only
  affect the broken code path, and it seems unlikely that anything else
  depends on the incorrect math fixed by this patch. This bug hasn't
  previously been reported in Ubuntu, which may imply that this code
  path is not exercised by other packages in the distro.

  The affected source file has had no further commits upstream since
  this patch was applied in April 2019, and some basic commit grepping
  didn't turn up any followup fixes elsewhere in the tree.

  [ Original message ]

  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

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


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

[Touch-packages] [Bug 1992968] [NEW] nmcli disconnect leads to segmentation fault

[Heinrich Schuchardt]

Public bug reported:

Disconnecting the WLAN on riscv64 (LicheeRV with driver licheerv-
rtl8723ds-dkms) leads to a segmentation fault:

$ sudo nmcli -a d  disconnect
Interface(s): wlan0
Segmentation fault

Oct 14 12:17:48 ubuntu kernel: [ 5672.571893] nmcli[6918]: unhandled signal 11 
code 0x1 at 0x002af65cb856 in libc.so.6[3f80746000+126000]
Oct 14 12:17:48 ubuntu kernel: [ 5672.571971] CPU: 0 PID: 6918 Comm: nmcli 
Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
Oct 14 12:17:48 ubuntu kernel: [ 5672.571988] Hardware name: Sipeed Lichee RV 
Dock (DT)
Oct 14 12:17:48 ubuntu kernel: [ 5672.571997] epc : 003f807bca18 ra : 
003f809221e4 sp : 003feebe7550
Oct 14 12:17:48 ubuntu kernel: [ 5672.572011]  gp : 002ac9a46b48 tp : 
003f8004d780 t0 : 
Oct 14 12:17:48 ubuntu kernel: [ 5672.572024]  t1 : 003f808dc74c t2 : 
001a s0 : 002af4f3e420
Oct 14 12:17:48 ubuntu kernel: [ 5672.572036]  s1 : 002af4f3e410 a0 : 
002af65cb85e a1 : 002af4eac010
Oct 14 12:17:48 ubuntu kernel: [ 5672.572047]  a2 : 002af4f3f760 a3 : 
0002 a4 : 
Oct 14 12:17:48 ubuntu kernel: [ 5672.572059]  a5 :  a6 : 
002af4f3e410 a7 : fc164803c80b4e4b
Oct 14 12:17:48 ubuntu kernel: [ 5672.572070]  s2 : 002af4f14290 s3 : 
0001 s4 : 003feebe75a4
Oct 14 12:17:48 ubuntu kernel: [ 5672.572082]  s5 : 002af4f1fb00 s6 : 
002af4f02e80 s7 : 0001
Oct 14 12:17:48 ubuntu kernel: [ 5672.572093]  s8 : 002ac99fefe8 s9 : 
002af4f3e410 s10: 003f80c73d30
Oct 14 12:17:48 ubuntu kernel: [ 5672.572105]  s11: 003f809b4368 t3 : 
003f807bca14 t4 : 
Oct 14 12:17:48 ubuntu kernel: [ 5672.572117]  t5 : 0020 t6 : 
000a
Oct 14 12:17:48 ubuntu kernel: [ 5672.572126] status: 80026020 badaddr: 
002af65cb856 cause: 000d
Oct 14 12:20:19 ubuntu wpa_supplicant[661]: wlan0: WPA: Group rekeying 
completed with 2c:91:ab:91:c5:77 [GTK=CCMP]

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

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

Title:
  nmcli disconnect leads to segmentation fault

Status in network-manager package in Ubuntu:
  New

Bug description:
  Disconnecting the WLAN on riscv64 (LicheeRV with driver licheerv-
  rtl8723ds-dkms) leads to a segmentation fault:

  $ sudo nmcli -a d  disconnect
  Interface(s): wlan0
  Segmentation fault

  Oct 14 12:17:48 ubuntu kernel: [ 5672.571893] nmcli[6918]: unhandled signal 
11 code 0x1 at 0x002af65cb856 in libc.so.6[3f80746000+126000]
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571971] CPU: 0 PID: 6918 Comm: nmcli 
Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571988] Hardware name: Sipeed Lichee RV 
Dock (DT)
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571997] epc : 003f807bca18 ra : 
003f809221e4 sp : 003feebe7550
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572011]  gp : 002ac9a46b48 tp : 
003f8004d780 t0 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572024]  t1 : 003f808dc74c t2 : 
001a s0 : 002af4f3e420
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572036]  s1 : 002af4f3e410 a0 : 
002af65cb85e a1 : 002af4eac010
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572047]  a2 : 002af4f3f760 a3 : 
0002 a4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572059]  a5 :  a6 : 
002af4f3e410 a7 : fc164803c80b4e4b
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572070]  s2 : 002af4f14290 s3 : 
0001 s4 : 003feebe75a4
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572082]  s5 : 002af4f1fb00 s6 : 
002af4f02e80 s7 : 0001
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572093]  s8 : 002ac99fefe8 s9 : 
002af4f3e410 s10: 003f80c73d30
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572105]  s11: 003f809b4368 t3 : 
003f807bca14 t4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572117]  t5 : 0020 t6 : 
000a
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572126] status: 80026020 
badaddr: 002af65cb856 cause: 000d
  Oct 14 12:20:19 ubuntu wpa_supplicant[661]: wlan0: WPA: Group rekeying 
completed with 2c:91:ab:91:c5:77 [GTK=CCMP]

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


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

[Touch-packages] [Bug 1992454] Re: iptables: segfault when renaming a chain

[Louis Bouchard]

Here is an autopkgtest run with the latest patch :

Removing autopkgtest-satdep (0) ... 
 
autopkgtest [14:09:03]: test command17: chmod +x 
./iptables/tests/shell/testcases/iptables/0007-zero-counters_0 
./iptables/tests/shell/testcases/chain/0006rename-segfault_0; cd 
iptables/tests/shell; ./run-testst
autopkgtest [14:09:03]: test command17: [---


 
I: [OK]  ././testcases/arptables/0001-arptables-save-restore_0  
I: [OK]  ././testcases/arptables/0002-arptables-restore-defaults_0
I: [OK]  ././testcases/arptables/0003-arptables-verbose-output_0
I: [OK]  ././testcases/chain/0001duplicate_1
I: [OK]  ././testcases/chain/0002newchain_0 
 
I: [OK]  ././testcases/chain/0003rename_1   
 
I: [OK]  ././testcases/chain/0006rename-segfault_0  
...
autopkgtest [14:09:19]: test command17:  - - - - - - - - - - results - - - - - 
- - - - -
command17PASS
autopkgtest [14:09:19]:  summary
command1 PASS
command2 PASS
command3 PASS
command4 PASS
command5 PASS
command6 PASS
command7 PASS
command8 PASS
command9 PASS
command10PASS
command11PASS
command12PASS
command13PASS
command14PASS
command15PASS
command16PASS
command17PASS

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1992454

Title:
  iptables: segfault when renaming a chain

Status in iptables package in Ubuntu:
  In Progress
Status in iptables source package in Bionic:
  In Progress
Status in iptables source package in Focal:
  In Progress
Status in iptables source package in Jammy:
  In Progress
Status in iptables source package in Kinetic:
  In Progress

Bug description:
  This is the description for the upstream fix of this bug[1] :

  This is an odd bug: If the number of chains is right and one renames the
  last one in the list, libiptc dereferences a NULL pointer.

  Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug
  upstream. This bug is to have the fix included in Ubuntu in order to
  avoid such segmentation faults.

  For Jammy and onward, iptables uses the new nft libraries so the
  problem does not appear unless the -legacy commands are used.

  The following code (adapted from the upstream commit to work on Kinetic) may 
be used to reproduce the issue :
  8<
  #!/bin/bash
  #
  # Cover for a bug in libiptc:
  # - the chain 'node-98-tmp' is the last in the list sorted by name
  # - there are 81 chains in total, so three chain index buckets
  # - the last index bucket contains only the 'node-98-tmp' chain
  # => rename temporarily removes it from the bucket, leaving a NULL bucket
  #behind which is dereferenced later when inserting the chain again with 
new
  #name again

  (
echo "*filter"
for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 
node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 
node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 
node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 
node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 
node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 
node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 
node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 
node-92 node-93 node-95 node-98-tmp; do
echo ":$chain - [0:0]"
done
echo "COMMIT"
  ) | $XT_MULTI iptables-legacy-restore
  $XT_MULTI iptables-legacy -E node-98-tmp node-98
  exit $?
  >8

  [1]
  
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

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


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

[Touch-packages] [Bug 1992930] Re: chromium won't launch at menu when installed; lubuntu kinetic

[Chris Guiver]

Fossfreedom (https://launchpad.net/~fossfreedom) has chromium starts
normally in Ubuntu Budgie (kinetic).

Also I'd not noticed the u/neblaz on Lubuntu's discourse also reported
the same with Opera.  I've only used opera as a deb package & thus may
differ to chromium??


** Description changed:

  Lubuntu kinetic live test
  
  `chromium` snap once installed; will not open from menu, but will open
  if started from terminal.  This maybe filed against incorrect package
  sorry.
  
  Originally reported here - https://discourse.lubuntu.me/t/lubuntu-
  kinetic-after-5-19-update-chromium-only-start-from-terminal/3685 where
  it was reported as an issue on the 5.19.0-19-generic kernel update
  
  ** to re-create
  
  - boot currently lubuntu kinetic daily
  - snap install chromium
  - using menu, attempt to run chromium from internet apps
  
  ** expected outcome
  
  chromium starts
  
  ** actual outcome
  
  menu just closes; no messages.
  
- ** in `dmesg` I note the following (this may be unrelated or unhelpful
- sorry)
+ ** further notes
+ 
+ u/FossFreedom (Ubuntu Budgie) reports no issues with Ubuntu Budgie
+ kinetic starting Chromium.
+ 
+ On Lubuntu's discourse; u/neblaz (OP for issue) also reported issues
+ starting Opera; I've asked what package type & from where.
+ 
+ 
+ ** in `dmesg` I note the following (this may be unrelated or unhelpful sorry)
  
  [ 1510.255228] loop7: detected capacity change from 0 to 293648
  [ 1510.739240] audit: type=1400 audit(1665727470.633:54): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap-update-ns.chromium" 
pid=3359 comm="apparmor_parser"
  [ 1510.820094] audit: type=1400 audit(1665727470.713:55): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap.chromium.chromedriver" 
pid=3360 comm="apparmor_parser"
  [ 1511.014103] audit: type=1400 audit(1665727470.909:56): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap.chromium.chromium" 
pid=3361 comm="apparmor_parser"
  [ 1511.071575] audit: type=1400 audit(1665727470.965:57): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="snap.chromium.hook.configure" pid=3362 comm="apparmor_parser"
  [ 1515.313383] audit: type=1400 audit(1665727475.206:58): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="/snap/snapd/17029/usr/lib/snapd/snap-confine" 
pid=3496 comm="apparmor_parser"
  [ 1515.313401] audit: type=1400 audit(1665727475.206:59): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" 
name="/snap/snapd/17029/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
 pid=3496 comm="apparmor_parser"
  [ 1516.817149] audit: type=1400 audit(1665727476.710:60): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap-update-ns.chromium" 
pid=3498 comm="apparmor_parser"
  [ 1518.067335] audit: type=1400 audit(1665727477.962:61): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="snap.chromium.chromedriver" pid=3499 comm="apparmor_parser"
  [ 1518.568962] audit: type=1400 audit(1665727478.462:62): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="snap.chromium.hook.configure" pid=3501 comm="apparmor_parser"
  [ 1519.485025] audit: type=1400 audit(1665727479.378:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.chromium.chromium" 
pid=3500 comm="apparmor_parser"
  [ 1520.203518] audit: type=1400 audit(1665727480.098:64): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/meta/snap.yaml" pid=3518 comm="6" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  [ 1520.245234] audit: type=1400 audit(1665727480.142:65): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/fonts/" pid=3518 comm="6" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 1520.245256] audit: type=1400 audit(1665727480.142:66): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/" pid=3518 comm="6" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  [ 1520.246876] audit: type=1400 audit(1665727480.142:67): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/var/lib/snapd/hostfs/usr/share/doc/" pid=3518 comm="6" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 1520.246933] audit: type=1400 audit(1665727480.142:68): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/var/lib/snapd/hostfs/usr/share/fonts/" pid=3518 comm="6" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 1520.349971] audit: type=1400 audit(1665727480.246:69): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/fonts/" pid=3518 comm="6" requested_mask="r" 
denied_

[Touch-packages] [Bug 1970402] Re: Initrd out of memory error after upgrade to 22.04

[Trip Ericson]

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

I have an Asus G752VY and encountered this issue when upgrading from
Kubuntu 20.04 to 22.04 this morning.  Neither my new kernel nor my old
one would boot, whether into recovery mode or not.  I ended up spending
a lot of time figuring out how to fix it through the USB live disk.

While I know this is a bug tracker and not a how-to guide, I'm posting
the steps I used to recover because this is one of the first results
that comes up in Google for this problem and I'd hope to save others
from my hours of frustration this morning.  My root partition is on
/dev/nvme0n1p1, so you'll need to adjust if yours is elsewhere.

1) Boot USB disk and select Try It.
2) Open a command line.
3) sudo mount /dev/nvme0n1p1 /mnt
4) sudo mount --bind /dev /mnt/dev && sudo mount --bind /proc /mnt/proc && sudo 
mount --bind /sys /mnt/sys && sudo chroot /mnt
5) Use your favorite command line text editor to edit 
/etc/initramfs-tools/initramfs.conf as noted above.  I used:

MODULES=dep
COMPRESS=xz

6) For safety, I made a backup copy of my existing init file, not that it 
worked in the first place, but it seemed smart.
7) update-initramfs -c -k all
8) update-grub
9) Reboot system.

With all of that, it booted successfully.  Hope it helps someone.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1970402

Title:
  Initrd out of memory error after upgrade to 22.04

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Confirmed

Bug description:
  After upgrading to 22.04 system is unbootable because of "out of memory" 
error when loading initial ramdisk. I was able to fix it by editing cat 
/etc/initramfs-tools/initramfs.conf
  and changing configuration to:
  MODULES=dep
  COMPRESS=xz
  RUNSIZE=15%

  Not sure which one helped, but I can test it if needed.

  System information:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  initramfs-tools:
Installed: 0.140ubuntu13
Candidate: 0.140ubuntu13
Version table:
   *** 0.140ubuntu13 500
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  100 /var/lib/dpkg/status

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


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

[Touch-packages] [Bug 1971632] Re: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time

[ogooreck]

Hello,

I installed the package from proposed and it fixes bug for me.

pulseaudio:
  Installed: 1:15.99.1+dfsg1-1ubuntu2
  Candidate: 1:15.99.1+dfsg1-1ubuntu2
  Version table:
 *** 1:15.99.1+dfsg1-1ubuntu2 400
400 http://pl.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 1:15.99.1+dfsg1-1ubuntu1 500
500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

before installing package: after switching off and then switching on bt
headphones (previously paired with my laptop bt device) connect
automatically, then immediately disconnect

after installing package: after switching off and then switching on bt
headphones (previously paired with my laptop bt device) connect
automatically and stay connected, sound working properly.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1971632

Title:
  Kubuntu 22.04, Bluetooth Headphones connect automatically, then
  immediately disconnect; pulseautio crashes every time

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

Bug description:
  * Impact

  On a fresh install of Kubuntu 22.04, when I turn my properly paired
  bluetooth headphones on they automatically connect to the system, then
  immediately disconnect again. The headphones thus have to be manually
  're-connected' every time.

  * Test case

  Connect a bluetooth headset to the computer, try to change the active
  profile. The selection should be reflected and the quality match, the
  pairing and service should be stable

  * Regression potential

  The changes are in the bluetooth a2dp/sbc functions so any potential
  regression would impact the connectivity with bluetooth devices using
  an a2dp profile (aptX, SBC, AAC). Check with different devices using
  the previously listed profiles.

  
  

  Best as I understand it from the logs (appended below), pulseaudio showing up 
killed just after the headphones turn up as an unregistered sender ...
  4/30/22 7:33 PM   systemd pulseaudio.service: Main process exited, 
code=killed, status=8/FPE

  ... is responsible for the observed problem, i.e. the disconnect, probably 
triggered when pulseaudio restarts ...
  4/30/22 7:33 PM   systemd pulseaudio.service: Scheduled restart job, 
restart counter is at 2.

  So it seems either an internal pulseaudio problem, or a problem triggered by 
the division by 0 in the bluetooth module ...
  4/30/22 7:33 PM   kernel  traps: bluetooth[8884] trap divide error 
ip:7f862dc68490 sp:7f862498cc30 error:0 in 
module-bluez5-device.so[7f862dc66000+9000]

  or some combination of the two ... but again, I'm only guessing here.

  
___

  System Logs after switching headphones on:

  4/30/22 7:33 PM   kernel  input: Nat's Flex (AVRCP) as 
/devices/virtual/input/input31
  4/30/22 7:33 PM   systemd-logind  Watching system buttons on 
/dev/input/event19 (Nat's Flex (AVRCP))
  4/30/22 7:33 PM   bluetoothd  
/org/bluez/hci0/dev_A8_91_3D_DF_A8_F4/fd3: fd(43) ready
  4/30/22 7:33 PM   rtkit-daemonSupervising 0 threads of 0 processes of 
0 users.
  4/30/22 7:33 PM   rtkit-daemonSuccessfully made thread 8884 of 
process 3426 owned by '1000' RT at priority 5.
  4/30/22 7:33 PM   rtkit-daemonSupervising 1 threads of 1 processes of 
1 users.
  4/30/22 7:33 PM   kernel  traps: bluetooth[8884] trap divide error 
ip:7f862dc68490 sp:7f862498cc30 error:0 in 
module-bluez5-device.so[7f862dc66000+9000]
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSink/sbc
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSource/sbc
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSink/sbc_xq_453
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSource/sbc_xq_453
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSink/sbc_xq_512
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSource/sbc_xq_512
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSink/sbc_xq_552
  4/30/22 7:33 PM   systemd pulseaudio.service: Main process exited, 
code=killed, status=8/FPE
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSource/sbc_xq_552
  4/30/22 7:33 PM   systemd pulseaudio.service: Failed with result 'signal'.
  4/30/22 7:33 PM   systemd pulseaudio.service: Consumed 2min 20.027s CPU 
time.
  4/30/22 7:33 PM   acp

[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken

[Sebastien Bacher]

the issue is not likely in the font nor the viewer but in the rendering
stack, I can't confirm here either. Could you give a bit more details on
the desktop environment/fonts settings/locale you are using and include
the output of

$ gsettings list-recursively org.gnome.desktop.interface | grep font

?

** Changed in: gnome-font-viewer (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu.
https://bugs.launchpad.net/bugs/1992369

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fonts-dejavu package in Ubuntu:
  Invalid
Status in gnome-font-viewer package in Ubuntu:
  Incomplete

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

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


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

[Touch-packages] [Bug 1992930] Re: chromium won't launch at menu when installed; lubuntu kinetic

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1992930

** Tags added: iso-testing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1992930

Title:
  chromium won't launch at menu when installed; lubuntu kinetic

Status in apparmor package in Ubuntu:
  New

Bug description:
  Lubuntu kinetic live test

  `chromium` snap once installed; will not open from menu, but will open
  if started from terminal.  This maybe filed against incorrect package
  sorry.

  Originally reported here - https://discourse.lubuntu.me/t/lubuntu-
  kinetic-after-5-19-update-chromium-only-start-from-terminal/3685 where
  it was reported as an issue on the 5.19.0-19-generic kernel update

  ** to re-create

  - boot currently lubuntu kinetic daily
  - snap install chromium
  - using menu, attempt to run chromium from internet apps

  ** expected outcome

  chromium starts

  ** actual outcome

  menu just closes; no messages.

  ** in `dmesg` I note the following (this may be unrelated or unhelpful
  sorry)

  [ 1510.255228] loop7: detected capacity change from 0 to 293648
  [ 1510.739240] audit: type=1400 audit(1665727470.633:54): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap-update-ns.chromium" 
pid=3359 comm="apparmor_parser"
  [ 1510.820094] audit: type=1400 audit(1665727470.713:55): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap.chromium.chromedriver" 
pid=3360 comm="apparmor_parser"
  [ 1511.014103] audit: type=1400 audit(1665727470.909:56): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap.chromium.chromium" 
pid=3361 comm="apparmor_parser"
  [ 1511.071575] audit: type=1400 audit(1665727470.965:57): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="snap.chromium.hook.configure" pid=3362 comm="apparmor_parser"
  [ 1515.313383] audit: type=1400 audit(1665727475.206:58): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="/snap/snapd/17029/usr/lib/snapd/snap-confine" 
pid=3496 comm="apparmor_parser"
  [ 1515.313401] audit: type=1400 audit(1665727475.206:59): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" 
name="/snap/snapd/17029/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
 pid=3496 comm="apparmor_parser"
  [ 1516.817149] audit: type=1400 audit(1665727476.710:60): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap-update-ns.chromium" 
pid=3498 comm="apparmor_parser"
  [ 1518.067335] audit: type=1400 audit(1665727477.962:61): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="snap.chromium.chromedriver" pid=3499 comm="apparmor_parser"
  [ 1518.568962] audit: type=1400 audit(1665727478.462:62): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="snap.chromium.hook.configure" pid=3501 comm="apparmor_parser"
  [ 1519.485025] audit: type=1400 audit(1665727479.378:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.chromium.chromium" 
pid=3500 comm="apparmor_parser"
  [ 1520.203518] audit: type=1400 audit(1665727480.098:64): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/meta/snap.yaml" pid=3518 comm="6" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  [ 1520.245234] audit: type=1400 audit(1665727480.142:65): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/fonts/" pid=3518 comm="6" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 1520.245256] audit: type=1400 audit(1665727480.142:66): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/" pid=3518 comm="6" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  [ 1520.246876] audit: type=1400 audit(1665727480.142:67): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/var/lib/snapd/hostfs/usr/share/doc/" pid=3518 comm="6" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 1520.246933] audit: type=1400 audit(1665727480.142:68): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/var/lib/snapd/hostfs/usr/share/fonts/" pid=3518 comm="6" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 1520.349971] audit: type=1400 audit(1665727480.246:69): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/fonts/" pid=3518 comm="6" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 1628.635260] kauditd_printk_skb: 6 callbacks suppressed
  [ 1628.635268] audit: type=1400 audit(166572758

[Touch-packages] [Bug 1971712] Re: Add support for Intel DG2

[Timo Aaltonen]

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1971712

Title:
  Add support for Intel DG2

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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

[Touch-packages] [Bug 1980386] Re: `radeonsi_dri.so` driver missing on riscv64

[Timo Aaltonen]

not so fast, llvm-15 will get backported to jammy for mesa hwe backport
;)

** Changed in: llvm-toolchain-15 (Ubuntu Jammy)
   Status: Invalid => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1980386

Title:
  `radeonsi_dri.so` driver missing on riscv64

Status in llvm-toolchain-15 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in llvm-toolchain-15 source package in Jammy:
  In Progress
Status in mesa source package in Jammy:
  Confirmed
Status in llvm-toolchain-15 source package in Kinetic:
  Fix Released
Status in mesa source package in Kinetic:
  Confirmed

Bug description:
  The package is missing the `radeonsi` driver, with the reasoning that
  LLVM is not implemented on the architecture:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618

  That said, it works just fine on focal, where it is still enabled.
  Without this driver there's no way to use AMD graphics cards on
  RISC-V.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.1-1ubuntu2
  ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30
  Uname: Linux 5.15.0-1007-generic riscv64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  Date: Thu Jun 30 15:48:11 2022
  ProcCpuinfoMinimal:
   processor: 3
   hart : 4
   isa  : rv64imafdc
   mmu  : sv39
   uarch: sifive,u74-mc
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1980386/+subscriptions


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