Re: [Touch-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )
On Thu, May 25, 2023 at 5:35 PM Thorsten Glaser
<2020...@bugs.launchpad.net> wrote:
>
> I doubt this is a bug: nowhere do you pass the validator a DTD, and
> entities are defined in the DTD.
>
> It’s best practice nowadays to not use entities but just write the UTF-8
> characters directly.
>
> An em dash surrounded by hair spaces is: “ — ” (for your copy/paste
> convenience)
I think you are right - this is not a bug. I took a quick peek at RFC
3470, and I don't see where HTML entity references are optional.
Sorry about that. I got some bad info off the internet (surprise,
surprise). It said to use the character entity reference for emdash
due to portability problems when using the character itself.
Jeff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020814
Title:
xmllint does not recognize emdash ()
Status in libxml2 package in Ubuntu:
New
Bug description:
I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to
build a PDF. One of the steps I use in my build script is to validate and
format the XML using xmllint from libxml2-utils
2.9.13+dfsg-1ubuntu0.3:
echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."
echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."
When I added an emdash () the book failed to format:
Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
injections are remediated using several methods. And two output devices
^
ch02.xml:58: parser error : Entity 'mdash' not defined
methods. And two output devices the printer and plaintext email
^
Complete.
The text is:
... And two output devices the printer and plaintext
email do not require...
It seems like emdash should be recognized.
-
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename: jammy
-
$ xmllint --version
xmllint: using libxml version 20913
compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma
$ command -v xmllint
/usr/bin/xmllint
$ dpkg -S /usr/bin/xmllint
libxml2-utils: /usr/bin/xmllint
$ apt-cache show libxml2-utils
Package: libxml2-utils
Architecture: amd64
Version: 2.9.13+dfsg-1ubuntu0.3
Multi-Arch: foreign
Priority: optional
Section: text
Source: libxml2
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian XML/SGML Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 202
Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
Filename:
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
Size: 40192
MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
SHA512:
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
Homepage: http://xmlsoft.org
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+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 1801540]
(In reply to Frédéric Pierret from comment #5)
> Hi,
>
> I also had the same problem with my ASROCK X370 Gaming K4 (ALC1220):
>
> 1st case: Booting FIRST Linux: Sound with noise/crackling.
> 2nd case: Booting FIRST Windows and SECOND Linux: Sound is perfect.
>
> I suceed in solving the problem by comparing the Coeff values in both cases
> and assign the values of the second case in a script at boot time. How to:
>
> - Install alsa-tools.
> - In both cases, you have to: echo 1 >
> /sys/module/snd_hda_codec/parameters/dump_coefs
> - Then, in the first case, alsa-info --no-upload --output infos_bad
> - Then, in the second case, alsa-info --no-upload --output infos_good
> - Finally, you compare the coef values: diff infos_bad infos_good | grep
> Coeff
>
> For changing the value of each different Coeff, you need to proceed as
> follow: for example, changing Coeff 0x67 to value 0x3000
>
> hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67
> hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x3000
>
> You have to do this in the growing order of Coeff. Remark that hwC0D0 refers
> to your sound card. In case of HDMI output like me, my sound card if hwC1D0.
>
> Here is a quick script:
>
>
> #!/bin/bash
>
> coeffs=($(echo 0x{16,43,44,5d,5e,63,67}))
> values=($(echo 0x{8020,3405,fa10,0606,,e430,3000}))
>
> for i in `seq 0 $(( ${#coeffs[@]} - 1 ))`
> do
> hda-verb /dev/snd/hwC1D0 0x20 SET_COEF_INDEX ${coeffs[$i]} && hda-verb
> /dev/snd/hwC1D0 0x20 SET_PROC_COEF ${values[$i]}
> done
>
>
> Just change the coeffs to change in the array 'coeffs' and the new values in
> array 'values' and exec this script. A remark, while I do not shutdown the
> power supply, my audio chipset keeps the values. This is why you need to do
> the FIRST case (first...) and then the second. Then, you could test if it
> works only when you shutdown the power supply of your mobo and then booting
> into Linux directly.
>
> I'm preparing a patch for the kernel but for those who have the problem,
> could you post your coeff/values which need to be change please.
>
> Hope this helps.
Hi Frederic,
thank you for sharing your approach and script.
It helped me to solve a problem with my ALC3234 (Dell Optiplex 3040 Micro). The
analog output format was limited to 44.1kHz/48kHz after direct linux boot. With
a previous Windows boot, additional 96kHz/192kHz are available.
I will attach the adapted script, that works for me. May be it helps someone.
--
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/1801540
Title:
Microphone distorted sound on ALC892/1220 on AMD chipsets
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Won't Fix
Status in pulseaudio package in Ubuntu:
Won't Fix
Bug description:
Not sure if I'll report this upstream but there is definitely an issue
with microphone recording on my desktop, this is not happening on my
laptop which has a different codec.
Already tried all workarounds possible, no luck. Only with my desktop
with this particular motherboard. No issues in Windows, the sound
recorded in there is distorted and has some static and robotic tone on
high-pitch.
alsa-info on the attachments
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 2020812] Re: Unable to change color highlight in apt output
I think you need to url encode the sequence, but not sure. I don't think there's anything we can do here about handling backslashes, the problem is backspaces do happen in actual config items and we can't introduce a behavior change for them as that would cause regressions. You should be free to also printf the actual special character into the config option or the command line argument. -- 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/2020812 Title: Unable to change color highlight in apt output Status in apt package in Ubuntu: New Bug description: Ubuntu Release: lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 Source package and version: dpkg-query -W apt apt 2.4.9 Binary apt command has support for color output on some commands such as "apt list " Where enabled the default color output is unbolded green color. This is due to the apt configuration item, APT::Color::Highlight being set to the default ANSI color code of "\x1B[32m", Setting it to another ANSI code should alter the apt output. Expectation:Setting the Highlight configuration option to another ANSI code should alter the apt output to the specified color code. $ apt list apt -o apt::color::highlight="\x1b[31m" should set the highlighted package name to an unbold red color. What happens: $ apt list apt -o apt::color::highlight="\x1b[31m" Listing... Done \x1b[31mapt/jammy-updates,now 2.4.9 amd64 [installed,automatic] \x1b[31mapt/jammy-updates 2.4.9 i386 Prepends literal string of \x1b[31m instead of producing colored output. "\033[31m" doesn't work either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2020812/+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 1801540]
Created attachment 304321 script to adapt alc3234 codec coefs -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 2018013] Re: package ca-certificates 20230311 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 3
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ca-certificates (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/2018013 Title: package ca-certificates 20230311 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 3 Status in ca-certificates package in Ubuntu: Confirmed Bug description: do-release upgrade from 22.10-> 23.04 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: ca-certificates 20230311 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 28 17:38:06 2023 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 3 InstallationDate: Installed on 2022-07-28 (274 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: ca-certificates Title: package ca-certificates 20230311 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 3 UpgradeStatus: Upgraded to lunar on 2023-04-28 (0 days ago) modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2018013/+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 2012943] Re: systemd-resolved crashes due to use-after-free bug
With 245.4-4ubuntu3.21, I was seeing resolved crash every few minutes due to this bug. With 245.4-4ubuntu3.22, I have not seen this crash, resolved seems to be working correctly. -- 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/2012943 Title: systemd-resolved crashes due to use-after-free bug Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [ Impact ] The continuous systemd-resolved crashes delay/hang the device startup. And this leads to unresponsive devices in the system. Specifically, the crash looks like: Dec 16 12:51:21 TREND-24-AF-7A systemd[1]: Started Time & Date Service. Dec 16 12:51:24 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=11/SEGV [...] Dec 16 12:53:47 TREND-24-AF-7A systemd-resolved[2591]: Assertion 'DNS_TRANSACTION_IS_LIVE(q->state)' failed at src/resolve/resolved-dns-query.c:520, function dns_query_complete(). Aborting. Dec 16 12:53:47 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=6/ABRT [ Test Plan ] The exact steps to reproduce this issue are still not known. But we see this crash only in Static IP Addressing mode enabled, where systemd-resolved is enabled for LLMNR service. But we were not able to see this crash in DHCP mode. Steps to reproduce: 1) Powercycle the device. 2) Soft-reboot. It was also pointed out by Brian Murray that this error in the Ubuntu error tracker is likely the same bug: https://errors.ubuntu.com/problem/3cb08ae5efaa4d8c6ce992f7cebd2751ae3f168f. Therefore, we would expect to stop seeing this error in the tracker as a result of this patch. [ Where problems could occur ] The patch[1] simply disables the timer event source for a DNS query when the struct representing that query is free'd. I cannot see any realistic regression potential, because if the timer event fired on the DNS query after it has been free'd, then that would be this bug. I.e. no working code should be relying on the timer event source still being around after the query is free'd. [1] https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012943/+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 2020838] [NEW] [regression][jammy] augenrules Error sending add rule data request (No such file or directory)
Public bug reported: The rule '-a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged' can not be loaded during system boot up. # lsb_release -rc Release:22.04 Codename: jammy # dpkg -l|grep audit ii auditd 1:3.0.7-1build1 amd64User space tools for security auditing ii libaudit-common 1:3.0.7-1build1 all Dynamic library for security auditing - common files ii libaudit1:amd64 1:3.0.7-1build1 amd64Dynamic library for security auditing ii libauparse0:amd64 1:3.0.7-1build1 amd64Dynamic library for parsing security auditing # cat /etc/audit/rules.d/audit.rules|grep -v ^#|grep -v ^$ -D -a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts -b 8192 --backlog_wait_time 6 -f 1 # >/etc/audit/audit.rules reboot the system, no rule can be loaded # auditctl -l No rules syslog: May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: Error sending add rule data request (No such file or directory) May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: There was an error in line 5 of /etc/audit/audit.rules May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: No rules May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: enabled 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: failure 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: pid 476 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: rate_limit 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_limit 8192 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: lost 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time 15000 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time_actual 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: enabled 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: failure 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: pid 476 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: rate_limit 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_limit 8192 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: lost 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time 15000 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time_actual 0 # cat /etc/audit/audit.rules ## This file is automatically generated from /etc/audit/rules.d -D -b 8192 -f 1 -a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts --backlog_wait_time 6 But I can manually load the rule file. Seems this issue only happen during system boot up. # auditctl -R /etc/audit/audit.rules No rules enabled 1 failure 1 pid 476 rate_limit 0 backlog_limit 8192 lost 0 backlog 4 backlog_wait_time 15000 backlog_wait_time_actual 0 enabled 1 failure 1 pid 476 rate_limit 0 backlog_limit 8192 lost 0 backlog 4 backlog_wait_time 15000 backlog_wait_time_actual 0 enabled 1 failure 1 pid 476 rate_limit 0 backlog_limit 8192 lost 0 backlog 14 backlog_wait_time 6 backlog_wait_time_actual 0 # auditctl -l -a always,exit -S all -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=-1 -F key=mounts If I move the file /home/ubuntu/test.sh to / opt/test.sh or /etc/test.sh /usr/bin/test.sh, then I can not reproduce the issue. Additionally, I have ruled out AppArmor as a factor. I have already disabled the AppArmor service and append "apparmor=0" into the kernel command line before rebooting. Moreover, I can NOT reproduce this issue on Focal(1:2.8.5-2ubuntu6) There are 2 issues here, I think 1) If the rules can be loaded manually, why can't they be loaded automatically at system startup? 2) When loading a particular rule fails, why are the subsequent rules skipped? ** Affects: audit (Ubuntu) Importance: Undecided Status: New ** Tags: sts ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/2020838 Title: [regression][jammy] augenrules Error sending add rule data request (No such file or directory) Status in audit package in Ubuntu: New Bug description: The rule '-a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged' can not be loaded during system boot up. # lsb_release -rc Release: 22.04 Codename: jammy # dpkg -l|grep audit ii
[Touch-packages] [Bug 2020796] Re: Latest Ubuntu update kills Chrome and Brave
Please look in /var/log/apt/history.log to identify which update you are referring to. If the problem is caused by some Ubuntu update then it will be tracked here, but if it's just a bug in Brave and Chrome then it would need to be tracked at https://bugs.chromium.org/p/chromium/issues/list ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2020796 Title: Latest Ubuntu update kills Chrome and Brave Status in Ubuntu: Incomplete Bug description: The update installed this morning (May 25, 2023) disabled both Brave and Chrome. Firefox is OK. I have installed a newer Brave-beta and it works fine. The problem first appeared in Xorg, where no page could be rendered, including settings. I then rebooted into Wayland and Brave and Chrome can render pictures but not text. The Brave version is brave-browser/stable,now 1.51.118 amd64 [installed] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 25 11:26:48 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 5.19.0-41-generic, x86_64: installed bcmwl/6.30.223.271+bdcom, 5.19.0-42-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity 2 [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Trinity 2 [Radeon HD 7520G] [103c:1992] InstallationDate: Installed on 2022-06-15 (344 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP ProBook 645 G1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=20cda528-3e8f-4a58-b19f-969a0f06aae3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L72 Ver. 01.47 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1992 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 05.34 dmi.chassis.asset.tag: 016269 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 5.52 dmi.modalias: dmi:bvnHewlett-Packard:bvrL72Ver.01.47:bd07/30/2018:br1.47:efr5.52:svnHewlett-Packard:pnHPProBook645G1:pvrA3009DD10303:rvnHewlett-Packard:rn1992:rvrKBCVersion05.34:cvnHewlett-Packard:ct10:cvr:skuD2Z92AV: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 645 G1 dmi.product.sku: D2Z92AV dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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/+bug/2020796/+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 2020838] Re: [regression][jammy] augenrules Error sending add rule data request (No such file or directory)
** Description changed: - - The rule '-a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged' can not be loaded during system boot up. + The rule '-a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F + auid>=1000 -F auid!=unset -k privileged' can not be loaded during system + boot up. # lsb_release -rc Release: 22.04 Codename: jammy # dpkg -l|grep audit ii auditd 1:3.0.7-1build1 amd64User space tools for security auditing ii libaudit-common 1:3.0.7-1build1 all Dynamic library for security auditing - common files ii libaudit1:amd64 1:3.0.7-1build1 amd64Dynamic library for security auditing ii libauparse0:amd64 1:3.0.7-1build1 amd64Dynamic library for parsing security auditing # cat /etc/audit/rules.d/audit.rules|grep -v ^#|grep -v ^$ -D -a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts -b 8192 --backlog_wait_time 6 -f 1 + + # ls -l /home/ubuntu/test.sh + -rwxr-xr-x 1 root ubuntu 19 May 25 14:19 /home/ubuntu/test.sh + + # cat /home/ubuntu/test.sh + #!/bin/bash + echo 1 # >/etc/audit/audit.rules reboot the system, no rule can be loaded # auditctl -l No rules syslog: May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: Error sending add rule data request (No such file or directory) May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: There was an error in line 5 of /etc/audit/audit.rules May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: No rules May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: enabled 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: failure 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: pid 476 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: rate_limit 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_limit 8192 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: lost 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time 15000 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time_actual 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: enabled 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: failure 1 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: pid 476 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: rate_limit 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_limit 8192 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: lost 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog 0 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time 15000 May 26 02:17:36 juju-d929ae-con28-1 augenrules[507]: backlog_wait_time_actual 0 # cat /etc/audit/audit.rules ## This file is automatically generated from /etc/audit/rules.d -D -b 8192 -f 1 -a always,exit -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=unset -k privileged -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=unset -k mounts --backlog_wait_time 6 But I can manually load the rule file. Seems this issue only happen during system boot up. # auditctl -R /etc/audit/audit.rules No rules enabled 1 failure 1 pid 476 rate_limit 0 backlog_limit 8192 lost 0 backlog 4 backlog_wait_time 15000 backlog_wait_time_actual 0 enabled 1 failure 1 pid 476 rate_limit 0 backlog_limit 8192 lost 0 backlog 4 backlog_wait_time 15000 backlog_wait_time_actual 0 enabled 1 failure 1 pid 476 rate_limit 0 backlog_limit 8192 lost 0 backlog 14 backlog_wait_time 6 backlog_wait_time_actual 0 - # auditctl -l -a always,exit -S all -F path=/home/ubuntu/test.sh -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged -a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=-1 -F key=mounts - - If I move the file /home/ubuntu/test.sh to / opt/test.sh or /etc/test.sh /usr/bin/test.sh, then I can not reproduce the issue. - Additionally, I have ruled out AppArmor as a factor. I have already disabled the AppArmor service and append "apparmor=0" into the kernel command line before rebooting. + If I move the file /home/ubuntu/test.sh to / opt/test.sh or /etc/test.sh /usr/bin/test.sh, then I can not reproduce the issue. + Additionally, I have ruled out AppArmor as a factor. I have already disabled the AppArmor service and append "apparmor=0" into the kernel command line before rebooting. Moreover, I can NOT reproduce this issue on Focal(1:2.8.5-2ubuntu6) - There are 2 issues here, I think 1) If the rules can be loaded manually, why can't they
[Touch-packages] [Bug 2020163] Re: only = and != equations work for auid field
> and < should be escaped in shell. It's not a bug. closing it. ** Changed in: audit (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/2020163 Title: only = and != equations work for auid field Status in audit package in Ubuntu: Invalid Bug description: lsb_release -rc Release: 22.04 Codename: jammy dpkg -l|grep audi ii auditd 1:3.0.7-1build1 amd64User space tools for security auditing ii libaudit-common 1:3.0.7-1build1 all Dynamic library for security auditing - common files ii libaudit1:amd64 1:3.0.7-1build1 amd64Dynamic library for security auditing ii libauparse0:amd64 1:3.0.7-1build1 amd64Dynamic library for parsing security auditing work for = and != $ sudo auditctl -a always,exit -F auid=1000 $ sudo auditctl -a always,exit -F auid!=1000 $ sudo auditctl -D No rules Do not work for < > <= >= $ sudo auditctl -a always,exit -F auid<1000 -bash: 1000: No such file or directory $ sudo auditctl -a always,exit -F auid>1000 -F missing operation for auid $ sudo auditctl -a always,exit -F auid<=1000 -F missing operation for auid $ sudo auditctl -a always,exit -F auid>=1000 -F missing operation for auid sudo auditctl -a always,exit -F auidubuntu -F missing operation for auid sudo auditctl -a always,exit -F auid<=ubuntu bash: =ubuntu: No such file or directory sudo auditctl -a always,exit -F auid>=ubuntu -F missing operation for auid sudo auditctl -a always,exit -F auid>'ubuntu' -F missing operation for auid sudo auditctl -a always,exit -F auid<'ubuntu' -F missing operation for auid sudo auditctl -a always,exit -F auid<='ubuntu' -F missing operation for auid sudo auditctl -a always,exit -F auid>='ubuntu' -F missing operation for auid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/2020163/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
** Changed in: maas
Milestone: 3.4.0 => 3.4.0-beta2
--
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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
New
Status in MAAS:
Fix Committed
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
New
Status in linux package in Ubuntu:
Fix Committed
Status in systemd package in Ubuntu:
Invalid
Status in apparmor source package in Lunar:
New
Status in linux source package in Lunar:
Fix Committed
Status in systemd source package in Lunar:
New
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2020759] Re: App bar non-responsive when not in front
*** This bug is a duplicate of bug 2013216 *** https://bugs.launchpad.net/bugs/2013216 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2013216, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 2013216 Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) -- 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/2020759 Title: App bar non-responsive when not in front Status in mutter package in Ubuntu: New Bug description: When clicking on the "app bar" of some applications (containing the name and close/minimise/... button) which are not in the foreground, nothing happens. This seems to currently happen with the sioyek app (which was not installed but is running through some fuse) and Discord, but did happen to other stuff too :) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 25 10:52:01 2023 DistUpgraded: 2023-04-23 21:55:53,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8292] InstallationDate: Installed on 2023-03-30 (56 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05c8:0397 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP HD Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 03f0:a31d HP, Inc HP lt4132 LTE/HSPA+ 4G Module Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 820 G4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=8b91027a-0905-472e-925a-7554704d7b0e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-23 (31 days ago) dmi.bios.date: 07/17/2018 dmi.bios.release: 1.23 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.23 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.43 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 69.67 dmi.modalias: dmi:bvnHP:bvrP78Ver.01.23:bd07/17/2018:br1.23:efr69.67:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.43:cvnHP:ct10:cvr:skuX3T23AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 820 G4 dmi.product.sku: X3T23AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020759/+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 2020383] Re: Please merge avahi 0.8-10 from Debian unstable
This bug was fixed in the package avahi - 0.8-10ubuntu1 --- avahi (0.8-10ubuntu1) mantic; urgency=medium * Merge with Debian unstable (LP: #2020383). Remaining changes: + Disable lto, see https://bugzilla.redhat.com/show_bug.cgi?id=1907727 + avahi-daemon-chroot-fix-bogus-assignments-in-assertions.patch, avahi-client-fix-resource-leak.patch: Issues discovered by static analysis (Upstream pull request #202) * Dropped changes, included in Debian: + avoid-infinite-loop-in-avahi-daemon-by-handling-hup-event-in-client-work.patch: Avoid infinite-loop in avahi-daemon by handling HUP event in client_work() (Upstream pull request #330) * Dropped changes, no longer needed: + debian/avahi-daemon.postinst: remove the deprecated conffiles if-up/down entries on upgrade, use a simple logic and no dpkg-maintscript-helper since there is no configuration worth saving (All releases from which upgrades are supported have a new enough version) -- Nick Rosbrook Tue, 23 May 2023 10:02:00 -0400 ** Changed in: avahi (Ubuntu) Status: In Progress => Fix Released ** Bug watch added: Red Hat Bugzilla #1907727 https://bugzilla.redhat.com/show_bug.cgi?id=1907727 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/2020383 Title: Please merge avahi 0.8-10 from Debian unstable Status in avahi package in Ubuntu: Fix Released Bug description: Tracking bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/2020383/+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 2018596] Re: Please merge sysvinit 3.06-4 (main) from Debian unstable (main)
This bug was fixed in the package sysvinit - 3.06-4ubuntu1 --- sysvinit (3.06-4ubuntu1) mantic; urgency=medium * Merge with Debian unstable (LP: #2018596). Remaining changes: - When building for Ubuntu, skip all binaries except for sysvinit-utils - d/rules: fix installation of 50-ubuntu-logging when building on Ubuntu (Closes: #1028586) * Dropped changes: - Define the DEB_HOST_* variables in d/rules if not defined already * The dropped change was undocumented and first introduced in focal. It is unclear what it was originally fixing. One assumption is that, when Debian started relying on /usr/share/dpkg/common.mk, the file was not present (or incomplete) on some architectures in Ubuntu. We have kept this change around for nearly four years, potentially for no valid reason. In 3.06-2ubuntu1, this change was worded as "Adjust debian/rules to fix an arch: all build failure". This is a mistake and should not be trusted. sysvinit (3.06-4) unstable; urgency=medium * Add Romanian debconf translations with thanks to Remus-Gabriel Chelu . (Closes: #1033723) sysvinit (3.06-3) unstable; urgency=medium * Cherry pick hunk from upstream to fix regression in pidof not matching symlinks. (Closes: #1033311) * Cherry pick upstream patch to fix memory initialisation in pidof. (Closes: #1033311) -- Olivier Gayot Sun, 07 May 2023 01:04:33 +0200 ** Changed in: sysvinit (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/2018596 Title: Please merge sysvinit 3.06-4 (main) from Debian unstable (main) Status in sysvinit package in Ubuntu: Fix Released Bug description: This is a merge of sysvinit 3.06-4. Please see the relevant merge proposal. The ubuntu delta is unaffected. We should be able to drop one patch when we will merge the next upstream version (i.e., 3.07) which is currently in debian experimental. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2018596/+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 1993800]
This is an autogenerated message for OBS integration: This bug (1204267) was mentioned in https://build.opensuse.org/request/show/1088949 Backports:SLE-15-SP4 / llvm15 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1993800 Title: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> Status in LLVM: Fix Released Status in llvm-toolchain-15 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in llvm-toolchain-15 package in openSUSE: Fix Released Bug description: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> 0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 0x2f84090:1, Constant:i32<4> 0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0x2aad434, 0x2f63a30, Constant:i32<64> 0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23 0x2f51c10: i32 = Register %23 0x2f82500: i32 = Constant<64> 0x2f81b28: i32 = Constant<4> 0x2f81e40: i32 = Constant<2> In function: fs_variant_partial [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic- armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz] Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't determine what project "fs_variant_partial" is in. Sounds like it might be in some old version of Mesa? The start of the log suggests it's running on focal. To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1993800/+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 2020759] [NEW] App bar non-responsive when not in front
Public bug reported: When clicking on the "app bar" of some applications (containing the name and close/minimise/... button) which are not in the foreground, nothing happens. This seems to currently happen with the sioyek app (which was not installed but is running through some fuse) and Discord, but did happen to other stuff too :) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 25 10:52:01 2023 DistUpgraded: 2023-04-23 21:55:53,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8292] InstallationDate: Installed on 2023-03-30 (56 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05c8:0397 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP HD Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 03f0:a31d HP, Inc HP lt4132 LTE/HSPA+ 4G Module Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 820 G4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=8b91027a-0905-472e-925a-7554704d7b0e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-23 (31 days ago) dmi.bios.date: 07/17/2018 dmi.bios.release: 1.23 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.23 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.43 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 69.67 dmi.modalias: dmi:bvnHP:bvrP78Ver.01.23:bd07/17/2018:br1.23:efr69.67:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.43:cvnHP:ct10:cvr:skuX3T23AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 820 G4 dmi.product.sku: X3T23AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 lunar ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2020759 Title: App bar non-responsive when not in front Status in xorg package in Ubuntu: New Bug description: When clicking on the "app bar" of some applications (containing the name and close/minimise/... button) which are not in the foreground, nothing happens. This seems to currently happen with the sioyek app (which was not installed but is running through some fuse) and Discord, but did happen to other stuff too :) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 25 10:52:01 2023 DistUpgraded: 2023-04-23 21:55:53,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8292] InstallationDate: Installed on 2023-03-30 (56 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05c8:0397 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP HD Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 03f0:a31d HP, Inc HP lt4132 LTE/HSPA+ 4G Module Bus 001 Device 001: ID
[Touch-packages] [Bug 401935] Re: aa-genprof fails if profiles are in a subdirectory of /etc/apparmor.d
It is imperative that we read blog post very carefully. I am already done it and find that this post is really amazing. https://xtrench- run.com -- 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/401935 Title: aa-genprof fails if profiles are in a subdirectory of /etc/apparmor.d Status in apparmor package in Ubuntu: Fix Released Bug description: Binary package hint: apparmor aa-genprof fails if there are profiles in a subdirectory of /etc/apparmor.d. Reproducer: $ sudo mkdir /etc/apparmor.d/foo $ sudo cp /etc/apparmor.d/usr.sbin.cupsd /etc/apparmor.d/foo $ sudo aa-genprof /usr/bin/gedit include contains syntax errors. ProblemType: Bug ApparmorStatusOutput: Error: command /usr/sbin/apparmor_status failed with exit code 4: You do not have enough privilege to read the profile set. apparmor module is loaded. Architecture: amd64 Date: Mon Jul 20 16:12:57 2009 DistroRelease: Ubuntu 9.10 Package: apparmor 2.3.1+1403-0ubuntu5 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-3.19-generic SourcePackage: apparmor Uname: Linux 2.6.31-3-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/401935/+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 2020749] [NEW] Please merge console-setup 1.221 into mantic
Public bug reported: console-setup (1.221) unstable; urgency=medium * Team upload. [ Updated translations ] * Belarusian (be.po) by Viktar Siarheichyk * Bengali (bn.po) by Indrani Roy * Norwegian Nynorsk (nn.po) by Yngve Spjeld-Landro console-setup (1.220) unstable; urgency=medium * Team upload. [ Updated translations ] * Norwegian Bokmal (nb.po) by Kjetil Sørlund * Norwegian Nynorsk (nn.po) by Kjetil Sørlund console-setup (1.219) unstable; urgency=medium [ Updated translations ] * Georgian (ka.po) by Temuri Doghonadze console-setup (1.218) unstable; urgency=medium * Team upload. [ Updated translations ] * German (de.po) by Holger Wansing * Vietnamese (vi.po) by tictactoe ** Affects: console-setup (Ubuntu) Importance: Undecided Assignee: Shengjing Zhu (zhsj) Status: New ** Changed in: console-setup (Ubuntu) Assignee: (unassigned) => Shengjing Zhu (zhsj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/2020749 Title: Please merge console-setup 1.221 into mantic Status in console-setup package in Ubuntu: New Bug description: console-setup (1.221) unstable; urgency=medium * Team upload. [ Updated translations ] * Belarusian (be.po) by Viktar Siarheichyk * Bengali (bn.po) by Indrani Roy * Norwegian Nynorsk (nn.po) by Yngve Spjeld-Landro console-setup (1.220) unstable; urgency=medium * Team upload. [ Updated translations ] * Norwegian Bokmal (nb.po) by Kjetil Sørlund * Norwegian Nynorsk (nn.po) by Kjetil Sørlund console-setup (1.219) unstable; urgency=medium [ Updated translations ] * Georgian (ka.po) by Temuri Doghonadze console-setup (1.218) unstable; urgency=medium * Team upload. [ Updated translations ] * German (de.po) by Holger Wansing * Vietnamese (vi.po) by tictactoe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2020749/+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 2020748] Re: package ca-certificates 20230311ubuntu0.22.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/2020748 Title: package ca-certificates 20230311ubuntu0.22.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: Out of standby this morning, I saw a popup reporting the crash and suggesting to submit a report. That's it. Good luck. Matthieu ProblemType: Package DistroRelease: Ubuntu 22.04 Package: ca-certificates 20230311ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: ca-certificates:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu May 25 09:08:25 2023 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-12-29 (511 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: ca-certificates Title: package ca-certificates 20230311ubuntu0.22.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-10-08 (228 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2020748/+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 2020748] [NEW] package ca-certificates 20230311ubuntu0.22.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exi
Public bug reported: Out of standby this morning, I saw a popup reporting the crash and suggesting to submit a report. That's it. Good luck. Matthieu ProblemType: Package DistroRelease: Ubuntu 22.04 Package: ca-certificates 20230311ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: ca-certificates:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu May 25 09:08:25 2023 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-12-29 (511 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: ca-certificates Title: package ca-certificates 20230311ubuntu0.22.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-10-08 (228 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/2020748 Title: package ca-certificates 20230311ubuntu0.22.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: Out of standby this morning, I saw a popup reporting the crash and suggesting to submit a report. That's it. Good luck. Matthieu ProblemType: Package DistroRelease: Ubuntu 22.04 Package: ca-certificates 20230311ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: ca-certificates:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu May 25 09:08:25 2023 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-12-29 (511 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: ca-certificates Title: package ca-certificates 20230311ubuntu0.22.04.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-10-08 (228 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2020748/+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 2020503] Re: Build libvisual-plugins on i386
** Changed in: libvisual (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libvisual in Ubuntu. https://bugs.launchpad.net/bugs/2020503 Title: Build libvisual-plugins on i386 Status in libvisual package in Ubuntu: Fix Released Status in libvisual-plugins package in Ubuntu: Fix Released Bug description: The source package libvisual is built on i386 (as a dependency of gstreamer). libvisual now builds a new binary package, lv-tool-0.4. lv-tool-0.4 depends on libvisual-0.4-plugins. libvisual-0.4-plugins appears to have no dependencies that are not already available on i386 Therefore, please enable libvisual-plugins to build on i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvisual/+bug/2020503/+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 1979879] Re: Apparmor profile in 22.04 jammy - fails to start when printing enabled
I'll check the current status -- 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/1979879 Title: Apparmor profile in 22.04 jammy - fails to start when printing enabled Status in apparmor package in Ubuntu: Invalid Status in samba package in Ubuntu: Fix Released Status in apparmor source package in Jammy: In Progress Bug description: [Impact] Users who have: a) opted in to confining samba with apparmor (by installing apparmor-profiles); and b) changed the usr.sbin.smbd and samba-bgqd apparmor profiles to enforce mode; will experience an error in starting the smbd service in jammy: [2022/08/25 16:04:05.848067, 0] ../../lib/util/become_daemon.c:119(exit_daemon) exit_daemon: daemon failed to start: Samba failed to init printing subsystem, error code 13 This "printing subsystem" is actually a new daemon called samba-bgqd. This errors prevents "smbd" from starting. The reason it failed to start is that this binary is installed on a different path than what is allowed in the samba apparmor profiles, and as a result its execution is denied. The chosen fix for this is to change the path of samba-bgqd in the samba apparmor profiles to match where it is actually being installed in the jammy packaging. Changing the actual path in the samba packaging would be a more invasive fix. In kinetic and later, the installation path of samba-bgqd was changed instead, and requires no changes to the apparmor profiles. However, once the path in the apparmor profiles was fixed for jammy, another error comes up which also requires an apparmor change. samba- bgqd is using locking when opening the *.tdb files in /run/samba, and that requires an extra "k" flag to apparmor rules that cover that directory and its tdb files. This bug doesn't affect jammy samba users by default, as they have to complete steps (a) and (b) from above to be impacted. Therefore, on its own, this bug does not warrant an SRU, and we are using the block- proposed-jammy tag to prevent its release until such time when another more SRU-worthy apparmor bug is fixed for Jammy. [Test Plan] Make a container for testing: $ lxc launch ubuntu-daily:jammy jammy-test $ lxc shell jammy-test Install the needed packages in this order, with two separate commands:L # apt update # apt install apparmor-profiles apparmor-utils apparmor-profiles-extra # apt install samba smbclient cups cups-client Confirm that you have smbd and samba-bgqd processes confined and in complain mode (check first column): # ps faxZ | grep -E "(smbd|bgqd)" | grep -v grep smbd (complain)2432 ?Ss 0:00 /usr/sbin/smbd --foreground --no-process-group smbd (complain)2434 ?S 0:00 \_ /usr/sbin/smbd --foreground --no-process-group smbd (complain)2435 ?S 0:00 \_ /usr/sbin/smbd --foreground --no-process-group smbd//null-/usr/lib/x86_64-linux-gnu/samba/samba-bgqd (complain) 2436 ? S 0:00 \_ /usr/lib/x86_64-linux-gnu/samba/samba-bgqd Change the samba profiles to enforce mode: # aa-enforce /etc/apparmor.d/usr.sbin.smbd /etc/apparmor.d/samba-bgqd Setting /etc/apparmor.d/usr.sbin.smbd to enforce mode. Setting /etc/apparmor.d/samba-bgqd to enforce mode. Restart smbd: # systemctl restart smbd systemctl won't complain, but smbd failed to start: # ps faxZ | grep smbd | grep -v grep # # tail -2 /var/log/samba/log.smbd [2022/09/09 18:20:35.200901, 0] ../../lib/util/become_daemon.c:119(exit_daemon) exit_daemon: daemon failed to start: Samba failed to init printing subsystem, error code 13 And dmesg on the *host* (not the container) will log a few DENIED messages like this: [sex set 9 15:20:30 2022] audit: type=1400 audit(1662747635.194:10356): apparmor="DENIED" operation="exec" namespace="root//lxd-jammy-test_" profile="smbd" name="/usr/lib/x86_64-linux-gnu/samba/samba-bgqd" pid=994396 comm="smbd" requested_mask="x" denied_mask="x" fsuid=100 ouid=100 After installing the fixed package (and accepting the dpkg conf prompt changes), the new profile will be loaded in complain mode again. So let's put it in enforce mode one more time: # aa-enforce /etc/apparmor.d/usr.sbin.smbd /etc/apparmor.d/samba-bgqd Setting /etc/apparmor.d/usr.sbin.smbd to enforce mode. Setting /etc/apparmor.d/samba-bgqd to enforce mode. Restart: # systemctl restart smbd And confirm that smbd and samba-bgqd are running this time, and in enforce mode: # ps faxZ | grep -E "(smbd|bgqd)" | grep -v grep avahi-daemon (complain)4363 ?Ss 0:00 avahi-daemon: running [j-samba-bgqd-apparmor.local] smbd (enforce) 6734 ?Ss 0:00 /usr/sbin/smbd --foreground --no-process-group smbd (enforce)
[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020474 Title: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session Status in openssh package in Ubuntu: In Progress Bug description: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell server socket... May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. At this point, sshd is no longer listening for new connections. A manual systemctl restart of ssh.socket fails with the same error. I am ssh-ed into this box, so I *think* the failure is because my session is already sitting on port 22, maybe? The only way I can be sure I will be able to ssh to this box again is to reboot it (so that ssh.socket can start cleanly). $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu1 Candidate: 1:9.2p1-2ubuntu1 Version table: *** 1:9.2p1-2ubuntu1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.2p1-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6 Uname: Linux 6.2.0-19-generic riscv64 ApportVersion: 2.26.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230413.1 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue May 23 14:58:35 2023 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2020789] [NEW] pcscd should depend on vsmartcard-vpcd
Public bug reported: If I install pcscd but not vsmartcard-vpcd, the service fails to start: ---> × pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; preset: enabled) Active: failed (Result: exit-code) since Thu 2023-05-25 16:11:31 CEST; 1min 52s ago Duration: 59ms TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Process: 410224 ExecStart=/usr/sbin/pcscd --foreground --auto-exit $PCSCD_ARGS (code=exited, status=1/FAILURE) Main PID: 410224 (code=exited, status=1/FAILURE) CPU: 8ms mai 25 16:11:30 canonical systemd[1]: Started pcscd.service - PC/SC Smart Card Daemon. mai 25 16:11:31 canonical pcscd[410224]: configfile.l:163:evaluatetoken() Error with library /usr/lib/pcsc/drivers/serial/libifdvpcd.so: No such file or directory mai 25 16:11:31 canonical pcscd[410224]: 00017989 pcscdaemon.c:835:clean_temp_files() Cannot remove /run/pcscd/pcscd.pid: No such file or directory mai 25 16:11:31 canonical systemd[1]: pcscd.service: Main process exited, code=exited, status=1/FAILURE mai 25 16:11:31 canonical systemd[1]: pcscd.service: Failed with result 'exit-code'. <--- Should pcscd depend on it? ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/2020789 Title: pcscd should depend on vsmartcard-vpcd Status in pcsc-lite package in Ubuntu: New Bug description: If I install pcscd but not vsmartcard-vpcd, the service fails to start: ---> × pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; preset: enabled) Active: failed (Result: exit-code) since Thu 2023-05-25 16:11:31 CEST; 1min 52s ago Duration: 59ms TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Process: 410224 ExecStart=/usr/sbin/pcscd --foreground --auto-exit $PCSCD_ARGS (code=exited, status=1/FAILURE) Main PID: 410224 (code=exited, status=1/FAILURE) CPU: 8ms mai 25 16:11:30 canonical systemd[1]: Started pcscd.service - PC/SC Smart Card Daemon. mai 25 16:11:31 canonical pcscd[410224]: configfile.l:163:evaluatetoken() Error with library /usr/lib/pcsc/drivers/serial/libifdvpcd.so: No such file or directory mai 25 16:11:31 canonical pcscd[410224]: 00017989 pcscdaemon.c:835:clean_temp_files() Cannot remove /run/pcscd/pcscd.pid: No such file or directory mai 25 16:11:31 canonical systemd[1]: pcscd.service: Main process exited, code=exited, status=1/FAILURE mai 25 16:11:31 canonical systemd[1]: pcscd.service: Failed with result 'exit-code'. <--- Should pcscd depend on it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/2020789/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After mesa upgrades, Chrome won't show graphics Status in mesa package in Ubuntu: Confirmed Bug description: After today's Ubuntu 22.04 mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There is a bypass listed in that article. Not sure if this is an issue with mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2020604/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics
I confirm the issue on a desktop with Intel HD Graphics 530 (rev 06) (Core i7-6700 CPU). At present time I found that it can be worked around in two ways: 1) Using the '--disable-gpu-driver-bug-workarounds' option: # google-chrome-stable --disable-gpu-driver-bug-workarounds 2) Defining MESA_LOADER_DRIVER_OVERRIDE=i965 in the environment in which chrome is executed: # MESA_LOADER_DRIVER_OVERRIDE=i965 google-chrome-stable I can send any further information (or make any test) that can help you in fixing the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After mesa upgrades, Chrome won't show graphics Status in mesa package in Ubuntu: Confirmed Bug description: After today's Ubuntu 22.04 mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There is a bypass listed in that article. Not sure if this is an issue with mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2020604/+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 1892225] Re: apport-gtk consumes 100% CPU for way too long after something crashes
The same on Ubuntu 20.04; `apport-cli --version` prints 2.20.11 -- 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/1892225 Title: apport-gtk consumes 100% CPU for way too long after something crashes Status in apport package in Ubuntu: Confirmed Bug description: Something (related to Cinnamon) crashes, so the usual popup appears telling me that something crashed, and asking me whether I wanted to send a report. I choose Send. Every time this happens, then a process called apport-gtk starts consuming 100% CPU and it goes on for several minutes, so long that I end up killing it. There's no way there is a good reason for consuming so much CPU for so long. If you need to do such an amount of processing just to generate and send a bug report, something is deeply broken. But if the operation actually had to be that computationally expensive, then you must do it in a less intensive way so that it can go on in the background, for no matter how long, without rendering me unable to use my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: called for pid 2405, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: executable: /usr/bin/cinnamon (command line "cinnamon --replace") ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: debug: session gdbus call: (true,) ERROR: apport (pid 2908) Wed Aug 19 18:39:34 2020: wrote report /var/crash/_usr_bin_cinnamon.1000.crash ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:110:69556:2020-08-19 18:39:33.732794284 +0200:2020-08-19 18:39:34.732794284 +0200:/var/crash/_usr_bin_cinnamon-launcher.1000.crash 640:1000:110:15432562:2020-08-19 18:39:34.466977487 +0200:2020-08-19 18:42:42.722667813 +0200:/var/crash/_usr_bin_cinnamon.1000.crash CurrentDesktop: X-Cinnamon Date: Wed Aug 19 18:42:34 2020 InstallationDate: Installed on 2013-10-11 (2503 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-07-12 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1892225/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics
I confirm the issue on a ThinkPad T440 Intel® Core™ i5-4300U CPU @ 1.90GHz × 4 Mesa Intel® HD Graphics 4400 (HSW GT2) As a workaround I have renamed GPUCache folder for both chrome and brave browser. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After mesa upgrades, Chrome won't show graphics Status in mesa package in Ubuntu: Confirmed Bug description: After today's Ubuntu 22.04 mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There is a bypass listed in that article. Not sure if this is an issue with mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2020604/+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 2020796] [NEW] Latest Ubuntu update kills Chrome and Brave
Public bug reported: The update installed this morning (May 25, 2023) disabled both Brave and Chrome. Firefox is OK. I have installed a newer Brave-beta and it works fine. The problem first appeared in Xorg, where no page could be rendered, including settings. I then rebooted into Wayland and Brave and Chrome can render pictures but not text. The Brave version is brave- browser/stable,now 1.51.118 amd64 [installed] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 25 11:26:48 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 5.19.0-41-generic, x86_64: installed bcmwl/6.30.223.271+bdcom, 5.19.0-42-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity 2 [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Trinity 2 [Radeon HD 7520G] [103c:1992] InstallationDate: Installed on 2022-06-15 (344 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Hewlett-Packard HP ProBook 645 G1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=20cda528-3e8f-4a58-b19f-969a0f06aae3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L72 Ver. 01.47 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1992 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 05.34 dmi.chassis.asset.tag: 016269 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 5.52 dmi.modalias: dmi:bvnHewlett-Packard:bvrL72Ver.01.47:bd07/30/2018:br1.47:efr5.52:svnHewlett-Packard:pnHPProBook645G1:pvrA3009DD10303:rvnHewlett-Packard:rn1992:rvrKBCVersion05.34:cvnHewlett-Packard:ct10:cvr:skuD2Z92AV: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 645 G1 dmi.product.sku: D2Z92AV dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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/2020796 Title: Latest Ubuntu update kills Chrome and Brave Status in xorg package in Ubuntu: New Bug description: The update installed this morning (May 25, 2023) disabled both Brave and Chrome. Firefox is OK. I have installed a newer Brave-beta and it works fine. The problem first appeared in Xorg, where no page could be rendered, including settings. I then rebooted into Wayland and Brave and Chrome can render pictures but not text. The Brave version is brave-browser/stable,now 1.51.118 amd64 [installed] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 25 11:26:48 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 5.19.0-41-generic, x86_64: installed bcmwl/6.30.223.271+bdcom, 5.19.0-42-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity 2 [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Trinity 2 [Radeon HD 7520G] [103c:1992] InstallationDate: Installed on 2022-06-15 (344 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
[Touch-packages] [Bug 2020749] Re: Please merge console-setup 1.221 into mantic
** Merge proposal linked: https://code.launchpad.net/~zhsj/ubuntu/+source/console-setup/+git/console-setup/+merge/443584 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/2020749 Title: Please merge console-setup 1.221 into mantic Status in console-setup package in Ubuntu: New Bug description: console-setup (1.221) unstable; urgency=medium * Team upload. [ Updated translations ] * Belarusian (be.po) by Viktar Siarheichyk * Bengali (bn.po) by Indrani Roy * Norwegian Nynorsk (nn.po) by Yngve Spjeld-Landro console-setup (1.220) unstable; urgency=medium * Team upload. [ Updated translations ] * Norwegian Bokmal (nb.po) by Kjetil Sørlund * Norwegian Nynorsk (nn.po) by Kjetil Sørlund console-setup (1.219) unstable; urgency=medium [ Updated translations ] * Georgian (ka.po) by Temuri Doghonadze console-setup (1.218) unstable; urgency=medium * Team upload. [ Updated translations ] * German (de.po) by Holger Wansing * Vietnamese (vi.po) by tictactoe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2020749/+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 1971425] Re: The "look" cli dictionary only sees capitalized words
** Changed in: util-linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: util-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: util-linux (Ubuntu Jammy) Status: New => Triaged ** Changed in: util-linux (Ubuntu Lunar) Status: New => Triaged ** Changed in: util-linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: util-linux (Ubuntu Lunar) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1971425 Title: The "look" cli dictionary only sees capitalized words Status in util-linux package in Ubuntu: Triaged Status in util-linux source package in Jammy: Triaged Status in util-linux source package in Lunar: Triaged Status in util-linux package in Debian: Unknown Bug description: In Ubuntu 20.04; ~ > look accident accident accident's accidental accidental's accidentally accidentals accidents In Ubuntu 22.04; ~ > look accident (nothing) ~ > look acc Accenture Accenture's Accra Accra's Digging deeper; the dictionary at /usr/share/dict/words seems OK. If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it works; ~ > ./look accident accident accidental accidentally accidental's accidentals accident's accidents ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bsdextrautils 2.37.2-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue May 3 14:19:57 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: util-linux UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics
--disable-gpu-driver-bug-workarounds did not work for me, but deleting GPUCache did. Keep in mind that GPUCache could be inside a profile folder like ~/.config/google-chrome/Profile 1/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After mesa upgrades, Chrome won't show graphics Status in mesa package in Ubuntu: Confirmed Bug description: After today's Ubuntu 22.04 mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There is a bypass listed in that article. Not sure if this is an issue with mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2020604/+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 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session
** Tags removed: rls-mm-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020474 Title: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session Status in openssh package in Ubuntu: In Progress Bug description: Installation seems to fail on restarting ssh.socket via systemctl Setting up openssh-server (1:9.2p1-2ubuntu1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) $ systemctl status ssh.socket × ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s ago Duration: 3h 6min 36.071s Triggers: ● ssh.service Listen: [::]:22 (Stream) CPU: 2ms May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully. May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell server socket. May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell server socket... May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening socket ([::]:22): Address already in use May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening socket ([::]:22): Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: Input/output error May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'. May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD Secure Shell server socket. At this point, sshd is no longer listening for new connections. A manual systemctl restart of ssh.socket fails with the same error. I am ssh-ed into this box, so I *think* the failure is because my session is already sitting on port 22, maybe? The only way I can be sure I will be able to ssh to this box again is to reboot it (so that ssh.socket can start cleanly). $ lsb_release -rd No LSB modules are available. Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 $ apt policy openssh-server openssh-server: Installed: 1:9.2p1-2ubuntu1 Candidate: 1:9.2p1-2ubuntu1 Version table: *** 1:9.2p1-2ubuntu1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main riscv64 Packages 100 /var/lib/dpkg/status 1:9.0p1-1ubuntu8.1 500 500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.2p1-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6 Uname: Linux 6.2.0-19-generic riscv64 ApportVersion: 2.26.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230413.1 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Tue May 23 14:58:35 2023 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2019940] Re: Directly manipulating NetworkManager keyfiles
** Tags removed: rls-mm-incoming ** Tags added: foundations-todo -- 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/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: Invalid Status in cruft package in Ubuntu: Won't Fix Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 2019940] Re: Directly manipulating NetworkManager keyfiles
Have any snaps been looked at e.g. subiquity or ubuntu-desktop- installer? -- 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/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: Invalid Status in cruft package in Ubuntu: Won't Fix Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 1971425] Re: The "look" cli dictionary only sees capitalized words
** Changed in: util-linux (Ubuntu) Importance: Low => Medium ** Tags added: regression-release ** Bug watch added: Debian Bug tracker #973471 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973471 ** Also affects: util-linux (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973471 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1971425 Title: The "look" cli dictionary only sees capitalized words Status in util-linux package in Ubuntu: Confirmed Status in util-linux package in Debian: Unknown Bug description: In Ubuntu 20.04; ~ > look accident accident accident's accidental accidental's accidentally accidentals accidents In Ubuntu 22.04; ~ > look accident (nothing) ~ > look acc Accenture Accenture's Accra Accra's Digging deeper; the dictionary at /usr/share/dict/words seems OK. If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it works; ~ > ./look accident accident accidental accidentally accidental's accidentals accident's accidents ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bsdextrautils 2.37.2-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue May 3 14:19:57 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: util-linux UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 1971425] Re: The "look" cli dictionary only sees capitalized words
** Tags removed: regression-release rls-jj-incoming ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1971425 Title: The "look" cli dictionary only sees capitalized words Status in util-linux package in Ubuntu: Confirmed Status in util-linux package in Debian: Unknown Bug description: In Ubuntu 20.04; ~ > look accident accident accident's accidental accidental's accidentally accidentals accidents In Ubuntu 22.04; ~ > look accident (nothing) ~ > look acc Accenture Accenture's Accra Accra's Digging deeper; the dictionary at /usr/share/dict/words seems OK. If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it works; ~ > ./look accident accident accidental accidentally accidental's accidentals accident's accidents ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bsdextrautils 2.37.2-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue May 3 14:19:57 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: util-linux UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hi Ghadi Rahme,
I see this ticket is in progress, just want to check when the fix will be
updated in Ubuntu's packages?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
In Progress
Status in python2.7 source package in Focal:
In Progress
Status in python2.7 source package in Jammy:
In Progress
Status in python2.7 source package in Kinetic:
In Progress
Status in python2.7 source package in Lunar:
In Progress
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics
While it's obviously not a real fix, As I don't use chrome as my primary browser, simply regenerating my ~/.config/google-chrome/ directory resolved this issue. Others may not have this option. Question 1 : What is it about the Mesa upgrade that kills chrome but not Firefox? Question 2 : Is there a less nuclear fix than wiping the Chrome settings? e.g. Deleting just the ShaderCache or GrShaderCache directories? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After mesa upgrades, Chrome won't show graphics Status in mesa package in Ubuntu: Confirmed Bug description: After today's Ubuntu 22.04 mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There is a bypass listed in that article. Not sure if this is an issue with mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2020604/+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 2020707] Re: Merge tiff 4.5.0-6 (main) from Debian unstable (main)
This bug was fixed in the package tiff - 4.5.0-6ubuntu1 --- tiff (4.5.0-6ubuntu1) mantic; urgency=medium * Merge from Debian unstable (LP: #2020707). Remaining changes: - Don't build with LERC on i386 because it requires numpy (Closes: #1017958) tiff (4.5.0-6) unstable; urgency=high * Backport security fix for CVE-2023-2731, NULL pointer dereference flaw in LZWDecode() (closes: #1036282). -- Amin Bandali Wed, 24 May 2023 16:13:57 -0400 ** Changed in: tiff (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/2020707 Title: Merge tiff 4.5.0-6 (main) from Debian unstable (main) Status in tiff package in Ubuntu: Fix Released Bug description: Please merge tiff 4.5.0-6 (main) from Debian unstable (main) Changelog entries since current mantic version 4.5.0-5ubuntu1: tiff (4.5.0-6) unstable; urgency=high * Backport security fix for CVE-2023-2731, NULL pointer dereference flaw in LZWDecode() (closes: #1036282). -- Laszlo Boszormenyi (GCS) Thu, 18 May 2023 18:20:39 +0200 Remaining changes: - Don't build with LERC on i386 because it requires numpy (Closes: #1017958) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2020707/+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 1971425] Re: The "look" cli dictionary only sees capitalized words
** Changed in: util-linux (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1971425 Title: The "look" cli dictionary only sees capitalized words Status in util-linux package in Ubuntu: Triaged Status in util-linux source package in Jammy: Triaged Status in util-linux source package in Lunar: Triaged Status in util-linux package in Debian: Confirmed Bug description: In Ubuntu 20.04; ~ > look accident accident accident's accidental accidental's accidentally accidentals accidents In Ubuntu 22.04; ~ > look accident (nothing) ~ > look acc Accenture Accenture's Accra Accra's Digging deeper; the dictionary at /usr/share/dict/words seems OK. If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it works; ~ > ./look accident accident accidental accidentally accidental's accidentals accident's accidents ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bsdextrautils 2.37.2-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue May 3 14:19:57 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: util-linux UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992454] Re: iptables: segfault when renaming a chain
iptables in excuses triggers tests in other packages. The excuses report doesn't show the fully green results anymore, so it's easy to miss them. I think we can consider the ufw dep8 tests as sufficient for the case of "normal iptables usage hasn't regressed". I ran the ufw debian/tests/root-unittest DEP8 test in a jammy vm, and checked with execsnoop that it was calling the real iptables during the tests, and not just pretending or calling a fake binary like the normal unittest test. I aborted it after a few minutes, because the extra logging was taking a lot of time, but here is a sample: 17:12:30 TIME TIME(s) UID PCOMMPIDPPID RET ARGS 17:12:30 1.962 0 iptables 28768 287670 /usr/sbin/iptables --version 17:12:30 1.964 0 iptables 28773 287720 /usr/sbin/iptables --version 17:12:30 2.002 0 iptables 28817 288160 /usr/sbin/iptables -V 17:12:30 2.203 0 iptables 29060 290590 /usr/sbin/iptables -V 17:12:30 2.205 0 ip6tables29062 290610 /sbin/ip6tables -L INPUT -n 17:12:30 2.205 0 iptables 29063 290610 /sbin/iptables -F ufw-logging-deny 17:12:30 2.206 0 iptables 29064 290610 /sbin/iptables -F ufw-logging-allow (...) 17:12:30 2.552 0 iptables 29371 292250 /usr/sbin/iptables -D ufw-user-logging-forward -j RETURN 17:12:30 2.553 0 iptables 29372 292250 /usr/sbin/iptables -A ufw-after-logging-input -j LOG --log-prefix [UFW BLOCK] -m limit --limit 3/min --limit-burst 10 17:12:30 2.553 0 iptables 29373 292250 /usr/sbin/iptables -A ufw-after-logging-forward -j LOG --log-prefix [UFW BLOCK] -m limit --limit 3/min --limit-burst 10 17:12:30 2.554 0 iptables 29374 292250 /usr/sbin/iptables -I ufw-logging-deny -m conntrack --ctstate INVALID -j RETURN -m limit --limit 3/min --limit-burst 10 17:12:30 2.555 0 iptables 29375 292250 /usr/sbin/iptables -A ufw-logging-deny -j LOG --log-prefix [UFW BLOCK] -m limit --limit 3/min --limit-burst 10 17:12:30 2.555 0 iptables 29376 292250 /usr/sbin/iptables -A ufw-logging-allow -j LOG --log-prefix [UFW ALLOW] -m limit --limit 3/min --limit-burst 10 17:12:30 2.556 0 iptables 29377 292250 /usr/sbin/iptables -D ufw-user-limit -m limit --limit 3/minute -j LOG --log-prefix [UFW LIMIT BLOCK] 17:12:30 2.557 0 iptables 29378 292250 /usr/sbin/iptables -I ufw-user-limit -m limit --limit 3/minute -j LOG --log-prefix [UFW LIMIT BLOCK] 17:12:31 2.601 0 iptables 29380 293790 /usr/sbin/iptables -V 17:12:31 2.609 0 iptables 29383 290570 /usr/sbin/iptables -L -n (...) # grep iptables d-t-root-unittest.log |wc -l 9389 All these while iptables from jammy-proposed was installed: # apt-cache policy iptables iptables: Installed: 1.8.7-1ubuntu5.1 Candidate: 1.8.7-1ubuntu5.1 Version table: *** 1.8.7-1ubuntu5.1 500 500 http://br.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages With that in mind, let's confirm that the ufw dep8 tests ran with the iptables package from proposed for each ubuntu release: # Kinetic Results yaml: https://ubuntu-archive-team.ubuntu.com/proposed-migration/kinetic/update_excuses.yaml.xz ufw/amd64 log: https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/amd64/u/ufw/20230515_201517_324f0@/log.gz iptables from kinetic-proposed: $ zgrep kinetic-proposed/main.*iptables log.gz |head -n 1 Get:1 http://ftpmaster.internal/ubuntu kinetic-proposed/main amd64 iptables amd64 1.8.7-1ubuntu6.1 [454 kB] root-unittest passed: $ zgrep ^root-unittest kinetic-log.gz root-unittestPASS root-unittestPASS # Jammy Results yaml: https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.yaml.xz ufw/amd64 log: https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/amd64/u/ufw/20230516_174358_f55b2@/log.gz iptables from jammy-proposed: $ zgrep jammy-proposed/main.*iptables jammy-log.gz |head -n 1 Get:1 http://ftpmaster.internal/ubuntu jammy-proposed/main amd64 iptables amd64 1.8.7-1ubuntu5.1 [455 kB] root-unittest passed: $ zgrep ^root-unittest jammy-log.gz root-unittestPASS root-unittestPASS # focal Results yaml: https://ubuntu-archive-team.ubuntu.com/proposed-migration/focal/update_excuses.yaml.xz ufw/amd64 log: https://autopkgtest.ubuntu.com/results/autopkgtest- focal/focal/amd64/u/ufw/20230518_023831_3747d@/log.gz iptables from focal-proposed: $ zgrep focal-proposed/main.*iptables focal-log.gz |head -n 1 Get:1 http://ftpmaster.internal/ubuntu focal-proposed/main amd64 iptables amd64 1.8.4-3ubuntu2.1 [390 kB] root-unittest passed: $ zgrep ^root-unittest focal-log.gz root-unittestPASS root-unittestPASS # bionic Results yaml:
[Touch-packages] [Bug 2020814] Re: xmllint does not recognize emdash ( )
I doubt this is a bug: nowhere do you pass the validator a DTD, and
entities are defined in the DTD.
It’s best practice nowadays to not use entities but just write the UTF-8
characters directly.
An em dash surrounded by hair spaces is: “ — ” (for your copy/paste
convenience)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020814
Title:
xmllint does not recognize emdash ()
Status in libxml2 package in Ubuntu:
New
Bug description:
I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to
build a PDF. One of the steps I use in my build script is to validate and
format the XML using xmllint from libxml2-utils
2.9.13+dfsg-1ubuntu0.3:
echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."
echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."
When I added an emdash () the book failed to format:
Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
injections are remediated using several methods. And two output devices
^
ch02.xml:58: parser error : Entity 'mdash' not defined
methods. And two output devices the printer and plaintext email
^
Complete.
The text is:
... And two output devices the printer and plaintext
email do not require...
It seems like emdash should be recognized.
-
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename: jammy
-
$ xmllint --version
xmllint: using libxml version 20913
compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma
$ command -v xmllint
/usr/bin/xmllint
$ dpkg -S /usr/bin/xmllint
libxml2-utils: /usr/bin/xmllint
$ apt-cache show libxml2-utils
Package: libxml2-utils
Architecture: amd64
Version: 2.9.13+dfsg-1ubuntu0.3
Multi-Arch: foreign
Priority: optional
Section: text
Source: libxml2
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian XML/SGML Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 202
Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
Filename:
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
Size: 40192
MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
SHA512:
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
Homepage: http://xmlsoft.org
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics
`rm -R ~/.config/google-chrome/Default/GPUCache` (and then restarting chrome) from the askubuntu post fixed it! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After mesa upgrades, Chrome won't show graphics Status in mesa package in Ubuntu: Confirmed Bug description: After today's Ubuntu 22.04 mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2020604/+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 2012943] Re: systemd-resolved crashes due to use-after-free bug
Hi Brian, Commercial Engineering(CE) and field team provided a custom core20 snap to Naveen(customer) that includes the suggested fix and it is being tested around 2 months. According to the customer input, the reported issue is no longer seen and the fix is valid. Thank you, Bugra ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2012943 Title: systemd-resolved crashes due to use-after-free bug Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [ Impact ] The continuous systemd-resolved crashes delay/hang the device startup. And this leads to unresponsive devices in the system. Specifically, the crash looks like: Dec 16 12:51:21 TREND-24-AF-7A systemd[1]: Started Time & Date Service. Dec 16 12:51:24 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=11/SEGV [...] Dec 16 12:53:47 TREND-24-AF-7A systemd-resolved[2591]: Assertion 'DNS_TRANSACTION_IS_LIVE(q->state)' failed at src/resolve/resolved-dns-query.c:520, function dns_query_complete(). Aborting. Dec 16 12:53:47 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=6/ABRT [ Test Plan ] The exact steps to reproduce this issue are still not known. But we see this crash only in Static IP Addressing mode enabled, where systemd-resolved is enabled for LLMNR service. But we were not able to see this crash in DHCP mode. Steps to reproduce: 1) Powercycle the device. 2) Soft-reboot. It was also pointed out by Brian Murray that this error in the Ubuntu error tracker is likely the same bug: https://errors.ubuntu.com/problem/3cb08ae5efaa4d8c6ce992f7cebd2751ae3f168f. Therefore, we would expect to stop seeing this error in the tracker as a result of this patch. [ Where problems could occur ] The patch[1] simply disables the timer event source for a DNS query when the struct representing that query is free'd. I cannot see any realistic regression potential, because if the timer event fired on the DNS query after it has been free'd, then that would be this bug. I.e. no working code should be relying on the timer event source still being around after the query is free'd. [1] https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012943/+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 2016439] Re: Regression finding system certificates
All dep8 failures have been resolved.
--
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/2016439
Title:
Regression finding system certificates
Status in curl package in Ubuntu:
Fix Released
Status in curl source package in Lunar:
Fix Committed
Status in curl source package in Mantic:
Fix Released
Status in curl package in Debian:
Fix Released
Bug description:
[ Impact ]
Users of applications that link against libcurl's NSS flavour might
experience issues when trying to contact HTTPS servers. This can lead
to scenarios where the application is unable to connect.
[ Test Plan ]
First, let's verify that the GNUTLS flavour of libcurl does the right
thing:
$ lxc launch ubuntu-daily:lunar curl-bug2016439
$ lxc shell curl-bug2016439
# apt update && apt install -y libcurl4-gnutls-dev gcc
# cat > curl-test.c << __EOF__
#include
#include
int main(void)
{
CURL *curl;
CURLcode res;
curl = curl_easy_init();
if(curl) {
curl_easy_setopt(curl, CURLOPT_URL, "https://example.com;);
/* example.com is redirected, so we tell libcurl to follow redirection */
curl_easy_setopt(curl, CURLOPT_FOLLOWLOCATION, 1L);
/* Perform the request, res will get the return code */
res = curl_easy_perform(curl);
/* Check for errors */
if(res != CURLE_OK)
fprintf(stderr, "curl_easy_perform() failed: %s\n",
curl_easy_strerror(res));
/* always cleanup */
curl_easy_cleanup(curl);
}
return 0;
}
__EOF__
# gcc curl-test.c -o curl-test -lcurl
# ./curl-test
Example Domain
...
#
You should see the HTML dump of example.com. Now, let's install the
NSS flavour of libcurl and recompile the test program against it:
# apt install -y libcurl4-nss-dev
# gcc curl-test.c -o curl-test -lcurl
# ./curl-test
curl_easy_perform() failed: SSL peer certificate or SSH remote key was not OK
As we can see, there was an error when validating the TLS certificate.
[ Where problems could occur ]
The adjustment needed to the downstream patch is pretty simple and has
been tested extensively. The original reporter mentioned that the
issue did not happen before this patch was applied, so in the unlikely
event of a regression the best route would be to revert the patch
entirely.
[ More Info ]
This happens because of an error in one of our patches (authored by
me) to teach libcurl where to properly find libnsspem.so and
libnssckbi.so. The problem is that libnsspem.so is installed under
/usr/lib/$(DEB_HOST_ARCH)/nss/, while libnssckbi.so is installed under
/usr/lib/$(DEB_HOST_ARCH)/, but I mistakenly pointed libcurl to look
under the "/nss/" directory for both libraries. As it turns out,
libnssckbi.so is necessary in order to use the Mozilla's root
certificate.
[ Original Description ]
[ Clone of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034359 ]
Between 7.88.1-2 and 7.88.1-5, there was a change to where curl with
nss looks for loadable libraries:
curl (7.88.1-4) unstable; urgency=medium
* d/p/Use-correct-path-when-loading-libnss-pem-ckbi-.so.patch:
Prepend "/nss/" before the library name.
Before the change to the load path, curl could find
/lib/x86_64-linux-gnu/libnssckbi.so but not
/lib/x86_64-linux-gnu/nss/libnsspem.so, after the change it's the
reverse.
libnssckbi.so is enough to get a trust root (the mozilla certificate
store is compiled inside that library), whereas libnsspem.so
(1.0.8+1-1) isn't.
This makes it impossible to connect to https servers by default for
programs that use curl with NSS.
Here is a way to test the regression:
debbisect -v --cache=./cache \
--depends=libcurl4-nss-dev,git,pkg-config,libssl-dev,ca-certificates,cargo,nss-plugin-pem,p11-kit-modules,strace
\
20230306T145638Z 20230306T203828Z \
'chroot "$1" bash -exuc "
git clone --depth 1 https://github.com/alexcrichton/curl-rust.git
cd curl-rust
time cargo fetch
time cargo build --offline --example https
strace -efile target/debug/examples/https >/dev/null
"'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2016439/+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 2018538] Re: All PDFs when printed come out mirror image
I am not able to reproduce this bug. Could anyone of you please provide me your queue's PPD file from the /etc/cups/ppd/ directory? Thanks. Could you please also run the command cupsctl --debug-logging then print a job which comes out mirrored and after that attach the file /var/log/cups/error_log to this bug report? Thanks. Please attach your files one by one, do not compress them and do not package them together. Thanks. ** Changed in: cups (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2018538 Title: All PDFs when printed come out mirror image Status in cups package in Ubuntu: Incomplete Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as instead. (I'm printing double sided/long edge print, so one side is normal and the other side becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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 2016439] Re: Regression finding system certificates
This bug was fixed in the package curl - 7.88.1-8ubuntu2
---
curl (7.88.1-8ubuntu2) lunar; urgency=medium
* d/p/Use-correct-path-when-loading-libnss-pem-ckbi-.so.patch:
Don't prepend "nss" when opening libnssckbi.so. Rename definition
to _DEB_TARGET_ARCH. (LP: #2016439)
* d/rules: Declare DEB_TARGET_MULTIARCH. Rename definition to
_DEB_TARGET_ARCH.
-- Sergio Durigan Junior Thu, 20 Apr
2023 17:30:44 -0400
** Changed in: curl (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
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/2016439
Title:
Regression finding system certificates
Status in curl package in Ubuntu:
Fix Released
Status in curl source package in Lunar:
Fix Released
Status in curl source package in Mantic:
Fix Released
Status in curl package in Debian:
Fix Released
Bug description:
[ Impact ]
Users of applications that link against libcurl's NSS flavour might
experience issues when trying to contact HTTPS servers. This can lead
to scenarios where the application is unable to connect.
[ Test Plan ]
First, let's verify that the GNUTLS flavour of libcurl does the right
thing:
$ lxc launch ubuntu-daily:lunar curl-bug2016439
$ lxc shell curl-bug2016439
# apt update && apt install -y libcurl4-gnutls-dev gcc
# cat > curl-test.c << __EOF__
#include
#include
int main(void)
{
CURL *curl;
CURLcode res;
curl = curl_easy_init();
if(curl) {
curl_easy_setopt(curl, CURLOPT_URL, "https://example.com;);
/* example.com is redirected, so we tell libcurl to follow redirection */
curl_easy_setopt(curl, CURLOPT_FOLLOWLOCATION, 1L);
/* Perform the request, res will get the return code */
res = curl_easy_perform(curl);
/* Check for errors */
if(res != CURLE_OK)
fprintf(stderr, "curl_easy_perform() failed: %s\n",
curl_easy_strerror(res));
/* always cleanup */
curl_easy_cleanup(curl);
}
return 0;
}
__EOF__
# gcc curl-test.c -o curl-test -lcurl
# ./curl-test
Example Domain
...
#
You should see the HTML dump of example.com. Now, let's install the
NSS flavour of libcurl and recompile the test program against it:
# apt install -y libcurl4-nss-dev
# gcc curl-test.c -o curl-test -lcurl
# ./curl-test
curl_easy_perform() failed: SSL peer certificate or SSH remote key was not OK
As we can see, there was an error when validating the TLS certificate.
[ Where problems could occur ]
The adjustment needed to the downstream patch is pretty simple and has
been tested extensively. The original reporter mentioned that the
issue did not happen before this patch was applied, so in the unlikely
event of a regression the best route would be to revert the patch
entirely.
[ More Info ]
This happens because of an error in one of our patches (authored by
me) to teach libcurl where to properly find libnsspem.so and
libnssckbi.so. The problem is that libnsspem.so is installed under
/usr/lib/$(DEB_HOST_ARCH)/nss/, while libnssckbi.so is installed under
/usr/lib/$(DEB_HOST_ARCH)/, but I mistakenly pointed libcurl to look
under the "/nss/" directory for both libraries. As it turns out,
libnssckbi.so is necessary in order to use the Mozilla's root
certificate.
[ Original Description ]
[ Clone of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034359 ]
Between 7.88.1-2 and 7.88.1-5, there was a change to where curl with
nss looks for loadable libraries:
curl (7.88.1-4) unstable; urgency=medium
* d/p/Use-correct-path-when-loading-libnss-pem-ckbi-.so.patch:
Prepend "/nss/" before the library name.
Before the change to the load path, curl could find
/lib/x86_64-linux-gnu/libnssckbi.so but not
/lib/x86_64-linux-gnu/nss/libnsspem.so, after the change it's the
reverse.
libnssckbi.so is enough to get a trust root (the mozilla certificate
store is compiled inside that library), whereas libnsspem.so
(1.0.8+1-1) isn't.
This makes it impossible to connect to https servers by default for
programs that use curl with NSS.
Here is a way to test the regression:
debbisect -v --cache=./cache \
--depends=libcurl4-nss-dev,git,pkg-config,libssl-dev,ca-certificates,cargo,nss-plugin-pem,p11-kit-modules,strace
\
20230306T145638Z 20230306T203828Z \
'chroot "$1" bash -exuc "
git clone --depth 1 https://github.com/alexcrichton/curl-rust.git
cd curl-rust
time cargo fetch
time cargo build --offline --example https
strace -efile target/debug/examples/https >/dev/null
"'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2016439/+subscriptions
--
Mailing list:
[Touch-packages] [Bug 2016439] Re: Regression finding system certificates
I just checked and a rebuild of the test app is not necessary, which is
good, otherwise we would have to chase down anything in the archive that
linked with the libcurl3-nss library package and rebuild those.
--
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/2016439
Title:
Regression finding system certificates
Status in curl package in Ubuntu:
Fix Released
Status in curl source package in Lunar:
Fix Released
Status in curl source package in Mantic:
Fix Released
Status in curl package in Debian:
Fix Released
Bug description:
[ Impact ]
Users of applications that link against libcurl's NSS flavour might
experience issues when trying to contact HTTPS servers. This can lead
to scenarios where the application is unable to connect.
[ Test Plan ]
First, let's verify that the GNUTLS flavour of libcurl does the right
thing:
$ lxc launch ubuntu-daily:lunar curl-bug2016439
$ lxc shell curl-bug2016439
# apt update && apt install -y libcurl4-gnutls-dev gcc
# cat > curl-test.c << __EOF__
#include
#include
int main(void)
{
CURL *curl;
CURLcode res;
curl = curl_easy_init();
if(curl) {
curl_easy_setopt(curl, CURLOPT_URL, "https://example.com;);
/* example.com is redirected, so we tell libcurl to follow redirection */
curl_easy_setopt(curl, CURLOPT_FOLLOWLOCATION, 1L);
/* Perform the request, res will get the return code */
res = curl_easy_perform(curl);
/* Check for errors */
if(res != CURLE_OK)
fprintf(stderr, "curl_easy_perform() failed: %s\n",
curl_easy_strerror(res));
/* always cleanup */
curl_easy_cleanup(curl);
}
return 0;
}
__EOF__
# gcc curl-test.c -o curl-test -lcurl
# ./curl-test
Example Domain
...
#
You should see the HTML dump of example.com. Now, let's install the
NSS flavour of libcurl and recompile the test program against it:
# apt install -y libcurl4-nss-dev
# gcc curl-test.c -o curl-test -lcurl
# ./curl-test
curl_easy_perform() failed: SSL peer certificate or SSH remote key was not OK
As we can see, there was an error when validating the TLS certificate.
[ Where problems could occur ]
The adjustment needed to the downstream patch is pretty simple and has
been tested extensively. The original reporter mentioned that the
issue did not happen before this patch was applied, so in the unlikely
event of a regression the best route would be to revert the patch
entirely.
[ More Info ]
This happens because of an error in one of our patches (authored by
me) to teach libcurl where to properly find libnsspem.so and
libnssckbi.so. The problem is that libnsspem.so is installed under
/usr/lib/$(DEB_HOST_ARCH)/nss/, while libnssckbi.so is installed under
/usr/lib/$(DEB_HOST_ARCH)/, but I mistakenly pointed libcurl to look
under the "/nss/" directory for both libraries. As it turns out,
libnssckbi.so is necessary in order to use the Mozilla's root
certificate.
[ Original Description ]
[ Clone of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034359 ]
Between 7.88.1-2 and 7.88.1-5, there was a change to where curl with
nss looks for loadable libraries:
curl (7.88.1-4) unstable; urgency=medium
* d/p/Use-correct-path-when-loading-libnss-pem-ckbi-.so.patch:
Prepend "/nss/" before the library name.
Before the change to the load path, curl could find
/lib/x86_64-linux-gnu/libnssckbi.so but not
/lib/x86_64-linux-gnu/nss/libnsspem.so, after the change it's the
reverse.
libnssckbi.so is enough to get a trust root (the mozilla certificate
store is compiled inside that library), whereas libnsspem.so
(1.0.8+1-1) isn't.
This makes it impossible to connect to https servers by default for
programs that use curl with NSS.
Here is a way to test the regression:
debbisect -v --cache=./cache \
--depends=libcurl4-nss-dev,git,pkg-config,libssl-dev,ca-certificates,cargo,nss-plugin-pem,p11-kit-modules,strace
\
20230306T145638Z 20230306T203828Z \
'chroot "$1" bash -exuc "
git clone --depth 1 https://github.com/alexcrichton/curl-rust.git
cd curl-rust
time cargo fetch
time cargo build --offline --example https
strace -efile target/debug/examples/https >/dev/null
"'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2016439/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics
** Description changed: After today's Ubuntu 22.04 mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi - There is a bypass listed in that article. Not sure if this is an issue - with mesa or Chrome or specific machine graphics or an interaction - between them. + There are several useful pointers and bypasses listed in that AskUbuntu + link (one being to remove affected users' GPUCache directories, which + does not destroy their profiles, and seems to work in many but not all + cases). + + Not sure if this is an issue with mesa or Chrome or specific machine + graphics or an interaction between them. ** Description changed: After today's Ubuntu 22.04 mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which - does not destroy their profiles, and seems to work in many but not all + does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with mesa or Chrome or specific machine graphics or an interaction between them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After mesa upgrades, Chrome won't show graphics Status in mesa package in Ubuntu: Confirmed Bug description: After today's Ubuntu 22.04 mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2020604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 2016439] Update Released
The verification of the Stable Release Update for curl 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 curl in Ubuntu.
https://bugs.launchpad.net/bugs/2016439
Title:
Regression finding system certificates
Status in curl package in Ubuntu:
Fix Released
Status in curl source package in Lunar:
Fix Released
Status in curl source package in Mantic:
Fix Released
Status in curl package in Debian:
Fix Released
Bug description:
[ Impact ]
Users of applications that link against libcurl's NSS flavour might
experience issues when trying to contact HTTPS servers. This can lead
to scenarios where the application is unable to connect.
[ Test Plan ]
First, let's verify that the GNUTLS flavour of libcurl does the right
thing:
$ lxc launch ubuntu-daily:lunar curl-bug2016439
$ lxc shell curl-bug2016439
# apt update && apt install -y libcurl4-gnutls-dev gcc
# cat > curl-test.c << __EOF__
#include
#include
int main(void)
{
CURL *curl;
CURLcode res;
curl = curl_easy_init();
if(curl) {
curl_easy_setopt(curl, CURLOPT_URL, "https://example.com;);
/* example.com is redirected, so we tell libcurl to follow redirection */
curl_easy_setopt(curl, CURLOPT_FOLLOWLOCATION, 1L);
/* Perform the request, res will get the return code */
res = curl_easy_perform(curl);
/* Check for errors */
if(res != CURLE_OK)
fprintf(stderr, "curl_easy_perform() failed: %s\n",
curl_easy_strerror(res));
/* always cleanup */
curl_easy_cleanup(curl);
}
return 0;
}
__EOF__
# gcc curl-test.c -o curl-test -lcurl
# ./curl-test
Example Domain
...
#
You should see the HTML dump of example.com. Now, let's install the
NSS flavour of libcurl and recompile the test program against it:
# apt install -y libcurl4-nss-dev
# gcc curl-test.c -o curl-test -lcurl
# ./curl-test
curl_easy_perform() failed: SSL peer certificate or SSH remote key was not OK
As we can see, there was an error when validating the TLS certificate.
[ Where problems could occur ]
The adjustment needed to the downstream patch is pretty simple and has
been tested extensively. The original reporter mentioned that the
issue did not happen before this patch was applied, so in the unlikely
event of a regression the best route would be to revert the patch
entirely.
[ More Info ]
This happens because of an error in one of our patches (authored by
me) to teach libcurl where to properly find libnsspem.so and
libnssckbi.so. The problem is that libnsspem.so is installed under
/usr/lib/$(DEB_HOST_ARCH)/nss/, while libnssckbi.so is installed under
/usr/lib/$(DEB_HOST_ARCH)/, but I mistakenly pointed libcurl to look
under the "/nss/" directory for both libraries. As it turns out,
libnssckbi.so is necessary in order to use the Mozilla's root
certificate.
[ Original Description ]
[ Clone of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034359 ]
Between 7.88.1-2 and 7.88.1-5, there was a change to where curl with
nss looks for loadable libraries:
curl (7.88.1-4) unstable; urgency=medium
* d/p/Use-correct-path-when-loading-libnss-pem-ckbi-.so.patch:
Prepend "/nss/" before the library name.
Before the change to the load path, curl could find
/lib/x86_64-linux-gnu/libnssckbi.so but not
/lib/x86_64-linux-gnu/nss/libnsspem.so, after the change it's the
reverse.
libnssckbi.so is enough to get a trust root (the mozilla certificate
store is compiled inside that library), whereas libnsspem.so
(1.0.8+1-1) isn't.
This makes it impossible to connect to https servers by default for
programs that use curl with NSS.
Here is a way to test the regression:
debbisect -v --cache=./cache \
--depends=libcurl4-nss-dev,git,pkg-config,libssl-dev,ca-certificates,cargo,nss-plugin-pem,p11-kit-modules,strace
\
20230306T145638Z 20230306T203828Z \
'chroot "$1" bash -exuc "
git clone --depth 1 https://github.com/alexcrichton/curl-rust.git
cd curl-rust
time cargo fetch
time cargo build --offline --example https
strace -efile target/debug/examples/https >/dev/null
"'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2016439/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 2020789] Re: pcscd should depend on vsmartcard-vpcd
I guess you have a file in /etc/reader.conf.d/ with a configuration referencing /usr/lib/pcsc/drivers/serial/libifdvpcd.so Exact? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/2020789 Title: pcscd should depend on vsmartcard-vpcd Status in pcsc-lite package in Ubuntu: New Bug description: If I install pcscd but not vsmartcard-vpcd, the service fails to start: ---> × pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; preset: enabled) Active: failed (Result: exit-code) since Thu 2023-05-25 16:11:31 CEST; 1min 52s ago Duration: 59ms TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Process: 410224 ExecStart=/usr/sbin/pcscd --foreground --auto-exit $PCSCD_ARGS (code=exited, status=1/FAILURE) Main PID: 410224 (code=exited, status=1/FAILURE) CPU: 8ms mai 25 16:11:30 canonical systemd[1]: Started pcscd.service - PC/SC Smart Card Daemon. mai 25 16:11:31 canonical pcscd[410224]: configfile.l:163:evaluatetoken() Error with library /usr/lib/pcsc/drivers/serial/libifdvpcd.so: No such file or directory mai 25 16:11:31 canonical pcscd[410224]: 00017989 pcscdaemon.c:835:clean_temp_files() Cannot remove /run/pcscd/pcscd.pid: No such file or directory mai 25 16:11:31 canonical systemd[1]: pcscd.service: Main process exited, code=exited, status=1/FAILURE mai 25 16:11:31 canonical systemd[1]: pcscd.service: Failed with result 'exit-code'. <--- Should pcscd depend on it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/2020789/+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 2020812] [NEW] Unable to change color highlight in apt output
Public bug reported: Ubuntu Release: lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Source package and version: dpkg-query -W apt apt 2.4.9 Binary apt command has support for color output on some commands such as "apt list " Where enabled the default color output is unbolded green color. This is due to the apt configuration item, APT::Color::Highlight being set to the default ANSI color code of "\x1B[32m", Setting it to another ANSI code should alter the apt output. Expectation:Setting the Highlight configuration option to another ANSI code should alter the apt output to the specified color code. $ apt list apt -o apt::color::highlight="\x1b[31m" should set the highlighted package name to an unbold red color. What happens: $ apt list apt -o apt::color::highlight="\x1b[31m" Listing... Done \x1b[31mapt/jammy-updates,now 2.4.9 amd64 [installed,automatic] \x1b[31mapt/jammy-updates 2.4.9 i386 Prepends literal string of \x1b[31m instead of producing colored output. "\033[31m" doesn't work either. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/2020812 Title: Unable to change color highlight in apt output Status in apt package in Ubuntu: New Bug description: Ubuntu Release: lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 Source package and version: dpkg-query -W apt apt 2.4.9 Binary apt command has support for color output on some commands such as "apt list " Where enabled the default color output is unbolded green color. This is due to the apt configuration item, APT::Color::Highlight being set to the default ANSI color code of "\x1B[32m", Setting it to another ANSI code should alter the apt output. Expectation:Setting the Highlight configuration option to another ANSI code should alter the apt output to the specified color code. $ apt list apt -o apt::color::highlight="\x1b[31m" should set the highlighted package name to an unbold red color. What happens: $ apt list apt -o apt::color::highlight="\x1b[31m" Listing... Done \x1b[31mapt/jammy-updates,now 2.4.9 amd64 [installed,automatic] \x1b[31mapt/jammy-updates 2.4.9 i386 Prepends literal string of \x1b[31m instead of producing colored output. "\033[31m" doesn't work either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2020812/+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 2020814] [NEW] xmllint does not recognize emdash ( )
Public bug reported:
I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to build
a PDF. One of the steps I use in my build script is to validate and format the
XML using xmllint from libxml2-utils
2.9.13+dfsg-1ubuntu0.3:
echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."
echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."
When I added an emdash () the book failed to format:
Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
injections are remediated using several methods. And two output devices
^
ch02.xml:58: parser error : Entity 'mdash' not defined
methods. And two output devices the printer and plaintext email
^
Complete.
The text is:
... And two output devices the printer and plaintext
email do not require...
It seems like emdash should be recognized.
-
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename: jammy
-
$ xmllint --version
xmllint: using libxml version 20913
compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma
$ command -v xmllint
/usr/bin/xmllint
$ dpkg -S /usr/bin/xmllint
libxml2-utils: /usr/bin/xmllint
$ apt-cache show libxml2-utils
Package: libxml2-utils
Architecture: amd64
Version: 2.9.13+dfsg-1ubuntu0.3
Multi-Arch: foreign
Priority: optional
Section: text
Source: libxml2
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian XML/SGML Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 202
Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
Filename: pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
Size: 40192
MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
SHA512:
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
Homepage: http://xmlsoft.org
...
** Affects: libxml2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020814
Title:
xmllint does not recognize emdash ()
Status in libxml2 package in Ubuntu:
New
Bug description:
I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to
build a PDF. One of the steps I use in my build script is to validate and
format the XML using xmllint from libxml2-utils
2.9.13+dfsg-1ubuntu0.3:
echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."
echo "Formatting source code..."
for file in *.xml
do
if xmllint --format "${file}" --output "${file}.format"
then
mv "${file}.format" "${file}"
fi
done
echo "Complete."
When I added an emdash () the book failed to format:
Validating book...
Complete.
Formatting source code...
ch02.xml:58: parser error : Entity 'mdash' not defined
injections are remediated using several methods. And two output devices
^
ch02.xml:58: parser error : Entity 'mdash' not defined
methods. And two output devices the printer and plaintext email
^
Complete.
The text is:
... And two output devices the printer and plaintext
email do not require...
It seems like emdash should be recognized.
-
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename: jammy
-
$ xmllint --version
xmllint: using libxml version 20913
compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma
$ command -v
