[Touch-packages] [Bug 2058162] [NEW] regression: "pacmd dump" reports incorrect status for muted microphone
Public bug reported: pacmd dump | grep mute The "set-source-mute" for my mic should say "no" when my mic is not muted but it always says "yes" nowadays. This used to work earlier. Broken version: $ apt policy pulseaudio-utils pulseaudio-utils: Installed: 1:15.99.1+dfsg1-1ubuntu2.1 Candidate: 1:15.99.1+dfsg1-1ubuntu2.1 I'm pretty sure at least version 1:11.1-1ubuntu7.11 used to work correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio-utils 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-25.25.1~22.04.1-lowlatency 6.5.13 Uname: Linux 6.5.0-25-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Mar 18 01:38:38 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1898 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2023-08-11 (219 days ago) dmi.bios.date: 10/17/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.init.d.apport: [modified] modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158 mtime.conffile..etc.pulse.daemon.conf: 2021-11-19T14:33:38.709428 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2058162 Title: regression: "pacmd dump" reports incorrect status for muted microphone Status in pulseaudio package in Ubuntu: New Bug description: pacmd dump | grep mute The "set-source-mute" for my mic should say "no" when my mic is not muted but it always says "yes" nowadays. This used to work earlier. Broken version: $ apt policy pulseaudio-utils pulseaudio-utils: Installed: 1:15.99.1+dfsg1-1ubuntu2.1 Candidate: 1:15.99.1+dfsg1-1ubuntu2.1 I'm pretty sure at least version 1:11.1-1ubuntu7.11 used to work correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio-utils 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-25.25.1~22.04.1-lowlatency 6.5.13 Uname: Linux 6.5.0-25-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Mar 18 01:38:38 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1898 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2023-08-11 (219 days ago) dmi.bios.date: 10/17/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.init.d.apport: [modified] modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158 mtime.conffile..etc.pulse.daemon.conf: 2021-11-19T14:33:38.709428 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2058162/+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 2049019] [NEW] RFE: also show processes witing for IO (status "D") as running (highlight y)
Public bug reported: Currently when I run top and use key "y" to enable highlighting for running task, only tasks with status "R" are highlighted. However, as many modern processes are IO limited instead of CPU limited, it would make sense to highlight both CPU limited and IO limited processes because both are logically running as far as the user is interested. I'm hereby requesting that the "running tasks" highlight should highlight all processes with status "R" or "D" instead of only "R" like it currently does. I don't understand the "I" state to know if it would make sense to include that, too, as a "running task". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: procps 2:3.3.17-6ubuntu2.1 ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-lowlatency 6.2.16 Uname: Linux 6.2.0-1014-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Jan 11 13:05:28 2024 InstallationDate: Installed on 2022-03-25 (657 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: procps UpgradeStatus: Upgraded to jammy on 2023-05-25 (230 days ago) ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2049019 Title: RFE: also show processes witing for IO (status "D") as running (highlight y) Status in procps package in Ubuntu: New Bug description: Currently when I run top and use key "y" to enable highlighting for running task, only tasks with status "R" are highlighted. However, as many modern processes are IO limited instead of CPU limited, it would make sense to highlight both CPU limited and IO limited processes because both are logically running as far as the user is interested. I'm hereby requesting that the "running tasks" highlight should highlight all processes with status "R" or "D" instead of only "R" like it currently does. I don't understand the "I" state to know if it would make sense to include that, too, as a "running task". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: procps 2:3.3.17-6ubuntu2.1 ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-lowlatency 6.2.16 Uname: Linux 6.2.0-1014-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Jan 11 13:05:28 2024 InstallationDate: Installed on 2022-03-25 (657 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: procps UpgradeStatus: Upgraded to jammy on 2023-05-25 (230 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2049019/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
I was hit this bug and it turned out that for me the best fix was to start /usr/lib/x86_64-linux-gnu/polkit-mate/polkit-mate-authentication- agent-1 before using the software-properties-gtk application. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Released Bug description: * Impact Changes on the 'Other Software tab' sometime fail to ask for credential and fail to apply as a consequence * Test Case - start software-properties-gtk - got to the 'Other Software Tab' - try to change the value of a checkbox The change should prompt for a password and be active * Regression potential the change is a small sleep workaround to avoid trying to get the focus while GTK still has it, outside of a tiny delay in the active it should have no consequence --- On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+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 2027674] [NEW] apt dist-upgrade shows crap messages (really poor user experience)
Public bug reported:
I executed following in terminal
$ sudo apt update && sudo apt dist-upgrade
and received following mess:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
vlc-plugin-qt libvlc5 libimage-magick-perl vlc-data maven libvlccore9 vlc
imagemagick vlc-bin libjs-jquery-ui vlc-l10n libmaven3-core-java
libavdevice58 ffmpeg libopenexr25 libmagick++-6.q16-8 python3-scipy
libpostproc55 libmagickcore-6.q16-6-extra vlc-plugin-samba libavcodec58
libimage-magick-q16-perl libmagickwand-6.q16-6 vlc-plugin-notify libavutil56
imagemagick-6.q16 libswscale5 libeditorconfig0 libmagickcore-6.q16-6
vlc-plugin-access-extra vlc-plugin-skins2 vlc-plugin-video-splitter
libswresample3 imagemagick-6-common vlc-plugin-video-output libavformat58
libvlc-bin vlc-plugin-base vlc-plugin-visualization libavfilter7
Learn more about Ubuntu Pro at https://ubuntu.com/pro
#
# An OpenSSL vulnerability has recently been fixed with USN-6188-1 & 6119-1:
# CVE-2023-2650: possible DoS translating ASN.1 object identifiers.
# Ensure you have updated the package to its latest version.
#
The following packages have been kept back:
gjs libgjs0g libspeechd2 python3-speechd speech-dispatcher
speech-dispatcher-audio-plugins speech-dispatcher-espeak-ng
The following packages will be upgraded:
alsa-ucm-conf debootstrap dkms ghostscript ghostscript-x gir1.2-adw-1
gir1.2-gnomedesktop-3.0 gir1.2-mutter-10 gnome-desktop3-data gnome-shell
gnome-shell-common gnome-shell-extension-prefs initramfs-tools
initramfs-tools-bin initramfs-tools-core iotop libadwaita-1-0 libgnome-bg-4-1
libgnome-desktop-3-19 libgnome-desktop-4-1 libgs9 libgs9-common libllvm15
libllvm15:i386 libmutter-10-0 libruby3.0 libvirt-clients
libvirt-daemon libvirt-daemon-config-network libvirt-daemon-config-nwfilter
libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd
libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 mutter
mutter-common python3-ubuntutools ruby3.0 thunderbird
thunderbird-gnome-support thunderbird-locale-fi ubuntu-advantage-tools
ubuntu-dev-tools
44 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
11 standard LTS security updates
Need to get 136 MB of archives.
After this operation, 30,7 kB of additional disk space will be used.
Do you want to continue? [Y/n]
This has two big problems:
(1) Ubuntu Pro ad cannot be disabled which causes lots of extra clutter
on the output which will result in *training people to skip reading* the
output of dist-upgdade. This is obviously a big problem and to "fix"
that problem, new "important" message has been prefixed with "# " to
make it more visible. If this trend continues, I'm sure next message
will have "# * NOTICE THIS IMPORTANT MESSAGE!!#"!"!!! *" to
make people notice the important part. Command line administrative tools
should be about real stuff, not a shouting contest over ads. If you
truly think ads should be enforced, keep it to the login message only.
(2) The new message is unneeded crap about unspecified openssl package
*that I already have installed*! I found this by googling the warning
message and finding page https://ubuntu.com/security/CVE-2023-2650 which
clearly tells me that jammy has this bug fixed in package openssl
version 3.0.2-0ubuntu1.10.
If you think that the message about CVE-2023-2650 is important enough to be
displayed even if the package has already been installed ("tell friends about
this"), then very minimum should be explicitly saying the package name and
minimum version with the fix. Only having text "the package" doesn't cut.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apt 2.4.9
ProcVersionSignature: Ubuntu 5.19.0-1027.28~22.04.1-lowlatency 5.19.17
Uname: Linux 5.19.0-1027-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Thu Jul 13 13:04:19 2023
InstallationDate: Installed on 2022-03-25 (475 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: apt
UpgradeStatus: Upgraded to jammy on 2023-05-25 (48 days ago)
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2027674
Title:
apt dist-upgrade shows crap messages (really poor user experience)
Status in apt package in Ubuntu:
New
Bug description:
I executed following in terminal
$ sudo apt update && sudo apt dist-upgrade
and received following mess:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Ge
[Touch-packages] [Bug 1989957] [NEW] `man ip-address` fails to document subcommands "change" and "replace"
Public bug reported:
$ man ip-address
...
SYNOPSIS
...
ip address { add | change | replace } ...
However, the subcommands "change" and "replace" are not documented
anywhere. As these may be used in scripts, there should be clear
definition of these features or nobody can know if a script using these
features is actually correctly implemented.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: iproute2 5.5.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-125.141-lowlatency 5.4.195
Uname: Linux 5.4.0-125-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Fri Sep 16 14:40:10 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-05 (1349 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: iproute2
UpgradeStatus: Upgraded to focal on 2022-09-13 (2 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158
** Affects: iproute2 (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 iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1989957
Title:
`man ip-address` fails to document subcommands "change" and "replace"
Status in iproute2 package in Ubuntu:
New
Bug description:
$ man ip-address
...
SYNOPSIS
...
ip address { add | change | replace } ...
However, the subcommands "change" and "replace" are not documented
anywhere. As these may be used in scripts, there should be clear
definition of these features or nobody can know if a script using
these features is actually correctly implemented.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: iproute2 5.5.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-125.141-lowlatency 5.4.195
Uname: Linux 5.4.0-125-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Fri Sep 16 14:40:10 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-05 (1349 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: iproute2
UpgradeStatus: Upgraded to focal on 2022-09-13 (2 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1989957/+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 1988774] [NEW] timeout hangs when combined with sudo and watch
Public bug reported: Command $ timeout 15s watch -d date --iso=ns works as expected and shows clock going forward for 15 seconds and then stops. However, command $ sudo timeout 15s watch -d date --iso=ns hangs forever. I'm not sure if this is a bug in sudo, timeout or watch but I'm reporting this as timeout issue because I haven't experienced similar problem unless I use timeout. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-124.140~18.04.1-lowlatency 5.4.195 Uname: Linux 5.4.0-124-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: MATE Date: Mon Sep 5 18:41:42 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1338 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1988774 Title: timeout hangs when combined with sudo and watch Status in coreutils package in Ubuntu: New Bug description: Command $ timeout 15s watch -d date --iso=ns works as expected and shows clock going forward for 15 seconds and then stops. However, command $ sudo timeout 15s watch -d date --iso=ns hangs forever. I'm not sure if this is a bug in sudo, timeout or watch but I'm reporting this as timeout issue because I haven't experienced similar problem unless I use timeout. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-124.140~18.04.1-lowlatency 5.4.195 Uname: Linux 5.4.0-124-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: MATE Date: Mon Sep 5 18:41:42 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1338 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1988774/+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 1978943] [NEW] tc qdisc cake fails on Ubuntu 18.04 LTS
Public bug reported: I'm running Ubuntu 18.04 LTS with latest lowlatency kernel. In practice I've installed package linux-lowlatency-hwe-18.04-edge which has resulted packages linux-image-5.4.0-117-lowlatency and linux- modules-5.4.0-117-lowlatency to be installed right now. $ dpkg -L linux-modules-5.4.0-117-lowlatency | grep cake /lib/modules/5.4.0-117-lowlatency/kernel/net/sched/sch_cake.ko $ sudo modprobe sch_cake # completes successfully $ sudo tc qdisc add dev enp3s0 root cake bandwidth 101Mbit ethernet rtt 20ms Unknown qdisc "cake", hence option "bandwidth" is unparsable It appears that iproute2 cannot correctly support this kernel. Similar thing works just fine with Ubuntu 20.04 LTS (tested with generic kernel only, though). Is this a known limitation or a bug? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1.3 ProcVersionSignature: Ubuntu 5.4.0-117.132~18.04.1-lowlatency 5.4.189 Uname: Linux 5.4.0-117-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jun 16 15:30:17 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1257 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1978943 Title: tc qdisc cake fails on Ubuntu 18.04 LTS Status in iproute2 package in Ubuntu: New Bug description: I'm running Ubuntu 18.04 LTS with latest lowlatency kernel. In practice I've installed package linux-lowlatency-hwe-18.04-edge which has resulted packages linux-image-5.4.0-117-lowlatency and linux- modules-5.4.0-117-lowlatency to be installed right now. $ dpkg -L linux-modules-5.4.0-117-lowlatency | grep cake /lib/modules/5.4.0-117-lowlatency/kernel/net/sched/sch_cake.ko $ sudo modprobe sch_cake # completes successfully $ sudo tc qdisc add dev enp3s0 root cake bandwidth 101Mbit ethernet rtt 20ms Unknown qdisc "cake", hence option "bandwidth" is unparsable It appears that iproute2 cannot correctly support this kernel. Similar thing works just fine with Ubuntu 20.04 LTS (tested with generic kernel only, though). Is this a known limitation or a bug? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1.3 ProcVersionSignature: Ubuntu 5.4.0-117.132~18.04.1-lowlatency 5.4.189 Uname: Linux 5.4.0-117-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jun 16 15:30:17 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1257 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1978943/+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 1971895] Re: Warning messages from stat printed on installation with no user crontabs
Confirming this on Ubuntu 18.04.6 LTS while installing updates: Setting up cron (3.0pl1-128.1ubuntu1.1) ... stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory Warning: * is not a regular file! update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults I'm pretty sure I haven't seen this problem with other updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1971895 Title: Warning messages from stat printed on installation with no user crontabs Status in cron package in Ubuntu: Confirmed Bug description: On installation of cron on a new system, or (I expect) an upgrade with no user crontab files the following is printed: Setting up cron (3.0pl1-128.1ubuntu1.1) ... stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory Warning: * is not a regular file! This is related to the fix for CVE-2017-9525 introduced in 3.0pl1-128.1ubuntu1.1. The for loop at line 66 of cron.postinst needs to have a guard like the following added to it: [ "$tab_name" = "*" ] && continue We have observed this with Bionic, I haven't checked any other Ubuntu releases. Cheers, Andrew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1971895/+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 1969118] Re: Certificate viewer shows extra bytes for RSA keys
OK, I agree that this is not a security problem but UI issue only. However, note that the UI says "Public key" and before that "Key algorithm: RSA". As such, the public key should not have any extra bytes at the start or at the end, just the public RSA 2048 bit key as is (as desribed by "Key Algorithm" and "Key Size" fields immediately above). Also note that the key displayed by gcr-viewer does not match key value displayed by `openssl x509 -in ... -text`, Google Chrome, nor Firefox. Is this also by design? That said, I agree that gcr-viewer doesn't show the exponent separate from the modulus either so maybe the easiest fix would be to change the label "Public Key" to say "DER Encoded Public Key" to make it obvious that user must decode the encoding of the key by themselves. When I'm viewing PEM encoded key I sure didn't expect to see the public key as DER encoded raw data. A better fix would be to render modulus and exponent as separate fields without any extra bytes. Of course, that would require different code paths for e.g. RSA and x25519. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1969118 Title: Certificate viewer shows extra bytes for RSA keys Status in gcr package in Ubuntu: Invalid Bug description: When I view a x509 certificate using gcr-viewer .../path/to/certificate.pem and open the "Details" section and check the RSA public key information, the section that lists the public key renders extra 8 bytes at the start and 5 bytes at the end which are not actually part of the key. I haven't tried if this happens with other file types except x509, or with encryption methods except RSA. The exact certificate I viewed can be downloaded from https://crt.sh/?d=6454583403 and the expected public key modulus should start with 00:b6:28:0b:44:... but the certificate viewer shows public key starting with bytes 30 82 01 0A 02 82 01 01 00 B6 28 0B 44. Note the extra bytes 30 82 01 0A 02 82 01 01. The extra bytes seem to be static and do not change after re-lanching the viewer again. There are also extra bytes in the end of the displayed key. I'm marking this bug as a security vulnerability for now because (1) This tool is supposed to used to check encryption credentials, and (2) It's still unknown if this is some kind of 8 byte underflow/5 byte overflow or just a rendering problem. I'm not aware of the viewer writing extra bytes to any memory location so I would assume this is just a rendering issue. I'm fine with this issue being public so feel free to publish at your discretion. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gcr 3.28.0-1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-lowlatency 5.4.174 Uname: Linux 5.4.0-107-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: MATE Date: Thu Apr 14 15:47:18 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1194 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gcr UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1969118/+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 591823] Re: "File descriptor \d+ (\S+) leaked on lvs invocation."
I would guess some files are left open when grub_util_pull_lvm_by_command() calls grub_util_exec_pipe() in grub2 /grub-core/osdep/unix/getroot.c -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/591823 Title: "File descriptor \d+ (\S+) leaked on lvs invocation." Status in aptitude: Fix Released Status in lvm2: Fix Released Status in lvm2 package in Ubuntu: Opinion Bug description: If you see messages like these: File descriptor 40 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 41 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 42 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 43 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh You can set LVM_SUPPRESS_FD_WARNINGS to suppress these warnings. Reference: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581339 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432986 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466138 This is a slightly controversial bug and it's not yet fixed either way (aka fix not to leak file descriptors or stop warning by default) To manage notifications about this bug go to: https://bugs.launchpad.net/aptitude/+bug/591823/+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 591823] Re: "File descriptor \d+ (\S+) leaked on lvs invocation."
I got this same warning: $ sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-5.4.0-66-lowlatency linux-headers-5.4.0-73-lowlatency linux-hwe-5.4-headers-5.4.0-66 linux-hwe-5.4-headers-5.4.0-73 linux-image-5.4.0-66-lowlatency linux-image-5.4.0-73-lowlatency linux-modules-5.4.0-66-lowlatency linux-modules-5.4.0-73-lowlatency 0 to upgrade, 0 to newly install, 8 to remove and 0 not to upgrade. After this operation, 714 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 492639 files and directories currently installed.) Removing linux-headers-5.4.0-66-lowlatency (5.4.0-66.74~18.04.2) ... Removing linux-headers-5.4.0-73-lowlatency (5.4.0-73.82~18.04.1) ... Removing linux-hwe-5.4-headers-5.4.0-66 (5.4.0-66.74~18.04.2) ... Removing linux-hwe-5.4-headers-5.4.0-73 (5.4.0-73.82~18.04.1) ... Removing linux-image-5.4.0-66-lowlatency (5.4.0-66.74~18.04.2) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.4.0-66-lowlatency /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-77-lowlatency Found initrd image: /boot/initrd.img-5.4.0-77-lowlatency Found linux image: /boot/vmlinuz-5.4.0-74-lowlatency Found initrd image: /boot/initrd.img-5.4.0-74-lowlatency Found linux image: /boot/vmlinuz-5.4.0-73-lowlatency Found initrd image: /boot/initrd.img-5.4.0-73-lowlatency done Removing linux-image-5.4.0-73-lowlatency (5.4.0-73.82~18.04.1) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.4.0-73-lowlatency /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-77-lowlatency Found initrd image: /boot/initrd.img-5.4.0-77-lowlatency Found linux image: /boot/vmlinuz-5.4.0-74-lowlatency Found initrd image: /boot/initrd.img-5.4.0-74-lowlatency File descriptor 10 (/var/lib/dpkg/triggers/linux-update-5.4.0-66-lowlatency (deleted)) leaked on lvs invocation. Parent PID 12476: /bin/sh done Removing linux-modules-5.4.0-66-lowlatency (5.4.0-66.74~18.04.2) ... Removing linux-modules-5.4.0-73-lowlatency (5.4.0-73.82~18.04.1) ... $ lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.04.5 LTS Release:18.04 Codename: bionic I would guess this is actually a bug in grub-probe. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/591823 Title: "File descriptor \d+ (\S+) leaked on lvs invocation." Status in aptitude: Fix Released Status in lvm2: Fix Released Status in lvm2 package in Ubuntu: Opinion Bug description: If you see messages like these: File descriptor 40 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 41 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 42 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 43 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh You can set LVM_SUPPRESS_FD_WARNINGS to suppress these warnings. Reference: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581339 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432986 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466138 This is a slightly controversial bug and it's not yet fixed either way (aka fix not to leak file descriptors or stop warning by default) To manage notifications about this bug go to: https://bugs.launchpad.net/aptitude/+bug/591823/+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 1914029] [NEW] pulseaudio startup script should not blindly force audible bell
Public bug reported: File /usr/bin/start-pulseaudio-x11 ALWAYS loads module module-x11-bell and uploads audio sample for Pulseaudio if the file /usr/share/sounds/ubuntu/stereo/bell.ogg EXISTS in the filesystem. I have configured only visual bell for everything and therefore any part of the system that forcibly tries to play any kind of audio for bell output is simply broken. At bare minimum, this script should first check if the desktop environment has been configured to use visual bell instead of audible bell before loading the module. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.11 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-lowlatency 5.4.78 Uname: Linux 5.4.0-64-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mira 6634 F pulseaudio /dev/snd/controlC0: mira 6634 F pulseaudio CurrentDesktop: MATE Date: Mon Feb 1 11:48:03 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (757 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1914029 Title: pulseaudio startup script should not blindly force audible bell Status in pulseaudio package in Ubuntu: New Bug description: File /usr/bin/start-pulseaudio-x11 ALWAYS loads module module-x11-bell and uploads audio sample for Pulseaudio if the file /usr/share/sounds/ubuntu/stereo/bell.ogg EXISTS in the filesystem. I have configured only visual bell for everything and therefore any part of the system that forcibly tries to play any kind of audio for bell output is simply broken. At bare minimum, this script should first check if the desktop environment has been configured to use visual bell instead of audible bell before loading the module. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.11 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-lowlatency 5.4.78 Uname: Linux 5.4.0-64-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mira 6634 F pulseaudio /dev/snd/controlC0: mira 6634 F pulseaudio CurrentDesktop: MATE Date: Mon Feb 1 11:48:03 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (757 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1914029/+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 1903449] [NEW] accountsservice displays "Libvirt Qemu"
Public bug reported: Installing libvirt-manager results in account libvirt-qemu being created. This user has config in /etc/passwd like follows: libvirt-qemu:x:64055:125:Libvirt Qemu,,,:/var/lib/libvirt:/usr/sbin/nologin The "nologin" should be pretty clear signal that this account is not usable for logging in. Despite this, this account is offered in visual login (e.g. lightdm). The computation for possible user accounts is handled by package accountsservice. A workaround is to manually list this user as system user: echo -e "[User]\nSystemAccount=true" > /var/lib/AccountsService/users/libvirt-qemu However, as this user cannot be logged in (/etc/shadow contains "!" as the password hash, too) it never makes any sense to show this in login screen even without the above manual configuration. Related: bug 857651 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: accountsservice 0.6.45-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 8 16:54:24 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (672 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: accountsservice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1903449 Title: accountsservice displays "Libvirt Qemu" Status in accountsservice package in Ubuntu: New Bug description: Installing libvirt-manager results in account libvirt-qemu being created. This user has config in /etc/passwd like follows: libvirt-qemu:x:64055:125:Libvirt Qemu,,,:/var/lib/libvirt:/usr/sbin/nologin The "nologin" should be pretty clear signal that this account is not usable for logging in. Despite this, this account is offered in visual login (e.g. lightdm). The computation for possible user accounts is handled by package accountsservice. A workaround is to manually list this user as system user: echo -e "[User]\nSystemAccount=true" > /var/lib/AccountsService/users/libvirt-qemu However, as this user cannot be logged in (/etc/shadow contains "!" as the password hash, too) it never makes any sense to show this in login screen even without the above manual configuration. Related: bug 857651 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: accountsservice 0.6.45-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 8 16:54:24 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (672 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: accountsservice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1903449/+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 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"
Minimal test case (run in empty directory): mkdir -p a/1 b/1; echo "/1/2/3" > list; rsync --delete-missing-args --files-from=list a b Example output: file has vanished: ".../rsync-bug/a/1/2" ABORTING due to invalid path from sender: 1/2/3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1896251 Title: rsync --delete-missing-args fails with "error: protocol incompatibility" Status in rsync package in Ubuntu: New Bug description: Running rsync --delete-missing-args --files-from=... fails with error message like ABORTING due to invalid path from sender: dir1/dir2/dir3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] if the listed directories are trying to delete full subtree of files. According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has been fixed in version 3.2.2. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334 Could you update the rsync package or backport the fix? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 18 18:27:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (621 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1896251/+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 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"
I forgot to mention that according to https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=863334 this issue does not exist in version 3.1.1-3. That should help pinpointing the actual problem if you want to backport the fix instead of upgrading the whole rsync package to latest version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1896251 Title: rsync --delete-missing-args fails with "error: protocol incompatibility" Status in rsync package in Ubuntu: New Bug description: Running rsync --delete-missing-args --files-from=... fails with error message like ABORTING due to invalid path from sender: dir1/dir2/dir3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] if the listed directories are trying to delete full subtree of files. According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has been fixed in version 3.2.2. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334 Could you update the rsync package or backport the fix? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 18 18:27:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (621 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1896251/+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 1896251] [NEW] rsync --delete-missing-args fails with "error: protocol incompatibility"
Public bug reported: Running rsync --delete-missing-args --files-from=... fails with error message like ABORTING due to invalid path from sender: dir1/dir2/dir3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] if the listed directories are trying to delete full subtree of files. According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has been fixed in version 3.2.2. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334 Could you update the rsync package or backport the fix? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 18 18:27:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (621 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Bug watch added: Debian Bug tracker #863334 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1896251 Title: rsync --delete-missing-args fails with "error: protocol incompatibility" Status in rsync package in Ubuntu: New Bug description: Running rsync --delete-missing-args --files-from=... fails with error message like ABORTING due to invalid path from sender: dir1/dir2/dir3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] if the listed directories are trying to delete full subtree of files. According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has been fixed in version 3.2.2. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334 Could you update the rsync package or backport the fix? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 18 18:27:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (621 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1896251/+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 1886163] Re: systemd-resolved emits totally useless warning
Maybe related: bug 1785383 -- 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/1886163 Title: systemd-resolved emits totally useless warning Status in systemd package in Ubuntu: New Bug description: With systemd-resolved taking care of resolving DNS requests, it will emit following warning message when domain fails to resolve: Jul 02 07:19:22 balancer1 systemd-resolved[1269]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. This warning message is missing information about the process that's trying to resolve a domain and (this part is the more important bit) information about the domain that systemd-resolved is trying to resolve in the first place. If the warning message cannot be made meaningful, it should be dropped for good. I'd prefer to log at least the domain name that was being tried to be resolved. Having pid and name of the process that needed the information would be a plus. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 3 11:59:22 2020 InstallationDate: Installed on 2019-05-22 (407 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M MachineType: Dell Inc. PowerEdge R230 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=41607337-6732-464c-b97c-429504aa1b23 ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-01 (31 days ago) dmi.bios.date: 12/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0FRVY0 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.asset.tag: lb1.peda.net dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd12/06/2018:svnDellInc.:pnPowerEdgeR230:pvr:rvnDellInc.:rn0FRVY0:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R230 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R230 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886163/+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 1886163] Re: systemd-resolved emits totally useless warning
Maybe related: bug 1796501 -- 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/1886163 Title: systemd-resolved emits totally useless warning Status in systemd package in Ubuntu: New Bug description: With systemd-resolved taking care of resolving DNS requests, it will emit following warning message when domain fails to resolve: Jul 02 07:19:22 balancer1 systemd-resolved[1269]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. This warning message is missing information about the process that's trying to resolve a domain and (this part is the more important bit) information about the domain that systemd-resolved is trying to resolve in the first place. If the warning message cannot be made meaningful, it should be dropped for good. I'd prefer to log at least the domain name that was being tried to be resolved. Having pid and name of the process that needed the information would be a plus. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 3 11:59:22 2020 InstallationDate: Installed on 2019-05-22 (407 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M MachineType: Dell Inc. PowerEdge R230 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=41607337-6732-464c-b97c-429504aa1b23 ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-01 (31 days ago) dmi.bios.date: 12/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0FRVY0 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.asset.tag: lb1.peda.net dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd12/06/2018:svnDellInc.:pnPowerEdgeR230:pvr:rvnDellInc.:rn0FRVY0:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R230 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R230 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886163/+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 1886163] [NEW] systemd-resolved emits totally useless warning
Public bug reported: With systemd-resolved taking care of resolving DNS requests, it will emit following warning message when domain fails to resolve: Jul 02 07:19:22 balancer1 systemd-resolved[1269]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. This warning message is missing information about the process that's trying to resolve a domain and (this part is the more important bit) information about the domain that systemd-resolved is trying to resolve in the first place. If the warning message cannot be made meaningful, it should be dropped for good. I'd prefer to log at least the domain name that was being tried to be resolved. Having pid and name of the process that needed the information would be a plus. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 3 11:59:22 2020 InstallationDate: Installed on 2019-05-22 (407 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M MachineType: Dell Inc. PowerEdge R230 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=41607337-6732-464c-b97c-429504aa1b23 ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-01 (31 days ago) dmi.bios.date: 12/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0FRVY0 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.asset.tag: lb1.peda.net dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd12/06/2018:svnDellInc.:pnPowerEdgeR230:pvr:rvnDellInc.:rn0FRVY0:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R230 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R230 dmi.sys.vendor: Dell Inc. ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1886163 Title: systemd-resolved emits totally useless warning Status in systemd package in Ubuntu: New Bug description: With systemd-resolved taking care of resolving DNS requests, it will emit following warning message when domain fails to resolve: Jul 02 07:19:22 balancer1 systemd-resolved[1269]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. This warning message is missing information about the process that's trying to resolve a domain and (this part is the more important bit) information about the domain that systemd-resolved is trying to resolve in the first place. If the warning message cannot be made meaningful, it should be dropped for good. I'd prefer to log at least the domain name that was being tried to be resolved. Having pid and name of the process that needed the information would be a plus. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 3 11:59:22 2020 InstallationDate: Installed on 2019-05-22 (407 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M MachineType: Dell Inc. PowerEdge R230 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=41607337-6732-464c-b97c-429504aa1b23 ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-01 (31 days ago) dmi.bios.date: 12/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0FRVY0 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.asset.tag: lb1.peda.net dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr
[Touch-packages] [Bug 1877571] [NEW] bash is missing feature to use keyword if identically named alias exists
Public bug reported: If following command is run (sleep 1 & sleep 1 & time wait); date bash is supposed to run two commands in parallel, wait for both to complete and the run third command. However, if current environment has following alias configured alias time='/usr/bin/time -v' then the above command will fail with /usr/bin/time: cannot run wait: No such file or directory and the final command is run without a wait. Bash already has "command" to force interpretation as system command and "builtin" to force interpretation as built-in command. However bash is missing "keyword" to force interpretation as keyword. One should be able to write (sleep 1 & sleep 1 & keyword time wait); date to force time to be interpreted as bash keyword. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bash 4.4.18-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-lowlatency 5.3.18 Uname: Linux 5.3.0-51-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: MATE Date: Fri May 8 15:48:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (488 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1877571 Title: bash is missing feature to use keyword if identically named alias exists Status in bash package in Ubuntu: New Bug description: If following command is run (sleep 1 & sleep 1 & time wait); date bash is supposed to run two commands in parallel, wait for both to complete and the run third command. However, if current environment has following alias configured alias time='/usr/bin/time -v' then the above command will fail with /usr/bin/time: cannot run wait: No such file or directory and the final command is run without a wait. Bash already has "command" to force interpretation as system command and "builtin" to force interpretation as built-in command. However bash is missing "keyword" to force interpretation as keyword. One should be able to write (sleep 1 & sleep 1 & keyword time wait); date to force time to be interpreted as bash keyword. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bash 4.4.18-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-lowlatency 5.3.18 Uname: Linux 5.3.0-51-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: MATE Date: Fri May 8 15:48:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (488 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1877571/+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 861642] Re: upowerd uses 100% cpu till killed
Any updates? The diagnosis in comment #10 seems to make sense. This has been a problem since 2011 and I still see the same issue on Ubuntu 16.04 LTS with latests patches. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/861642 Title: upowerd uses 100% cpu till killed Status in Upower: New Status in upower package in Ubuntu: Confirmed Bug description: top - 12:57:54 up 2:56, 3 users, load average: 1.06, 1.12, 1.35 Tasks: 219 total, 2 running, 216 sleeping, 0 stopped, 1 zombie Cpu0 : 70.2%us, 29.8%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu1 : 2.3%us, 1.3%sy, 0.0%ni, 96.4%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu2 : 1.0%us, 0.3%sy, 0.0%ni, 98.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu3 : 0.7%us, 1.6%sy, 0.0%ni, 97.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu4 : 0.0%us, 0.3%sy, 0.0%ni, 99.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu5 : 0.0%us, 0.3%sy, 0.0%ni, 98.3%id, 1.4%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 5994176k total, 4198260k used, 1795916k free,63308k buffers Swap: 8193144k total, 355188k used, 7837956k free, 334316k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 2268 root 20 0 148m 1572 680 R 100 0.0 111:08.37 upowerd ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: upower 0.9.9-4 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Sep 28 12:53:23 2011 ExecutablePath: /usr/lib/upower/upowerd InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: SourcePackage: upower UpgradeStatus: Upgraded to natty on 2011-04-06 (175 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/861642/+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 1834994] Re: rsync: --xattrs is extremely slow
Note that this bug is NOT a duplicate of https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1524703 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1834994 Title: rsync: --xattrs is extremely slow Status in rsync package in Ubuntu: New Bug description: Ubuntu 16.04 LTS repositories contain only rsync version 3.1.1: $ apt policy rsync rsync: Installed: 3.1.1-3ubuntu1.2 Candidate: 3.1.1-3ubuntu1.2 Version table: *** 3.1.1-3ubuntu1.2 500 500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 3.1.1-3ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages However, this version has a bug where flag --xattrs causes very very high CPU usage if source contains lots of unique extended attributes. I'm trying to sync 13 TB (roughly 6.5 M files) with extended attributes and this bug seems to make this slower and slower as the time goes by. The system has been copying the stuff for three weeks (!) now. It's getting slower every day but still seems to make progress so I try to run it to completion. First couple of terabytes suggested that this sync operation should have taken around 4 days. The source directory is used by glusterfs which creates checksums as extended attributes and practically every file has different checksum. Please, update rsync package on Ubuntu 16.04 to 3.1.2-2 or later. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799143 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rsync 3.1.1-3ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-51-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 2 09:07:49 2019 InstallationDate: Installed on 2015-02-23 (1589 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: rsync UpgradeStatus: Upgraded to xenial on 2016-06-10 (1116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1834994/+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 1834994] [NEW] rsync: --xattrs is extremely slow
Public bug reported: Ubuntu 16.04 LTS repositories contain only rsync version 3.1.1: $ apt policy rsync rsync: Installed: 3.1.1-3ubuntu1.2 Candidate: 3.1.1-3ubuntu1.2 Version table: *** 3.1.1-3ubuntu1.2 500 500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 3.1.1-3ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages However, this version has a bug where flag --xattrs causes very very high CPU usage if source contains lots of unique extended attributes. I'm trying to sync 13 TB (roughly 6.5 M files) with extended attributes and this bug seems to make this slower and slower as the time goes by. The system has been copying the stuff for three weeks (!) now. It's getting slower every day but still seems to make progress so I try to run it to completion. First couple of terabytes suggested that this sync operation should have taken around 4 days. The source directory is used by glusterfs which creates checksums as extended attributes and practically every file has different checksum. Please, update rsync package on Ubuntu 16.04 to 3.1.2-2 or later. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799143 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rsync 3.1.1-3ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-51-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 2 09:07:49 2019 InstallationDate: Installed on 2015-02-23 (1589 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: rsync UpgradeStatus: Upgraded to xenial on 2016-06-10 (1116 days ago) ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1834994 Title: rsync: --xattrs is extremely slow Status in rsync package in Ubuntu: New Bug description: Ubuntu 16.04 LTS repositories contain only rsync version 3.1.1: $ apt policy rsync rsync: Installed: 3.1.1-3ubuntu1.2 Candidate: 3.1.1-3ubuntu1.2 Version table: *** 3.1.1-3ubuntu1.2 500 500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 3.1.1-3ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages However, this version has a bug where flag --xattrs causes very very high CPU usage if source contains lots of unique extended attributes. I'm trying to sync 13 TB (roughly 6.5 M files) with extended attributes and this bug seems to make this slower and slower as the time goes by. The system has been copying the stuff for three weeks (!) now. It's getting slower every day but still seems to make progress so I try to run it to completion. First couple of terabytes suggested that this sync operation should have taken around 4 days. The source directory is used by glusterfs which creates checksums as extended attributes and practically every file has different checksum. Please, update rsync package on Ubuntu 16.04 to 3.1.2-2 or later. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799143 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rsync 3.1.1-3ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-51-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 2 09:07:49 2019 InstallationDate: Installed on 2015-02-23 (1589 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: rsync UpgradeStatus: Upgraded to xenial on 2016-06-10 (1116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1834994/+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 1810683] Re: Suspend does not work in the login screen
Does anybody care about lightdm bugs? I'm still seeing this issue but I haven't found a way to debug it. Is there some environment variable or some other method that can make all g_debug() messages visible from lightdm? Currently no log seems to contain any of the g_debug() messages in the lightdm source code. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1810683 Title: Suspend does not work in the login screen Status in lightdm package in Ubuntu: New Bug description: After booting the system and login screen is displayed top right gear- icon contains option to Suspend. However, selecting that action has no results at all (no error message, nothing in any file under /var/log or journalctl). I would like to get the suspend action to work similar to older Ubuntu versions (this system used to run Ubuntu 16.04 LTS and I did a fresh install of 18.04.1 LTS). I have removed package gdm3 and installed lightdm instead because I like the lightdm interface better for our use case. Looking at the source code in liblightdm-gobject/power.c suggests that lightdm_get_can_suspend() returns true because I get the suspend option. However, selecting the option does nothing so I would guess that lightdm_suspend() is called but somehow none of the g_debug() log messages never appear anywhere so I cannot debug the problem any further. (The above is just a guess because I didn't have enough time to read the source well enough to figure out if this is the codepath I'm trying to activate.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Jan 6 22:23:20 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1810683/+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 1834206] [NEW] fc-match -v reports rgba:1 instead of rgba:2 with BGR display
Public bug reported:
I have a BGR display so I really would like to have BGR subpixel
rendering. I'm having major trouble getting fc-match to emit correct
info.
$ fc-match -v | grep -E 'rgba|lcdfilter|antialias|hintstyle|dpi'
antialias: True(w)
hintstyle: 2(i)(w)
dpi: 75(f)(s)
rgba: 1(i)(w)
lcdfilter: 1(i)(w)
$ ls -l /etc/fonts/conf.d/10*
lrwxrwxrwx 1 root root 31 2016-08-16 22:18 /etc/fonts/conf.d/10-antialias.conf
-> ../conf.avail/10-antialias.conf
lrwxrwxrwx 1 root root 30 2019-06-14 12:27 /etc/fonts/conf.d/10-autohint.conf
-> ../conf.avail/10-autohint.conf
lrwxrwxrwx 1 root root 29 2016-08-16 22:18 /etc/fonts/conf.d/10-hinting.conf ->
../conf.avail/10-hinting.conf
lrwxrwxrwx 1 root root 36 2016-08-16 22:18
/etc/fonts/conf.d/10-hinting-slight.conf -> ../conf.avail/10-hinting-slight.conf
lrwxrwxrwx 1 root root 40 2016-08-16 22:18
/etc/fonts/conf.d/10-scale-bitmap-fonts.conf ->
../conf.avail/10-scale-bitmap-fonts.conf
lrwxrwxrwx 1 root root 35 2019-06-13 12:16
/etc/fonts/conf.d/10-sub-pixel-bgr.conf -> ../conf.avail/10-sub-pixel-bgr.conf
$ strace -e trace=file fc-match -v 2>&1 | grep "open.*bgr"
open("/etc/fonts/conf.d/10-sub-pixel-bgr.conf", O_RDONLY|O_CLOEXEC) = 5
$ gsettings list-recursively | grep bgr
com.canonical.unity-greeter xft-rgba 'bgr'
org.cinnamon.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.gnome.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.cinnamon.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.gnome.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.mate.font-rendering rgba-order 'bgr'
Is there some documented reason that fc-match fails to report correct
subpixel order given this config? Is there some another configuration
file that I must modify or create to get fc-match to correctly declare
BGR subpixel structure?
Also, the dpi above is incorrect too, the correct value would be near
96.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-lowlatency 4.15.18
Uname: Linux 4.15.0-51-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Jun 25 16:50:15 2019
InstallationDate: Installed on 2015-02-23 (1583 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: fontconfig
UpgradeStatus: Upgraded to xenial on 2016-06-10 (1110 days ago)
** Affects: fontconfig (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1834206
Title:
fc-match -v reports rgba:1 instead of rgba:2 with BGR display
Status in fontconfig package in Ubuntu:
New
Bug description:
I have a BGR display so I really would like to have BGR subpixel
rendering. I'm having major trouble getting fc-match to emit correct
info.
$ fc-match -v | grep -E 'rgba|lcdfilter|antialias|hintstyle|dpi'
antialias: True(w)
hintstyle: 2(i)(w)
dpi: 75(f)(s)
rgba: 1(i)(w)
lcdfilter: 1(i)(w)
$ ls -l /etc/fonts/conf.d/10*
lrwxrwxrwx 1 root root 31 2016-08-16 22:18
/etc/fonts/conf.d/10-antialias.conf -> ../conf.avail/10-antialias.conf
lrwxrwxrwx 1 root root 30 2019-06-14 12:27 /etc/fonts/conf.d/10-autohint.conf
-> ../conf.avail/10-autohint.conf
lrwxrwxrwx 1 root root 29 2016-08-16 22:18 /etc/fonts/conf.d/10-hinting.conf
-> ../conf.avail/10-hinting.conf
lrwxrwxrwx 1 root root 36 2016-08-16 22:18
/etc/fonts/conf.d/10-hinting-slight.conf -> ../conf.avail/10-hinting-slight.conf
lrwxrwxrwx 1 root root 40 2016-08-16 22:18
/etc/fonts/conf.d/10-scale-bitmap-fonts.conf ->
../conf.avail/10-scale-bitmap-fonts.conf
lrwxrwxrwx 1 root root 35 2019-06-13 12:16
/etc/fonts/conf.d/10-sub-pixel-bgr.conf -> ../conf.avail/10-sub-pixel-bgr.conf
$ strace -e trace=file fc-match -v 2>&1 | grep "open.*bgr"
open("/etc/fonts/conf.d/10-sub-pixel-bgr.conf", O_RDONLY|O_CLOEXEC) = 5
$ gsettings list-recursively | grep bgr
com.canonical.unity-greeter xft-rgba 'bgr'
org.cinnamon.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.gnome.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.cinnamon.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.gnome.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.mate.font-rendering rgba-order 'bgr'
Is there some documented reason that fc-match fails to report correct
subpixel order given this config? Is there some another configuration
file that I must modify or create to get fc-match to correctly declare
BGR subpixel structure?
Also, the dpi above is incorrect too, the correct value would be near
96.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
[Touch-packages] [Bug 1759008] Re: Revert automatic suspend by default for bionic?
Still broken with MATE desktop on Ubuntu 18.04.2 LTS. If I run mate- power-preferences and select ON AC Power - Put computer to sleep when inactive for: [never] the computer still automatically sleeps (enters S3) after 20 minutes. $ grep -C1 sleep-inactive-ac-timeout /usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override [org.gnome.settings-daemon.plugins.power] sleep-inactive-ac-timeout = 0 I've tried to manually run $ systemd-inhibit --mode=block sleep 2h but the system still enters S3 after 20 minutes unless I disable screen saver using mate-inhibit-applet. $ apt policy mate-desktop mate-desktop: Installed: 1.20.1-2ubuntu1 Candidate: 1.20.1-2ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1759008 Title: Revert automatic suspend by default for bionic? Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Bionic: Fix Released Bug description: GNOME 3.28 has turned Automatic Suspend on by default and set it to 20 minutes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/2fdb48fa I generally think this is a good thing. There are a few issues though. 1. The computer will still suspend even if there are remote users logged in or the computer is being used as a server for files, printers, etc. 2. Some software doesn't set inhibit correctly. ~ahasenack mentioned he was using the Spotify Snap and the computer suspend after 20 minutes. (Maybe Spotify needs to use the screen-inhibit-control snap interface.) 3. Even if it does set inhibit, there is a report that the computer will suspend as soon as the inhibit is removed if there is no other activity. (Imagine a movie playing. At the end of the movie, the computer goes to sleep immediately.) More details and proposed fix at https://bugzilla.gnome.org/show_bug.cgi?id=705942#c21 4. There is no GUI way to change this setting for the login screen yet. https://gitlab.gnome.org/GNOME/gnome-control-center/issues/22 5. Some users think that desktop computers should be always running unless told otherwise. Personally, I don't give this argument much weight at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1759008/+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 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)
This bug is still relevant for Bionic. Any info about possible backport? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1691908 Title: fstab binds appear as mounts (x-gvfs-hide is being ignored) Status in GLib: Expired Status in glib2.0 package in Ubuntu: Triaged Bug description: glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as well, I haven't tested) causes fstab binds to appear as mounts in Nautilus (and in Deepin Dock - Deepin is based on Gnome). Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour. I first noted this bug behaviour here: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049 Details of my particular system and issue with what I tried to resolve it can be found here: https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030 1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux. OS: Arch Linux Kernel: x86_64 Linux 4.10.13-1-ARCH Shell: bash 4.4.12 Resolution: 1920x1200 DE: Deepin 15.4 WM: Deepin WM WM Theme: Arc-Darker GTK Theme: Arc-Darker [GTK2/3] Icon Theme: deepin Font: Noto Sans 11 CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C] GPU: GeForce GTX 950 RAM: 2598MiB / 15990MiB 2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the problem). 3. Nautilus to list internal physical drives (my SSD and 1TB HDD) only. 4. Nautilus listed my system disk (as expected) but also listed all of my fstab binds as removable drives (Downloads, Music, Pictures, Videos and Documents although this was not listed as "Documents" but instead listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide those drives. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1691908/+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 1808133] Re: python3-apport emits a deprecation warning
Could this be fixed for bionic, too?
$ python3 -Wall -c '1/0'
/usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the imp
module is deprecated in favour of importlib; see the module's documentation for
alternative uses
import fnmatch, glob, traceback, errno, sys, atexit, locale, imp
Traceback (most recent call last):
File "", line 1, in
ZeroDivisionError: division by zero
$ lsb_release -a
LSB Version:
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1808133
Title:
python3-apport emits a deprecation warning
Status in apport package in Ubuntu:
Fix Released
Bug description:
python3-apport uses the deprecated module imp. This causes to emitting
a deprecation warning when run python3 with the -Walways option, and
even to changing a traceback when run python3 with the -Werror option.
Example:
```
$ python3 -Walways -c '1/0'
/usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the
imp module is deprecated in favour of importlib; see the module's documentation
for alternative uses
import fnmatch, glob, traceback, errno, sys, atexit, locale, imp
Traceback (most recent call last):
File "", line 1, in
ZeroDivisionError: division by zero
```
```
$ python3 -Werror -c '1/0'
Traceback (most recent call last):
File "", line 1, in
ZeroDivisionError: division by zero
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in
apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 13, in
import fnmatch, glob, traceback, errno, sys, atexit, locale, imp
File "/usr/lib/python3.6/imp.py", line 33, in
DeprecationWarning, stacklevel=2)
DeprecationWarning: the imp module is deprecated in favour of importlib; see
the module's documentation for alternative uses
Original exception was:
Traceback (most recent call last):
File "", line 1, in
ZeroDivisionError: division by zero
```
The -Werror option can be used for catching possible issues, and
additional output from apport spoils the result.
```
$ python3 -b -Werror -c 'str(b"")'
Traceback (most recent call last):
File "", line 1, in
BytesWarning: str() on a bytes instance
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in
apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 13, in
import fnmatch, glob, traceback, errno, sys, atexit, locale, imp
File "/usr/lib/python3.6/imp.py", line 33, in
DeprecationWarning, stacklevel=2)
DeprecationWarning: the imp module is deprecated in favour of importlib; see
the module's documentation for alternative uses
Original exception was:
Traceback (most recent call last):
File "", line 1, in
BytesWarning: str() on a bytes instance
```
The solution is to silence DeprecationWarning for `import imp`:
import warnings
with warnings.catch_warnings():
warnings.simplefilter('ignore', DeprecationWarning)
import imp
To manage notifications about this bug go to:
https://bug
[Touch-packages] [Bug 1811447] [NEW] update-initramfs generates wrong RESUME if no swap + zram
Public bug reported: On a system with swap disabled (removed from /etc/fstab) and package zram-config installed update-initramfs -u will emit something like following: I: The initramfs will attempt to resume from /dev/zram1 I: (UUID=1d4b8573-7eee-43c9-a02a-10a65fc17b8a) I: Set the RESUME variable to override this. Obviously, resuming from zram device without actual non-volatile storage is not going to work. update-initramfs should be fixed to ignore /dev/zram* because otherwise the user must e.g. create file /etc /initramfs-tools/conf.d/resume-none with case-sensitive contents RESUME=none to workaround the issue, which may be a bit hard to guess from the above notice only. See also, somewhat related bug: 1781746 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 11 19:10:41 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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 bionic -- 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/1811447 Title: update-initramfs generates wrong RESUME if no swap + zram Status in initramfs-tools package in Ubuntu: New Bug description: On a system with swap disabled (removed from /etc/fstab) and package zram-config installed update-initramfs -u will emit something like following: I: The initramfs will attempt to resume from /dev/zram1 I: (UUID=1d4b8573-7eee-43c9-a02a-10a65fc17b8a) I: Set the RESUME variable to override this. Obviously, resuming from zram device without actual non-volatile storage is not going to work. update-initramfs should be fixed to ignore /dev/zram* because otherwise the user must e.g. create file /etc/initramfs-tools/conf.d/resume-none with case-sensitive contents RESUME=none to workaround the issue, which may be a bit hard to guess from the above notice only. See also, somewhat related bug: 1781746 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 11 19:10:41 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1811447/+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 1810683] [NEW] Suspend does not work in the login screen
Public bug reported: After booting the system and login screen is displayed top right gear- icon contains option to Suspend. However, selecting that action has no results at all (no error message, nothing in any file under /var/log or journalctl). I would like to get the suspend action to work similar to older Ubuntu versions (this system used to run Ubuntu 16.04 LTS and I did a fresh install of 18.04.1 LTS). I have removed package gdm3 and installed lightdm instead because I like the lightdm interface better for our use case. Looking at the source code in liblightdm-gobject/power.c suggests that lightdm_get_can_suspend() returns true because I get the suspend option. However, selecting the option does nothing so I would guess that lightdm_suspend() is called but somehow none of the g_debug() log messages never appear anywhere so I cannot debug the problem any further. (The above is just a guess because I didn't have enough time to read the source well enough to figure out if this is the codepath I'm trying to activate.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Jan 6 22:23:20 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1810683 Title: Suspend does not work in the login screen Status in lightdm package in Ubuntu: New Bug description: After booting the system and login screen is displayed top right gear- icon contains option to Suspend. However, selecting that action has no results at all (no error message, nothing in any file under /var/log or journalctl). I would like to get the suspend action to work similar to older Ubuntu versions (this system used to run Ubuntu 16.04 LTS and I did a fresh install of 18.04.1 LTS). I have removed package gdm3 and installed lightdm instead because I like the lightdm interface better for our use case. Looking at the source code in liblightdm-gobject/power.c suggests that lightdm_get_can_suspend() returns true because I get the suspend option. However, selecting the option does nothing so I would guess that lightdm_suspend() is called but somehow none of the g_debug() log messages never appear anywhere so I cannot debug the problem any further. (The above is just a guess because I didn't have enough time to read the source well enough to figure out if this is the codepath I'm trying to activate.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Jan 6 22:23:20 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1810683/+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 1803353] Re: Display freezes (possible i915 freeze/hang)
Extra information: sudo kill -9 via ssh connection did restore the display in working order without restarting the system so I'm pretty sure this is caused by some kind of hang caused by xorg process. Plain kill without -9 did not do anything, though. Perhaps this is caused by some race conditition while xorg is keeping some locks which cause keyboard not to work (e.g. Alt+Ctrl+F1) and the display does not update. After saying that, the system seems to be in some weird state where pretty much all my old X client processess are still running (e.g. Chrome, Opera, Thunderbird) even though the original xorg process does not exists anymore. Thunderbird seems to be eating 100% of a single core. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1803353 Title: Display freezes (possible i915 freeze/hang) Status in xorg package in Ubuntu: New Bug description: Xorg suddenly stops updating the display and CTRL+ALT+F1 does not work. The issue happens randomly and does not seem to be related to content being rendered. This time the display hang occurred while I was typing in gnome-terminal. I can successfully ssh into the system from another computer and run ubuntu-bug xorg while the display is frozen. Disconnecting the display port cable and reconnecting does not successfully restore the image. However, after disconnecting the cable and reconnecting, the monitor never resumed from DPMS suspend so the signal emitted did in fact change when I disconnected the cable. The problem occurs both with official lowlatency Ubuntu kernel and custom kernel built from vanilla kernel sources. I haven't found a way to deduce if this is in reality caused by kernel, xorg or the hardware. However, considering that this happens with many different kernel versions, I'd assume this is caused by xorg, instead. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 Uname: Linux 4.18.0-memalloc-watchdog+ x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,mousepoll,move,resize,imgpng,wall,animation,grid,fade,place,vpswitch,gnomecompat,session,workarounds,expo,scale,ezoom] Date: Wed Nov 14 15:23:50 2018 DistUpgraded: 2016-06-10 11:06:21,514 WARNING no activity on terminal for 300 seconds (Applying changes) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2015-02-23 (1360 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-memalloc-watchdog+ root=UUID=254cacdb-f61b-45a6-9885-37afd2b598ce ro libata.noacpi=1 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-06-10 (887 days ago) dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd02/04/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Sep 6 15:40:48 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41047 vendor DEL xserver.version: 2:1.19.5-0ubuntu2~16.04.1 To manage n
[Touch-packages] [Bug 1803353] [NEW] Display freezes (possible i915 freeze/hang)
Public bug reported: Xorg suddenly stops updating the display and CTRL+ALT+F1 does not work. The issue happens randomly and does not seem to be related to content being rendered. This time the display hang occurred while I was typing in gnome-terminal. I can successfully ssh into the system from another computer and run ubuntu-bug xorg while the display is frozen. Disconnecting the display port cable and reconnecting does not successfully restore the image. However, after disconnecting the cable and reconnecting, the monitor never resumed from DPMS suspend so the signal emitted did in fact change when I disconnected the cable. The problem occurs both with official lowlatency Ubuntu kernel and custom kernel built from vanilla kernel sources. I haven't found a way to deduce if this is in reality caused by kernel, xorg or the hardware. However, considering that this happens with many different kernel versions, I'd assume this is caused by xorg, instead. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 Uname: Linux 4.18.0-memalloc-watchdog+ x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,mousepoll,move,resize,imgpng,wall,animation,grid,fade,place,vpswitch,gnomecompat,session,workarounds,expo,scale,ezoom] Date: Wed Nov 14 15:23:50 2018 DistUpgraded: 2016-06-10 11:06:21,514 WARNING no activity on terminal for 300 seconds (Applying changes) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2015-02-23 (1360 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-memalloc-watchdog+ root=UUID=254cacdb-f61b-45a6-9885-37afd2b598ce ro libata.noacpi=1 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-06-10 (887 days ago) dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd02/04/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Sep 6 15:40:48 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41047 vendor DEL xserver.version: 2:1.19.5-0ubuntu2~16.04.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1803353 Title: Display freezes (possible i915 freeze/hang) Status in xorg package in Ubuntu: New Bug description: Xorg suddenly stops updating the display and CTRL+ALT+F1 does not work. The issue happens randomly and does not seem to be related to content being rendered. This time the display hang occurred while I was typing in gnome-terminal. I can successfully ssh into the system from another computer and run ubuntu-bug xorg while the display is frozen. Disconnecting the display port cable and reconnecting does not successfully restore the image. However, after disconnecting the cable and reconnecting, the monitor never resumed from DPMS suspend so the signal emitted did in fact change when I disconnected the cable. The problem occurs both with official lowlatency Ubuntu kernel and custom kernel
[Touch-packages] [Bug 1531622] Re: default config still using a legacy keyword: KLogPermitNonKernelFacility
Is Ubuntu 16.04 missing this patch by any change? http://rsyslog-users.1305293.n2.nabble.com/PATCH-imklog-Fix-permitnonkernelfacility-not-working-tt7591305.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1531622 Title: default config still using a legacy keyword: KLogPermitNonKernelFacility Status in rsyslog package in Ubuntu: Fix Released Bug description: /etc/rsyslog.conf contains: $KLogPermitNonKernelFacility on But this no longer supported and trigger this log message: Jan 5 08:56:16 simon-laptop rsyslogd-: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.14.0 try http://www.rsyslog.com/e/ ] Error is described as "legacy parameter no longer permitted". This legacy parameter causes config syntax checks (rsyslogd -N1) to fail. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rsyslog 8.14.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 6 15:47:15 2016 SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logcheck.ignore.d.server.rsyslog: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+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 1703987] Re: New style permitnonkernelfacility imklog option inside module() doesn't work
Could this be backported to Ubuntu 16.04 LTS? It still only has 8.16.0-1ubuntu3. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1703987 Title: New style permitnonkernelfacility imklog option inside module() doesn't work Status in Rsyslog: Unknown Status in rsyslog package in Ubuntu: Fix Released Bug description: artful 8.16.0-1ubuntu5 (which is way behind upstream and debian, btw) There are two ways to load the imklog module and pass it an option (PermitNonKernelFacility in this case). a) legacy $ModLoad imklog $KLogPermitNonKernelFacility on b) "new style", also referred to as "v6+": module(load="imklog" permitnonkernelfacility="on") For a while the ubuntu package was using a mix: loading the module with the new style, but setting the option via the legacy method. In bug #1531622 this was fixed for yakkety+. Problem is, upstream isn't honouring the new style option setting due to a bug of its own: https://github.com/rsyslog/rsyslog/issues/477 With the legacy config: #module(load="imklog" permitnonkernelfacility="on") $ModLoad imklog $KLogPermitNonKernelFacility on I get kernel messages in /var/log/syslog: root@nsn7:~# grep andreas-was-here /var/log/syslog root@nsn7:~# echo andreas-was-here > /dev/kmsg root@nsn7:~# grep andreas-was-here /var/log/syslog Jul 12 16:46:33 nsn7 kernel: [27774.476193] andreas-was-here root@nsn7:~# But with this new v6 config style: module(load="imklog" permitnonkernelfacility="on") # provides kernel logging support #$ModLoad imklog #$KLogPermitNonKernelFacility on The text doesn't show up in /var/log/syslog. That's the upstream bug. To manage notifications about this bug go to: https://bugs.launchpad.net/rsyslog/+bug/1703987/+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 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup
Should it be safe to install ligthdm package from zesty to xenial to test if it fixes the issue? (https://packages.ubuntu.com/zesty/lightdm version 1.22.0-0ubuntu2.1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/997483 Title: VT_WAITACTIVE does not work well with a multiseat setup Status in Light Display Manager: Incomplete Status in lightdm package in Ubuntu: Incomplete Bug description: Related to the fix introduced in bug #851612 . Saw this in lightdm.log (system call interrupted because of ctrl-alt-del pressed): [+2.97s] DEBUG: New display ready, switching to it [+2.97s] DEBUG: Activating VT 8 [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted system call [+77.56s] DEBUG: Got signal 15 from process 1 [+77.56s] DEBUG: Caught Terminated signal, shutting down And in x-1-greeter.log: [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001 [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000 [+50.56s] WARNING: Error getting session list from org.freedesktop.DisplayManager: Timeout was reached On vt7, unity-greeter would get stuck after password input. On vt8, unity-greeter appears after that "getting session list timeout", which is about a minute later than vt7, and does not have a password input field. lightdm blocked by VT_WAITACTIVE may be the cause... Tested with lightdm 1.2.0-0ubuntu2 in precise. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/997483/+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 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup
It seems to be that the problem occurs after this: ** (lightdm:1153): WARNING **: Error using VT_WAITACTIVE 7 on /dev/tty0: Interrupted system call (The console number depends on luck, of course.) I would guess that whatever code is emitting that error message is not handling the situation correctly. In case of "Interrupted system call" I would guess the correct way to handle the problem is to repeat the system call. I think the code instead emits this error and proceeds blindly forward. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/997483 Title: VT_WAITACTIVE does not work well with a multiseat setup Status in Light Display Manager: In Progress Status in lightdm package in Ubuntu: In Progress Bug description: Related to the fix introduced in bug #851612 . Saw this in lightdm.log (system call interrupted because of ctrl-alt-del pressed): [+2.97s] DEBUG: New display ready, switching to it [+2.97s] DEBUG: Activating VT 8 [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted system call [+77.56s] DEBUG: Got signal 15 from process 1 [+77.56s] DEBUG: Caught Terminated signal, shutting down And in x-1-greeter.log: [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001 [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000 [+50.56s] WARNING: Error getting session list from org.freedesktop.DisplayManager: Timeout was reached On vt7, unity-greeter would get stuck after password input. On vt8, unity-greeter appears after that "getting session list timeout", which is about a minute later than vt7, and does not have a password input field. lightdm blocked by VT_WAITACTIVE may be the cause... Tested with lightdm 1.2.0-0ubuntu2 in precise. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/997483/+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 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup
Happening here, too, randomly after return from S3 (Ubuntu 16.04.3 LTS). $ uname -a Linux desktop 4.10.0-38-lowlatency #42~16.04.1-Ubuntu SMP PREEMPT Tue Oct 10 17:35:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Using integrated intel graphics on i5-3570K. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/997483 Title: VT_WAITACTIVE does not work well with a multiseat setup Status in Light Display Manager: In Progress Status in lightdm package in Ubuntu: In Progress Bug description: Related to the fix introduced in bug #851612 . Saw this in lightdm.log (system call interrupted because of ctrl-alt-del pressed): [+2.97s] DEBUG: New display ready, switching to it [+2.97s] DEBUG: Activating VT 8 [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted system call [+77.56s] DEBUG: Got signal 15 from process 1 [+77.56s] DEBUG: Caught Terminated signal, shutting down And in x-1-greeter.log: [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001 [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000 [+50.56s] WARNING: Error getting session list from org.freedesktop.DisplayManager: Timeout was reached On vt7, unity-greeter would get stuck after password input. On vt8, unity-greeter appears after that "getting session list timeout", which is about a minute later than vt7, and does not have a password input field. lightdm blocked by VT_WAITACTIVE may be the cause... Tested with lightdm 1.2.0-0ubuntu2 in precise. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/997483/+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 1727291] Re: fonts-droid-fallback is missing "Provides: fonts-droid"
See also: https://bugs.launchpad.net/ubuntu/+source/fonts- android/+bug/1536547 ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1727291/+attachment/4994138/+files/JournalErrors.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1727291/+attachment/4994139/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1727291/+attachment/4994140/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1727291 Title: fonts-droid-fallback is missing "Provides: fonts-droid" Status in fonts-android package in Ubuntu: New Bug description: 16.04 LTS has renamed package "fonts-droid" as "fonts-droid-fallback" and the new package Breaks the old package. However, the new package is missing "Provides: fonts-droid" which would allow existing scripts and 3rd party packages with dependency to "fonts-droid" to continue working. Unless there's some reason not to include "Provides: fonts-droid" I would request adding it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: fonts-droid-fallback (not installed) ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-lowlatency 4.8.17 Uname: Linux 4.8.0-54-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Wed Oct 25 14:08:54 2017 InstallationDate: Installed on 2015-02-23 (975 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: fonts-android UpgradeStatus: Upgraded to xenial on 2016-06-10 (502 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1727291/+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 1727291] [NEW] fonts-droid-fallback is missing "Provides: fonts-droid"
Public bug reported: 16.04 LTS has renamed package "fonts-droid" as "fonts-droid-fallback" and the new package Breaks the old package. However, the new package is missing "Provides: fonts-droid" which would allow existing scripts and 3rd party packages with dependency to "fonts-droid" to continue working. Unless there's some reason not to include "Provides: fonts-droid" I would request adding it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: fonts-droid-fallback (not installed) ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-lowlatency 4.8.17 Uname: Linux 4.8.0-54-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Wed Oct 25 14:08:54 2017 InstallationDate: Installed on 2015-02-23 (975 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: fonts-android UpgradeStatus: Upgraded to xenial on 2016-06-10 (502 days ago) ** Affects: fonts-android (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1727291 Title: fonts-droid-fallback is missing "Provides: fonts-droid" Status in fonts-android package in Ubuntu: New Bug description: 16.04 LTS has renamed package "fonts-droid" as "fonts-droid-fallback" and the new package Breaks the old package. However, the new package is missing "Provides: fonts-droid" which would allow existing scripts and 3rd party packages with dependency to "fonts-droid" to continue working. Unless there's some reason not to include "Provides: fonts-droid" I would request adding it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: fonts-droid-fallback (not installed) ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-lowlatency 4.8.17 Uname: Linux 4.8.0-54-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Wed Oct 25 14:08:54 2017 InstallationDate: Installed on 2015-02-23 (975 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: fonts-android UpgradeStatus: Upgraded to xenial on 2016-06-10 (502 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1727291/+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 876279] Re: Upowerd excessive CPU usage
I found a workaround for Ubuntu 16.04 LTS:
(1) Open "Network connections" ("nm-connection-editor" from command line)
(2) Try to figure out which "Ethernet" connection is iPad
(3) Select the iPad and click "Edit"
(4) On "General" tab, uncheck "Automatically connect to this network when it is
available"
(5) On "IPv4 Settings" tab select "Method: Disabled"
(6) On "IPv6 Settings" tab select "Method: Ignore"
It seems that the issue is caused by iPad/iPhone pretending to offer
Ethernet connection and "upowerd" automatically trying to enable that
connection. This operation fails and "upowerd" is stupid enough to
repeat the process forever.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/876279
Title:
Upowerd excessive CPU usage
Status in upower package in Ubuntu:
Confirmed
Bug description:
Fresh installation of Oneiric on Activo A-1100 (Atom N450-based)
netbook. Top reports CPU usage fluctuating between 60% and 100%,
averaging around 80%. Machine still marginally usable, due to having a
second core.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: upower 0.9.13-1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Mon Oct 17 18:59:31 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, no user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/876279/+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 861642] Re: upowerd uses 100% cpu till killed
Duplicate bug 876279 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/861642 Title: upowerd uses 100% cpu till killed Status in upower package in Ubuntu: Confirmed Bug description: top - 12:57:54 up 2:56, 3 users, load average: 1.06, 1.12, 1.35 Tasks: 219 total, 2 running, 216 sleeping, 0 stopped, 1 zombie Cpu0 : 70.2%us, 29.8%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu1 : 2.3%us, 1.3%sy, 0.0%ni, 96.4%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu2 : 1.0%us, 0.3%sy, 0.0%ni, 98.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu3 : 0.7%us, 1.6%sy, 0.0%ni, 97.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu4 : 0.0%us, 0.3%sy, 0.0%ni, 99.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Cpu5 : 0.0%us, 0.3%sy, 0.0%ni, 98.3%id, 1.4%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 5994176k total, 4198260k used, 1795916k free,63308k buffers Swap: 8193144k total, 355188k used, 7837956k free, 334316k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 2268 root 20 0 148m 1572 680 R 100 0.0 111:08.37 upowerd ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: upower 0.9.9-4 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Sep 28 12:53:23 2011 ExecutablePath: /usr/lib/upower/upowerd InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: SourcePackage: upower UpgradeStatus: Upgraded to natty on 2011-04-06 (175 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/861642/+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 876279] Re: Upowerd excessive CPU usage
After upgrading from Ubuntu 14.04 LTS to 16.04 LTS (xenial) I'm affected by this bug, too. If I connect an Apple iPad Mini using USB cable (with the intent to charge the tablet only) I get excessive CPU usage. Process /usr/lib/upower/upowerd owned by root seems to be doing nothing but eating CPU until I manually kill it or disconnect the iPad. Comment #10 claims that this might be a kernel bug but the referenced source (http://web.archiveorange.com/archive/v/7azSgetwkAZWsEpXKXWy) is no longer available. $ apt-cache policy upower upower: Installed: 0.99.4-2ubuntu0.2 Candidate: 0.99.4-2ubuntu0.2 Version table: *** 0.99.4-2ubuntu0.2 500 500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.99.4-2 500 500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages $ uname -a Linux semyol-329-b 4.4.0-24-lowlatency #43-Ubuntu SMP PREEMPT Wed Jun 8 20:27:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/876279 Title: Upowerd excessive CPU usage Status in upower package in Ubuntu: Confirmed Bug description: Fresh installation of Oneiric on Activo A-1100 (Atom N450-based) netbook. Top reports CPU usage fluctuating between 60% and 100%, averaging around 80%. Machine still marginally usable, due to having a second core. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: upower 0.9.13-1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Mon Oct 17 18:59:31 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/876279/+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
