[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Agreed, the low activity could be because the bug is confirmed, reproduced and set at high priority. Most users who face the same issue (myself included) won't see any reason to add to the issue when a solution seems to be on its way. -- 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 gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: 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/gnome-shell/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
this should be the diff to be tested:
diff --git a/softwareproperties/qt/SoftwarePropertiesQt.py
b/softwareproperties/qt/SoftwarePropertiesQt.py
index 8172e25..b210323 100644
--- a/softwareproperties/qt/SoftwarePropertiesQt.py
+++ b/softwareproperties/qt/SoftwarePropertiesQt.py
@@ -709,8 +709,7 @@ class SoftwarePropertiesQt(SoftwareProperties):
home = QDir.homePath()
if "SUDO_USER" in os.environ:
home = os.path.expanduser("~%s" % os.environ["SUDO_USER"])
-url = KUrl.fromPath(home)
-filename = KFileDialog.getOpenFileName(url, 'application/pgp-keys',
self.userinterface, _("Import key"))
+filename = QFileDialog.getOpenFileName(self.userinterface, _("Import
key"), home, 'application/pgp-keys')
if filename:
if not self.add_key(filename):
title = _("Error importing selected file")
--
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/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
I see this as well. It seems to happen every 2 or 3 days as a result a some combination of random keystrokes. i reboot fixes the issue, but it is very annoying. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+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 1825378] Re: systemd-networkd doesn't set wireguard peer endpoint
I can confirm this issue with systemd/bionic-updates, now 237-3ubuntu10.39 amd64 Is there a way to get an bionic update as well? This is very annoying bug, as systemd-networkd intergrates with systemd- resolve and wg-quick does not. -- 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/1825378 Title: systemd-networkd doesn't set wireguard peer endpoint Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Cosmic: Invalid Status in systemd source package in Disco: Fix Released Status in systemd source package in Eoan: Fix Released Bug description: [impact] systemd does not set endpoints for wireguard interfaces correctly. This makes wireguard unusable. [test case] install a disco or eoan system and set up a wireguard interface: $ sudo add-apt-repository ppa:wireguard/wireguard $ sudo apt install wireguard ...(this does a lot of stuff)... create a file as below; There is no need to setup remote server to reproduce this issue, but PublicKey/PrivateKey should be valid one (used instructions from https://www.linode.com/docs/networking/vpn /set-up-wireguard-vpn-on-ubuntu/#configure-wireguard-server): $ cat /etc/systemd/network/wg0.netdev [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=uMuCbguKYdKanRYMbDSriIdgxGxJR57Us1zEy8wRc1M= ListenPort=51820 [WireGuardPeer] PublicKey=ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 $ sudo systemctl restart systemd-networkd $ sudo wg show wg0 interface: wg0 public key: BnvFgvPiVb5xURfzZ5liV1P77qeGeJDIX3C1iNquA2k= private key: (hidden) listening port: 51820 peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= allowed ips: 10.0.0.0/8 the last command should print remote endpoint address, e.g.: peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 [regression potential] any changes to systemd contain the potential for serious regressions. However, this is cherry picked directly from upstream, with the releases requiring patching (disco and eoan) being at exactly the same version and very close to upstream already. Additionally, while this does add 2 new functions (from upstream commit https://github.com/systemd/systemd/pull/11580/commits/abd48ec87f2ac5dd571a99dcb4db88c4affdffc8), they are only used - and code is only changed in - wireguard.c, so any regressions should be limited to wireguard interfaces (unless systemd crashes completely). [other info] this bug is not present in cosmic and earlier, and is already fixed in upstream systemd, so this is needed only for disco and eoan. original description: --- systemd/disco 240 shipped with Ubuntu 19.04 beta does not set endpoints for [WireguradPeer] properly. This regression was introduced in v241 and merged into v240. systemd 241 doesn't set wireguard peer endpoint https://github.com/systemd/systemd/issues/11579 Revert of the regression was landed on v240 stable branch https://github.com/systemd/systemd-stable/pull/39 1)2) confirmed with, systemd/disco 240-6ubuntu5 amd64 3) put a netdev file /etc/systemd/network/wg0.netdev --- [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=** ListenPort=51820 [WireGuardPeer] PublicKey=* AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 and run --- # systemctl restart systemd-networkd # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * allowed ips: 10.0.0.0/8 4) the last command should print remote endpoint address. --- # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825378/+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 saw this bug mentioned on https://discourse.ubuntu.com/t/release-bugs- for-week-commencing-monday-24th-february-2020/14540 with the comment "can’t confirm, lew activity, suggest we untarget from rls set" It would really be a shame if this stays the way it is now, since it is annoying for those that are hit by it, although with an easy workaround, just do anything else requiring authorisation, and then the toggles work too. For example highlighting one source and then selecting edit and then ok without do any changes. Or just repeating the mouse clicks until it works like others wrote. But those workarounds are not obvious for all new users. I can reproduce it by trying to toggle the extra sources with my mouse, It seems to work every time with keyboard though, maybe that is the reason not to be able to reproduce? This is on several different systems, both on physical hardware and in virtualbox, ranging from 18.04 to 20.04 including all those in between. And this is not just for the Canonical Partners repository, but any repositories I have in a system. On some system with not much extra or even fresh installs of 19.04 and 19.10 I can not reproduce it every time on the first try, but closing software-properties-gtk down and starting it again seems to increase the chance of a failure by a lot. So please try closing and opening a few times if you can not reproduce the bug. I am not sure but I think that app indicators like psensor and indicator-cpufreq also increase the chance of failure to display the authorization window. If I try to toggle an apt source and do not fix it with one of the working functions, or by repeating the mouse clicks, but instead wait for the screenlock to come and then unlock it, I actually get an authorisation window in the upper left corner. It does take my password, but software-properties-gtk does not get notified by it then. Mint asks for authorising right away on starting their modified software-properties-gtk, so they do not get this problem. If the bug can not be found and fixed in time for 20.04, could we then get a "unlock" button on the "Other Software" tab? Once any of the other functions that requires authorization have been used, the toggles on the "Other Software" tab do work every time. The "Revert" button actually gets active after the authorisation for the toggles fails, and that reliably opens the authorisation window. So maybe it could start active but with the text "Unlock" and then changing to the text "Revert" after a successful authorisation. Then there would be an obvious way for users that do not know the workarounds to toggle software sources, and those that do not experience the bug will not see any functionality changes. -- 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 gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: 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
[Touch-packages] [Bug 1866124] Re: ps -eo lxc no longer shows a task's lxc container
The top command's LXC column (not shown by default, but can be enabled
through the 'f' menu) also shows a - for all processes, including those
that belong to containers.
My containers are unprivileged, in case that matters.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1866124
Title:
ps -eo lxc no longer shows a task's lxc container
Status in lxc package in Ubuntu:
New
Status in procps package in Ubuntu:
New
Bug description:
When I use the ps command's "lxc" format specifier, for example:
ps -eo pid,lxc,command
The second output column is supposed to show "the name of the lxc
container within which a task is running. If a process is not running
inside a container, a dash ('-') will be shown." [1]
This worked fine until I upgraded from ubuntu 19.04 to 19.10, which
brought me from lxc 3.03 to 3.04. Now, that column always contains a
dash instead of the container name, even for processes that are
running inside a container. The "lxc" format specifier seems to be
broken now.
[1]
https://manpages.ubuntu.com/manpages/eoan/man1/ps.1.html#standard%20format%20specifiers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1866124/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails
Is this strictly a Thunderbird Bug? Or should it be moved to a more appropriate package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/802942 Title: printing PDFs (and other complex documents) from GTK applications fails Status in Mozilla Firefox: New Status in cups package in Ubuntu: Invalid Status in cups-filters package in Ubuntu: Invalid Status in firefox package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Hello, I'm discovering a bug when printing complex PDFs or other complex documents from GTK applications. Printing complex PDFs from evince, or sometimes even printing comples webpages from firefox result in one error page being printed instead of the document content: +-+ | ERROR NAME;| | undefined| | COMMAND; | | Q| | OPERAND STACK; | +-+ My printer is a Brother HL 5270DN. It doesn't matter whether the printer is connected via USB or as network printer. In both cases the described bug does happen. The PPD I use is "Brother HL-5270DN BR- Script3", similar to the one at http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd I discovered this bug in up-to-date Debian unstable for several years already. Now I switched one of my laptops to Ubuntu Natty (fresh installation), and unfortunately discovered the same bug there as well. I'm pretty sure that this bug is related to bug #419143, and not really in CUPS, but rather in some library (poppler or cairo) used by GTK applications. The same PDFs that produce the described error in evince, print fine in okular. I attach an example PDF that doesn't print in evince, but prints fine in okular. It's sufficient to (try to) print page 1 of the document. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cups 1.4.6-5ubuntu1.2 ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5 Uname: Linux 2.6.39-0-generic x86_64 Architecture: amd64 CupsErrorLog: Date: Tue Jun 28 13:13:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU MachineType: LENOVO 4180W1H Papersize: a4 PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3 ProcEnviron: LANGUAGE=de:en LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180W1H dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180W1H dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/802942/+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 1866124] [NEW] ps -eo lxc no longer shows a task's lxc container
Public bug reported:
When I use the ps command's "lxc" format specifier, for example:
ps -eo pid,lxc,command
The second output column is supposed to show "the name of the lxc
container within which a task is running. If a process is not running
inside a container, a dash ('-') will be shown." [1]
This worked fine until I upgraded from ubuntu 19.04 to 19.10, which
brought me from lxc 3.03 to 3.04. Now, that column always contains a
dash instead of the container name, even for processes that are running
inside a container. The "lxc" format specifier seems to be broken now.
[1]
https://manpages.ubuntu.com/manpages/eoan/man1/ps.1.html#standard%20format%20specifiers
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Affects: procps (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
When I use the ps command's "lxc" format specifier, for example:
ps -eo pid,lxc,command
The second output column is supposed to show "the name of the lxc
container within which a task is running. If a process is not running
inside a container, a dash ('-') will be shown." [1]
- This worked fine until I upgraded from ubuntu 19.04 to 19.10. Now, that
- column always contains a dash instead of the container name, even for
- processes that are running inside a container. The "lxc" format
- specifier seems to be broken now.
+ This worked fine until I upgraded from ubuntu 19.04 to 19.10, which
+ brought me from lxc 3.03 to 3.04. Now, that column always contains a
+ dash instead of the container name, even for processes that are running
+ inside a container. The "lxc" format specifier seems to be broken now.
-
- [1]
https://manpages.ubuntu.com/manpages/eoan/man1/ps.1.html#standard%20format%20specifiers
+ [1]
+
https://manpages.ubuntu.com/manpages/eoan/man1/ps.1.html#standard%20format%20specifiers
--
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/1866124
Title:
ps -eo lxc no longer shows a task's lxc container
Status in lxc package in Ubuntu:
New
Status in procps package in Ubuntu:
New
Bug description:
When I use the ps command's "lxc" format specifier, for example:
ps -eo pid,lxc,command
The second output column is supposed to show "the name of the lxc
container within which a task is running. If a process is not running
inside a container, a dash ('-') will be shown." [1]
This worked fine until I upgraded from ubuntu 19.04 to 19.10, which
brought me from lxc 3.03 to 3.04. Now, that column always contains a
dash instead of the container name, even for processes that are
running inside a container. The "lxc" format specifier seems to be
broken now.
[1]
https://manpages.ubuntu.com/manpages/eoan/man1/ps.1.html#standard%20format%20specifiers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1866124/+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 1866122] [NEW] hp laserjet m1319f stop printing work after ubuntu upgrade
Public bug reported: 3) What you expected to happen Before upgrade Ubuntu (reinstall), I used just to connect printer to usb and it worked. 4) What happened instead After system reinstall, I plug in same printer and it is stuck in an error without further messages. Outputs, see https://wiki.ubuntu.com/DebuggingPrintingProblems $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 $ apt-cache policy cups cups: Installed: 2.2.7-1ubuntu2.7 Candidate: 2.2.7-1ubuntu2.7 Version table: *** 2.2.7-1ubuntu2.7 500 500 http://mirror.ufscar.br/ubuntu bionic-updates/main amd64 Packages 500 http://mirror.ufscar.br/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.7-1ubuntu2 500 500 http://mirror.ufscar.br/ubuntu bionic/main amd64 Packages $ apt-cache policy hplip hplip: Installed: 3.17.10+repack0-5 Candidate: 3.17.10+repack0-5 Version table: *** 3.17.10+repack0-5 500 500 http://mirror.ufscar.br/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ lsmod | grep usb usblp 24576 0 btusb 57344 0 btrtl 20480 1 btusb btbcm 16384 1 btusb btintel24576 1 btusb bluetooth 573440 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm usbhid 53248 0 hid 131072 3 usbhid,hid_apple,hid_generic usb_storage73728 1 uas $ tail -f /var/log/syslog Mar 4 16:45:06 mbprot /hp-config_usb_printer: hp-config_usb_printer[10990]: error: hp-systray must be running.#012 Run 'hp-systray &' in a terminal. Mar 4 16:45:06 mbprot /hp-config_usb_printer: hp-config_usb_printer[10990]: error: HP Device plugin's are not installed. Please install plugin's using hp-plugin command. Mar 4 16:45:06 mbprot upowerd[1025]: unhandled action 'bind' on /sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1 Mar 4 16:45:06 mbprot upowerd[1025]: unhandled action 'bind' on /sys/devices/pci:00/:00:14.0/usb1/1-2 Mar 4 16:45:11 mbprot colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied Mar 4 16:45:34 mbprot kernel: [ 3902.670054] usb 1-2: USB disconnect, device number 9 Mar 4 16:45:34 mbprot kernel: [ 3902.670646] usblp0: removed Mar 4 16:45:11 mbprot colord-sane: message repeated 3 times: [ io/hpmud/musb.c 2101: Invalid usb_open: Permission denied] Mar 4 16:45:34 mbprot upowerd[1025]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1 Mar 4 16:45:34 mbprot upowerd[1025]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-2 Mar 4 16:45:45 mbprot kernel: [ 3913.631586] usb 1-2: new high-speed USB device number 10 using xhci_hcd Mar 4 16:45:45 mbprot kernel: [ 3913.782607] usb 1-2: New USB device found, idVendor=03f0, idProduct=5817, bcdDevice= 1.00 Mar 4 16:45:45 mbprot kernel: [ 3913.782613] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 4 16:45:45 mbprot kernel: [ 3913.782616] usb 1-2: Product: HP LaserJet M1319f MFP Mar 4 16:45:45 mbprot kernel: [ 3913.782619] usb 1-2: Manufacturer: Hewlett-Packard Mar 4 16:45:45 mbprot kernel: [ 3913.782622] usb 1-2: SerialNumber: PR40AZQ Mar 4 16:45:45 mbprot kernel: [ 3913.790585] usblp 1-2:1.1: usblp0: USB Bidirectional printer dev 10 if 1 alt 0 proto 2 vid 0x03F0 pid 0x5817 Mar 4 16:45:45 mbprot root: loading HP Device 001 010 Mar 4 16:45:45 mbprot python3: io/hpmud/musb.c 2189: [11031] hpmud_make_usb_uri() bus=001 dev=010 Mar 4 16:45:45 mbprot python3: io/hpmud/musb.c 2287: hpmud_make_usb_uri() uri=hp:/usb/HP_LaserJet_M1319f_MFP?serial=PR40AZQ bytes_read=45 Mar 4 16:45:45 mbprot /hp-config_usb_printer: hp-config_usb_printer[11031]: error: hp-systray must be running.#012 Run 'hp-systray &' in a terminal. Mar 4 16:45:45 mbprot /hp-config_usb_printer: hp-config_usb_printer[11031]: error: HP Device plugin's are not installed. Please install plugin's using hp-plugin command. Mar 4 16:45:46 mbprot upowerd[1025]: unhandled action 'bind' on /sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1 Mar 4 16:45:46 mbprot upowerd[1025]: unhandled action 'bind' on /sys/devices/pci:00/:00:14.0/usb1/1-2 ^C $ lsusb Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0259 Apple, Inc. Bus 001 Device 006: ID 05ac:8289 Apple, Inc. Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 010: ID 03f0:5817 Hewlett-Packard LaserJet M1319f MFP Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ ls -l /dev/usb/lp* /dev/bus/usb/*/* crw-rw-r-- 1 root root 189, 0 mar 4 15:28 /dev/bus/usb/001/001 crw-rw-r-- 1 root root 189, 1 mar 4 15:28 /dev/bus/usb/001/002 crw-rw-r-- 1 root root 189, 2 mar 4 15:28 /dev/bus/usb/001/003 crw-rw-r-- 1 root root 189, 5 mar 4 15:29
[Touch-packages] [Bug 1865351] Re: Update to poppler 0.86.1 in Focal
** Changed in: poppler (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1865351 Title: Update to poppler 0.86.1 in Focal Status in poppler package in Ubuntu: New Bug description: Please update to poppler 0.86.1 in Focal https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/NEWS Release 0.86.1: core: * Fix regression in Browse Link handling * Internal code improvements Release 0.86.0: core: * Fix link content exfiltration attack * Splash: Implement gouraudTriangleShadedFill for some non parametrized shadings * Fix case unsensitive search for Old Hungarian, Warang Citi, Medefaidrin and Adlam * Internal code improvements glib: * Automatic handle of page's cropbox on annots. Issue #129 * Fix memory leak if poppler_document_new_from_file fails * Minor speed optimization on poppler_page_get_annot_mapping utils: * pdfdetach: add 'savefile' option * pdftoppm/pdftocairo: Fix more odd/even mismatch qt5: * Fix loading from iodevice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1865351/+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 1832057] Re: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow
*** This bug is a duplicate of bug 1829401 *** https://bugs.launchpad.net/bugs/1829401 The bug occurred after my upgrade to Focal Fossa after the reboot, while I was reactivating the ppa's. -- 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/1832057 Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow Status in software-properties package in Ubuntu: Confirmed Bug description: Falló actualización de repositorios ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: software-properties-gtk 0.98.4 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 21:32:02 2019 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-06-02 (5 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 --toplevel 75497475 ProcEnviron: LANGUAGE=es_SV:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_SV.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', '--toplevel', '75497475'] PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: software-properties Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow UpgradeStatus: Upgraded to eoan on 2019-06-02 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1832057/+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 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
It's not an upstream bug. I checked several other distribution with different themes, none of them is affected. Only Ubuntu's gnome-terminal is affected. I don't understand why this simple bug is still around after realizing it was reported 3 years ago! I am retrying to home on Ubuntu after several years of leave, but again annoyed by this bug! The report saying 'fixed released' without any fixes! Please, try to fix these annoying bugs which preventing us to use themes other than default Ones! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+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 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
I support the idea in the last para. of @egmont-gmail. If a patch introduce a regression which is worse than the improvement made by the patch, the patch should be dropped. I'm getting tired of Ubuntu fixing something and breaking some other things. Ubuntu LTS was rock solid once upon a time, but for regular users I don't see any point using LTS these days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+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 1865387] Re: Linux Biolinum O italic lowercase m not displayed by poppler
http://git.ghostscript.com/?p=user/chrisl/freetype2.git;a=commitdiff;h=c9a14b040932 is the upstream freetype fix if someone wants to work on backporting the change ** Changed in: fonts-linuxlibertine (Ubuntu) Status: New => Invalid ** Changed in: freetype (Ubuntu) Status: New => Triaged ** Changed in: freetype (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1865387 Title: Linux Biolinum O italic lowercase m not displayed by poppler Status in FreeType: Unknown Status in Linux Libertine: New Status in fonts-linuxlibertine package in Ubuntu: Invalid Status in freetype package in Ubuntu: Triaged Bug description: STEPS TO REPRODUCE: Create a PDF document with the character U+006D LATIN SMALL LETTER M in Linux Biolinum O, for example with libreoffice. Expected behavior: The 'm' is displayed Actual behavior: The 'm' is not displayed (but does take up space) This issue is discussed in this thread in the poppler forum, which leads me to think it is a problem with the font: https://lists.nongnu.org/archive/html/freetype- devel/2018-12/msg00063.html ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: fonts-linuxlibertine 5.3.0-4 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Mar 1 17:13:17 2020 Dependencies: PackageArchitecture: all SourcePackage: fonts-linuxlibertine UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/freetype/+bug/1865387/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
I have a similar problem: more than 4000 messages: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.6.0-050600rc4-generic/modules.builtin.bin' installing kernel 5.6.0-050600rc4-generic downloadsd from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc4/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1864992 Title: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' Status in curtin: Invalid Status in subiquity: New Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: During a Focal install from the ISO image several errors like: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' are logged in curtin's install logs. The installed system boots and works fine, but the error is clearly something we want to get rid of. At first glance this seems related to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261 but the version of initramfs-tools in both the installer and installed system (checked with `chroot /target dpkg -l initramfs-tools` during the installation) is 0.136ubuntu1, which should contain Rafael's fix for that bug. I wonder if the update-initramfs diversion has a role here. I verified this happens at least on amd64 and arm64. I'm attaching the full install logs for a amd64 installation. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperVersion: 1.439 DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 ProcFB: 0 qxldrmfb ProcKernelCmdLine: initrd=/casper/initrd quiet --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1864992/+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 1866066] Re: Sound defaults to DUMMY output on resume
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- 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/1866066 Title: Sound defaults to DUMMY output on resume Status in pulseaudio package in Ubuntu: New Bug description: Sounds works perfectly. Suspend the laptop and then upon resume sound is switched to DUMMY OUTPUT requires restart. Just started happening. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 ProcVersionSignature: Ubuntu 5.3.0-7629.31~1581628854~18.04~2db8a7a~dev-generic 5.3.13 Uname: Linux 5.3.0-7629-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Mar 4 07:43:54 2020 InstallationDate: Installed on 2020-02-06 (26 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03-1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp3-c dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: galp3-c dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03-1:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.sku: Not Applicable dmi.product.version: galp3-c dmi.sys.vendor: System76 modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-03-04T07:42:51.788265 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866066/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
There are no PyKDE imports anymore, only PyQt. That said, replacing
`KUrl.fromPath` with just `QUrl` should resolve that.
But that's not our only issue:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py",
line 713, in add_key_clicked
filename = KFileDialog.getOpenFileName(url, 'application/pgp-keys',
self.userinterface, _("Import key"))
NameError: name 'KFileDialog' is not defined
So we replace `KFileDialog` with `QFileDialog` and move some arguments
around:
filename = QFileDialog.getOpenFileName(self.userinterface, _("Import
key"), url, 'application/pgp-keys')
The only other thing missing is that KFileDialog wanted a KUrl while
QFileDialog wants a string. So we should cast our QUrl call:
url = str(QUrl(home))
Maybe there's a prettier/better way to do this, but that's what I got
for 10 minutes which is more progress than I can say this bug has had in
the past XD If people can test those changes, it would be greatly
appreciated.
** Changed in: software-properties (Ubuntu)
Status: Confirmed => Triaged
--
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/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug
It certainly caused me to waste some time trying to work out why it was not sending them. -- 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/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Triaged Status in apport source package in Bionic: Triaged Status in apport source package in Disco: Triaged Status in apport source package in Eoan: Triaged Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
According to the dupe, this affects more recent versions, too. And not
just Kubuntu.
** Summary changed:
- software-properties-kde attempts to use KUrl but it doesn't exist
+ software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
** Tags added: eoan focal kubuntu lubuntu
--
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/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 1865906] Re: software-properties-{qt, kde} import key issue
*** This bug is a duplicate of bug 1795278 ***
https://bugs.launchpad.net/bugs/1795278
** Summary changed:
- software-properties-* import key issue
+ software-properties-{qt,kde} import key issue
** This bug has been marked a duplicate of bug 1795278
software-properties-kde attempts to use KUrl but it doesn't exist
--
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/1865906
Title:
software-properties-{qt,kde} import key issue
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
My system: Lubuntu 19.04 run from Live-CD (from the original ISO
image)
Note: Followig issue apply to both software-properties: Qt and KDE run from
LiveCD.
After opening thru the console (as root) the software-properties,
switching to the "Authentication" tab and pressing the "Import key
file", I recieve following error output:
# software-properties-qt
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Trackback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py",
line 712, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
=
same happens with software-properties-kde.
When I'm trying to check their version, I'll get following output:
# software-properties-qt -v
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-
root'
software-properties-qt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1865906/+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 1862913] Re: ubuntu-bug failing silently if Settings > Privacy > Problem Reporting disabled
*** This bug is a duplicate of bug 1814611 *** https://bugs.launchpad.net/bugs/1814611 ** Tags added: focal ** This bug has been marked a duplicate of bug 1814611 turning off "Send error reports to Canonical" prevents using ubuntu-bug -- 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/1862913 Title: ubuntu-bug failing silently if Settings > Privacy > Problem Reporting disabled Status in apport package in Ubuntu: New Bug description: On a system running Ubuntu 19.10 (upgraded over several versions) if Settings > Privacy > Problem Reporting is disabled then running ubuntu-bug collects the data and asks if it should send it. On clicking Send it silently terminates and does nothing. An appropriate response would either be to send the data anyway, since the user has been explicitly asked, or to fail with a message explaining why. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportLog: ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: called for pid 2865, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: executable: /usr/lib/tracker/tracker-miner-fs (command line "/usr/lib/tracker/tracker-miner-fs") ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: debug: session gdbus call: (true,) ERROR: apport (pid 3384) Mon Feb 10 14:41:31 2020: wrote report /var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 09:03:53 2020 InstallationDate: Installed on 2014-10-21 (1939 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1862913/+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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
Thx 'abhir...@in.ibm.com' for verification - the tags are set to done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26
[Touch-packages] [Bug 1865504] Re: hwclock reports incorrect status in audit message
** Attachment added: "debdiff for focal"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+attachment/5333544/+files/debdiff.focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865504
Title:
hwclock reports incorrect status in audit message
Status in util-linux package in Ubuntu:
New
Status in util-linux package in Debian:
Unknown
Bug description:
[IMPACT]
hwclock reports incrorect status in audit message
hwclock calls audit_log_user_message(3) to create an audit entry.
audit_log_user_message(3) result 1 is "success" and 0 is
"failed", hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse
status. Thus reports it's status incorrectly in audit message.
It is a requirement for Common Criteria Certification that hwclock
reports correct status in audit message.
This has been fixed upstream in https://github.com/karelzak/util-
linux/commit/189edf1fe501ea39b35911337eab1740888fae7a
[TEST]
Steps to test:
1. Install auditd
2. Run following testcase,
# hwclock
2020-03-02 15:03:03.280351+
# hwclock --set --date "1/1/2000 00:00:00"
# echo $?
0
# hwclock
2000-01-01 00:00:05.413924+
# hwclock --utc --systohc
# echo $?
0
# hwclock
2020-03-02 15:07:00.264331+
Following audit messages from /var/log/audit/audit.log,
type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0 auid=1000
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips
addr=? terminal=pts/0 res=failed'
type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0 auid=1000
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips
addr=? terminal=pts/0 res=failed'
Note that last entry in each audit record produced when hardware clock
was modified has, "res=failed". Although, testcase shows no failure
occurred.
[Regression Potential]
There should not be any regression to fix the status given to auditd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1865504] Re: hwclock reports incorrect status in audit message
Build log
https://launchpad.net/~j-latten/+archive/ubuntu/joyppa/+build/18795481
** Bug watch added: Debian Bug tracker #953065
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953065
** Also affects: util-linux (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953065
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865504
Title:
hwclock reports incorrect status in audit message
Status in util-linux package in Ubuntu:
New
Status in util-linux package in Debian:
Unknown
Bug description:
[IMPACT]
hwclock reports incrorect status in audit message
hwclock calls audit_log_user_message(3) to create an audit entry.
audit_log_user_message(3) result 1 is "success" and 0 is
"failed", hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse
status. Thus reports it's status incorrectly in audit message.
It is a requirement for Common Criteria Certification that hwclock
reports correct status in audit message.
This has been fixed upstream in https://github.com/karelzak/util-
linux/commit/189edf1fe501ea39b35911337eab1740888fae7a
[TEST]
Steps to test:
1. Install auditd
2. Run following testcase,
# hwclock
2020-03-02 15:03:03.280351+
# hwclock --set --date "1/1/2000 00:00:00"
# echo $?
0
# hwclock
2000-01-01 00:00:05.413924+
# hwclock --utc --systohc
# echo $?
0
# hwclock
2020-03-02 15:07:00.264331+
Following audit messages from /var/log/audit/audit.log,
type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0 auid=1000
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips
addr=? terminal=pts/0 res=failed'
type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0 auid=1000
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips
addr=? terminal=pts/0 res=failed'
Note that last entry in each audit record produced when hardware clock
was modified has, "res=failed". Although, testcase shows no failure
occurred.
[Regression Potential]
There should not be any regression to fix the status given to auditd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1864253] Re: Pulseaudio sink/source selection, weird behaviour.
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- 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/1864253 Title: Pulseaudio sink/source selection, weird behaviour. Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: I have a Laptop connected to an USB-C dock. By default the docks analog audio output is chosen as the default pulse audio sink. I want that the analog output of the Laptop is the default, hence I configured this in /etc/pulse/default.py This does not work and journalctl informs me that the device chosen by me (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached output from journalctl. I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp to prevent pulseaudio getting started in gdm to prevent device capture. This does not work, the device does still not exist. Restarting pulseaudio sometimes, but not always sets the configured default sink. Furthermore plugging in the headphones in the Laptops analog input switches audio to the dock. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: findus 3055 F pulseaudio /dev/snd/controlC1: findus 3055 F pulseaudio /dev/snd/controlC0: findus 3055 F pulseaudio /dev/snd/pcmC0D0p: findus 3055 F...m pulseaudio CurrentDesktop: i3 Date: Fri Feb 21 22:19:04 2020 InstallationDate: Installed on 2019-06-13 (253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET80W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S0UB00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S0UB00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439 mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938 mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1864253/+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 1855009] Re: autopkgtests all fail on s390x
autopkgtests on s390x now pass (well, are 'neutral'): https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/n/network-manager/20200303_120208_f754d@/log.gz also since this is now bundled with a non-autopkgtest-only change, i'll remove the block-proposed tag ** Tags removed: block-proposed-bionic verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1855009] Re: autopkgtests all fail on s390x
as this will never leave disco-proposed, marking wontfix for disco ** Changed in: network-manager (Ubuntu Disco) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1850267] Re: autopkgtest 'nm' fails because it can't find dnsmasq
autopkgtests now pass: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/n/network-manager/20200303_121053_bbc2d@/log.gz also since this is now bundled with a non-autopkgtest-only change, i'll remove the block-proposed tag ** Tags removed: block-proposed-bionic verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1850267 Title: autopkgtest 'nm' fails because it can't find dnsmasq Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: [impact] test 'nm' fails because dnsmasq-base isn't installed [test case] see test results http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64 [regression potential] low, test fix only [other info] The d/t/control file 'nm' test section, for bionic, needs to include dnsmasq-base in its dep list. disco and later already include dnsmasq-base in test dep packages, and in xenial network-manager directly depends on dnsmasq-base. So this is needed only for bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850267/+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 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic
Sorry, I was getting that confused with another file, modules.builtin.modinfo. That was the one we just added to linux- modules. modules.builtin.bin is generated by depmod, and if I remove the file for a given kernel and run depmod I get these messages. So this looks like something fully from depmod and not a result of anything wrong in our kernel packages. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1866012 Title: depmod ERROR during Setting up linux-modules-5.4.0-17-generic Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Deploy Focal on a KVM ndoe, enable proposed 2. Run sudo apt dist-upgrade The console will be flushed with: Setting up libisc1105:amd64 (1:9.11.16+dfsg-3~build1) ... Setting up linux-modules-5.4.0-17-generic (5.4.0-17.21) ... depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' Setting up apt-utils (1.9.12) ... Setting up libselinux1-dev:amd64 (3.0-1build2) ... Setting up libglib2.0-0:amd64 (2.64.0-1) ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: User Name 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 4 08:29 seq crw-rw 1 root audio 116, 33 Mar 4 08:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 4 09:06:42 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-5.4 StagingDrivers: exfat UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+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 1776622] Re: snapd updates on focal never finish installing. Can't install any other updates.
I can confirm i hit this with a fresh install of Focal Desktop today. -- 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/1776622 Title: snapd updates on focal never finish installing. Can't install any other updates. Status in snapd: Confirmed Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't install any other updates. The first time I gave up waiting and killed it. Then... $ sudo apt full-upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. $ sudo dpkg --configure -a Setting up snapd (2.33+18.10ubuntu3) ... snapd.snap-repair.service is a disabled or a static unit, not starting it. << never ends >> All the while the snap and snapd process use about 0.3% CPU (which is more than usual). WORKAROUND: sudo killall apt dpkg sudo dpkg -r snapd gnome-software-plugin-snap sudo apt update sudo apt full-upgrade --- ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: snapd 2.33+18.10ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 Date: Wed Jun 13 16:49:20 2018 InstallationDate: Installed on 2018-05-26 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776622/+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 1863825] Re: 20.04 apt update of python 3.8 gives errors
*** This bug is a duplicate of bug 1863414 *** https://bugs.launchpad.net/bugs/1863414 i solve this Using choosing another version of Ubuntu sudo update-alternatives --config python3 and i choosed another version of Ubuntu i already used -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863825 Title: 20.04 apt update of python 3.8 gives errors Status in python3-defaults package in Ubuntu: Confirmed Bug description: Run sudo apt dist-upgrade on 20.04 install. Expected result: python3 is updated without issue Actual result: After this operation, 1,114 kB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-minimal amd64 3.8.0-3ubuntu1 [23.3 kB] Get:2 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3 amd64 3.8.0-3ubuntu1 [47.6 kB] Get:3 http://us.archive.ubuntu.com/ubuntu focal/main amd64 libpython3-stdlib amd64 3.8.0-3ubuntu1 [6,872 B] Get:4 http://us.archive.ubuntu.com/ubuntu focal/main amd64 libnewt0.52 amd64 0.52.21-4ubuntu2 [41.1 kB] Get:5 http://us.archive.ubuntu.com/ubuntu focal/main amd64 whiptail amd64 0.52.21-4ubuntu2 [17.0 kB] Get:6 http://us.archive.ubuntu.com/ubuntu focal/main amd64 gnome-disk-utility amd64 3.35.91-1ubuntu1 [186 kB] Get:7 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 onboard-data all 1.4.1-2ubuntu7 [3,803 kB] Get:8 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 onboard amd64 1.4.1-2ubuntu7 [351 kB] Get:9 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 onboard-common all 1.4.1-2ubuntu7 [530 kB] Get:10 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 python3-html5-parser amd64 0.4.9-3build1 [125 kB] Get:11 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-renderpm amd64 3.5.34-1build1 [60.4 kB] Get:12 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-reportlab-accel amd64 3.5.34-1build1 [19.4 kB] Get:13 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-reportlab all 3.5.34-1build1 [546 kB] Get:14 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-systemd amd64 234-3build2 [36.5 kB] Fetched 5,793 kB in 8s (694 kB/s) (Reading database ... 529746 files and directories currently installed.) Preparing to unpack .../python3-minimal_3.8.0-3ubuntu1_amd64.deb ... Unpacking python3-minimal (3.8.0-3ubuntu1) over (3.8.0-3) ... Setting up python3-minimal (3.8.0-3ubuntu1) ... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be use d self.stdin = io.open(p2cwrite, 'wb', bufsize) (Reading database ... 529746 files and directories currently installed.) Preparing to unpack .../00-python3_3.8.0-3ubuntu1_amd64.deb ... running python pre-rtupdate hooks for python3.8... Unpacking python3 (3.8.0-3ubuntu1) over (3.8.0-3) ... Preparing to unpack .../01-libpython3-stdlib_3.8.0-3ubuntu1_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.8.0-3ubuntu1) over (3.8.0-3) ... Preparing to unpack .../02-libnewt0.52_0.52.21-4ubuntu2_amd64.deb ... Unpacking libnewt0.52:amd64 (0.52.21-4ubuntu2) over (0.52.21-4ubuntu1) ... Preparing to unpack .../03-whiptail_0.52.21-4ubuntu2_amd64.deb ... Unpacking whiptail (0.52.21-4ubuntu2) over (0.52.21-4ubuntu1) ... Preparing to unpack .../04-gnome-disk-utility_3.35.91-1ubuntu1_amd64.deb ... Unpacking gnome-disk-utility (3.35.91-1ubuntu1) over (3.35.2-1ubuntu1) ... Preparing to unpack .../05-onboard-data_1.4.1-2ubuntu7_all.deb ... Unpacking onboard-data (1.4.1-2ubuntu7) over (1.4.1-2ubuntu6) ... Preparing to unpack .../06-onboard_1.4.1-2ubuntu7_amd64.deb ... Unpacking onboard (1.4.1-2ubuntu7) over (1.4.1-2ubuntu6) ... Preparing to unpack .../07-onboard-common_1.4.1-2ubuntu7_all.deb ... Unpacking onboard-common (1.4.1-2ubuntu7) over (1.4.1-2ubuntu6) ... Preparing to unpack .../08-python3-html5-parser_0.4.9-3build1_amd64.deb ... Unpacking python3-html5-parser (0.4.9-3build1) over (0.4.9-3) ... Preparing to unpack .../09-python3-renderpm_3.5.34-1build1_amd64.deb ... Unpacking python3-renderpm:amd64 (3.5.34-1build1) over (3.5.34-1) ... Preparing to unpack .../10-python3-reportlab-accel_3.5.34-1build1_amd64.deb ... Unpacking python3-reportlab-accel:amd64 (3.5.34-1build1) over (3.5.34-1) ... Preparing to unpack
[Touch-packages] [Bug 1864253] Re: Pulseaudio sink/source selection, weird behaviour.
Ubuntu does not have to fix anything. -- 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/1864253 Title: Pulseaudio sink/source selection, weird behaviour. Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a Laptop connected to an USB-C dock. By default the docks analog audio output is chosen as the default pulse audio sink. I want that the analog output of the Laptop is the default, hence I configured this in /etc/pulse/default.py This does not work and journalctl informs me that the device chosen by me (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached output from journalctl. I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp to prevent pulseaudio getting started in gdm to prevent device capture. This does not work, the device does still not exist. Restarting pulseaudio sometimes, but not always sets the configured default sink. Furthermore plugging in the headphones in the Laptops analog input switches audio to the dock. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: findus 3055 F pulseaudio /dev/snd/controlC1: findus 3055 F pulseaudio /dev/snd/controlC0: findus 3055 F pulseaudio /dev/snd/pcmC0D0p: findus 3055 F...m pulseaudio CurrentDesktop: i3 Date: Fri Feb 21 22:19:04 2020 InstallationDate: Installed on 2019-06-13 (253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET80W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S0UB00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S0UB00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439 mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938 mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1864253/+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 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic
Adding kmod, since the error comes from depmod. The file it's complaining about is relatively new (added in 5.2 timeframe iirc), and we haven't been shipping it. However as of 5.4.0-17 we are shipping it in linux-modules. I've confirmed that /lib/modules/5.4.0-17-generic/modules.builtin.bin is there after the installation, so I don't yet know why it wouldn't be there when depmod runs. ** Also affects: kmod (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1866012 Title: depmod ERROR during Setting up linux-modules-5.4.0-17-generic Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Deploy Focal on a KVM ndoe, enable proposed 2. Run sudo apt dist-upgrade The console will be flushed with: Setting up libisc1105:amd64 (1:9.11.16+dfsg-3~build1) ... Setting up linux-modules-5.4.0-17-generic (5.4.0-17.21) ... depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' Setting up apt-utils (1.9.12) ... Setting up libselinux1-dev:amd64 (3.0-1build2) ... Setting up libglib2.0-0:amd64 (2.64.0-1) ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: User Name 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 4 08:29 seq crw-rw 1 root audio 116, 33 Mar 4 08:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 4 09:06:42 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-5.4 StagingDrivers: exfat UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+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 1794478] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2020-03-04 08:55 EDT--- The network manager fix provided is working fine. The version on the tested machine is as below: root@NetworkTest:/usr/local/zACI/test/suites/net/web# dpkg -l | grep 1.10.6-2ubuntu1.4 ii libnm0:s390x 1.10.6-2ubuntu1.4 s390xGObject-based client library for NetworkManager ii network-manager 1.10.6-2ubuntu1.4 s390xnetwork management framework (daemon and userspace tools) root@ABHIRAM:/usr/local/zACI/test/suites/net/web# Ok with changing the tag from verification-needed-bionic to verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0
[Touch-packages] [Bug 1865450] Re: PermissionError for AppArmor Profiles i.e., SSH
Thanks John. It was a capability issue i.e., adding the CAP_MKNOD fixed
the problems and I don't see the never ending denials anymore. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1865450
Title:
PermissionError for AppArmor Profiles i.e., SSH
Status in apparmor package in Ubuntu:
New
Bug description:
I have created an AppArmor profile for SSH.
The profile is created successfully but each time I run aa-logprof it gives
PermissionError: [Errno 13]
An example of the error:
Traceback (most recent call last):
File "/usr/sbin/aa-enforce", line 35, in module>
tool.cmd_enforce()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 150, in
cmd_enforce
apparmor.set_enforce(profile, program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 293, in
set_enforce
change_profile_flags(filename, program, 'complain', False)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 704, in
change_profile_flags
set_profile_flags(filename, program, newflags)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 753, in
set_profile_flags
os.rename(temp_file.name, prof_filename)
PermissionError: [Errno 13] Permission denied:
'/etc/apparmor.d/usr.sbin.tcpdumpwvx1h0xl~' ->
'/etc/apparmor.d/usr.sbin.tcpdump'
Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
and attach this file.
+++
Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in
apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 1824, in
do_logprof_pass
save_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 1921, in
save_profiles
write_profile_ui_feedback(profile_name)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3404, in
write_profile_ui_feedback
write_profile(profile)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3413, in
write_profile
newprof = tempfile.NamedTemporaryFile('w', suffix='~', delete=False,
dir=profile_dir)
File "/usr/lib/python3.5/tempfile.py", line 688, in NamedTemporaryFile
(fd, name) = _mkstemp_inner(dir, prefix, suffix, flags, output_type)
File "/usr/lib/python3.5/tempfile.py", line 399, in _mkstemp_inner
fd = _os.open(file, flags, 0o600)
PermissionError: [Errno 13] Permission denied: '/etc/apparmor.d/tmpujtge2jq~'
An unexpected error occurred!
For details, see /tmp/apparmor-bug report-5qnjyx3t.txt
Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
and attach this file.
+++
+++
root@protegrity-framework314:/var/www# aa-complain /etc/apparmor.d/*
Profile for /etc/apparmor.d/abstractions not found, skipping
Profile for /etc/apparmor.d/apache2.d not found, skipping
Setting /etc/apparmor.d/bin.ping to complain mode.
Profile for /etc/apparmor.d/cache not found, skipping
Profile for /etc/apparmor.d/disable not found, skipping
Setting /etc/apparmor.d/etc.opt.Cluster.cluster_config.status.xml to complain
mode.
Setting /etc/apparmor.d/etc.opt.Cluster.cluster_config.xml to complain mode.
Traceback (most recent call last):
File "/usr/sbin/aa-complain", line 35, in
tool.cmd_complain()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 165, in
cmd_complain
apparmor.set_complain(profile, program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 286, in
set_complain
change_profile_flags(filename, program, 'complain', True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 704, in
change_profile_flags
set_profile_flags(filename, program, newflags)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 720, in
set_profile_flags
temp_file = tempfile.NamedTemporaryFile('w', prefix=prof_filename,
suffix='~', delete=False, dir=profile_dir)
File "/usr/lib/python3.5/tempfile.py", line 688, in NamedTemporaryFile
(fd, name) = _mkstemp_inner(dir, prefix, suffix, flags, output_type)
File "/usr/lib/python3.5/tempfile.py", line 399, in _mkstemp_inner
fd = _os.open(file, flags, 0o600)
PermissionError: [Errno 13] Permission denied:
'/etc/apparmor.d/etc.opt.Cluster.cluster_config.xml7m7t4rvb~'
An unexpected error occurred!
For details, see /tmp/apparmor-bugreport-oe_mo879.txt
Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
and attach this file.
++
Secondly, once
[Touch-packages] [Bug 1866062] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@429:parse_arguments:print_usage:_print_message
This seems to occur when an executable that has been deleted crashes -- the apport hook is called with the executable name set to "/path/to/exe (deleted)" and somehow this is being split on spaces and the extra (deleted) argument causes this crash. But simple attempts at reproducing this scenario failed. -- 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/1866062 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@429:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu18, the problem page at https://errors.ubuntu.com/problem/4450779f25a7f4e3c3713198defeefd98859f1a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866062/+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 1866062] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@429:parse_arguments:print_usage:_print_message
Here is the Traceback: Traceback (most recent call last): File "/usr/share/apport/apport", line 429, in options = parse_arguments() File "/usr/share/apport/apport", line 374, in parse_arguments parser.print_usage() File "/usr/lib/python3.7/argparse.py", line 2484, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.7/argparse.py", line 2495, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' ** Changed in: apport (Ubuntu) Status: New => Triaged -- 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/1866062 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@429:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu18, the problem page at https://errors.ubuntu.com/problem/4450779f25a7f4e3c3713198defeefd98859f1a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866062/+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 1866069] [NEW] Investigate segfault on Mir
Public bug reported:
This occurs with the development version of Mir running on 18.04LTS (not
seen on later series). (This version of Mir can be installed from ppa
:mir-team/dev).
1. Start multiscreen Mir-on-X: miral-app -demo-server --x11-output
640x480:800x600.
2. Position windows side-by-side to make it easy to move cursor across windows.
3. Drag the terminal window back and forth between windows.
Expect: everything works smoothly.
Actual: Eventually (can take 30sec) a core dump.
It looks like internal mesa state is inconsistent as src_mt is assigned with
intelImage->mt and not changed in ntel_miptree_copy_teximage() but...
...
multi-thre Thread 0x7fee68b117 In: intel_miptree_copy_teximage
L1438 PC: 0x7fee6bd1739a
(gdb) f 1
#1 0x7fee6bd1739a in intel_miptree_copy_teximage (brw=0x55e9f1a066a0,
intelImage=0x7fee58075fc0, dst_mt=0x7fee5807b120)
at ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1438
(gdb) p src_mt
$1 = (struct intel_mipmap_tree *) 0x0
(gdb) p intelImage->mt
$2 = (struct intel_mipmap_tree *) 0x7fee5807b120
Backtrace:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7fee6bd16ea6 in intel_miptree_copy_slice (brw=0x55e9f1a066a0,
src_mt=0x0, src_level=0, src_layer=0, dst_mt=0x7fee5807b120,
dst_level=0, dst_layer=0) at
../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1332
1332../src/mesa/drivers/dri/i965/intel_mipmap_tree.c: No such file or
directory.
[Current thread is 1 (Thread 0x7fee68b11700 (LWP 7872))]
(gdb) bt
#0 0x7fee6bd16ea6 in intel_miptree_copy_slice (brw=0x55e9f1a066a0,
src_mt=0x0, src_level=0, src_layer=0, dst_mt=
0x7fee5807b120, dst_level=0, dst_layer=0) at
../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1332
#1 0x7fee6bd1739a in intel_miptree_copy_teximage (brw=0x55e9f1a066a0,
intelImage=0x7fee58075fc0, dst_mt=0x7fee5807b120)
at ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1438
#2 0x7fee6bd280e6 in intel_finalize_mipmap_tree (brw=0x55e9f1a066a0,
tObj=0x7fee58086910)
at ../src/mesa/drivers/dri/i965/intel_tex_validate.c:179
#3 0x7fee6bd281fb in brw_validate_textures (brw=0x55e9f1a066a0) at
../src/mesa/drivers/dri/i965/intel_tex_validate.c:219
#4 0x7fee6bce3932 in brw_prepare_drawing (ctx=0x55e9f1a066a0, ib=0x0,
index_bounds_valid=true, min_index=0, max_index=3)
at ../src/mesa/drivers/dri/i965/brw_draw.c:816
#5 0x7fee6bce4496 in brw_draw_prims (ctx=0x55e9f1a066a0,
prims=0x7fee68b10480, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001',
min_index=0, max_index=3, gl_xfb_obj=0x0, stream=0, indirect=0x0) at
../src/mesa/drivers/dri/i965/brw_draw.c:1148
#6 0x7fee6c0e4163 in _mesa_draw_arrays (ctx=0x55e9f1a066a0, mode=5,
start=0, count=4, numInstances=1, baseInstance=0, drawID=0)
at ../src/mesa/main/draw.c:374
#7 0x7fee6c0e48eb in _mesa_DrawArrays (mode=5, start=0, count=4) at
../src/mesa/main/draw.c:531
#8 0x7fee77148a8a in
mir::renderer::gl::Renderer::draw(mir::graphics::Renderable const&) const
(this=0x7fee58000b20, renderable=
...) at /home/alan/display_server/mir/src/renderers/gl/renderer.cpp:631
#9 0x7fee77147e13 in
mir::renderer::gl::Renderer::render(std::vector,
std::allocator > > const&) const
(this=0x7fee58000b20, renderables=std::vector of length 2, capacity 2 = {...})
at /home/alan/display_server/mir/src/renderers/gl/renderer.cpp:437
#10 0x7fee76f0c728 in
mir::compositor::DefaultDisplayBufferCompositor::composite(std::vector,
std::allocator > >&&)
(this=0x7fee5800c840, scene_elements=...)
at
/home/alan/display_server/mir/src/server/compositor/default_display_buffer_compositor.cpp:84
#11 0x7fee76f12781 in mir::compositor::CompositingFunctor::operator()()
(this=0x55e9f1b6a3a0)
at
/home/alan/display_server/mir/src/server/compositor/multi_threaded_compositor.cpp:141
#12 0x7fee76f18311 in std::__invoke_impl(std::__invoke_other,
mir::compositor::CompositingFunctor&) (__f=...) at
/usr/include/c++/7/bits/invoke.h:60
#13 0x7fee76f178b4 in
std::__invoke(mir::compositor::CompositingFunctor&)
(__fn=...)
at /usr/include/c++/7/bits/invoke.h:95
#14 0x7fee76f16ae0 in
std::reference_wrapper::operator()<>()
const (this=0x7fee68b10af0)
at /usr/include/c++/7/bits/refwrap.h:356
#15 0x7fee76f15aac in std::_Function_handler
>::_M_invoke(std::_Any_data const&) (__functor=...) at
/usr/include/c++/7/bits/std_function.h:316
#16 0x7fee76daedbc in std::function::operator()() const
(this=0x7fee68b10af0) at /usr/include/c++/7/bits/std_function.h:706
#17 0x7fee77108ed3 in (anonymous namespace)::Task::execute()
(this=0x7fee68b10af0)
at /home/alan/display_server/mir/src/server/thread/basic_thread_pool.cpp:40
#18 0x7fee7710922e in (anonymous namespace)::Worker::operator()()
(this=0x55e9f172f5d0)
at /home/alan/display_server/mir/src/server/thread/basic_thread_pool.cpp:91
#19 0x7fee7710bc51 in std::__invoke_impl(std::__invoke_other,
[Touch-packages] [Bug 1866066] [NEW] Sound defaults to DUMMY output on resume
Public bug reported: Sounds works perfectly. Suspend the laptop and then upon resume sound is switched to DUMMY OUTPUT requires restart. Just started happening. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 ProcVersionSignature: Ubuntu 5.3.0-7629.31~1581628854~18.04~2db8a7a~dev-generic 5.3.13 Uname: Linux 5.3.0-7629-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Mar 4 07:43:54 2020 InstallationDate: Installed on 2020-02-06 (26 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03-1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp3-c dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: galp3-c dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03-1:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.sku: Not Applicable dmi.product.version: galp3-c dmi.sys.vendor: System76 modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-03-04T07:42:51.788265 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- 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/1866066 Title: Sound defaults to DUMMY output on resume Status in pulseaudio package in Ubuntu: New Bug description: Sounds works perfectly. Suspend the laptop and then upon resume sound is switched to DUMMY OUTPUT requires restart. Just started happening. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 ProcVersionSignature: Ubuntu 5.3.0-7629.31~1581628854~18.04~2db8a7a~dev-generic 5.3.13 Uname: Linux 5.3.0-7629-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Mar 4 07:43:54 2020 InstallationDate: Installed on 2020-02-06 (26 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03-1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp3-c dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: galp3-c dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03-1:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.sku: Not Applicable dmi.product.version: galp3-c dmi.sys.vendor: System76 modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-03-04T07:42:51.788265 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866066/+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 1866062] [NEW] /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@429:parse_arguments:print_usage:_print_message
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu18, the problem page at https://errors.ubuntu.com/problem/4450779f25a7f4e3c3713198defeefd98859f1a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: eoan focal -- 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/1866062 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@429:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu18, the problem page at https://errors.ubuntu.com/problem/4450779f25a7f4e3c3713198defeefd98859f1a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866062/+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 1866049] Re: If you increase dpi would it help mouse acceleration algorithm to behave better?
** Package changed: wayland (Ubuntu) => null-and-void -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1866049 Title: If you increase dpi would it help mouse acceleration algorithm to behave better? Status in NULL Project: New Bug description: If you increased dpi would it help to impove mouse smoothing (including acceleration) algorithms? /just a thought :) To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1866049/+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 1866049] [NEW] If you increase dpi would it help mouse acceleration algorithm to behave better?
Public bug reported: If you increased dpi would it help to impove mouse smoothing (including acceleration) algorithms? /just a thought :) ** Affects: null-and-void Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1866049 Title: If you increase dpi would it help mouse acceleration algorithm to behave better? Status in NULL Project: New Bug description: If you increased dpi would it help to impove mouse smoothing (including acceleration) algorithms? /just a thought :) To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1866049/+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 1864253] Re: Pulseaudio sink/source selection, weird behaviour.
It looks like the solution is specific to your system, is that right? If not then is there anything that Ubuntu generally needs to fix? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1864253 Title: Pulseaudio sink/source selection, weird behaviour. Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a Laptop connected to an USB-C dock. By default the docks analog audio output is chosen as the default pulse audio sink. I want that the analog output of the Laptop is the default, hence I configured this in /etc/pulse/default.py This does not work and journalctl informs me that the device chosen by me (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached output from journalctl. I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp to prevent pulseaudio getting started in gdm to prevent device capture. This does not work, the device does still not exist. Restarting pulseaudio sometimes, but not always sets the configured default sink. Furthermore plugging in the headphones in the Laptops analog input switches audio to the dock. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: findus 3055 F pulseaudio /dev/snd/controlC1: findus 3055 F pulseaudio /dev/snd/controlC0: findus 3055 F pulseaudio /dev/snd/pcmC0D0p: findus 3055 F...m pulseaudio CurrentDesktop: i3 Date: Fri Feb 21 22:19:04 2020 InstallationDate: Installed on 2019-06-13 (253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET80W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S0UB00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S0UB00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439 mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938 mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1864253/+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 1864253] Re: Pulseaudio sink/source selection, weird behaviour.
The issue has been resolved. See the pulseaudio issue linked above. -- 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/1864253 Title: Pulseaudio sink/source selection, weird behaviour. Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: I have a Laptop connected to an USB-C dock. By default the docks analog audio output is chosen as the default pulse audio sink. I want that the analog output of the Laptop is the default, hence I configured this in /etc/pulse/default.py This does not work and journalctl informs me that the device chosen by me (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached output from journalctl. I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp to prevent pulseaudio getting started in gdm to prevent device capture. This does not work, the device does still not exist. Restarting pulseaudio sometimes, but not always sets the configured default sink. Furthermore plugging in the headphones in the Laptops analog input switches audio to the dock. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: findus 3055 F pulseaudio /dev/snd/controlC1: findus 3055 F pulseaudio /dev/snd/controlC0: findus 3055 F pulseaudio /dev/snd/pcmC0D0p: findus 3055 F...m pulseaudio CurrentDesktop: i3 Date: Fri Feb 21 22:19:04 2020 InstallationDate: Installed on 2019-06-13 (253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET80W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S0UB00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S0UB00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439 mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938 mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1864253/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
https://gitlab.freedesktop.org/drm/intel/issues/1377 This is the first time I open a report, so I don't know if I did it correctly PS: in the initial part I reported the problem as it was written by the user who opened the bug here, I hope it is not a problem ** Bug watch added: gitlab.freedesktop.org/drm/intel/issues #1377 https://gitlab.freedesktop.org/drm/intel/issues/1377 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+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 1866000] Re: incorrect default apps for calendar and photos
Thank you for your bug report, the calendar issue is known as bug #1828491 and due to the fact that gnome-calendar doesn't handle ics files so upstream refuses to declare it as a calendar handler. The image viewer is a bug due to the change or .desktop naming which is about to be fixed ** Package changed: gnome-control-center (Ubuntu) => ubuntu-settings (Ubuntu) ** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-settings (Ubuntu) Status: Confirmed => In Progress -- 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/1866000 Title: incorrect default apps for calendar and photos Status in ubuntu-settings package in Ubuntu: In Progress Bug description: Open settings > Default Applications and you'll see 'Text Editor' set for Calendar and 'Firefox' set for Photos, though Image Viewer and Shotwell are listed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CasperVersion: 1.441 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 08:20:54 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1866000/+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 1866000] [NEW] incorrect default apps for calendar and photos
You have been subscribed to a public bug: Open settings > Default Applications and you'll see 'Text Editor' set for Calendar and 'Firefox' set for Photos, though Image Viewer and Shotwell are listed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CasperVersion: 1.441 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 08:20:54 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-settings (Ubuntu) Importance: High Status: In Progress ** Tags: amd64 apport-bug focal -- incorrect default apps for calendar and photos https://bugs.launchpad.net/bugs/1866000 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864974] Re: apt clash with python
** Changed in: apport (Ubuntu) Status: New => Invalid -- 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/1864974 Title: apt clash with python Status in apport package in Ubuntu: Invalid Bug description: [code]Traceback (most recent call last): File "/usr/lib/cnf-update-db", line 8, in from CommandNotFound.db.creator import DbCreator File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 11, in import apt_pkg ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZTI9pkgDPkgPM, version APTPKG_6.0 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 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZTI9pkgDPkgPM, version APTPKG_6.0 Original exception was: Traceback (most recent call last): File "/usr/lib/cnf-update-db", line 8, in from CommandNotFound.db.creator import DbCreator File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 11, in import apt_pkg ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZTI9pkgDPkgPM, version APTPKG_6.0 ... E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then /usr/lib/cnf-update-db > /dev/null; fi' E: Sub-process returned an error code[/code][code]:~$ apt policy apt apt: Installed: 1.9.11 Candidate: 1.9.11 Version table: *** 1.9.11 500 500 http://us.archive.ubuntu.com/ubuntu devel-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.9.10+0~202002252104~ubuntu20.04.1 500 500 http://ppa.launchpad.net/deity/sid/ubuntu devel/main amd64 Packages 1.9.10 500 500 http://us.archive.ubuntu.com/ubuntu devel/main amd64 Packages[/code] [code]apt (1.9.11) experimental; urgency=medium [ Tomáš Janoušek ] * bash completion: Add autopurge command [ Tris Emmy Wilson ] * apt-mark: don't lie about successful marks [ Julian Andres Klode ] * apt(8): Wait for lock (Closes: #754103) * policy: Implement pinning by source package (Closes: #166032) * Initialize libgcrypt on first use (Closes: #949074) * Fix various compiler warnings * Bump ABI to 6.0; update symbols file; cleanup ABI: - Merge various function overloads together - Make stuff that should be virtual virtual - Default to hidden visibility * Code removals: - Use a 32-bit djb VersionHash instead of CRC-16 - Remove CRC-16 implementation * Hardening: - tagfile: Check if memchr() returned null before using - tagfile: Check out-of-bounds access to Tags vector * Cache improvements: - Type safe cache: Replace map_pointer_t with map_pointer - Extensibility: Add d-pointers to groups, packages, versions, and files - Prepare for package hashtable removal: Swap locations of hashtables [ Nis Martensen ] * apt-pkg/srcrecords.cc: 'source' means 'deb-src' in error message [ David Kalnischkies ] * Parse records including empty tag names correctly -- Julian Andres Klode Wed, 26 Feb 2020 21:29:48 +0100[/code] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1864974/+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 1863354] Re: exact scrolling
** Changed in: ubuntu Importance: Undecided => Wishlist ** Package changed: ubuntu => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1863354 Title: exact scrolling Status in gtk+3.0 package in Ubuntu: New Bug description: When you use the text editor, gedit, the web browser, firefox, the e-mail reader, thunderbird, the file manager, nautilus, the word processor, writer of LibreOffice, and more in general every window having a scroll bar, tipically on the right side, in all these Ubuntu applications there is a good problem as user experience. This because, in example, to choose the a new font in writer when you click with the mouse in the scroll bar on the right, the page jump to the page clicked without show the fonts page by page (that obviously is of the size of the list of the showed fonts). In example, this happen even during the installation of Ubuntu when it's necessary to choose the language. This happen even in the window of thunderbird where, clicking on the right scroll bar, the user wants to see the e-mails page by page thus a little at the time, otherwise is quite impossible to use the scrollbar and the user is forced to use the arrow on the keyboard scrolling the e-mails one at the time. More, the function should not be a horizontal line with a fixed speed but an incrased and decreased speed like a gaussian shape https://upload.wikimedia.org/wikipedia/it/b/b3/Gaussiana_chauvenet.jpeg or if you prefer another shape as speed profile but should be delicate, proportional, in\decremental and smooth. If you don't want to loose the capability to jump at the end of a window with the scrolling bar, jumping thousands of pages, you could put an option on the top of the scrolling bar to choose the kind of user experience "jump to this page" or "scroll page by page". In example, in nautilus, if you have thousands of pages you could highlight on the right scrollbar the letter (or number) where will start the page where you are going to jump. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1863354/+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 1863354] [NEW] exact scrolling
You have been subscribed to a public bug: When you use the text editor, gedit, the web browser, firefox, the e-mail reader, thunderbird, the file manager, nautilus, the word processor, writer of LibreOffice, and more in general every window having a scroll bar, tipically on the right side, in all these Ubuntu applications there is a good problem as user experience. This because, in example, to choose the a new font in writer when you click with the mouse in the scroll bar on the right, the page jump to the page clicked without show the fonts page by page (that obviously is of the size of the list of the showed fonts). In example, this happen even during the installation of Ubuntu when it's necessary to choose the language. This happen even in the window of thunderbird where, clicking on the right scroll bar, the user wants to see the e-mails page by page thus a little at the time, otherwise is quite impossible to use the scrollbar and the user is forced to use the arrow on the keyboard scrolling the e-mails one at the time. More, the function should not be a horizontal line with a fixed speed but an incrased and decreased speed like a gaussian shape https://upload.wikimedia.org/wikipedia/it/b/b3/Gaussiana_chauvenet.jpeg or if you prefer another shape as speed profile but should be delicate, proportional, in\decremental and smooth. If you don't want to loose the capability to jump at the end of a window with the scrolling bar, jumping thousands of pages, you could put an option on the top of the scrolling bar to choose the kind of user experience "jump to this page" or "scroll page by page". In example, in nautilus, if you have thousands of pages you could highlight on the right scrollbar the letter (or number) where will start the page where you are going to jump. ** Affects: gtk+3.0 (Ubuntu) Importance: Wishlist Status: Incomplete ** Tags: bionic bot-comment -- exact scrolling https://bugs.launchpad.net/bugs/1863354 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26
