[Touch-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8

2024-03-24 Thread John Johansen
So what I think is going on from a first pass look at this is that

We are seeing a change in kernel behavior around exec. The 6.8 has a
known change here, that doesn't normally trigger because unconfined is
delegating access into the profile. However in the lxd case, unconfined
can is not delegating access it the profile needs access to the
application.

the accompanying patch should fix the issue, and does not actually grant
anymore permission that was already required, it was just being
delegated in by unconfined.


** Patch added: "apparmor-add-execmap.patch"
   
https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2058866/+attachment/5758964/+files/apparmor-add-execmap.patch

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

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu8

Status in apparmor package in Ubuntu:
  New
Status in cups-browsed package in Ubuntu:
  New

Bug description:
  cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
  via an autopkgtest), early enough that LD_DEBUG=all gives no output.
  A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
  executable ran, so 8 was uploaded to try to fix this.  But the
  executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
  browsed and segfaults when invoked as /usr/sbin/cups-browsed.

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


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


Re: [Touch-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8

2024-03-24 Thread Steve Langasek
On Mon, Mar 25, 2024 at 05:16:57AM -, John Johansen wrote:
> Do we know if there is a difference in the kernel between the runs?

> The 2.0.0.0~0ubuntu3 autopackage run log I was pointed at was on a
>   Linux 5.4.0-170-generic #188-Ubuntu

> Do we know what kernel that 2.0.0-0ubuntu7 is failing on? There was a
> change to when security checks were made in on the exec path, this
> particular denial makes me wonder if we are seeing an artifact of that
> here.

All logs on https://autopkgtest.ubuntu.com/packages/c/cups-browsed/noble/armhf
should include kernel information.

Latest 2.0.0-0ubuntu8 failure has:

211s autopkgtest [22:10:53]: testbed running kernel: Linux
5.15.0-101-generic #111-Ubuntu SMP Wed Mar 6 18:01:01 UTC 2024

Last successful 2.0.0-0ubuntu3 log has:

349s autopkgtest [18:43:33]: testbed running kernel: Linux
5.4.0-170-generic #188-Ubuntu SMP Wed Jan 10 09:51:10 UTC 2024

But that was a retry of the release version of the package AFTER things
started failing;
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/c/cups-browsed/20240322_173402_07be9@/log.gz
is earlier and has:

351s autopkgtest [17:30:50]: testbed running kernel: Linux
5.4.0-170-generic #188-Ubuntu SMP Wed Jan 10 09:51:10 UTC 2024

so it's not a kernel difference.

It appears to be a genuine change in the binaries when built with new
toolchain that causes them to have a new mmap that wasn't there before?

If I aa-enforce and run strace, I see:

execve("/usr/sbin/cups-browsed", ["cups-browsed"], 0xffa82a54 /* 12 vars
*/) = -1 EACCES (Permission denied)

so this failure happens before we even reach the executable?

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

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu8

Status in apparmor package in Ubuntu:
  New
Status in cups-browsed package in Ubuntu:
  New

Bug description:
  cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
  via an autopkgtest), early enough that LD_DEBUG=all gives no output.
  A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
  executable ran, so 8 was uploaded to try to fix this.  But the
  executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
  browsed and segfaults when invoked as /usr/sbin/cups-browsed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8

2024-03-24 Thread John Johansen
Do we know if there is a difference in the kernel between the runs?

The 2.0.0.0~0ubuntu3 autopackage run log I was pointed at was on a
  Linux 5.4.0-170-generic #188-Ubuntu

Do we know what kernel that 2.0.0-0ubuntu7 is failing on? There was a
change to when security checks were made in on the exec path, this
particular denial makes me wonder if we are seeing an artifact of that
here.

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

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu8

Status in apparmor package in Ubuntu:
  New
Status in cups-browsed package in Ubuntu:
  New

Bug description:
  cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
  via an autopkgtest), early enough that LD_DEBUG=all gives no output.
  A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
  executable ran, so 8 was uploaded to try to fix this.  But the
  executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
  browsed and segfaults when invoked as /usr/sbin/cups-browsed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

2024-03-24 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

2024-03-24 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 868279] Re: curl crashed with SIGSEGV in Curl_do()

2024-03-24 Thread Launchpad Bug Tracker
[Expired for curl (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  curl crashed with SIGSEGV in Curl_do()

Status in curl package in Ubuntu:
  Expired

Bug description:
  something wrong

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: curl 7.21.6-3ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  Date: Wed Oct  5 14:30:11 2011
  ExecutablePath: /usr/bin/curl
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110901)
  ProcCmdline: curl -v smtps://post.teletrade.ru -o /dev/null
  SegvAnalysis:
   Segfault happened at: 0x7f824e7d31ad:cmpb   $0x3c,(%rdx)
   PC (0x7f824e7d31ad) ok
   source "$0x3c" ok
   destination "(%rdx)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: curl
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcurl.so.4
   Curl_do () from /usr/lib/x86_64-linux-gnu/libcurl.so.4
   ?? () from /usr/lib/x86_64-linux-gnu/libcurl.so.4
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
  Title: curl crashed with SIGSEGV in Curl_do()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/868279/+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 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

2024-03-24 Thread Bug Watch Updater
** Changed in: gobject-introspection (Debian)
   Status: New => Fix Released

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Fix Committed
Status in gobject-introspection package in Debian:
  Fix Released

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+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 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8

2024-03-24 Thread John Johansen
** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu8

Status in apparmor package in Ubuntu:
  New
Status in cups-browsed package in Ubuntu:
  New

Bug description:
  cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
  via an autopkgtest), early enough that LD_DEBUG=all gives no output.
  A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
  executable ran, so 8 was uploaded to try to fix this.  But the
  executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
  browsed and segfaults when invoked as /usr/sbin/cups-browsed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 1970069] Re: Annoying boot messages interfering with splash screen

2024-03-24 Thread Daniel van Vugt
That commit is not meant to reflect the outcome of discussions that
happened after it (comment #93). It's just an intermediate "UNRELEASED"
commit reflecting intermediate development.

My intent with shared repos like this is to show what is being worked on
before anything is released to the archive. The tags still accurately
reflect what reached or was proposed to the archive.

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

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in plymouth package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
    quiet splash loglevel=3 fastboot

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8

2024-03-24 Thread Steve Langasek
cupsd 2.0.0-0ubuntu8 contains no sourceful changes vs 2.0.0-0ubuntu3 in
noble release; these are no-change rebuilds only.

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

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu8

Status in apparmor package in Ubuntu:
  New
Status in cups-browsed package in Ubuntu:
  New

Bug description:
  cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
  via an autopkgtest), early enough that LD_DEBUG=all gives no output.
  A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
  executable ran, so 8 was uploaded to try to fix this.  But the
  executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
  browsed and segfaults when invoked as /usr/sbin/cups-browsed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8

2024-03-24 Thread Steve Langasek
Reproducible on amd64.

[6037055.006277] audit: type=1400 audit(1711335561.053:35916):
apparmor="DENIED" operation="file_mmap" class="file"
namespace="root//lxd-noble_"
profile="/usr/sbin/cups-browsed" name="/usr/sbin/cups-browsed"
pid=788055 comm="cups-browsed" requested_mask="r" denied_mask="r"
fsuid=1000110 ouid=100

So this is a regression wrt cups-browsed running under apparmor in a
container, and not specific to armhf.

** Changed in: cups-browsed (Ubuntu)
   Importance: Undecided => Critical

** Changed in: cups-browsed (Ubuntu)
 Assignee: Steve Langasek (vorlon) => (unassigned)

** Tags added: time-t

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

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

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu8

Status in apparmor package in Ubuntu:
  New
Status in cups-browsed package in Ubuntu:
  New

Bug description:
  cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
  via an autopkgtest), early enough that LD_DEBUG=all gives no output.
  A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
  executable ran, so 8 was uploaded to try to fix this.  But the
  executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
  browsed and segfaults when invoked as /usr/sbin/cups-browsed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8

2024-03-24 Thread Steve Langasek
[1724567.629003] audit: type=1400 audit(1711133926.877:813):
apparmor="DENIED" operation="file_mmap" class="file"
namespace="root//lxd-noble-armhf_"
profile="/usr/sbin/cups-browsed" name="/usr/sbin/cups-browsed"
pid=876865 comm="cups-browsed" requested_mask="rm" denied_mask="rm"
fsuid=1000110 ouid=100


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

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

Title:
  proposed-migration for cups-browsed 2.0.0-0ubuntu8

Status in apparmor package in Ubuntu:
  New
Status in cups-browsed package in Ubuntu:
  New

Bug description:
  cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected
  via an autopkgtest), early enough that LD_DEBUG=all gives no output.
  A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the
  executable ran, so 8 was uploaded to try to fix this.  But the
  executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups-
  browsed and segfaults when invoked as /usr/sbin/cups-browsed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled

2024-03-24 Thread Matthew Ruffell
Thank you for the help sorting autopkgtests Mauricio.

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

Title:
  ls -l triggers mount of autofs shares when --ghost option is present
  or browse_mode is enabled

Status in coreutils package in Ubuntu:
  Fix Released
Status in coreutils source package in Jammy:
  Fix Committed
Status in coreutils package in Fedora:
  Fix Released

Bug description:
  [Impact]

  Issuing a 'ls -l' or a 'stat' on an autofs share when you have set
  --ghost in the auto.master file, or browse_mode=yes in autofs.conf
  will lead to the shares being mounted, when they didn't previously.

  Disks / shares may not be present and the mounts may fail, leading to
  errors in your output.

  This is a behaviour change in autofs 8.32, which occurred in the
  transition to using statx() instead of stat()/lstat() in previous
  releases.

  There doesn't seem to be any workarounds, apart from not running a 'ls
  -l' in your autofs share directory.

  [Testcase]

  Start two Jammy VMs. One will be a NFS server, the other, the client.

  NFS server:

  Server VM:
  $ sudo hostnamectl set-hostname jammy-nfs-server
  $ sudo apt update && sudo apt upgrade -y
  $ sudo apt install nfs-kernel-server
  $ sudo mkdir /export
  $ sudo mkdir /export/users
  $ sudo vi /etc/exports # add the following lines:
  /export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync)
  /export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync)
  $ sudo systemctl restart nfs-server.service

  AutoFS Client:
  $ sudo apt update
  $ sudo apt install autofs
  $ sudo vim /etc/autofs.conf
  browse_mode = yes
  $ sudo mkdir /mnt2
  $ sudo vim /etc/auto.master
  /mnt2 /etc/auto.indirect
  $ sudo vim /etc/auto.indirect
  export 192.168.122.18:/export
  export-missing 192.168.122.18:/export-missing
  $ sudo reboot
  $ cd /mnt2
  $ ls -l
  ls: cannot access 'export-missing': No such file or directory
  total 4
  drwxr-xr-x 3 root root 4096 Feb 12 21:48 export
  d? ? ??   ?? export-missing
  $ mount -l | grep /mnt2
  /etc/auto.indirect on /mnt2 type autofs 
(rw,relatime,fd=6,pgrp=634,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=21561)
  192.168.122.18:/export on /mnt2/export type nfs 
(rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.122.18,mountvers=3,mountport=35786,mountproto=udp,local_lock=none,addr=192.168.122.18)

  We see the mount for export occurred, and export-missing was
  attempted, but it was either bogus or the disk was not present,
  leading to a "No such file or directory" error.

  There are test packages available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf378489-test

  If you install them, this is what should occur:

  $ ls -l
  total 0
  drwxr-xr-x 2 root root 0 Feb 12 22:01 export
  drwxr-xr-x 2 root root 0 Feb 12 22:01 export-missing
  $ mount -l | grep /mnt2
  /etc/auto.indirect on /mnt2 type autofs 
(rw,relatime,fd=6,pgrp=636,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=18346)

  No mounts happen, and no errors either.

  [Where problems could occur]

  We are changing the behaviour of core utilities, ls and stat, such
  that they no longer attempt to mount autofs shares when --ghost option
  is present or browse_mode is enabled.

  This is the intended behaviour in the first place, and has been this
  way for at least a decade prior, and was changed to return to this
  behaviour shortly after the release of coreutils that introduced
  statx() that caused automounts to occur.

  It is unlikely any system administrators are relying on the behaviour
  found in jammy in any scripts or day to day operations that would be
  adversely affected by the change. The worst case scenario is that a
  user doing an 'ls -l' on an unmounted disk finds the mount doesn't
  automatically occur, and they have to attach the disk and issue the
  mount themselves.

  If a regression were to occur, it would be limited to the ls and stat
  commands, specifically when listing directories linked to autofs
  mountpoints.

  [Other info]

  The automount behaviour change was introduced upstream in version
  8.32, with the introduction of the statx() call. This means only Jammy
  is affected.

  It was quickly reverted back to how it was originally in version 9.1,
  which is already available in Mantic and onward.

  The commits that solve the issue are:

  commit 85c975df2c25bd799370b04bb294e568e001102f
  From: Rohan Sable 
  Date: Mon, 7 Mar 2022 14:14:13 +
  Subject: ls: avoid triggering automounts
  Link: 
https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2

  commit 92cb8427c537f37edd43c5cef1909585201372ab 
  From: Pádraig Brady 
  Date: Mon, 7 Mar 2022 23:29:20 +
  Subject: stat: only automount with 

[Touch-packages] [Bug 2053228] Re: software-properties-gtk does not start

2024-03-24 Thread corrado venturini
Using old format sources is a dirty trick, this bug affects Deb822
format sources.

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

Title:
  software-properties-gtk does not start

Status in software-properties package in Ubuntu:
  Fix Committed

Bug description:
  On a new install with the new format sources.list software-properties-gtk 
does not start:
  corrado@corrado-n4-nn-0215:~$ software-properties-gtk
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file
  corrado@corrado-n4-nn-0215:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.42
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:07:43 2024
  InstallationDate: Installed on 2024-02-15 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low

2024-03-24 Thread Julian Andres Klode
Uploaded procps with the file; leaving gamemode task open because maybe
dynamic enhancements there still make some sense in 24.10

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

Title:
  Some Games are crashing linked to a vm_max_map_count too low

Status in gamemode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in procps package in Ubuntu:
  Fix Committed

Bug description:
  Hello there,

  I submit this request to improve the gaming experience in ubuntu for all 
users. 
  Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just 
not starting because the vm_max_map_count is locked at 65530. If we change this 
value to a value > 20, all games are working well and there is no bug 
linked to maps. 

  Some others distribution like Fedora or Pop OS, have already made the
  change few month before.

  It's time to Ubuntu to makes the change also.

  Thanks in advance for applying this request.

  How to make this change :

  One file to modify : 
  /etc/sysctl.conf
  Add this line :
  vm.max_map_count=2147483642
  Save
  Reboot and enjoy

  Best Regards
  Vinceff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low

2024-03-24 Thread Julian Andres Klode
I'm agreeing with desktop in following Fedora to bump to 1048576, the
precedence makes this safe, and this I consider this a bug fix for
crashing software and not a feature request.

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: procps (Ubuntu)
   Status: Triaged => In Progress

** Changed in: procps (Ubuntu)
   Status: In Progress => Fix Committed

** No longer affects: ubuntu

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

Title:
  Some Games are crashing linked to a vm_max_map_count too low

Status in gamemode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in procps package in Ubuntu:
  Fix Committed

Bug description:
  Hello there,

  I submit this request to improve the gaming experience in ubuntu for all 
users. 
  Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just 
not starting because the vm_max_map_count is locked at 65530. If we change this 
value to a value > 20, all games are working well and there is no bug 
linked to maps. 

  Some others distribution like Fedora or Pop OS, have already made the
  change few month before.

  It's time to Ubuntu to makes the change also.

  Thanks in advance for applying this request.

  How to make this change :

  One file to modify : 
  /etc/sysctl.conf
  Add this line :
  vm.max_map_count=2147483642
  Save
  Reboot and enjoy

  Best Regards
  Vinceff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+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 2058691] Re: No sound card detected on the Dell xps 16 2024 (9640)

2024-03-24 Thread Moritz
After extracting the intel/sof-ipc4/mtl/sof-mtl.ri.zst and intel/sof-
ace-tplg/sof-mtl-rt711-4ch.tplg.zst and placing them in the same folder,
the following dmesg output is created:

snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 
0x040380
snd_hda_intel :00:1f.3: SoundWire enabled on CannonLake+ platform, using 
SOF driver
sof-audio-pci-intel-mtl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040380
sof-audio-pci-intel-mtl :00:1f.3: SoundWire enabled on CannonLake+ 
platform, using SOF driver
sof-audio-pci-intel-mtl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040380
sof-audio-pci-intel-mtl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
sof-audio-pci-intel-mtl :00:1f.3: use msi interrupt mode
sof-audio-pci-intel-mtl :00:1f.3: DMICs detected in NHLT tables: 0
sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4
sof-audio-pci-intel-mtl :00:1f.3: Firmware paths/files for ipc type 1:
sof-audio-pci-intel-mtl :00:1f.3:  Firmware file: 
intel/sof-ipc4/mtl/sof-mtl.ri
sof-audio-pci-intel-mtl :00:1f.3:  Firmware lib path: intel/sof-ipc4-lib/mtl
sof-audio-pci-intel-mtl :00:1f.3:  Topology file: 
intel/sof-ace-tplg/sof-mtl-rt711.tplg
sof-audio-pci-intel-mtl :00:1f.3: Loaded firmware library: ADSPFW, version: 
2.8.1.1
cs42l43 sdw:0:0:01fa:4243:01: supply vdd-p not found, using dummy regulator
cs42l43 sdw:0:0:01fa:4243:01: supply vdd-d not found, using dummy regulator
cs42l43 sdw:0:0:01fa:4243:01: supply vdd-a not found, using dummy regulator
cs42l43 sdw:0:0:01fa:4243:01: supply vdd-io not found, using dummy regulator
cs42l43 sdw:0:0:01fa:4243:01: supply vdd-cp not found, using dummy regulator
cs35l56 sdw:0:2:01fa:3556:01:2: supply VDD_P not found, using dummy regulator
cs35l56 sdw:0:2:01fa:3556:01:2: supply VDD_IO not found, using dummy regulator
cs35l56 sdw:0:2:01fa:3556:01:2: supply VDD_A not found, using dummy regulator
cs35l56 sdw:0:2:01fa:3556:01:3: supply VDD_P not found, using dummy regulator
cs35l56 sdw:0:2:01fa:3556:01:3: supply VDD_IO not found, using dummy regulator
cs35l56 sdw:0:2:01fa:3556:01:3: supply VDD_A not found, using dummy regulator
cs35l56 sdw:0:3:01fa:3556:01:0: supply VDD_P not found, using dummy regulator
cs35l56 sdw:0:3:01fa:3556:01:0: supply VDD_IO not found, using dummy regulator
cs35l56 sdw:0:3:01fa:3556:01:0: supply VDD_A not found, using dummy regulator
cs35l56 sdw:0:3:01fa:3556:01:1: supply VDD_P not found, using dummy regulator
cs35l56 sdw:0:3:01fa:3556:01:1: supply VDD_IO not found, using dummy regulator
cs35l56 sdw:0:3:01fa:3556:01:1: supply VDD_A not found, using dummy regulator
sof-audio-pci-intel-mtl :00:1f.3: Booted firmware version: 2.8.1.1
cs42l43 sdw:0:0:01fa:4243:01: devid: 0x042a43, rev: 0xa1, otp: 0x03
cs35l56 sdw:0:2:01fa:3556:01:3: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 
(patched=0)
cs35l56 sdw:0:3:01fa:3556:01:1: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 
(patched=0)
cs35l56 sdw:0:2:01fa:3556:01:2: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 
(patched=0)
cs35l56 sdw:0:3:01fa:3556:01:0: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 
(patched=0)
cs42l43 sdw:0:0:01fa:4243:01: Slave 6 state check1: UNATTACHED, status was 1
cs35l56 sdw:0:2:01fa:3556:01:3: Slave 1 state check1: UNATTACHED, status was 1
cs35l56 sdw:0:2:01fa:3556:01:2: Slave 2 state check1: UNATTACHED, status was 1
cs35l56 sdw:0:3:01fa:3556:01:1: Slave 1 state check1: UNATTACHED, status was 1
cs35l56 sdw:0:3:01fa:3556:01:0: Slave 2 state check1: UNATTACHED, status was 1
Adding alias for supply vdd-amp,(null) -> vdd-amp,sdw:0:0:01fa:4243:01
sof-audio-pci-intel-mtl :00:1f.3: Topology: ABI 3:29:0 Kernel ABI 3:23:0
sof-audio-pci-intel-mtl :00:1f.3: error: can't connect DAI 
dai-copier.DMIC.dmic01.capture stream dmic01
sof-audio-pci-intel-mtl :00:1f.3: error: failed to add widget id 0 type 28 
name : dai-copier.DMIC.dmic01.capture stream dmic01
sof_sdw sof_sdw: ASoC: failed to load widget dai-copier.DMIC.dmic01.capture
sof_sdw sof_sdw: ASoC: topology: could not load header: -22
sof-audio-pci-intel-mtl :00:1f.3: error: tplg component load failed -22
sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP topology -22
sof-audio-pci-intel-mtl :00:1f.3: ASoC: error at snd_soc_component_probe on 
:00:1f.3: -22
sof_sdw sof_sdw: ASoC: failed to instantiate card -22
sof_sdw sof_sdw: error -EINVAL: snd_soc_register_card failed -22
sof_sdw: probe of sof_sdw failed with error -22

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

Title:
  No sound card detected on the Dell xps 16 2024 (9640)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sound card is not detected on the Dell XPS 16 2024 (9640). A
  Cirrus Logic CS42L43 card is used which apparently got support in
  Linux 6.6

  

[Touch-packages] [Bug 2058691] Re: No sound card detected on the Dell xps 16 2024 (9640)

2024-03-24 Thread Moritz
During boot, dmesg reports that the intel/sof-ipc4/mtl/sof-mtl.ri and
intel/sof-ace-tplg/sof-mtl-rt711.tplg files can not be found. However,
the corresponding files are there but packaged with zst file endings.

sof-audio-pci-intel-mtl :00:1f.3: use msi interrupt mode
sof-audio-pci-intel-mtl :00:1f.3: DMICs detected in NHLT tables: 0
sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4
sof-audio-pci-intel-mtl :00:1f.3: SOF firmware and/or topology file not 
found.
sof-audio-pci-intel-mtl :00:1f.3: Supported default profiles
sof-audio-pci-intel-mtl :00:1f.3: - ipc type 1 (Requested):
sof-audio-pci-intel-mtl :00:1f.3:  Firmware file: 
intel/sof-ipc4/mtl/sof-mtl.ri
sof-audio-pci-intel-mtl :00:1f.3:  Topology file: 
intel/sof-ace-tplg/sof-mtl-rt711.tplg
sof-audio-pci-intel-mtl :00:1f.3: Check if you have 'sof-firmware' package 
installed.
sof-audio-pci-intel-mtl :00:1f.3: Optionally it can be manually downloaded 
from:
sof-audio-pci-intel-mtl :00:1f.3:
https://github.com/thesofproject/sof-bin/
sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed err: -2

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

Title:
  No sound card detected on the Dell xps 16 2024 (9640)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sound card is not detected on the Dell XPS 16 2024 (9640). A
  Cirrus Logic CS42L43 card is used which apparently got support in
  Linux 6.6

  
https://www.google.com/url?sa=t=web=j=89978449=https://www.phoronix.com/forums/forum/software/general-
  linux-open-source/1408193-linux-6-6-lands-support-for-the-cirrus-
  logic-cs42l43-audio-codec=2ahUKEwiukq-ZroaFAxUWhf0HHe-
  jCngQFnoECA8QAQ=AOvVaw3VW5hROJFzdJPUaIX-3igC

  
https://www.reddit.com/r/DellXPS/comments/1ax1i4t/support_for_xps_16_9640_documentation/

  
  No LSB modules are available.
  Description:  Ubuntu Noble Numbat (development branch)
  Release:  24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 21 23:00:06 2024
  InstallationDate: Installed on 2024-03-19 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240319)
  MachineType: Dell Inc. XPS 16 9640
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2024
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 0YFT36
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/15/2024:br1.1:efr1.2:svnDellInc.:pnXPS169640:pvr:rvnDellInc.:rn0YFT36:rvrA00:cvnDellInc.:ct10:cvr:sku0C62:
  dmi.product.family: XPS
  dmi.product.name: XPS 16 9640
  dmi.product.sku: 0C62
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2058691/+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 2055124] Re: WiFi adapter cannot get IP configuration from Netgear orbi RBR20

2024-03-24 Thread Frédéric Ruellé
I made an Ubuntu update this week and now my laptop is able to connect
to my Orbi access point.

Maybe this one ?

Start-Date: 2024-03-13  06:52:44
Commandline: apt-get upgrade
Requested-By: fred (1000)
Upgrade: dpkg:amd64 (1.21.1ubuntu2.2, 1.21.1ubuntu2.3), libcups2:amd64 
(2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-bsd:amd64 
(2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-common:amd64 
(2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-client:amd64 
(2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-ppdc:amd64 
(2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-daemon:amd64 
(2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-ipp-utils:amd64 
(2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), dpkg-dev:amd64 (1.21.1ubuntu2.2, 
1.21.1ubuntu2.3), gir1.2-accountsservice-1.0:amd64 (22.07.5-2ubuntu1.4, 
22.07.5-2ubuntu1.5), libcupsimage2:amd64 (2.4.1op1-1ubuntu4.7, 
2.4.1op1-1ubuntu4.8), libdpkg-perl:amd64 (1.21.1ubuntu2.2, 1.21.1ubuntu2.3), 
accountsservice:amd64 (22.07.5-2ubuntu1.4, 22.07.5-2ubuntu1.5), 
cups-core-drivers:amd64 (2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups:amd64 
(2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), cups-server-common:amd64 
(2.4.1op1-1ubuntu4.7, 2.4.1op1-1ubuntu4.8), libaccountsservice0:amd64 
(22.07.5-2ubuntu1.4, 22.07.5-2ubuntu1.5)
End-Date: 2024-03-13  06:52:52

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

Title:
  WiFi adapter cannot get IP configuration from Netgear orbi RBR20

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since a recent Ubuntu update (~6 weeks ago), my laptop cannot connect
  anymore to my Netgear Orbi RBR20 WiFi access point.

  The wifi connection is still working fine with my Android smartphone
  set as a WiFi access point.

  My other devices can connect successfully to the Orbi RBR20: printers,
  smartphones, TV, tablets, desktop, Sonos, Netatmo...

  Expected:
  -
 Get an IP address from the Netgear Orbi RBR20.

  Happened instead:
  -
 No IP address obtained, stuck with no WiFi connectivity.


  ThinkPad X13 Gen2 with Ubuntu 22.04.4 LTS:
  --
   fred@ThinkPad:~$ lsb_release -a
   No LSB modules are available.
   Distributor ID:  Ubuntu
   Description: Ubuntu 22.04.4 LTS
   Release: 22.04
   Codename:jammy

  Mediatek WiFi adapter:
  --
  *-network
   description: Interface réseau sans fil
   produit: MT7921 802.11ax PCI Express Wireless Network Adapter
   fabricant: MEDIATEK Corp.
   identifiant matériel: 0
   information bus: pci@:03:00.0
   nom logique: wlp3s0
   nom logique: /dev/fb0
   version: 00
   numéro de série: 74:97:79:8a:36:e7
   bits: 64 bits
   horloge: 33MHz
   fonctionnalités: pciexpress msi pm bus_master cap_list ethernet 
physical wireless fb
   configuration : broadcast=yes depth=32 driver=mt7921e 
driverversion=6.5.0-15-generic firmware=01-20220209150915 latency=0 
link=yes mode=1920x1200 multicast=yes visual=truecolor wireless=IEEE 802.11 
xres=1920 yres=1200
 ressources : mémoireE/S:40-3f mémoireE/S:40-3f mémoireE/S:40-3f irq:87 
mémoire:47020-4702f mémoire:47030-470303fff 
mémoire:470304000-470304fff

  No power saving:
  
   [connection]
   wifi.powersave = 2

  
  Cannot obtain IP configuration:
  ---
   DEVICE TYPE  STATE   
  CONNECTION
   wlp3s0 wifi  connexion (obtention de la configuration 
IP)  ORBIchamprond 

  
  Device association looks OK:
  
   [241460.865152] wlp3s0: authenticate with c2:a5:11:2f:00:c1
   [241460.883343] wlp3s0: send auth to c2:a5:11:2f:00:c1 (try 1/3)
   [241460.886001] wlp3s0: authenticated
   [241460.887489] wlp3s0: associate with c2:a5:11:2f:00:c1 (try 1/3)
   [241460.991496] wlp3s0: associate with c2:a5:11:2f:00:c1 (try 2/3)
   [241461.016131] wlp3s0: RX AssocResp from c2:a5:11:2f:00:c1 
(capab=0x1511 status=0 aid=1)
   [241461.046179] wlp3s0: associated

  
  RBR20 firmware version:
  
   v2.7.3.22

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055124/+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 2033440] Re: ubuntu-desktop: unnecessary hard "Depends: pipewire-audio"

2024-03-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  ubuntu-desktop: unnecessary hard "Depends: pipewire-audio"

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Lunar:
  Won't Fix

Bug description:
  Recommend demoting pipewire-audio from Depends: to Recommends:.

  Reason: While it's not ideal, the Ubuntu Desktop can still function on
  the pulseaudio backend rather than using the direct pipewire-alsa
  backend which conflicts with the pulseaudio package. This would help
  people who wish to have a more traditional JACK setup that is bridged
  to pulseaudio. Right now, this setup is incompatible.

  
  Original description:

  I have installed successfully the standard Ubuntu 23.04 (on a 500 GB
  external USB drive). Immediately after the installation, I have also
  installed with apt the "ubuntustudio-installer" package.

  In the dialog provided by the ubuntustudio-installer, I have selected
  the following metapackages:

  - linux-lowlatency
  - ubuntustudio-lowlatency-settings
  - ubuntustudio-performance-tweaks
  - ubuntustudio-audio
  - ubuntu-pulseaudio-config

  and pressed "Modify installed Package Selection"

  After a while a "qaptbatch" dialog has appeared with title

  "Commit Error"

  and message

  "An error occurred while applying changes"

  So the installation has failed. Then I have tried to manually install
  each metapackage in the list above with apt and every package was
  installed successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2033440/+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 2053228] Re: software-properties-gtk does not start

2024-03-24 Thread Mike
downgrading python3-276 to python3-271 helped! since then GTK is opening
up again.

https://discourse.ubuntu.com/t/spec-apt-deb822-sources-by-default/29333


fthx
Feb 16
FYI I did revert to this one:
https://launchpad.net/ubuntu/+source/python-apt/2.7.1~ubuntu1/+build/27047450/+files/python3-apt_2.7.1~ubuntu1_amd64.deb
 12
(I do use old sources format).

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

Title:
  software-properties-gtk does not start

Status in software-properties package in Ubuntu:
  Fix Committed

Bug description:
  On a new install with the new format sources.list software-properties-gtk 
does not start:
  corrado@corrado-n4-nn-0215:~$ software-properties-gtk
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file
  corrado@corrado-n4-nn-0215:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.42
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:07:43 2024
  InstallationDate: Installed on 2024-02-15 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales

2024-03-24 Thread Thomas Dreibholz
** Project changed: coreutils => glibc

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

Title:
  coreutils: printf formatting bug for nb_NO and nn_NO locales

Status in GLibC:
  New
Status in coreutils package in Ubuntu:
  New

Bug description:
  I just discovered a printf bug for at least the nb_NO and nn_NO
  locales when printing numbers with thousands separator. To reproduce:

  #!/bin/bash
  for l in de_DE en_US nb_NO ; do
     echo "LC_NUMERIC=$l.UTF-8"
     for n in 1 100 1000 1 10 100 1000 ; do
    LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
     done
  done

  The expected output of "%'10d" is a right-formatted number string with
  10 characters.

  The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
  and LC_NUMERIC=en_US.UTF-8:

  LC_NUMERIC=de_DE.UTF-8
  < 1>
  <   100>
  < 1.000>
  <10.000>
  <   100.000>
  < 1.000.000>
  <10.000.000>
  LC_NUMERIC=en_US.UTF-8
  < 1>
  <   100>
  < 1,000>
  <10,000>
  <   100,000>
  < 1,000,000>
  <10,000,000>

  However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the
  formatting is wrong:

  LC_NUMERIC=nb_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>
  LC_NUMERIC=nn_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>

  I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04)
  as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: coreutils 8.32-4.1ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Mar 22 21:33:13 2024
  InstallationDate: Installed on 2022-11-29 (479 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/2058775/+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 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales

2024-03-24 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=31542.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-03-24T09:42:26+00:00 Thomas Dreibholz wrote:

There is a formatting bug for integers in printf() when using locale
settings and formatting with thousands separator.

Test program printfbug.c:
#include 
#include 
#include 

int main(int argc, char** argv)
{
   setlocale (LC_ALL, "");

   struct lconv* loc = localeconv();
   printf("Thousands Separator: <%s>\n", loc->thousands_sep);

   for(int i = 1; i \tint <%'10d>\n", f, n);
   }
   return 0;
}

Test run:
for l in en_US de_DE nb_NO nn_NO ; do
   echo "$l:" ; LC_ALL=$l.UTF-8 ./printfbug 1 10 100 1000 1 10 100 
1000
done

Output:
en_US:
Thousands Separator: <,>
double < 1> int < 1>
double <10> int <10>
double <   100> int <   100>
double < 1,000> int < 1,000>
double <10,000> int <10,000>
double <   100,000> int <   100,000>
double < 1,000,000> int < 1,000,000>
double <10,000,000> int <10,000,000>
de_DE:
Thousands Separator: <.>
double < 1> int < 1>
double <10> int <10>
double <   100> int <   100>
double < 1.000> int < 1.000>
double <10.000> int <10.000>
double <   100.000> int <   100.000>
double < 1.000.000> int < 1.000.000>
double <10.000.000> int <10.000.000>
nb_NO:
Thousands Separator: < >
double < 1> int < 1>
double <10> int <10>
double <   100> int <   100>
double < 1 000> int <   1 000>
double <10 000> int <  10 000>
double <   100 000> int < 100 000>
double < 1 000 000> int <1 000 000>
double <10 000 000> int <10 000 000>
nn_NO:
Thousands Separator: < >
double < 1> int < 1>
double <10> int <10>
double <   100> int <   100>
double < 1 000> int <   1 000>
double <10 000> int <  10 000>
double <   100 000> int < 100 000>
double < 1 000 000> int <1 000 000>
double <10 000 000> int <10 000 000>

That is, en_US and de_DE are fine (they use ',' and '.' as thousands
separator). But nb_NO and nn_NO produce the wrong output when using
integers (%'10d). However, float is fine as well (%'10.0f).

For nb_NO and nn_NO, the separator is a 3-byte UTF-8 character 0xe2 0x80
0xaf, which is UTF-8 NARROW NO-BREAK SPACE ->
https://www.fileformat.info/info/unicode/char/202f/index.htm . It seems
that for integer formatting, the number of bytes is processed, instead
of counting the actual characters. For float formatting, the number of
characters is counted correctly.

That is:
$ LC_ALL=nb_NO.UTF-8 ./printfbug 1000 | hexdump -C
  54 68 6f 75 73 61 6e 64  73 20 53 65 70 61 72 61  |Thousands Separa|
0010  74 6f 72 3a 20 3c e2 80  af 3e 0a 64 6f 75 62 6c  |tor: <...>.doubl|
0020  65 20 3c 20 20 20 20 20  31 e2 80 af 30 30 30 3e  |e < 1...000>|
0030  09 69 6e 74 20 3c 20 20  20 31 e2 80 af 30 30 30  |.int <   1...000|
0040  3e 0a |>.|
0042

I can reproduce the issue under Ubuntu 22.04, Ubuntu 24.04 (development
version), and Fedora 39.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2058775/comments/5


** Changed in: coreutils
   Status: Unknown => New

** Changed in: coreutils
   Importance: Unknown => Medium

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

Title:
  coreutils: printf formatting bug for nb_NO and nn_NO locales

Status in coreutils:
  New
Status in coreutils package in Ubuntu:
  New

Bug description:
  I just discovered a printf bug for at least the nb_NO and nn_NO
  locales when printing numbers with thousands separator. To reproduce:

  #!/bin/bash
  for l in de_DE en_US nb_NO ; do
     echo "LC_NUMERIC=$l.UTF-8"
     for n in 1 100 1000 1 10 100 1000 ; do
    LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
     done
  done

  The expected output of "%'10d" is a right-formatted number string with
  10 characters.

  The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
  and LC_NUMERIC=en_US.UTF-8:

  LC_NUMERIC=de_DE.UTF-8
  < 1>
  <   100>
  < 1.000>
  <10.000>
  <   100.000>
  < 1.000.000>
  <10.000.000>
  LC_NUMERIC=en_US.UTF-8
  < 1>
  <   100>
  < 1,000>
  <10,000>
  <   100,000>
  < 1,000,000>
  <10,000,000>

  However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the
  

[Touch-packages] [Bug 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales

2024-03-24 Thread Thomas Dreibholz
** Bug watch added: Sourceware.org Bugzilla #31542
   https://sourceware.org/bugzilla/show_bug.cgi?id=31542

** Also affects: coreutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=31542
   Importance: Unknown
   Status: Unknown

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

Title:
  coreutils: printf formatting bug for nb_NO and nn_NO locales

Status in coreutils:
  Unknown
Status in coreutils package in Ubuntu:
  New

Bug description:
  I just discovered a printf bug for at least the nb_NO and nn_NO
  locales when printing numbers with thousands separator. To reproduce:

  #!/bin/bash
  for l in de_DE en_US nb_NO ; do
     echo "LC_NUMERIC=$l.UTF-8"
     for n in 1 100 1000 1 10 100 1000 ; do
    LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
     done
  done

  The expected output of "%'10d" is a right-formatted number string with
  10 characters.

  The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
  and LC_NUMERIC=en_US.UTF-8:

  LC_NUMERIC=de_DE.UTF-8
  < 1>
  <   100>
  < 1.000>
  <10.000>
  <   100.000>
  < 1.000.000>
  <10.000.000>
  LC_NUMERIC=en_US.UTF-8
  < 1>
  <   100>
  < 1,000>
  <10,000>
  <   100,000>
  < 1,000,000>
  <10,000,000>

  However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the
  formatting is wrong:

  LC_NUMERIC=nb_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>
  LC_NUMERIC=nn_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>

  I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04)
  as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: coreutils 8.32-4.1ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Mar 22 21:33:13 2024
  InstallationDate: Installed on 2022-11-29 (479 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/coreutils/+bug/2058775/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low

2024-03-24 Thread vince
Hello Sebastien,

I agree with you.

The value 2147483642 is the value purposed by TKG kernel, but as
mentioned in my report, if the value is > 200k well issues in game is
over.

I think, the fedora value is a good approach because we already have
return of their experience, and there is no trouble linked about this
value reported in the fedora side.

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

Title:
  Some Games are crashing linked to a vm_max_map_count too low

Status in Ubuntu:
  Confirmed
Status in gamemode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Hello there,

  I submit this request to improve the gaming experience in ubuntu for all 
users. 
  Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just 
not starting because the vm_max_map_count is locked at 65530. If we change this 
value to a value > 20, all games are working well and there is no bug 
linked to maps. 

  Some others distribution like Fedora or Pop OS, have already made the
  change few month before.

  It's time to Ubuntu to makes the change also.

  Thanks in advance for applying this request.

  How to make this change :

  One file to modify : 
  /etc/sysctl.conf
  Add this line :
  vm.max_map_count=2147483642
  Save
  Reboot and enjoy

  Best Regards
  Vinceff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2057792/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low

2024-03-24 Thread Sebastien Bacher
Thanks for the report.

So

- the kernel default and current value is 65530

- Fedora changed to 1048576
(https://src.fedoraproject.org/rpms/systemd/blob/rawhide/f/10-map-
count.conf) which was enough according to their testing

- you are suggesting 2147483642 , which is several order of magnitude
higher

Unsure if there are possible side effects or downside of having a too
high value but it's late in the cycle and 1048576 seems like a more
reasonable default


@Julian I think from a Desktop perspective we are +1 on bumping to at least 
1048576, technically that should be done in systemd I think. It that a 
FFe/change that you/foundations are wanting to work on?

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

Title:
  Some Games are crashing linked to a vm_max_map_count too low

Status in Ubuntu:
  Confirmed
Status in gamemode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Hello there,

  I submit this request to improve the gaming experience in ubuntu for all 
users. 
  Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just 
not starting because the vm_max_map_count is locked at 65530. If we change this 
value to a value > 20, all games are working well and there is no bug 
linked to maps. 

  Some others distribution like Fedora or Pop OS, have already made the
  change few month before.

  It's time to Ubuntu to makes the change also.

  Thanks in advance for applying this request.

  How to make this change :

  One file to modify : 
  /etc/sysctl.conf
  Add this line :
  vm.max_map_count=2147483642
  Save
  Reboot and enjoy

  Best Regards
  Vinceff

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