[Touch-packages] [Bug 1988864] Re: Screen freezes after display turns on from standby

[Daniel van Vugt]

Thanks for the bug report.

Next time the bug happens, please:

1. Use the workaround to recover.

2. Run:

   journalctl -b0 > journal.txt

3. Attach the resulting text file here.


** Tags added: radeon

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

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

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

Title:
  Screen freezes after display turns on from standby

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  This happens after automatic Blank Screen about 25% of the time. Mouse
  cursor doesn't move and alt-tab doesn't work.

  Workaround: ctrl-alt-f3, ctrl-alt-f1, login screen appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 14:13:08 2022
  DistUpgraded: 2022-07-28 04:25:49,168 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] 
[1002:130f] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Kaveri [Radeon R7 Graphics] [1043:85cb]
  InstallationDate: Installed on 2020-06-25 (802 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=25ac8a19-c1fe-4cac-a26c-50c592bf9181 ro quiet splash 
video=HDMI-A-1:1920x1080M@72 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-07-28 (40 days ago)
  dmi.bios.date: 04/14/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3004:bd04/14/2017:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1988864/+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 1940996] Re: test failure - test-regex

[Bug Watch Updater]

** Changed in: grep
   Status: In Progress => Fix Released

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

Title:
  test failure - test-regex

Status in grep:
  Fix Released
Status in grep package in Ubuntu:
  New

Bug description:
  'test-regex' fails when building grep against glibc 2.34.
  Per commentary from grep upstream at 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, 
  the test failure can be attributed to skew between the glibc built-in regex 
and the one that is found in the grep source code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]

[Vincent-srcware]

(In reply to eggert from comment #20)
> OK, so in that case how about if we update Bug#17356 by (1) saying it is no
> longer a duplicate of Bug#11053 (as we've fixed the latter but not the
> former), and (2) reopening Bug#17536? If I understand you correctly, that
> would match the symptoms you describe.

Yes, I think that this is the best solution.

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

Title:
  test failure - test-regex

Status in grep:
  Fix Released
Status in grep package in Ubuntu:
  New

Bug description:
  'test-regex' fails when building grep against glibc 2.34.
  Per commentary from grep upstream at 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, 
  the test failure can be attributed to skew between the glibc built-in regex 
and the one that is found in the grep source code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]

[Paul Eggert]

(In reply to Vincent Lefèvre from comment #19)

> regbug.c is derived from the attachment in Bug#17356 (as said in comment 5).
> I've tested this original testcase: with glibc 2.34 on x86_64, it crashes
> (segmentation fault); with glibc 2.35 on riscv64 (host gcc92), it outputs
> "no match (incorrect)".
> 
> So it seems that the fix mentioned in comment 13 fixed the crashes (which
> was the initial bug report), but not the misbehavior.

OK, so in that case how about if we update Bug#17356 by (1) saying it is
no longer a duplicate of Bug#11053 (as we've fixed the latter but not
the former), and (2) reopening Bug#17536? If I understand you correctly,
that would match the symptoms you describe.

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

Title:
  test failure - test-regex

Status in grep:
  Fix Released
Status in grep package in Ubuntu:
  New

Bug description:
  'test-regex' fails when building grep against glibc 2.34.
  Per commentary from grep upstream at 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, 
  the test failure can be attributed to skew between the glibc built-in regex 
and the one that is found in the grep source code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]

[Paul Eggert]

(In reply to Vincent Lefèvre from comment #16)
> (In reply to eggert from comment #15)
> > glibc bug 11053 is fixed,
> 
> Shouldn't this bug be resolved as fixed, then?

OK, done.


> > Perhaps a better match for 
> > Debian bug 884075 is glibc bug 10844.
> 
> It seems different.

In that case it might be better to file a new glibc bug report, one that
corresponds more closely to Debian bug 884075.

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

Title:
  test failure - test-regex

Status in grep:
  Fix Released
Status in grep package in Ubuntu:
  New

Bug description:
  'test-regex' fails when building grep against glibc 2.34.
  Per commentary from grep upstream at 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, 
  the test failure can be attributed to skew between the glibc built-in regex 
and the one that is found in the grep source code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]

[Vincent-srcware]

Sorry, actually both regbug.c and rebug2.c fail as they return the exit
status 1 (with my usual configuration, my prompt shows any non-zero exit
status, but this is not the case of the machine on which I had done the
test, so that I missed the failure initially):

vinc17@gcc92:~$ ./regbug
vinc17@gcc92:~$ echo $?
1
vinc17@gcc92:~$ ./rebug2
vinc17@gcc92:~$ echo $?
1

However, in the test from Paolo Bonzini's bug report (comment 0), grep
no longer crashes (while it still crashes with glibc 2.34, which does
not have the fix).

regbug.c is derived from the attachment in Bug#17356 (as said in comment
5). I've tested this original testcase: with glibc 2.34 on x86_64, it
crashes (segmentation fault); with glibc 2.35 on riscv64 (host gcc92),
it outputs "no match (incorrect)".

So it seems that the fix mentioned in comment 13 fixed the crashes
(which was the initial bug report), but not the misbehavior.

Now, with these new details, is it still OK to regard this bug as fixed
and that the misbehavior (rebug.c from Bug#17356; regbug.c and rebug2.c
from this bug) is actually a new bug?

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

Title:
  test failure - test-regex

Status in grep:
  Fix Released
Status in grep package in Ubuntu:
  New

Bug description:
  'test-regex' fails when building grep against glibc 2.34.
  Per commentary from grep upstream at 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, 
  the test failure can be attributed to skew between the glibc built-in regex 
and the one that is found in the grep source code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]

[Vincent-srcware]

(In reply to eggert from comment #15)
> glibc bug 11053 is fixed,

Shouldn't this bug be resolved as fixed, then?

> but Debian bug 884075 is not fixed. Perhaps a better match for 
> Debian bug 884075 is glibc bug 10844.

It seems different. With Debian bug 884075, the "|^1?$" part is
important (it yields the incorrect output, even though this part isn't
matched), and there is nothing like that in glibc bug 10844:

vinc17@gcc92:~$ echo 111 | grep --color=auto -E '^(11+)\1+$|^1?$'
111
vinc17@gcc92:~$ echo 111 | grep --color=auto -E '^(11+)\1+$'
vinc17@gcc92:~$ 

Note that for the first command, nothing is colored in "111",
i.e. the line is output as appeared to be matched, but no matches are
shown by colors. As a comparison, with ten 1s instead of eleven, the
line is output and the ten 1s are colored.

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

Title:
  test failure - test-regex

Status in grep:
  Fix Released
Status in grep package in Ubuntu:
  New

Bug description:
  'test-regex' fails when building grep against glibc 2.34.
  Per commentary from grep upstream at 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, 
  the test failure can be attributed to skew between the glibc built-in regex 
and the one that is found in the grep source code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]

[Vincent-srcware]

This could be simplified a bit:

vinc17@gcc92:~$ echo 111 | grep --color=auto -E '^(11+)\1+$|^$'
111

(nothing colored).

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

Title:
  test failure - test-regex

Status in grep:
  Fix Released
Status in grep package in Ubuntu:
  New

Bug description:
  'test-regex' fails when building grep against glibc 2.34.
  Per commentary from grep upstream at 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, 
  the test failure can be attributed to skew between the glibc built-in regex 
and the one that is found in the grep source code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]

[Paul Eggert]

On 9/5/22 18:06, vincent-srcware at vinc17 dot net wrote:
>
> What is the status of this bug? The comment says that it is fixed, and I could
> check on an Ubuntu 22.04.1 LTS machine with libc6 2.35-0ubuntu3.1 that 
> regbug.c
> and rebug2.c no longer fail, but the result is still incorrect with the grep
> example from Debian bug 884075:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884075
>
> vinc17@gcc92:~$ echo 111 | grep -E '^(11+)\1+$|^1?$' ; echo $?
> 111
> 0
>
It looks like my comment 
 was 
incorrect, in that the two bugs are different bugs. glibc bug 11053 is 
fixed, but Debian bug 884075 is not fixed. Perhaps a better match for 
Debian bug 884075 is glibc bug 10844.

It's not an important bug. However, if you have time to fix it please 
feel free to send in a fix.

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

Title:
  test failure - test-regex

Status in grep:
  Fix Released
Status in grep package in Ubuntu:
  New

Bug description:
  'test-regex' fails when building grep against glibc 2.34.
  Per commentary from grep upstream at 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, 
  the test failure can be attributed to skew between the glibc built-in regex 
and the one that is found in the grep source code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grep/+bug/1940996/+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 1988772] Re: kinetic livefs builds are failing on dns errors

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/429535

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

Title:
  kinetic livefs builds are failing on dns errors

Status in live-build package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  the livefs kinetic builds are still failing, every job failed for a
  week

  https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/kinetic/ubuntu

  >'Temporary failure resolving 'ftpmaster.internal'

  Colin poked at it and wrote

  > livecd-rootfs initially sets up a correct /etc/resolv.conf inside its build 
chroot; but then
  > systemd-resolved.postinst moves that aside in favour of a symlink to 
/run/systemd/resolve/stub-
  > resolv.conf, but systemd-resolved itself isn't running because 
livecd-rootfs builds in a chroot, 
  > not a container

  he also suggested that it could be perhaps handled from live-build
  scripts/build/lb_chroot_resolv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1988772/+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 1988230] Re: glib 2.73 breaks modemmanager

[Bug Watch Updater]

** Changed in: glib
   Status: Fix Released => New

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

Title:
  glib 2.73 breaks modemmanager

Status in GLib:
  New
Status in glib2.0 package in Ubuntu:
  Triaged
Status in modemmanager package in Ubuntu:
  Fix Released
Status in glib2.0 package in Debian:
  Confirmed

Bug description:
  I'm filing this bug in case we want to fix it before letting glib 2.73
  in to kinetic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1988230/+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 1971901] Re: dlltool uses non-unique temp filenames

[John Goodman]

This is fixed upstream in 2.39... can we have updated packages for
ubuntu? Some other distros have it already.

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

Title:
  dlltool uses non-unique temp filenames

Status in binutils:
  Fix Released
Status in Wine:
  Won't Fix
Status in binutils package in Ubuntu:
  Confirmed
Status in binutils-mingw-w64 package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1

  /usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like

  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.delay.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec
  Assembler messages:
  Error: can't open winmm_dll_t.s for reading: No such file or directory
  /usr/bin/x86_64-w64-mingw32-dlltool: /usr/bin/x86_64-w64-mingw32-as exited 
with status 1
  /usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: 
winmm_dll_t.o: No such file or directory
  winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1
  make: *** [Makefile:195227: dlls/winmm/libwinmm.delay.a] Error 1
  make: *** Waiting for unfinished jobs
  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.cross.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec

  Due to dlltool using names like winmm_dll_t.s and winmm_dll_t.o for
  it's temp file - these are not unique when building libwinmm.delay.a
  and libwinmm.cross.a in parallel. (This can of course affect any dll
  wine is building import libs for, winmm is just the one I happaned to
  get caught on).

  This is regression newly introduced in binutils 2.38 vs older versions
  which used getpid() as the basis of their temp name. We just
  encountered it as part of updating our CI for a winelib application
  from focal to jammy, but it seems to have been discovered by others
  already: see https://sourceware.org/bugzilla/show_bug.cgi?id=28885

  There is an upstream fix on master (2.39) which is already backported
  to the binutils-2_38 branch:
  https://sourceware.org/git/gitweb.cgi?p=binutils-
  gdb.git;h=99852365513266afdd793289813e8e565186c9e6, so it should just
  be a matter of cherry-picking. Hopefully the fact it's a regression
  from impish->jammy and that upstream already backported it to 2.38
  might make this a candidate for jammy-updates?

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1971901/+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 1973231] Re: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Brian Murray]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition.  Please resolve this situation manually and try
the update again.

** This bug is no longer a duplicate of bug 1956835
   zsys cleanup of /boot should be reevaluated

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Tags added: no-boot-space

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

Title:
  package initramfs-tools 0.140ubuntu13 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  recent upgrade from 21.10 to 22.04, now i see this message at startup
  of the GUI.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30
  Uname: Linux 5.15.0-27-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed May  4 20:31:09 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-07-18 (298 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: /usr/bin/python3.10, Python 3.10.4, python-is-python3, 3.9.2-2
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-05-04 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1973231/+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 1977897] Re: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Brian Murray]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition.  Please resolve this situation manually and try
the update again.

** This bug is no longer a duplicate of bug 1956835
   zsys cleanup of /boot should be reevaluated

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Tags added: no-boot-space

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

Title:
  package initramfs-tools 0.140ubuntu13 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Error just popped up while I was browsing, i.e. I was not upgrading at
  the time.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   ntfs-3g:amd64: Install
   libntfs-3g89:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jun  7 20:22:10 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-10-30 (220 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: /usr/bin/python3.10, Python 3.10.4, python-is-python3, 3.9.2-2
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1977897/+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 1977647] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error

[Brian Murray]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition.  Please resolve this situation manually and try
the update again.

** This bug is no longer a duplicate of bug 1956835
   zsys cleanup of /boot should be reevaluated

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Tags added: no-boot-space

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

Title:
  package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to
  install/upgrade: installed linux-firmware package post-installation
  script subprocess returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  I didn't perform any action to get this crash.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-lowlatency 5.15.30
  Uname: Linux 5.15.0-33-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marqrdt   676730 F pulseaudio
   /dev/snd/controlC0:  marqrdt   676730 F pulseaudio
   /dev/snd/controlC1:  marqrdt   676730 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue May 31 11:25:55 2022
  Dependencies: firmware-sof-signed 2.0-1ubuntu3
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-07-09 (330 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI
  PackageArchitecture: all
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-lowlatency 
root=/dev/mapper/vgubuntu-root ro threadirqs quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: /usr/bin/python3.10, Python 3.10.4, python-is-python3, 3.9.2-2
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7
  SourcePackage: initramfs-tools
  Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to 
install/upgrade: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (43 days ago)
  dmi.bios.date: 06/13/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS PRO WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/13/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1977647/+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 1978068] Re: initramfs-tools 0.140ubuntu13 failed to install/upgrade: update-initramfs fails: No space left on device

[Brian Murray]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition.  Please resolve this situation manually and try
the update again.

** This bug is no longer a duplicate of bug 1956835
   zsys cleanup of /boot should be reevaluated

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Tags added: no-boot-space

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

Title:
  initramfs-tools 0.140ubuntu13 failed to install/upgrade: update-
  initramfs fails: No space left on device

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  The error appeared right after login and was caught by the Ubuntu
  error reporting tool.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   ntfs-3g:amd64: Install
   libntfs-3g89:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jun  9 09:33:58 2022
  ErrorMessage: »installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2022-01-17 (142 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
»installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to jammy on 2022-05-03 (36 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1978068/+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 1979199] Re: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: podproces zainstalowany pakiet initramfs-tools skrypt post-installation zwrócił kod błędu 1

[Brian Murray]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition.  Please resolve this situation manually and try
the update again.

** This bug is no longer a duplicate of bug 1956835
   zsys cleanup of /boot should be reevaluated

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Tags added: no-boot-space

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

Title:
  package initramfs-tools 0.140ubuntu13 failed to install/upgrade:
  podproces zainstalowany pakiet initramfs-tools skrypt post-
  installation zwrócił kod błędu 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  :)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   intel-microcode:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Jun 20 12:06:16 2022
  ErrorMessage: podproces zainstalowany pakiet initramfs-tools skrypt 
post-installation zwrócił kod błędu 1
  InstallationDate: Installed on 2020-09-18 (639 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
podproces zainstalowany pakiet initramfs-tools skrypt post-installation zwrócił 
kod błędu 1
  UpgradeStatus: Upgraded to jammy on 2022-06-12 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1979199/+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 1979990] Re: package linux-image-5.15.0-39-generic 5.15.0-39.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Brian Murray]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition.  Please resolve this situation manually and try
the update again.

** This bug is no longer a duplicate of bug 1956835
   zsys cleanup of /boot should be reevaluated

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Tags added: no-boot-space

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

Title:
  package linux-image-5.15.0-39-generic 5.15.0-39.42 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Also:

  $ sudo apt purge linux-image-unsigned-5.15.0-35-generic 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Package 'linux-image-unsigned-5.15.0-35-generic' is not installed, so not 
removed
  The following packages were automatically installed and are no longer 
required:
linux-headers-5.15.0-35 linux-headers-5.15.0-35-generic 
linux-headers-5.15.0-39 linux-headers-5.15.0-39-generic
linux-image-5.15.0-35-generic linux-image-5.15.0-39-generic 
linux-modules-5.15.0-35-generic linux-modules-5.15.0-39-generic
linux-modules-extra-5.15.0-35-generic linux-modules-extra-5.15.0-39-generic
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 92 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up linux-image-5.15.0-39-generic (5.15.0-39.42) ...
  Processing triggers for linux-image-5.15.0-39-generic (5.15.0-39.42) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 5.15.0-39-generic
 ...done.
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.15.0-39-generic
  I: The initramfs will attempt to resume from /dev/dm-2
  I: (/dev/mapper/vgubuntu-swap_1)
  I: Set the RESUME variable to override this.
  zstd: error 25 : Write error : No space left on device (cannot write 
compressed block) 
  E: mkinitramfs failure zstd -q -1 -T0 25
  update-initramfs: failed for /boot/initrd.img-5.15.0-39-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  dpkg: error processing package linux-image-5.15.0-39-generic (--configure):
   installed linux-image-5.15.0-39-generic package post-installation script 
subprocess returned error exit status 1
  Errors were encountered while processing:
   linux-image-5.15.0-39-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-39-generic 5.15.0-39.42
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fdimeglio   2053 F pulseaudio
   /dev/snd/controlC0:  fdimeglio   2053 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Mon Jun 27 06:47:12 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-01-16 (161 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-39-generic 5.15.0-39.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (60 days ago)
  dmi.bios.date: 06/16/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5851
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Touch-packages] [Bug 1969182] Re: package linux-image-5.15.0-25-generic 5.15.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Brian Murray]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to update the kernel on your system due to a lack of free space
in your boot partition.  Please resolve this situation manually and try
the update again.

** This bug is no longer a duplicate of bug 1956835
   zsys cleanup of /boot should be reevaluated

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Tags added: no-boot-space

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

Title:
  package linux-image-5.15.0-25-generic 5.15.0-25.25 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Have this problem and kernel panic when boot on 5.15.0-25.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  grid   2148 F pulseaudio
   /dev/snd/pcmC0D0p:   grid   2148 F...m pulseaudio
  CasperMD5CheckResult: fail
  Date: Fri Apr 15 08:32:07 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-04-04 (10 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: LENOVO 20RA002SRT
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/vg_core-sys ro quite splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-25-generic 5.15.0-25.25 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R16ET33W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20RA002SRT
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrR16ET33W(1.19):bd09/15/2021:br1.19:efr1.13:svnLENOVO:pn20RA002SRT:pvrThinkPadE14:rvnLENOVO:rn20RA002SRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14:
  dmi.product.family: ThinkPad E14
  dmi.product.name: 20RA002SRT
  dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14
  dmi.product.version: ThinkPad E14
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1969182/+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 1980560] Re: package nvidia-kernel-common-470 470.129.06-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-kernel-common-470 package post-installation script subproces

[Brian Murray]

Actually, it looks like you ran out of free space in your /boot
partition on your live usb drive. This is a situation you'll need to
resolve manually.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  package nvidia-kernel-common-470 470.129.06-0ubuntu0.22.04.1 failed to
  install/upgrade: installed nvidia-kernel-common-470 package post-
  installation script subprocess returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  driver won't install

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-kernel-common-470 470.129.06-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Jul  2 10:08:00 2022
  ErrorMessage: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  SourcePackage: initramfs-tools
  Title: package nvidia-kernel-common-470 470.129.06-0ubuntu0.22.04.1 failed to 
install/upgrade: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1980560/+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 1980560] Re: package nvidia-kernel-common-470 470.129.06-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-kernel-common-470 package post-installation script subproces

[Brian Murray]

** This bug is no longer a duplicate of bug 1956835
   zsys cleanup of /boot should be reevaluated

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

Title:
  package nvidia-kernel-common-470 470.129.06-0ubuntu0.22.04.1 failed to
  install/upgrade: installed nvidia-kernel-common-470 package post-
  installation script subprocess returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  driver won't install

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-kernel-common-470 470.129.06-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Jul  2 10:08:00 2022
  ErrorMessage: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  SourcePackage: initramfs-tools
  Title: package nvidia-kernel-common-470 470.129.06-0ubuntu0.22.04.1 failed to 
install/upgrade: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1980560/+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 1988819] Re: When apt keeps back packages due to phased updates, it should say so

[Julian Andres Klode]

We can't really store reasons for why something is kept back. And if we
managed to do that, we'd end up with an untranslated line in the middle
of the output for every non-English locale until it's translated and apt
updated (it does not use language packs).

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

Title:
  When apt keeps back packages due to phased updates, it should say so

Status in apt package in Ubuntu:
  New

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+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 1988661] Re: Having network issues on server with error: networkd-dispatcher[781]: WARNING:Unknown index 56 seen, reloading interface list systemd-udevd[455717]: ethtool: autoneg

[Brian Murray]

** Tags added: focal

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

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

Title:
  Having network issues on server with error: networkd-dispatcher[781]:
  WARNING:Unknown index 56 seen, reloading interface list systemd-
  udevd[455717]: ethtool: autonegotiation is unset or enabled, the speed
  and duplex are not writable.

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi!
  My server has this rare intermittent error - 
  networkd-dispatcher[781]: WARNING:Unknown index 56 seen, reloading interface 
list
  systemd-udevd[455717]: ethtool: autonegotiation is unset or enabled, the 
speed and duplex are not writable.

  This causes failure of network for some time. I'm using kubernetes so
  my probes start failing and pods get killed.

  Ideally this error should not be coming.

  What is the root cause of this problem?

  Ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988661/+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 1988661] [NEW] Having network issues on server with error: networkd-dispatcher[781]: WARNING:Unknown index 56 seen, reloading interface list systemd-udevd[455717]: ethtool: auton

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi!
My server has this rare intermittent error - 
networkd-dispatcher[781]: WARNING:Unknown index 56 seen, reloading interface 
list
systemd-udevd[455717]: ethtool: autonegotiation is unset or enabled, the speed 
and duplex are not writable.

This causes failure of network for some time. I'm using kubernetes so my
probes start failing and pods get killed.

Ideally this error should not be coming.

What is the root cause of this problem?

Ubuntu 20.04

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


** Tags: bot-comment focal
-- 
Having network issues on server with error: networkd-dispatcher[781]: 
WARNING:Unknown index 56 seen, reloading interface list systemd-udevd[455717]: 
ethtool: autonegotiation is unset or enabled, the speed and duplex are not 
writable.
https://bugs.launchpad.net/bugs/1988661
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1988819] Re: When apt keeps back packages due to phased updates, it should say so

[Seth Arnold]

I have seen many people on IRC *very* upset after wasting a lot of time
trying to install updates that apt will not let them install. Fixing
this is critical to our reputation.

Thanks

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

Title:
  When apt keeps back packages due to phased updates, it should say so

Status in apt package in Ubuntu:
  New

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+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 1988870] [NEW] apport-autoreport.service fails: whoopsie.path is not enabled

[satmandu]

Public bug reported:

This is what the service reports. Aside from crash reports no longer
uploading automatically, I'm having trouble pointing ubuntu-bug to crash
reports in /var/crash - a window opens, but then a browser never opens.
ubuntu-bug program-name does open the browser though.

× apport-autoreport.service - Process error reports when automatic reporting is 
enabled
 Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static)
 Active: failed (Result: exit-code) since Tue 2022-09-06 14:27:48 EDT; 2min 
33s ago
TriggeredBy: ● apport-autoreport.path
 ● apport-autoreport.timer
Process: 24994 ExecStart=/usr/share/apport/whoopsie-upload-all --timeout 20 
(code=exited, status=1/FAILURE)
   Main PID: 24994 (code=exited, status=1/FAILURE)
CPU: 115ms

Sep 06 14:27:48 mbp113 systemd[1]: Starting Process error reports when 
automatic reporting is enabled...
Sep 06 14:27:48 mbp113 whoopsie-upload-all[24994]: ERROR: whoopsie.path is not 
enabled
Sep 06 14:27:48 mbp113 systemd[1]: apport-autoreport.service: Main process 
exited, code=exited, status=1/FAILURE
Sep 06 14:27:48 mbp113 systemd[1]: apport-autoreport.service: Failed with 
result 'exit-code'.
Sep 06 14:27:48 mbp113 systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: apport 2.23.0-0ubuntu1
Uname: Linux 6.0.0-rc4 x86_64
NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
ApportLog:
 ERROR: apport (pid 20795) Tue Sep  6 14:26:35 2022: called for pid 3732, 
signal 6, core limit 0, dump mode 1
 ERROR: apport (pid 20795) Tue Sep  6 14:26:35 2022: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
 ERROR: apport (pid 20795) Tue Sep  6 14:26:36 2022: debug: session gdbus call: 
(true,)
 
 ERROR: apport (pid 20795) Tue Sep  6 14:26:46 2022: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CrashReports:
 640:1000:123:43075180:2022-09-06 14:26:45.388720512 -0400:2022-09-06 
14:27:48.608538333 -0400:/var/crash/_usr_bin_gnome-shell.1000.crash
 640:1000:123:8681261:2022-08-29 22:32:29.231918756 -0400:2022-08-29 
20:57:41.939131333 -0400:/var/crash/_usr_libexec_goa-daemon.1000.crash
 640:1000:123:44557691:2022-08-30 08:01:54.998418753 -0400:2022-08-30 
08:01:50.202489325 -0400:/var/crash/_opt_google_chrome_chrome.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  6 14:29:03 2022
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kinetic third-party-packages wayland-session

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

Title:
  apport-autoreport.service fails: whoopsie.path is not enabled

Status in apport package in Ubuntu:
  New

Bug description:
  This is what the service reports. Aside from crash reports no longer
  uploading automatically, I'm having trouble pointing ubuntu-bug to
  crash reports in /var/crash - a window opens, but then a browser never
  opens. ubuntu-bug program-name does open the browser though.

  × apport-autoreport.service - Process error reports when automatic reporting 
is enabled
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static)
   Active: failed (Result: exit-code) since Tue 2022-09-06 14:27:48 EDT; 
2min 33s ago
  TriggeredBy: ● apport-autoreport.path
   ● apport-autoreport.timer
  Process: 24994 ExecStart=/usr/share/apport/whoopsie-upload-all --timeout 
20 (code=exited, status=1/FAILURE)
 Main PID: 24994 (code=exited, status=1/FAILURE)
  CPU: 115ms

  Sep 06 14:27:48 mbp113 systemd[1]: Starting Process error reports when 
automatic reporting is enabled...
  Sep 06 14:27:48 mbp113 whoopsie-upload-all[24994]: ERROR: whoopsie.path is 
not enabled
  Sep 06 14:27:48 mbp113 systemd[1]: apport-autoreport.service: Main process 
exited, code=exited, status=1/FAILURE
  Sep 06 14:27:48 mbp113 systemd[1]: apport-autoreport.service: Failed with 
result 'exit-code'.
  Sep 06 14:27:48 mbp113 systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apport 2.23.0-0ubuntu1
  Uname: Linux 6.0.0-rc4 x86_64
  NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 20795) Tue Sep  6 14:26:35 2022: called for pid 3732, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 20795) Tue Sep  6 14:26:35 2022: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
   ERROR: apport (pid 20795) 

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

[Jorge Merlino]

This big is fixed in kinetic

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

** Changed in: pulseaudio (Ubuntu Jammy)
 Assignee: (unassigned) => Jorge Merlino (jorge-merlino)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Committed

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

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

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

Title:
  Pulsaudio crashes once BT microphone is connected

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

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

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

  I've identified the upstream fix for this:

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

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

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

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


-- 
Mailing list: https://launchpad.net/~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 1988864] [NEW] Screen freezes after display turns on from standby

[user722]

Public bug reported:

This happens after automatic Blank Screen about 25% of the time. Mouse
cursor doesn't move and alt-tab doesn't work.

Workaround: ctrl-alt-f3, ctrl-alt-f1, login screen appears.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  6 14:13:08 2022
DistUpgraded: 2022-07-28 04:25:49,168 DEBUG icon theme changed, re-reading
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Kaveri [Radeon R7 Graphics] [1043:85cb]
InstallationDate: Installed on 2020-06-25 (802 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=25ac8a19-c1fe-4cac-a26c-50c592bf9181 ro quiet splash 
video=HDMI-A-1:1920x1080M@72 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to jammy on 2022-07-28 (40 days ago)
dmi.bios.date: 04/14/2017
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3004
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88XM-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3004:bd04/14/2017:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze jammy ubuntu wayland-session

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

Title:
  Screen freezes after display turns on from standby

Status in xorg package in Ubuntu:
  New

Bug description:
  This happens after automatic Blank Screen about 25% of the time. Mouse
  cursor doesn't move and alt-tab doesn't work.

  Workaround: ctrl-alt-f3, ctrl-alt-f1, login screen appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 14:13:08 2022
  DistUpgraded: 2022-07-28 04:25:49,168 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] 
[1002:130f] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Kaveri [Radeon R7 Graphics] [1043:85cb]
  InstallationDate: Installed on 2020-06-25 (802 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=25ac8a19-c1fe-4cac-a26c-50c592bf9181 ro quiet splash 
video=HDMI-A-1:1920x1080M@72 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 

[Touch-packages] [Bug 1888004] Re: Bash crashed with exit code 2 after a makefile script ended up with make saying "Clang - no input files"

[Seija K.]

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1888004/+attachment/5393623/+files/Dependencies.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1888004/+attachment/5393624/+files/ProcCpuinfoMinimal.txt

** Information type changed from Public to Private

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

Title:
  Bash crashed with exit code 2 after a makefile script ended up with
  make saying "Clang - no input files"

Status in bash package in Ubuntu:
  New

Bug description:
  Immediately after I ran the build script in bash in vscode, the moment
  the "clang - no input files" error appeared, bash crashed with an exit
  code of 2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bash 5.0-6ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Fri Jul 17 14:30:11 2020
  InstallationDate: Installed on 2020-07-06 (10 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1888004/+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 1987523] Re: Pulsaudio crashes once BT microphone is connected

[Jorge Merlino]

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Jorge Merlino (jorge-merlino)

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

Title:
  Pulsaudio crashes once BT microphone is connected

Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

  I've identified the upstream fix for this:

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

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

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

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


-- 
Mailing list: https://launchpad.net/~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 1988643] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1988643/+attachment/5614066/+files/StacktraceSource.txt

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

Title:
  ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Status in ibus package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: ibus 1.5.27-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  4 02:00:33 2022
  Disassembly: => 0x7f4e338e34f0:   Cannot access memory at address 
0x7f4e338e34f0
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '--priority=warning', '--since=@1662228023', 
'--until=@1662228043'] failed with exit code 1: Hint: You are currently not 
seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/libexec/ibus-x11
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7f4e338e34f0:Cannot access memory at address 
0x7f4e338e34f0
   PC (0x7f4e338e34f0) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: nordvpn sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1988643/+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 1988643] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1988643/+attachment/5614067/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1988643/+attachment/5613467/+files/CoreDump.gz

** Changed in: ibus (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Status in ibus package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: ibus 1.5.27-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  4 02:00:33 2022
  Disassembly: => 0x7f4e338e34f0:   Cannot access memory at address 
0x7f4e338e34f0
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '--priority=warning', '--since=@1662228023', 
'--until=@1662228043'] failed with exit code 1: Hint: You are currently not 
seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/libexec/ibus-x11
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7f4e338e34f0:Cannot access memory at address 
0x7f4e338e34f0
   PC (0x7f4e338e34f0) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: nordvpn sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1988643/+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 1988643] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1988643/+attachment/5614065/+files/Stacktrace.txt

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

Title:
  ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Status in ibus package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: ibus 1.5.27-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  4 02:00:33 2022
  Disassembly: => 0x7f4e338e34f0:   Cannot access memory at address 
0x7f4e338e34f0
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '--priority=warning', '--since=@1662228023', 
'--until=@1662228043'] failed with exit code 1: Hint: You are currently not 
seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/libexec/ibus-x11
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7f4e338e34f0:Cannot access memory at address 
0x7f4e338e34f0
   PC (0x7f4e338e34f0) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: nordvpn sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1988643/+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 1988643] ibus-x11 crashed with SIGSEGV in g_closure_invoke()

[Apport retracing service]

StacktraceTop:
 ?? ()
 g_closure_invoke (closure=0x5585a8f5d740, return_value=0x0, n_param_values=2, 
param_values=0x7fffa8e38000, invocation_hint=0x7fffa8e37f80) at 
../../../gobject/gclosure.c:832
 signal_emit_unlocked_R.isra.0 (node=node@entry=0x5585a8e36990, 
detail=detail@entry=349, instance=instance@entry=0x5585a8e98840, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffa8e38000) at 
../../../gobject/gsignal.c:3796
 g_signal_emit_valist (instance=, signal_id=, 
detail=, var_args=var_args@entry=0x7fffa8e381c0) at 
../../../gobject/gsignal.c:3549
 g_signal_emit (instance=, signal_id=, 
detail=) at ../../../gobject/gsignal.c:3606

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

Title:
  ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Status in ibus package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: ibus 1.5.27-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  4 02:00:33 2022
  Disassembly: => 0x7f4e338e34f0:   Cannot access memory at address 
0x7f4e338e34f0
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '--priority=warning', '--since=@1662228023', 
'--until=@1662228043'] failed with exit code 1: Hint: You are currently not 
seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/libexec/ibus-x11
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7f4e338e34f0:Cannot access memory at address 
0x7f4e338e34f0
   PC (0x7f4e338e34f0) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: nordvpn sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1988643/+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 1988644] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1988644/+attachment/5614070/+files/ThreadStacktrace.txt

** Tags added: apport-failed-retrace

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

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

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


-- 
Mailing list: https://launchpad.net/~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 1988644] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1988644/+attachment/5614069/+files/StacktraceSource.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/1988644

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

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

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


-- 
Mailing list: https://launchpad.net/~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 1988644] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1988644/+attachment/5614068/+files/Stacktrace.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/1988644

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

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

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


-- 
Mailing list: https://launchpad.net/~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 1988644] NetworkManager crashed with SIGABRT in g_assertion_message_expr()

[Apport retracing service]

StacktraceTop:
 ?? () from /srv/vms/apport-sandbox-dir/Ubuntu 
22.10/amd64/report-sandbox/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7303.0
 ?? ()
 ?? ()
 ?? ()
 ?? () from /srv/vms/apport-sandbox-dir/Ubuntu 
22.10/amd64/report-sandbox/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7303.0

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  occurred when toggle darkmode

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

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


-- 
Mailing list: https://launchpad.net/~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 1987625] Re: lxc: FTBFS against glibc 2.36.0

[Launchpad Bug Tracker]

This bug was fixed in the package lxc -
1:5.0.0~git2209-g5a7b9ce67-0ubuntu2

---
lxc (1:5.0.0~git2209-g5a7b9ce67-0ubuntu2) kinetic; urgency=medium

  * d/p/lp1987625/*.patch: cherry-picked to fix FTBFS against glibc 2.36
(LP: #1987625)
  * d/p/ppc64el-gcc12-warning.patch: work around a false positive warning in
GCC 12 on ppc64el due to it defaulting to -O3

 -- Simon Chopin   Fri, 26 Aug 2022 11:18:18 +0200

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

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

Title:
  lxc: FTBFS against glibc 2.36.0

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  lxc currently fails to build against glibc 2.36, which also affects
  its autopkgtests. Here's an excerpt of the failed build logs
  containing the first error detected:

  gcc -DHAVE_CONFIG_H -I. -I../../src   -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE 
-Wvla -std=gnu11 -fms-extensions -fdiagnostics-color -Wimplicit-fallthrough=5 
-Wcast-align -Wstrict-prototypes -fno-strict-aliasing -fstack-clash-protection 
-fstack-protector-strong --param=ssp-buffer-size=4 -g -fcf-protection 
-Werror=implicit-function-declaration -Wlogical-op -Wmissing-include-dirs 
-Wold-style-definition -Winit-self -Wunused-but-set-variable -Wfloat-equal 
-Wsuggest-attribute=noreturn -Werror=return-type 
-Werror=incompatible-pointer-types -Wformat=2 -Wshadow -Wendif-labels 
-Werror=overflow -fdiagnostics-show-option -Werror=shift-count-overflow 
-Werror=shift-overflow=2 -Wdate-time -Wnested-externs 
-fasynchronous-unwind-tables -pipe -fexceptions -Warray-bounds -Wrestrict 
-Wreturn-local-addr -Wstringop-overflow 
-DLXCROOTFSMOUNT=\"/usr/lib/x86_64-linux-gnu/lxc\" -DLXCPATH=\"/var/lib/lxc\" 
-DLXC_GLOBAL_CONF=\"/etc/lxc/lxc.conf\" 
-DLXCINITDIR=\"/usr/lib/x86_64-linux-gnu\" 
-DLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu\" 
-DLXCTEMPLATEDIR=\"/usr/share/lxc/templates\" 
-DLXCTEMPLATECONFIG=\"/usr/share/lxc/config\" -DLOGPATH=\"/var/log/lxc\" 
-DLXC_DEFAULT_CONFIG=\"/etc/lxc/default.conf\" 
-DLXC_USERNIC_DB=\"/run/lxc/nics\" -DLXC_USERNIC_CONF=\"/etc/lxc/lxc-usernet\" 
-DDEFAULT_CGROUP_PATTERN=\"\" -DRUNTIME_PATH=\"/run\" -DSBINDIR=\"/usr/sbin\" 
-DAPPARMOR_CACHE_DIR=\"/var/cache/lxc/apparmor\" -I ../../src -I 
../../src/include -I ../../src/lxc -I ../../src/lxc/storage -I 
../../src/lxc/cgroups -DHAVE_APPARMOR  -DHAVE_SECCOMP  -DHAVE_SELINUX   -g -O2 
-ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-Wvla -std=gnu11 -fms-extensions -Werror -c -o conf.o conf.c
  conf.c: In function ‘__lxc_idmapped_mounts_child’:
  conf.c:2993:37: error: passing argument 4 of ‘mount_setattr’ from 
incompatible pointer type [-Werror=incompatible-pointer-types]
   2993 | ,
| ^
| |
| struct lxc_mount_attr *
  In file included from conf.c:22:
  /usr/include/x86_64-linux-gnu/sys/mount.h:317:46: note: expected ‘struct 
mount_attr *’ but argument is of type ‘struct lxc_mount_attr *’
317 |   struct mount_attr *__uattr, size_t __usize)
|   ~~~^~~
  conf.c:3016:41: error: passing argument 4 of ‘mount_setattr’ from 
incompatible pointer type [-Werror=incompatible-pointer-types]
   3016 | ,
| ^
| |
| struct lxc_mount_attr *
  /usr/include/x86_64-linux-gnu/sys/mount.h:317:46: note: expected ‘struct 
mount_attr *’ but argument is of type ‘struct lxc_mount_attr *’
317 |   struct mount_attr *__uattr, size_t __usize)
|   ~~~^~~
  conf.c: In function ‘lxc_idmapped_mounts_parent’:
  conf.c:4130:37: error: passing argument 4 of ‘mount_setattr’ from 
incompatible pointer type [-Werror=incompatible-pointer-types]
   4130 | , sizeof(attr));
| ^
| |
| struct lxc_mount_attr *
  /usr/include/x86_64-linux-gnu/sys/mount.h:317:46: note: expected ‘struct 
mount_attr *’ but argument is of type ‘struct lxc_mount_attr *’
317 |   struct mount_attr *__uattr, size_t __usize)
|   ~~~^~~

  I believe the following upstream PR should fix the issue:
  https://github.com/lxc/lxc/pull/4181

  I'll be testing a patched version shortly and will post a debdiff if
  it pans out.

[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)

[murat esgin]

Hi. I have same error.

---
:~$ sudo dmesg | grep mtd 
[6.992949] systemd[1]: Starting Load Kernel Module mtdpstore...
[7.028962] mtd device must be supplied (device name is empty)
[7.073396] systemd[1]: modprobe@mtdpstore.service: Deactivated successfully.
[7.076597] systemd[1]: Finished Load Kernel Module mtdpstore.
[8.719446] mtd device must be supplied (device name is empty)
[8.992816] mtd device must be supplied (device name is empty)


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

Title:
  mtd device must be supplied (device name is empty)

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

Bug description:
  [WORKAROUND]

  This will NOT fix a system that is not booting, because the "mtd
  device must be supplied (device name is empty)" message is not the
  cause of failed boots. This work around is only for those who are
  annoyed by the error message, but are otherwise not experiencing any
  issues.

  If you are not able to boot your system, but you see this error
  message, please open a separate bug with your journalctl and dmesg
  logs.

  # cp /{lib,etc}/systemd/system/systemd-pstore.service
  # sed -i 's/modprobe@mtdpstore.service //' 
/etc/systemd/system/systemd-pstore.service
  # systemctl daemon-reload

  [Impact]

  Due to mtdpstore not being properly configured as a pstore backend,
  when systemd-pstore.service tries to load the module, users get the
  following error in dmesg:

  [   18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
  [   18.462685] mtd device must be supplied (device name is empty)

  This is a distracting error for users trying to diagnose other system
  issues, especially if their system does not boot after a kernel crash
  and this is the only message displayed on the console.

  [Test Plan]

  * Force a kernel crash to populate /sys/fs/pstore, thus causing
  systemd-pstore.service to start on the subsequent boot:

  # echo 1 > /proc/sys/kernel/sysrq
  # echo 1 > /proc/sys/kernel/panic
  # echo c > /proc/sysrq-trigger

  * When the system reboots, observe the error in dmesg:

  # dmesg | grep mtd

  [Where problems could occur]

  If a system was relying on this pstore backend, and mtdpstore is built
  as a module, it is possible for systemd-pstore.service to trigger
  before mtdpstore is loaded, causing systemd-pstore to not copy the
  contents of /sys/fs/pstore. Note however that before the patched
  introduced as a result of bug 1978079, systemd-pstore.service would
  not attempt to load *any* kernel modules.

  [Original Description]

  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1988629] Re: apt install libudev-dev fails on bionic (dependency conflict)

[Hans Joachim Desserud]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1988563, so it is being marked as such. Based on the
comments there, it seems like this is indeed due to the reverted systemd
update.

** This bug has been marked a duplicate of bug 1988563
   package libudev-dev dependency conflict

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

Title:
  apt install libudev-dev fails on bionic (dependency conflict)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following fails, this was broken within the last few days:

  docker run -it --rm ubuntu:bionic
  apt update
  apt install libudev-dev

  
  Output:
  ```
  ~$ docker run -it --rm ubuntu:bionic
  Unable to find image 'ubuntu:bionic' locally
  bionic: Pulling from library/ubuntu
  dad0f37c70a6: Pull complete
  Digest: 
sha256:3aa2ccb021969aadb28381fee1b247422e845b176e241cd1540c4b6831e000bb
  Status: Downloaded newer image for ubuntu:bionic
  root@391196612b51:/# apt update
  Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
  Get:2 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
  Get:3 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 
Packages [1114 kB]
  Get:4 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 
Packages [22.8 kB]
  Get:5 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 
[2953 kB]
  Get:6 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages [1540 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
  Get:8 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 
kB]
  Get:10 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages 
[13.5 kB]
  Get:11 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 
MB]
  Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1344 kB]
  Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 
Packages [29.9 kB]
  Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 
Packages [1162 kB]
  Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [2318 kB]
  Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 
[3390 kB]
  Get:17 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 
Packages [12.9 kB]
  Get:18 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages 
[12.2 kB]
  Fetched 25.9 MB in 2s (10.4 MB/s)
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  All packages are up to date.
  root@391196612b51:/# apt install libudev-dev
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libudev-dev : Depends: libudev1 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is 
to be installed
  E: Unable to correct problems, you have held broken packages.
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988629/+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 1988563] Re: package libudev-dev dependency conflict

[Hans Joachim Desserud]

** Tags added: bionic unmetdeps

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

Title:
  package libudev-dev dependency conflict

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am not sure if this is the right place to file this, but we are
  getting the following error when installing libudev-dev on bionic

  Installing libudev-dev fails for bionic with the following error:

  ```
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libudev-dev : Depends: libudev1 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is 
to be installed
  E: Unable to correct problems, you have held broken packages.
  ```

  Steps to reproduce:

  ```
  docker run -it --rm ubuntu:bionic
  apt update
  apt install libudev-dev
  ```

  Complete log:
  ```
  ~$ docker run -it --rm ubuntu:bionic
  Unable to find image 'ubuntu:bionic' locally
  bionic: Pulling from library/ubuntu
  dad0f37c70a6: Pull complete 
  Digest: 
sha256:3aa2ccb021969aadb28381fee1b247422e845b176e241cd1540c4b6831e000bb
  Status: Downloaded newer image for ubuntu:bionic
  root@391196612b51:/# apt update
  Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
  Get:2 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]  
 
  Get:3 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 
Packages [1114 kB]
  Get:4 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 
Packages [22.8 kB]
  Get:5 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 
[2953 kB]
  Get:6 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages [1540 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] 
 
  Get:8 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 
kB]
  Get:10 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages 
[13.5 kB]
  Get:11 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 
MB]
  Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1344 kB]
  Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 
Packages [29.9 kB]
  Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 
Packages [1162 kB]
  Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [2318 kB]
  Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 
[3390 kB]
  Get:17 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 
Packages [12.9 kB]
  Get:18 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages 
[12.2 kB]
  Fetched 25.9 MB in 2s (10.4 MB/s) 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  All packages are up to date.
  root@391196612b51:/# apt install libudev-dev
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libudev-dev : Depends: libudev1 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is 
to be installed
  E: Unable to correct problems, you have held broken packages.
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988563/+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 1981622] Re: mtd device must be supplied (device name is empty)

[Taha]

systemd 249.11-0ubuntu3.5 got rid of the error messages.

>From the bug definition:
"This will NOT fix a system that is not booting, because the "mtd device must 
be supplied (device name is empty)" message is not the cause of failed boots."

** Tags removed: verification-failed-jammy

** Tags added: verification-done-jammy

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

Title:
  mtd device must be supplied (device name is empty)

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

Bug description:
  [WORKAROUND]

  This will NOT fix a system that is not booting, because the "mtd
  device must be supplied (device name is empty)" message is not the
  cause of failed boots. This work around is only for those who are
  annoyed by the error message, but are otherwise not experiencing any
  issues.

  If you are not able to boot your system, but you see this error
  message, please open a separate bug with your journalctl and dmesg
  logs.

  # cp /{lib,etc}/systemd/system/systemd-pstore.service
  # sed -i 's/modprobe@mtdpstore.service //' 
/etc/systemd/system/systemd-pstore.service
  # systemctl daemon-reload

  [Impact]

  Due to mtdpstore not being properly configured as a pstore backend,
  when systemd-pstore.service tries to load the module, users get the
  following error in dmesg:

  [   18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
  [   18.462685] mtd device must be supplied (device name is empty)

  This is a distracting error for users trying to diagnose other system
  issues, especially if their system does not boot after a kernel crash
  and this is the only message displayed on the console.

  [Test Plan]

  * Force a kernel crash to populate /sys/fs/pstore, thus causing
  systemd-pstore.service to start on the subsequent boot:

  # echo 1 > /proc/sys/kernel/sysrq
  # echo 1 > /proc/sys/kernel/panic
  # echo c > /proc/sysrq-trigger

  * When the system reboots, observe the error in dmesg:

  # dmesg | grep mtd

  [Where problems could occur]

  If a system was relying on this pstore backend, and mtdpstore is built
  as a module, it is possible for systemd-pstore.service to trigger
  before mtdpstore is loaded, causing systemd-pstore to not copy the
  contents of /sys/fs/pstore. Note however that before the patched
  introduced as a result of bug 1978079, systemd-pstore.service would
  not attempt to load *any* kernel modules.

  [Original Description]

  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1969976] Autopkgtest regression report (fwupd/1.8.3-1~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted fwupd (1.8.3-1~22.04.1) for jammy have 
finished running.
The following regressions have been reported in tests triggered by the package:

fwupd/1.8.3-1~22.04.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#fwupd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  DynamicUser=1 doesn't get along with services that need dbus-daemon

Status in Fwupd:
  Fix Released
Status in systemd:
  New
Status in fwupd package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in fwupd source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Won't Fix
Status in fwupd source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix
Status in fwupd source package in Jammy:
  Fix Committed
Status in systemd source package in Jammy:
  Won't Fix

Bug description:
  Updating to systemd 245.4-4ubuntu3.16 has caused a regression in
  Ubuntu 20.04, that fwupd-refresh.service always fails to run.

  This has been root caused down to the changes in
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538

  Unfortunately this is an upstream issue introduced by stable systemd.
  https://github.com/systemd/systemd/issues/22737

  The problem also occurs in Ubuntu 22.04 with a newer systemd release.
  As discussed in 
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61
 it's a tradeoff of issues.  So within Ubuntu something probably needs to be 
done about fwupd-refresh.service.

  One proposal is to remove DynamicUser=yes from the systemd unit, but
  this will mean fwupdgmr refresh runs as root.  It's relatively
  sandboxed by other security mechanisms, but still not ideal.  Could we
  repurpose any other service account?  Or alternatively we can make a
  new fwupd service account that this systemd unit uses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon

[Steven Hay]

Aaron:

This step adds the repository to apt:

cat 

[Touch-packages] [Bug 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon

[Steven Hay]

I am on jammy and have tested the package.

Package: fwupd
Version: 1.8.3-1~22.04.1
Priority: optional
Section: admin
Origin: Ubuntu
Maintainer: Ubuntu Developers 

My testing has been to install the package then stop and start the
fwupd-refresh.service unit. The unit exited successfully.

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

Title:
  DynamicUser=1 doesn't get along with services that need dbus-daemon

Status in Fwupd:
  Fix Released
Status in systemd:
  New
Status in fwupd package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in fwupd source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Won't Fix
Status in fwupd source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix
Status in fwupd source package in Jammy:
  Fix Committed
Status in systemd source package in Jammy:
  Won't Fix

Bug description:
  Updating to systemd 245.4-4ubuntu3.16 has caused a regression in
  Ubuntu 20.04, that fwupd-refresh.service always fails to run.

  This has been root caused down to the changes in
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538

  Unfortunately this is an upstream issue introduced by stable systemd.
  https://github.com/systemd/systemd/issues/22737

  The problem also occurs in Ubuntu 22.04 with a newer systemd release.
  As discussed in 
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61
 it's a tradeoff of issues.  So within Ubuntu something probably needs to be 
done about fwupd-refresh.service.

  One proposal is to remove DynamicUser=yes from the systemd unit, but
  this will mean fwupdgmr refresh runs as root.  It's relatively
  sandboxed by other security mechanisms, but still not ideal.  Could we
  repurpose any other service account?  Or alternatively we can make a
  new fwupd service account that this systemd unit uses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon

[Aaron Carlton]

I would be happy to test this on 22.04. However, I am new to the
process. I followed the linked instructions to enable proposed
repository, but I don't see a fwupd/jammy-proposed available after an
apt-get update. I'm unfamiliar with the process -- does it just take
more time to get into -proposed, or is there some other step in the
pipeline needed to go from Fix Committed -> -proposed? I set the
software updater to use "Main Servers", thinking that a gap in mirroring
could be an issue, but it's been over 24h...

I know process issues probably don't belong here, but I would like to
learn how to get involved in things like this. Thanks in advance for
patience.

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

Title:
  DynamicUser=1 doesn't get along with services that need dbus-daemon

Status in Fwupd:
  Fix Released
Status in systemd:
  New
Status in fwupd package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in fwupd source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Won't Fix
Status in fwupd source package in Impish:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix
Status in fwupd source package in Jammy:
  Fix Committed
Status in systemd source package in Jammy:
  Won't Fix

Bug description:
  Updating to systemd 245.4-4ubuntu3.16 has caused a regression in
  Ubuntu 20.04, that fwupd-refresh.service always fails to run.

  This has been root caused down to the changes in
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538

  Unfortunately this is an upstream issue introduced by stable systemd.
  https://github.com/systemd/systemd/issues/22737

  The problem also occurs in Ubuntu 22.04 with a newer systemd release.
  As discussed in 
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61
 it's a tradeoff of issues.  So within Ubuntu something probably needs to be 
done about fwupd-refresh.service.

  One proposal is to remove DynamicUser=yes from the systemd unit, but
  this will mean fwupdgmr refresh runs as root.  It's relatively
  sandboxed by other security mechanisms, but still not ideal.  Could we
  repurpose any other service account?  Or alternatively we can make a
  new fwupd service account that this systemd unit uses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1988563] Re: package libudev-dev dependency conflict

[Mike Grice]

Just to confirm Justas' fix in comment #4 temporarily works around the
issue for me.  Thanks!

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

Title:
  package libudev-dev dependency conflict

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am not sure if this is the right place to file this, but we are
  getting the following error when installing libudev-dev on bionic

  Installing libudev-dev fails for bionic with the following error:

  ```
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libudev-dev : Depends: libudev1 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is 
to be installed
  E: Unable to correct problems, you have held broken packages.
  ```

  Steps to reproduce:

  ```
  docker run -it --rm ubuntu:bionic
  apt update
  apt install libudev-dev
  ```

  Complete log:
  ```
  ~$ docker run -it --rm ubuntu:bionic
  Unable to find image 'ubuntu:bionic' locally
  bionic: Pulling from library/ubuntu
  dad0f37c70a6: Pull complete 
  Digest: 
sha256:3aa2ccb021969aadb28381fee1b247422e845b176e241cd1540c4b6831e000bb
  Status: Downloaded newer image for ubuntu:bionic
  root@391196612b51:/# apt update
  Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
  Get:2 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]  
 
  Get:3 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 
Packages [1114 kB]
  Get:4 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 
Packages [22.8 kB]
  Get:5 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 
[2953 kB]
  Get:6 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages [1540 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] 
 
  Get:8 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 
kB]
  Get:10 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages 
[13.5 kB]
  Get:11 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 
MB]
  Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1344 kB]
  Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 
Packages [29.9 kB]
  Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 
Packages [1162 kB]
  Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [2318 kB]
  Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 
[3390 kB]
  Get:17 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 
Packages [12.9 kB]
  Get:18 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages 
[12.2 kB]
  Fetched 25.9 MB in 2s (10.4 MB/s) 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  All packages are up to date.
  root@391196612b51:/# apt install libudev-dev
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libudev-dev : Depends: libudev1 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is 
to be installed
  E: Unable to correct problems, you have held broken packages.
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988563/+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 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)

[Minx Ab]

As for #32 this might be helpful for some when it comes to:

sudo apt-key list | grep C8CAB6595FDFF622

do:

sudo APT_KEY_DONT_WARN_ON_DANGEROUS_USAGE=DontWarn apt-key list | grep
...

to get print to STDOUT.

Beside that I'm somewhat curious how this is an issue *now* when bug is
from 2021-03-20

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

Title:
  EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic
  Signing Key (2016) 

Status in ubuntu-keyring package in Ubuntu:
  Fix Released
Status in ubuntu-keyring source package in Bionic:
  Fix Released
Status in ubuntu-keyring source package in Focal:
  Fix Released
Status in ubuntu-keyring source package in Groovy:
  Fix Released
Status in ubuntu-keyring source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Cannot update apt metadata from ddebs.ubuntu.com whilst using
  ubuntu-dbgsym-keyring package

  [Test Plan]

   * Install ubuntu-dbgsym-keyring package
   * Add ddebs.ubuntu.com repository for your release
   * sudo apt update must be successful

   * Install ubuntu-dbgsym-keyring package
   * Install and use `apt-key list` and check that there is no expiry on the 
dbgsym key

  I.e. bad output
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 2021-03-20]
F2ED C64D C5AE E1F6 B9C6  21F0 C8CA B659 5FDF F622
  uid   [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) 

  
  Good output has no [date] in the pub line.

  [Where problems could occur]

   * At the moment the signature was bumped by one year
   * Meaning this issue will occur again in 2022
   * Instead the key must be set to not expire & new round of SRUs issued

  [Other Info]

   * Original bug report

  The public key used by the debugging symbols repository
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu-
  dbgsym-keyring expired.

  $ apt policy ubuntu-dbgsym-keyring
  ubuntu-dbgsym-keyring:
    Installed: 2020.02.11.2
    Candidate: 2020.02.11.2
    Version table:
   *** 2020.02.11.2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status
  $ gpg --no-default-keyring --keyring 
/usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 2021-03-20]
    F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622
  uid   [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) 

  Error message on "apt update":

  E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ddebs.ubuntu.com bionic Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive 
Automatic Signing Key (2016) 
  E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive 
Automatic Signing Key (2016) 
  E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+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 1988583] Re: ubuntu 18.04 cups network printer not working

[Terrence Buckey]

added information, the gui is seeing a canon printer in one of the
"adds", it does not see any network printer if you you a find network
printer.

Using the "Add" at the top of the printer gui, I was able to add the
Canon printer, and printer.conf has all the info.

The gui adds a MG3600 printer instead of the Canon_MG3600_series that
the qt qpinfo sees.

Looks like none of the command line commands can be used to add default
printer which breaks my embedded qt app.

Thanks,

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

Title:
  ubuntu 18.04 cups network printer not working

Status in cups package in Ubuntu:
  New

Bug description:
  all debug info from the ubuntu cup help page looks correct except that
  none of the snmp command work.

   netstat -rn
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG0 0  0 wlo1
  10.0.0.0192.168.168.54  255.255.0.0 UG0 0  0 ppp0
  10.0.0.00.0.0.0 255.255.0.0 U 0 0  0 eno2
  66.196.209.178  192.168.1.254   255.255.255.255 UGH   0 0  0 wlo1
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 eno2
  172.16.0.0  192.168.168.54  255.255.0.0 UG0 0  0 ppp0
  192.0.2.1   0.0.0.0 255.255.255.255 UH0 0  0 ppp0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 wlo1
  192.168.1.254   0.0.0.0 255.255.255.255 UH0 0  0 wlo1
  tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ ping 
1892.168.1.102
  ^C
  tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ ping 
192.168.1.102
  PING 192.168.1.102 (192.168.1.102) 56(84) bytes of data.
  64 bytes from 192.168.1.102: icmp_seq=1 ttl=64 time=50.6 ms
  64 bytes from 192.168.1.102: icmp_seq=2 ttl=64 time=5.60 ms
  64 bytes from 192.168.1.102: icmp_seq=3 ttl=64 time=5.75 ms
  ^C
  --- 192.168.1.102 ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2003ms
  rtt min/avg/max/mdev = 5.603/20.676/50.675/21.212 ms
  tbuckley@tbuckley-OptiPlex-7070:/mnt/sda/tbuckley/imxDevopment/sources$ nmap 
192.168.1.102

  Starting Nmap 7.60 ( https://nmap.org ) at 2022-09-02 10:11 CDT
  Nmap scan report for 192.168.1.102
  Host is up (0.035s latency).
  Not shown: 996 closed ports
  PORTSTATE SERVICE
  80/tcp  open  http
  443/tcp open  https
  515/tcp open  printer
  631/tcp open  ipp

  lpinfo -v gives
  network ipp
  file cups-brf:/
  network https
  network beh
  serial serial:/dev/ttyS0?baud=115200
  serial serial:/dev/ttyS4?baud=115200
  serial serial:/dev/ttyUSB0?baud=230400
  serial serial:/dev/ttyUSB1?baud=230400
  serial serial:/dev/ttyUSB2?baud=230400
  network lpd
  network http
  direct hp
  network socket
  network ipps
  direct hpfax
  network 
dnssd://Canon%20MG3600%20series._ipp._tcp.local/?uuid=--1000-8000-F4A997389B3C
  network ipp://389B3C00.local:631/ipp/print
  network cnijbe2://Canon/?port=net=F4-A9-97-38-9B-3C

  lpoptions -d Canon_MG3600_series
  device-uri=ipps://Canon%20MG3600%20series._ipps._tcp.local/ 
printer-info='Canon MG3600 series' printer-location 
printer-make-and-model='Canon MG3600 series' printer-type=83890204
  tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpoptions
  device-uri=ipps://Canon%20MG3600%20series._ipps._tcp.local/ 
printer-info='Canon MG3600 series' printer-location 
printer-make-and-model='Canon MG3600 series' printer-type=83890204
  tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpoptions -l
  lpoptions: Unable to get PPD file for Canon_MG3600_series: The printer or 
class does not exist.
  tbuckley@tbuckley-OptiPlex-7070:/tmp$ lpq
  lpq: Error - no default destination available.
  tbuckley@tbuckley-OptiPlex-7070:/tmp$ 

  this use to work but now it seems that cups is not setting the default
  printer using lpoption or something is failing in the setup.

  This is happening on a product and on my person ubuntu 18.04 home
  machine

  Thanks,
  Terry

  972-814-9422(c)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.9
  ProcVersionSignature: Ubuntu 5.4.0-124.140~18.04.1-generic 5.4.195
  Uname: Linux 5.4.0-124-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  2 10:13:02 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+bison-elk-cougar-mlk+X53
  InstallationDate: Installed on 2019-10-16 (1051 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lpstat:
   

[Touch-packages] [Bug 1988842] [NEW] [NUC11PAHi5, Realtek ALC256, Analog audio 3.5mmnot listed in Ubuntu GUI audio settings

[Mattias Andersson]

Public bug reported:

It is posible to apply "workaround" by adding options snd-hda-intel
model=dell-headset-multi in a -cong file in  /etc/modprobe.d/ then
restart.

Hardware is Intel NUC gen 11 and it has been out for over a year,
perhaps it is a good idea that a more permanent fix i being pushed in to
wherever it is required. Unfortunatly I do not have the competence to
solve this but it would make sense to make it work "out of the box" if
possible.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mattias 923 F pulseaudio
 /dev/snd/pcmC0D0c:   mattias 923 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  6 13:32:58 2022
InstallationDate: Installed on 2022-08-30 (6 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mattias 923 F pulseaudio
 /dev/snd/pcmC0D0c:   mattias 923 F...m pulseaudio
Symptom_Jack: Black Headphone Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [NUC11PAHi5, Realtek ALC256, Black Headphone Out, Rear] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2022
dmi.bios.release: 0.46
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PATGL357.0046.2022.0608.1909
dmi.board.name: NUC11PABi5
dmi.board.vendor: Intel Corporation
dmi.board.version: K90634-302
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 3.1
dmi.modalias: 
dmi:bvnIntelCorp.:bvrPATGL357.0046.2022.0608.1909:bd06/08/2022:br0.46:efr3.1:svnIntel(R)ClientSystems:pnNUC11PAHi5:pvrM15533-303:rvnIntelCorporation:rnNUC11PABi5:rvrK90634-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC11PAHi5000:
dmi.product.family: PA
dmi.product.name: NUC11PAHi5
dmi.product.sku: RNUC11PAHi5000
dmi.product.version: M15533-303
dmi.sys.vendor: Intel(R) Client Systems

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


** Tags: amd64 apport-bug jammy wayland-session

** Summary changed:

- [NUC11PAHi5, Realtek ALC256, BAnalog audio not listes in GUI settings
+ [NUC11PAHi5, Realtek ALC256, Analog audio 3.5mmnot listed in Ubuntu GUI audio 
settings

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

Title:
  [NUC11PAHi5, Realtek ALC256, Analog audio 3.5mmnot listed in Ubuntu
  GUI audio settings

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  It is posible to apply "workaround" by adding options snd-hda-intel
  model=dell-headset-multi in a -cong file in  /etc/modprobe.d/ then
  restart.

  Hardware is Intel NUC gen 11 and it has been out for over a year,
  perhaps it is a good idea that a more permanent fix i being pushed in
  to wherever it is required. Unfortunatly I do not have the competence
  to solve this but it would make sense to make it work "out of the box"
  if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mattias 923 F pulseaudio
   /dev/snd/pcmC0D0c:   mattias 923 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 13:32:58 2022
  InstallationDate: Installed on 2022-08-30 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mattias 923 F pulseaudio
   /dev/snd/pcmC0D0c:   mattias 923 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [NUC11PAHi5, Realtek ALC256, Black Headphone Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2022
  dmi.bios.release: 0.46
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PATGL357.0046.2022.0608.1909
  

[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)

[Dimitri John Ledkov]

I can add maintainer script to check and remove expired copies of
0xC8CAB6595FDFF622 and then like print a message that one needs to
install ubuntu-dbgsym-keyring

Unfortunately, I cannot automatically ask apt to install ubuntu-dbgsym-
keyring if expired dbgsym key is detected on disk =/

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

Title:
  EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic
  Signing Key (2016) 

Status in ubuntu-keyring package in Ubuntu:
  Fix Released
Status in ubuntu-keyring source package in Bionic:
  Fix Released
Status in ubuntu-keyring source package in Focal:
  Fix Released
Status in ubuntu-keyring source package in Groovy:
  Fix Released
Status in ubuntu-keyring source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Cannot update apt metadata from ddebs.ubuntu.com whilst using
  ubuntu-dbgsym-keyring package

  [Test Plan]

   * Install ubuntu-dbgsym-keyring package
   * Add ddebs.ubuntu.com repository for your release
   * sudo apt update must be successful

   * Install ubuntu-dbgsym-keyring package
   * Install and use `apt-key list` and check that there is no expiry on the 
dbgsym key

  I.e. bad output
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 2021-03-20]
F2ED C64D C5AE E1F6 B9C6  21F0 C8CA B659 5FDF F622
  uid   [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) 

  
  Good output has no [date] in the pub line.

  [Where problems could occur]

   * At the moment the signature was bumped by one year
   * Meaning this issue will occur again in 2022
   * Instead the key must be set to not expire & new round of SRUs issued

  [Other Info]

   * Original bug report

  The public key used by the debugging symbols repository
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu-
  dbgsym-keyring expired.

  $ apt policy ubuntu-dbgsym-keyring
  ubuntu-dbgsym-keyring:
    Installed: 2020.02.11.2
    Candidate: 2020.02.11.2
    Version table:
   *** 2020.02.11.2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status
  $ gpg --no-default-keyring --keyring 
/usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 2021-03-20]
    F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622
  uid   [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) 

  Error message on "apt update":

  E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ddebs.ubuntu.com bionic Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive 
Automatic Signing Key (2016) 
  E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive 
Automatic Signing Key (2016) 
  E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+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 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal

[Dimitri John Ledkov]

Used systemd packaging repo's ./debian/git-cherry-pick and gbp dch + gbp
tag to convert the cherry-pick request into a typical looking systemd
sru backport.

Submitted merge proposal to https://code.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/+git/systemd/+merge/429491

will ask for review and/or will upload it to proposed shortly.

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

Title:
  systemd: fix test-execute autotest failure with kernel 5.15 in focal

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress

Bug description:
  [Impact]

  test-execute autotest is failing in focal with kernel 5.15. This is
  because the following kernel commit changed the ABI for ioprio:

  e70344c05995 ("block: fix default IO priority handling")

  Previously setting IOPRIO_CLASS_NONE for a process would report
  IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
  IOPRIO_CLASS_BE instead.

  [Test case]

  Run systemd autopkgtest and check for the test-execute result.

  [Fix]

  Change test/test-execute/exec-ioschedulingclass-none.service to
  recognize both "none" and "best-effort" as valid returned strings from
  ionice.

  This change is already available in jammy and above.

  [Regression potential]

  We may see regressions in systemd autopkgtest, we won't introduce any
  potential regressions in systemd itself, because this is only
  affecting the specific unit test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+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 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/429490

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/429491

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

Title:
  systemd: fix test-execute autotest failure with kernel 5.15 in focal

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress

Bug description:
  [Impact]

  test-execute autotest is failing in focal with kernel 5.15. This is
  because the following kernel commit changed the ABI for ioprio:

  e70344c05995 ("block: fix default IO priority handling")

  Previously setting IOPRIO_CLASS_NONE for a process would report
  IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
  IOPRIO_CLASS_BE instead.

  [Test case]

  Run systemd autopkgtest and check for the test-execute result.

  [Fix]

  Change test/test-execute/exec-ioschedulingclass-none.service to
  recognize both "none" and "best-effort" as valid returned strings from
  ionice.

  This change is already available in jammy and above.

  [Regression potential]

  We may see regressions in systemd autopkgtest, we won't introduce any
  potential regressions in systemd itself, because this is only
  affecting the specific unit test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+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 1981622] Re: mtd device must be supplied (device name is empty)

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/429490

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

Title:
  mtd device must be supplied (device name is empty)

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

Bug description:
  [WORKAROUND]

  This will NOT fix a system that is not booting, because the "mtd
  device must be supplied (device name is empty)" message is not the
  cause of failed boots. This work around is only for those who are
  annoyed by the error message, but are otherwise not experiencing any
  issues.

  If you are not able to boot your system, but you see this error
  message, please open a separate bug with your journalctl and dmesg
  logs.

  # cp /{lib,etc}/systemd/system/systemd-pstore.service
  # sed -i 's/modprobe@mtdpstore.service //' 
/etc/systemd/system/systemd-pstore.service
  # systemctl daemon-reload

  [Impact]

  Due to mtdpstore not being properly configured as a pstore backend,
  when systemd-pstore.service tries to load the module, users get the
  following error in dmesg:

  [   18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
  [   18.462685] mtd device must be supplied (device name is empty)

  This is a distracting error for users trying to diagnose other system
  issues, especially if their system does not boot after a kernel crash
  and this is the only message displayed on the console.

  [Test Plan]

  * Force a kernel crash to populate /sys/fs/pstore, thus causing
  systemd-pstore.service to start on the subsequent boot:

  # echo 1 > /proc/sys/kernel/sysrq
  # echo 1 > /proc/sys/kernel/panic
  # echo c > /proc/sysrq-trigger

  * When the system reboots, observe the error in dmesg:

  # dmesg | grep mtd

  [Where problems could occur]

  If a system was relying on this pstore backend, and mtdpstore is built
  as a module, it is possible for systemd-pstore.service to trigger
  before mtdpstore is loaded, causing systemd-pstore to not copy the
  contents of /sys/fs/pstore. Note however that before the patched
  introduced as a result of bug 1978079, systemd-pstore.service would
  not attempt to load *any* kernel modules.

  [Original Description]

  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1978079] Re: EFI pstore not cleared on boot

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/429490

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

Title:
  EFI pstore not cleared on boot

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Won't Fix
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  Systemd has a systemd-pstore component that scans the pstore on boot
  and if non-empty, takes all previously created dumps, transfers them
  into its journal and removes the pstore elements. This is very
  important on UEFI systems, which only have a limited amount of space
  for variables.

  In Ubuntu, the kernel is configured with CONFIG_EFI_VARS_PSTORE=m
  which means the EFI pstore support gets loaded dynamically. In all of
  my boots, this dynamic module loading happened *after* systemd tried
  to check for pstore variables. So systemd-pstore never starts and
  never clears the UEFI variable store. I see this happening in AWS on
  Graviton instances, which eventually run out of space to store the
  dumps. On real hardware, this behavior may lead to unbootable systems.

  ```
  $ systemctl status systemd-pstore
  ○ systemd-pstore.service - Platform Persistent Storage Archival
   Loaded: loaded (/lib/systemd/system/systemd-pstore.service; enabled; 
vendor preset: enabled)
   Active: inactive (dead)
    Condition: start condition failed at Thu 2022-06-09 09:11:41 UTC; 29min ago
   └─ ConditionDirectoryNotEmpty=/sys/fs/pstore was not met
     Docs: man:systemd-pstore(8)

  Jun 09 09:11:41 ip-172-31-0-61 systemd[1]: Condition check resulted in
  Platform Persistent Storage Archival being skipped.

  $ ls -la /sys/fs/pstore
  total 0
  drwxr-x--- 2 root root0 Jun  9 09:11 .
  drwxr-xr-x 8 root root0 Jun  9 09:11 ..
  -r--r--r-- 1 root root 1803 Jun  9 09:07 dmesg-efi-165476562001001
  -r--r--r-- 1 root root 1777 Jun  9 09:07 dmesg-efi-165476562002001
  -r--r--r-- 1 root root 1773 Jun  9 09:07 dmesg-efi-165476562003001
  -r--r--r-- 1 root root 1815 Jun  9 09:07 dmesg-efi-165476562004001
  -r--r--r-- 1 root root 1826 Jun  9 09:07 dmesg-efi-165476562005001
  -r--r--r-- 1 root root 1754 Jun  9 09:07 dmesg-efi-165476562006001
  -r--r--r-- 1 root root 1821 Jun  9 09:07 dmesg-efi-165476562007001
  -r--r--r-- 1 root root 1767 Jun  9 09:07 dmesg-efi-165476562008001
  -r--r--r-- 1 root root 1729 Jun  9 09:07 dmesg-efi-165476562009001
  -r--r--r-- 1 root root 1819 Jun  9 09:07 dmesg-efi-165476562010001
  -r--r--r-- 1 root root 1767 Jun  9 09:07 dmesg-efi-165476562011001
  -r--r--r-- 1 root root 1775 Jun  9 09:07 dmesg-efi-165476562012001
  -r--r--r-- 1 root root 1802 Jun  9 09:07 dmesg-efi-165476562013001
  -r--r--r-- 1 root root 1812 Jun  9 09:07 dmesg-efi-165476562014001
  -r--r--r-- 1 root root 1764 Jun  9 09:07 dmesg-efi-165476562015001
  -r--r--r-- 1 root root 1795 Jun  9 09:11 dmesg-efi-165476589801001
  -r--r--r-- 1 root root 1785 Jun  9 09:11 dmesg-efi-165476589802001
  -r--r--r-- 1 root root 1683 Jun  9 09:11 dmesg-efi-165476589803001
  -r--r--r-- 1 root root 1785 Jun  9 09:11 dmesg-efi-165476589804001
  -r--r--r-- 1 root root 1771 Jun  9 09:11 dmesg-efi-165476589805001
  -r--r--r-- 1 root root 1797 Jun  9 09:11 dmesg-efi-165476589806001
  -r--r--r-- 1 root root 1805 Jun  9 09:11 dmesg-efi-165476589807001
  -r--r--r-- 1 root root 1781 Jun  9 09:11 dmesg-efi-165476589808001
  -r--r--r-- 1 root root 1806 Jun  9 09:11 dmesg-efi-165476589809001
  -r--r--r-- 1 root root 1821 Jun  9 09:11 dmesg-efi-165476589810001
  -r--r--r-- 1 root root 1763 Jun  9 09:11 dmesg-efi-165476589811001
  -r--r--r-- 1 root root 1783 Jun  9 09:11 dmesg-efi-165476589812001
  -r--r--r-- 1 root root 1788 Jun  9 09:11 dmesg-efi-165476589813001
  -r--r--r-- 1 root root 1788 Jun  9 09:11 dmesg-efi-165476589814001
  -r--r--r-- 1 root root 1786 Jun  9 09:11 dmesg-efi-165476589815001
  ```

  This problem affects (at least) Ubuntu 20.04 and 22.04. A quick fix
  would be to configure CONFIG_EFI_VARS_PSTORE=y so that it's always
  available. A long term fix would make systemd rescan the directory
  after all module probing settled.

  [Test Plan]

  In order to be able to reproduce this issue, the system must have EFI-
  backed pstore.

  To check which kind of backend that pstore, use `cat
  /sys/module/pstore/parameters/backend`

  If it says `efi`, the steps below are applicable. Otherwise, find an
  environment that has EFI backed pstore.

  # Enable the pstore service. This service is supposed to move the data in 
/sys/fs/pstore
  # to the `/var/lib/systemd/pstore` path on boot.
  systemctl enable systemd-pstore.service # (or can be vendor enabled)

  # Crash 

[Touch-packages] [Bug 1979951] Re: 127.0.0.1/::1 removed from loopback interface if you configure extra IPs on lo (r104 regression/behaviour change)

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/429490

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

Title:
  127.0.0.1/::1 removed from loopback interface if you configure extra
  IPs on lo (r104 regression/behaviour change)

Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Committed
Status in netplan.io source package in Jammy:
  New
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Users who wish to configure additional addresses on lo may
  inadvertently remove the 127.0.0.1/8 address from the interface. And,
  because this only happens on the second invocation of `netplan apply`,
  it can create confusing breakages for users. Although this is not a
  recommended configuration, it was previously supported and the current
  behavior is a regression.

  [Test Plan]

  * Configure additional addresses on the lo interface. I am testing in
  a LXD container, so I added the following to /etc/netplan/10-lxc.yaml
  under `ethernets:`

  lo:
addresses: ["10.10.10.17/24","10.10.10.19/24"]

  * Apply the config, and then inspect the lo interface's addresses:

   $ netplan apply
   $ ip addr show dev lo

  * Observe that the 127.0.0.1/8 address is still present. Now, run the
  same commands again:

   $ netplan apply
   $ ip addr show dev lo

  * On an affected system, observe that the 127.0.0.1/8 address is now
  gone. On a patched system, the address should still be present.

  [Where problems could occur]

  The patch removes cases where systemd-networkd will drop foreign
  addresses from a managed link. If problems were to occur, it would be
  related to the addresses configured on a managed link.

  [Original Description]

  If you configure the loopback interface using netplan without listing
  the standard loopback addresses (127.0.0.1 / ::1) that are auto-
  configured on boot then they are removed by netplan in r104+ but were
  not in r103.

  Confusingly this only happens the second time "netplan apply" is
  invoked and not the first time.

  There is some argument this is not a valid configuration, however
  - It worked on r103 and broke in the r104 SRU for 20.04 and breaks on upgrade
  - Since it only occurs on the second "netplan apply" it is likely people will 
accidentally create a configuration that on first verification works but breaks 
later
  - Adding addresses to a loopback or dummy interface is a common need
  - There is no dummy interface support in Netplan
  - Removing the loopback IP doesn't immediately cause obvious breakage in an 
SSH session but causes all sorts of hard to diagnose issues with applications

  Thus I consider this a high priority regression because of the
  multiple ways this can break a system at an unexpected/unrelated time
  to when the original change was made.

  As a workaround you can add 127.0.0.1/::1 to the file and this seems
  to generally work and product almost the same configuration with the
  exception that "brd 127.255.255.255" is added to the "ip addr" output
  compared to the auto-created configuration. All of the different
  routing tables seem otherwise the tame.

  = Test Case =
  (1) Add IP configuration for lo to /etc/netplan/lo.yaml

  lo:
    match:
  name: lo
    addresses:
    - 10.10.10.17/24
    - 10.10.10.19/24

  (2) Run "netplan apply" and observe the "ip addr show dev lo" output. 
Expected: 127.0.0.1/::1 are still there.
  (3) Run "netplan apply" a second time and observe the "ip addr show dev lo" 
output. Expected: 127.0.0.1/::1 are now removed.
  (4) Repeat the same test under netplan r103. Expected: 127.0.0.1/::1 are 
still there in both cases.

  = Observations =

  I found this change of behaviour happens only in r104. It is suspected
  but not clear that this is due to the configuraiton diffing behaviour
  introduced in r104. It's not clear to me why it doesn't happen on the
  first "netplan apply".

  I also found a recent upstream systemd commit to prevent networkd removing 
127.0.0.1/::1 which solves this issue on r104 as well. It's possible this is a 
better fix to backport to solve this:
  
https://github.com/systemd/systemd/commit/b69bfa43052586cd6894c32d7d3d447195539ec5

  Reverting to r103 *or* running a newer systemd with that patch
  resolves the issue on 20.04 and 22.04 in my testing.

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


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

[Touch-packages] [Bug 1982462] Re: Some modprobe loading services requested by the pstore service fail

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/429490

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

Title:
  Some modprobe loading services requested by the pstore service fail

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

Bug description:
  [Impact]

  It has been detected that some modprobe services fail on UC22 after
  the jammy upgrade  249.11-0ubuntu3.4:

  $ systemctl --system --no-ask-password --no-pager list-units --state=failed
  Failed units:
UNIT LOAD   ACTIVE SUBDESCRIPTION
  ● modprobe@chromeos_pstore.service loaded failed failed Load Kernel Module 
chromeos_pstore
  ● modprobe@efi_pstore.service  loaded failed failed Load Kernel Module 
efi_pstore
  ● modprobe@mtdpstore.service   loaded failed failed Load Kernel Module 
mtdpstore
  ● modprobe@pstore_blk.service  loaded failed failed Load Kernel Module 
pstore_blk
  ● modprobe@pstore_zone.service loaded failed failed Load Kernel Module 
pstore_zone
  ● modprobe@ramoops.service loaded failed failed Load Kernel Module 
ramoops

  This happens because of some changes to systemd-pstore.service that
  now has:

  After=modprobe@efi_pstore.service modprobe@mtdpstore.service 
modprobe@chromeos_pstore.service modprobe@ramoops.service 
modprobe@pstore_zone.service modprobe@pstore_blk.service
  Wants=modprobe@efi_pstore.service modprobe@mtdpstore.service 
modprobe@chromeos_pstore.service modprobe@ramoops.service 
modprobe@pstore_zone.service modprobe@pstore_blk.service

  This causes too many tries of the modprobe services, that fail in the
  end with

  Jul 20 09:02:39 ubuntu systemd[1]: modprobe@chromeos_pstore.service:
  Start request repeated too quickly.

  Although we have seen this only on UC22, it potentially can affect
  classic systems as well, as systemd-pstore.service is re-tried there a
  few times too. See https://github.com/snapcore/core-base/issues/72 for
  more details.

  A fix for this is available upstream:
  
https://github.com/systemd/systemd/commit/9625350e5381a68c1179ae4581e7586c206663e1

  [Test Plan]

  Start the device and check that there is no modprobe-pstore related
  failed service. This is racy, so a few tries will be needed to make
  sure things are fine.

  [Where problems could occur]

  The modprobe services are usually dependencies from other services, so
  it should be fine if the retry behavior is controlled by those other
  services. Risk should be small. If something goes wrong we might see a
  lot of restarts for these services.

  [Other Info]

  Testing should happen on UC22 too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982462/+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 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal

[Kleber Sacilotto de Souza]

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

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

Title:
  systemd: fix test-execute autotest failure with kernel 5.15 in focal

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress

Bug description:
  [Impact]

  test-execute autotest is failing in focal with kernel 5.15. This is
  because the following kernel commit changed the ABI for ioprio:

  e70344c05995 ("block: fix default IO priority handling")

  Previously setting IOPRIO_CLASS_NONE for a process would report
  IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
  IOPRIO_CLASS_BE instead.

  [Test case]

  Run systemd autopkgtest and check for the test-execute result.

  [Fix]

  Change test/test-execute/exec-ioschedulingclass-none.service to
  recognize both "none" and "best-effort" as valid returned strings from
  ionice.

  This change is already available in jammy and above.

  [Regression potential]

  We may see regressions in systemd autopkgtest, we won't introduce any
  potential regressions in systemd itself, because this is only
  affecting the specific unit test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+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 1988777] Re: libgail-3-0 dependencies cause a complete downgrade/uninstall of various packages

[Sebastien Bacher]

-updates is recommended and enabled by default, those are stable serie
bugfixes, I'm unsure why it got disabled on your installation. Closing
the bug since that was not a problem in the package

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  libgail-3-0 dependencies cause a complete downgrade/uninstall of
  various packages

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  Hi,

  i have a fresh 22.04-LTS install on my new Huawei laptop, i tried and
  reviewed some mail clients and came to the conclusion to choose
  "evolution" as my new client, but my problem is i can't install
  "evolution" because some of his dependencies have to strong
  constrains, one of them is "libgail-3-0" which has "libgtk-3-0 (=
  3.24.33-1ubuntu1)" as dependency, which causes a downgrade/uninstall
  of some required packages, look at this console output:

  -- %< ---
  root@ebony:~# apt-get install evolution
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgail-3-0 : Depends: libgtk-3-0 (= 3.24.33-1ubuntu1) but 3.24.33-1ubuntu2 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@ebony:~# apt-get install evolution libgtk-3-0=3.24.33-1ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    apg gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-clutter-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdata-0.0
    gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 
gir1.2-graphene-1.0 gir1.2-gsound-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0 
gir1.2-json-1.0 gir1.2-nautilus-3.0 gir1.2-nm-1.0
    gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-unity-7.0 gir1.2-upowerglib-1.0 
gkbd-capplet gnome-bluetooth-3-common gnome-control-center-faces 
gnome-online-accounts gstreamer1.0-pipewire
    libcolord-gtk1 libfreerdp-server2-2 libgnome-bluetooth-3.0-13 
libgnomekbd-common libgnomekbd8 libgsound0 libgupnp-av-1.0-3 
libgupnp-dlna-2.0-4 libmediaart-2.0-0 librygel-core-2.6-2
    librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 
libsoup-3.0-0 libsoup-3.0-common libtext-engine-0.1-0 libvncserver1 
libxklavier16 mobile-broadband-provider-info
    network-manager-gnome policykit-1-gnome python3-certifi python3-chardet 
python3-debconf python3-debian python3-idna python3-macaroonbakery python3-nacl 
python3-nautilus python3-protobuf
    python3-pymacaroons python3-requests python3-rfc3339 python3-tz 
python3-urllib3 rygel sshfs switcheroo-control update-notifier-common xwayland
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  Suggested packages:
    db5.3-util doc-base evolution-ews evolution-plugins-experimental
  Recommended packages:
    libgtk-3-bin
  The following packages will be REMOVED:
    chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-control-center 
gnome-remote-desktop gnome-shell gnome-shell-extension-appindicator 
gnome-shell-extension-desktop-icons-ng
    gnome-shell-extension-gsconnect gnome-shell-extension-gsconnect-browsers 
gnome-shell-extension-manager gnome-shell-extension-ubuntu-dock libgtk-3-bin 
libmutter-10-0 ubuntu-desktop
    ubuntu-desktop-minimal ubuntu-release-upgrader-gtk ubuntu-session 
update-manager update-notifier
  The following NEW packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  The following packages will be DOWNGRADED:
    libgtk-3-0
  0 upgraded, 18 newly installed, 1 downgraded, 20 to remove and 0 not upgraded.
  Need to get 8.602 kB of archives.
  After this operation, 16,0 MB of additional disk 

[Touch-packages] [Bug 1988777] Re: libgail-3-0 dependencies cause a complete downgrade/uninstall of various packages

[Enrico]

BTW it worked now, i'm able to install evolution without any hasle.

Tyvm
Sebastien

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

Title:
  libgail-3-0 dependencies cause a complete downgrade/uninstall of
  various packages

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have a fresh 22.04-LTS install on my new Huawei laptop, i tried and
  reviewed some mail clients and came to the conclusion to choose
  "evolution" as my new client, but my problem is i can't install
  "evolution" because some of his dependencies have to strong
  constrains, one of them is "libgail-3-0" which has "libgtk-3-0 (=
  3.24.33-1ubuntu1)" as dependency, which causes a downgrade/uninstall
  of some required packages, look at this console output:

  -- %< ---
  root@ebony:~# apt-get install evolution
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgail-3-0 : Depends: libgtk-3-0 (= 3.24.33-1ubuntu1) but 3.24.33-1ubuntu2 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@ebony:~# apt-get install evolution libgtk-3-0=3.24.33-1ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    apg gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-clutter-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdata-0.0
    gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 
gir1.2-graphene-1.0 gir1.2-gsound-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0 
gir1.2-json-1.0 gir1.2-nautilus-3.0 gir1.2-nm-1.0
    gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-unity-7.0 gir1.2-upowerglib-1.0 
gkbd-capplet gnome-bluetooth-3-common gnome-control-center-faces 
gnome-online-accounts gstreamer1.0-pipewire
    libcolord-gtk1 libfreerdp-server2-2 libgnome-bluetooth-3.0-13 
libgnomekbd-common libgnomekbd8 libgsound0 libgupnp-av-1.0-3 
libgupnp-dlna-2.0-4 libmediaart-2.0-0 librygel-core-2.6-2
    librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 
libsoup-3.0-0 libsoup-3.0-common libtext-engine-0.1-0 libvncserver1 
libxklavier16 mobile-broadband-provider-info
    network-manager-gnome policykit-1-gnome python3-certifi python3-chardet 
python3-debconf python3-debian python3-idna python3-macaroonbakery python3-nacl 
python3-nautilus python3-protobuf
    python3-pymacaroons python3-requests python3-rfc3339 python3-tz 
python3-urllib3 rygel sshfs switcheroo-control update-notifier-common xwayland
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  Suggested packages:
    db5.3-util doc-base evolution-ews evolution-plugins-experimental
  Recommended packages:
    libgtk-3-bin
  The following packages will be REMOVED:
    chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-control-center 
gnome-remote-desktop gnome-shell gnome-shell-extension-appindicator 
gnome-shell-extension-desktop-icons-ng
    gnome-shell-extension-gsconnect gnome-shell-extension-gsconnect-browsers 
gnome-shell-extension-manager gnome-shell-extension-ubuntu-dock libgtk-3-bin 
libmutter-10-0 ubuntu-desktop
    ubuntu-desktop-minimal ubuntu-release-upgrader-gtk ubuntu-session 
update-manager update-notifier
  The following NEW packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  The following packages will be DOWNGRADED:
    libgtk-3-0
  0 upgraded, 18 newly installed, 1 downgraded, 20 to remove and 0 not upgraded.
  Need to get 8.602 kB of archives.
  After this operation, 16,0 MB of additional disk space will be used.
  Do you want to continue? [Y/n] N
  Abort.

  -- %< 

  as you can see, this will downgrade and therefore destroy my entire
  setup.

  I'm not sure if i should send a email to the package 

[Touch-packages] [Bug 1988777] Re: libgail-3-0 dependencies cause a complete downgrade/uninstall of various packages

[Enrico]

so should ubuntu-updates then be used or not, i mean i want a system
with less/no bugs if possible!?

and i choose the LTS version for that specific purpose, because i use my
laptop for work.

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

Title:
  libgail-3-0 dependencies cause a complete downgrade/uninstall of
  various packages

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have a fresh 22.04-LTS install on my new Huawei laptop, i tried and
  reviewed some mail clients and came to the conclusion to choose
  "evolution" as my new client, but my problem is i can't install
  "evolution" because some of his dependencies have to strong
  constrains, one of them is "libgail-3-0" which has "libgtk-3-0 (=
  3.24.33-1ubuntu1)" as dependency, which causes a downgrade/uninstall
  of some required packages, look at this console output:

  -- %< ---
  root@ebony:~# apt-get install evolution
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgail-3-0 : Depends: libgtk-3-0 (= 3.24.33-1ubuntu1) but 3.24.33-1ubuntu2 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@ebony:~# apt-get install evolution libgtk-3-0=3.24.33-1ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    apg gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-clutter-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdata-0.0
    gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 
gir1.2-graphene-1.0 gir1.2-gsound-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0 
gir1.2-json-1.0 gir1.2-nautilus-3.0 gir1.2-nm-1.0
    gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-unity-7.0 gir1.2-upowerglib-1.0 
gkbd-capplet gnome-bluetooth-3-common gnome-control-center-faces 
gnome-online-accounts gstreamer1.0-pipewire
    libcolord-gtk1 libfreerdp-server2-2 libgnome-bluetooth-3.0-13 
libgnomekbd-common libgnomekbd8 libgsound0 libgupnp-av-1.0-3 
libgupnp-dlna-2.0-4 libmediaart-2.0-0 librygel-core-2.6-2
    librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 
libsoup-3.0-0 libsoup-3.0-common libtext-engine-0.1-0 libvncserver1 
libxklavier16 mobile-broadband-provider-info
    network-manager-gnome policykit-1-gnome python3-certifi python3-chardet 
python3-debconf python3-debian python3-idna python3-macaroonbakery python3-nacl 
python3-nautilus python3-protobuf
    python3-pymacaroons python3-requests python3-rfc3339 python3-tz 
python3-urllib3 rygel sshfs switcheroo-control update-notifier-common xwayland
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  Suggested packages:
    db5.3-util doc-base evolution-ews evolution-plugins-experimental
  Recommended packages:
    libgtk-3-bin
  The following packages will be REMOVED:
    chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-control-center 
gnome-remote-desktop gnome-shell gnome-shell-extension-appindicator 
gnome-shell-extension-desktop-icons-ng
    gnome-shell-extension-gsconnect gnome-shell-extension-gsconnect-browsers 
gnome-shell-extension-manager gnome-shell-extension-ubuntu-dock libgtk-3-bin 
libmutter-10-0 ubuntu-desktop
    ubuntu-desktop-minimal ubuntu-release-upgrader-gtk ubuntu-session 
update-manager update-notifier
  The following NEW packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  The following packages will be DOWNGRADED:
    libgtk-3-0
  0 upgraded, 18 newly installed, 1 downgraded, 20 to remove and 0 not upgraded.
  Need to get 8.602 kB of archives.
  After this operation, 16,0 MB of additional disk space will be used.
  Do you want to continue? [Y/n] N
  Abort.

  -- %< 

  as you can see, this will 

[Touch-packages] [Bug 1988777] Re: libgail-3-0 dependencies cause a complete downgrade/uninstall of various packages

[Enrico]

** Attachment added: "evolution dependency graph"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1988777/+attachment/5613997/+files/evolution-dependency-graph.png

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

Title:
  libgail-3-0 dependencies cause a complete downgrade/uninstall of
  various packages

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have a fresh 22.04-LTS install on my new Huawei laptop, i tried and
  reviewed some mail clients and came to the conclusion to choose
  "evolution" as my new client, but my problem is i can't install
  "evolution" because some of his dependencies have to strong
  constrains, one of them is "libgail-3-0" which has "libgtk-3-0 (=
  3.24.33-1ubuntu1)" as dependency, which causes a downgrade/uninstall
  of some required packages, look at this console output:

  -- %< ---
  root@ebony:~# apt-get install evolution
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgail-3-0 : Depends: libgtk-3-0 (= 3.24.33-1ubuntu1) but 3.24.33-1ubuntu2 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@ebony:~# apt-get install evolution libgtk-3-0=3.24.33-1ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    apg gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-clutter-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdata-0.0
    gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 
gir1.2-graphene-1.0 gir1.2-gsound-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0 
gir1.2-json-1.0 gir1.2-nautilus-3.0 gir1.2-nm-1.0
    gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-unity-7.0 gir1.2-upowerglib-1.0 
gkbd-capplet gnome-bluetooth-3-common gnome-control-center-faces 
gnome-online-accounts gstreamer1.0-pipewire
    libcolord-gtk1 libfreerdp-server2-2 libgnome-bluetooth-3.0-13 
libgnomekbd-common libgnomekbd8 libgsound0 libgupnp-av-1.0-3 
libgupnp-dlna-2.0-4 libmediaart-2.0-0 librygel-core-2.6-2
    librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 
libsoup-3.0-0 libsoup-3.0-common libtext-engine-0.1-0 libvncserver1 
libxklavier16 mobile-broadband-provider-info
    network-manager-gnome policykit-1-gnome python3-certifi python3-chardet 
python3-debconf python3-debian python3-idna python3-macaroonbakery python3-nacl 
python3-nautilus python3-protobuf
    python3-pymacaroons python3-requests python3-rfc3339 python3-tz 
python3-urllib3 rygel sshfs switcheroo-control update-notifier-common xwayland
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  Suggested packages:
    db5.3-util doc-base evolution-ews evolution-plugins-experimental
  Recommended packages:
    libgtk-3-bin
  The following packages will be REMOVED:
    chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-control-center 
gnome-remote-desktop gnome-shell gnome-shell-extension-appindicator 
gnome-shell-extension-desktop-icons-ng
    gnome-shell-extension-gsconnect gnome-shell-extension-gsconnect-browsers 
gnome-shell-extension-manager gnome-shell-extension-ubuntu-dock libgtk-3-bin 
libmutter-10-0 ubuntu-desktop
    ubuntu-desktop-minimal ubuntu-release-upgrader-gtk ubuntu-session 
update-manager update-notifier
  The following NEW packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  The following packages will be DOWNGRADED:
    libgtk-3-0
  0 upgraded, 18 newly installed, 1 downgraded, 20 to remove and 0 not upgraded.
  Need to get 8.602 kB of archives.
  After this operation, 16,0 MB of additional disk space will be used.
  Do you want to continue? [Y/n] N
  Abort.

  -- %< 

  as you can see, this will downgrade and therefore 

[Touch-packages] [Bug 1988777] Re: libgail-3-0 dependencies cause a complete downgrade/uninstall of various packages

[Enrico]

Sorry if i caused to much trouble.

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

Title:
  libgail-3-0 dependencies cause a complete downgrade/uninstall of
  various packages

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have a fresh 22.04-LTS install on my new Huawei laptop, i tried and
  reviewed some mail clients and came to the conclusion to choose
  "evolution" as my new client, but my problem is i can't install
  "evolution" because some of his dependencies have to strong
  constrains, one of them is "libgail-3-0" which has "libgtk-3-0 (=
  3.24.33-1ubuntu1)" as dependency, which causes a downgrade/uninstall
  of some required packages, look at this console output:

  -- %< ---
  root@ebony:~# apt-get install evolution
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgail-3-0 : Depends: libgtk-3-0 (= 3.24.33-1ubuntu1) but 3.24.33-1ubuntu2 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@ebony:~# apt-get install evolution libgtk-3-0=3.24.33-1ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    apg gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-clutter-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdata-0.0
    gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 
gir1.2-graphene-1.0 gir1.2-gsound-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0 
gir1.2-json-1.0 gir1.2-nautilus-3.0 gir1.2-nm-1.0
    gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-unity-7.0 gir1.2-upowerglib-1.0 
gkbd-capplet gnome-bluetooth-3-common gnome-control-center-faces 
gnome-online-accounts gstreamer1.0-pipewire
    libcolord-gtk1 libfreerdp-server2-2 libgnome-bluetooth-3.0-13 
libgnomekbd-common libgnomekbd8 libgsound0 libgupnp-av-1.0-3 
libgupnp-dlna-2.0-4 libmediaart-2.0-0 librygel-core-2.6-2
    librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 
libsoup-3.0-0 libsoup-3.0-common libtext-engine-0.1-0 libvncserver1 
libxklavier16 mobile-broadband-provider-info
    network-manager-gnome policykit-1-gnome python3-certifi python3-chardet 
python3-debconf python3-debian python3-idna python3-macaroonbakery python3-nacl 
python3-nautilus python3-protobuf
    python3-pymacaroons python3-requests python3-rfc3339 python3-tz 
python3-urllib3 rygel sshfs switcheroo-control update-notifier-common xwayland
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  Suggested packages:
    db5.3-util doc-base evolution-ews evolution-plugins-experimental
  Recommended packages:
    libgtk-3-bin
  The following packages will be REMOVED:
    chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-control-center 
gnome-remote-desktop gnome-shell gnome-shell-extension-appindicator 
gnome-shell-extension-desktop-icons-ng
    gnome-shell-extension-gsconnect gnome-shell-extension-gsconnect-browsers 
gnome-shell-extension-manager gnome-shell-extension-ubuntu-dock libgtk-3-bin 
libmutter-10-0 ubuntu-desktop
    ubuntu-desktop-minimal ubuntu-release-upgrader-gtk ubuntu-session 
update-manager update-notifier
  The following NEW packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  The following packages will be DOWNGRADED:
    libgtk-3-0
  0 upgraded, 18 newly installed, 1 downgraded, 20 to remove and 0 not upgraded.
  Need to get 8.602 kB of archives.
  After this operation, 16,0 MB of additional disk space will be used.
  Do you want to continue? [Y/n] N
  Abort.

  -- %< 

  as you can see, this will downgrade and therefore destroy my entire
  setup.

  I'm not sure if i should send a email to the package maintainer
  directly or better file a bug here (i 

[Touch-packages] [Bug 1988825] Re: [ASUS ROG Flow X13] Cannot turn Bluetooth on in Ubuntu 22.04.01

[Daniel van Vugt]

Being machine-specific means this is almost certainly a kernel bug.

** Summary changed:

- Cannot turn Bluetooth on in Ubuntu 22.04.01
+ [ASUS ROG Flow X13] Cannot turn Bluetooth on in Ubuntu 22.04.01

** Package changed: bluez (Ubuntu) => linux (Ubuntu)

** Summary changed:

- [ASUS ROG Flow X13] Cannot turn Bluetooth on in Ubuntu 22.04.01
+ [mt7921e] Cannot turn Bluetooth on in Ubuntu 22.04.01

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

Title:
  [mt7921e] Cannot turn Bluetooth on in Ubuntu 22.04.01

Status in linux package in Ubuntu:
  New

Bug description:
  The steps:

  * Going to settings -> Bluetooth
  * Turn Bluetooth on. Seems to stay on, but can't connect anything to it
  * Go to another place in Settings, go back to Bluetooth
  * Result: Bluetooth is turned off

  Thank you!
  Alex

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 11:52:13 2022
  InstallationDate: Installed on 2022-06-16 (81 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  InterestingModules: bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. ROG Flow X13 GV301RE_GV301RE
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: GV301RE.313
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GV301RE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.8
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301RE.313:bd03/24/2022:br5.24:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301RE_GV301RE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGV301RE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: ROG Flow X13
  dmi.product.name: ROG Flow X13 GV301RE_GV301RE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

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

Re: [Touch-packages] [Bug 1979639] Re: Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

[Simon Chopin]

Hi!

I apologize, I thought I'd sent here the gameplan for the issue, but it
must have only been discussed out of band within the team. As noted by
Robie, the consensus is not to change the default configuration, but
instead patching node.js on Jammy (patches welcome for that one though).

I've already reverted the change in kinetic in my last upload
(3.0.5-2ubuntu1)

Thanks for the follow-up, Robie!

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

Title:
  Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

Status in nodejs package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Fix Released
Status in nodejs source package in Jammy:
  Confirmed
Status in openssl source package in Jammy:
  Won't Fix
Status in nodejs source package in Kinetic:
  Confirmed
Status in openssl source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  While the default configuration works fine for every package that uses the 
system libssl3, libssl1.1.1 (which implicitly loads the configuration on 
OPENSSL_crypto_init()) fails to parse it.

  Our nodejs package vendors openssl 1.1.1, which means it will trigger this 
bug. In addition, upstream NodeJS explicitly points their statically-linked 
OpenSSL to this file as well, and ships 1.1.1 in their current LTS (branch 
16.x).
  Finally, we can also expect breakage for third-party packages that still 
depends on libssl1.1.

  If the provider section isn't present in the configuration, libssl3
  will load the default provider, which means that commenting out the
  section won't impact the behavior of standard libssl3 users.

  [Test Plan]

  On a system with a pristine openssl configuration:

  $ sudo apt install nodejs
  $ nodejs -  const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  Uncaught:
  Error: error:25066067:DSO support routines:dlfcn_load:could not load the 
shared library
  at Sign.sign (node:internal/crypto/sig:131:29) {
    opensslErrorStack: [
  'error:0E076071:configuration file routines:module_run:unknown module 
name',
  'error:0E07506E:configuration file routines:module_load_dso:error loading 
dso',
  'error:25070067:DSO support routines:DSO_load:could not load the shared 
library'
    ],
    library: 'DSO support routines',
    function: 'dlfcn_load',
    reason: 'could not load the shared library',
    code: 'ERR_OSSL_DSO_COULD_NOT_LOAD_THE_SHARED_LIBRARY'
  }

  Removing the relevant provider section lines (the Debian patch doesn't
  apply cleanly, hence the use of sed) fixes it:

  ~ $ sed -i '/_sect\b/s/^/# /' /etc/ssl/openssl.cnf
  ~ $ node
  Welcome to Node.js v16.15.0.
  Type ".help" for more information.
  > const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  

  I realize there is no libssl1.1 on jammy, but a statically linked
  OpenSSL is not uncommon (Node.js being a very prominent example).

  Would it be possible to get this Debian sid change ported to jammy?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1979639/+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 1988777] Re: libgail-3-0 dependencies cause a complete downgrade/uninstall of various packages

[Sebastien Bacher]

the easiest option is to the enable 'updates' (it's in the 3rd tab of
software-properties by picking 'security and recommended' updates in the
first selector. You had it installed at some point and your gtk is
coming from there which creates the issue. As said before, if it's
uninstalling things you might need to add more binaries to the apt cmd,
like  gir1.2-gtk-3.0=3.24.33-1ubuntu1

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

Title:
  libgail-3-0 dependencies cause a complete downgrade/uninstall of
  various packages

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have a fresh 22.04-LTS install on my new Huawei laptop, i tried and
  reviewed some mail clients and came to the conclusion to choose
  "evolution" as my new client, but my problem is i can't install
  "evolution" because some of his dependencies have to strong
  constrains, one of them is "libgail-3-0" which has "libgtk-3-0 (=
  3.24.33-1ubuntu1)" as dependency, which causes a downgrade/uninstall
  of some required packages, look at this console output:

  -- %< ---
  root@ebony:~# apt-get install evolution
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgail-3-0 : Depends: libgtk-3-0 (= 3.24.33-1ubuntu1) but 3.24.33-1ubuntu2 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@ebony:~# apt-get install evolution libgtk-3-0=3.24.33-1ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    apg gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-clutter-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdata-0.0
    gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 
gir1.2-graphene-1.0 gir1.2-gsound-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0 
gir1.2-json-1.0 gir1.2-nautilus-3.0 gir1.2-nm-1.0
    gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-unity-7.0 gir1.2-upowerglib-1.0 
gkbd-capplet gnome-bluetooth-3-common gnome-control-center-faces 
gnome-online-accounts gstreamer1.0-pipewire
    libcolord-gtk1 libfreerdp-server2-2 libgnome-bluetooth-3.0-13 
libgnomekbd-common libgnomekbd8 libgsound0 libgupnp-av-1.0-3 
libgupnp-dlna-2.0-4 libmediaart-2.0-0 librygel-core-2.6-2
    librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 
libsoup-3.0-0 libsoup-3.0-common libtext-engine-0.1-0 libvncserver1 
libxklavier16 mobile-broadband-provider-info
    network-manager-gnome policykit-1-gnome python3-certifi python3-chardet 
python3-debconf python3-debian python3-idna python3-macaroonbakery python3-nacl 
python3-nautilus python3-protobuf
    python3-pymacaroons python3-requests python3-rfc3339 python3-tz 
python3-urllib3 rygel sshfs switcheroo-control update-notifier-common xwayland
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  Suggested packages:
    db5.3-util doc-base evolution-ews evolution-plugins-experimental
  Recommended packages:
    libgtk-3-bin
  The following packages will be REMOVED:
    chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-control-center 
gnome-remote-desktop gnome-shell gnome-shell-extension-appindicator 
gnome-shell-extension-desktop-icons-ng
    gnome-shell-extension-gsconnect gnome-shell-extension-gsconnect-browsers 
gnome-shell-extension-manager gnome-shell-extension-ubuntu-dock libgtk-3-bin 
libmutter-10-0 ubuntu-desktop
    ubuntu-desktop-minimal ubuntu-release-upgrader-gtk ubuntu-session 
update-manager update-notifier
  The following NEW packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  The following packages will be DOWNGRADED:
    libgtk-3-0
  0 upgraded, 18 newly installed, 1 downgraded, 20 to remove and 0 not upgraded.
  Need to get 8.602 kB of 

[Touch-packages] [Bug 1988825] [NEW] Cannot turn Bluetooth on in Ubuntu 22.04.01

[Alexandru Bolboaca]

Public bug reported:

The steps:

* Going to settings -> Bluetooth
* Turn Bluetooth on. Seems to stay on, but can't connect anything to it
* Go to another place in Settings, go back to Bluetooth
* Result: Bluetooth is turned off

Thank you!
Alex

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  6 11:52:13 2022
InstallationDate: Installed on 2022-06-16 (81 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
InterestingModules: bnep btusb bluetooth
MachineType: ASUSTeK COMPUTER INC. ROG Flow X13 GV301RE_GV301RE
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/24/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: GV301RE.313
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GV301RE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.8
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301RE.313:bd03/24/2022:br5.24:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301RE_GV301RE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGV301RE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
dmi.product.family: ROG Flow X13
dmi.product.name: ROG Flow X13 GV301RE_GV301RE
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

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


** Tags: amd64 apport-bug jammy

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

Title:
  Cannot turn Bluetooth on in Ubuntu 22.04.01

Status in bluez package in Ubuntu:
  New

Bug description:
  The steps:

  * Going to settings -> Bluetooth
  * Turn Bluetooth on. Seems to stay on, but can't connect anything to it
  * Go to another place in Settings, go back to Bluetooth
  * Result: Bluetooth is turned off

  Thank you!
  Alex

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  6 11:52:13 2022
  InstallationDate: Installed on 2022-06-16 (81 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  InterestingModules: bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. ROG Flow X13 GV301RE_GV301RE
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: GV301RE.313
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GV301RE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.8
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301RE.313:bd03/24/2022:br5.24:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301RE_GV301RE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGV301RE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: ROG Flow X13
  dmi.product.name: ROG Flow X13 GV301RE_GV301RE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1988825/+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 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)

[Christian Ehrhardt ]

FYI: I've today had two systems exposing that issue.
The cleanup in comment #32 helped, but I wonder what caused it initially.
Sadly I can't recreate it anymore with a new system/container - might have been 
related to the keying update to 2021.03.26 a few days ago.

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

Title:
  EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic
  Signing Key (2016) 

Status in ubuntu-keyring package in Ubuntu:
  Fix Released
Status in ubuntu-keyring source package in Bionic:
  Fix Released
Status in ubuntu-keyring source package in Focal:
  Fix Released
Status in ubuntu-keyring source package in Groovy:
  Fix Released
Status in ubuntu-keyring source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Cannot update apt metadata from ddebs.ubuntu.com whilst using
  ubuntu-dbgsym-keyring package

  [Test Plan]

   * Install ubuntu-dbgsym-keyring package
   * Add ddebs.ubuntu.com repository for your release
   * sudo apt update must be successful

   * Install ubuntu-dbgsym-keyring package
   * Install and use `apt-key list` and check that there is no expiry on the 
dbgsym key

  I.e. bad output
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 2021-03-20]
F2ED C64D C5AE E1F6 B9C6  21F0 C8CA B659 5FDF F622
  uid   [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) 

  
  Good output has no [date] in the pub line.

  [Where problems could occur]

   * At the moment the signature was bumped by one year
   * Meaning this issue will occur again in 2022
   * Instead the key must be set to not expire & new round of SRUs issued

  [Other Info]

   * Original bug report

  The public key used by the debugging symbols repository
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu-
  dbgsym-keyring expired.

  $ apt policy ubuntu-dbgsym-keyring
  ubuntu-dbgsym-keyring:
    Installed: 2020.02.11.2
    Candidate: 2020.02.11.2
    Version table:
   *** 2020.02.11.2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status
  $ gpg --no-default-keyring --keyring 
/usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 2021-03-20]
    F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622
  uid   [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) 

  Error message on "apt update":

  E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ddebs.ubuntu.com bionic Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive 
Automatic Signing Key (2016) 
  E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive 
Automatic Signing Key (2016) 
  E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+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 1988777] Re: libgail-3-0 dependencies cause a complete downgrade/uninstall of various packages

[Enrico]

I also looked at my apt cache and my installed versions...

-- %< 
root@ebony:/var/cache/apt/archives# ll | grep gtk
-rw-r--r-- 1 root root216418 Jul 13 02:30 
gir1.2-gtk-4.0_4.6.6+ds-0ubuntu1_amd64.deb
-rw-r--r-- 1 root root 31346 Aug 15 14:23 
gir1.2-javascriptcoregtk-4.0_2.36.6-0ubuntu0.22.04.1_amd64.deb
-rw-r--r-- 1 root root 30880 Mär 24 17:57 
libdbusmenu-gtk4_16.04.1+18.10.20180917-0ubuntu8_amd64.deb
-rw-r--r-- 1 root root   3334266 Mär 24 19:44 
libgtk-3-doc_3.24.33-1ubuntu1_all.deb
-rw-r--r-- 1 root root   2864536 Jul 13 02:30 
libgtk-4-1_4.6.6+ds-0ubuntu1_amd64.deb
-rw-r--r-- 1 root root   2869302 Jul 13 02:30 
libgtk-4-bin_4.6.6+ds-0ubuntu1_amd64.deb
-rw-r--r-- 1 root root661682 Jul 13 02:30 
libgtk-4-common_4.6.6+ds-0ubuntu1_all.deb
-rw-r--r-- 1 root root   6675300 Aug 15 14:23 
libjavascriptcoregtk-4.0-18_2.36.6-0ubuntu0.22.04.1_amd64.deb
-rw-r--r-- 1 root root  16366740 Aug 15 14:23 
libwebkit2gtk-4.0-37_2.36.6-0ubuntu0.22.04.1_amd64.deb
-rw-r--r-- 1 root root130226 Jul  2 02:19 
qt5-gtk-platformtheme_5.15.3+dfsg-2ubuntu0.1_amd64.deb
-rw-r--r-- 1 root root 65236 Jul 26 15:13 
software-properties-gtk_0.99.22.3_all.deb
-- %< 

and here all "gtk-3" related versions...

-- %< 
root@ebony:/var/cache/apt/archives# dpkg -l | grep gtk-3
ii  gir1.2-gtk-3.0:amd64   3.24.33-1ubuntu2 
amd64GTK graphical user interface library -- gir bindings
ii  libgtk-3-0:amd64   3.24.33-1ubuntu2 
amd64GTK graphical user interface library
ii  libgtk-3-bin   3.24.33-1ubuntu2 
amd64programs for the GTK graphical user interface library
ii  libgtk-3-common3.24.33-1ubuntu2 
all  common files for the GTK graphical user interface library
ii  libgtk-3-doc   3.24.33-1ubuntu1 
all  documentation for the GTK graphical user interface library
ii  libspice-client-gtk-3.0-5:amd640.39-3ubuntu1
amd64GTK3 widget for SPICE clients (runtime library)
-- %< 

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

Title:
  libgail-3-0 dependencies cause a complete downgrade/uninstall of
  various packages

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have a fresh 22.04-LTS install on my new Huawei laptop, i tried and
  reviewed some mail clients and came to the conclusion to choose
  "evolution" as my new client, but my problem is i can't install
  "evolution" because some of his dependencies have to strong
  constrains, one of them is "libgail-3-0" which has "libgtk-3-0 (=
  3.24.33-1ubuntu1)" as dependency, which causes a downgrade/uninstall
  of some required packages, look at this console output:

  -- %< ---
  root@ebony:~# apt-get install evolution
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgail-3-0 : Depends: libgtk-3-0 (= 3.24.33-1ubuntu1) but 3.24.33-1ubuntu2 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@ebony:~# apt-get install evolution libgtk-3-0=3.24.33-1ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    apg gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-clutter-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdata-0.0
    gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 
gir1.2-graphene-1.0 gir1.2-gsound-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0 
gir1.2-json-1.0 gir1.2-nautilus-3.0 gir1.2-nm-1.0
    gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-unity-7.0 gir1.2-upowerglib-1.0 
gkbd-capplet gnome-bluetooth-3-common gnome-control-center-faces 
gnome-online-accounts gstreamer1.0-pipewire
    libcolord-gtk1 libfreerdp-server2-2 libgnome-bluetooth-3.0-13 
libgnomekbd-common libgnomekbd8 libgsound0 libgupnp-av-1.0-3 
libgupnp-dlna-2.0-4 libmediaart-2.0-0 librygel-core-2.6-2
    librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 
libsoup-3.0-0 libsoup-3.0-common libtext-engine-0.1-0 libvncserver1 
libxklavier16 

[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)

[Allan Lind Jensen]

The bug seems to cause Maple's authentication to fail. It uses the host-
id, which returns empty.

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

Title:
  mtd device must be supplied (device name is empty)

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

Bug description:
  [WORKAROUND]

  This will NOT fix a system that is not booting, because the "mtd
  device must be supplied (device name is empty)" message is not the
  cause of failed boots. This work around is only for those who are
  annoyed by the error message, but are otherwise not experiencing any
  issues.

  If you are not able to boot your system, but you see this error
  message, please open a separate bug with your journalctl and dmesg
  logs.

  # cp /{lib,etc}/systemd/system/systemd-pstore.service
  # sed -i 's/modprobe@mtdpstore.service //' 
/etc/systemd/system/systemd-pstore.service
  # systemctl daemon-reload

  [Impact]

  Due to mtdpstore not being properly configured as a pstore backend,
  when systemd-pstore.service tries to load the module, users get the
  following error in dmesg:

  [   18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
  [   18.462685] mtd device must be supplied (device name is empty)

  This is a distracting error for users trying to diagnose other system
  issues, especially if their system does not boot after a kernel crash
  and this is the only message displayed on the console.

  [Test Plan]

  * Force a kernel crash to populate /sys/fs/pstore, thus causing
  systemd-pstore.service to start on the subsequent boot:

  # echo 1 > /proc/sys/kernel/sysrq
  # echo 1 > /proc/sys/kernel/panic
  # echo c > /proc/sysrq-trigger

  * When the system reboots, observe the error in dmesg:

  # dmesg | grep mtd

  [Where problems could occur]

  If a system was relying on this pstore backend, and mtdpstore is built
  as a module, it is possible for systemd-pstore.service to trigger
  before mtdpstore is loaded, causing systemd-pstore to not copy the
  contents of /sys/fs/pstore. Note however that before the patched
  introduced as a result of bug 1978079, systemd-pstore.service would
  not attempt to load *any* kernel modules.

  [Original Description]

  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1967448] Re: All the windows and the desktop icons disappear constantly after setting Scaling to 300%

[Daniel van Vugt]

** Tags removed: fixed-in-42.1
** Tags added: fixed-in-gtk-3.24.35

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

Title:
  All the windows and the desktop icons disappear constantly after
  setting Scaling to 300%

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Summary
  ===

  Device with nvidia GPU, using proprietary drivers, wayland activated
  by default.

  By default, the scaling is set to 200% (the screen is UHD). If
  selecting 300%, all the windows close down, as well as the desktop
  icons (Home) as long as the mouse cursor is in the way.

  To fix the issue, one has to open the Display Settings (while making
  sure the mouse cursor is never above any of the Settings windows!),
  then set Scaling back to 200% using the keyboard.

  This problem does not happen in X11, and does not happen in Wayland if
  I select 100%, 200% or even 400% scaling!

  Steps to reproduce
  ==

  - Install 22.04 beta, selecting "install third party software" to make sure 
ubuntu-drivers installs the appropriate proprietary nvidia drivers.
  - After installation, make sure Wayland is in use (echo $XDG_SESSION_TYPE 
should return `wayland`)
  - Go to Settings > Display, select 300% scaling, then press Apply

  Expected result
  ===

  The scaling is set to 300% and user can keep using the device.

  Actual result
  =

  The scaling is set to 300% and all the windows are shut down. If user
  tries to reopen a window (e.g. Terminal), it is shut down immediately
  if the mouse cursor is hovering it. The desktop icons keep
  disappearing and reappearing for as long as the mouse cursor is
  hovering the background.

  The only way to stop this is to go back to Settings > Display, and,
  using the keyboard, set the scaling back to 200%.

  Information
  ===

  Version:  Ubuntu Jammy Jellyfish (development branch) [Beta image]
  Release:  22.04

  Device: Dell Precision 7760 with Nvidia GPU
  CID: 202103-28858

  Third party software installed during installation

  Wayland in use.

  ii  linux-generic-hwe-20.045.15.0.23.25   
 amd64Complete Generic Linux kernel and headers
  ii  linux-headers-5.15.0-235.15.0-23.23   
 all  Header files related to Linux kernel version 5.15.0
  ii  linux-headers-5.15.0-23-generic5.15.0-23.23   
 amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP
  ii  linux-headers-generic-hwe-20.045.15.0.23.25   
 amd64Generic Linux kernel headers
  ii  linux-image-5.15.0-23-generic  5.15.0-23.23   
 amd64Signed kernel image generic
  ii  linux-image-generic-hwe-20.04  5.15.0.23.25   
 amd64Generic Linux kernel image
  ii  linux-modules-5.15.0-23-generic5.15.0-23.23   
 amd64Linux kernel extra modules for version 5.15.0 on 64 bit 
x86 SMP
  ii  linux-modules-extra-5.15.0-23-generic  5.15.0-23.23   
 amd64Linux kernel extra modules for version 5.15.0 on 64 bit 
x86 SMP
  ii  linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 
 amd64Linux kernel nvidia modules for version 5.15.0-23
  ii  linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 
 amd64Extra drivers for nvidia-510 for the generic-hwe-20.04 
flavour
  ii  linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 
 amd64Linux kernel nvidia modules for version 5.15.0-23 
(objects)
  ii  linux-signatures-nvidia-5.15.0-23-generic  5.15.0-23.23+1 
 amd64Linux kernel signatures for nvidia modules for version 
5.15.0-23-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 10:24:25 2022
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: 

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

[Ubuntu Foundations Team Bug Bot]

The attachment "1-0.38.4-0ubuntu2.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
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:
  New

Bug description:
  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 1988777] Re: libgail-3-0 dependencies cause a complete downgrade/uninstall of various packages

[Enrico]

No jammy-updates repo isn't available or configured.

if i try a downgrade as you mentioned, then i have to reinstall my
entire desktop, is this really the only/final solution?


** Attachment added: "screenshot of configured repos"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1988777/+attachment/5613959/+files/Screenshot%20from%202022-09-06%2010-27-24.png

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

Title:
  libgail-3-0 dependencies cause a complete downgrade/uninstall of
  various packages

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have a fresh 22.04-LTS install on my new Huawei laptop, i tried and
  reviewed some mail clients and came to the conclusion to choose
  "evolution" as my new client, but my problem is i can't install
  "evolution" because some of his dependencies have to strong
  constrains, one of them is "libgail-3-0" which has "libgtk-3-0 (=
  3.24.33-1ubuntu1)" as dependency, which causes a downgrade/uninstall
  of some required packages, look at this console output:

  -- %< ---
  root@ebony:~# apt-get install evolution
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgail-3-0 : Depends: libgtk-3-0 (= 3.24.33-1ubuntu1) but 3.24.33-1ubuntu2 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@ebony:~# apt-get install evolution libgtk-3-0=3.24.33-1ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    apg gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-clutter-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdata-0.0
    gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 
gir1.2-graphene-1.0 gir1.2-gsound-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0 
gir1.2-json-1.0 gir1.2-nautilus-3.0 gir1.2-nm-1.0
    gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-unity-7.0 gir1.2-upowerglib-1.0 
gkbd-capplet gnome-bluetooth-3-common gnome-control-center-faces 
gnome-online-accounts gstreamer1.0-pipewire
    libcolord-gtk1 libfreerdp-server2-2 libgnome-bluetooth-3.0-13 
libgnomekbd-common libgnomekbd8 libgsound0 libgupnp-av-1.0-3 
libgupnp-dlna-2.0-4 libmediaart-2.0-0 librygel-core-2.6-2
    librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 
libsoup-3.0-0 libsoup-3.0-common libtext-engine-0.1-0 libvncserver1 
libxklavier16 mobile-broadband-provider-info
    network-manager-gnome policykit-1-gnome python3-certifi python3-chardet 
python3-debconf python3-debian python3-idna python3-macaroonbakery python3-nacl 
python3-nautilus python3-protobuf
    python3-pymacaroons python3-requests python3-rfc3339 python3-tz 
python3-urllib3 rygel sshfs switcheroo-control update-notifier-common xwayland
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  Suggested packages:
    db5.3-util doc-base evolution-ews evolution-plugins-experimental
  Recommended packages:
    libgtk-3-bin
  The following packages will be REMOVED:
    chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-control-center 
gnome-remote-desktop gnome-shell gnome-shell-extension-appindicator 
gnome-shell-extension-desktop-icons-ng
    gnome-shell-extension-gsconnect gnome-shell-extension-gsconnect-browsers 
gnome-shell-extension-manager gnome-shell-extension-ubuntu-dock libgtk-3-bin 
libmutter-10-0 ubuntu-desktop
    ubuntu-desktop-minimal ubuntu-release-upgrader-gtk ubuntu-session 
update-manager update-notifier
  The following NEW packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  The following packages will be DOWNGRADED:
    libgtk-3-0
  0 upgraded, 18 newly installed, 1 downgraded, 20 to remove and 0 not upgraded.
  Need to get 8.602 kB of archives.
  

[Touch-packages] [Bug 1941962] Re: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref()

[Daniel van Vugt]

Fixed in Ubuntu 22.04 and later.

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

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

Title:
  pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from
  pa_x11_wrapper_unref()

Status in X.Org X server:
  Fix Released
Status in libx11 package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/52094416ad4b4132ebf639ec8530fed1fdbac584

  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  Uname: Linux 5.13.13-xanmod1-cacule x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anasc  1719 F pulseaudio
   /dev/snd/pcmC0D0p:   anasc  1719 F...m pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Aug 28 21:00:59 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-08-26 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210824)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  SegvAnalysis:
   Segfault happened at: 0x7fbcc9d6a8a4 :  mov%edx,0x4(%rax)
   PC (0x7fbcc9d6a8a4) ok
   source "%edx" ok
   destination "0x4(%rax)" (0x0004) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   XFreeGC () from /lib/x86_64-linux-gnu/libX11.so.6
   XCloseDisplay () from /lib/x86_64-linux-gnu/libX11.so.6
   pa_x11_wrapper_unref () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
   module_x11_publish_LTX_pa__done () from 
/usr/lib/pulse-15.0+dfsg1/modules/module-x11-publish.so
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
  Title: pulseaudio crashed with SIGSEGV in XFreeGC()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 02/05/2021
  dmi.bios.release: 15.14
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 86E2
  dmi.board.vendor: HP
  dmi.board.version: 95.36
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.36
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd02/05/2021:br15.14:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:sku5SU52EA#BH4:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs3xxx
  dmi.product.sku: 5SU52EA#BH4
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1941962/+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 1981622] Re: mtd device must be supplied (device name is empty)

[Taha]

I have installed and tested the proposed package and my system is NOT
booting up as before.

Ubuntu 22.04.1 LTS
systemd: 249.11-0ubuntu3.5
kernel: 5.15.0-47-generic (tested also on 5.15.0-25-generic with the same 
result)

I get into the maintenance mode, reboot into the recovery and try to fix
things at this stage.

** Tags added: verification-failed-jammy

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

Title:
  mtd device must be supplied (device name is empty)

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

Bug description:
  [WORKAROUND]

  This will NOT fix a system that is not booting, because the "mtd
  device must be supplied (device name is empty)" message is not the
  cause of failed boots. This work around is only for those who are
  annoyed by the error message, but are otherwise not experiencing any
  issues.

  If you are not able to boot your system, but you see this error
  message, please open a separate bug with your journalctl and dmesg
  logs.

  # cp /{lib,etc}/systemd/system/systemd-pstore.service
  # sed -i 's/modprobe@mtdpstore.service //' 
/etc/systemd/system/systemd-pstore.service
  # systemctl daemon-reload

  [Impact]

  Due to mtdpstore not being properly configured as a pstore backend,
  when systemd-pstore.service tries to load the module, users get the
  following error in dmesg:

  [   18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
  [   18.462685] mtd device must be supplied (device name is empty)

  This is a distracting error for users trying to diagnose other system
  issues, especially if their system does not boot after a kernel crash
  and this is the only message displayed on the console.

  [Test Plan]

  * Force a kernel crash to populate /sys/fs/pstore, thus causing
  systemd-pstore.service to start on the subsequent boot:

  # echo 1 > /proc/sys/kernel/sysrq
  # echo 1 > /proc/sys/kernel/panic
  # echo c > /proc/sysrq-trigger

  * When the system reboots, observe the error in dmesg:

  # dmesg | grep mtd

  [Where problems could occur]

  If a system was relying on this pstore backend, and mtdpstore is built
  as a module, it is possible for systemd-pstore.service to trigger
  before mtdpstore is loaded, causing systemd-pstore to not copy the
  contents of /sys/fs/pstore. Note however that before the patched
  introduced as a result of bug 1978079, systemd-pstore.service would
  not attempt to load *any* kernel modules.

  [Original Description]

  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1988777] Re: libgail-3-0 dependencies cause a complete downgrade/uninstall of various packages

[Sebastien Bacher]

the issue is that you installed libgtk-3-0 from jammy-updates but that
source it's enabled anymore (or apt is phasing the update and not
proposing it to you)

check if jammy-updates is enabled (either in software-properties or by
editing the /etc/apt/sources.list configuration directly)

otherwise you should be able to download the newer libgail version from 
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.33-1ubuntu2/+build/23743631 
or to downgrade by using
$ sudo apt install libgtk-3-0=3.24.33-1ubuntu1 libgtk-3-bin=3.24.33-1ubuntu1 
libgtk-3-common=3.24.33-1ubuntu1 (you might need to add some extra gtk binaries 
to that list depending of what is installed on your system)

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

Title:
  libgail-3-0 dependencies cause a complete downgrade/uninstall of
  various packages

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have a fresh 22.04-LTS install on my new Huawei laptop, i tried and
  reviewed some mail clients and came to the conclusion to choose
  "evolution" as my new client, but my problem is i can't install
  "evolution" because some of his dependencies have to strong
  constrains, one of them is "libgail-3-0" which has "libgtk-3-0 (=
  3.24.33-1ubuntu1)" as dependency, which causes a downgrade/uninstall
  of some required packages, look at this console output:

  -- %< ---
  root@ebony:~# apt-get install evolution
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgail-3-0 : Depends: libgtk-3-0 (= 3.24.33-1ubuntu1) but 3.24.33-1ubuntu2 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@ebony:~# apt-get install evolution libgtk-3-0=3.24.33-1ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    apg gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-clutter-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdata-0.0
    gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 
gir1.2-graphene-1.0 gir1.2-gsound-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0 
gir1.2-json-1.0 gir1.2-nautilus-3.0 gir1.2-nm-1.0
    gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-unity-7.0 gir1.2-upowerglib-1.0 
gkbd-capplet gnome-bluetooth-3-common gnome-control-center-faces 
gnome-online-accounts gstreamer1.0-pipewire
    libcolord-gtk1 libfreerdp-server2-2 libgnome-bluetooth-3.0-13 
libgnomekbd-common libgnomekbd8 libgsound0 libgupnp-av-1.0-3 
libgupnp-dlna-2.0-4 libmediaart-2.0-0 librygel-core-2.6-2
    librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 
libsoup-3.0-0 libsoup-3.0-common libtext-engine-0.1-0 libvncserver1 
libxklavier16 mobile-broadband-provider-info
    network-manager-gnome policykit-1-gnome python3-certifi python3-chardet 
python3-debconf python3-debian python3-idna python3-macaroonbakery python3-nacl 
python3-nautilus python3-protobuf
    python3-pymacaroons python3-requests python3-rfc3339 python3-tz 
python3-urllib3 rygel sshfs switcheroo-control update-notifier-common xwayland
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  Suggested packages:
    db5.3-util doc-base evolution-ews evolution-plugins-experimental
  Recommended packages:
    libgtk-3-bin
  The following packages will be REMOVED:
    chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-control-center 
gnome-remote-desktop gnome-shell gnome-shell-extension-appindicator 
gnome-shell-extension-desktop-icons-ng
    gnome-shell-extension-gsconnect gnome-shell-extension-gsconnect-browsers 
gnome-shell-extension-manager gnome-shell-extension-ubuntu-dock libgtk-3-bin 
libmutter-10-0 ubuntu-desktop
    ubuntu-desktop-minimal ubuntu-release-upgrader-gtk ubuntu-session 
update-manager update-notifier
  The following NEW packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 

[Touch-packages] [Bug 1988819] [NEW] When apt keeps back packages due to phased updates, it should say so

[Sergio Callegari]

Public bug reported:

After phased updates have been introduced, it may happen that apt
upgrade shows packages as upgradable but ends up not upgrading them. In
this case the packages are indicated as being "kept back".

Unfortunately, the feedback provided about this to the user is not very
informative. The user sees the packages being kept back and thinks
something is going wrong on the system.

When packages are kept back because of phased updates, apt should say so
e.g., it should say that the upgrade is delayed.

Incidentally note that aptitude does not respect phased updates.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apt 2.4.7
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Sep  6 10:05:14 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-02-16 (933 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: apt
UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  When apt keeps back packages due to phased updates, it should say so

Status in apt package in Ubuntu:
  New

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+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 1970047] Re: GTK file open dialog hangs Chrome/Brave

[vinz486]

Fresh install Ubuntu 22.04
Chrome 105.0.5195.102 (Official Build) (64-bit)

Hardware: Lenovo Thinkpad P53 using native NVidia drivers.

Same issue, also disabling hardware acceleration in Chrome.

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

Title:
  GTK file open dialog hangs Chrome/Brave

Status in gtk+3.0 package in Ubuntu:
  Expired

Bug description:
  I removed xdg-desktop-portal because I use Xorg, don't use any snaps or 
flatpaks and GTK file open dialog is better than portal one.
  But GTK file open dialog makes Chrome/Brave freeze after closing it.

  Steps to reproduce:
  1. Install Chrome or Brave
  2. Remove xdg-desktop-portal so Chrome/Brave use GTK file open dialog instead 
of portal one
  3. Press Ctrl+O to open file open dialog
  4. Close dialog or choose any file, does not matter, browser is stuck 

  I don't see this behavior on Debian that I also use, so I guess bug is
  in GTK rather than Chrome/Brave.

  Fresh install of Ubuntu 22.04
  lsb_release:
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  libgtk-3-0:
Installed: 3.24.33-1ubuntu1
Candidate: 3.24.33-1ubuntu1
Version table:
   *** 3.24.33-1ubuntu1 500
  500 http://rs.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgtk-3-0 3.24.33-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 23 19:27:45 2022
  InstallationDate: Installed on 2022-04-22 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1970047/+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 1256999] Re: QFontDatabase: Cannot find font directory spams logs

[Daniel van Vugt]

No progress in the upstream bug for 8.5 years, but we don't ship Qt GUIs
anymore either. So "Won't Fix".

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  QFontDatabase: Cannot find font directory spams logs

Status in Ubuntu UI Toolkit:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Won't Fix
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  I was once again bitten by vital pieces missing in builds logs…
  QFontDatabase warnings contribute significantly to the noise in all
  builds. The fix is dead easy, create the folder usr/lib/*/fonts. But
  there's no work-around I'm aware of that doesn't touch system files so
  this should be fixed in Qt5 builds.

  I did report it against the toolkit for two reasons 1) I can't file
  bugs against the qt5 ppa 2) the toolkit is where these warnings cause
  problems so it's "affected" in launchpad jargon.

  Upstream: https://bugreports.qt-project.org/browse/QTBUG-36243

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1256999/+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 1988772] Re: kinetic livefs builds are failing on dns errors

[Łukasz Zemczak]

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

Title:
  kinetic livefs builds are failing on dns errors

Status in live-build package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  the livefs kinetic builds are still failing, every job failed for a
  week

  https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/kinetic/ubuntu

  >'Temporary failure resolving 'ftpmaster.internal'

  Colin poked at it and wrote

  > livecd-rootfs initially sets up a correct /etc/resolv.conf inside its build 
chroot; but then
  > systemd-resolved.postinst moves that aside in favour of a symlink to 
/run/systemd/resolve/stub-
  > resolv.conf, but systemd-resolved itself isn't running because 
livecd-rootfs builds in a chroot, 
  > not a container

  he also suggested that it could be perhaps handled from live-build
  scripts/build/lb_chroot_resolv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1988772/+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 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal

[Kleber Sacilotto de Souza]

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

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

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

Title:
  systemd: fix test-execute autotest failure with kernel 5.15 in focal

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress

Bug description:
  [Impact]

  test-execute autotest is failing in focal with kernel 5.15. This is
  because the following kernel commit changed the ABI for ioprio:

  e70344c05995 ("block: fix default IO priority handling")

  Previously setting IOPRIO_CLASS_NONE for a process would report
  IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
  IOPRIO_CLASS_BE instead.

  [Test case]

  Run systemd autopkgtest and check for the test-execute result.

  [Fix]

  Change test/test-execute/exec-ioschedulingclass-none.service to
  recognize both "none" and "best-effort" as valid returned strings from
  ionice.

  This change is already available in jammy and above.

  [Regression potential]

  We may see regressions in systemd autopkgtest, we won't introduce any
  potential regressions in systemd itself, because this is only
  affecting the specific unit test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+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 1988777] Re: libgail-3-0 dependencies cause a complete downgrade/uninstall of various packages

[Enrico]

Hi Sebastien,

as i reported before, ...

-- %< 
root@ebony:~# apt-cache policy evolution libgail-3-0 libgtk-3-0
evolution:
  Installed: (none)
  Candidate: 3.44.0-1
  Version table:
 3.44.0-1 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
libgail-3-0:
  Installed: (none)
  Candidate: 3.24.33-1ubuntu1
  Version table:
 3.24.33-1ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
libgtk-3-0:
  Installed: 3.24.33-1ubuntu2
  Candidate: 3.24.33-1ubuntu2
  Version table:
 *** 3.24.33-1ubuntu2 100
100 /var/lib/dpkg/status
 3.24.33-1ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
-- %< 

Both packages came from the Ubuntu main repositories, but during my
installation and upgrade process apt/dpkg decided to install libgtk-3-0
(3.24.33-1ubuntu2) but, libgail-3-0 needs version (3.24.33-1ubuntu1 <--
look at the end it has a "1") of libgtk-3-0, that's the root of all my
issues.

From my point of view, it looks like libgail-3-0 has a strong constrain
on version libgtk-3-0 (3.24.33-1ubuntu1), look at the following
output...

-- %< 
root@ebony:~# apt-cache show libgail-3-0
Package: libgail-3-0
...
Depends: at-spi2-core, libatk1.0-0 (>= 2.35.1), libc6 (>= 2.4), libglib2.0-0 
(>= 2.57.2), libgtk-3-0 (= 3.24.33-1ubuntu1), libpango-1.0-0 (>= 1.44.0)
Filename: pool/main/g/gtk+3.0/libgail-3-0_3.24.33-1ubuntu1_amd64.deb
...
-- %< 

i hope this makes it clear now, if u have further question, just ask,
i'm available the entire week 16x7 ;-) .

Best regards
Enrico

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

Title:
  libgail-3-0 dependencies cause a complete downgrade/uninstall of
  various packages

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have a fresh 22.04-LTS install on my new Huawei laptop, i tried and
  reviewed some mail clients and came to the conclusion to choose
  "evolution" as my new client, but my problem is i can't install
  "evolution" because some of his dependencies have to strong
  constrains, one of them is "libgail-3-0" which has "libgtk-3-0 (=
  3.24.33-1ubuntu1)" as dependency, which causes a downgrade/uninstall
  of some required packages, look at this console output:

  -- %< ---
  root@ebony:~# apt-get install evolution
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgail-3-0 : Depends: libgtk-3-0 (= 3.24.33-1ubuntu1) but 3.24.33-1ubuntu2 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@ebony:~# apt-get install evolution libgtk-3-0=3.24.33-1ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    apg gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-clutter-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdata-0.0
    gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 
gir1.2-graphene-1.0 gir1.2-gsound-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0 
gir1.2-json-1.0 gir1.2-nautilus-3.0 gir1.2-nm-1.0
    gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-unity-7.0 gir1.2-upowerglib-1.0 
gkbd-capplet gnome-bluetooth-3-common gnome-control-center-faces 
gnome-online-accounts gstreamer1.0-pipewire
    libcolord-gtk1 libfreerdp-server2-2 libgnome-bluetooth-3.0-13 
libgnomekbd-common libgnomekbd8 libgsound0 libgupnp-av-1.0-3 
libgupnp-dlna-2.0-4 libmediaart-2.0-0 librygel-core-2.6-2
    librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 
libsoup-3.0-0 libsoup-3.0-common libtext-engine-0.1-0 libvncserver1 
libxklavier16 mobile-broadband-provider-info
    network-manager-gnome policykit-1-gnome python3-certifi python3-chardet 
python3-debconf python3-debian python3-idna python3-macaroonbakery python3-nacl 
python3-nautilus python3-protobuf
    python3-pymacaroons python3-requests python3-rfc3339 python3-tz 
python3-urllib3 rygel sshfs switcheroo-control update-notifier-common xwayland
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 

[Touch-packages] [Bug 1982108] Re: SRU: update python3.10 to the 3.10.5 release in 22.04 LTS

[Graham Inggs]

After some retries, the regressions were reduced to:

loguru/0.6.0-1 (arm64, amd64, s390x)
mypy/0.942-1 (ppc64el, arm64, amd64, s390x, armhf)

These are test failures already fixed in kinetic.  I'm investigating
SRUs for these two packages.

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

Title:
  SRU: update python3.10 to the 3.10.5 release in 22.04 LTS

Status in python3-defaults package in Ubuntu:
  New
Status in python3-stdlib-extensions package in Ubuntu:
  Confirmed
Status in python3.10 package in Ubuntu:
  Confirmed
Status in python3-defaults source package in Jammy:
  Fix Committed
Status in python3-stdlib-extensions source package in Jammy:
  Fix Committed
Status in python3.10 source package in Jammy:
  Fix Committed

Bug description:
  SRU: update python3.10 to the 3.10.5 release in 22.04 LTS

  we are doing a test rebuild of 22.04 main to check for regressions.

  test rebuilds at
  
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-jammy.html
  
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220728-jammy-gcc-jammy.html

  the first one is the reference test rebuild, the second one the
  rebuild using updated binutils, GCC and python packages.

  Analysis:

  regressions on riscv64 (caused by enabling the tests) are:

  abseil
  adsys
  colord
  dovecot
  glib-networking
  glibc
  gnome-bluetooth3
  gnome-control-center
  google-perftools
  json-glib
  libfprint
  libgdata
  memcached
  mir
  openvswitch
  ovn
  pmdk
  power-profiles-daemon
  strace
  swtpm
  vim

  devscripts is not a regression, introduced by a custom dpkg-
  buildpackage wrapper.

  binutils and python3-stdlib-extensions are superseded which are part
  of the planned updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1982108/+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 1988777] Re: libgail-3-0 dependencies cause a complete downgrade/uninstall of various packages

[Sebastien Bacher]

Thank you for your bug report. What's the output of

$ apt policy  libgail-3-0 libgtk-3-0

it sounds like one package is coming from update but the other one not
available, which could be because a source is disable or due to apt
doing selective updates

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  libgail-3-0 dependencies cause a complete downgrade/uninstall of
  various packages

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have a fresh 22.04-LTS install on my new Huawei laptop, i tried and
  reviewed some mail clients and came to the conclusion to choose
  "evolution" as my new client, but my problem is i can't install
  "evolution" because some of his dependencies have to strong
  constrains, one of them is "libgail-3-0" which has "libgtk-3-0 (=
  3.24.33-1ubuntu1)" as dependency, which causes a downgrade/uninstall
  of some required packages, look at this console output:

  -- %< ---
  root@ebony:~# apt-get install evolution
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgail-3-0 : Depends: libgtk-3-0 (= 3.24.33-1ubuntu1) but 3.24.33-1ubuntu2 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@ebony:~# apt-get install evolution libgtk-3-0=3.24.33-1ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    apg gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-clutter-1.0 
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 
gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdata-0.0
    gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 
gir1.2-graphene-1.0 gir1.2-gsound-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0 
gir1.2-json-1.0 gir1.2-nautilus-3.0 gir1.2-nm-1.0
    gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-unity-7.0 gir1.2-upowerglib-1.0 
gkbd-capplet gnome-bluetooth-3-common gnome-control-center-faces 
gnome-online-accounts gstreamer1.0-pipewire
    libcolord-gtk1 libfreerdp-server2-2 libgnome-bluetooth-3.0-13 
libgnomekbd-common libgnomekbd8 libgsound0 libgupnp-av-1.0-3 
libgupnp-dlna-2.0-4 libmediaart-2.0-0 librygel-core-2.6-2
    librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 
libsoup-3.0-0 libsoup-3.0-common libtext-engine-0.1-0 libvncserver1 
libxklavier16 mobile-broadband-provider-info
    network-manager-gnome policykit-1-gnome python3-certifi python3-chardet 
python3-debconf python3-debian python3-idna python3-macaroonbakery python3-nacl 
python3-nautilus python3-protobuf
    python3-pymacaroons python3-requests python3-rfc3339 python3-tz 
python3-urllib3 rygel sshfs switcheroo-control update-notifier-common xwayland
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  Suggested packages:
    db5.3-util doc-base evolution-ews evolution-plugins-experimental
  Recommended packages:
    libgtk-3-bin
  The following packages will be REMOVED:
    chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-control-center 
gnome-remote-desktop gnome-shell gnome-shell-extension-appindicator 
gnome-shell-extension-desktop-icons-ng
    gnome-shell-extension-gsconnect gnome-shell-extension-gsconnect-browsers 
gnome-shell-extension-manager gnome-shell-extension-ubuntu-dock libgtk-3-bin 
libmutter-10-0 ubuntu-desktop
    ubuntu-desktop-minimal ubuntu-release-upgrader-gtk ubuntu-session 
update-manager update-notifier
  The following NEW packages will be installed:
    bogofilter bogofilter-bdb bogofilter-common evolution evolution-common 
evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins 
libchamplain-0.12-0 libchamplain-gtk-0.12-0
    libcmark0.30.2 libevolution libgail-3-0 libgnome-autoar-gtk-0-0 libpst4 
libytnef0 notification-daemon policykit-1-gnome
  The following packages will be DOWNGRADED:
    libgtk-3-0
  0 upgraded, 18 newly installed, 1 downgraded, 20 to remove and 0 not upgraded.
  Need to get 8.602 kB of archives.
  After this operation, 16,0 MB of additional disk space