[Touch-packages] [Bug 1990312] Re: Can't change desktop language in Ubuntu 22.04

[Michael Opdenacker]

Set the package to "ubuntu-meta" containing "ubuntu-desktop"

** Package changed: ubuntu => ubuntu-meta (Ubuntu)

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

Title:
  Can't change desktop language in Ubuntu 22.04

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  I initially installed Ubuntu 22.04 with the English language.
  Now, I'd like to use the Ubuntu desktop in the German language.
  I believe I've done everything needed. I rebooted of course. The login screen 
is now in German, but my user desktop is still in English, except the calendar 
showing the date.

  See the attached screenshot.

  Here is the output of the "locale" command:

  LANG=de_DE.UTF-8
  LANGUAGE=en
  LC_CTYPE=en_US.UTF-8
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE=en_US.UTF-8
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES=en_US.UTF-8
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  Am I the only one having this issue?
  Thanks in advance
  Michael

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990312/+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 1990312] [NEW] Can't change desktop language in Ubuntu 22.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I initially installed Ubuntu 22.04 with the English language.
Now, I'd like to use the Ubuntu desktop in the German language.
I believe I've done everything needed. I rebooted of course. The login screen 
is now in German, but my user desktop is still in English, except the calendar 
showing the date.

See the attached screenshot.

Here is the output of the "locale" command:

LANG=de_DE.UTF-8
LANGUAGE=en
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=de_DE.UTF-8
LC_TIME=de_DE.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=de_DE.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_ALL=

Am I the only one having this issue?
Thanks in advance
Michael

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


** Tags: bot-comment
-- 
Can't change desktop language in Ubuntu 22.04
https://bugs.launchpad.net/bugs/1990312
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-meta 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 1990315] Re: cannot link against libudev

[Thomas Debesse]

I had noticed `pkg-config --list-all` is listing two udev packages,
`udev` and `libudev`. `pkg-config --libs udev` prints nothing but `pkg-
config --libs libudev` prints `-ludev`.

I had also noticed that the link command did not featured `-ludev`. I
also had tried to set compile/link flags to `-ludev` using environment
variables without success at the time, but now that I just retried I
noticed that if I delete the build dir, the flags are used and the build
pass.

I assume `libudev.h` is found properly because the code compiles, the
error is a link error.

Now, why there are two udev packages listed by pkg-config and why the
linker flag isn't passed to mesa is a mystery to me.

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

Title:
  cannot link against libudev

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When building Mesa vulkan drivers I get a lot of those error messages
  and the build fails:

  ```
  error: undefined symbol: udev_new
  error: undefined symbol: udev_monitor_get_fd
  error: undefined symbol: udev_monitor_new_from_netlink
  error: undefined symbol: udev_monitor_receive_device
  error: undefined symbol: udev_monitor_unref
  error: undefined symbol: udev_unref
  error: undefined symbol: udev_device_unref
  error: undefined symbol: udev_device_get_property_value
  error: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype
  error: undefined symbol: udev_monitor_enable_receiving
  ```

  It worked on Ubuntu 21.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990315/+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 1990287] Re: Two-finger right-click and drag causes additional click

[Daniel van Vugt]

It sounds like you're moving too fast for the default tap-to-click
thresholds :)

I would recommend disabling tap-to-click in Settings so that only
physical clicks of the pad are used as button press events. If you need
very accurate, very fast input then always use physical buttons.

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

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

** Changed in: libinput (Ubuntu)
   Status: New => Opinion

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

Title:
  Two-finger right-click and drag causes additional click

Status in libinput package in Ubuntu:
  Opinion

Bug description:
  I've found a consistent issue since upgrading from 20.04 to 22.04 where 
performing a two-finger tap (to right click) and then quickly performing a 
single tap drag causes a click event on the release of the drag.
  One place this manifests is when in a browser, if you two-finger right-click 
on a link, then quickly (must be done quickly) drag the cursor over the menu 
(eg open in new tab). When the finger is released from the drag, it performs a 
click on the menu item.
  It also happens in other applications as far as I can tell.
  Not a critical bug, but very frustrating as the muscle memory means lots of 
mis-clicks.

  I've found the timing between the two-finger tap and one-finger drag
  must be small (fraction of a section) to trigger the behaviour.

  I've tried installing 22.04 fresh, with no change.

  I'm using a Lenovo Thinkpad Carbon X1 G9.

  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: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 20 14:16:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d5]
  InstallationDate: Installed on 2022-09-19 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XWCTO1WW
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=ab25a65e-dd77-4b5c-bd5e-75691f427498 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2022
  dmi.bios.release: 1.55
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET79W (1.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  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.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  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/libinput/+bug/1990287/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()

[Daniel van Vugt]

** Summary changed:

- apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)
+ apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) 
from gtk_css_value_icon_theme_compute() from 
gtk_css_static_style_compute_value()

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0) from
  gtk_css_value_icon_theme_compute() from
  gtk_css_static_style_compute_value()

Status in apport package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in apport source package in Focal:
  Triaged
Status in gtk+3.0 source package in Focal:
  Confirmed

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

[Seth Arnold]

An alternative, proposed by user avih on IRC, is to not report any of
these packages to the user at all:

 however, these phased updates are quite a big list which adds a lot of 
noise to my regular dist-upgrade, and it interferes  with me reviewing what's 
about to get updated
 the kept back list is quite bigger than the list of things to update...
 arraybolt3: if this is indeed the standard order of things, why am i 
being shown at all what it's NOT going to install for reasons not related to 
errors or conflicts?

I can see a lot of appeal to not telling the user information -- from
their perspective, the packages don't actually exist yet.

Maybe it'll cause confusion if of two machines sitting right next to
each other, one can see the updates and the other cannot. That's not
ideal.

But holding information back from the user doesn't require new strings,
and casual users with one machine might never notice.

It's just fun to see an alternative idea that's 180 degrees different
from my initial thought. :)

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

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 1981622] Re: mtd device must be supplied (device name is empty)

[Onuh Victor]

Thanks Nick, the issue is now fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Invalid
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 1990315] Re: cannot link against libudev

[Steve Langasek]

For the record, showing only the errors, without showing the linker
command that produced them, is not an actionable bug report.

These symbols are certainly present in libudev.so.1 in kinetic so this
is likely not a bug in the Ubuntu systemd package.

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

Title:
  cannot link against libudev

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When building Mesa vulkan drivers I get a lot of those error messages
  and the build fails:

  ```
  error: undefined symbol: udev_new
  error: undefined symbol: udev_monitor_get_fd
  error: undefined symbol: udev_monitor_new_from_netlink
  error: undefined symbol: udev_monitor_receive_device
  error: undefined symbol: udev_monitor_unref
  error: undefined symbol: udev_unref
  error: undefined symbol: udev_device_unref
  error: undefined symbol: udev_device_get_property_value
  error: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype
  error: undefined symbol: udev_monitor_enable_receiving
  ```

  It worked on Ubuntu 21.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990315/+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 1990315] Re: cannot link against libudev

[Nick Rosbrook]

Are you missing a linker flag, i.e. -ludev, or did you forget to include
libudev.h?

If it's not either of those, please provide some more information such
as your current Ubuntu release, and what version of libudev-dev is
installed on your system:

$ apt-cache policy libudev-dev

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

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

Title:
  cannot link against libudev

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When building Mesa vulkan drivers I get a lot of those error messages
  and the build fails:

  ```
  error: undefined symbol: udev_new
  error: undefined symbol: udev_monitor_get_fd
  error: undefined symbol: udev_monitor_new_from_netlink
  error: undefined symbol: udev_monitor_receive_device
  error: undefined symbol: udev_monitor_unref
  error: undefined symbol: udev_unref
  error: undefined symbol: udev_device_unref
  error: undefined symbol: udev_device_get_property_value
  error: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype
  error: undefined symbol: udev_monitor_enable_receiving
  ```

  It worked on Ubuntu 21.10.

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

[Robie Basak]

> We can't really store reasons for why something is kept back.

How about:

When something is scored down because it is not phased, make a note.
When the scoring is all done, take the list of held back packages, and
identify all those that have a note against them. Then print (up to) two
lists:

The following packages are being phased and have been kept back:
   ...

The following [additional] packages have been kept back:
   ...

(use two translatable strings for the second message, adding
"additional" if the first list was non-zero).

Of course the exact strings can be adjusted, but I hope you see my point
in fixing the "we don't know what final reason is because the different
scoring adjustments get conflated" problem.

> 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).

We should certainly be able to fix this in the development release and
get translations in the usual way. For SRU, we could wait for
translations, or not, but no need to block on a fix in the development
release for this.

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

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 1990315] [NEW] cannot link against libudev

[Thomas Debesse]

Public bug reported:

When building Mesa vulkan drivers I get a lot of those error messages
and the build fails:

```
error: undefined symbol: udev_new
error: undefined symbol: udev_monitor_get_fd
error: undefined symbol: udev_monitor_new_from_netlink
error: undefined symbol: udev_monitor_receive_device
error: undefined symbol: udev_monitor_unref
error: undefined symbol: udev_unref
error: undefined symbol: udev_device_unref
error: undefined symbol: udev_device_get_property_value
error: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype
error: undefined symbol: udev_monitor_enable_receiving
```

It worked on Ubuntu 21.10.

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

** Package changed: nfs-utils (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/1990315

Title:
  cannot link against libudev

Status in systemd package in Ubuntu:
  New

Bug description:
  When building Mesa vulkan drivers I get a lot of those error messages
  and the build fails:

  ```
  error: undefined symbol: udev_new
  error: undefined symbol: udev_monitor_get_fd
  error: undefined symbol: udev_monitor_new_from_netlink
  error: undefined symbol: udev_monitor_receive_device
  error: undefined symbol: udev_monitor_unref
  error: undefined symbol: udev_unref
  error: undefined symbol: udev_device_unref
  error: undefined symbol: udev_device_get_property_value
  error: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype
  error: undefined symbol: udev_monitor_enable_receiving
  ```

  It worked on Ubuntu 21.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990315/+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 1990315] [NEW] cannot link against libudev

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When building Mesa vulkan drivers I get a lot of those error messages
and the build fails:

```
error: undefined symbol: udev_new
error: undefined symbol: udev_monitor_get_fd
error: undefined symbol: udev_monitor_new_from_netlink
error: undefined symbol: udev_monitor_receive_device
error: undefined symbol: udev_monitor_unref
error: undefined symbol: udev_unref
error: undefined symbol: udev_device_unref
error: undefined symbol: udev_device_get_property_value
error: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype
error: undefined symbol: udev_monitor_enable_receiving
```

It worked on Ubuntu 21.10.

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

-- 
cannot link against libudev
https://bugs.launchpad.net/bugs/1990315
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 1980545] Re: Update evolution-data-server to 3.44.4

[Launchpad Bug Tracker]

This bug was fixed in the package evolution-data-server -
3.44.4-0ubuntu1

---
evolution-data-server (3.44.4-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1980545)

 -- Nathan Pratta Teodosio   Wed, 06 Jul
2022 10:46:37 -0300

** Changed in: evolution-data-server (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Update evolution-data-server to 3.44.4

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series.

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.4/NEWS

  The current version in Ubuntu 22.04 LTS is 3.44.2.

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

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

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

[Brian Murray]

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

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

Title:
  Update evolution-data-server to 3.44.4

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series.

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.4/NEWS

  The current version in Ubuntu 22.04 LTS is 3.44.2.

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

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

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

[Seth Arnold]

apt-cache policy knows when packages are phased; when apt needs to
report that packages are held back, apt could look up each one to report
phased status.

Not fixing this because the strings need translating is an argument for
declaring APT a finished project and moving on to the Next Big Thing.

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

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 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )

[den]

i have this probleme only on ubuntu 22.04.1 LTS AND on linux mint 21 .

i have tested on ubuntu 20.04 and all works fine .

i have a debian testing , if you want , i can do the same things to see
if the problem is still present on this OS .

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

Title:
  Cannot move file to trash, do you want to delete immediately?" on EXT4
  partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on
  ubuntu 20.04 )

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Hi , when i delete a file where is in another partition than " / " or
  mounted in /media/ , i obtain the message in title.

  how can i use trash again please ?

  iznobe@iznobe-PC:~$ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # 
 
  # / was on /dev/nvme0n1p2 during installation
  UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e /   ext4
noatime,errors=remount-ro   0   1

  # /boot/efi was on /dev/nvme0n1p1 during installation
  UUID=C071-9050/boot/efi   
vfatdefaults0   0

  # swap was on /dev/sdc3 during installation
  UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap
sw,pri=10   0

  # partition de données separée comune aux OS linux
  UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas  ext4
defaults0   0
  LABEL=WD8 /Vidéos/WD8 ext4
defaults0   0
  #/dev/disk/by-label/WD8PRO2  /media/WD8PRO2 ext4  
  defaults0   0

  LABEL=WD8PRO2   /Vidéos/WD8PRO2
  ext4defaults 0   0

  LABEL=WD8PRO1 /media/WD8PRO1  ext4
defaults0   0
  LABEL=Seagate_4T  /media/Seagate_4T   ext4
defaults,noauto 0   0

  trash is working for filesysteme mounted on /media/WD8PRO1 but not in
  FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS
  .

  Exactly same file systeme mounted on same directory , with same trash
  directory is working fine on ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+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 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )

[Aaron Rainbolt]

I'm not sure if this problem is happening on Linux Mint 21 or Ubuntu
22.04.1. While Linux Mint is based on Ubuntu, it is not the same as
Ubuntu, and may have behaviors (and bugs!) that differ from Ubuntu's.
Could you clarify which Linux distro you're experiencing this problem
on?

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

Title:
  Cannot move file to trash, do you want to delete immediately?" on EXT4
  partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on
  ubuntu 20.04 )

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Hi , when i delete a file where is in another partition than " / " or
  mounted in /media/ , i obtain the message in title.

  how can i use trash again please ?

  iznobe@iznobe-PC:~$ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # 
 
  # / was on /dev/nvme0n1p2 during installation
  UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e /   ext4
noatime,errors=remount-ro   0   1

  # /boot/efi was on /dev/nvme0n1p1 during installation
  UUID=C071-9050/boot/efi   
vfatdefaults0   0

  # swap was on /dev/sdc3 during installation
  UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap
sw,pri=10   0

  # partition de données separée comune aux OS linux
  UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas  ext4
defaults0   0
  LABEL=WD8 /Vidéos/WD8 ext4
defaults0   0
  #/dev/disk/by-label/WD8PRO2  /media/WD8PRO2 ext4  
  defaults0   0

  LABEL=WD8PRO2   /Vidéos/WD8PRO2
  ext4defaults 0   0

  LABEL=WD8PRO1 /media/WD8PRO1  ext4
defaults0   0
  LABEL=Seagate_4T  /media/Seagate_4T   ext4
defaults,noauto 0   0

  trash is working for filesysteme mounted on /media/WD8PRO1 but not in
  FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS
  .

  Exactly same file systeme mounted on same directory , with same trash
  directory is working fine on ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+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 1971409] Re: value_copy: Assertion `arg->contents != nullptr' failed.

[Brian Murray]

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

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

Title:
  value_copy: Assertion `arg->contents != nullptr' failed.

Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  When debugging RP2040 with vscode this assert makes gdb crash.
  This is a new assert, that wasn't present in gdb 11.
  The fix is easy, replace `if (!value_lazy (val))` to `if (!value_lazy (val) 
&& arg->contents != nullptr) `.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971409/+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 1974456] Re: regression: apt.postint fails if never previously configured

[Brian Murray]

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

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

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Released

Bug description:
  [Impact]
  bootstrapping a system with apt that fixes #1968154 fails in focal and 
bionic, as they try to execute the config file that is being removed.

  This is not a problem on updates, only on new installs, so impact is
  limited to bootstrapping tools that enable -updates, such as
  mmdebstrap.

  [Test case]

  bootstrapping with -updates enabled can easily be tested with
  mmdebstrap:

  mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal

  for example, on focal:

  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: 
not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  [Regression potential]
  We remove 5 lines from the shell postinst script, there could be syntax 
errors? But then we'd see those during upgrades, so practically none.

  [Original bug report]
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  It works with apt 2.0.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )

[den]

** Description changed:

  Hi , when i delete a file where is in another partition than " / " or
- mounted in /media/ , i obtain this message .
+ mounted in /media/ , i obtain the message in title.
  
  how can i use trash again please ?
  
  iznobe@iznobe-PC:~$ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # 
 
  # / was on /dev/nvme0n1p2 during installation
  UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e /   ext4
noatime,errors=remount-ro   0   1
  
  # /boot/efi was on /dev/nvme0n1p1 during installation
  UUID=C071-9050/boot/efi   
vfatdefaults0   0
  
  # swap was on /dev/sdc3 during installation
  UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap
sw,pri=10   0
  
  # partition de données separée comune aux OS linux
  UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas  ext4
defaults0   0
  LABEL=WD8 /Vidéos/WD8 ext4
defaults0   0
  #/dev/disk/by-label/WD8PRO2  /media/WD8PRO2 ext4  
  defaults0   0
  
  LABEL=WD8PRO2   /Vidéos/WD8PRO2
  ext4defaults 0   0
  
  LABEL=WD8PRO1 /media/WD8PRO1  ext4
defaults0   0
  LABEL=Seagate_4T  /media/Seagate_4T   ext4
defaults,noauto 0   0
  
  trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS
  mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS .
  
  Exactly same file systeme mounted on same directory , with same trash
  directory is working fine on ubuntu 20.04

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

Title:
  Cannot move file to trash, do you want to delete immediately?" on EXT4
  partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on
  ubuntu 20.04 )

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Hi , when i delete a file where is in another partition than " / " or
  mounted in /media/ , i obtain the message in title.

  how can i use trash again please ?

  iznobe@iznobe-PC:~$ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # 
 
  # / was on /dev/nvme0n1p2 during installation
  UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e /   ext4
noatime,errors=remount-ro   0   1

  # /boot/efi was on /dev/nvme0n1p1 during installation
  UUID=C071-9050/boot/efi   
vfatdefaults0   0

  # swap was on /dev/sdc3 during installation
  UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap
sw,pri=10   0

  # partition de données separée comune aux OS linux
  UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas  ext4
defaults0   0
  LABEL=WD8 /Vidéos/WD8 ext4
defaults0   0
  #/dev/disk/by-label/WD8PRO2  /media/WD8PRO2 ext4  
  defaults0   0

  LABEL=WD8PRO2   /Vidéos/WD8PRO2
  ext4defaults 0   0

  LABEL=WD8PRO1 /media/WD8PRO1  ext4
defaults0   0
  LABEL=Seagate_4T  /media/Seagate_4T   ext4
defaults,noauto 0   0

  trash is working for filesysteme mounted on /media/WD8PRO1 but not in
  FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS
  .

  Exactly same file systeme mounted on same directory , with same trash
  directory is working fine on ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+subscriptions


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

[Touch-packages] [Bug 1966849] Re: gzip exec format error under WSL1

[Brian Murray]

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

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

Title:
  gzip exec format error under WSL1

Status in gzip:
  New
Status in gzip package in Ubuntu:
  Fix Released
Status in gzip source package in Jammy:
  Fix Committed
Status in gzip source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

   * Optimization features included in jammy cause atypical alignment of
  LOAD ELF sections. This in turn causes failure to execute binaries on
  WSL1. Upstream have since integrated the optimization features
  included in jammy, but also reverted alignment to a previously used
  one. This also results in working binary under WSL1.

   * Cherry-pick upstream applied revert to alignment to resolve running
  gzip under WSL1.

  [Test Plan]

   * Use powershell to set default WSL version to 1

   * Deploy WSL1, unpack and use updated gzip package

   * gzip --version should execute correctly under WSL 1

  [Where problems could occur]

   * I cannot tell why performance improvement patches introduced
  alignment change, and if revert of the alignment change affects the
  performance. Note that this change aligns the codebase closer to what
  kinetic & upstream now are.

  [Other Info]
   
   * This bug fix is upstream commit 
https://git.savannah.gnu.org/cgit/gzip.git/commit/gzip.c?id=23a870d14a49803c6d2579071886c1acf497c9d1

  ---

  gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows
  19044.1620, making WSL pretty much unusable.

  bash: /usr/bin/gzip: cannot execute binary file: Exec format error

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gzip 1.10-4ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35
  Uname: Linux 4.4.0-19041-Microsoft x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Mar 29 06:40:33 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gzip
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gzip/+bug/1966849/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

Might i have emptied or removed 
/etc/modprobe.d/blacklist.conf
by mistake? It was awfully empty!?

--- pre ---
# https://askubuntu.com/a/67028/289138

$ dpkg -S /etc/modprobe.d/blacklist.conf
kmod: /etc/modprobe.d/blacklist.conf

$ sudo apt install --reinstall -o 
Dpkg::Options::="--force-confask,confnew,confmiss" kmod
...
--- /pre ---

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

Might it be the case that I somehow removed or emptied
/etc/modprobe.d/blacklist.conf ?

--- pre ---
# https://askubuntu.com/a/67028/289138
$ dpkg -S /etc/modprobe.d/blacklist.conf
dpkg -S /etc/modprobe.d/blacklist.conf
$ sudo apt install --reinstall -o 
Dpkg::Options::="--force-confask,confnew,confmiss" kmod
--- /pre ---

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1989973] Re: focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it uninstallable without explicit version

[Brian Murray]

** Tags added: regression-security

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

Title:
  focal: Vim 2:8.1.2269-1ubuntu5.8 failed to build for arm32, makes it
  uninstallable without explicit version

Status in vim package in Ubuntu:
  Fix Released

Bug description:
  In a fresh focal install/container, vim is uninstallable because
  version 2:8.1.2269-1ubuntu5.8 failed to build for vim, but the `all`
  packages did succeed.

  ```
  $ docker run -ti --rm arm32v7/ubuntu:focal bash -c 'apt update && apt install 
vim-tiny'
  WARNING: The requested image's platform (linux/arm/v7) does not match the 
detected host platform (linux/amd64) and no specific platform was requested
  Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB]
  Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB]
  Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB]
  Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB]
  Get:5 http://ports.ubuntu.com/ubuntu-ports focal/main armhf Packages [1227 kB]
  Get:6 http://ports.ubuntu.com/ubuntu-ports focal/universe armhf Packages 
[10.9 MB]
  Get:7 http://ports.ubuntu.com/ubuntu-ports focal/multiverse armhf Packages 
[141 kB]
  Get:8 http://ports.ubuntu.com/ubuntu-ports focal/restricted armhf Packages 
[10.8 kB]
  Get:9 http://ports.ubuntu.com/ubuntu-ports focal-updates/restricted armhf 
Packages [16.9 kB]
  Get:10 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe armhf 
Packages [996 kB]
  Get:11 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse armhf 
Packages [9626 B]
  Get:12 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf Packages 
[1400 kB]
  Get:13 http://ports.ubuntu.com/ubuntu-ports focal-backports/universe armhf 
Packages [27.4 kB]
  Get:14 http://ports.ubuntu.com/ubuntu-ports focal-backports/main armhf 
Packages [54.7 kB]
  Get:15 http://ports.ubuntu.com/ubuntu-ports focal-security/main armhf 
Packages [1032 kB]
  Get:16 http://ports.ubuntu.com/ubuntu-ports focal-security/multiverse armhf 
Packages [4730 B]
  Get:17 http://ports.ubuntu.com/ubuntu-ports focal-security/universe armhf 
Packages [698 kB]
  Get:18 http://ports.ubuntu.com/ubuntu-ports focal-security/restricted armhf 
Packages [16.6 kB]
  Fetched 17.2 MB in 8s (2274 kB/s)
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  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:
   vim-tiny : Depends: vim-common (= 2:8.1.2269-1ubuntu5.7) but 
2:8.1.2269-1ubuntu5.8 is to be installed
  E: Unable to correct problems, you have held broken packages.
  ```

  Seems to be due to
  https://launchpad.net/ubuntu/+source/vim/2:8.1.2269-1ubuntu5.8/+build/24478851

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

[Nick Rosbrook]

** Changed in: systemd (Ubuntu Focal)
   Status: In Progress => Invalid

-- 
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:
  Invalid
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 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )

[den]

** Description changed:

  Hi , when i delete a file where is in another partition than " / " or
  mounted in /media/ , i obtain this message .
  
  how can i use trash again please ?
  
  iznobe@iznobe-PC:~$ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # 
 
  # / was on /dev/nvme0n1p2 during installation
  UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e /   ext4
noatime,errors=remount-ro   0   1
  
  # /boot/efi was on /dev/nvme0n1p1 during installation
  UUID=C071-9050/boot/efi   
vfatdefaults0   0
  
  # swap was on /dev/sdc3 during installation
  UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap
sw,pri=10   0
  
  # partition de données separée comune aux OS linux
  UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas  ext4
defaults0   0
  LABEL=WD8 /Vidéos/WD8 ext4
defaults0   0
  #/dev/disk/by-label/WD8PRO2  /media/WD8PRO2 ext4  
  defaults0   0
  
  LABEL=WD8PRO2   /Vidéos/WD8PRO2
  ext4defaults 0   0
  
  LABEL=WD8PRO1 /media/WD8PRO1  ext4
defaults0   0
  LABEL=Seagate_4T  /media/Seagate_4T   ext4
defaults,noauto 0   0
  
  trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS
  mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS .
  
- 
- see more details in french : 
https://forum.ubuntu-fr.org/viewtopic.php?id=2073925
+ Exactly same file systeme mounted on same directory , with same trash
+ directory is working fine on ubuntu 22.04

** Description changed:

  Hi , when i delete a file where is in another partition than " / " or
  mounted in /media/ , i obtain this message .
  
  how can i use trash again please ?
  
  iznobe@iznobe-PC:~$ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # 
 
  # / was on /dev/nvme0n1p2 during installation
  UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e /   ext4
noatime,errors=remount-ro   0   1
  
  # /boot/efi was on /dev/nvme0n1p1 during installation
  UUID=C071-9050/boot/efi   
vfatdefaults0   0
  
  # swap was on /dev/sdc3 during installation
  UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap
sw,pri=10   0
  
  # partition de données separée comune aux OS linux
  UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas  ext4
defaults0   0
  LABEL=WD8 /Vidéos/WD8 ext4
defaults0   0
  #/dev/disk/by-label/WD8PRO2  /media/WD8PRO2 ext4  
  defaults0   0
  
  LABEL=WD8PRO2   /Vidéos/WD8PRO2
  ext4defaults 0   0
  
  LABEL=WD8PRO1 /media/WD8PRO1  ext4
defaults0   0
  LABEL=Seagate_4T  /media/Seagate_4T   ext4
defaults,noauto 0   0
  
  trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS
  mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS .
  
  Exactly same file systeme mounted on same directory , with same trash
- directory is working fine on ubuntu 22.04
+ directory is working fine on ubuntu 20.04

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

Title:
  Cannot move file to trash, do you want to delete immediately?" on EXT4
  partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on
  ubuntu 20.04 )

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Hi , when i delete a file where is in another partition than " / " or
  mounted in /media/ , i obtain this message .

  

[Touch-packages] [Bug 1983618] Re: New upstream microrelease 2.5.13

[Sergio Durigan Junior]

** Changed in: openldap (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  New upstream microrelease 2.5.13

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

Bug description:
  [ Impact ]

   * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.13.

  This update includes bugfixes only following the SRU policy exception
  defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

  [ Major Changes ]

   * See the list of bugs fixed in this release here:

  https://lists.openldap.org/hyperkitty/list/openldap-
  annou...@openldap.org/thread/3PLJDVP7QWTRFHC2GPQTGBLEQFCBUZZ2/

  [ Test Plan ]

   * Upstream gitlab pipeline results:
  https://git.openldap.org/openldap/openldap/-/pipelines/4504

   * Upstream "call for testing":
  https://lists.openldap.org/hyperkitty/list/openldap-
  techni...@openldap.org/thread/RXOSXVLKTIDM4XJUA5EZZ42677JXRHYN/

   * As described in the MRE wiki page for OpenLDAP, the test plan is to
  build the package in bileto and make sure that (1) all build-time
  tests pass and (2) all autopkgtest runs (from reverse dependencies)
  also pass.

   * Build log (amd64) confirming that the build-time testsuite has been
  performed and completed successfully: https://launchpad.net/~ci-train-
  ppa-service/+archive/ubuntu/4887/+build/24250107

   * Bileto ticket: https://bileto.ubuntu.com/#/ticket/4895

  [ Where problems could occur ]

   * Upstream tests are always executed during build-time. There are
  many reverse dependencies whose dep8 tests depend on OpenLDAP so the
  coverage is good. Nevertheless, there is always a risk for something
  to break since we are dealing with a microrelease upgrade. Whenever a
  test failure is detected, we will be on top of it and make sure it
  doesn't affect existing users.

  [ Other Info ]

   * This is a reoccurring MRE. See below for links to previous OpenLDAP
  MREs.

   * CVEs fixed by this release:
     - None.

  Current versions in supported releases that got updates:
   openldap | 2.5.12+dfsg-0ubuntu0.22.04.1 | jammy-updates   | source

  Special cases:
  - None.

  Previous MREs for OpenLDAP:
  - https://pad.lv/1977627

  As usual we test and prep from the PPA and then push through
  SRU/Security as applicable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1983618/+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 1983618] Re: New upstream microrelease 2.5.13

[Robie Basak]

** Changed in: openldap (Ubuntu)
   Status: Invalid => Triaged

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

Title:
  New upstream microrelease 2.5.13

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

Bug description:
  [ Impact ]

   * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.13.

  This update includes bugfixes only following the SRU policy exception
  defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

  [ Major Changes ]

   * See the list of bugs fixed in this release here:

  https://lists.openldap.org/hyperkitty/list/openldap-
  annou...@openldap.org/thread/3PLJDVP7QWTRFHC2GPQTGBLEQFCBUZZ2/

  [ Test Plan ]

   * Upstream gitlab pipeline results:
  https://git.openldap.org/openldap/openldap/-/pipelines/4504

   * Upstream "call for testing":
  https://lists.openldap.org/hyperkitty/list/openldap-
  techni...@openldap.org/thread/RXOSXVLKTIDM4XJUA5EZZ42677JXRHYN/

   * As described in the MRE wiki page for OpenLDAP, the test plan is to
  build the package in bileto and make sure that (1) all build-time
  tests pass and (2) all autopkgtest runs (from reverse dependencies)
  also pass.

   * Build log (amd64) confirming that the build-time testsuite has been
  performed and completed successfully: https://launchpad.net/~ci-train-
  ppa-service/+archive/ubuntu/4887/+build/24250107

   * Bileto ticket: https://bileto.ubuntu.com/#/ticket/4895

  [ Where problems could occur ]

   * Upstream tests are always executed during build-time. There are
  many reverse dependencies whose dep8 tests depend on OpenLDAP so the
  coverage is good. Nevertheless, there is always a risk for something
  to break since we are dealing with a microrelease upgrade. Whenever a
  test failure is detected, we will be on top of it and make sure it
  doesn't affect existing users.

  [ Other Info ]

   * This is a reoccurring MRE. See below for links to previous OpenLDAP
  MREs.

   * CVEs fixed by this release:
     - None.

  Current versions in supported releases that got updates:
   openldap | 2.5.12+dfsg-0ubuntu0.22.04.1 | jammy-updates   | source

  Special cases:
  - None.

  Previous MREs for OpenLDAP:
  - https://pad.lv/1977627

  As usual we test and prep from the PPA and then push through
  SRU/Security as applicable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1983618/+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 1990293] [NEW] Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )

[den]

Public bug reported:

Hi , when i delete a file where is in another partition than " / " or
mounted in /media/ , i obtain this message .

how can i use trash again please ?

iznobe@iznobe-PC:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#   
 
# / was on /dev/nvme0n1p2 during installation
UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e   /   ext4
noatime,errors=remount-ro   0   1

# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=C071-9050  /boot/efi   vfat
defaults0   0

# swap was on /dev/sdc3 during installation
UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456   noneswap
sw,pri=10   0

# partition de données separée comune aux OS linux
UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257   /datas  ext4
defaults0   0
LABEL=WD8   /Vidéos/WD8 ext4
defaults0   0
#/dev/disk/by-label/WD8PRO2  /media/WD8PRO2 ext4
defaults0   0

LABEL=WD8PRO2   /Vidéos/WD8PRO2
ext4defaults 0   0

LABEL=WD8PRO1   /media/WD8PRO1  ext4
defaults0   0
LABEL=Seagate_4T/media/Seagate_4T   ext4
defaults,noauto 0   0

trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS
mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS .


see more details in french : 
https://forum.ubuntu-fr.org/viewtopic.php?id=2073925

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Hi , when i delete a file where is in another partition than " / " or
  mounted in /media/ , i obtain this message .
  
  how can i use trash again please ?
  
  iznobe@iznobe-PC:~$ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # 
 
  # / was on /dev/nvme0n1p2 during installation
  UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e /   ext4
noatime,errors=remount-ro   0   1
  
  # /boot/efi was on /dev/nvme0n1p1 during installation
  UUID=C071-9050/boot/efi   
vfatdefaults0   0
  
  # swap was on /dev/sdc3 during installation
  UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap
sw,pri=10   0
  
  # partition de données separée comune aux OS linux
  UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas  ext4
defaults0   0
  LABEL=WD8 /Vidéos/WD8 ext4
defaults0   0
  #/dev/disk/by-label/WD8PRO2  /media/WD8PRO2 ext4  
  defaults0   0
  
- 
- LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4
defaults 0   0
+ LABEL=WD8PRO2   /Vidéos/WD8PRO2
+ ext4defaults 0   0
  
  LABEL=WD8PRO1 /media/WD8PRO1  ext4
defaults0   0
  LABEL=Seagate_4T  /media/Seagate_4T   ext4
defaults,noauto 0   0
  
  trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS
  mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS .
+ 
+ 
+ see more details in french : 
https://forum.ubuntu-fr.org/viewtopic.php?id=2073925

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

Title:
  Cannot move file to trash, do you want to delete immediately?" on EXT4
  partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on
  ubuntu 20.04 )

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Hi , when i delete a file where is in another partition than " / " or
  mounted in /media/ , i obtain this message .

  how can i use trash again please ?

  

[Touch-packages] [Bug 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)

[Sebastien Bacher]

the stacktrace is similar to
https://gitlab.gnome.org/GNOME/gtk/-/issues/3310

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

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0)

Status in apport package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in apport source package in Focal:
  Triaged
Status in gtk+3.0 source package in Focal:
  Confirmed

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+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 1990278] Re: systemd-resolved not included in Ubuntu bootstrap

[Launchpad Bug Tracker]

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

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

Title:
  systemd-resolved not included in Ubuntu bootstrap

Status in systemd package in Ubuntu:
  New

Bug description:
  By default, i.e. with no --variant specified, debootstrap will only
  pull in packages with Priority: required or important. Before the
  systemd-resolved package split, resolved would be included because it
  was shipped with the systemd binary package, which is Priority:
  important. Currently there is no Priority: set on systemd-resolved, so
  it is not included with the deafult Ubuntu bootstrap.

  The systemd-resolved package should have Priority: important to fix
  this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990278/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)

[Brian Murray]

** Tags added: rls-kk-incoming

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0)

Status in apport package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in apport source package in Focal:
  Triaged
Status in gtk+3.0 source package in Focal:
  Confirmed

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+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 1990216] Re: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy

[Simon Chopin]

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

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

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

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

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

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

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

Title:
  backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL
  1.1 with blowfish in OFB or CFB modes" to Jammy

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Confirmed

Bug description:
  OpenSSL upstream implemented a fix for their issue #18359  "OpenSSL 3 cannot 
decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" 
https://github.com/openssl/openssl/issues/18359
  as of libssl3 3.0.4 (and thus it is included in recent libssl3 versions in 
Kinetic).

  Could this fix be backported to libssl3 in Jammy?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1990216/+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 1972939] Re: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes

[Simon Chopin]

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

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

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

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

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

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

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

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

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

Title:
  Jammy tinc  incompatibile with older (e.g. Xenial) tinc nodes

Status in Release Notes for Ubuntu:
  New
Status in openssl package in Ubuntu:
  Fix Released
Status in tinc package in Ubuntu:
  Invalid
Status in openssl source package in Jammy:
  Confirmed
Status in tinc source package in Jammy:
  Invalid

Bug description:
  The tinc included in Jammy (1.0.36-2build1 linked with libssl3) cannot
  connect to tinc nodes running e.g. tinc from Xenial (1.0.26-1).

  (Tinc from Impish, which is also v1.0.36-2 but is linked to libssl1.1,
  can connect to these nodes without problems.)

  The symptom is a log message (on the system running Jammy) during the
  metadata channel negotiation (with debug level set to 5):

  Error during initialisation of cipher from tinc_xenial [...]
  error:0308010C:digital envelope routines::unsupported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1972939/+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 1983665] Re: Problem loading private RSA key with pkcs11 engine, tpm2 module

[Simon Chopin]

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

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

Title:
  Problem loading private RSA key with pkcs11 engine, tpm2 module

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  Problem:

  We have prepared an rsa2048 keypair in tpm2 and would like to access
  it using the pkcs11 engine of OpenSSL which fails as described below.

  Please note that the error messages pasted below look somewhat related
  to https://bugs.launchpad.net/ubuntu/+source/tpm2-tss/+bug/1983160

  Is the fix mentioned in that bug already published or could this be a
  different error?

  Setup:

  The TPM2 device:

  ~# dmesg | grep TPM
  [0.006201] ACPI: TPM2 0x7EB75000 4C (v04 BOCHS  BXPCTPM2 
0001 BXPC 0001)
  [0.006209] ACPI: Reserving TPM2 table memory at [mem 
0x7eb75000-0x7eb7504b]
  [0.372512] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x1, rev-id 1)

  The RSA keypair in TPM2:

  ~# pkcs11-tool --module /usr/lib/x86_64-linux-gnu/pkcs11/libtpm2_pkcs11.so 
--login --list-objects 
  WARNING: Getting tokens from fapi backend failed.
  Using slot 0 with a present token (0x1)
  Logging in to "testlabel".
  Please enter User PIN:  
  Private Key Object; RSA 
label:  
ID: 31323731386436643066616361643434
Usage:  decrypt, sign
Access: sensitive, always sensitive, never extractable, local
Allowed mechanisms: 
RSA-X-509,RSA-PKCS-OAEP,RSA-PKCS,SHA256-RSA-PKCS,SHA384-RSA-PKCS,SHA512-RSA-PKCS,RSA-PKCS-PSS,SHA1-RSA-PKCS-PSS,SHA256-RSA-PKCS-PSS,SHA384-RSA-PKCS-PSS
  Public Key Object; RSA 2048 bits
label:  
ID: 31323731386436643066616361643434
Usage:  encrypt, verify
Access: local

  Here the openssl.cnf:

  openssl_conf = openssl_init
  [openssl_init]
  engines = engine_section
  [engine_section]
  pkcs11 = pkcs11_section
  [pkcs11_section]
  engine_id = pkcs11
  # See also note on dynamic_path = ... below
  MODULE_PATH = /usr/lib/x86_64-linux-gnu/pkcs11/libtpm2_pkcs11.so
  init = 0
  [ req ]
  distinguished_name = req_dn
  string_mask = utf8only
  utf8 = yes
  basicConstraints = critical,CA:FALSE
  subjectKeyIdentifier = hash
  req_extensions = v3_req
  [ v3_req ]
  keyUsage = critical, digitalSignature, keyEncipherment
  extendedKeyUsage = critical, clientAuth
  [ req_dn ]
  commonName = Test Subject

  We test the pcks11 engine availability:

  ~# openssl engine pkcs11 -t
  (pkcs11) pkcs11 engine
   [ available ]

  Now we try using OpenSSL to generate a CSR:

  ~# openssl req -config ./openssl.cnf -verbose -new -engine pkcs11
  -keyform engine -key slot_1-id_38636232383264363035316365623962 -out
  ./test.csr -subj /CN=some.test.name

  Results in an error:

  Engine "pkcs11" set.
  Using configuration from ./openssl.cnf
  WARNING: Getting tokens from fapi backend failed.
  Enter PKCS#11 token PIN for openvpn:
  
ERROR:esys_crypto:src/tss2-esys/esys_crypto_ossl.c:754:iesys_cryptossl_pk_encrypt()
 ErrorCode (0x00070001) Could not create rsa key. 
  ERROR:esys:src/tss2-esys/esys_iutil.c:521:iesys_compute_encrypted_salt() 
During encryption. ErrorCode (0x00070001) 
  
ERROR:esys:src/tss2-esys/api/Esys_StartAuthSession.c:226:Esys_StartAuthSession_Async()
 Error in parameter encryption. ErrorCode (0x00070001) 
  
ERROR:esys:src/tss2-esys/api/Esys_StartAuthSession.c:113:Esys_StartAuthSession()
 Error in async function ErrorCode (0x00070001) 
  ERROR: Esys_StartAuthSession: esapi:Catch all for all errors not otherwise 
specified
  ERROR: Could not start Auth Session with the TPM.
  ERROR: Error unsealing wrapping key
  Login failed
  Login to token failed, returning NULL...
  PKCS11_get_private_key returned NULL
  Could not read private key from 
org.openssl.engine:pkcs11:slot_1-id_38636232383264363035316365623962
  80DB703FD47F:error:0396:digital envelope 
routines:fromdata_init:operation not supported for this 
keytype:../crypto/evp/pmeth_gn.c:354:
  80DB703FD47F:error:4185:PKCS#11 module:ERR_CKR_error:General 
Error:p11_slot.c:245:
  80DB703FD47F:error:1380:engine 
routines:ENGINE_load_private_key:failed loading private 
key:../crypto/engine/eng_pkey.c:79:

  On a sidenote, we do no specify dynamic_path in the openssl.cnf.
  If we set in openssl.cnf:

  dynamic_path = /usr/lib/x86_64-linux-gnu/engines-3/libpkcs11.so

  then we receive a different error:

  ...
  807B8B140C7F:error:1280006A:DSO support routines:dlfcn_bind_func:could 
not bind to the requested symbol 
name:../crypto/dso/dso_dlfcn.c:188:symname(EVP_PKEY_base_id): 
/usr/lib/x86_64-linux-gnu/engines-3/libpkcs11.so: undefined symbol: 
EVP_PKEY_base_id
  ...

  Additional information:

  Release: 22.04.1 LTS (Jammy Jellyfish)

  Packages:

  libengine-pkcs11-openssl:amd640.4.11-1build3   
  libp11-3:amd64

[Touch-packages] [Bug 1990287] [NEW] Two-finger right-click and drag causes additional click

[Coran]

Public bug reported:

I've found a consistent issue since upgrading from 20.04 to 22.04 where 
performing a two-finger tap (to right click) and then quickly performing a 
single tap drag causes a click event on the release of the drag.
One place this manifests is when in a browser, if you two-finger right-click on 
a link, then quickly (must be done quickly) drag the cursor over the menu (eg 
open in new tab). When the finger is released from the drag, it performs a 
click on the menu item.
It also happens in other applications as far as I can tell.
Not a critical bug, but very frustrating as the muscle memory means lots of 
mis-clicks.

I've found the timing between the two-finger tap and one-finger drag
must be small (fraction of a section) to trigger the behaviour.

I've tried installing 22.04 fresh, with no change.

I'm using a Lenovo Thinkpad Carbon X1 G9.

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: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 20 14:16:05 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d5]
InstallationDate: Installed on 2022-09-19 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: LENOVO 20XWCTO1WW
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=ab25a65e-dd77-4b5c-bd5e-75691f427498 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/27/2022
dmi.bios.release: 1.55
dmi.bios.vendor: LENOVO
dmi.bios.version: N32ET79W (1.55 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20XWCTO1WW
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.33
dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
dmi.product.family: ThinkPad X1 Carbon Gen 9
dmi.product.name: 20XWCTO1WW
dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
dmi.product.version: ThinkPad X1 Carbon Gen 9
dmi.sys.vendor: LENOVO
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 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/1990287

Title:
  Two-finger right-click and drag causes additional click

Status in xorg package in Ubuntu:
  New

Bug description:
  I've found a consistent issue since upgrading from 20.04 to 22.04 where 
performing a two-finger tap (to right click) and then quickly performing a 
single tap drag causes a click event on the release of the drag.
  One place this manifests is when in a browser, if you two-finger right-click 
on a link, then quickly (must be done quickly) drag the cursor over the menu 
(eg open in new tab). When the finger is released from the drag, it performs a 
click on the menu item.
  It also happens in other applications as far as I can tell.
  Not a critical bug, but very frustrating as the muscle memory means lots of 
mis-clicks.

  I've found the timing between the two-finger tap and one-finger drag
  must be small (fraction of a section) to trigger the behaviour.

  I've tried installing 22.04 fresh, with no change.

  I'm using a Lenovo Thinkpad Carbon X1 G9.

  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
  

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

[Launchpad Bug Tracker]

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

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

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

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 1990280] Re: apt-get dist-upgrade does not upgrade some packages, only manual dist-upgrade possible by adding affected package to command line

[Julian Andres Klode]

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

The behavior is expected at the moment as part of the phased updates
rework. These packages are not kept back due to broken dependencies, but
due to not yet being available for your system as they are still
phasing.

The behavior you are seeing when adding the libreoffice package
explicitly is correct, the other packages are still kept back. If you
passed the package name to the install command instead, it would be
upgraded. This might or might not be what you expect, it's highly
variable from one person to the next whether they expect install to
respect phased updates or not.

The suboptimal user experience is being tracked in bug 1988819 already,
so I am marking this bug as a duplicate.

** This bug has been marked a duplicate of bug 1988819
   When apt keeps back packages due to phased updates, it should say so

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

Title:
  apt-get dist-upgrade does not upgrade some packages, only manual dist-
  upgrade possible by adding affected package to command line

Status in apt package in Ubuntu:
  New

Bug description:
  Trying to use apt dist-upgrade mode to upgrade some packages results
  in such packages not upgraded. Some packages can be manually upgraded
  w/o problem (adding package name to dist-upgrade command line), others
  result in dependency error only solved by upgrading every other
  package that other package depends on which is annoying. Considering
  an expample below, it shows a wrong behavior and does not upgrade
  properly when it is expected to do that.

  juozas@xubuntu:~$ export LC_ALL=C
  juozas@xubuntu:~$ sudo apt-get --no-install-recommends dist-upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
    linux-headers-5.15.0-46 linux-headers-5.15.0-46-generic 
linux-image-5.15.0-46-generic linux-modules-5.15.0-46-generic 
linux-modules-extra-5.15.0-46-generic
    linux-tools-5.15.0-46 linux-tools-5.15.0-46-generic
  Use 'sudo apt autoremove' to remove them.
  The following packages have been kept back:
    fonts-opensymbol libreoffice libreoffice-base libreoffice-base-core 
libreoffice-base-drivers libreoffice-calc libreoffice-common libreoffice-core
    libreoffice-draw libreoffice-gtk libreoffice-gtk2 libreoffice-gtk3 
libreoffice-help-common libreoffice-help-en-gb libreoffice-help-en-us 
libreoffice-impress
    libreoffice-l10n-en-gb libreoffice-l10n-en-za libreoffice-l10n-lt 
libreoffice-math libreoffice-report-builder-bin libreoffice-style-colibre 
libreoffice-writer
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3 
libuno-salhelpergcc3-3 python3-uno uno-libs-private ure
  0 upgraded, 0 newly installed, 0 to remove and 31 not upgraded.
  juozas@xubuntu:~$ sudo apt-get --no-install-recommends dist-upgrade 
fonts-opensymbol
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
    linux-headers-5.15.0-46 linux-headers-5.15.0-46-generic 
linux-image-5.15.0-46-generic linux-modules-5.15.0-46-generic 
linux-modules-extra-5.15.0-46-generic
    linux-tools-5.15.0-46 linux-tools-5.15.0-46-generic
  Use 'sudo apt autoremove' to remove them.
  The following packages have been kept back:
    libreoffice libreoffice-base libreoffice-base-core libreoffice-base-drivers 
libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw
    libreoffice-gtk libreoffice-gtk2 libreoffice-gtk3 libreoffice-help-common 
libreoffice-help-en-gb libreoffice-help-en-us libreoffice-impress
    libreoffice-l10n-en-gb libreoffice-l10n-en-za libreoffice-l10n-lt 
libreoffice-math libreoffice-report-builder-bin libreoffice-style-colibre 
libreoffice-writer
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3 
libuno-salhelpergcc3-3 python3-uno uno-libs-private ure
  The following packages will be upgraded:
    fonts-opensymbol
  1 upgraded, 0 newly installed, 0 to remove and 30 not upgraded.
  Need to get 102 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n]
  Get:1 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 
fonts-opensymbol all 2:102.12+LibO7.3.6-0ubuntu0.22.04.1 [102 kB]
  Fetched 102 kB in 0s (340 kB/s)
  (Reading database ... 332342 files and directories currently installed.)
  Preparing to unpack 
.../fonts-opensymbol_2%3a102.12+LibO7.3.6-0ubuntu0.22.04.1_all.deb ...
  Unpacking fonts-opensymbol (2:102.12+LibO7.3.6-0ubuntu0.22.04.1) over 
(2:102.12+LibO7.3.5-0ubuntu0.22.04.1) ...
  

[Touch-packages] [Bug 1990187] Re: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before

[Heinrich Schuchardt]

** Tags added: foundations-todo

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

Title:
  systemd-resolved recommends libnss-resolve in kinetic, pulls it into
  minimal system where it was explicitly excluded before

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling
  it into the ubuntu-minimal seed.

  In the past we briefly had libnss-resolve seeded (between xenial and
  bionic LTSes but not in any LTS) but it was removed because:

   - it was redundant; /etc/resolv.conf was consistent and correct.
   - its presence could mask wrong DNS configuration resulting in 
difficult-to-debug differences in behavior between applications that did use 
nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 
binaries that could not use nss_resolved because it was not installed; 
statically-linked go implementations that parsed /etc/resolve.conf directly and 
did not load NSS modules)

  This new recommends was noticed specifically because of some broken
  kinetic container images where /etc/resolv.conf was broken (empty) and
  *some* applications still worked via nss but others failed by trying
  to use the DNS protocol directly.  (I.e.: 2nd point above)

  I believe systemd-resolved should drop its recommends on libnss-
  resolve for Ubuntu.

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

[Nick Rosbrook]

Thanks, Onuh. It looks like you have overridden the systemd-
pstore.service file with one in /etc/systemd/system/systemd-
pstore.service, so the one shipped by the systemd package
(/lib/systemd/system/systemd-pstore.service) is not being used. Please
remove the one in /etc/, and run systemctl daemon-reload. That should
resolve your problem.

-- 
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:
  In Progress
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 1990280] [NEW] apt-get dist-upgrade does not upgrade some packages, only manual dist-upgrade possible by adding affected package to command line

[Juozas Pocius]

Public bug reported:

Trying to use apt dist-upgrade mode to upgrade some packages results in
such packages not upgraded. Some packages can be manually upgraded w/o
problem (adding package name to dist-upgrade command line), others
result in dependency error only solved by upgrading every other package
that other package depends on which is annoying. Considering an expample
below, it shows a wrong behavior and does not upgrade properly when it
is expected to do that.

juozas@xubuntu:~$ export LC_ALL=C
juozas@xubuntu:~$ sudo apt-get --no-install-recommends dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  linux-headers-5.15.0-46 linux-headers-5.15.0-46-generic 
linux-image-5.15.0-46-generic linux-modules-5.15.0-46-generic 
linux-modules-extra-5.15.0-46-generic
  linux-tools-5.15.0-46 linux-tools-5.15.0-46-generic
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
  fonts-opensymbol libreoffice libreoffice-base libreoffice-base-core 
libreoffice-base-drivers libreoffice-calc libreoffice-common libreoffice-core
  libreoffice-draw libreoffice-gtk libreoffice-gtk2 libreoffice-gtk3 
libreoffice-help-common libreoffice-help-en-gb libreoffice-help-en-us 
libreoffice-impress
  libreoffice-l10n-en-gb libreoffice-l10n-en-za libreoffice-l10n-lt 
libreoffice-math libreoffice-report-builder-bin libreoffice-style-colibre 
libreoffice-writer
  libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3 
libuno-salhelpergcc3-3 python3-uno uno-libs-private ure
0 upgraded, 0 newly installed, 0 to remove and 31 not upgraded.
juozas@xubuntu:~$ sudo apt-get --no-install-recommends dist-upgrade 
fonts-opensymbol
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  linux-headers-5.15.0-46 linux-headers-5.15.0-46-generic 
linux-image-5.15.0-46-generic linux-modules-5.15.0-46-generic 
linux-modules-extra-5.15.0-46-generic
  linux-tools-5.15.0-46 linux-tools-5.15.0-46-generic
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
  libreoffice libreoffice-base libreoffice-base-core libreoffice-base-drivers 
libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw
  libreoffice-gtk libreoffice-gtk2 libreoffice-gtk3 libreoffice-help-common 
libreoffice-help-en-gb libreoffice-help-en-us libreoffice-impress
  libreoffice-l10n-en-gb libreoffice-l10n-en-za libreoffice-l10n-lt 
libreoffice-math libreoffice-report-builder-bin libreoffice-style-colibre 
libreoffice-writer
  libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3 
libuno-salhelpergcc3-3 python3-uno uno-libs-private ure
The following packages will be upgraded:
  fonts-opensymbol
1 upgraded, 0 newly installed, 0 to remove and 30 not upgraded.
Need to get 102 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 
fonts-opensymbol all 2:102.12+LibO7.3.6-0ubuntu0.22.04.1 [102 kB]
Fetched 102 kB in 0s (340 kB/s)
(Reading database ... 332342 files and directories currently installed.)
Preparing to unpack 
.../fonts-opensymbol_2%3a102.12+LibO7.3.6-0ubuntu0.22.04.1_all.deb ...
Unpacking fonts-opensymbol (2:102.12+LibO7.3.6-0ubuntu0.22.04.1) over 
(2:102.12+LibO7.3.5-0ubuntu0.22.04.1) ...
Setting up fonts-opensymbol (2:102.12+LibO7.3.6-0ubuntu0.22.04.1) ...
Processing triggers for fontconfig (2.13.1-4.2ubuntu5) ...
juozas@xubuntu:~$ sudo apt-get --no-install-recommends dist-upgrade libreoffice
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... 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:
 libreoffice-base : Depends: libreoffice-core (= 1:7.3.5-0ubuntu0.22.04.1) but 
1:7.3.6-0ubuntu0.22.04.1 is to be installed
 libreoffice-base-core : Depends: libreoffice-core (= 1:7.3.5-0ubuntu0.22.04.1) 
but 1:7.3.6-0ubuntu0.22.04.1 is to be installed or
  libreoffice-core-nogui (= 
1:7.3.5-0ubuntu0.22.04.1) but it is not installable
 libreoffice-calc : Depends: libreoffice-core (= 1:7.3.5-0ubuntu0.22.04.1) but 
1:7.3.6-0ubuntu0.22.04.1 is to be installed
 libreoffice-core : Breaks: libreoffice-base (< 1:7.3.6-0ubuntu0.22.04.1) but 
1:7.3.5-0ubuntu0.22.04.1 is to be installed
Breaks: libreoffice-calc (< 1:7.3.6-0ubuntu0.22.04.1) but 

[Touch-packages] [Bug 1989969] Re: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el

[Launchpad Bug Tracker]

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

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

Title:
  autopkgtest TEST-36-NUMAPOLICY failure on ppc64el

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  In Kinetic, TEST-36-NUMAPOLICY from upstream-2 fails very frequently
  on ppc64el. See for example:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  kinetic/kinetic/ppc64el/s/systemd/20220908_195425_da51e@/log.gz, and
  the full kinetic ppc64el history:
  https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el.

  It has passed on very few occasions. I have tried to debug this
  locally but have gotten very little useful information (i.e. not
  enough to open an upstream bug).

  For now it is probably best to denylist this test on ppc64el.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989969/+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 1990187] Re: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before

[Launchpad Bug Tracker]

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

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

Title:
  systemd-resolved recommends libnss-resolve in kinetic, pulls it into
  minimal system where it was explicitly excluded before

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling
  it into the ubuntu-minimal seed.

  In the past we briefly had libnss-resolve seeded (between xenial and
  bionic LTSes but not in any LTS) but it was removed because:

   - it was redundant; /etc/resolv.conf was consistent and correct.
   - its presence could mask wrong DNS configuration resulting in 
difficult-to-debug differences in behavior between applications that did use 
nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 
binaries that could not use nss_resolved because it was not installed; 
statically-linked go implementations that parsed /etc/resolve.conf directly and 
did not load NSS modules)

  This new recommends was noticed specifically because of some broken
  kinetic container images where /etc/resolv.conf was broken (empty) and
  *some* applications still worked via nss but others failed by trying
  to use the DNS protocol directly.  (I.e.: 2nd point above)

  I believe systemd-resolved should drop its recommends on libnss-
  resolve for Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990187/+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 1990278] [NEW] systemd-resolved not included in Ubuntu bootstrap

[Nick Rosbrook]

Public bug reported:

By default, i.e. with no --variant specified, debootstrap will only pull
in packages with Priority: required or important. Before the systemd-
resolved package split, resolved would be included because it was
shipped with the systemd binary package, which is Priority: important.
Currently there is no Priority: set on systemd-resolved, so it is not
included with the deafult Ubuntu bootstrap.

The systemd-resolved package should have Priority: important to fix
this.

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

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

Title:
  systemd-resolved not included in Ubuntu bootstrap

Status in systemd package in Ubuntu:
  New

Bug description:
  By default, i.e. with no --variant specified, debootstrap will only
  pull in packages with Priority: required or important. Before the
  systemd-resolved package split, resolved would be included because it
  was shipped with the systemd binary package, which is Priority:
  important. Currently there is no Priority: set on systemd-resolved, so
  it is not included with the deafult Ubuntu bootstrap.

  The systemd-resolved package should have Priority: important to fix
  this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990278/+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 1990187] Re: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before

[Nick Rosbrook]

systemd-resolved was previously shipped in the systemd package, and
became a separate binary package during the kinetic cycle. This package
provides the default DNS resolver for Ubuntu, so we want it in ubuntu-
minimal.

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

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

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

Title:
  systemd-resolved recommends libnss-resolve in kinetic, pulls it into
  minimal system where it was explicitly excluded before

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling
  it into the ubuntu-minimal seed.

  In the past we briefly had libnss-resolve seeded (between xenial and
  bionic LTSes but not in any LTS) but it was removed because:

   - it was redundant; /etc/resolv.conf was consistent and correct.
   - its presence could mask wrong DNS configuration resulting in 
difficult-to-debug differences in behavior between applications that did use 
nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 
binaries that could not use nss_resolved because it was not installed; 
statically-linked go implementations that parsed /etc/resolve.conf directly and 
did not load NSS modules)

  This new recommends was noticed specifically because of some broken
  kinetic container images where /etc/resolv.conf was broken (empty) and
  *some* applications still worked via nss but others failed by trying
  to use the DNS protocol directly.  (I.e.: 2nd point above)

  I believe systemd-resolved should drop its recommends on libnss-
  resolve for Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990187/+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 1962454] Re: Oops pages show wrong time window in JournalErrors

[Heinrich Schuchardt]

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

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

Title:
  Oops pages show wrong time window in JournalErrors

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  New
Status in apport source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  Oops pages show wrong time window in JournalErrors. For example, I
  just experienced a crash at:

    Feb 28 17:31:12

  And the JournalErrors entries are:

    Feb 28 17:31:30 - Feb 28 17:31:41

  So don't relate to the crash.

  [Test Plan]

  1. Find a recent crash report from a relevant Ubuntu release on
  https://errors.ubuntu.com/ If you're looking at
  https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick
  a relevant instance from the Occurrences list.

  2. Now you're on a page starting with https://errors.ubuntu.com/oops/
  look at ApportVersion and verify that apport is a recent enough
  version to contain the proposed fix. If not then go to step 1.

  3. Verify the Date field falls within the time range of the
  JournalErrors entries.

  Step 3 might fail in the case of there being no system log entries
  from around the time of the crash. That does not necessarily mean the
  test plan has failed. Go to step 1 and pick a different crash.

  Prior to the fix you would almost never find oops pages that would
  pass the test. After the fix you should find many/most oops pages do
  pass the test.

  [Where problems could occur]

  Worst case - in any part of the bug reporting/collection procedure,
  since that is what's changing.

  [Other Info]

  Due to the huge amount of broken autopkgtest tests, the diff for the
  SRUs are bigger than desired. The individual commits in
  https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are
  probably easier to review.

  * jammy SRU: 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb
  * focal SRU: 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1962454/+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 1990187] Re: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before

[Heinrich Schuchardt]

Jammy's systemd 249.11-0ubuntu3.6 does not provide package systemd-resolved at 
all.
Could we drop systemd-resolved from ubuntu-minimal?

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

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

Title:
  systemd-resolved recommends libnss-resolve in kinetic, pulls it into
  minimal system where it was explicitly excluded before

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling
  it into the ubuntu-minimal seed.

  In the past we briefly had libnss-resolve seeded (between xenial and
  bionic LTSes but not in any LTS) but it was removed because:

   - it was redundant; /etc/resolv.conf was consistent and correct.
   - its presence could mask wrong DNS configuration resulting in 
difficult-to-debug differences in behavior between applications that did use 
nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 
binaries that could not use nss_resolved because it was not installed; 
statically-linked go implementations that parsed /etc/resolve.conf directly and 
did not load NSS modules)

  This new recommends was noticed specifically because of some broken
  kinetic container images where /etc/resolv.conf was broken (empty) and
  *some* applications still worked via nss but others failed by trying
  to use the DNS protocol directly.  (I.e.: 2nd point above)

  I believe systemd-resolved should drop its recommends on libnss-
  resolve for Ubuntu.

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