[Touch-packages] [Bug 2059417] Re: Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)
It’s 5.4.5, so “no, but it does not contain the known backdoor”. Both Debian and Ubuntu are currently analysing what needs to be done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2059417 Title: Sync xz-utils 5.6.1-1 (main) from Debian unstable (main) Status in xz-utils package in Ubuntu: Won't Fix Bug description: Please sync xz-utils 5.6.1-1 (main) from Debian unstable (main) Hello! I am one of the upstream maintainers for XZ Utils. Version 5.6.1 was recently released and uploaded to Debian as a bugfix only release. Notably, this fixes a bug that causes Valgrind to issue a warning on any application dynamically linked with liblzma. This includes a lot of important applications. This could break build scripts and test pipelines that expect specific output from Valgrind in order to pass. Additionally, this fixes a small typo for the man pages translations for Brazilian Portuguese, German, French, Korean, Romanian, and Ukrainian, and removes the need for patches applied for version 5.6.0-0.2. The other bugfixes in this release have no impact on Ubuntu. They involve building with CMake or when building on a system without Landlock system calls defined (these are defined in Ubuntu). Changelog entries since current noble version 5.6.0-0.2: xz-utils (5.6.1-1) unstable; urgency=medium * Non-maintainer upload. * Import 5.6.1 (Closes: #1067708). * Takeover maintenance of the package. -- Sebastian Andrzej Siewior Wed, 27 Mar 2024 22:53:21 +0100 Excerpt from the NEWS entry from upstream: 5.6.1 (2024-03-09) * liblzma: Fixed two bugs relating to GNU indirect function (IFUNC) with GCC. The more serious bug caused a program linked with liblzma to crash on start up if the flag -fprofile-generate was used to build liblzma. The second bug caused liblzma to falsely report an invalid write to Valgrind when loading liblzma. * xz: Changed the messages for thread reduction due to memory constraints to only appear under the highest verbosity level. * Build: - Fixed a build issue when the header file was present on the system but the Landlock system calls were not defined in . - The CMake build now warns and disables NLS if both gettext tools and pre-created .gmo files are missing. Previously, this caused the CMake build to fail. * Minor improvements to man pages. * Minor improvements to tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2059417/+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 2032577] Re: xz crashed with SIGSEGV in lzma_lzma_optimum_normal
That sounds even more like a RAM issue (that it stopped occurring with the same kernel and software version). Perhaps when you switched away from Wayland, your graphics card is now used less heavily, and when the GPU was used more, the RAM got hotter or got minimally less power and therefore had issues, or something. (This is something people have indeed seen, so…) If you can trigger it reliably again, the changes would indeed be interesting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2032577 Title: xz crashed with SIGSEGV in lzma_lzma_optimum_normal Status in xz-utils package in Ubuntu: New Bug description: xz segfaults. More details in https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379 From Dmesg.txt on that report [114838.184191] xz[431483]: segfault at 7f9a93f3701a ip 7f9b3f780c1a sp 7f9a957baa50 error 4 in liblzma.so.5.2.5[7f9b3f771000+1b000] ProblemType: Crash ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 ExecutablePath: /usr/bin/xz ExecutableTimestamp: 1649422298 InstallationDate: Installed on 2021-04-09 (863 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: xz-utils 5.2.5-2ubuntu1 ProcCmdline: xz --check=crc32 --threads=0 -c /var/tmp/mkinitramfs-MAIN_E1GbD9 ProcCwd: / ProcEnviron: LC_CTYPE=C.UTF-8 TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 SegvAnalysis: Segfault happened at: 0x7f9b3f780c1a:movzbl (%rdi,%r8,1),%r10d PC (0x7f9b3f780c1a) ok source "(%rdi,%r8,1)" (0x7f9a93f3701a) in non-readable VMA region: 0x7f9a90021000-0x7f9a9400 ---p None destination "%r10d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading VMA None Signal: 11 SourcePackage: xz-utils Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-01-29 (204 days ago) UserGroups: N/A StacktraceTop: bt_find_func (len_limit=64, pos=9137198, cur=0x7f9a943edc3d "", cur_match=4194304, depth=24, son=son@entry=0x7f9a8afbd010, cyclic_pos=748589, cyclic_size=8388609, matches=0x7f9adc0ec324, len_best=11) at ../../../../src/liblzma/lz/lz_encoder_mf.c:483 lzma_mf_bt4_find (mf=0x7f9a9c70, matches=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:721 lzma_mf_find (mf=mf@entry=0x7f9a9c70, count_ptr=count_ptr@entry=0x7f9adc0ecb94, matches=matches@entry=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:28 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:846 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2032577/+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 1307883] Re: ca-certificates-java misses runtime dependency on initscripts
openjdk-8 fixed this by introducing explicit dependencies on the package carrying mountpoint: ifneq (,$(filter $(distrel),wheezy jessie precise trusty)) control_vars += '-Vmountpoint:Depends=initscripts' else control_vars += '-Vmountpoint:Depends=util-linux (>= 2.26.2-4)' endif ** Changed in: openjdk-8 (Ubuntu) Status: Confirmed => Fix Released -- 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/1307883 Title: ca-certificates-java misses runtime dependency on initscripts Status in ca-certificates-java package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Confirmed Status in openjdk-8 package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Triaged Bug description: Jitsi build-depends on openjdk-7-jre but the package fails to install in pbuilder and thus I currently cannot build the package. Here is the output I get while I am logged in to the trusty chroot. # aptitude install default-jdk [...] E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up ca-certificates-java (20130815ubuntu1) ... /var/lib/dpkg/info/ca-certificates-java.postinst: line 90: mountpoint: command not found the keytool command requires a mounted proc fs (/proc). dpkg: error processing package ca-certificates-java (--configure): subprocess installed post-installation script returned error exit status 1 Setting up openjdk-7-jre-headless:i386 (7u51-2.4.6-1ubuntu4) ... /var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: 18: /var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: mountpoint: not found the java command requires a mounted proc fs (/proc). dpkg: error processing package openjdk-7-jre-headless:i386 (--configure): subprocess installed post-installation script returned error exit status 1 Setting up default-jre-headless (2:1.7-51) ... dpkg: dependency problems prevent configuration of openjdk-7-jre:i386: openjdk-7-jre:i386 depends on openjdk-7-jre-headless (= 7u51-2.4.6-1ubuntu4); however: Package openjdk-7-jre-headless:i386 is not configured yet. dpkg: error processing package openjdk-7-jre:i386 (--configure): dependency problems - leaving unconfigured Setting up default-jre (2:1.7-51) ... dpkg: dependency problems prevent configuration of openjdk-7-jdk:i386: openjdk-7-jdk:i386 depends on openjdk-7-jre (= 7u51-2.4.6-1ubuntu4); however: Package openjdk-7-jre:i386 is not configured yet. dpkg: error processing package openjdk-7-jdk:i386 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of default-jdk: default-jdk depends on openjdk-7-jdk (>= 7~u3-2.1.1); however: Package openjdk-7-jdk:i386 is not configured yet. dpkg: error processing package default-jdk (--configure): dependency problems - leaving unconfigured Processing triggers for ca-certificates (20130906ubuntu2) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d /etc/ca-certificates/update.d/jks-keystore: 33: /etc/ca-certificates/update.d/jks-keystore: mountpoint: not found the keytool command requires a mounted proc fs (/proc). E: /etc/ca-certificates/update.d/jks-keystore exited with code 1. done. Errors were encountered while processing: ca-certificates-java openjdk-7-jre-headless:i386 openjdk-7-jre:i386 openjdk-7-jdk:i386 default-jdk # mount /proc on /proc type proc (rw,relatime) tmpfs on /run/shm type tmpfs (rw,relatime) /dev/pts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1307883/+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 993843] Re: Bluetooth keyboard unavailable during LUKS disk unlocking
@zwingo (and for reference if somebody wants to tackle this): Same keyboard here with an MX Master mouse. Both devices (and some other bluetooth devices iiuc) do not indicate a class in `/var/lib/bluetooth/*/*/info`. However, I think one could grep for Bluetooth Appearance values in addition: ``` APPEARANCE_HID_KEYBOARD 961 --> works for K860 keyboard (Appearance=0x03c1) APPEARANCE_HID_MOUSE962 --> works for MX Master (Appearance=0x03c2) ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/993843 Title: Bluetooth keyboard unavailable during LUKS disk unlocking Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I need to keep a spare USB keyboard around to be able to boot my system. Having bluetooth keyboard support in initramfs would make that unnecessary. A trimmed down bluez in the initramfs will solve the problem. It would also need access to a copy of /var/lib/bluetooth in, say, /boot/bluetooth. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/993843/+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 2028571] Re: klibc-utils contains identical binaries
jdupes normally considers hardlinks as one. And, indeed, on my Debian system, I see: -rwxr-xr-x 1 root root 36656 May 27 2021 gunzip* -rwxr-xr-x 1 root root 36656 May 27 2021 gzip* These aren’t hardlinks. And indeed they aren’t hardlinks in the Debian binary package either: $ paxtar -xOf klibc-utils_2.0.8-6.1_amd64.deb data.tar.xz | xz -d | paxtar -tvf - | fgrep zip -rwxr-xr-x 1 root root 36656 May 27 2021 ./usr/lib/klibc/bin/gunzip -rwxr-xr-x 1 root root 36656 May 27 2021 ./usr/lib/klibc/bin/gzip debian/klibc-utils.install just has: usr/lib/klibc/bin/* These get placed there by: override_dh_auto_install: $(MAKE) install $(KLIBC_MAKEFLAGS) Upstream usr/gzip/Kbuild does hardlink them in the build directory: $(obj)/gunzip $(obj)/zcat: $(obj)/gzip $(call cmd,ln) The upstream “make install” call causes execution of: install -m 755 usr/gzip/gzip usr/gzip/gunzip usr/gzip/zcat ../tmp/usr/lib/klibc/bin And, indeed, this breaks up the hardlink. I see two actions arising from this: ① The Debian packaging probably should run something like… for pkgtopdir in debian/*/; do jdupes -rL "$pkgtopdir"; done … after installing all the files. @maximilian attems, are you reading? ② Upstream should probably not use install(1) to install hardlinked files; perhaps recreate the hardlinks in the destination like the BSDs do? I’ll forward this to the upstream mailing list. ** Changed in: klibc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2028571 Title: klibc-utils contains identical binaries Status in klibc package in Ubuntu: Confirmed Bug description: ``` $ jdupes -r /usr/lib/klibc/bin Scanning: 38 files, 1 items (in 1 specified) /usr/lib/klibc/bin/gunzip /usr/lib/klibc/bin/gzip /usr/lib/klibc/bin/zcat /usr/lib/klibc/bin/halt /usr/lib/klibc/bin/poweroff /usr/lib/klibc/bin/reboot ``` Please replace these binaries with symlinks to reduce the size of the uncompressed initramfs. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: klibc-utils 2.0.12-1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jul 24 21:14:36 2023 Dependencies: libklibc 2.0.12-1 InstallationDate: Installed on 2022-03-20 (491 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: klibc UpgradeStatus: Upgraded to lunar on 2023-04-20 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/2028571/+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] Re: xmllint does not recognize emdash (— )
Hmm. I normally use libxml2 via xmlstarlet which has a somewhat nicer UX
than xmllint.
My guess is that you didn’t give a DTD, so it could only check that all
present entities are syntactically valid, but not expand them.
--
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:
Invalid
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 2020814] Re: xmllint does not recognize emdash (— )
Yeah well, those portability problems were back in the 1990s when people
used latin1 or whatever codepages.
** Changed in: libxml2 (Ubuntu)
Status: New => Invalid
--
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:
Invalid
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 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 2003826] [NEW] klibc/s390x on focal has broken setjmp/longjmp
Public bug reported: This is the same as https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=943425 which is fixed in Debian bullseye and Ubuntu impish but still present in focal. ** Affects: klibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2003826 Title: klibc/s390x on focal has broken setjmp/longjmp Status in klibc package in Ubuntu: New Bug description: This is the same as https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=943425 which is fixed in Debian bullseye and Ubuntu impish but still present in focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/2003826/+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 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Have you considered informing klibc upstream? (Granted, save for hpa that’s basically the Debian maintainers, but they don’t necessarily get Launchpad bugreports either.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1921476] Re: systemd-resolved error while reading 'ReadEtcHosts' config option
I guess this config option is not available in 18.04. can be closed. ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/systemd/+question/696259 -- 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/1921476 Title: systemd-resolved error while reading 'ReadEtcHosts' config option Status in systemd package in Ubuntu: Invalid Bug description: [~] # cat /etc/systemd/resolved.conf [Resolve] DNS=8.8.8.8 8.8.4.4 2001:4860:4860:: Domains= DNSStubListener=yes ReadEtcHosts=yes if my configs looks like this (above) I get the following error message at startup systemd-resolved[21573]: /etc/systemd/resolved.conf:5: Unknown lvalue 'ReadEtcHosts' in section 'Resolve' my systemd-version is the following systemd-resolve --version systemd 237 [~] # lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 [~] # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.45 Candidate: 237-3ubuntu10.45 Version table: *** 237-3ubuntu10.45 500 All updates of Ubuntu installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1921476/+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 1921476] [NEW] systemd-resolved error while reading 'ReadEtcHosts' config option
Public bug reported: [~] # cat /etc/systemd/resolved.conf [Resolve] DNS=8.8.8.8 8.8.4.4 2001:4860:4860:: Domains= DNSStubListener=yes ReadEtcHosts=yes if my configs looks like this (above) I get the following error message at startup systemd-resolved[21573]: /etc/systemd/resolved.conf:5: Unknown lvalue 'ReadEtcHosts' in section 'Resolve' my systemd-version is the following systemd-resolve --version systemd 237 [~] # lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 [~] # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.45 Candidate: 237-3ubuntu10.45 Version table: *** 237-3ubuntu10.45 500 All updates of Ubuntu installed. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1921476 Title: systemd-resolved error while reading 'ReadEtcHosts' config option Status in systemd package in Ubuntu: New Bug description: [~] # cat /etc/systemd/resolved.conf [Resolve] DNS=8.8.8.8 8.8.4.4 2001:4860:4860:: Domains= DNSStubListener=yes ReadEtcHosts=yes if my configs looks like this (above) I get the following error message at startup systemd-resolved[21573]: /etc/systemd/resolved.conf:5: Unknown lvalue 'ReadEtcHosts' in section 'Resolve' my systemd-version is the following systemd-resolve --version systemd 237 [~] # lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 [~] # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.45 Candidate: 237-3ubuntu10.45 Version table: *** 237-3ubuntu10.45 500 All updates of Ubuntu installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1921476/+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 1729558] Re: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements
As far as I see, openjdk-8 (8u275-b01-1) contains this patch, so it was backported upstream. ** Changed in: openjdk-8 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1729558 Title: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements Status in Ubuntu theme: Invalid Status in openjdk-8 package in Ubuntu: Fix Released Status in openjdk-9 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: This fix, #961679, specifically Ambiance/gtk-2.0/gtkrc:346 (http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu- themes/trunk/revision/583), makes disabled elements in menus look terrible. Unfortunately I'm not aware of an easy way to get screenshots of open menus, so hopefully these attached phone pictures of Netbeans are enough to illustrate the issue. As you can see it is hard to tell the difference between what is disabled and what isn't, and the disabled items look fuzzy (easier to observe on monitor). I really don't see the issue with lighter menus, but if they must stay dark then the readability / contrast of disabled items needs to be fixed. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1729558/+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 1873907] [NEW] initramfs no dhcp because of 'Error getting hardware address for " en2s0": No such device'
Public bug reported:
kernel cmdline "ip=dhcp"
results in:
Error getting hardware address for " en2s0": No such device
No network during boot
I have to change /usr/share/initramfs-tools/scripts/functions
fix:
run_dhclient() {
...
dhclient -v -1 -cf "$conffile" -pf "$pidfile" "$@"
to
dhclient -v -1 -cf "$conffile" -pf "$pidfile" $@
regards
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: initramfs-tools-core 0.136ubuntu6 [modified:
usr/share/initramfs-tools/hook-functions
usr/share/initramfs-tools/scripts/functions]
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Apr 20 18:49:00 2020
InstallationDate: Installed on 2020-04-18 (2 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873907
Title:
initramfs no dhcp because of 'Error getting hardware address for "
en2s0": No such device'
Status in initramfs-tools package in Ubuntu:
New
Bug description:
kernel cmdline "ip=dhcp"
results in:
Error getting hardware address for " en2s0": No such device
No network during boot
I have to change /usr/share/initramfs-tools/scripts/functions
fix:
run_dhclient() {
...
dhclient -v -1 -cf "$conffile" -pf "$pidfile" "$@"
to
dhclient -v -1 -cf "$conffile" -pf "$pidfile" $@
regards
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: initramfs-tools-core 0.136ubuntu6 [modified:
usr/share/initramfs-tools/hook-functions
usr/share/initramfs-tools/scripts/functions]
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Apr 20 18:49:00 2020
InstallationDate: Installed on 2020-04-18 (2 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1873907/+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 1873591] [NEW] initramfs-tools-core multiarch dns problem
Public bug reported: Hi, in x86_64 multiarch environment the hook-functions -> add_dns() copy i386 libdns instead of 64bit one. in add_dns() i replace for f in "$d"/libc.so.?; do [ -f "$f" ] && break; done with for f in "$d"/libc.so; do [ -f "$f" ] && break; done to fix the problem regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools-core 0.136ubuntu6 [modified: usr/share/initramfs-tools/hook-functions] ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Apr 18 21:10:51 2020 InstallationDate: Installed on 2020-04-18 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1873591 Title: initramfs-tools-core multiarch dns problem Status in initramfs-tools package in Ubuntu: New Bug description: Hi, in x86_64 multiarch environment the hook-functions -> add_dns() copy i386 libdns instead of 64bit one. in add_dns() i replace for f in "$d"/libc.so.?; do [ -f "$f" ] && break; done with for f in "$d"/libc.so; do [ -f "$f" ] && break; done to fix the problem regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools-core 0.136ubuntu6 [modified: usr/share/initramfs-tools/hook-functions] ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Apr 18 21:10:51 2020 InstallationDate: Installed on 2020-04-18 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1873591/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
Yeah, I saw the mail; much better. I fixed one of these in dietlibc the other day… -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Status in klibc source package in Focal: Confirmed Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
How is this even a fix? Also, does this affect other applications built against klibc? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Status in klibc source package in Focal: Confirmed Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
Fun: this works with 2.0.7-1 built with gcc-9 in Debian. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in klibc package in Ubuntu: New Bug description: http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+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] Fwd: [Bug 1843743] Re: klibc ftbfs in eoan
-- Forwarded message -- From: Adam Conrad Message-ID: <157106879908.15546.2658970073129703906.mal...@soybean.canonical.com> 2.0.7-1 fails to build in the same way on Ubuntu 19.10. I'm assuming it's either glibc 2.30 (Debian is at 2.29) or linux 5.3 (Debian is at 5.2), with the latter being more likely. -- You received this bug notification because you are subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+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 1843743] Re: klibc ftbfs in eoan
Probably fixed in 2.0.7 which fixed a parallel make issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+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 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
The testcase needs the “package test;” in the first line removed / commented-out, then it works. This works in 11.0.1+13-2 on Debian sid, as a new data point. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in freetype package in Ubuntu: Confirmed Status in openjdk-lts package in Ubuntu: New Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+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 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
works perfect! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Won't Fix Status in cryptsetup package in Ubuntu: Fix Released Status in cryptsetup source package in Bionic: Fix Committed Bug description: SRU for bionic: Acceptance criteria: An encrypted partition can be decrypted using cryptroot-unlock. Regression potential: It's not the default method, so unused by the majority of people. Besides that the patched script runs fine in cosmic. The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+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 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
@Trent Nelson: thanks for the patch! I applied it and it's working flawlessly! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Confirmed Status in cryptsetup package in Ubuntu: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+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 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
pls fix this! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Confirmed Status in cryptsetup package in Ubuntu: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+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 1772638] Re: Segfault in libmutter-2.so after suspend/resume using wayland. Core files are always truncated and invalid while the default shell is zsh.
O error handler doing an exit(), pid = 1725, errno = 11 Mai 22 13:11:15 x1 org.gnome.SettingsDaemon.Power.desktop[1611]: xcb_connection_has_error() returned true Mai 22 13:11:15 x1 firefox.desktop[2050]: xcb_connection_has_error() returned true Mai 22 13:11:15 x1 pulseaudio[2430]: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true Mai 22 13:11:15 x1 polkitd(authority=local)[1059]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.74, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Mai 22 13:11:15 x1 rtkit-daemon[1171]: Successfully made thread 2434 of process 2434 (n/a) owned by '1000' high priority at nice level -11. Mai 22 13:11:15 x1 rtkit-daemon[1171]: Supervising 2 threads of 2 processes of 1 users. Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] pid.c: Stale PID file, overwriting. Mai 22 13:11:15 x1 gdm-password][1430]: pam_unix(gdm-password:session): session closed for user thorsten Mai 22 13:11:15 x1 gsd-color[1217]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_AU_Optronics_thorsten_1000 Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] sink.c: Default and alternate sample rates are the same. ... followup crashes... Moreover, here is the apport.log: ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: called for pid 1483, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: debug: session gdbus call: (true,) ERROR: apport (pid 2357) Tue May 22 13:11:15 2018: wrote report /var/crash/_usr_bin_gnome-shell.1000.crash ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: called for pid 1502, signal 6, core limit 18446744073709551615, dump mode 1 ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: ignoring implausibly big core limit, treating as unlimited ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: executable: /usr/bin/Xwayland (command line "/usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6") ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: debug: session gdbus call: ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: wrote report /var/crash/_usr_bin_Xwayland.1000.crash ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: writing core dump to /home/thorsten/core (limit: -1) ERROR: apport (pid 2429) Tue May 22 13:11:20 2018: writing core dump /home/thorsten/core of size 107855872 Additionally, i have ~100MB "core" file in my home directory. I tried to report the created _usr_bin_gnome-shell.1000.crash file using the workaround from https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 and ubuntu-bug. However, i get the error: "The problem cannot be reported: Invalid core dump: BFD: warning /tmp/apport_core_ersfx7ym is truncated: expected core file size >= 846290944, found: 216288" reporting the corresponding _usr_bin_Xwayland.1000.crash file forwards me to https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911. But this only seems to indicate that Xwayland crashes since mutter has crashed. This error only occurs when using the wayland and not in the xorg session. I am running 4.16.10 mainline kernel due to some driver issues with my laptop (thinkpad x1 carbon gen6) but this also occurs when using the 4.15 kernel and with and without loading the guc firmware. Thanks! --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 PackageArchitecture: amd64 Tags: wayland-session bionic Uname: Linux 4.16.10-041610-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1772638/+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 1765463] Re: Bionic: systemd: rename interface
the fault was somewhere else, this issue can be closed -- 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/1765463 Title: Bionic: systemd: rename interface Status in systemd package in Ubuntu: Invalid Bug description: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) apt-cache policy systemd systemd: Installed: 237-3ubuntu8 3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18 /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" /etc/systemd/netword/uplink0.link [Match] Path=pci-:02:00.0 [Link] Name=uplink0 # update-initramfs -u 4) journalctl -b | grep rename kernel: tg3 :02:00.1 eno2: renamed from eth1 kernel: tg3 :02:00.0 eno1: renamed from eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765463/+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 1765463] Re: Bionic: systemd: rename interface
typo -- 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/1765463 Title: Bionic: systemd: rename interface Status in systemd package in Ubuntu: Invalid Bug description: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) apt-cache policy systemd systemd: Installed: 237-3ubuntu8 3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18 /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" /etc/systemd/netword/uplink0.link [Match] Path=pci-:02:00.0 [Link] Name=uplink0 # update-initramfs -u 4) journalctl -b | grep rename kernel: tg3 :02:00.1 eno2: renamed from eth1 kernel: tg3 :02:00.0 eno1: renamed from eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765463/+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 1765463] Re: Bionic: systemd: rename interface
systemd.network is working cat /etc/systemd/network/uplink0.network [Match] Path=pci-:02:00.0 #Name=uplkink0 [Network] DHCP=yes networkctl status eno1 Path: pci-:02:00.0 This was no solution: cp /etc/systemd/netword/uplink0.link /lib/systemd/network/ update-initramfs -u ** Description changed: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) apt-cache policy systemd systemd: - Installed: 237-3ubuntu8 + Installed: 237-3ubuntu8 3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18 /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" - - /etc/systemd/networ/uplink0.link + /etc/systemd/netword/uplink0.link [Match] Path=pci-:02:00.0 [Link] Name=uplink0 # update-initramfs -u - 4) journalctl -b | grep rename + 4) journalctl -b | grep rename kernel: tg3 :02:00.1 eno2: renamed from eth1 kernel: tg3 :02:00.0 eno1: renamed from eth0 -- 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/1765463 Title: Bionic: systemd: rename interface Status in systemd package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) apt-cache policy systemd systemd: Installed: 237-3ubuntu8 3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18 /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" /etc/systemd/netword/uplink0.link [Match] Path=pci-:02:00.0 [Link] Name=uplink0 # update-initramfs -u 4) journalctl -b | grep rename kernel: tg3 :02:00.1 eno2: renamed from eth1 kernel: tg3 :02:00.0 eno1: renamed from eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765463/+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 1765463] [NEW] Bionic: systemd: rename interface
Public bug reported: 1) lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 2) apt-cache policy systemd systemd: Installed: 237-3ubuntu8 3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18 /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" /etc/systemd/networ/uplink0.link [Match] Path=pci-:02:00.0 [Link] Name=uplink0 # update-initramfs -u 4) journalctl -b | grep rename kernel: tg3 :02:00.1 eno2: renamed from eth1 kernel: tg3 :02:00.0 eno1: renamed from eth0 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel networ ** Package changed: linux-hwe-edge (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1765463 Title: Bionic: systemd: rename interface Status in systemd package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) apt-cache policy systemd systemd: Installed: 237-3ubuntu8 3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18 /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" /etc/systemd/networ/uplink0.link [Match] Path=pci-:02:00.0 [Link] Name=uplink0 # update-initramfs -u 4) journalctl -b | grep rename kernel: tg3 :02:00.1 eno2: renamed from eth1 kernel: tg3 :02:00.0 eno1: renamed from eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765463/+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 1765380] Re: Bionic: busybox sh preseed/late_command
If I'm using xenial and in pressed file bionic it's NOT working -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1765380 Title: Bionic: busybox sh preseed/late_command Status in busybox package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/ initrd.gz 2018-04-18 09:13 45M linux 2018-04-18 09:13 7.9M busybox: Installed: 1:1.27.2-2ubuntu3 3+4) preseed installation on Bionic, late_command almost the same in Xenial and there is working preseed.cfg d-i preseed/late_command string /tmp/late_command ls -l /bin/sh lrwxrwxrwx 1 root root 4 Sep 26 2014 /bin/sh -> busybox syslog: running: /tmp/late_command nothing happend on shell: /tmp/late_command head late_commaand #!/bin/sh printf '' > /usr/lib/finish-install.d/55netcfg-copy-config; in-target mkdir -p /opt/MegaRAID/MegaCli/; in-target mkdir -p /root/.ssh; in-target mkdir /etc/check_mk; So is there a bug in busybox sh? How can I debug busybox sh script.sh? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1765380/+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 1765380] Re: Bionic: busybox sh preseed/late_command
If I'm using xenial and in pressed file bionic it's working -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1765380 Title: Bionic: busybox sh preseed/late_command Status in busybox package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/ initrd.gz 2018-04-18 09:13 45M linux 2018-04-18 09:13 7.9M busybox: Installed: 1:1.27.2-2ubuntu3 3+4) preseed installation on Bionic, late_command almost the same in Xenial and there is working preseed.cfg d-i preseed/late_command string /tmp/late_command ls -l /bin/sh lrwxrwxrwx 1 root root 4 Sep 26 2014 /bin/sh -> busybox syslog: running: /tmp/late_command nothing happend on shell: /tmp/late_command head late_commaand #!/bin/sh printf '' > /usr/lib/finish-install.d/55netcfg-copy-config; in-target mkdir -p /opt/MegaRAID/MegaCli/; in-target mkdir -p /root/.ssh; in-target mkdir /etc/check_mk; So is there a bug in busybox sh? How can I debug busybox sh script.sh? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1765380/+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 1765380] Re: busybox sh preseed/late_command
** Also affects: busybox (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-firmware (Ubuntu) ** Summary changed: - busybox sh preseed/late_command + Bionic: busybox sh preseed/late_command ** Tags added: netinstall ** Description changed: - 1) lsb_release -rd + 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 - 2) apt-cache policy busybox - busybox: - Installed: 1:1.27.2-2ubuntu3 + 2) http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/ + initrd.gz 2018-04-18 09:13 45M + linux 2018-04-18 09:13 7.9M 3+4) preseed installation on Bionic, late_command almost the same in Xenial and there is working preseed.cfg d-i preseed/late_command string /tmp/late_command ls -l /bin/sh lrwxrwxrwx 1 root root 4 Sep 26 2014 /bin/sh -> busybox - syslog: + syslog: running: /tmp/late_command nothing happend on shell: /tmp/late_command head late_commaand #!/bin/sh printf '' > /usr/lib/finish-install.d/55netcfg-copy-config; in-target mkdir -p /opt/MegaRAID/MegaCli/; in-target mkdir -p /root/.ssh; in-target mkdir /etc/check_mk; So is there a bug in busybox sh? How can I debug busybox sh script.sh? ** Description changed: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/ initrd.gz 2018-04-18 09:13 45M linux 2018-04-18 09:13 7.9M - 3+4) preseed installation on Bionic, late_command almost the same in - Xenial and there is working + busybox: + Installed: 1:1.27.2-2ubuntu3 + + + 3+4) preseed installation on Bionic, late_command almost the same in Xenial and there is working preseed.cfg d-i preseed/late_command string /tmp/late_command ls -l /bin/sh lrwxrwxrwx 1 root root 4 Sep 26 2014 /bin/sh -> busybox syslog: running: /tmp/late_command nothing happend on shell: /tmp/late_command head late_commaand #!/bin/sh printf '' > /usr/lib/finish-install.d/55netcfg-copy-config; in-target mkdir -p /opt/MegaRAID/MegaCli/; in-target mkdir -p /root/.ssh; in-target mkdir /etc/check_mk; So is there a bug in busybox sh? How can I debug busybox sh script.sh? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1765380 Title: Bionic: busybox sh preseed/late_command Status in busybox package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/ initrd.gz 2018-04-18 09:13 45M linux 2018-04-18 09:13 7.9M busybox: Installed: 1:1.27.2-2ubuntu3 3+4) preseed installation on Bionic, late_command almost the same in Xenial and there is working preseed.cfg d-i preseed/late_command string /tmp/late_command ls -l /bin/sh lrwxrwxrwx 1 root root 4 Sep 26 2014 /bin/sh -> busybox syslog: running: /tmp/late_command nothing happend on shell: /tmp/late_command head late_commaand #!/bin/sh printf '' > /usr/lib/finish-install.d/55netcfg-copy-config; in-target mkdir -p /opt/MegaRAID/MegaCli/; in-target mkdir -p /root/.ssh; in-target mkdir /etc/check_mk; So is there a bug in busybox sh? How can I debug busybox sh script.sh? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1765380/+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 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load
i can just add that its working fine under arch. However the error occurs under ubuntu 18.04. Both use 4.15. Moreover i have a thinkpad x1 gen 6 and not a dell -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1728238 Title: update-initramfs not adding i915 GuC firmware, firmware fails to load Status in initramfs-tools: New Status in initramfs-tools package in Ubuntu: Confirmed Bug description: The i915 Kabylake GuC firmware is failing to load on boot, and generating dmesg errors. The Kabylake HuC firmware succeeds. All files exist. I've also verified the Kabylake GuC firmware matches the correct file size and md5 listed on 01.org. I then ran update-initramfs verbosely, and see that only /lib/firmware/i915/skl_guc_ver6_1.bin is being added. /lib/firmware/i915/bxt_guc_ver8_7.bin and /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored. I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and initramfs-tools 0.125ubuntu12. Perhaps Broxton systems might have the same issue? Output and logs: - ls -al /lib/firmware/i915/kbl_* -rw-r--r-- 1 root root 8616 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1_01.bin lrwxrwxrwx 1 root root 19 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin -rw-r--r-- 1 root root 142656 Oct 20 21:12 /lib/firmware/i915/kbl_guc_ver9_14.bin -rw-r--r-- 1 root root 218688 Aug 17 11:09 /lib/firmware/i915/kbl_huc_ver02_00_1810.bin sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: FAIL load: NONE version wanted: 9.14 version found: 0.0 header: offset is 0; size = 0 uCode: offset is 0; size = 0 RSA: offset is 0; size = 0 GuC status 0x0001: Bootrom status = 0x0 uKernel status = 0x0 MIA Core status = 0x0 Scratch registers: 0: 0x0 1: 0x0 2: 0x0 3: 0x0 4: 0x0 5: 0x0 6: 0x0 7: 0x0 8: 0x0 9: 0x0 10: 0x0 11: 0x0 12: 0x0 13: 0x0 14: 0x0 15: 0x0 sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status HuC firmware status: path: i915/kbl_huc_ver02_00_1810.bin fetch: SUCCESS load: SUCCESS version wanted: 2.0 version found: 2.0 header: offset is 0; size = 128 uCode: offset is 128; size = 218304 RSA: offset is 218432; size = 256 HuC status 0x6000: dmesg [1.052879] hidraw: raw HID events driver (C) Jiri Kosina [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method not found [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002) [1.082308] nvme nvme0: pci function :3c:00.0 [1.095073] Setting dangerous option enable_guc_loading - tainting kernel [1.095075] Setting dangerous option enable_guc_submission - tainting kernel [1.097867] [drm] Memory usable by graphics device = 4078M [1.097869] checking generic (9000 1fb) vs hw (9000 1000) [1.097869] fb: switching to inteldrmfb from EFI VGA [1.097899] Console: switching to colour dummy device 80x25 [1.098049] [drm] Replacing VGA console driver [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.104157] [drm] Driver supports precise vblank timestamp query. [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd [1.298572] nvme0n1: p1 p2 [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1.433243] usb 1-1: Product: USB+PS2 Keyboard [1.433244] usb 1-1: Manufacturer: Generic [1.446460] usbcore: registered new interface driver usbhid [1.446461] usbhid: USB HID core driver [1.448067] input: Generic USB+PS2 Keyboard as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7 [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0 [1.508541] input: Generic USB+PS2 Keyboard as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8 [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1 [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1.695657] usb 1-2: Product: USB Receiver [1.695658] usb 1-2: Manufacturer: Logitech [1.702641] logitech
[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load
also happens on ubuntu 18.04 on a i7-8550U [2.084195] i915 :00:02.0: Direct firmware load for i915/kbl_guc_ver9_14.bin failed with error -2 [2.084196] [drm] GuC: Failed to fetch firmware i915/kbl_guc_ver9_14.bin (error -2) [2.084197] [drm] GuC: Firmware can be downloaded from https://01.org/linuxgraphics/downloads/firmware [2.089954] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0) [2.09] [drm] GuC init failed. Firmware loading disabled. [2.090003] [drm] Falling back from GuC submission to execlist mode [2.090717] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1728238 Title: update-initramfs not adding i915 GuC firmware, firmware fails to load Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: New Bug description: The i915 Kabylake GuC firmware is failing to load on boot, and generating dmesg errors. The Kabylake HuC firmware succeeds. All files exist. I've also verified the Kabylake GuC firmware matches the correct file size and md5 listed on 01.org. I then ran update-initramfs verbosely, and see that only /lib/firmware/i915/skl_guc_ver6_1.bin is being added. /lib/firmware/i915/bxt_guc_ver8_7.bin and /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored. I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and initramfs-tools 0.125ubuntu12. Perhaps Broxton systems might have the same issue? Output and logs: - ls -al /lib/firmware/i915/kbl_* -rw-r--r-- 1 root root 8616 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1_01.bin lrwxrwxrwx 1 root root 19 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin -rw-r--r-- 1 root root 142656 Oct 20 21:12 /lib/firmware/i915/kbl_guc_ver9_14.bin -rw-r--r-- 1 root root 218688 Aug 17 11:09 /lib/firmware/i915/kbl_huc_ver02_00_1810.bin sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: FAIL load: NONE version wanted: 9.14 version found: 0.0 header: offset is 0; size = 0 uCode: offset is 0; size = 0 RSA: offset is 0; size = 0 GuC status 0x0001: Bootrom status = 0x0 uKernel status = 0x0 MIA Core status = 0x0 Scratch registers: 0: 0x0 1: 0x0 2: 0x0 3: 0x0 4: 0x0 5: 0x0 6: 0x0 7: 0x0 8: 0x0 9: 0x0 10: 0x0 11: 0x0 12: 0x0 13: 0x0 14: 0x0 15: 0x0 sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status HuC firmware status: path: i915/kbl_huc_ver02_00_1810.bin fetch: SUCCESS load: SUCCESS version wanted: 2.0 version found: 2.0 header: offset is 0; size = 128 uCode: offset is 128; size = 218304 RSA: offset is 218432; size = 256 HuC status 0x6000: dmesg [1.052879] hidraw: raw HID events driver (C) Jiri Kosina [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method not found [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002) [1.082308] nvme nvme0: pci function :3c:00.0 [1.095073] Setting dangerous option enable_guc_loading - tainting kernel [1.095075] Setting dangerous option enable_guc_submission - tainting kernel [1.097867] [drm] Memory usable by graphics device = 4078M [1.097869] checking generic (9000 1fb) vs hw (9000 1000) [1.097869] fb: switching to inteldrmfb from EFI VGA [1.097899] Console: switching to colour dummy device 80x25 [1.098049] [drm] Replacing VGA console driver [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.104157] [drm] Driver supports precise vblank timestamp query. [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd [1.298572] nvme0n1: p1 p2 [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1.433243] usb 1-1: Product: USB+PS2 Keyboard [1.433244] usb 1-1: Manufacturer: Generic [1.446460] usbcore: registered new interface driver usbhid [1.446461] usbhid: USB HID core driver [1.448067] input: Generic USB+PS2 Keyboard as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7 [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0 [1.508541] input: Generic USB+PS2 Keyboard as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/inp
[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Confirmed Status in cryptsetup package in Ubuntu: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+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 1735296] [NEW] systemd-resolved.service
Public bug reported: if you purge resolvconf on Xenial and want systemd-resolve the link is not update and its doesn't use systemd-resolce cache 1) Description:Ubuntu 16.04.3 LTS Release:16.04 2) systemd 229-4ubuntu21 amd64 system and service manager 3) ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 29 Nov 29 22:40 /etc/resolv.conf -> ../run/resolvconf/resolv.conf aptitude purge -y resolvconf ls -l /run/systemd/resolve total 4 -rw-r--r-- 1 systemd-resolve systemd-resolve 381 Nov 29 22:42 resolv.conf ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf # on it's working Description:Ubuntu Bionic Beaver (development branch) Release:18.04 systemd --version 235 ls -l /run/systemd/resolve/ total 8 -rw-r--r-- 1 systemd-resolve systemd-resolve 608 Nov 29 16:36 resolv.conf -rw-r--r-- 1 systemd-resolve systemd-resolve 264 Nov 29 16:36 stub-resolv.conf ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 39 Oct 25 10:38 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf 4) ## ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 29 Nov 29 22:40 /etc/resolv.conf -> ../run/resolvconf/resolv.conf systemctl status/restart systemd-resolved.service ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Package changed: linux-hwe-edge (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1735296 Title: systemd-resolved.service Status in systemd package in Ubuntu: New Bug description: if you purge resolvconf on Xenial and want systemd-resolve the link is not update and its doesn't use systemd-resolce cache 1) Description:Ubuntu 16.04.3 LTS Release:16.04 2) systemd 229-4ubuntu21 amd64 system and service manager 3) ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 29 Nov 29 22:40 /etc/resolv.conf -> ../run/resolvconf/resolv.conf aptitude purge -y resolvconf ls -l /run/systemd/resolve total 4 -rw-r--r-- 1 systemd-resolve systemd-resolve 381 Nov 29 22:42 resolv.conf ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf # on it's working Description:Ubuntu Bionic Beaver (development branch) Release:18.04 systemd --version 235 ls -l /run/systemd/resolve/ total 8 -rw-r--r-- 1 systemd-resolve systemd-resolve 608 Nov 29 16:36 resolv.conf -rw-r--r-- 1 systemd-resolve systemd-resolve 264 Nov 29 16:36 stub-resolv.conf ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 39 Oct 25 10:38 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf 4) ## ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 29 Nov 29 22:40 /etc/resolv.conf -> ../run/resolvconf/resolv.conf systemctl status/restart systemd-resolved.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1735296/+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 1724285] Re: Diffie Hellman parameter created with paramter "-dsaparam" stopped working with slapd
01 slapd[7928]: connection_get(14): got connid= Okt 19 09:34:55 dc01 slapd[7928]: connection_read(14): checking for input on id= Okt 19 09:34:55 dc01 slapd[7928]: op tag 0x42, time 1508398495 Okt 19 09:34:55 dc01 slapd[7928]: ber_get_next on fd 14 failed errno=0 (Success) Okt 19 09:34:55 dc01 slapd[7928]: connection_read(14): input error=-2 id=, closing. Okt 19 09:34:55 dc01 slapd[7928]: connection_closing: readying conn= sd=14 for close Okt 19 09:34:55 dc01 slapd[7928]: daemon: activity on 1 descriptor Okt 19 09:34:55 dc01 slapd[7928]: daemon: activity on: Okt 19 09:34:55 dc01 slapd[7928]: Okt 19 09:34:55 dc01 slapd[7928]: daemon: epoll: listen=8 active_threads=1 tvp=zero Okt 19 09:34:55 dc01 slapd[7928]: daemon: epoll: listen=9 active_threads=1 tvp=zero Okt 19 09:34:55 dc01 slapd[7928]: daemon: epoll: listen=10 active_threads=1 tvp=zero Okt 19 09:34:55 dc01 slapd[7928]: daemon: epoll: listen=11 active_threads=1 tvp=zero Okt 19 09:34:55 dc01 slapd[7928]: daemon: epoll: listen=12 active_threads=1 tvp=zero Okt 19 09:34:55 dc01 slapd[7928]: connection_close: deferring conn= sd=14 Okt 19 09:34:55 dc01 slapd[7928]: conn= op=2 do_unbind Okt 19 09:34:55 dc01 slapd[7928]: conn= op=2 UNBIND Okt 19 09:34:55 dc01 slapd[7928]: connection_resched: attempting closing conn= sd=14 Okt 19 09:34:55 dc01 slapd[7928]: connection_close: conn= sd=14 Okt 19 09:34:55 dc01 slapd[7928]: daemon: removing 14 Okt 19 09:34:55 dc01 slapd[7928]: conn= fd=14 closed Best regards, Thorsten -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1724285 Title: Diffie Hellman parameter created with paramter "-dsaparam" stopped working with slapd Status in openldap package in Ubuntu: Incomplete Bug description: If the dh parameter is created with openssl and the '-dsaparam' parameter is set the resulting diffi hellman paramter can not be added to the openldap server. If a existing dhparam is replaced with one which is create with '-dsaparam' slapd wont start anymore. From the openssl manpage: -dsaparam If this option is used, DSA rather than DH parameters are read or created; they are converted to DH format. Otherwise, "strong" primes (such that (p-1)/2 is also prime) will be used for DH parameter generation. DH parameter generation with the -dsaparam option is much faster, and the recommended exponent length is shorter, which makes DH key exchange more efficient. Beware that with such DSA-style DH parameters, a fresh DH key should be created for each use to avoid small-subgroup attacks that may be possible otherwise. # Works with openldap 2.4.44+dfsg-3ubuntu2.1 and 2.4.45+dfsg-1ubuntu1 openssl dhparam -outform PEM -out dhparam.pem 2048 # Works only with 2.4.44+dfsg-3ubuntu2.1 openssl dhparam -dsaparam -outform PEM -out dhparam.pem 2048 Adding to ldap: dn: cn=config changetype: modify replace: olcTLSDHParamFile olcTLSDHParamFile: /etc/ldap/ssl/dhparam.pem Error message from ldap server: ldap_modify: Other (e.g., implementation specific) error (80) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1724285/+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 1724285] [NEW] Diffie Hellman parameter created with paramter "-dsaparam" stopped working with slapd
Public bug reported: If the dh parameter is created with openssl and the '-dsaparam' parameter is set the resulting diffi hellman paramter can not be added to the openldap server. If a existing dhparam is replaced with one which is create with '-dsaparam' slapd wont start anymore. >From the openssl manpage: -dsaparam If this option is used, DSA rather than DH parameters are read or created; they are converted to DH format. Otherwise, "strong" primes (such that (p-1)/2 is also prime) will be used for DH parameter generation. DH parameter generation with the -dsaparam option is much faster, and the recommended exponent length is shorter, which makes DH key exchange more efficient. Beware that with such DSA-style DH parameters, a fresh DH key should be created for each use to avoid small-subgroup attacks that may be possible otherwise. # Works with openldap 2.4.44+dfsg-3ubuntu2.1 and 2.4.45+dfsg-1ubuntu1 openssl dhparam -outform PEM -out dhparam.pem 2048 # Works only with 2.4.44+dfsg-3ubuntu2.1 openssl dhparam -dsaparam -outform PEM -out dhparam.pem 2048 Adding to ldap: dn: cn=config changetype: modify replace: olcTLSDHParamFile olcTLSDHParamFile: /etc/ldap/ssl/dhparam.pem Error message from ldap server: ldap_modify: Other (e.g., implementation specific) error (80) ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: dsaparam openldap openssl slapd ** Tags added: dsaparam openldap openssl slapd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1724285 Title: Diffie Hellman parameter created with paramter "-dsaparam" stopped working with slapd Status in openldap package in Ubuntu: New Bug description: If the dh parameter is created with openssl and the '-dsaparam' parameter is set the resulting diffi hellman paramter can not be added to the openldap server. If a existing dhparam is replaced with one which is create with '-dsaparam' slapd wont start anymore. From the openssl manpage: -dsaparam If this option is used, DSA rather than DH parameters are read or created; they are converted to DH format. Otherwise, "strong" primes (such that (p-1)/2 is also prime) will be used for DH parameter generation. DH parameter generation with the -dsaparam option is much faster, and the recommended exponent length is shorter, which makes DH key exchange more efficient. Beware that with such DSA-style DH parameters, a fresh DH key should be created for each use to avoid small-subgroup attacks that may be possible otherwise. # Works with openldap 2.4.44+dfsg-3ubuntu2.1 and 2.4.45+dfsg-1ubuntu1 openssl dhparam -outform PEM -out dhparam.pem 2048 # Works only with 2.4.44+dfsg-3ubuntu2.1 openssl dhparam -dsaparam -outform PEM -out dhparam.pem 2048 Adding to ldap: dn: cn=config changetype: modify replace: olcTLSDHParamFile olcTLSDHParamFile: /etc/ldap/ssl/dhparam.pem Error message from ldap server: ldap_modify: Other (e.g., implementation specific) error (80) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1724285/+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 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
I can confirm this one on (X)ubuntu 14.04.5 LTS with XFCE 4.10 desktop. The suggested fixes work for me aswell. Another problem appears when bluetooth is disabled on boot (which I always do because of paranoia ;)). Both Pulseaudio modules won't get loaded by my XFCE autostart script. I have to run it again after bluetooth is enabled manually. Then my JBL Flip 3 speaker appers instantly in the Pulseaudio settings besides the onboard sound device. Everything else works like a charm. -- 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/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM Status in gdm: Confirmed Status in PulseAudio: Confirmed Status in gdm3 package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in gdm3 source package in Xenial: Triaged Status in pulseaudio source package in Xenial: Triaged Status in gdm3 source package in Zesty: Triaged Status in pulseaudio source package in Zesty: Triaged Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)
“The default configuration is that this "motd-news" feature is enabled and that it will check https://motd.ubuntu.com for updates.” is called “a useful feature” by the author of the LWN article, and in this bugreport. In the Debian world, we call this a phone-home privacy violation which is a security-relevant release-critical bug and an absolute MUST NOT. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1701068 Title: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu) Status in base-files package in Ubuntu: Opinion Bug description: In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50 -motd-news that reads https://motd.ubuntu.com/ and displays that text with the rest of the MOTD. Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon Valley which has a reference to Ubuntu. Instead, https://motd.ubuntu.com should show relevant items to those that use Ubuntu Server (relevant security issues, etc), instead of items for desktop users. = Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow, Keras & React Native on Ubuntu - https://ubu.one/HBOubu == ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed Jun 28 12:31:24 2017 InstallationDate: Installed on 2017-05-02 (56 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+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 1130571] Re: wired network disabled after resume (AR9485)
Interesting: Today network-manager 1.2.4 was published in "Xenial (16.04) proposed" which contains the cherry-picked fix from 1.2.6... -- 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/1130571 Title: wired network disabled after resume (AR9485) Status in network-manager package in Ubuntu: Confirmed Bug description: I have both a wired network and wireless. On first boot both are functional, but on resuming from sleep the wired controller is disabled (wireless still works). This behaviour started with the latest kernel installed yesterday. From syslog on resume Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: (eth4): now managed Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: (eth4): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: (eth4): bringing up device. Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: (eth4): deactivating device (reason 'managed') [2] uname -a Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -C network [sudo] password for mthornton: *-network description: Wireless interface product: AR9485 Wireless Network Adapter vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:03:00.0 logical name: wlan3 version: 01 serial: dc:85:de:03:c8:ce width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless configuration: broadcast=yes driver=ath9k driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn resources: irq:17 memory:f790-f797 memory:f798-f798 *-network DISABLED description: Ethernet interface product: AR8161 Gigabit Ethernet vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:04:00.0 logical name: eth4 version: 10 serial: 10:bf:48:9f:e9:c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical configuration: broadcast=yes driver=alx latency=0 multicast=yes resources: irq:19 memory:f780-f783 ioport:d000(size=128) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1130571/+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 1130571] Re: wired network disabled after resume (AR9485)
I also have this problem on several machines running Ubuntu 16.04. After resume from suspend no IPv4 address is assigned to the network interfaces (both wired and wireless). Seems to be not related to hardware or driver but to NetworkManager. Maybe this (known) problem is corrected in version 1.2.6 (see change log). -- 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/1130571 Title: wired network disabled after resume (AR9485) Status in network-manager package in Ubuntu: Confirmed Bug description: I have both a wired network and wireless. On first boot both are functional, but on resuming from sleep the wired controller is disabled (wireless still works). This behaviour started with the latest kernel installed yesterday. From syslog on resume Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: (eth4): now managed Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: (eth4): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: (eth4): bringing up device. Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: (eth4): deactivating device (reason 'managed') [2] uname -a Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -C network [sudo] password for mthornton: *-network description: Wireless interface product: AR9485 Wireless Network Adapter vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:03:00.0 logical name: wlan3 version: 01 serial: dc:85:de:03:c8:ce width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless configuration: broadcast=yes driver=ath9k driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn resources: irq:17 memory:f790-f797 memory:f798-f798 *-network DISABLED description: Ethernet interface product: AR8161 Gigabit Ethernet vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:04:00.0 logical name: eth4 version: 10 serial: 10:bf:48:9f:e9:c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical configuration: broadcast=yes driver=alx latency=0 multicast=yes resources: irq:19 memory:f780-f783 ioport:d000(size=128) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1130571/+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 1647120] Re: File::Find does not work on WSL
This issue has been resolved by Microsoft by changing the links count returned from “always 2” to “always 0”. See https://github.com/Microsoft/BashOnWindows/issues/910 . This bug can be closed. GA of the fixed Windows/WSL code is expected in Q1, likely sometime February 2017. ** Bug watch added: github.com/Microsoft/BashOnWindows/issues #910 https://github.com/Microsoft/BashOnWindows/issues/910 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1647120 Title: File::Find does not work on WSL Status in perl package in Ubuntu: New Bug description: As per discussion here https://github.com/Microsoft/BashOnWindows/issues/186, WSL confuses File::Find. WSL is the “Windows Subsystem for Linux”, which runs Ubuntu on top of Windows 10. File::Find sees that $^O is ‘linux’ and uses nlink, which doesn’t work. After some discussion, patching File::Find to special-case for WSL would solve the issue. I have a patch that works, see link above. Discussion as to whether it's acceptable to be included in perl on Ubuntu is the desired outcome of this bug report. P5P maintainers direct me to get in touch with perl maintainers for Ubuntu, satisfy your requirements for a patch, and then that patch can get submitted upstream by you to P5P. This as per @kid51, James E Keenan. This has been found in perl 5.18.2 on Ubuntu 14.04.5 LTS on WSL/Windows 10. Since Microsoft/Ubuntu are preparing for 16.04 LTS support in the next public update to WSL/Windows 10, it'd make sense to fix the issue for that version, and address 14.04 LTS only if desired. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1647120/+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 1647120] Re: File::Find does not work on WSL
James E. Keenan has a patch for this, which also cleans up how dont_use_nlink is set in general. https://rt.perl.org/Public/Bug/Display.html?id=130258 ** Bug watch added: rt.perl.org/Public/ #130258 https://rt.perl.org/Public/Ticket/Display.html?id=130258 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1647120 Title: File::Find does not work on WSL Status in perl package in Ubuntu: New Bug description: As per discussion here https://github.com/Microsoft/BashOnWindows/issues/186, WSL confuses File::Find. WSL is the “Windows Subsystem for Linux”, which runs Ubuntu on top of Windows 10. File::Find sees that $^O is ‘linux’ and uses nlink, which doesn’t work. After some discussion, patching File::Find to special-case for WSL would solve the issue. I have a patch that works, see link above. Discussion as to whether it's acceptable to be included in perl on Ubuntu is the desired outcome of this bug report. P5P maintainers direct me to get in touch with perl maintainers for Ubuntu, satisfy your requirements for a patch, and then that patch can get submitted upstream by you to P5P. This as per @kid51, James E Keenan. This has been found in perl 5.18.2 on Ubuntu 14.04.5 LTS on WSL/Windows 10. Since Microsoft/Ubuntu are preparing for 16.04 LTS support in the next public update to WSL/Windows 10, it'd make sense to fix the issue for that version, and address 14.04 LTS only if desired. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1647120/+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 1647120] [NEW] File::Find does not work on WSL
Public bug reported: As per discussion here https://github.com/Microsoft/BashOnWindows/issues/186, WSL confuses File::Find. WSL is the “Windows Subsystem for Linux”, which runs Ubuntu on top of Windows 10. File::Find sees that $^O is ‘linux’ and uses nlink, which doesn’t work. After some discussion, patching File::Find to special-case for WSL would solve the issue. I have a patch that works, see link above. Discussion as to whether it's acceptable to be included in perl on Ubuntu is the desired outcome of this bug report. P5P maintainers direct me to get in touch with perl maintainers for Ubuntu, satisfy your requirements for a patch, and then that patch can get submitted upstream by you to P5P. This as per @kid51, James E Keenan. This has been found in perl 5.18.2 on Ubuntu 14.04.5 LTS on WSL/Windows 10. Since Microsoft/Ubuntu are preparing for 16.04 LTS support in the next public update to WSL/Windows 10, it'd make sense to fix the issue for that version, and address 14.04 LTS only if desired. ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: windows10 wsl -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1647120 Title: File::Find does not work on WSL Status in perl package in Ubuntu: New Bug description: As per discussion here https://github.com/Microsoft/BashOnWindows/issues/186, WSL confuses File::Find. WSL is the “Windows Subsystem for Linux”, which runs Ubuntu on top of Windows 10. File::Find sees that $^O is ‘linux’ and uses nlink, which doesn’t work. After some discussion, patching File::Find to special-case for WSL would solve the issue. I have a patch that works, see link above. Discussion as to whether it's acceptable to be included in perl on Ubuntu is the desired outcome of this bug report. P5P maintainers direct me to get in touch with perl maintainers for Ubuntu, satisfy your requirements for a patch, and then that patch can get submitted upstream by you to P5P. This as per @kid51, James E Keenan. This has been found in perl 5.18.2 on Ubuntu 14.04.5 LTS on WSL/Windows 10. Since Microsoft/Ubuntu are preparing for 16.04 LTS support in the next public update to WSL/Windows 10, it'd make sense to fix the issue for that version, and address 14.04 LTS only if desired. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1647120/+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 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"
I am also affected by this bug. It only occurs in ~1 out of 3 suspend/resumes and can be fixed by sudo systemctl restart NetworkManager. I am using ubuntu 16.04, with all updates available until today. My hardware is a thinkpad t440s with the following wlan card Intel Corporation Wireless 7260 (rev 83). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1422143 Title: No wifi connection after suspend with systemd due to missing "wpa_cli suspend" Status in One Hundred Papercuts: Confirmed Status in NetworkManager: Unknown Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Wily: Fix Committed Status in wpa source package in Xenial: Fix Released Bug description: Using systemd as my default init system if I resume from suspend my laptop, it doesn't automatically reconnect to the wireless network and it doesn't list the available network connections. The only way to get a wireless connection is to restart the network- manager daemon or going to the gnome-control-center, disable wireless and enable it again. SRU INFORMATION === In some of these cases this bug can be worked around by calling "wpa_cli suspend/resume" before/after suspend, like we used to do with the old pm-utils quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects particular hardware, and thus this needs to be tested by affected reporters, there is no general reproducer for arbitrary systems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.19.0-031900-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 15 18:27:39 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-10-22 (116 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) IpRoute: default via 10.0.0.1 dev wlan0 proto static metric 1024 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.36 169.254.0.0/16 dev wlan0 scope link metric 1000 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0wifi connected/org/freedesktop/NetworkManager/Devices/2 openhost_caldas 09d1f69d-d3da-4978-a69c-d94455db7ecf /org/freedesktop/NetworkManager/ActiveConnection/0 docker0 bridgeunavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+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 1589836] Re: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet
AUB niet de files verwijderen tijdens apt nog aan’t werken is. Probeer es: $ sudo apt-get update $ sudo apt-get -f install -- 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/1589836 Title: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet Status in libxml2 package in Ubuntu: Invalid Bug description: The package failed to upgrade in the terminal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxml2-utils 2.9.3+dfsg1-1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Jun 7 09:40:41 2016 ErrorMessage: krijg geen toegang tot archief: Bestand of map bestaat niet InstallationDate: Installed on 2016-04-23 (44 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libxml2 Title: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1589836/+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 1589679] Re: package libxml2 2.9.3+dfsg1-1 failed to install/upgrade: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system
I suggest to learn to read. Mount your filesystems read-write when you install packages. ** Changed in: libxml2 (Ubuntu) Status: New => Invalid -- 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/1589679 Title: package libxml2 2.9.3+dfsg1-1 failed to install/upgrade: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system Status in libxml2 package in Ubuntu: Invalid Bug description: occur when i update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxml2 2.9.3+dfsg1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Mon Jun 6 17:10:44 2016 DuplicateSignature: package:libxml2:2.9.3+dfsg1-1 Unpacking libxml2:i386 (2.9.3+dfsg1-1ubuntu0.1) over (2.9.3+dfsg1-1) ... dpkg: error processing archive /var/cache/apt/archives/libxml2_2.9.3+dfsg1-1ubuntu0.1_i386.deb (--unpack): unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system ErrorMessage: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system InstallationDate: Installed on 2016-05-26 (10 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libxml2 Title: package libxml2 2.9.3+dfsg1-1 failed to install/upgrade: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system UpgradeStatus: Upgraded to xenial on 2016-05-27 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1589679/+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 1493999] Re: xz-utils package is really, really old
This is being discussed in Debian already. Please don’t do this separately. Instead, work with the Debian maintainer to do this, then do a SyncRequest. ** Bug watch added: Debian Bug tracker #731634 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731634 ** Also affects: xz-utils (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731634 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1493999 Title: xz-utils package is really, really old Status in xz-utils package in Ubuntu: Confirmed Status in xz-utils package in Debian: Unknown Bug description: Willy is currently using a really old version of xz-utils. The latest version at this time is 5.2.1 released on 2015-02-26 http://git.tukaani.org/?p=xz.git;a=blob;f=NEWS;hb=HEAD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1493999/+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 1464324] [NEW] package jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Public bug reported: apt-get reports an error ProblemType: Package DistroRelease: Ubuntu 15.04 Package: jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu Jun 11 18:38:53 2015 DpkgHistoryLog: Start-Date: 2015-06-11 18:38:35 Commandline: apt-get --reinstall install grub-common grub-pc os-prober Reinstall: os-prober:amd64 (1.63ubuntu1), grub-common:amd64 (2.02~beta2-22ubuntu1), grub-pc:amd64 (2.02~beta2-22ubuntu1) DuplicateSignature: package:jackd2:1.9.10+20140719git3eb0ae6a~dfsg-2:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: jackd2 Title: package jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to vivid on 2015-04-28 (44 days ago) ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1464324 Title: package jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Status in jackd2 package in Ubuntu: New Bug description: apt-get reports an error ProblemType: Package DistroRelease: Ubuntu 15.04 Package: jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu Jun 11 18:38:53 2015 DpkgHistoryLog: Start-Date: 2015-06-11 18:38:35 Commandline: apt-get --reinstall install grub-common grub-pc os-prober Reinstall: os-prober:amd64 (1.63ubuntu1), grub-common:amd64 (2.02~beta2-22ubuntu1), grub-pc:amd64 (2.02~beta2-22ubuntu1) DuplicateSignature: package:jackd2:1.9.10+20140719git3eb0ae6a~dfsg-2:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: jackd2 Title: package jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to vivid on 2015-04-28 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1464324/+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 1444494] Re: In Split Screen Mode, Click Maximize, Window Disappears
*** This bug is a duplicate of bug 1408894 *** https://bugs.launchpad.net/bugs/1408894 ** This bug has been marked a duplicate of bug 1408894 pre-grid size of application window is lost, when restoring an application in maximized mode and then moving to left/right edge using + keybind -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/194 Title: In Split Screen Mode, Click Maximize, Window Disappears Status in unity package in Ubuntu: New Bug description: I've been using Libre Writer in split screen mode, using ctrl+Super+rightcursor, placing the libre writer window on the right hand side of my screen. All good. When I click on the maximize button, however, the window disappears. I can sometimes find it by moving my cursor around at the top left corner of the screen and an expand (upsidedown 'L') appears and I can stretch the window back out again. But when I hit maximize, from split screen mode, it should maximize rather than disappear. I hope this makes sense and can be fixed. Jim. --- ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-01-31 (78 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Package: libreoffice 1:4.2.7-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Tags: trusty Uname: Linux 3.13.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/194/+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 1444494] Re: In Split Screen Mode, Click Maximize, Window Disappears
Hi, is it possible that this bug is a duplicate of: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1408894 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/194 Title: In Split Screen Mode, Click Maximize, Window Disappears Status in unity package in Ubuntu: New Bug description: I've been using Libre Writer in split screen mode, using ctrl+Super+rightcursor, placing the libre writer window on the right hand side of my screen. All good. When I click on the maximize button, however, the window disappears. I can sometimes find it by moving my cursor around at the top left corner of the screen and an expand (upsidedown 'L') appears and I can stretch the window back out again. But when I hit maximize, from split screen mode, it should maximize rather than disappear. I hope this makes sense and can be fixed. Jim. --- ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-01-31 (78 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Package: libreoffice 1:4.2.7-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Tags: trusty Uname: Linux 3.13.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/194/+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 1358762] Re: Included gzip 1.2.4 has several vulnerabilities
As I mentioned in IRC: I can probably easily shave another 2½K off .text by removing stub support for multiple compressors and using the gzopen() API already shipped by klibc. Note that klibc bundles zlib 1.2.3 whereas even MirBSD has 1.2.8 already. That would also need updating. But at least, MirBSD compress uses zlib for gzip I/O instead of bundling its own inflate/deflate functions as GNU gzip does. All is 2-clause and 3-clause BSD and MIT licence. ** Also affects: klibc Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1358762 Title: Included gzip 1.2.4 has several vulnerabilities Status in klibc: New Status in “klibc” package in Ubuntu: Confirmed Bug description: The included gzip version is quite old (version 1.2.4) and has several security vulnerabilities. Check http://web.nvd.nist.gov/view/vuln/search- results?adv_search=true&cves=on&cpe_version=cpe:/a:gnu:gzip:1.2.4 for example. I explicitly checked for CVE-2001-1228, which was not fixed by a patch in the klibc package, so I assume the other vulnerabilities are not fixed either. I think it would be a good idea to update the included gzip to a current version. To manage notifications about this bug go to: https://bugs.launchpad.net/klibc/+bug/1358762/+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 1358762] Re: Included gzip 1.2.4 has several vulnerabilities
Nevermind. I hacked MirBSD compress to omit the BSD compress method (so it only does gzip), and replaced a few more things, and got a working gzip/gunzip under BSD licence. If there is any interest in the klibc side to include that, be my guest. Sizes are nice, too (dynamically linked): tglase@tglase:~/mbsd/src/usr.bin/compress $ size /usr/lib/klibc/bin/gzip obj/compress textdata bss dec hex filename 258283016 316552 345396 54534 /usr/lib/klibc/bin/gzip 18802 04208 2301059e2 obj/compress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1358762 Title: Included gzip 1.2.4 has several vulnerabilities Status in “klibc” package in Ubuntu: Confirmed Bug description: The included gzip version is quite old (version 1.2.4) and has several security vulnerabilities. Check http://web.nvd.nist.gov/view/vuln/search- results?adv_search=true&cves=on&cpe_version=cpe:/a:gnu:gzip:1.2.4 for example. I explicitly checked for CVE-2001-1228, which was not fixed by a patch in the klibc package, so I assume the other vulnerabilities are not fixed either. I think it would be a good idea to update the included gzip to a current version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1358762/+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 1358762] Re: Included gzip 1.2.4 has several vulnerabilities
I have just looked at whether gzip can be replaced by BSD compress(1), which is a drop-in replacement under a more free licence, but even after adding fts and a lot of BSD functions it still needs funopen() which klibc doesn’t have ☹ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1358762 Title: Included gzip 1.2.4 has several vulnerabilities Status in “klibc” package in Ubuntu: Confirmed Bug description: The included gzip version is quite old (version 1.2.4) and has several security vulnerabilities. Check http://web.nvd.nist.gov/view/vuln/search- results?adv_search=true&cves=on&cpe_version=cpe:/a:gnu:gzip:1.2.4 for example. I explicitly checked for CVE-2001-1228, which was not fixed by a patch in the klibc package, so I assume the other vulnerabilities are not fixed either. I think it would be a good idea to update the included gzip to a current version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1358762/+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 1370012] Re: upstart: (mis)uses shell reserved word ”stop”
@dino99 no it’s not related. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1370012 Title: upstart: (mis)uses shell reserved word ”stop” Status in “upstart” package in Ubuntu: Confirmed Bug description: upstart (1.5-0ubuntu7.2) /lib/init/upstart-job uses “stop” (in line 93) which is a reserved shell word. If using mksh (actually /bin/lksh) as /bin/sh, which defines this as default alias, upgrading udev, which wants to restart the udev service, fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1370012/+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 1370012] [NEW] upstart: (mis)uses shell reserved word ”stop”
Public bug reported: upstart (1.5-0ubuntu7.2) /lib/init/upstart-job uses “stop” (in line 93) which is a reserved shell word. If using mksh (actually /bin/lksh) as /bin/sh, which defines this as default alias, upgrading udev, which wants to restart the udev service, fails. ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1370012 Title: upstart: (mis)uses shell reserved word ”stop” Status in “upstart” package in Ubuntu: New Bug description: upstart (1.5-0ubuntu7.2) /lib/init/upstart-job uses “stop” (in line 93) which is a reserved shell word. If using mksh (actually /bin/lksh) as /bin/sh, which defines this as default alias, upgrading udev, which wants to restart the udev service, fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1370012/+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 1241805] Re: After Upgrade to Kubuntu 13.10 Bluetooth-Adapter couln't be found anymore
For me all works fine since Kubuntu 14.04 But I had to choose 'reset to factory defaults' and restore my changes in BIOS. (Changing BT / WLAN / other Hardwere settings didn't work.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1241805 Title: After Upgrade to Kubuntu 13.10 Bluetooth-Adapter couln't be found anymore Status in “bluez” package in Ubuntu: Confirmed Bug description: In Kubuntu 11.x, 12.x and 13.04 everything was fine, after the _secound_ boot to 13.10 the build-in BT-adapter seems to be deactivated. (I use a BT-mouse, so I noticed it that exactly.) Even on a boot to Windows 7BT-adapter can't be found anymore. It may be conected with changes on WLAN drivers. (Hardware could be turnd on and off with a system-key above keybord.) Other side of Problem: A BT-Dongle, which works fine on other laptop and on mine one under windows, isd't detected under Kubuntu 13.10, even too. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Fri Oct 18 21:13:50 2013 InstallationDate: Installed on 2012-11-26 (325 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) InterestingModules: btusb rfcomm bnep bluetooth MachineType: Hewlett-Packard HP Compaq 8710w MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=925ac4bf-795b-4e6a-a6c1-a69fee5d8377 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago) dmi.bios.date: 06/18/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MAD Ver. F.0D dmi.board.name: 30C3 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 73.31 dmi.chassis.asset.tag: Thorsel-HP dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MADVer.F.0D:bd06/18/2008:svnHewlett-Packard:pnHPCompaq8710w:pvrF.0D:rvnHewlett-Packard:rn30C3:rvrKBCVersion73.31:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 8710w dmi.product.version: F.0D dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:1B:DC:04:B4:63 ACL MTU: 310:10 SCO MTU: 64:8 DOWN RX bytes:514 acl:0 sco:0 events:25 errors:0 TX bytes:832 acl:0 sco:0 commands:25 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1241805/+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
