[Touch-packages] [Bug 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink
Are you still able to reproduce it with the stock bionic kernel? If yes, it's still a bug ** Changed in: mesa (Ubuntu) Status: Invalid => Incomplete -- 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/1815523 Title: The last MESA updates (02/07/19) corrupted output to DisplayLink Status in mesa package in Ubuntu: Incomplete Bug description: Prior to Thursday's "update" from Bionic-Proposed, the MESA was working fine; afterwards, gameplay on STEAM has become choppy and staccato; secondary display via a USB-C through DisplayPort UD3900 (Pluggable) is completely corrupted. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Feb 11 16:50:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1323] InstallationDate: Installed on 2019-01-15 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display 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 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: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 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/mesa/+bug/1815523/+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 1777415] Re: Local authorization bypass by using suspend mode
Which files, when missing, cause this to happen? Can you provide strace output of the failing process? This seems unlikely to be due to PAM, which has fairly well exercised error handling and is designed to fail closed; but it's possible there is a bug in the configuration of PAM for one or more services. ** Changed in: pam (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1777415 Title: Local authorization bypass by using suspend mode Status in Unity: New Status in pam package in Ubuntu: Incomplete Status in unity package in Ubuntu: Confirmed Bug description: Version: Ubuntu 16.04.04 LTS Desktop, all packets are updated at 15.06.2018 Affects: access to latest user opened applications, that can contain sensitive information (documents, private information, passwords, etc.) How to reproduce: 1. open some applications (LibreOffice, browsers, editors, ...) 2. go to suspend mode 3. extract hard drive 4. wake up 5. after that can be several behaviors: * Ubuntu show lock screen. Enter ANY password -> access granted. * Ubuntu show lock screen. Enter ANY password, access denied. Fast press the hardware shutdown button -> access granted. * Ubuntu does not show lock screen, only black screen. We can repeat actions like in previous paragraphs To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1777415/+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 1666203] Re: pam_tty_audit failed in pam_open_session
This has been fixed for disco with the upload of pam 1.3.1-2ubuntu1. ** Changed in: pam (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Fix Released Status in pam package in Debian: New Bug description: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=failed' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_DISP msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' Thanks regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+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 1815670] Re: Ubuntu 19.04: Severe GObject/GType error and crash
This bug was fixed in the package gst-plugins-good1.0 - 1.15.1-1ubuntu2 --- gst-plugins-good1.0 (1.15.1-1ubuntu2) disco; urgency=medium * Cherry-pick Revert-pulsesrc-Move-to-extended-stream-API.patch: - Back out a feature that depends on an unreleased PulseAudio feature and broke audio recording (LP: #1815670) -- Jeremy Bicha Tue, 12 Feb 2019 23:15:55 -0500 ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1815670 Title: Ubuntu 19.04: Severe GObject/GType error and crash Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Bug description: Hello, I am trying to make Audio-recorder to compile and run under Ubuntu 19.04 (Ubuntu Disco Dingo - development branch). 1) A GStreamer bug. This crash occurs if I run a Gstreamer pipleline on the command line (in a terminal window). Like this. $ gst-launch-1.0 -e pulsesrc | fakesink (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: ../../../gobject/gtype.c:4265: type id '0' is invalid (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: can't peek value table for type '' which is not currently referenced Caught SIGSEGV Spinning. Please run 'gdb gst-launch-1.0 8410' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core. -- 2) Also, it seems that the same bug causes my audio-recorder program crash. It happens in all gtk_button_set_image(...) calls during runtime. gtk_button_set_image(GTK_BUTTON(g_win.recorder_button), GTK_WIDGET(image)); The error message is: (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: ../../../gobject/gtype.c:4265: type id '0' is invalid (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: can't peek value table for type '' which is not currently referenced Segmentation fault (core dumped) Please educate me if you want more debug info or stacktrace. My system is: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Disco Dingo (development branch) Release: 19.04 Codename: disco My system has very latest updates. Any comments? Kindly Osmo (moma) Antero --- EDIT: This bug report is similar https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/552 --- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-tools 1.15.1-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 21:31:51 2019 ExecutablePath: /usr/bin/gst-launch-1.0 InstallationDate: Installed on 2019-02-04 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1815670/+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 1815711] [NEW] [Dell G7 7588] *ERROR* Fault errors on pipe B: 0x00000080
Public bug reported: Hi, Recently, I installed Ubuntu 18.04 on my Dell G7 7588. From day one, the system has random freezes/crashes (usually a few a day) The way the crashes manifest is that 2 out of my 3 monitors go black and in some cases sound and inputs get stuck. In some rare cases, I can continue to operate on one of the screens. I checked syslog and dmesg, and usually I don't see any messages at the time of the crash, except this one time that input did not freeze and I could run a dmesg. In that case I got this message: Feb 13 15:34:51 morningstar kernel: [ 1593.615704] [drm:gen8_de_irq_handler [i915]] *ERROR* Fault errors on pipe B: 0x0080 Feb 13 15:34:51 morningstar kernel: [ 1593.615999] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun Additionally, this message appears on dmesg fairly often: ... Feb 13 15:21:17 morningstar kernel: [ 780.324457] CPU6: Package temperature above threshold, cpu clock throttled (total events = 109) Feb 13 15:21:17 morningstar kernel: [ 780.324457] CPU0: Package temperature above threshold, cpu clock throttled (total events = 109) ... I tried to solve this issue on my own for a while now, without success, here are some of the things I tried: - Updated BIOS to latest version - Installed nvidia 415 graphic drivers - Tested using xwayland - Tried 4.15.0-45-48, 4.19.16 and 4.19.20 kernels (this last one generates problems with the graphic drivers, and does not solve the problem either. - Tried modifying power management profile on the BIOS. - Added splash acpi_rev_override=1 to /etc/default/grub as found here: https://www.reddit.com/r/Dell/comments/63cavx/fixed_nvidia_1050_freezing_in_ubuntu_linux/ - Ran dell diagnostic tools (no errors there) So far none of this things solved the issue. These error messages are the only noticeable things I could find to debug... Can someone help me find a fix or workaround the issue? I've been spending multiple days trying to solve this and I am not making any real progress Please let me know if you need me to submit more information to find the cause of the issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.16-041916-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Feb 13 15:51:17 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 415.27, 4.15.0-45-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-44-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-45-generic, x86_64: installed virtualbox, 5.2.18, 4.19.16-041916-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0825] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP106M [GeForce GTX 1060 Mobile] [1028:0825] InstallationDate: Installed on 2018-11-30 (75 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G7 7588 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.16-041916-generic root=UUID=ed06b2b0-7398-48df-9971-9f5f225c0152 ro quiet splash acpi_rev_override=1 vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0FDMYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd12/21/2018:svnDellInc.:pnG77588:pvr:rvnDellInc.:rn0FDMYT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G7 7588 dmi.product.sku: 0825 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-inpu
[Touch-packages] [Bug 1814562] Re: Update to new upstream 1.0.2
I am unsubscribing ubuntu-sponsors. Please feel free to resubscribe when you have something ready for sponsoring. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1814562 Title: Update to new upstream 1.0.2 Status in zeitgeist package in Ubuntu: New Bug description: There is a new upstream release which fixes issues with valac 0.43/44 https://launchpad.net/zeitgeist/+milestone/1.0.2 2018-01-31: Zeitgeist 1.0.2 "Phoenix" --- Overall: - Fix compile errors and warnings with new vala - fts: Correctly implement the org.gnome.zeitgeist.Index DBus interface - test-log: Use correct free function for ZeitgeistResultSet - Do not require rapper as it is not used anymore - Make ontology2code work with python3 - Properly fallback with the Zeitgeist version - rdflib directly to parse the trig files - Update Ontology2code to ba able to specify the output path Libzeitgeist: - Asynchronous out-parameters are only allowed at the end of argument lists *** THIS IS AN UNAVOIDABLE VALA API BREAK *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1814562/+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 1797282] Re: fsck not running at all on reboot
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1797282 Title: fsck not running at all on reboot Status in systemd package in Ubuntu: Expired Bug description: After upgrading some servers from 16.04 to 18.04 I'm met with a MOTD that says: *** /dev/xvda1 should be checked for errors *** I added "fsck.mode=force" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub before running 'sudo update-grub'. I also verified that fsck was present in /boot/grub/grub.cfg afterwards, before rebooting the server. Surprisingly I was met with the same error message in MOTD when logging in. I then ran tune2fs to see when the last check was performed and this is the output: $ sudo tune2fs -l /dev/xvda1 | grep checked Last checked: Wed Sep 12 16:17:00 2018 I then tried to change mount count to 1 with tune2fs -c 1 /dev/xvda1, but after another reboot I was still met with the same error message and the timestamp for last checked was unchanged. I have the same problem on all the servers that was upgraded from 16.04 to 18.04, but also on a new server installed directly with 18.04. In should be mentioned that the servers are AWS EC2 instances, so I have no way of trying to run fsck from a liveusb. Another user has reported the same issue here: https://ubuntuforums.org/showthread.php?t=2403368 I'm not quite sure what information is needed, but attached are some basic information about the system. Please let me know if you need any any other outputs or logs. Edit1: I tested fsck.mode=force on my laptop running Ubuntu 18.04.1 LTS (Xubuntu) and it works fine. Seems to be related to the server edition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797282/+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 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
*** This bug is a duplicate of bug 1688018 *** https://bugs.launchpad.net/bugs/1688018 This is the *nastiest* bug I've ever encountered in the wild on my own in Linux (that has no good solution after this long). Package 1.2.2-0ubuntu0.16.04.4 has disappeared from the mirrors for Xenial (not that anyone should expect a normal user to go through the deep dive that is this subject, once one realizes what is happening). The cipher in use by AWS for Client VPN isn't available in OpenSSL within Trusty Tahr, so running an old Ubuntu distro is also not a viable solution for me. This is about as serious of a bug as I could think of, and we're almost two years in without it being addressed. Hate to be tin-foil-hatty, but this seems like the kind of thing that gets put into software as a result of government-agency interests. How many people around the world expecting their VPN to protect them while viewing content from outside of their nation state are DNS-leaking all over the place to their local ISP? How many companies are leaking private zone DNS names (which often reflect what's running on the target boxes, and would then include information that could be used as part of an attack vector) to their ISP? I understand how open source works, but most people (including me) don't have the ability to work effectively on this nuanced bug. What's the plan? Sorry to sound disgruntled, but I spent about a week on this (coming to terms with understanding the issue, and then trying a number of workarounds). Initially I accused our CTO of running a broken VPN server (heh), because I could simply not believe that things didn't "just work" in Linux for this extremely common use case. So we don't support pushing "dhcp-option" for DNS in Linux. This works in Mac and in Windows. We need a working/easy way to update our DNS addresses upon connecting to/disconnected from a VPN that users can trust. This bug is so obscene, bwahah, I felt like Linus Torvalds dealing with Nvidia... :-P -- 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/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
This is the *nastiest* bug I've ever encountered in the wild on my own in Linux (that has no good solution after this long). Package 1.2.2-0ubuntu0.16.04.4 has disappeared from the mirrors for Xenial (not that anyone should expect a normal user to go through the deep dive that is this subject, once one realizes what is happening). The cipher in use by AWS for Client VPN isn't available in OpenSSL within Trusty Tahr, so running an old Ubuntu distro is also not a viable solution for me. This is about as serious of a bug as I could think of, and we're almost two years in without it being addressed. Hate to be tin-foil-hatty, but this seems like the kind of thing that gets put into software as a result of government-agency interests. How many people around the world expecting their VPN to protect them while viewing content from outside of their nation state are DNS-leaking all over the place to their local ISP? How many companies are leaking private zone DNS names (which often reflect what's running on the target boxes, and would then include information that could be used as part of an attack vector) to their ISP? I understand how open source works, but most people (including me) don't have the ability to work effectively on this nuanced bug. What's the plan? Sorry to sound disgruntled, but I spent about a week on this (coming to terms with understanding the issue, and then trying a number of workarounds). Initially, I accused our CTO of running a broken VPN server (heh), because I could simply not believe that things didn't "just work" in Linux for this extremely common use case. So we don't support pushing "dhcp-option" for DNS in Linux. This works in Mac and in Windows. We need a working/easy way to update our DNS addresses upon connecting to/disconnected from a VPN that users can trust. This bug is so obscene, bwahah, I felt like Linus Torvalds dealing with Nvidia... :-P -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? ->
[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
This bug was fixed in the package qtbase-opensource-src - 5.11.3+dfsg- 5ubuntu1 --- qtbase-opensource-src (5.11.3+dfsg-5ubuntu1) disco; urgency=medium * Sync with experimental branch of Debian packaging Git. -- Dmitry Shachnev Mon, 11 Feb 2019 13:43:15 +0300 ** Changed in: qtbase-opensource-src (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink
Not sure what happened, but I tried installing the HWE kernel, even those it's not entirely ready, but it did install the new video drivers and that solved it. ** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- 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/1815523 Title: The last MESA updates (02/07/19) corrupted output to DisplayLink Status in mesa package in Ubuntu: Invalid Bug description: Prior to Thursday's "update" from Bionic-Proposed, the MESA was working fine; afterwards, gameplay on STEAM has become choppy and staccato; secondary display via a USB-C through DisplayPort UD3900 (Pluggable) is completely corrupted. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Feb 11 16:50:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1323] InstallationDate: Installed on 2019-01-15 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display 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 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: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 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/mesa/+bug/1815523/+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 1815693] [NEW] Kubuntu 18.10 Xorg severe memory leak
Public bug reported: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR; I have today logged the memory consumption while I was handling some bills and linked is a log of constantly increasing Xorg memory usage. So it goes until it chokes the machine and only a hard reboot is possible. My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see how the Xorg usage creeps up. https://www.dropbox.com/s/nf1ev2dxdl..._leak.log?dl=0 Please advise what additional information I should post to have this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Feb 13 01:00:13 2019 DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2015-10-22 (1209 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu ** Attachment added: "Memory usage increase log over a few hours" https://bugs.launchpad.net/bugs/1815693/+attachment/5238125/+files/xorg_leak.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815693 Title: Kubuntu 18.10 Xorg severe memory leak Status in xorg package in Ubuntu: New Bug description: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR;
[Touch-packages] [Bug 1815415] Re: please update libseccomp for newer kernel syscalls
Thanks Christian, very thorough. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1815415 Title: please update libseccomp for newer kernel syscalls Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Bionic: In Progress Status in libseccomp source package in Cosmic: Fix Released Bug description: [Impact] * The libseccomp library provides an easy to use, platform independent, interface to the Linux Kernel's syscall filtering mechanism. But it can only "control" those syscalls it knows about. Therefore staying up to date with newer kernels is a requirement to be fully funcitonal. * At the time 18.04 was released with the 4.15 kernel the new definitions were not yet released for libseccomp - lets fix this mismatch by backporting the new syscall definitions [2][3][4]. [Test Case] * Note: a lot of this is kernel dependent it should work with the intended SRU target of Bionic with kernel 4.15 or 4.18, but be careful to run it there (e.g. not a LXD container on Xenials 4.4 kernel) * we modify the already existing autopkgtest for this SRU verification # Prep $ apt install ubuntu-dev-tools build-essential linux-libc-dev libseccomp-dev libseccomp2 seccomp $ pull-lp-source libseccomp bionic $ cd libseccomp-2.3.1 $ export ADTTMP=$(mktemp -d); echo $ADTTMP # run original tests as-is (should pass/fail as expected) $ ./debian/tests/test-filter # add new syscalls of this SRU $ cp debian/tests/data/safe.filter debian/tests/data/newcodes.filter $ printf "preadv2\npwritev2\npkey_mprotect\npkey_alloc\npkey_free\nget_tls\ns390_guarded_storage\ns390_sthyi\n" >> debian/tests/data/newcodes.filter # remove unknown calls (x86 4.18 kernel) sed -i -e '/^_exit$/d' -e '/^fstatvfs$/d' -e '/^llseek$/d' -e '/^pread$/d' -e '/^pselect$/d' -e '/^pwrite$/d' -e '/^sigtimedwait$/d' -e '/^sigwaitinfo$/d' -e '/^statvfs$/d' debian/tests/data/newcodes.filter # make unknown call a fail $ sed -i -e '111s/continue;/{fprintf(stderr, "failed to find %s\\n",buf);rc = -1;goto out;}/' debian/tests/src/test-seccomp.c # run this special test and check return value ${ADTTMP}/exe ./debian/tests/data/newcodes.filter /bin/date; echo $? Without the fix it will fail like: DEBUG: seccomp_load_filters ./debian/tests/data/newcodes.filter failed to find preadv2 seccomp_load_filters failed with -1 1 But with the fix applied those new calls will work: DEBUG: seccomp_load_filters ./debian/tests/data/newcodes.filter Tue Feb 12 07:41:05 UTC 2019 0 [Regression Potential] * This isn't adding new active code like functions, but only extending the definitions of per-arch syscall numbers to be aware of the newer syscalls that were added in the kernel. Therefore no old use-cases should regress (they are not touched). The only change in behavior for an SRU POV would be that things that got denied so far (e.g. if you tried to set such a new syscall through libseccomp) was denied before and would now work. I think that is exactly the intention of the SRU and not a regression. [Other Info] * Requested while security reviewing an libseccomp SRU to have one update for both [1]. * we also missed the former update for kernel 4.9 [3] AND 4.10 [4] as the official releases of the lib are rather seldom. * In general there already are build time tests and autopkgtests in the package already. So coverage of "old calls" for regressions is already good. --- This came up while working on bug 1755250 which asked for statx. But on the review of that it was pointed out [1] that it would be great to support further new kernel syscall defines - this isn't even looking at HWE kernels for Bionic, but "just" adding those which are there for the 4.15 kernel Bionic was released with. With the HWE kernels in mind there would be even more one might want to add, but there is no newer such update in the upstream repo yet. [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/libseccomp/+git/libseccomp/+merge/362906/comments/944418 [2]: https://github.com/seccomp/libseccomp/commit/c842c2f6c203ad9da37ca60219172aa0be68d26a [3]: https://github.com/seccomp/libseccomp/commit/d9102f12fd39bd77151a1f630fcfc8c80f86c55c [4]: https://github.com/seccomp/libseccomp/commit/116b3c1a2e1db53cc35b74f30c080f5265faa674 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1815415/+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: ubuntu-bug never (any longer) opens browser window
** Changed in: apport (Ubuntu) Status: Incomplete => New -- 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: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: New Bug 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 1413283] Re: "Set as default" is absent from "Open with.." context menu
The right place to report requests like that is also upstream where the code is written, https://gitlab.gnome.org/GNOME/gtk/issues -- 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/1413283 Title: "Set as default" is absent from "Open with.." context menu Status in One Hundred Papercuts: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Question http://askubuntu.com/questions/90214/how-to-set-default- program gets 35k+ views. I suspect much of it is because there is no intuitive way to set a file association. See the comment under accepted answer: Right-click -> open with -> other application DOES NOT show "Set as default"... Right-click -> Properties -> Open With DOES show "Set as default" I was looking for "Set as default" in "Open with.." menu myself . To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1413283/+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 1813432] Re: Specific PDF file fails to print to HP m551dn printer
** Changed in: cups (Ubuntu) Status: Incomplete => New -- 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/1813432 Title: Specific PDF file fails to print to HP m551dn printer Status in cups package in Ubuntu: New Bug description: One particular PDF file is failing to print. I have no idea why. When I say failing to print I mean that my computer thinks the file printed but the printer shows no sign of ever having received it. The display of the printer never changes to show that it is receiving or printing a file, and the job log of the printer doesn't show that it was received either. I also checked the printer event log and it doesn't show any events at the time I attempted to print the file. Unfortunately I can't attach the PDF file itself because it contains private information, and I can't find another PDF that exhibits this problem. I even tried generating a new PDF exactly the same way the old one was generated -- with the scan to email PDF function on my scanner -- and the new PDF prints just fine. I tried uploading the PDF directly to the printer with FTP and it prints just fine that way. I enabled CUPS debug mode before attempting to print the file. Attached is the resulting contents of /var/log/cups/error_log. I wish I knew what was going on here but honestly I have no idea. Perhaps you can learn something from the error_log. I hope so. Other files, including other PDFs, do print. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-3 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 17:47:49 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for HP_LaserJet_500_color_M551_1637DA_: ipps://m551dn.local:443/ipp/print device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd', '/etc/cups/ppd/duplex.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1813432/+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 1815323] Re: After Cheese update does not work
** Package changed: tracker (Ubuntu) => cheese (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1815323 Title: After Cheese update does not work Status in cheese package in Ubuntu: New Bug description: Hello guys After updating the version of Cheese 3.31.90-1 on Ubuntu Disk 19.04 this week it stopped working and the following error message appears as attached image. obs: The guvcview works normally and opens the webcam, since the cheese has failed. Here's the error message when opening the cheese from the terminal: edson@edson-p6540br:~$ cheese (cheese:13425): Clutter-WARNING **: 01:33:18.872: Whoever translated default:LTR did so wrongly. (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_object_unref: assertion 'object != NULL' failed (cheese:13425): cheese-CRITICAL **: 01:33:19.206: cheese_camera_set_error_element_not_found: assertion 'error == NULL || *error == NULL' failed ** Message: 01:33:19.206: cheese-application.vala:211: Error during camera setup: Um ou mais elementos necessários do GStreamer estão faltando: Um ou mais elementos necessários do GStreamer estão faltando: effects_valve. (cheese:13425): GStreamer-CRITICAL **: 01:33:19.229: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.229: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_object_unref: assertion 'object != NULL' failed *** Olá Pessoal Após atualização da versão do Cheese 3.31.90-1 no Ubuntu Disco 19.04 esta semana o mesmo deixou de funcionar e aparece a seguinte mensagem de erro conforme imagem em anexo. obs: O guvcview funciona normalmente e abre a webcam, já o cheese falhou. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1815323/+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 1814481] Re: bluetooth keyboard not working
** Package changed: xorg (Ubuntu) => bluez (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: bluetooth keyboard not working Status in bluez package in Ubuntu: Confirmed Bug description: I recently got a nice mechanical bluetooth keyboard to use on my thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04 live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it only works after calling `sudo evtest /dev/input/eventN`. Xorg.0.log shows it is detected fine, and I can't see anything there after temporarily getting it to work using the evtest trick. 18.515] (II) config/udev: Adding input device Keychron K1 (/dev/input/event23) [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.515] (II) Using input driver 'libinput' for 'Keychron K1' [18.515] (**) Keychron K1: always reports core events [18.515] (**) Option "Device" "/dev/input/event23" [18.515] (**) Option "_source" "server/udev" [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.516] (II) event23 - Keychron K1: device is a keyboard [18.516] (II) event23 - Keychron K1: device removed [18.524] (II) libinput: Keychron K1: needs a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: MOUSE, id 20) [18.524] (**) Option "AccelerationScheme" "none" [18.524] (**) Keychron K1: (accel) selected scheme none/0 [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000 [18.524] (**) Keychron K1: (accel) acceleration threshold: 4 [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.524] (II) event23 - Keychron K1: device is a keyboard [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.524] (II) Using input driver 'libinput' for 'Keychron K1' [18.524] (**) Keychron K1: always reports core events [18.524] (**) Option "Device" "/dev/input/event23" [18.524] (**) Option "_source" "_driver/libinput" [18.524] (II) libinput: Keychron K1: is a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: KEYBOARD, id 21) [18.524] (**) Option "xkb_model" "pc105" [18.524] (**) Option "xkb_layout" "us" [18.524] (**) Option "xkb_variant" "altgr-intl" [18.524] (WW) Option "xkb_options" requires a string value I've also tried using the latest 4.20.6 from mainline-ppa and the latest bluetooth/bluz ppa without success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18 Uname: Linux 4.15.0-45-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Feb 3 23:51:29 2019 DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2017-07-24 (559 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago) dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-d
[Touch-packages] [Bug 1815354] Re: BCM 43142 driver not installed - no WiFi
That's not really n-m's fault if the driver is missing... ** Package changed: network-manager (Ubuntu) => ubuntu-drivers-common (Ubuntu) -- 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/1815354 Title: BCM 43142 driver not installed - no WiFi Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Disco daily Lubuntu 09.02.2019 and Disco daily Kubuntu 10.02.2019 BCM 43142 drivers not installed resulting in no WiFi during and after installation. I was able to attach ethernet cable and use the command line "ubuntu- drivers" command to install the drivers and all worked well after that. Of course if running a machine with no ethernet then this is a huge problem for the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1815354/+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 1643959] Re: Unused parameter 'deterministic'
The issue is fixed now with https://launchpad.net/ubuntu/+source/protobuf/3.6.1.3-1 ** Changed in: protobuf (Ubuntu) Importance: Undecided => Low ** Changed in: protobuf (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1643959 Title: Unused parameter 'deterministic' Status in protobuf package in Ubuntu: Fix Released Bug description: The current version of protbuf in the Ubuntu 16.10 Repository (3.0.0-7ubuntu3) includes this bug: https://github.com/google/protobuf/issues/2032 "Every message generates an unused parameter warning for bool deterministic in ::google::protobuf::uint8* ::InternalSerializeWithCachedSizesToArray( bool deterministic, ::google::protobuf::uint8* target) const. " My project uses -Werror, and thus does not compile in current Ubuntu because of messages like this: NSMessage.pb.cc: In member function ‘virtual google::protobuf::uint8* NS_Message::InternalSerializeWithCachedSizesToArray(bool, google::protobuf::uint8*) const’: wifi/NSMessage.pb.cc:338:10: error: unused parameter ‘deterministic’ [-Werror=unused-parameter] bool deterministic, ::google::protobuf::uint8* target) const { ^ cc1plus: all warnings being treated as errors I would expect code being created by protobuf does not cause any warnings or errors. This issue is fixed in protobuf's git repository with the following commit: https://github.com/google/protobuf/commit/08b1c718e437041bfe0e6a28611621896e4fe904 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1643959/+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 1607696] Re: Version string missing in libjpeg.pc
Confirmed, the problem is with the sed added in http://launchpadlibrarian.net/241403193/libjpeg- turbo_1.4.2-0ubuntu2_1.4.2-0ubuntu3.diff.gz sed -e "s/@VERSION@/$(VERSION)/ But ${VERSION} is not defined ** Changed in: libjpeg-turbo (Ubuntu) Importance: Undecided => Low ** Changed in: libjpeg-turbo (Ubuntu) Assignee: (unassigned) => Matthias Klose (doko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1607696 Title: Version string missing in libjpeg.pc Status in libjpeg-turbo package in Ubuntu: Confirmed Bug description: Proper pkg-config files are installed if I build libjpeg-turbo myself. The description in the pkg-config file shipped by Ubuntu is also different from what is in upstream so I assume this is caused by Ubuntu (/Debian?) patching in a custom pkg-config file before they were included upstream in https://github.com/libjpeg-turbo/libjpeg- turbo/pull/53 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1607696/+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 1815649] Re: Vim on Ubuntu Disc 19.04 does not work
Hi, Sebastien Bache It should work, but it does not work. At the moment the Ubuntu Software screen is locked and I can not show it installed in the application central. But to see through synaptcis by the attachment below It also follows image of Ubuntu software caught. ** Attachment added: "Vim synaptcis by" https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+attachment/5238094/+files/Captura%20de%20tela%20de%202019-02-12%2020-57-13.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1815649 Title: Vim on Ubuntu Disc 19.04 does not work Status in vim package in Ubuntu: Incomplete Bug description: Hi guys The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not work. It is stated that it is installed by the Ubuntu software, but by the terminal says it is not installed as can be seen in the attached image. Command 'vim' not found, but can be installed with: Awaiting arrangements and correction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+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 1815649] Re: Vim on Ubuntu Disc 19.04 does not work
** Attachment added: "Ubuntu Software caught" https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+attachment/5238095/+files/Captura%20de%20tela%20de%202019-02-12%2020-57-32.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1815649 Title: Vim on Ubuntu Disc 19.04 does not work Status in vim package in Ubuntu: Incomplete Bug description: Hi guys The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not work. It is stated that it is installed by the Ubuntu software, but by the terminal says it is not installed as can be seen in the attached image. Command 'vim' not found, but can be installed with: Awaiting arrangements and correction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+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 1815649] Re: Vim on Ubuntu Disc 19.04 does not work
the log shows that only 'vim-tiny' is installed (and that's what Ubuntu installs by default), the 'vim.tiny' command should work? It's a bit misleading that gnome-software shows 'vim' as installed though -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1815649 Title: Vim on Ubuntu Disc 19.04 does not work Status in vim package in Ubuntu: Incomplete Bug description: Hi guys The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not work. It is stated that it is installed by the Ubuntu software, but by the terminal says it is not installed as can be seen in the attached image. Command 'vim' not found, but can be installed with: Awaiting arrangements and correction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+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 1815670] Re: Ubuntu 19.04: Severe GObject/GType error and crash
Thanks, that looks like a bug in the current 1.15 tarball which is fixed in git and is going to be fixed with the next update https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/commit/4e9a8e58 ** Package changed: gstreamer1.0 (Ubuntu) => gst-plugins-good1.0 (Ubuntu) ** Changed in: gst-plugins-good1.0 (Ubuntu) Importance: Undecided => High ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1815670 Title: Ubuntu 19.04: Severe GObject/GType error and crash Status in gst-plugins-good1.0 package in Ubuntu: Fix Committed Bug description: Hello, I am trying to make Audio-recorder to compile and run under Ubuntu 19.04 (Ubuntu Disco Dingo - development branch). 1) A GStreamer bug. This crash occurs if I run a Gstreamer pipleline on the command line (in a terminal window). Like this. $ gst-launch-1.0 -e pulsesrc | fakesink (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: ../../../gobject/gtype.c:4265: type id '0' is invalid (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: can't peek value table for type '' which is not currently referenced Caught SIGSEGV Spinning. Please run 'gdb gst-launch-1.0 8410' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core. -- 2) Also, it seems that the same bug causes my audio-recorder program crash. It happens in all gtk_button_set_image(...) calls during runtime. gtk_button_set_image(GTK_BUTTON(g_win.recorder_button), GTK_WIDGET(image)); The error message is: (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: ../../../gobject/gtype.c:4265: type id '0' is invalid (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: can't peek value table for type '' which is not currently referenced Segmentation fault (core dumped) Please educate me if you want more debug info or stacktrace. My system is: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Disco Dingo (development branch) Release: 19.04 Codename: disco My system has very latest updates. Any comments? Kindly Osmo (moma) Antero --- EDIT: This bug report is similar https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/552 --- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-tools 1.15.1-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 21:31:51 2019 ExecutablePath: /usr/bin/gst-launch-1.0 InstallationDate: Installed on 2019-02-04 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1815670/+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 1815649] Re: Vim on Ubuntu Disc 19.04 does not work
Follow the Requested: edson@edson-p6540br:~$ dpkg -l | grep vim ii vim-common2:8.1.0320-1ubuntu3 all Vi IMproved - Common files ii vim-tiny 2:8.1.0320-1ubuntu3 amd64Vi IMproved - enhanced vi editor - compact version edson@edson-p6540br:~$ sudo dpkg -l | grep vim ii vim-common2:8.1.0320-1ubuntu3 all Vi IMproved - Common files ii vim-tiny 2:8.1.0320-1ubuntu3 amd64Vi IMproved - enhanced vi editor - compact version edson@edson-p6540br:~ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1815649 Title: Vim on Ubuntu Disc 19.04 does not work Status in vim package in Ubuntu: Incomplete Bug description: Hi guys The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not work. It is stated that it is installed by the Ubuntu software, but by the terminal says it is not installed as can be seen in the attached image. Command 'vim' not found, but can be installed with: Awaiting arrangements and correction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+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 1815670] [NEW] Ubuntu 19.04: Severe GObject/GType error and crash
Public bug reported: Hello, I am trying to make Audio-recorder to compile and run under Ubuntu 19.04 (Ubuntu Disco Dingo - development branch). 1) A GStreamer bug. This crash occurs if I run a Gstreamer pipleline on the command line (in a terminal window). Like this. $ gst-launch-1.0 -e pulsesrc | fakesink (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: ../../../gobject/gtype.c:4265: type id '0' is invalid (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: can't peek value table for type '' which is not currently referenced Caught SIGSEGV Spinning. Please run 'gdb gst-launch-1.0 8410' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core. -- 2) Also, it seems that the same bug causes my audio-recorder program crash. It happens in all gtk_button_set_image(...) calls during runtime. gtk_button_set_image(GTK_BUTTON(g_win.recorder_button), GTK_WIDGET(image)); The error message is: (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: ../../../gobject/gtype.c:4265: type id '0' is invalid (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: can't peek value table for type '' which is not currently referenced Segmentation fault (core dumped) Please educate me if you want more debug info or stacktrace. My system is: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Disco Dingo (development branch) Release:19.04 Codename: disco My system has very latest updates. Any comments? Kindly Osmo (moma) Antero --- EDIT: This bug report is similar https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/552 --- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-tools 1.15.1-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 21:31:51 2019 ExecutablePath: /usr/bin/gst-launch-1.0 InstallationDate: Installed on 2019-02-04 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Description changed: Hello, I am trying to make Audio-recorder to compile and run under Ubuntu 19.04 (Ubuntu Disco Dingo - development branch). 1) A GStreamer bug. This crash occurs if I run a Gstreamer pipleline on the command line (in a terminal window). Like this. $ gst-launch-1.0 -e pulsesrc | fakesink (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: ../../../gobject/gtype.c:4265: type id '0' is invalid (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: can't peek value table for type '' which is not currently referenced Caught SIGSEGV Spinning. Please run 'gdb gst-launch-1.0 8410' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core. -- + 2) Also, it seems that the same bug causes my audio-recorder program crash. + It happens in all gtk_button_set_image(...) calls during runtime. - 2) Also, it seems that the same bug causes my audio-recorder program crash. - It happens in all gtk_button_set_image(...) calls during runtime. - - gtk_button_set_image(GTK_BUTTON(g_win.recorder_but ton), + gtk_button_set_image(GTK_BUTTON(g_win.recorder_button), GTK_WIDGET(image)); The error message is: (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: ../../../gobject/gtype.c:4265: type id '0' is invalid (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: can't peek value table for type '' which is not currently referenced Segmentation fault (core dumped) Please educate me if you want more debug info or stacktrace. My system is: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Disco Dingo (development branch) Release: 19.04 Codename: disco My system has very latest updates. Any comments? Kindly Osmo (moma) Antero --- EDIT: This bug report is similar - https://gitlab.freedesktop.org/gstre...ood/issues/552 + https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/552 + --- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-tools 1.15.1-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 21:31:51 2019 ExecutablePath: /usr/bin/gst-launch-1.0 InstallationDate: Installed on 2019-02-04 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gstreamer1.0 Upgrad
[Touch-packages] [Bug 1810840] Re: whoopsie can't remember "always report" setting
whoopsie-preferences is installed by default in Ubuntu, it should probalby be a recommends from apport though -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie-preferences in Ubuntu. https://bugs.launchpad.net/bugs/1810840 Title: whoopsie can't remember "always report" setting Status in whoopsie-preferences package in Ubuntu: Confirmed Bug description: After ticking the checkbox for whoopsie to automatically always send crash reports, I get the following error dialog (screenshot attached): *Can't remember send report status settings* Saving crash report state failed. Can't set auto or never reporting mode. Command '['/usr/bin/gdbus', 'call', '-y', '-d', 'com.ubuntu.WhoopsiePreferences', '-o', '/com/ubuntu/WhoopsiePreferences', '-m', 'com.ubuntu.WhoopsiePreferences.SetReportCrashes', 'true']' returned non-zero exit status 1. I'm pretty sure this error happens because whoopsie-preferences was not installed; afterwards I installed whoopsie-preferences and manually ran in a terminal: $ /usr/bin/gdbus call -y -d com.ubuntu.WhoopsiePreferences -o /com/ubuntu/WhoopsiePreferences -m com.ubuntu.WhoopsiePreferences.SetReportCrashes true and got a return value of () but no errors or warnings. This computer was freshly-installed with Xubuntu 18.04 less than 2 weeks ago... I've kept a record of everything I changed since then, and I've only removed five packages (sgt-puzzles, gnome-sudoku, gnome- mines, pidgin, mousepad). If whoopsie-preferences is not included in a fresh install of (X)ubuntu, then perhaps it should be; in any case, if it isn't installed then the checkbox for making crash reporting automatic should not be visible. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy whoopsie whoopsie: Installed: 0.2.62 Candidate: 0.2.62 Version table: *** 0.2.62 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy whoopsie-preferences whoopsie-preferences: Installed: (none) Candidate: 0.19 Version table: 0.19 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/1810840/+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 1815649] Re: Vim on Ubuntu Disc 19.04 does not work
What's the output of that command? - dpkg -l | grep vim ** Changed in: vim (Ubuntu) Importance: Undecided => High ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1815649 Title: Vim on Ubuntu Disc 19.04 does not work Status in vim package in Ubuntu: Incomplete Bug description: Hi guys The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not work. It is stated that it is installed by the Ubuntu software, but by the terminal says it is not installed as can be seen in the attached image. Command 'vim' not found, but can be installed with: Awaiting arrangements and correction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+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 1815649] [NEW] Vim on Ubuntu Disc 19.04 does not work
Public bug reported: Hi guys The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not work. It is stated that it is installed by the Ubuntu software, but by the terminal says it is not installed as can be seen in the attached image. Command 'vim' not found, but can be installed with: Awaiting arrangements and correction ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Vim on Ubuntu Disc 19.04 does not work" https://bugs.launchpad.net/bugs/1815649/+attachment/5238025/+files/Captura%20de%20tela%20de%202019-02-12%2016-16-03.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1815649 Title: Vim on Ubuntu Disc 19.04 does not work Status in vim package in Ubuntu: New Bug description: Hi guys The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not work. It is stated that it is installed by the Ubuntu software, but by the terminal says it is not installed as can be seen in the attached image. Command 'vim' not found, but can be installed with: Awaiting arrangements and correction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+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 1814261] Re: gpm prevents loging to the console: spurious “Enter” events seems inserted
Seen on linux-image-4.15.0-44-generic and linux-image-4.15.0-45-generic. When /bin/login is exec'd by agetty it tries to read stdin and gets EAGAIN: 5640 write(2, "Password: ", 10)= 10 5640 read(0, 0x7ffcca86a7f0, 511) = -1 EAGAIN (Resource temporarily unavailable) ... 55640 write(2, "\n", 1) = 1 taking that as a failed login attempt it tries again: 55640 write(2, "hilbert login: ", 15) = 15 55640 read(0, 0x7ffcca86a160, 511) = -1 EAGAIN (Resource temporarily unavailable) eventually logging a failed login attempt reverting to linux-image-4.15.0-43-generic also fixes the problem -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1814261 Title: gpm prevents loging to the console: spurious “Enter” events seems inserted Status in gpm package in Ubuntu: Confirmed Bug description: Hello, When our servers boot, We can't login because of spurious “enter”. We have this problem on virtual and physical machines since: * kernel linux-image-4.15.0-44-generic on bionic * kernel linux-image-4.4.0-142-generic on xenial To reproduce: 1. start an ubuntu server with the specific kernel 2. install GPM 3. on a console 1. type the user name “root” 2. hit “enter” 3. wait few seconds => spurious “Enter” are send to the console 4. Stop gpm.service 5. retry to login on a console => no problem lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1814261/+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 1815318] Re: mate 18.04.1 xserver won't open caja on local machine
I believe this is just a different behavior in caja itself. You see, in both cases there is already a caja process running. In bionic's version, if you run caja again, it doesn't bring up a new copy, but instead uses the existing one to spawn the new windows: ubuntu@bionic-mate:~$ ps fxaw|grep caja|grep -v grep 10308 ?Sl 0:01 \_ caja ubuntu@bionic-mate:~$ caja ubuntu@bionic-mate:~$ ps fxaw|grep caja|grep -v grep 10308 ?Sl 0:01 \_ caja ubuntu@bionic-mate:~$ caja ubuntu@bionic-mate:~$ ps fxaw|grep caja|grep -v grep 10308 ?Sl 0:01 \_ caja ubuntu@bionic-mate:~$ But I have many new windows opened already. In xenial, I do get new processes: ubuntu@xenial-mate:~$ caja & [1] 2764 ubuntu@xenial-mate:~$ Initializing caja-open-terminal extension /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py:50: RuntimeWarning: You have imported the Gtk 2.0 module. Because Gtk 2.0 was not designed for use with introspection some of the interfaces and API will fail. As such this is not supported by the pygobject development team and we encourage you to port your app to Gtk 3 or greater. PyGTK is the recomended python module to use with Gtk 2.0 warnings.warn(warn_msg, RuntimeWarning) sys:1: PyGIWarning: Caja was imported without specifying a version first. Use gi.require_version('Caja', '2.0') before import to ensure that the right version gets loaded. Initializing caja-main-menu extension ** Message: Initializing gksu extension... ps fxaw|grep caja|grep -v grep 2764 pts/8Sl 0:00 \_ caja 2338 ?Sl 0:00 \_ caja This is definitely not a problem with openssh, and one could argue caja is behaving like intended, but I'll leave that for others to decide. Marking the openssh task as invalid. ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1815318 Title: mate 18.04.1 xserver won't open caja on local machine Status in ubuntu-mate: New Status in caja package in Ubuntu: New Status in openssh package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have installed Ubuntu MATE 18.04 LTS (you know its hostname and IP - i.e. 192.168.1.162) 2. Install SSH server on Ubuntu MATE 18.04 LTS 3. Open terminal on other remote system (client) and execute command to run Caja over X forwarding: ssh -X user@192.168.1.162 caja Expected results: * Caja is shown on remote (client) screen with window title *folder (on hostname)* Actual results: * Caja is not shown on remote (client) screen, but launches on server locally. Note: this works normally if server runs Ubuntu MATE 16.04 LTS, but fails with 18.04 LTS. --- Original description below: I can open a remote terminal using ssh -X 192.168.1.162. All other gui's that I've tested opened locally except the file manager Caja. When issuing caja in the remote terminal, I get nothing locally. Caja does open on the remote machine however, just not locally. The ssh -X 18.04.1 client still works connecting to a mate 16.04 server. I've tested this on numerous mate 18.04 clients, two 16.04 servers and two 18.04 servers, all mate. Something is wonky with caja on an 18.04.1 server. Please let me know if I can provide any more information. The only file manager I've tested that works is an X file manager, xfimage. X2go works and connects to servers, SSH Connect to Server works, why isn't the remote X terminal working using caja? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1815318/+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 1814895] Re: display blinking and showing content of screen on sleep mode
*** This bug is a duplicate of bug 1570053 *** https://bugs.launchpad.net/bugs/1570053 ** This bug has been marked a duplicate of bug 1570053 Screen content is fully visible after unlocking screen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814895 Title: display blinking and showing content of screen on sleep mode Status in xorg package in Ubuntu: New Bug description: In previous versions of Ubuntu(18.04) when I close the laptop by flipping my display, it automatically goes to sleep mode and to turn it on, I have to enter the password. But in this version, when I close(flip the laptop display and make it in sleep mode), and again open and hit enter, it shows a blinking screen which shows all the content of screen without login and doesn't work anything on the screen. To come out from this issue I have to press the lock button from the keyboard and then it goes to the login screen. I should go to sleep mode and should not blink and show the content. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 6 18:31:06 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39f1] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:39f1] InstallationDate: Installed on 2019-02-05 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 0bda:57f9 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80SV ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=978388c7-13b2-4d73-90c2-0bc7490d3638 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C1 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN30WW:bd04/09/2018:svnLENOVO:pn80SV:pvrLenovoideapad510-15IKB:rvnLENOVO:rnTorronto5C1:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad510-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80SV dmi.product.sku: LENOVO_MT_80SV_BU_idea_FM_ dmi.product.version: Lenovo ideapad 510-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814895/+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 1815509] Re: Shutdown hung by firmware update daemon
** Changed in: fwupd (Ubuntu) Status: New => Incomplete -- 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/1815509 Title: Shutdown hung by firmware update daemon Status in fwupd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When rebooting my desktop, the shutdown sequence hangs for a long time on "Stopping firmware update daemon." It eventually will reboot but it hangs there for quite some time before doing so. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.12 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 11 13:39:51 2019 InstallationDate: Installed on 2018-07-24 (202 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1815509/+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 1451103] Re: ubuntu-standard depends on cron
I disagree a bit, I think we can just let new users use systemd timers.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1451103 Title: ubuntu-standard depends on cron Status in ubuntu-meta package in Ubuntu: New Bug description: ubuntu-standard have a hardcoded dependency on cron package. Instead it should depend on systemd-cron to decrease learning curve for new users and simplify system maintenance: it's much easier if periodic tasks are administered the same way as all other tasks - via standard units. People who need legacy software for some reason could easily install it from the repository. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451103/+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 1785629] Re: [MIR] gupnp-av
** Changed in: gupnp-av (Ubuntu) Assignee: Didier Roche (didrocks) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp-av in Ubuntu. https://bugs.launchpad.net/bugs/1785629 Title: [MIR] gupnp-av Status in gupnp-av package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries, including the gupnp-dlna one * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is not being used during build, we are going to look at changing that * Dependendies The package uses standard desktop libraries that are already in main (gstreamer, glib) * Standards compliance the package is using standard packaging (dh10), the standards-version is 3.9.8, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp-av/+bug/1785629/+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 1799974] Re: [MIR] gupnp
** Changed in: gupnp (Ubuntu) Assignee: Didier Roche (didrocks) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp in Ubuntu. https://bugs.launchpad.net/bugs/1799974 Title: [MIR] gupnp Status in gupnp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re- promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries * Security There is an old CVE recorded/fixed https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174 * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is used during build * Dependendies The package uses standard desktop libraries that are already in main * Standards compliance the package is using standard packaging (dh10), the standards-version is 4.2, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1799974/+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 1799977] Re: [MIR] gssdp
** Changed in: gssdp (Ubuntu) Assignee: Didier Roche (didrocks) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gssdp in Ubuntu. https://bugs.launchpad.net/bugs/1799977 Title: [MIR] gssdp Status in gssdp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re- promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on gssdp * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is being used during build * Dependendies The package dependencies are in main * Standards compliance the package is using standard packaging (dh11), the standards-version is 4.1.1, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssdp/+bug/1799977/+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 1798457] Re: Provide curtin-requirements and server-ship-live seeds
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu-seeds/+git/platform/+merge/363069 ** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu-seeds/+git/platform/+merge/363070 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1798457 Title: Provide curtin-requirements and server-ship-live seeds Status in ubuntu-meta package in Ubuntu: New Bug description: Provide curtin-requirements and server-ship-live seeds and make cdimage use them for server live images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1798457/+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 1815317] Re: Update gnome-online-accounts to 3.31.90
** Changed in: gnome-online-accounts (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1815317 Title: Update gnome-online-accounts to 3.31.90 Status in gnome-online-accounts package in Ubuntu: New Bug description: We should update gnome-online-accounts to 3.31.90 (Debian experimental has the update). GNOME has dropped its .png icons and replaced them with 128px .svg's. If we did the same, we could drop our binary patch since an .svg isn't a binary file. GNOME also includes a 16px symbolic .svg but I don't think those are used right now. So although getting the 128px .svg from Canonical Design isn't technically a blocker, I think it would be nice to get it for consistency (and simplifying our patches a bit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1815317/+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 1814355] Re: snapd remove /usr/local/bin from the PATH for all systemd unit (bionic SRU regression)
This bug was fixed in the package initramfs-tools - 0.131ubuntu17 --- initramfs-tools (0.131ubuntu17) disco; urgency=medium * Fix PATH to include /usr/local. LP: #1814355 -- Dimitri John Ledkov Tue, 12 Feb 2019 13:16:06 + ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1814355 Title: snapd remove /usr/local/bin from the PATH for all systemd unit (bionic SRU regression) Status in initramfs-tools package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in snapd source package in Bionic: Fix Released Status in systemd source package in Bionic: New Bug description: Big regression in 2.37.1+18.04 compare to version 2.34.2 all these paths /usr/local/sbin & /usr/local/bin are not anymore in the path of all systemd process . So we can not start a daemon that use /usr/local/bin reinstalling package 2.34.2 fix the problem in 2.34.2 : ~# strings /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin in 2.37.1+18.04 : ~# strings /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH PATH=/sbin:/usr/sbin:/bin:/usr/bin:/snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814355/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive
Oh I wasn't notified about Milan's answer. Sure I'll reinstall the addressbook (I've deleted it for now) and get a backtrace - in my copious spare time. Cheers, Xav -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1812474 Title: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive Status in evolution-data-server package in Ubuntu: Incomplete Bug description: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive; the GUI doesn't respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it lasts for a few minutes, then goes back to normal. If I wait long enough, the addressbook crashes (not enough memory ?). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 19 09:59:18 2019 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2017-01-09 (740 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+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 1815615] [NEW] Xorg freeze
Public bug reported: [ 290.765205] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=20358, emitted seq=20361 [ 290.765212] [drm] GPU recovery disabled. [ 485.063911] INFO: task kworker/u32:1:50 blocked for more than 120 seconds. [ 485.063922] Tainted: G OE 4.20.7-042007-generic #201902061234 [ 485.063925] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 485.063929] kworker/u32:1 D050 2 0x8000 [ 485.063952] Workqueue: events_unbound commit_work [drm_kms_helper] [ 485.063955] Call Trace: [ 485.063967] __schedule+0x29e/0x840 [ 485.063971] schedule+0x2c/0x80 [ 485.063974] schedule_preempt_disabled+0xe/0x10 [ 485.063977] __ww_mutex_lock.isra.11+0x3d8/0x760 [ 485.063981] __ww_mutex_lock_slowpath+0x16/0x20 [ 485.063983] ww_mutex_lock+0x34/0x50 [ 485.064115] amdgpu_dm_do_flip+0xeb/0x3a0 [amdgpu] [ 485.064213] amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu] [ 485.064216] ? __switch_to_asm+0x40/0x70 [ 485.064219] ? __switch_to_asm+0x34/0x70 [ 485.064221] ? wait_for_completion_timeout+0x38/0x140 [ 485.064223] ? __switch_to_asm+0x40/0x70 [ 485.064225] ? __switch_to_asm+0x34/0x70 [ 485.064227] ? __switch_to_asm+0x40/0x70 [ 485.064239] commit_tail+0x42/0x70 [drm_kms_helper] [ 485.064248] commit_work+0x12/0x20 [drm_kms_helper] [ 485.064253] process_one_work+0x20f/0x410 [ 485.064256] worker_thread+0x34/0x400 [ 485.064258] kthread+0x120/0x140 [ 485.064261] ? pwq_unbound_release_workfn+0xd0/0xd0 [ 485.064263] ? __kthread_parkme+0x70/0x70 [ 485.064266] ret_from_fork+0x22/0x40 [ 485.064463] INFO: task kworker/u32:14:2793 blocked for more than 120 seconds. [ 485.064467] Tainted: G OE 4.20.7-042007-generic #201902061234 [ 485.064468] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 485.064470] kworker/u32:14 D0 2793 2 0x8000 [ 485.064483] Workqueue: events_unbound commit_work [drm_kms_helper] [ 485.064484] Call Trace: [ 485.064487] __schedule+0x29e/0x840 [ 485.064489] schedule+0x2c/0x80 [ 485.064491] schedule_timeout+0x258/0x360 [ 485.064584] ? optc1_get_crtc_scanoutpos+0x69/0xa0 [amdgpu] [ 485.064590] dma_fence_default_wait+0x20a/0x280 [ 485.064592] ? dma_fence_release+0xa0/0xa0 [ 485.064595] dma_fence_wait_timeout+0xe7/0x110 [ 485.064598] reservation_object_wait_timeout_rcu+0x201/0x340 [ 485.064663] ? amdgpu_get_vblank_counter_kms+0x111/0x160 [amdgpu] [ 485.064757] amdgpu_dm_do_flip+0x12c/0x3a0 [amdgpu] [ 485.064852] amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu] [ 485.064855] ? __switch_to_asm+0x40/0x70 [ 485.064857] ? __switch_to_asm+0x34/0x70 [ 485.064859] ? wait_for_completion_timeout+0x38/0x140 [ 485.064861] ? __switch_to_asm+0x40/0x70 [ 485.064863] ? __switch_to_asm+0x34/0x70 [ 485.064865] ? __switch_to_asm+0x40/0x70 [ 485.064876] commit_tail+0x42/0x70 [drm_kms_helper] [ 485.064886] commit_work+0x12/0x20 [drm_kms_helper] [ 485.064889] process_one_work+0x20f/0x410 [ 485.064891] worker_thread+0x34/0x400 [ 485.064894] kthread+0x120/0x140 [ 485.064896] ? pwq_unbound_release_workfn+0xd0/0xd0 [ 485.064898] ? __kthread_parkme+0x70/0x70 [ 485.064901] ret_from_fork+0x22/0x40 [ 538.507722] r8169 :02:00.0: invalid short VPD tag 00 at offset 1 [ 538.507750] pcieport :00:01.3: AER: Multiple Corrected error received: :00:01.0 [ 538.507772] pcieport :00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 538.507781] pcieport :00:01.3: device [1022:15d3] error status/mask=1100/6000 [ 538.507787] pcieport :00:01.3:[ 8] Rollover [ 538.507791] pcieport :00:01.3:[12] Timeout [ 574.828588] RTW: WARN [TXFOVW] [ 574.831312] RTW: WARN [TXFOVW] [ 605.900149] INFO: task kworker/u32:1:50 blocked for more than 120 seconds. [ 605.900156] Tainted: G OE 4.20.7-042007-generic #201902061234 [ 605.900159] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 605.900162] kworker/u32:1 D050 2 0x8000 [ 605.900183] Workqueue: events_unbound commit_work [drm_kms_helper] [ 605.900185] Call Trace: [ 605.900195] __schedule+0x29e/0x840 [ 605.900199] schedule+0x2c/0x80 [ 605.900202] schedule_preempt_disabled+0xe/0x10 [ 605.900204] __ww_mutex_lock.isra.11+0x3d8/0x760 [ 605.900208] __ww_mutex_lock_slowpath+0x16/0x20 [ 605.900210] ww_mutex_lock+0x34/0x50 [ 605.900322] amdgpu_dm_do_flip+0xeb/0x3a0 [amdgpu] [ 605.900420] amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu] [ 605.900423] ? __switch_to_asm+0x40/0x70 [ 605.900425] ? __switch_to_asm+0x34/0x70 [ 605.900428] ? wait_for_completion_timeout+0x38/0x140 [ 605.900430] ? __switch_to_asm+0x40/0x70 [ 605.900432] ? __switch_to_asm+0x34/0x70 [ 605.900434] ? __switch_to_asm+0x40/0x70 [ 605.900445] commit_tail+0x42/0x70 [drm_kms_helper] [ 605.900455] commit_work+0x12/
[Touch-packages] [Bug 1777994] Re: the header xcb/xinput.h is missing
** Changed in: libxcb (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1777994 Title: the header xcb/xinput.h is missing Status in libxcb package in Ubuntu: Fix Released Status in libxcb source package in Bionic: Fix Committed Bug description: [Impact] Allow Qt 5.12 to be compiled with full input support. This allows applications to be built using complex input devices such as drawing pads. This is used in e.g Krita which KDE builds into a Snap package for distribution. Currently Krita does not work with pen input devices with pressure sensitivity. [Test Case] Install Krita with Qt 5.12 from current Snap and note how pressure sensitivity does not work. [Regression Potential] None that I can see, it's just packaging a few new header files. I suspect this means there should be another package, libxcb-xinput-dev perhaps? I already did sudo apt install "libxcb*dev" to get all related dev packages, but none of them provide xcb/xinput.h. The result is that when building Qt from source, it's necessary to use a copy of this file which Qt provides (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing from the system. So if you don't give the option -qt-xcb to configure, then Qt will be built without multi-touch support. https://bugreports.qt.io/browse/QTBUG-69045 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxcb1-dev 1.13-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 08:32:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3802] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: libxcb UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO 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 1:2.10.5-1ubuntu1 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/libxcb/+bug/1777994/+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 1815610] [NEW] Purple screen while booting
Public bug reported: I have to enter nouveau.modeset=0 every time I login ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 19:33:23 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8259] Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] [103c:8259] InstallationDate: Installed on 2019-02-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c87 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=06a4ab36-0cf8-4e0c-9a2d-acc278a88e47 ro quiet splash vt.handoff=1 nouveau.modeset=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.46 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd04/07/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.46:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 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 N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815610 Title: Purple screen while booting Status in xorg package in Ubuntu: New Bug description: I have to enter nouveau.modeset=0 every time I login ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 19:33:23 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8259] Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] [103c:8259] InstallationDate: Installed on 2019-02-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c87 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=06a4ab36-0cf8-4e0c-9a2d-acc278a88e47 ro quiet splash vt.handoff=1 nouveau.modeset=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.46 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd04/07/2017:svnHP:pnOMENbyHPLaptop:pvrT
[Touch-packages] [Bug 1810364] Re: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1810364 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: n@computer-1:~/Desktop$ sudo apt install lvm2 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 Suggested packages: thin-provisioning-tools The following NEW packages will be installed: dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 2,090 kB of archives. After this operation, 8,260 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 libdevmapper-event1.02.1 amd64 2:1.02.145-4.1ubuntu3 [10.9 kB] Get:2 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 liblvm2cmd2.02 amd64 2.02.176-4.1ubuntu3 [586 kB] Get:3 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 dmeventd amd64 2:1.02.145-4.1ubuntu3 [30.4 kB] Get:4 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 liblvm2app2.2 amd64 2.02.176-4.1ubuntu3 [433 kB] Get:5 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 libreadline5 amd64 5.2+dfsg-3build2 [101 kB] Get:6 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 lvm2 amd64 2.02.176-4.1ubuntu3 [929 kB] Fetched 2,090 kB in 4s (470 kB/s) Selecting previously unselected package libdevmapper-event1.02.1:amd64. (Reading database ... 298985 files and directories currently installed.) Preparing to unpack .../0-libdevmapper-event1.02.1_2%3a1.02.145-4.1ubuntu3_amd64.deb ... Unpacking libdevmapper-event1.02.1:amd64 (2:1.02.145-4.1ubuntu3) ... Selecting previously unselected package liblvm2cmd2.02:amd64. Preparing to unpack .../1-liblvm2cmd2.02_2.02.176-4.1ubuntu3_amd64.deb ... Unpacking liblvm2cmd2.02:amd64 (2.02.176-4.1ubuntu3) ... Selecting previously unselected package dmeventd. Preparing to unpack .../2-dmeventd_2%3a1.02.145-4.1ubuntu3_amd64.deb ... Unpacking dmeventd (2:1.02.145-4.1ubuntu3) ... Selecting previously unselected package liblvm2app2.2:amd64. Preparing to unpack .../3-liblvm2app2.2_2.02.176-4.1ubuntu3_amd64.deb ... Unpacking liblvm2app2.2:amd64 (2.02.176-4.1ubuntu3) ... Selecting previously unselected package libreadline5:amd64. Preparing to unpack .../4-libreadline5_5.2+dfsg-3build2_amd64.deb ... Unpacking libreadline5:amd64 (5.2+dfsg-3build2) ... Selecting previously unselected package lvm2. Preparing to unpack .../5-lvm2_2.02.176-4.1ubuntu3_amd64.deb ... Unpacking lvm2 (2.02.176-4.1ubuntu3) ... Setting up libdevmapper-event1.02.1:amd64 (2:1.02.145-4.1ubuntu3) ... Processing triggers for libc-bin (2.28-0ubuntu1) ... Processing triggers for systemd (239-7ubuntu10.4) ... Setting up liblvm2app2.2:amd64 (2.02.176-4.1ubuntu3) ... Processing triggers for man-db (2.8.4-2) ... Setting up libreadline5:amd64 (5.2+dfsg-3build2) ... Setting up liblvm2cmd2.02:amd64 (2.02.176-4.1ubuntu3) ... Setting up dmeventd (2:1.02.145-4.1ubuntu3) ... dm-event.service is a disabled or a static unit not running, not starting it. Setting up lvm2 (2.02.176-4.1ubuntu3) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) since Wed 2019-01-02 21:42:08 CST; 27min ago Docs: man:lvmetad(8) Main PID: 320 (code=exited, status=0/SUCCESS) Jan 02 21:28:53 audiocito-1 systemd[1]: Started LVM2 metadata daemon. Jan 02 21:42:08 audiocito-1 systemd[1]: Stopping LVM2 metadata daemon... Jan 02 21:42:08 audiocito-1 systemd[1]: Stopped LVM2 metadata daemon. dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.28-0ubuntu1) ... Processing triggers for initramfs-tools (0.131ubuntu15) ... update-initramfs: Generating /boot/initrd.img-4.18.0-13-lowlatency Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.10 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature:
[Touch-packages] [Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
I have just found the following message in syslog: Feb 12 13:25:56 samsung5-ubuntu colord-sane: message repeated 2 times: [ [bjnp] create_broadcast_socket: ERROR - bind socket to local address failed - Cannot assign requested address] that matches: ● colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled) Active: active (running) since Tue 2019-02-12 02:30:41 CET; 11h ago Main PID: 2098 (colord) Tasks: 3 (limit: 4915) Memory: 14.9M CGroup: /system.slice/colord.service └─2098 /usr/lib/colord/colord Feb 12 02:30:41 samsung5-ubuntu systemd[1]: Starting Manage, Install and Generate Color Profiles... Feb 12 02:30:41 samsung5-ubuntu systemd[1]: Started Manage, Install and Generate Color Profiles. Feb 12 02:30:42 samsung5-ubuntu colord[2098]: failed to get session [pid 2118]: No data available Feb 12 02:30:42 samsung5-ubuntu colord-sane[2240]: [bjnp] create_broadcast_socket: ERROR - bind socket to local address failed - Cannot assign requested address This lead me to investigate the SANE scanner and more specifically /etc/sane.d/dll.conf which seems to list image scanner hardware drivers, including canon ones. However, commenting out 'net' or all canon-related lines does not change anything: # systemctl restart colord # systemctl status colord ● colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled) Active: active (running) since Tue 2019-02-12 14:21:12 CET; 4s ago Main PID: 31838 (colord) Tasks: 4 (limit: 4915) Memory: 8.0M CGroup: /system.slice/colord.service └─31838 /usr/lib/colord/colord Feb 12 14:21:12 samsung5-ubuntu systemd[1]: Starting Manage, Install and Generate Color Profiles... Feb 12 14:21:12 samsung5-ubuntu systemd[1]: Started Manage, Install and Generate Color Profiles. Feb 12 14:21:13 samsung5-ubuntu colord-sane[31859]: [bjnp] create_broadcast_socket: ERROR - bind socket to local address failed - Cannot assign requested address -- 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/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP Status in cups package in Ubuntu: Confirmed Bug description: It appears that the cups-browsed service as of Xenial (version 1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected conditions and regardless of a presence or lack of Canon printer devices on the network. This is manifested by enabling UFW, and observing multicast requests being blocked that are sent from the host machine's network IPv4 or IPv6 address to the multicast address, e.g. [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24 IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24 Users have observed that the requests can be reproduced when any USB device is plugged/unplugged into the computer, regardless of whether the device has anything to do with printing: https://twitter.com/gertvdijk/status/621790755758178304 https://bugs.kali.org/view.php?id=3094 Just Googling "udp 8612", shows are a large number of results on different websites of people who have observed this behaviour in firewall and traffic logs, and have noticed that it may contribute to network slowdown and latency: https://askubuntu.com/questions/867739/what-is-this-traffic/867786 https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends disabling the cups-browsed service to stop these requests: systemctl stop cups-browsed.service systemctl disable cups-browsed.service There are probably two things to address here: 1. Connecting any USB device should not cause these requests unless the device is actually a printer or directly related to printing. 2. Requests independent of connecting USB devices should be rate limited to a degree and/or should be dependent on the actual presence of a Canon printer configured on the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1779157] Re: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@1927:main:do_install
** Tags added: id-5c5c4808c0b18e80534bdd44 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1779157 Title: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended- upgrade@1927:main:do_install Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] * Unattended-upgrades can be crashing when packages are marked for removal after collecting upgradable packages. * The fix clear the cache when it may be in an invalid state to lose markings. [Test Case] * Observe https://errors.ubuntu.com/problem/66b5fef8d6dd83a7db6c494c807cfc067626c0c2 not occurring in fixed versions. [Regression Potential] * The extra cache.clear() can take extra CPU time when invoked needlessly or can cause skipping updates when invoked at the wrong time. However the fix received extensive testing in newer releases making unnoticed regressions unlikely to surface. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.1, the problem page at https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c 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/. Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1927, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1782, in main logfile_dpkg) File "/usr/bin/unattended-upgrade", line 1057, in do_install "removal:%s" % "".join([pkg.name for pkg in marked_delete])) AssertionError: Internal error. The following packages are marked for removal:linux-headers-4.15.0-20-generic Also seen as: https://errors.ubuntu.com/problem/733d2e7865692e215f406231edd3692a6a1810c5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1779157/+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 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not
** Tags added: id-5c5c4493f028f40f2e8867c3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1781176 Title: Blacklisted packages are included in the "upgradable origin", while they should not Status in unattended-upgrades: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Bionic: Confirmed Bug description: [Impact] * Reports from u-u incorrectly list packages from non-upgradable origins as "Packages with upgradable origin but kept back" * Listing the packages incorrectly is a result of is_pkgname_in_blacklist() having a side effect and removing the side effect is part of fixing LP: #1396787 which fix is also being SRU-d. * The fix is removing the side effect of is_pkgname_in_blacklist() [Test Case] * There is a build-time test in test/test_blacklisted_wrong_origin.py * To reproduce the original problem set up a system where all security updates are installed but ebtables (from bionic-updates) is not updated: $ sudo unattended-upgrade --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic No packages found that can be upgraded unattended and no pending auto-removals $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: apt apt-utils ebtables initramfs-tools initramfs-tools-bin initramfs-tools-core libapt-inst2.0 libapt-pkg5.0 liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io networkd-dispatcher nplan python-apt-common python3 python3-apt python3-minimal python3-update-manager snapd squashfs-tools unattended-upgrades update-manager-core update-notifier-common 27 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 24.1 MB of archives. After this operation, 1454 kB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. * blacklist ebtables, set up emails from u-u, then run u-u again: $ sudo echo 'Unattended-Upgrade::Package-Blacklist {"ebtables";};' > /etc/apt/apt.conf.d/51unattended-upgrades-blacklist-ebtables $ sudo echo 'Unattended-Upgrade::Mail "root";' > /etc/apt/apt.conf.d/51unattended-upgrades-mail $ sudo unattended-upgrade --verbose Initial blacklisted packages: ebtables Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic Packages that will be upgraded: * Observe ebtables listed as being kept back and having upgradable origin with buggy u-u: $ sudo cat /var/mail/mail ... Packages with upgradable origin but kept back: ebtables=20 ... * Upgrade u-u to a fixed version and run it, observing ebtables to be not listed as having upgradable origin [Regression Potential] * Regressions may make packages incorrectly missing from u-u's report, but the autopkgtests also cover that to some extent. [Other Info] * Original report: https://github.com/mvo5/unattended- upgrades/issues/116 To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1781176/+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 1814355] Re: snapd remove /usr/local/bin from the PATH for all systemd unit (bionic SRU regression)
Also initramfs-tools sets PATH without /usr/local, which may leak into init environment. Fixing this as well. ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1814355 Title: snapd remove /usr/local/bin from the PATH for all systemd unit (bionic SRU regression) Status in initramfs-tools package in Ubuntu: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in snapd source package in Bionic: Fix Released Status in systemd source package in Bionic: New Bug description: Big regression in 2.37.1+18.04 compare to version 2.34.2 all these paths /usr/local/sbin & /usr/local/bin are not anymore in the path of all systemd process . So we can not start a daemon that use /usr/local/bin reinstalling package 2.34.2 fix the problem in 2.34.2 : ~# strings /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin in 2.37.1+18.04 : ~# strings /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH PATH=/sbin:/usr/sbin:/bin:/usr/bin:/snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814355/+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 1815509] Re: Shutdown hung by firmware update daemon
** Tags added: id-5c61d08a6841f5197a72f7ea -- 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/1815509 Title: Shutdown hung by firmware update daemon Status in fwupd package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When rebooting my desktop, the shutdown sequence hangs for a long time on "Stopping firmware update daemon." It eventually will reboot but it hangs there for quite some time before doing so. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.12 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 11 13:39:51 2019 InstallationDate: Installed on 2018-07-24 (202 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1815509/+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 1766140] Re: OpenGL Renderer window appears in tab list when playing a video
Most probably Wayland-specific. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1766140 Title: OpenGL Renderer window appears in tab list when playing a video Status in epiphany-browser package in Ubuntu: Confirmed Status in gst-plugins-base1.0 package in Ubuntu: Confirmed Bug description: Every time a web page plays a video in Epiphany, a window named "OpenGL Renderer" appears in the gnome-shell alt-tab list (but not in the overview), one for each video. If I have several pages open with several videos, I get several of these phantom windows. Selecting the window in the list does nothing. This started happening sometime during the beta, it didn't happen under 17.10 or after first upgrading to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: epiphany-browser 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 23 10:51:07 2018 InstallationDate: Installed on 2015-07-22 (1005 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1766140/+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 1766140] Re: OpenGL Renderer window appears in tab list when playing a video
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1766140 Title: OpenGL Renderer window appears in tab list when playing a video Status in epiphany-browser package in Ubuntu: Confirmed Status in gst-plugins-base1.0 package in Ubuntu: Confirmed Bug description: Every time a web page plays a video in Epiphany, a window named "OpenGL Renderer" appears in the gnome-shell alt-tab list (but not in the overview), one for each video. If I have several pages open with several videos, I get several of these phantom windows. Selecting the window in the list does nothing. This started happening sometime during the beta, it didn't happen under 17.10 or after first upgrading to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: epiphany-browser 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 23 10:51:07 2018 InstallationDate: Installed on 2015-07-22 (1005 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1766140/+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 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink
When I install an older kernel, do DKMS modules need to be rebuilt, or do DKMS modules only need to built for newer kernels? -- 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/1815523 Title: The last MESA updates (02/07/19) corrupted output to DisplayLink Status in mesa package in Ubuntu: Incomplete Bug description: Prior to Thursday's "update" from Bionic-Proposed, the MESA was working fine; afterwards, gameplay on STEAM has become choppy and staccato; secondary display via a USB-C through DisplayPort UD3900 (Pluggable) is completely corrupted. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Feb 11 16:50:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1323] InstallationDate: Installed on 2019-01-15 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display 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 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: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 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/mesa/+bug/1815523/+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 1766140] Re: OpenGL Renderer window appears in tab list when playing a video
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: epiphany-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1766140 Title: OpenGL Renderer window appears in tab list when playing a video Status in epiphany-browser package in Ubuntu: Confirmed Status in gst-plugins-base1.0 package in Ubuntu: Confirmed Bug description: Every time a web page plays a video in Epiphany, a window named "OpenGL Renderer" appears in the gnome-shell alt-tab list (but not in the overview), one for each video. If I have several pages open with several videos, I get several of these phantom windows. Selecting the window in the list does nothing. This started happening sometime during the beta, it didn't happen under 17.10 or after first upgrading to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: epiphany-browser 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 23 10:51:07 2018 InstallationDate: Installed on 2015-07-22 (1005 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1766140/+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 1810840] Re: whoopsie can't remember "always report" setting
Same for me, it seems like whoopsie-preferences is not installed by default v@v-IdeaPad-U330p:~$ /usr/bin/gdbus call -y -d com.ubuntu.WhoopsiePreferences -o \ /com/ubuntu/WhoopsiePreferences -m com.ubuntu.WhoopsiePreferences.SetReportCrashes true Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.ubuntu.WhoopsiePreferences was not provided by any .service files It can be fixed by installing whoopsie-preferences v@v-IdeaPad-U330p:~$ sudo apt-get install -y whoopsie-preferences -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie-preferences in Ubuntu. https://bugs.launchpad.net/bugs/1810840 Title: whoopsie can't remember "always report" setting Status in whoopsie-preferences package in Ubuntu: Confirmed Bug description: After ticking the checkbox for whoopsie to automatically always send crash reports, I get the following error dialog (screenshot attached): *Can't remember send report status settings* Saving crash report state failed. Can't set auto or never reporting mode. Command '['/usr/bin/gdbus', 'call', '-y', '-d', 'com.ubuntu.WhoopsiePreferences', '-o', '/com/ubuntu/WhoopsiePreferences', '-m', 'com.ubuntu.WhoopsiePreferences.SetReportCrashes', 'true']' returned non-zero exit status 1. I'm pretty sure this error happens because whoopsie-preferences was not installed; afterwards I installed whoopsie-preferences and manually ran in a terminal: $ /usr/bin/gdbus call -y -d com.ubuntu.WhoopsiePreferences -o /com/ubuntu/WhoopsiePreferences -m com.ubuntu.WhoopsiePreferences.SetReportCrashes true and got a return value of () but no errors or warnings. This computer was freshly-installed with Xubuntu 18.04 less than 2 weeks ago... I've kept a record of everything I changed since then, and I've only removed five packages (sgt-puzzles, gnome-sudoku, gnome- mines, pidgin, mousepad). If whoopsie-preferences is not included in a fresh install of (X)ubuntu, then perhaps it should be; in any case, if it isn't installed then the checkbox for making crash reporting automatic should not be visible. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy whoopsie whoopsie: Installed: 0.2.62 Candidate: 0.2.62 Version table: *** 0.2.62 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy whoopsie-preferences whoopsie-preferences: Installed: (none) Candidate: 0.19 Version table: 0.19 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/1810840/+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 1815509] Re: Shutdown hung by firmware update daemon
Can you please do the following: 1) confirm that masking the service (ur preventing it from starting) fixes the problem? 2) modify the service to start in verbose mode (add --verbose to launch flag) 3) share journal output from an attempt with verbose mode enabled. -- 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/1815509 Title: Shutdown hung by firmware update daemon Status in fwupd package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When rebooting my desktop, the shutdown sequence hangs for a long time on "Stopping firmware update daemon." It eventually will reboot but it hangs there for quite some time before doing so. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.12 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 11 13:39:51 2019 InstallationDate: Installed on 2018-07-24 (202 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1815509/+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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
I ha -- 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/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP Status in cups package in Ubuntu: Confirmed Bug description: It appears that the cups-browsed service as of Xenial (version 1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected conditions and regardless of a presence or lack of Canon printer devices on the network. This is manifested by enabling UFW, and observing multicast requests being blocked that are sent from the host machine's network IPv4 or IPv6 address to the multicast address, e.g. [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24 IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24 Users have observed that the requests can be reproduced when any USB device is plugged/unplugged into the computer, regardless of whether the device has anything to do with printing: https://twitter.com/gertvdijk/status/621790755758178304 https://bugs.kali.org/view.php?id=3094 Just Googling "udp 8612", shows are a large number of results on different websites of people who have observed this behaviour in firewall and traffic logs, and have noticed that it may contribute to network slowdown and latency: https://askubuntu.com/questions/867739/what-is-this-traffic/867786 https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends disabling the cups-browsed service to stop these requests: systemctl stop cups-browsed.service systemctl disable cups-browsed.service There are probably two things to address here: 1. Connecting any USB device should not cause these requests unless the device is actually a printer or directly related to printing. 2. Requests independent of connecting USB devices should be rate limited to a degree and/or should be dependent on the actual presence of a Canon printer configured on the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink
Yeah, I removed the older kernels during a clean-up. How do I re- install one back? -- 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/1815523 Title: The last MESA updates (02/07/19) corrupted output to DisplayLink Status in mesa package in Ubuntu: Incomplete Bug description: Prior to Thursday's "update" from Bionic-Proposed, the MESA was working fine; afterwards, gameplay on STEAM has become choppy and staccato; secondary display via a USB-C through DisplayPort UD3900 (Pluggable) is completely corrupted. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Feb 11 16:50:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1323] InstallationDate: Installed on 2019-01-15 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display 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 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: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 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/mesa/+bug/1815523/+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 1778844] Comment bridged from LTC Bugzilla
--- Comment From hbath...@in.ibm.com 2019-02-12 06:15 EDT--- (In reply to comment #87) > Hi, Andrew and Hari. > > The original issue is only resolved by using an initramfs-tools from my ppa. > We still need to get this fix included in our releases. I will start working > to get this in disco. > > Cascardo. Right, Cascardo. Waiting for the fix to be released in an official build.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: Won't Fix Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: In Progress Status in linux source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: In Progress Status in linux source package in Cosmic: Invalid Status in makedumpfile source package in Cosmic: Invalid Status in initramfs-tools source package in Disco: In Progress Status in linux source package in Disco: Invalid Status in makedumpfile source package in Disco: Invalid Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00:
[Touch-packages] [Bug 1815129] Re: apt segfaults when generating cache file
Hello Heitor, or anyone else affected, Accepted apt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.20 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815129 Title: apt segfaults when generating cache file Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Committed Status in apt package in Debian: Fix Released Bug description: [Impact] apt crashes (core dump) during cache creation [Description] When executing apt-cache several times on a memory constrained system, apt-cache can sometimes crash with a core dump file. This is related to mmap() failing allocations during cache generation, according to an upstream bug report (803417). There is an upstream patch for this bug (6789e01e do not segfault in cache generation on mmap failure) and it's included in the apt package for other series (see below), so we only need to backport it to Trusty. Upstream commit: https://salsa.debian.org/apt- team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1 $ git describe --contains 6789e01e9370 1.1_exp16~5 $ rmadison apt apt | 1.0.1ubuntu2| trusty | source, ... apt | 1.0.1ubuntu2.19 | trusty-security | source, ... apt | 1.0.1ubuntu2.19 | trusty-updates | source, ... apt | 1.2.10ubuntu1 | xenial | source, ... apt | 1.6.1 | bionic | source, ... apt | 1.7.0 | cosmic | source, ... apt | 1.8.0~rc2 | disco| source, ... [Test Case] 1) Deploy a Trusty (14.04 LTS) vm w/ 128M 2) Fetch latest stress-ng src code 2.1) git clone git://kernel.ubuntu.com/cking/stress-ng 2.2) cd stress-ng 2.3) make clean 2.4) make 3) Stress the mmap() with stress-ng 3.1) ./stress-ng --brk 2 --mmap 5 --vm 1 --mmap-bytes 90% 4) Disable swap (if any) 4.1) swapoff -a 5) for i in `seq 1 1`;do apt-cache policy vsftpd;done ... vsftpd: Installed: (none) Candidate: 3.0.2-1ubuntu2.14.04.1 Version table: 3.0.2-1ubuntu2.14.04.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3.0.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) ... [Regression Potential] The regression potential for this should be low, as it's a change in the failure path for memory allocations. This shouldn't be triggered during normal usage, and we'll thoroughly test the patched package with autopkgtests and perform scripted runs in memory-constrained systems with stress-ng. We also have a confirmation from an impacted user that the upstream patch fixes their issue without further problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815129/+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 1778844] Re: nvme multipath does not report path relationships
Hi, Andrew and Hari. The original issue is only resolved by using an initramfs-tools from my ppa. We still need to get this fix included in our releases. I will start working to get this in disco. Cascardo. ** Changed in: initramfs-tools (Ubuntu) Status: Invalid => In Progress ** Also affects: initramfs-tools (Ubuntu Disco) Importance: Critical Assignee: Canonical Kernel Team (canonical-kernel-team) Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Critical Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Also affects: makedumpfile (Ubuntu Disco) Importance: Critical Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Changed in: initramfs-tools (Ubuntu Cosmic) Status: Invalid => In Progress ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Invalid => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: Won't Fix Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: In Progress Status in linux source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: In Progress Status in linux source package in Cosmic: Invalid Status in makedumpfile source package in Cosmic: Invalid Status in initramfs-tools source package in Disco: In Progress Status in linux source package in Disco: Invalid Status in makedumpfile source package in Disco: Invalid Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_tra
[Touch-packages] [Bug 1815187] Re: Fix crash when opening DepCache before Cache
Hello Julian, or anyone else affected, Accepted apt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.20 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815187 Title: Fix crash when opening DepCache before Cache Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Committed Bug description: [Impact] apt search and probably other code crashes some time, as GetDepCache() in trusty does not call BuildCaches() first. [Test case] Run apt search -o RootDir=/dev/null foobar, make sure it does not crash. [Regression potential] There may be some locking implications, as we build caches when opening depcache first, without locks. That said, the same code is in use in all post-trusty releases, and they work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815187/+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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
Using Brian's workaround (#36) I'm able to netboot. However, raising the network interfaces fails. Is it related? journalctl shows: ubuntu ifup[3055]: Error: any valid prefix is expected rather than "dhcp/dhcp" Networking does partially work: pinging IP addresses work, but DNS resolution doesn't. -- 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/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Triaged Status in systemd source package in Disco: Fix Released Bug description: [Impact] Mounting manually a network share (NFS) and masking it breaks the state of other units (and their dependencies). Casper is masking a mounted NFS share, blocking the normal boot process as described in the original description, but the issue comes from systemd. [Test Case] - NFS mount point at /media root@iscsi-bionic:/home/ubuntu# mount | grep media 10.230.56.72:/tmp/mnt on /media type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72) - Test mount point (/test) defined in /etc/fstab: root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test tmpfs /test tmpfs nosuid,nodev 0 0 1. If media.mount is not masked, everything works fine: root@iscsi-bionic:/home/ubuntu# mount | grep test root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days ago root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago root@iscsi-bionic:/home/ubuntu# systemctl start test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test 2. If media.mount is masked, other mounts are failing: root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount Created symlink /etc/systemd/system/media.mount → /dev/null. root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) [Regression potential] Minimal. Originally, one failing mount point blocked the processing of the rest due to how the return codes were handled for every line in /proc/self/mountinfo. This patch removes this "dependency" and keeps the failure local to the affected mount point, allowing the rest to be processed normally. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10874 Fixed upstream with commit: https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3 [Original Description] netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm=
[Touch-packages] [Bug 1815187] Re: Fix crash when opening DepCache before Cache
** Description changed: [Impact] apt search and probably other code crashes some time, as GetDepCache() in trusty does not call BuildCaches() first. [Test case] - TODO, some apt search -o RootDir= foobar + Run apt search -o RootDir=/dev/null foobar, make sure it does not crash. [Regression potential] There may be some locking implications, as we build caches when opening depcache first, without locks. That said, the same code is in use in all post-trusty releases, and they work fine. ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Trusty) Status: New => In Progress ** Changed in: apt (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815187 Title: Fix crash when opening DepCache before Cache Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Bug description: [Impact] apt search and probably other code crashes some time, as GetDepCache() in trusty does not call BuildCaches() first. [Test case] Run apt search -o RootDir=/dev/null foobar, make sure it does not crash. [Regression potential] There may be some locking implications, as we build caches when opening depcache first, without locks. That said, the same code is in use in all post-trusty releases, and they work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815187/+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 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive
Did you read the upstream comment on https://gitlab.gnome.org/GNOME /evolution-data-server/issues/78 ? what do you need help with/is not clear in their instructions? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1812474 Title: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive Status in evolution-data-server package in Ubuntu: Incomplete Bug description: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive; the GUI doesn't respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it lasts for a few minutes, then goes back to normal. If I wait long enough, the addressbook crashes (not enough memory ?). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 19 09:59:18 2019 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2017-01-09 (740 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+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 1815509] Re: Shutdown hung by firmware update daemon
** Also affects: fwupd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815509 Title: Shutdown hung by firmware update daemon Status in fwupd package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When rebooting my desktop, the shutdown sequence hangs for a long time on "Stopping firmware update daemon." It eventually will reboot but it hangs there for quite some time before doing so. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.12 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 11 13:39:51 2019 InstallationDate: Installed on 2018-07-24 (202 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1815509/+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 1745908] Re: [32493DC, Conexant CX20585, Speaker, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1745908 Title: [32493DC, Conexant CX20585, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: When loading the desktop, the volume icon on the right top of the desktop was uncontrollably switched. And the link-sinks command tells the speaker unavailable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chen 1857 F pulseaudio chen 3278 F alsamixer CurrentDesktop: Unity Date: Mon Jan 29 10:10:33 2018 InstallationDate: Installed on 2018-01-01 (27 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: 内置音频 - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chen 1857 F pulseaudio chen 3278 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [32493DC, Conexant CX20585, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2018-01-28 (0 days ago) dmi.bios.date: 09/15/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET53WW (1.23 ) dmi.board.name: 32493DC 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:bvr6QET53WW(1.23):bd09/15/2010:svnLENOVO:pn32493DC:pvrThinkPadX201:rvnLENOVO:rn32493DC:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 32493DC dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1745908/+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 1815524] Re: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
*** This bug is a duplicate of bug 1745908 *** https://bugs.launchpad.net/bugs/1745908 ** This bug has been marked a duplicate of bug 1745908 [32493DC, Conexant CX20585, Speaker, Internal] No sound at all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1815524 Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Headphones work just fine. Internal speakers do not work. There was a brief moment where the drum sound played on log-in one time but then the speakers have never output anything again. NOTE: A few releases ago: 14.04 LTS?!? (Before 16.04, in any case) the sound worked perfectly. It hasn't worked since that time. I recently did a fresh install of Ubuntu 18.04 to se if it would clean up the problem. It only corrected the issue very briefly. 1) Ubuntu 18.04.2 LTS 2) alsa-base 1.0.25+dfsg-0ubuntu5 3) Sound output through internal speakers 4) No sound output through external speakers. The only sound output possible is via headphones. Headphones confirmed to work normally with sound output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geoffrey 1971 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Feb 11 17:11:25 2019 InstallationDate: Installed on 2019-02-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geoffrey 1971 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2012 dmi.bios.vendor: INSYDE dmi.bios.version: 2.60 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-0D102G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite L745 dmi.product.version: PSK0YU-0D102G dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1815524/+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 1815531] Re: xserver-xorg-video-intel unmet dependencies
you are using the hwe stack from 16.04.5, install xserver-xorg-video- intel-hwe-16.04 instead ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815531 Title: xserver-xorg-video-intel unmet dependencies Status in xorg package in Ubuntu: Invalid Bug description: sudo apt-get install xserver-xorg-video-intel Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-20 Depends: xserver-xorg-core (>= 2:1.17.99.902) E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Feb 11 17:31:56 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Core Processor Integrated Graphics Controller [104d:9071] InstallationDate: Installed on 2018-09-27 (137 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Sony Corporation VPCEB47GM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=0d81f100-6886-468d-afc5-7f52f2a1d3b2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1140Y8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:svnSonyCorporation:pnVPCEB47GM:pvrC6081XS0:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCEB47GM dmi.product.version: C6081XS0 dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Feb 11 10:48:05 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-1 HDMI-1 LVDS-1 VGA-1 xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815531/+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 1815429] Re: Xorg crash
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-410 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815429 Title: Xorg crash Status in nvidia-graphics-drivers-410 package in Ubuntu: New Bug description: Steps to reproduce 1. setup a virtual machine with GPU pass-through to a nvidia Quadro card (nvidia only supports passthrough to Quadro cards). Nvidia also recommends that the passed-through card has its ROM disabled in VM configuration, i.e. . Attached an example of such VM. 2. install vanilla Xubuntu 18.04, do not enable auto-login 3. install nvidia drivers, e.g. $ sudo add-apt-repository ppa:graphics-drivers/ppa $ sudo apt-get install nvidia-driver-410 4. reboot (the screen may be black until the greeter appears) 5. login 6. lock the screen back to the greeter $ light-locker-command --lock Now you have black screen and unresponsive keyboard, and also one more file in /var/crash . The only way to get to the greeter again is to run (from another session, e.g. ssh) $ sudo systemctl restart lightdm ... which will also kill all the sessions running under the login manger (including the one where we tried to lock the screen) I've found that this only happens with stock xfwm4 version 4.12 . If I upgrade xfwm4 to version 4.13 (from Mint) the screen lock works as expected, but this package is not in Ubuntu repo. So perhaps the problem is not with Xorg but with old xfwm4. I also tried other flavours of Ubuntu and IIRC also seen it in Lubuntu. At a stretch this could be called security vulnerability, because with this bug there is no way to lock the screen, hence users will always leave their session unlocked (or must log off) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 410.78 Sat Nov 10 22:09:04 CST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: CompositorRunning: None Date: Mon Feb 11 09:14:54 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 410.78, 4.15.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204GL [Quadro M5000] [10de:13f0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM204GL [Quadro M5000] [10de:1152] InstallationDate: Installed on 2019-02-10 (0 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=16524009-5b46-4f13-918c-0dee6cce40fe ro console=tty0 console=ttyS0,115200n8 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/nvidia-graphics-drivers-410/+bug/1815429/+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 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink
You mean it worked with mesa 18.2.2? Try with an older kernel too ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1815523 Title: The last MESA updates (02/07/19) corrupted output to DisplayLink Status in mesa package in Ubuntu: Incomplete Bug description: Prior to Thursday's "update" from Bionic-Proposed, the MESA was working fine; afterwards, gameplay on STEAM has become choppy and staccato; secondary display via a USB-C through DisplayPort UD3900 (Pluggable) is completely corrupted. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Feb 11 16:50:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1323] InstallationDate: Installed on 2019-01-15 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display 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 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: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 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/mesa/+bug/1815523/+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 1755250] Re: backport statx syscall whitelist fix
All pre-checks and tests complete, and uploaded to the SRU review queue ** Changed in: libseccomp (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1755250 Title: backport statx syscall whitelist fix Status in docker.io package in Ubuntu: Invalid Status in libseccomp package in Ubuntu: Fix Released Status in docker.io source package in Bionic: Invalid Status in libseccomp source package in Bionic: In Progress Status in docker.io source package in Cosmic: Invalid Status in libseccomp source package in Cosmic: Fix Released Bug description: [Impact] * Some newer workloads fail due to libseccomp as in Bionic lacking statx support * This backports the syscall definitions for statx to Bionic to allow to manage those [Test Case] # Note: I took a KVM image of Bionic to not spoil my system with Docker config for this test too much $ sudo apt install docker.io $ sudo usermod -a -G docker ubuntu $ cat > test-statx/Dockerfile << EOF FROM ubuntu:18.04 RUN apt-get update && apt-get install -y wget gcc WORKDIR /tmp RUN wget -q https://raw.githubusercontent.com/torvalds/linux/master/samples/statx/test-statx.c RUN gcc test-statx.c -o test-statx RUN touch test-file RUN chmod +x ./test-statx RUN ./test-statx test-file EOF $ docker build test-statx With the bug and current docker 18.06.1-0ubuntu1~18.04.1 in Bionic that yields [...] Step 8/8 : RUN ./test-statx test-file ---> Running in 6e60a82409e6 test-file: Operation not permitted statx(test-file) = -1 The command '/bin/sh -c ./test-statx test-file' returned a non-zero code: 1 With the fix applied it would work and look like: Step 8/8 : RUN ./test-statx test-file ---> Running in a83bc043e7bd statx(test-file) = 0 results=fff Size: 0 Blocks: 0 IO Block: 4096regular file Device: 00:32 Inode: 261994 Links: 1 Access: (0644/-rw-r--r--) Uid: 0 Gid: 0 Access: 2019-02-08 07:57:42.0+ Modify: 2019-02-08 07:57:42.0+ Change: 2019-02-08 07:57:43.076507007+ Birth: 2019-02-08 07:57:43.076507007+ Attributes: ( -... .---.-..) Removing intermediate container a83bc043e7bd ---> d428d14cbc57 Successfully built d428d14cbc57 [Regression Potential] * This "only" defines a new syscall number for all the architectures. It does not make any other changes, thereby it should be rather safe. If anything software could now manage statx through libseccomp and behavior that was formerly failing (like the reported docker case) would not succeed and due to that be a change in behavior - but I think it is a wanted change. [Other Info] * n/a --- Hello maintainer, The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall which is needed to build qt >=5.10 applications: https://github.com/docker/for-linux/issues/208#issuecomment-372400859 Could this fix be backported in the ubuntu package ? https://github.com/moby/moby/pull/36417 regards, xan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250/+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 1815415] Re: please update libseccomp for newer kernel syscalls
FYI (to find it easier) logs of the new build: - autopkgtest with new version https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-ci-train-ppa-service-3640/bionic/amd64/libs/libseccomp/20190211_095659_0b835@/log.gz - build time tests https://launchpadlibrarian.net/410848161/buildlog_ubuntu-bionic-amd64.libseccomp_2.3.1-2.1ubuntu5~ppa2_BUILDING.txt.gz ** Changed in: libseccomp (Ubuntu Bionic) Assignee: (unassigned) => Christian Ehrhardt (paelzer) ** Changed in: libseccomp (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1815415 Title: please update libseccomp for newer kernel syscalls Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Bionic: In Progress Status in libseccomp source package in Cosmic: Fix Released Bug description: [Impact] * The libseccomp library provides an easy to use, platform independent, interface to the Linux Kernel's syscall filtering mechanism. But it can only "control" those syscalls it knows about. Therefore staying up to date with newer kernels is a requirement to be fully funcitonal. * At the time 18.04 was released with the 4.15 kernel the new definitions were not yet released for libseccomp - lets fix this mismatch by backporting the new syscall definitions [2][3][4]. [Test Case] * Note: a lot of this is kernel dependent it should work with the intended SRU target of Bionic with kernel 4.15 or 4.18, but be careful to run it there (e.g. not a LXD container on Xenials 4.4 kernel) * we modify the already existing autopkgtest for this SRU verification # Prep $ apt install ubuntu-dev-tools build-essential linux-libc-dev libseccomp-dev libseccomp2 seccomp $ pull-lp-source libseccomp bionic $ cd libseccomp-2.3.1 $ export ADTTMP=$(mktemp -d); echo $ADTTMP # run original tests as-is (should pass/fail as expected) $ ./debian/tests/test-filter # add new syscalls of this SRU $ cp debian/tests/data/safe.filter debian/tests/data/newcodes.filter $ printf "preadv2\npwritev2\npkey_mprotect\npkey_alloc\npkey_free\nget_tls\ns390_guarded_storage\ns390_sthyi\n" >> debian/tests/data/newcodes.filter # remove unknown calls (x86 4.18 kernel) sed -i -e '/^_exit$/d' -e '/^fstatvfs$/d' -e '/^llseek$/d' -e '/^pread$/d' -e '/^pselect$/d' -e '/^pwrite$/d' -e '/^sigtimedwait$/d' -e '/^sigwaitinfo$/d' -e '/^statvfs$/d' debian/tests/data/newcodes.filter # make unknown call a fail $ sed -i -e '111s/continue;/{fprintf(stderr, "failed to find %s\\n",buf);rc = -1;goto out;}/' debian/tests/src/test-seccomp.c # run this special test and check return value ${ADTTMP}/exe ./debian/tests/data/newcodes.filter /bin/date; echo $? Without the fix it will fail like: DEBUG: seccomp_load_filters ./debian/tests/data/newcodes.filter failed to find preadv2 seccomp_load_filters failed with -1 1 But with the fix applied those new calls will work: DEBUG: seccomp_load_filters ./debian/tests/data/newcodes.filter Tue Feb 12 07:41:05 UTC 2019 0 [Regression Potential] * This isn't adding new active code like functions, but only extending the definitions of per-arch syscall numbers to be aware of the newer syscalls that were added in the kernel. Therefore no old use-cases should regress (they are not touched). The only change in behavior for an SRU POV would be that things that got denied so far (e.g. if you tried to set such a new syscall through libseccomp) was denied before and would now work. I think that is exactly the intention of the SRU and not a regression. [Other Info] * Requested while security reviewing an libseccomp SRU to have one update for both [1]. * we also missed the former update for kernel 4.9 [3] AND 4.10 [4] as the official releases of the lib are rather seldom. * In general there already are build time tests and autopkgtests in the package already. So coverage of "old calls" for regressions is already good. --- This came up while working on bug 1755250 which asked for statx. But on the review of that it was pointed out [1] that it would be great to support further new kernel syscall defines - this isn't even looking at HWE kernels for Bionic, but "just" adding those which are there for the 4.15 kernel Bionic was released with. With the HWE kernels in mind there would be even more one might want to add, but there is no newer such update in the upstream repo yet. [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/libseccomp/+git/libseccomp/+merge/362906/comments/944418 [2]: https://github.com/seccomp/libseccomp/commit/c842c2f6c203ad9da37ca60219172aa0be68d26a [3]: https://github.com/seccomp/libseccomp/commit
[Touch-packages] [Bug 1815415] Re: please update libseccomp for newer kernel syscalls
All pre-checks and tests complete, and uploaded to the SRU review queue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1815415 Title: please update libseccomp for newer kernel syscalls Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Bionic: In Progress Status in libseccomp source package in Cosmic: Fix Released Bug description: [Impact] * The libseccomp library provides an easy to use, platform independent, interface to the Linux Kernel's syscall filtering mechanism. But it can only "control" those syscalls it knows about. Therefore staying up to date with newer kernels is a requirement to be fully funcitonal. * At the time 18.04 was released with the 4.15 kernel the new definitions were not yet released for libseccomp - lets fix this mismatch by backporting the new syscall definitions [2][3][4]. [Test Case] * Note: a lot of this is kernel dependent it should work with the intended SRU target of Bionic with kernel 4.15 or 4.18, but be careful to run it there (e.g. not a LXD container on Xenials 4.4 kernel) * we modify the already existing autopkgtest for this SRU verification # Prep $ apt install ubuntu-dev-tools build-essential linux-libc-dev libseccomp-dev libseccomp2 seccomp $ pull-lp-source libseccomp bionic $ cd libseccomp-2.3.1 $ export ADTTMP=$(mktemp -d); echo $ADTTMP # run original tests as-is (should pass/fail as expected) $ ./debian/tests/test-filter # add new syscalls of this SRU $ cp debian/tests/data/safe.filter debian/tests/data/newcodes.filter $ printf "preadv2\npwritev2\npkey_mprotect\npkey_alloc\npkey_free\nget_tls\ns390_guarded_storage\ns390_sthyi\n" >> debian/tests/data/newcodes.filter # remove unknown calls (x86 4.18 kernel) sed -i -e '/^_exit$/d' -e '/^fstatvfs$/d' -e '/^llseek$/d' -e '/^pread$/d' -e '/^pselect$/d' -e '/^pwrite$/d' -e '/^sigtimedwait$/d' -e '/^sigwaitinfo$/d' -e '/^statvfs$/d' debian/tests/data/newcodes.filter # make unknown call a fail $ sed -i -e '111s/continue;/{fprintf(stderr, "failed to find %s\\n",buf);rc = -1;goto out;}/' debian/tests/src/test-seccomp.c # run this special test and check return value ${ADTTMP}/exe ./debian/tests/data/newcodes.filter /bin/date; echo $? Without the fix it will fail like: DEBUG: seccomp_load_filters ./debian/tests/data/newcodes.filter failed to find preadv2 seccomp_load_filters failed with -1 1 But with the fix applied those new calls will work: DEBUG: seccomp_load_filters ./debian/tests/data/newcodes.filter Tue Feb 12 07:41:05 UTC 2019 0 [Regression Potential] * This isn't adding new active code like functions, but only extending the definitions of per-arch syscall numbers to be aware of the newer syscalls that were added in the kernel. Therefore no old use-cases should regress (they are not touched). The only change in behavior for an SRU POV would be that things that got denied so far (e.g. if you tried to set such a new syscall through libseccomp) was denied before and would now work. I think that is exactly the intention of the SRU and not a regression. [Other Info] * Requested while security reviewing an libseccomp SRU to have one update for both [1]. * we also missed the former update for kernel 4.9 [3] AND 4.10 [4] as the official releases of the lib are rather seldom. * In general there already are build time tests and autopkgtests in the package already. So coverage of "old calls" for regressions is already good. --- This came up while working on bug 1755250 which asked for statx. But on the review of that it was pointed out [1] that it would be great to support further new kernel syscall defines - this isn't even looking at HWE kernels for Bionic, but "just" adding those which are there for the 4.15 kernel Bionic was released with. With the HWE kernels in mind there would be even more one might want to add, but there is no newer such update in the upstream repo yet. [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/libseccomp/+git/libseccomp/+merge/362906/comments/944418 [2]: https://github.com/seccomp/libseccomp/commit/c842c2f6c203ad9da37ca60219172aa0be68d26a [3]: https://github.com/seccomp/libseccomp/commit/d9102f12fd39bd77151a1f630fcfc8c80f86c55c [4]: https://github.com/seccomp/libseccomp/commit/116b3c1a2e1db53cc35b74f30c080f5265faa674 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1815415/+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 1815415] Re: please update libseccomp for newer kernel syscalls
Thanks for the reviews - I'll have to come up with some tests on my own then ... In general there already are build time tests and autopkgtests in the package. So coverage of "old calls" for regressions is already good. Fortunately the autopkgtests seem to be extendable for an explicit verification of a few of the new calls. IMHO there is no need to modify the packages test as run on autopkgtest for these more rare calls - the are focused on use cases like snaps which they got added for. We need to: - add the new calls - make it fail on unknown calls (without it says "syscall not available on this arch/kernel - as this is a syscall whitelist its ok and the error can be ignored - remove some syscalls that never (or no more) exist(ed) that way Note: a lot of this is kernel dependent it should work with the intended SRU target of Bionic with kernel 4.15 or 4.18, but be careful to run it there (e.g. not a LXD container on Xenials 4.4 kernel) # Prep $ apt install ubuntu-dev-tools build-essential linux-libc-dev libseccomp-dev libseccomp2 seccomp $ pull-lp-source libseccomp bionic $ cd libseccomp-2.3.1 $ export ADTTMP=$(mktemp -d); echo $ADTTMP # run original tests as-is (should pass/fail as expected) $ ./debian/tests/test-filter # add new syscalls of this SRU $ cp debian/tests/data/safe.filter debian/tests/data/newcodes.filter $ printf "preadv2\npwritev2\npkey_mprotect\npkey_alloc\npkey_free\nget_tls\ns390_guarded_storage\ns390_sthyi\n" >> debian/tests/data/newcodes.filter # remove unknown calls (x86 4.18 kernel) sed -i -e '/^_exit$/d' -e '/^fstatvfs$/d' -e '/^llseek$/d' -e '/^pread$/d' -e '/^pselect$/d' -e '/^pwrite$/d' -e '/^sigtimedwait$/d' -e '/^sigwaitinfo$/d' -e '/^statvfs$/d' debian/tests/data/newcodes.filter # make unknown call a fail $ sed -i -e '111s/continue;/{fprintf(stderr, "failed to find %s\\n",buf);rc = -1;goto out;}/' debian/tests/src/test-seccomp.c # run this special test and check return value ${ADTTMP}/exe ./debian/tests/data/newcodes.filter /bin/date; echo $? Without the fix it will fail like: DEBUG: seccomp_load_filters ./debian/tests/data/newcodes.filter failed to find preadv2 seccomp_load_filters failed with -1 1 But with the fix applied those new calls will work: DEBUG: seccomp_load_filters ./debian/tests/data/newcodes.filter Tue Feb 12 07:41:05 UTC 2019 0 Tested on the PPA builds and working - adding these as SRU test & verification steps ** Description changed: [Impact] * The libseccomp library provides an easy to use, platform independent, interface to the Linux Kernel's syscall filtering mechanism. But it can only "control" those syscalls it knows about. Therefore staying up to date with newer kernels is a requirement to be fully funcitonal. * At the time 18.04 was released with the 4.15 kernel the new definitions were not yet released for libseccomp - lets fix this mismatch by backporting the new syscall definitions [2][3][4]. [Test Case] - * TODO + * Note: a lot of this is kernel dependent it should work with the + intended SRU target of Bionic with kernel 4.15 or 4.18, but be careful + to run it there (e.g. not a LXD container on Xenials 4.4 kernel) + + * we modify the already existing autopkgtest for this SRU verification + + # Prep + $ apt install ubuntu-dev-tools build-essential linux-libc-dev libseccomp-dev libseccomp2 seccomp + $ pull-lp-source libseccomp bionic + $ cd libseccomp-2.3.1 + $ export ADTTMP=$(mktemp -d); echo $ADTTMP + # run original tests as-is (should pass/fail as expected) + $ ./debian/tests/test-filter + # add new syscalls of this SRU + $ cp debian/tests/data/safe.filter debian/tests/data/newcodes.filter + $ printf "preadv2\npwritev2\npkey_mprotect\npkey_alloc\npkey_free\nget_tls\ns390_guarded_storage\ns390_sthyi\n" >> debian/tests/data/newcodes.filter + # remove unknown calls (x86 4.18 kernel) + sed -i -e '/^_exit$/d' -e '/^fstatvfs$/d' -e '/^llseek$/d' -e '/^pread$/d' -e '/^pselect$/d' -e '/^pwrite$/d' -e '/^sigtimedwait$/d' -e '/^sigwaitinfo$/d' -e '/^statvfs$/d' debian/tests/data/newcodes.filter + # make unknown call a fail + $ sed -i -e '111s/continue;/{fprintf(stderr, "failed to find %s\\n",buf);rc = -1;goto out;}/' debian/tests/src/test-seccomp.c + # run this special test and check return value + ${ADTTMP}/exe ./debian/tests/data/newcodes.filter /bin/date; echo $? + + Without the fix it will fail like: + DEBUG: seccomp_load_filters ./debian/tests/data/newcodes.filter + failed to find preadv2 + seccomp_load_filters failed with -1 + 1 + + But with the fix applied those new calls will work: + DEBUG: seccomp_load_filters ./debian/tests/data/newcodes.filter + Tue Feb 12 07:41:05 UTC 2019 + 0 + [Regression Potential] * This isn't adding new active code like functions, but only extending the definitions of per-arch syscall numbers to be aware of the newer syscalls that were added in the kernel. Therefore no old use-cases should regress (they are not