[Touch-packages] [Bug 1798212] Re: systemd stuck in uninterruptible sleep state
4.15.0-43-generic #46~16.04.1-Ubuntu SMP x86_64 I have the same problem but the process that gets stuck is dockerd not systemd. 3,2077,80354225063,-;INFO: task dockerd:2070 blocked for more than 120 seconds. 3,2078,80354230430,-; Tainted: P O 4.15.0-43-generic #46~16.04.1-Ubuntu 3,2079,80354236566,-;"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 6,2080,80354242978,-;dockerd D0 2070 1 0x 4,2081,80354242981,-;Call Trace: 4,2082,80354242984,-; __schedule+0x3d6/0x8b0 4,2083,80354242986,-; ? xen_smp_send_reschedule+0x10/0x20 4,2084,80354242989,-; schedule+0x36/0x80 4,2085,80354242991,-; schedule_timeout+0x1db/0x370 4,2086,80354242993,-; ? try_to_wake_up+0x59/0x4a0 4,2087,80354242995,-; wait_for_completion+0xb4/0x140 4,2088,80354242996,-; ? wake_up_q+0x70/0x70 4,2089,80354242998,-; flush_work+0x129/0x1e0 4,2090,80354242999,-; ? worker_detach_from_pool+0xb0/0xb0 4,2091,80354243001,-; flush_delayed_work+0x3f/0x50 4,2092,80354243004,-; fsnotify_wait_marks_destroyed+0x15/0x20 4,2093,80354243005,-; fsnotify_destroy_group+0x48/0xd0 4,2094,80354243008,-; inotify_release+0x1e/0x50 4,2095,80354243011,-; __fput+0xea/0x220 4,2096,80354243013,-; fput+0xe/0x10 4,2097,80354243014,-; task_work_run+0x8a/0xb0 4,2098,80354243016,-; exit_to_usermode_loop+0xc4/0xd0 4,2099,80354243018,-; do_syscall_64+0xf4/0x130 4,2100,80354243020,-; entry_SYSCALL_64_after_hwframe+0x3d/0xa2 The tainted marker is from zfs module since I have a ZFS partition mounted in the system. The / partition however is EXT4, and docker is running from /. cat /proc/1/stack [<0>] flush_work+0x129/0x1e0 [<0>] flush_delayed_work+0x3f/0x50 [<0>] fsnotify_wait_marks_destroyed+0x15/0x20 [<0>] fsnotify_destroy_group+0x48/0xd0 [<0>] inotify_release+0x1e/0x50 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x8a/0xb0 [<0>] exit_to_usermode_loop+0xc4/0xd0 [<0>] do_syscall_64+0xf4/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x 6,2111,218820611653,-; taskPC stack pid father 6,2112,218820614372,-;systemd D0 1 0 0x0004 4,2113,218820616975,-;Call Trace: 4,2114,218820618224,-; __schedule+0x3d6/0x8b0 4,2115,218820619977,-; ? xen_smp_send_reschedule+0x10/0x20 4,2116,218820622101,-; schedule+0x36/0x80 4,2117,218820624470,-; schedule_timeout+0x1db/0x370 4,2118,218820627660,-; ? delete_node+0x1a5/0x1f0 4,2119,218820630763,-; wait_for_completion+0xb4/0x140 4,2120,218820634184,-; ? wake_up_q+0x70/0x70 4,2121,218820638148,-; flush_work+0x129/0x1e0 4,2122,218820642490,-; ? worker_detach_from_pool+0xb0/0xb0 4,2123,218820646706,-; flush_delayed_work+0x3f/0x50 4,2124,218820650474,-; fsnotify_wait_marks_destroyed+0x15/0x20 4,2125,218820654789,-; fsnotify_destroy_group+0x48/0xd0 4,2126,218820658838,-; inotify_release+0x1e/0x50 4,2127,218820662400,-; __fput+0xea/0x220 4,2128,218820665486,-; fput+0xe/0x10 4,2129,218820668890,-; task_work_run+0x8a/0xb0 4,2130,218820672633,-; exit_to_usermode_loop+0xc4/0xd0 4,2131,218820676852,-; do_syscall_64+0xf4/0x130 4,2132,218820680778,-; entry_SYSCALL_64_after_hwframe+0x3d/0xa2 4,2133,218820686587,-;RIP: 0033:0x7efd22aaf57d 4,2134,218820691555,-;RSP: 002b:7ffd463e6070 EFLAGS: 0293 ORIG_RAX: 0003 4,2135,218820699907,-;RAX: RBX: 000d RCX: 7efd22aaf57d 4,2136,218820708355,-;RDX: RSI: RDI: 000d 4,2137,218820717053,-;RBP: 7efd241ea708 R08: 5559085084d0 R09: 0001 4,2138,218820726163,-;R10: R11: 0293 R12: 0002 4,2139,218820734459,-;R13: 55590749d580 R14: 5559084bd9b8 R15: 55590749e9c0 Also kworker shows a stack at some point. 3,1861,80233315906,-;INFO: task kworker/u30:3:5705 blocked for more than 120 seconds. 3,1862,80233321444,-; Tainted: P O 4.15.0-43-generic #46~16.04.1-Ubuntu 3,1863,80233327648,-;"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 6,1864,8023902,-;kworker/u30:3 D0 5705 2 0x8000 6,1865,8023909,-;Workqueue: events_unbound fsnotify_mark_destroy_workfn 4,1866,8023910,-;Call Trace: 4,1867,8023914,-; __schedule+0x3d6/0x8b0 4,1868,8023918,-; schedule+0x36/0x80 4,1869,8023920,-; schedule_timeout+0x1db/0x370 4,1870,8023927,-; ? __enqueue_entity+0x5c/0x60 4,1871,8023932,-; ? enqueue_entity+0x112/0x670 4,1872,8023937,-; wait_for_completion+0xb4/0x140 4,1873,8023939,-; ? wake_up_q+0x70/0x70 4,1874,8023944,-; __synchronize_srcu.part.13+0x85/0xb0 4,1875,8023947,-; ? trace_raw_output_rcu_utilization+0x50/0x50 4,1876,8023950,-; synchronize_srcu+0xd3/0xe0 4,1877,8023956,-; ? synchronize_srcu+0xd3/0xe0 4,1878,8023962,-; fsnotify_mark_destroy_workfn+0x7c/0xe0 4,1879,8023966,-; process_one_work+0x14d/0x410 4,1880,8023968,-; worker_thread+0x22b/0x460 4,1881,8023971,-; k
[Touch-packages] [Bug 1811706] Re: eval: en: not found
bump -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1811706 Title: eval: en: not found Status in console-setup package in Ubuntu: New Bug description: I tried to create a minimal Ubuntu bionic arm64 installation using debootstrap that I would use to create a bootable Kubuntu 18.04 image for the Pi 3, but debootstrap seems to fail to configure keyboard- configuration, and therefore fails to install the Ubuntu base. Looking into the debootstrap logs, I get the error "eval: en: not found". I've searched Google for solutions but found nothing relevant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1811706/+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 1792978] Re: initscript avahi-daemon, action "start" failed
In the previous package removal, we are seeing: [10.244.40.30] out: Purging configuration files for avahi-daemon (0.7-3.1ubuntu1.1) ... [10.244.40.30] out: rmdir: failed to remove '/var/run/avahi-daemon': Directory not empty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1792978 Title: initscript avahi-daemon, action "start" failed Status in avahi package in Ubuntu: New Bug description: When installing maas-region-controller, avahi-deamon failed to install because it was it seemed to already be running. $ apt-get -q install -y maas-region-controller [1invoke-rc.d: initscript avahi-daemon, action "start" failed. [0;1;31m●[0m avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: [0;1;31mfailed[0m (Result: exit-code) since Sat 2018-09-15 19:42:29 UTC; 9ms ago Process: 22726 ExecStart=/usr/sbin/avahi-daemon -s [0;1;31m(code=exited, status=255)[0m Main PID: 22726 (code=exited, status=255) Sep 15 19:42:29 leafeon systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Sep 15 19:42:29 leafeon avahi-daemon[22726]: Daemon already running on PID 21868 Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Main process exit.../a[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;31mFailed to start Avahi mDNS/DNS-SD Stack.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Unit entered fail...e.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Failed with resul...'.[0m Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package avahi-daemon (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of avahi-utils: avahi-utils depends on avahi-daemon; however: Package avahi-daemon is not configured yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1792978/+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 1813333] Re: Battery Indicator on Bay Trail / Cherry Trail laptop
** Package changed: ubuntu => niop ** Also affects: batt-stat Importance: Undecided Status: New ** Also affects: battery-status Importance: Undecided Status: New ** Also affects: upower (Ubuntu) Importance: Undecided Status: New ** Also affects: acpi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Battery Indicator on Bay Trail / Cherry Trail laptop Status in battery-status: New Status in Battery Status: New Status in Custom Kernels for Netbooks ( Atom Processor ) : New Status in acpi package in Ubuntu: New Status in upower package in Ubuntu: New Bug description: Ubuntu/Kubuntu missing power management on laptop with bay Trail or cherry trail. Tested on HP X2 Detachable model 10-p028nl CPU x5-83xx on Ubuntu 16.04 and Kubuntu 18.04 the battery icon doesn't show info about remaining power. Tried kernel 4.15.x and 4.20.3 no success. upower -d doesn't show the battery. It works correctly on Fedora 29 kernel 4.18.x It could be some patches missing on APX20x, APX288 module. After other searches it could be some kernel configuration option To manage notifications about this bug go to: https://bugs.launchpad.net/batt-stat/+bug/181/+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 1798562] Re: After a side by side installation, resized filesystem is corrupted
** Tags added: id-5c49e9dab8b59b7d3bbca789 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1798562 Title: After a side by side installation, resized filesystem is corrupted Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Bionic: Fix Committed Status in e2fsprogs source package in Cosmic: Fix Committed Bug description: [Impact] - Users resizing filesystems using resize2fs. - Resizing an existing Linux filesystem from the Ubuntu installer. [Test cases] Test Case 1: With e2fsprogs 1.44.4-2: Download this file system image: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz Run the following commands: bunzip2 vda1b.qcow2.bz qemu-img convert vda1b.qcow2 vda1b.raw e2fsck -f vda1b.raw resize2fs vda1b.raw 6200M e2fsck -f vda1b.raw e2fsck 1.44.4 (18-Aug-2018) Pass 1: Checking inodes, blocks, and sizes Inode 45746 extent block passes checks, but checksum does not match extent (logical block 1272, physical block 466167, len 776) Fix? Test Case 2 (Use case of the installer): 1. Perform a first installation of Ubuntu 2. Reboot into the freshly installed system and verify everything works as expected 3. Do a second installation and select "Install alonogside". Keep the size proposed by the installer and proceed to the end of installation 4. Reboot 5. On boot, in the list of installed systems, select the first system installed on the machine 6. Verify that it boots, you can login and it works as expected Actual Result The FS is corrupted and depending on the corruption it goes to initramfs, boots but cannot login, ... [Regression potential] This changes behavior in the update logic for extent blocks; as such, care should be taken to make sure that testing takes into account the possibility to introduce filesystem corruption while resizing. This is why the test cases include running e2fsck as last step. --- Attached is the journal of the system installed on the corrupted partition. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) 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 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 10:53:57 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- InstallationDate: Installed on 2018-10-18 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+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 1754075] Re: apt-setup uses apt-key but probably should not anymore
** Tags added: id-5c4b9a39fe71d33a8db94ec3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1730004] [NEW] Sound system(alsa) fails on resume from suspend
You have been subscribed to a public bug: Desktop system audio failure upon resume from suspend. Event occurs approx. 50% of time and can be remedied with sudo alsa reload. Firefox is program where problem is first noted but no sound from any source is working. Using GUI for sound setting will not correct problem. KDE Plasma 5.5.5 Kernel 4.10.0-38-generic alsa-utils: Installed: 1.1.0-0ubuntu5 Candidate: 1.1.0-0ubuntu5 Version table: *** 1.1.0-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 56.0+build6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rob1489 F pulseaudio /dev/snd/controlC0: rob1489 F pulseaudio BuildID: 20171003101344 Channel: Unavailable CurrentDesktop: KDE Date: Fri Nov 3 15:50:31 2017 EcryptfsInUse: Yes ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-23 (11 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev enp5s0 proto static metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.117 metric 100 IwConfig: lono wireless extensions. enp5s0no wireless extensions. Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-e9b04fab-94a4-41d4-a32c-b6f0a1171023 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=56.0/20171003101344 (In use) RfKill: 5: hci0: Bluetooth Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09KPNV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd10/30/2011:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T3500 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- Sound system(alsa) fails on resume from suspend https://bugs.launchpad.net/bugs/1730004 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1730004] Re: Sound system(alsa) fails on resume from suspend
** Package changed: firefox (Ubuntu) => alsa-driver (Ubuntu) -- 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/1730004 Title: Sound system(alsa) fails on resume from suspend Status in alsa-driver package in Ubuntu: New Bug description: Desktop system audio failure upon resume from suspend. Event occurs approx. 50% of time and can be remedied with sudo alsa reload. Firefox is program where problem is first noted but no sound from any source is working. Using GUI for sound setting will not correct problem. KDE Plasma 5.5.5 Kernel 4.10.0-38-generic alsa-utils: Installed: 1.1.0-0ubuntu5 Candidate: 1.1.0-0ubuntu5 Version table: *** 1.1.0-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 56.0+build6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rob1489 F pulseaudio /dev/snd/controlC0: rob1489 F pulseaudio BuildID: 20171003101344 Channel: Unavailable CurrentDesktop: KDE Date: Fri Nov 3 15:50:31 2017 EcryptfsInUse: Yes ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-23 (11 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev enp5s0 proto static metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.117 metric 100 IwConfig: lono wireless extensions. enp5s0no wireless extensions. Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-e9b04fab-94a4-41d4-a32c-b6f0a1171023 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=56.0/20171003101344 (In use) RfKill: 5: hci0: Bluetooth Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09KPNV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd10/30/2011:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T3500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1730004/+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 1813400] [NEW] systemctl doesn't respect --dry-run
Public bug reported: [Expected behaviour] When I use the --dry-run flag with systemctl, I would expect it not to take any action, but instead print what it is going to do. [Actual behaviour] Passing --dry-run doesn't affect the behaviour of systemctl. [Test case] $ systemctl --dry-run reboot Ubuntu version: 18.04.1 systemd version: 237-3ubuntu10.11 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1813400 Title: systemctl doesn't respect --dry-run Status in systemd package in Ubuntu: New Bug description: [Expected behaviour] When I use the --dry-run flag with systemctl, I would expect it not to take any action, but instead print what it is going to do. [Actual behaviour] Passing --dry-run doesn't affect the behaviour of systemctl. [Test case] $ systemctl --dry-run reboot Ubuntu version: 18.04.1 systemd version: 237-3ubuntu10.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813400/+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 1813075] [NEW] Line Out audio output rapidly disapears and reappears
You have been subscribed to a public bug: Today my audio became choppy. At first I thought it was a bad audio file, but it turned out that everything I play is choppy. Then I thought that some process is clogging the CPU or IO, but it wasn't that either. After some searching, I opened sound settings and found out that Line Out audio output is rapidly disappearing and reappearing from the list. I checked the alsamixer and same thing was happening in its window. I tried to restart the computer, and the problem disappeared only to come back again after a short time. I still have my old 14.04 installation, I rebooted to that and everything worked as it should. I have never seen anything like this, I have no clue what is happening and I have no idea what to check. dmesg output showed nothing related to sound. Since it is very unusual, I have attached a video of what is going on. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Line Out audio output rapidly disapears and reappears https://bugs.launchpad.net/bugs/1813075 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813403] [NEW] Better kernel core dump defaults
Public bug reported: Currently, `$ sysctl kernel.core_pattern` gives `kernel.core_pattern = |/usr/share/apport/apport %p %s %c %d %P` This should be considered a bug, since a minimal version of ubuntu or even debian, and more notoriously when run from containers, this will just error out, with no core dump being produced, due to the absence of apport. Adding to the problem, is with container where you can't just change it per container, and should be changed from the host. I think using apport (a non essential package) as a default without thought as to it's absence is not robust design. There are multiple options to deal with this: 1. Drop apport as default and switch to a simple file in either /var/crash (this requires creating /var/crash as a part of the installation), or /tmp 2. Switch to systemd-coredump, and default to it, since it already does this very well and provides "coredumpctl" which is much nicer to work with. systemd-coredump also is a part of the systemd suite of utils and doesn't pull in a larger dependency as apport -- which to date, isn't as robust (I still have "core" files being left all over the place by apport, mostly in my home folder). This also has a nice advantage of unifying the OSS community in terms of coredump handler. 3. Employ a tiny helper script, as the default core dump handler, which looks for specified programs such as "apport", "abrt", systemd-coredump" and pipes to them, or pipes it to /var/crash, or /tmp during it's absence. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: procps 2:3.3.15-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 26 20:33:55 2019 InstallationDate: Installed on 2019-01-01 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: procps UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-01-15T04:51:59.517661 ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1813403 Title: Better kernel core dump defaults Status in procps package in Ubuntu: New Bug description: Currently, `$ sysctl kernel.core_pattern` gives `kernel.core_pattern = |/usr/share/apport/apport %p %s %c %d %P` This should be considered a bug, since a minimal version of ubuntu or even debian, and more notoriously when run from containers, this will just error out, with no core dump being produced, due to the absence of apport. Adding to the problem, is with container where you can't just change it per container, and should be changed from the host. I think using apport (a non essential package) as a default without thought as to it's absence is not robust design. There are multiple options to deal with this: 1. Drop apport as default and switch to a simple file in either /var/crash (this requires creating /var/crash as a part of the installation), or /tmp 2. Switch to systemd-coredump, and default to it, since it already does this very well and provides "coredumpctl" which is much nicer to work with. systemd-coredump also is a part of the systemd suite of utils and doesn't pull in a larger dependency as apport -- which to date, isn't as robust (I still have "core" files being left all over the place by apport, mostly in my home folder). This also has a nice advantage of unifying the OSS community in terms of coredump handler. 3. Employ a tiny helper script, as the default core dump handler, which looks for specified programs such as "apport", "abrt", systemd-coredump" and pipes to them, or pipes it to /var/crash, or /tmp during it's absence. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: procps 2:3.3.15-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 26 20:33:55 2019 InstallationDate: Installed on 2019-01-01 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: procps UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-01-15T04:51:59.517661 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1813403/+subscriptions -- Mailing list: https://launchpad.net/~tou
[Touch-packages] [Bug 1813075] Re: Line Out audio output rapidly disapears and reappears
I changed the bug report to alsa-driver, as it affects PulseAudio and ALSA, but I'm not sure if it is the right choice. ** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1813075 Title: Line Out audio output rapidly disapears and reappears Status in alsa-driver package in Ubuntu: New Bug description: Today my audio became choppy. At first I thought it was a bad audio file, but it turned out that everything I play is choppy. Then I thought that some process is clogging the CPU or IO, but it wasn't that either. After some searching, I opened sound settings and found out that Line Out audio output is rapidly disappearing and reappearing from the list. I checked the alsamixer and same thing was happening in its window. I tried to restart the computer, and the problem disappeared only to come back again after a short time. I still have my old 14.04 installation, I rebooted to that and everything worked as it should. I have never seen anything like this, I have no clue what is happening and I have no idea what to check. dmesg output showed nothing related to sound. Since it is very unusual, I have attached a video of what is going on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813075/+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 1813408] [NEW] package systemd 237-3ubuntu10.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Public bug reported: Attempting upgrade from 16.04 LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 237-3ubuntu10.11 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: systemd: Configure initramfs-tools: Configure libnss-systemd: Configure libpam-systemd: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jan 26 07:52:16 2019 DpkgTerminalLog: Setting up systemd (237-3ubuntu10.11) ... systemd-machine-id-setup: error while loading shared libraries: libcryptsetup.so.12: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): subprocess installed post-installation script returned error exit status 127 Setting up initramfs-tools (0.130ubuntu3.6) ... DuplicateSignature: package:systemd:237-3ubuntu10.11 Setting up systemd (237-3ubuntu10.11) ... systemd-machine-id-setup: error while loading shared libraries: libcryptsetup.so.12: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-09-15 (863 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) Lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: lspci: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /lib/x86_64-linux-gnu/libudev.so.1) Lsusb: Error: command ['lsusb'] failed with exit code 1: lsusb: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /lib/x86_64-linux-gnu/libudev.so.1) MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-127-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: systemd SystemdDelta: Error: command ['systemd-delta'] failed with exit code 127: systemd-delta: error while loading shared libraries: libcryptsetup.so.12: cannot open shared object file: No such file or directory SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 127: systemctl: error while loading shared libraries: libcryptsetup.so.12: cannot open shared object file: No such file or directory Title: package systemd 237-3ubuntu10.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UdevDb: Error: command ['udevadm', 'info', '--export-db'] failed with exit code 1: udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by udevadm) udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found (required by udevadm) udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /lib/x86_64-linux-gnu/libblkid.so.1) udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /lib/x86_64-linux-gnu/libuuid.so.1) UpgradeStatus: Upgraded to xenial on 2019-01-26 (0 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. modified.conffile..etc.dhcp.dhclient-enter-hooks.d.resolved: [deleted] mtime.conffile..etc.pam.d.systemd-user: 2016-04-12T03:34:03 mtime.conffile..etc.systemd.journald.conf: 2016-04-12T03:34:03 mtime.conffile..etc.systemd.logind.conf: 2016-04-12T03:34:03 mtime.conffile..etc.systemd.resolved.conf: 2016-04-12T03:34:04 mtime.conffile..etc.systemd.system.conf: 2016-09-07T02:32:47 mtime.conffile..etc.systemd.timesyncd.conf: 2016-04-12T03:34:04 mtime.conffile..etc.systemd.user.conf: 2016-04-12T03:34:03 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1813408 Title: package systemd 237-3ubuntu10.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in systemd package in Ubuntu: New Bug description: Attempting upgrade from 16.04 LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 237-3ubuntu10.11 ProcVersionSignatu
[Touch-packages] [Bug 1813408] Re: package systemd 237-3ubuntu10.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
** Tags removed: need-duplicate-check -- 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/1813408 Title: package systemd 237-3ubuntu10.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in systemd package in Ubuntu: New Bug description: Attempting upgrade from 16.04 LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 237-3ubuntu10.11 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: systemd: Configure initramfs-tools: Configure libnss-systemd: Configure libpam-systemd: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jan 26 07:52:16 2019 DpkgTerminalLog: Setting up systemd (237-3ubuntu10.11) ... systemd-machine-id-setup: error while loading shared libraries: libcryptsetup.so.12: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): subprocess installed post-installation script returned error exit status 127 Setting up initramfs-tools (0.130ubuntu3.6) ... DuplicateSignature: package:systemd:237-3ubuntu10.11 Setting up systemd (237-3ubuntu10.11) ... systemd-machine-id-setup: error while loading shared libraries: libcryptsetup.so.12: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-09-15 (863 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) Lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: lspci: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /lib/x86_64-linux-gnu/libudev.so.1) Lsusb: Error: command ['lsusb'] failed with exit code 1: lsusb: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /lib/x86_64-linux-gnu/libudev.so.1) MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-127-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: systemd SystemdDelta: Error: command ['systemd-delta'] failed with exit code 127: systemd-delta: error while loading shared libraries: libcryptsetup.so.12: cannot open shared object file: No such file or directory SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 127: systemctl: error while loading shared libraries: libcryptsetup.so.12: cannot open shared object file: No such file or directory Title: package systemd 237-3ubuntu10.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UdevDb: Error: command ['udevadm', 'info', '--export-db'] failed with exit code 1: udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by udevadm) udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found (required by udevadm) udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /lib/x86_64-linux-gnu/libblkid.so.1) udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /lib/x86_64-linux-gnu/libuuid.so.1) UpgradeStatus: Upgraded to xenial on 2019-01-26 (0 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. modified.conffile..etc.dhcp.dhclient-enter-hooks.d.resolved: [deleted] mtime.conffile..etc.pam.d.systemd-user: 2016-04-12T03:34:03 mtime.conffile..etc.systemd.journald.conf: 2016-04-12T03:34:03 mtime.conffile..etc.systemd.logind.conf: 2016-04-12T03:34:03 mtime.conffile..etc.systemd.resolved.conf: 2016-04-12T03:34:04 mtime.conffile..etc.systemd.system.conf: 2016-09-07T02:32:47 mtime.conffile..etc.systemd.timesyncd.conf: 2016-04-12T03:34:04 mtime.conffile..etc.systemd.user.conf: 2016-04-12T03:34:03 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/181340
[Touch-packages] [Bug 1813400] Re: systemctl doesn't respect --dry-run
h -- 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/1813400 Title: systemctl doesn't respect --dry-run Status in systemd package in Ubuntu: New Bug description: [Expected behaviour] When I use the --dry-run flag with systemctl, I would expect it not to take any action, but instead print what it is going to do. [Actual behaviour] Passing --dry-run doesn't affect the behaviour of systemctl. [Test case] $ systemctl --dry-run reboot Ubuntu version: 18.04.1 systemd version: 237-3ubuntu10.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813400/+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 1671975] Re: i915 GPU hang consistently
*** This bug is a duplicate of bug 1660619 *** https://bugs.launchpad.net/bugs/1660619 For anyone else still experiencing this, I've opened up a new bug for the current version of Ubuntu at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1813423 If this bug still affects you, please go and click "This bug affects me", too over at the bug report. -- 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/1671975 Title: i915 GPU hang consistently Status in xorg package in Ubuntu: Confirmed Bug description: [122640.044864] thinkpad_ec: thinkpad_ec_request_row: arg0 rejected: (0x01:0x00)->0x00 [122640.044869] thinkpad_ec: thinkpad_ec_read_row: failed requesting row: (0x01:0x00)->0xfffb [122640.044872] thinkpad_ec: initial ec test failed [122640.122664] thinkpad_acpi: EC reports that Thermal Table has changed [122647.489239] usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd [122647.507393] usb 2-3: New USB device found, idVendor=18d1, idProduct=4ee2 [122647.507406] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [122647.507413] usb 2-3: Product: Pixel [122647.507419] usb 2-3: Manufacturer: Google [122647.507425] usb 2-3: SerialNumber: FA68H0304817 [122647.509395] usb 2-3: Enable of device-initiated U1 failed. [122647.509790] usb 2-3: Enable of device-initiated U2 failed. [124521.948736] [drm] stuck on render ring [124521.949487] [drm] GPU HANG: ecode 9:0:0x84d8, in Xorg [3132], reason: Engine(s) hung, action: reset [124521.952321] drm/i915: Resetting chip after gpu hang [124523.936544] [drm] RC6 on [124531.947819] [drm] stuck on render ring [124531.948595] [drm] GPU HANG: ecode 9:0:0x84d8, in Xorg [3132], reason: Engine(s) hung, action: reset [124531.948834] [drm:i915_set_reset_status [i915_bpo]] *ERROR* gpu hanging too fast, banning! [124531.951107] drm/i915: Resetting chip after gpu hang [124533.936064] [drm] RC6 on [126108.373960] [drm:intel_pipe_update_end [i915_bpo]] *ERROR* Atomic update failure on pipe B (start=729158 end=729159) time 167 us, min 1073, max 1079, scanline start 1070, end 1081 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Mar 10 16:34:49 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:504a] InstallationDate: Installed on 2016-08-10 (212 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: LENOVO 20F6CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic root=UUID=ed52c6b5-6141-4fca-958a-e7492664fd2f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET48W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW 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:bvrR02ET48W(1.21):bd06/01/2016:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20F6CTO1WW dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packa
[Touch-packages] [Bug 1660619] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B
For anyone else still experiencing this, I've opened up a new bug for the current version of Ubuntu at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1813423 If this bug still affects you, please go and click "This bug affects me", too over at the bug report. -- 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/1660619 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B Status in xorg package in Ubuntu: Invalid Bug description: I've a dual monitor setup and I'm running latest version of kubuntu. After a few days of uptime the desktop becomes so slow that I've to reboot it. In the log I find those errors, I don't know if they are related: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=150051 end=150052) time 110 us, min 1073, max 1079, scanline start 1072, end 1080 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Jan 31 14:06:17 2017 DistUpgraded: 2016-10-16 19:45:53,200 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 [1462:7978] InstallationDate: Installed on 2013-04-25 (1376 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: MSI MS-7978 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=f848f2e6-9d53-4c75-823a-fa97cfe10aa6 ro SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-10-16 (106 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.60 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnZ170AGAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Jan 28 11:57:37 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619/+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 1813423] [NEW] Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A"
Public bug reported: My system keeps freezing on a brand new install of Kubuntu 18.10, always with the kern.log error "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235) time 486 us, min 763, max 767, scanline start 760, end 783" I think it's probably a duplicate of these bugs which were closed unresolved: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was on an older version of Ubuntu) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because it was a duplicate of the first bug) It happens far more frequently if I have desktop effects turned on, and far less frequently when using a live USB key (at always happens eventually though. Usually once every few hours.) Please advise how I can help triage / test. My system is a new install now, so I'm perfectly willing to modify / reinstall to help testing (I've reinstalled 5 times to test things, but never managed to find a solution) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 26 14:19:52 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227a] InstallationDate: Installed on 2019-01-18 (8 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227A dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 14 Notebook PC dmi.product.sku: J9L01UA#ABL dmi.product.version: 096C110800405F1620180 dmi.sys.vendor: Hewlett-Packard 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 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic 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/1813423 Title: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A" Status in xorg package in Ubuntu: New Bug description: My system keeps freezing on a brand new install of Kubuntu 18.10, always with the kern.log error "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235) time 486 us, min 763, max 767, scanline start 760, end 783" I think it's probably a duplicate of these bugs which were closed unresolved: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was on an older version of Ubuntu) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because it was a duplicate of the first bug) It happens far more frequently if I have desktop effects turned on, and far less frequently when using a live USB key (at always happens eventually though. Usually once every few hours.) Please advise how I can help triage / test. My system is a new install now, so I'm pe
[Touch-packages] [Bug 1813423] Re: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A"
I have records of the last 5 kern.og / syslog / Xorg.log files from when it hung. When it does hang, the last thing visible on the screen stays there stationary, the cursor doesn't move and no keyboard inputs eg. alt+crtl+f2 / crtl+sysrq+RSEINUB, do nothing. -- 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/1813423 Title: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A" Status in xorg package in Ubuntu: New Bug description: My system keeps freezing on a brand new install of Kubuntu 18.10, always with the kern.log error "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235) time 486 us, min 763, max 767, scanline start 760, end 783" I think it's probably a duplicate of these bugs which were closed unresolved: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was on an older version of Ubuntu) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because it was a duplicate of the first bug) It happens far more frequently if I have desktop effects turned on, and far less frequently when using a live USB key (at always happens eventually though. Usually once every few hours.) Please advise how I can help triage / test. My system is a new install now, so I'm perfectly willing to modify / reinstall to help testing (I've reinstalled 5 times to test things, but never managed to find a solution) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 26 14:19:52 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227a] InstallationDate: Installed on 2019-01-18 (8 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227A dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 14 Notebook PC dmi.product.sku: J9L01UA#ABL dmi.product.version: 096C110800405F1620180 dmi.sys.vendor: Hewlett-Packard 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 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/1813423/+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 1813403] Re: Better kernel core dump defaults
** Description changed: Currently, `$ sysctl kernel.core_pattern` gives `kernel.core_pattern = |/usr/share/apport/apport %p %s %c %d %P` - This should be considered a bug, since a minimal version of ubuntu or - even debian, and more notoriously when run from containers, this will - just error out, with no core dump being produced, due to the absence of - apport. Adding to the problem, is with container where you can't just - change it per container, and should be changed from the host. I think - using apport (a non essential package) as a default without thought as - to it's absence is not robust design. + This should be considered a bug, since a minimal version of ubuntu + (server, core etc) and more notoriously when run from containers, this + will just error out, with no core dump being produced, due to the + absence of apport. Adding to the problem, is with container where you + can't just change it per container, and should be changed from the host. + I think using apport (a non essential package) as a default without + thought as to it's absence is not robust design. There are multiple options to deal with this: - 1. Drop apport as default and switch to a simple file in either /var/crash (this requires creating /var/crash as a part of the installation), or /tmp - 2. Switch to systemd-coredump, and default to it, since it already does this very well and provides "coredumpctl" which is much nicer to work with. systemd-coredump also is a part of the systemd suite of utils and doesn't pull in a larger dependency as apport -- which to date, isn't as robust (I still have "core" files being left all over the place by apport, mostly in my home folder). This also has a nice advantage of unifying the OSS community in terms of coredump handler. + 1. Drop apport as default and switch to a simple file in either /var/crash (this requires creating /var/crash as a part of the installation as it's currently created by apport), or /tmp + 2. Switch to systemd-coredump, and default to it, since it already does this very well and provides "coredumpctl" which is much nicer to work with. systemd-coredump also is a part of the systemd suite of utils and doesn't pull in a larger dependency as apport -- which to date, isn't as robust (I still have "core" files being left all over the place by apport, mostly in my home folder). This also has a nice advantage of unifying the OSS community in terms of coredump handler. 3. Employ a tiny helper script, as the default core dump handler, which looks for specified programs such as "apport", "abrt", systemd-coredump" and pipes to them, or pipes it to /var/crash, or /tmp during it's absence. + + And add a sysctl.d default rule here, or more cleanly a separate package + that does exactly this on option 3. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: procps 2:3.3.15-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 26 20:33:55 2019 InstallationDate: Installed on 2019-01-01 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: procps UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-01-15T04:51:59.517661 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1813403 Title: Better kernel core dump defaults Status in procps package in Ubuntu: New Bug description: Currently, `$ sysctl kernel.core_pattern` gives `kernel.core_pattern = |/usr/share/apport/apport %p %s %c %d %P` This should be considered a bug, since a minimal version of ubuntu (server, core etc) and more notoriously when run from containers, this will just error out, with no core dump being produced, due to the absence of apport. Adding to the problem, is with container where you can't just change it per container, and should be changed from the host. I think using apport (a non essential package) as a default without thought as to it's absence is not robust design. There are multiple options to deal with this: 1. Drop apport as default and switch to a simple file in either /var/crash (this requires creating /var/crash as a part of the installation as it's currently created by apport), or /tmp 2. Switch to systemd-coredump, and default to it, since it already does this very well and provides "coredumpctl" which is much nicer to work with. systemd-coredump also is a part of the systemd suite of utils and doesn't pull in a larger dependency as apport -- which to date, isn't as robust (I still have "core" fil
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Jurit (juritxyz) You need the following packages to downgrade systemd: libpam-systemd libsystemd0 systemd systemd-sysv you can get them from here https://launchpad.net/ubuntu/bionic/amd64/libpam-systemd/ https://launchpad.net/ubuntu/bionic/amd64/libsystemd0/ https://launchpad.net/ubuntu/bionic/amd64/systemd/ https://launchpad.net/ubuntu/bionic/amd64/systemd-sysv/ download the last working revision for all of them and install it. Afterwards the issue should be gone. However you have to set the four packages to hold with apt to ensure that they won't get updated ... to prevent issues until the problem gets resolved. As you said November update broke it, it would start with 237-3ubuntu10.8 and check if this solves it. You can also try a later revision but I assume this is good to go. -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+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 1789523] Re: The ssh-agent launcher script fails to relaunch ssh-agent
@kode54 Re: comment #5 The link gives 404 now!? https://gitlab.freedesktop.org/xorg/meta shows not issues at all. Probably they were moved but where? -- 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/1789523 Title: The ssh-agent launcher script fails to relaunch ssh-agent Status in xorg package in Ubuntu: Confirmed Bug description: There is an issue with the Xsession, in which logging out and logging back in again does not clear environment variables, so the ssh-agent script thinks that the agent is already running, and thus does not bother to start it again. I have altered the script, albeit in not the most pretty way, to detect if the agent is already running, and if not, force a restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 28 17:33:34 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installed anbox, 1, 4.15.0-33-generic, x86_64: installed nvidia, 396.54, 4.15.0-33-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2018-08-04 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7751 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash amdgpu.dc=0 mem=33554428k vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-GD65 (MS-7751) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.11:bd10/09/2013:svnMSI:pnMS-7751:pvr2.0:rvnMSI:rnZ77A-GD65(MS-7751):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7751 dmi.product.version: 2.0 dmi.sys.vendor: MSI mtime.conffile..etc.X11.Xsession.d.90x11-common_ssh-agent: 2018-08-28T17:23:14.025376 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1808281609.f3d90e8~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:18.3~git180816191500.b618d7e~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:18.3~git180816191500.b618d7e~b~padoka0 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.99+git1808290006.cba8fe4~b~padoka0 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1806121919.3d39506~b~padoka0 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/xorg/+bug/1789523/+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 1813403] Re: Better kernel core dump defaults
** Package changed: procps (Ubuntu) => ubuntu ** Description changed: Currently, `$ sysctl kernel.core_pattern` gives `kernel.core_pattern = |/usr/share/apport/apport %p %s %c %d %P` This should be considered a bug, since a minimal version of ubuntu (server, core etc) and more notoriously when run from containers, this will just error out, with no core dump being produced, due to the absence of apport. Adding to the problem, is with container where you can't just change it per container, and should be changed from the host. I think using apport (a non essential package) as a default without thought as to it's absence is not robust design. There are multiple options to deal with this: 1. Drop apport as default and switch to a simple file in either /var/crash (this requires creating /var/crash as a part of the installation as it's currently created by apport), or /tmp - 2. Switch to systemd-coredump, and default to it, since it already does this very well and provides "coredumpctl" which is much nicer to work with. systemd-coredump also is a part of the systemd suite of utils and doesn't pull in a larger dependency as apport -- which to date, isn't as robust (I still have "core" files being left all over the place by apport, mostly in my home folder). This also has a nice advantage of unifying the OSS community in terms of coredump handler. - 3. Employ a tiny helper script, as the default core dump handler, which looks for specified programs such as "apport", "abrt", systemd-coredump" and pipes to them, or pipes it to /var/crash, or /tmp during it's absence. + 2. Switch to systemd-coredump, and default to it, since it already does this very well and provides "coredumpctl" which is much nicer to work with. systemd-coredump also is a part of the systemd suite of utils and doesn't pull in a larger dependency as apport -- which to date, isn't as robust (I still have "core" files being left all over the place by apport, mostly in my home folder). This also has a nice advantage of unifying the OSS community in terms of coredump handler. apport can handle things from the core dumps that systemd generates, further on desktops. + 3. Employ a tiny helper script, as the default core dump handler, which looks for specified programs such as "apport", "abrt", systemd-coredump" and pipes to them, or pipes it to /var/crash, or /tmp during it's absence. This does have the disadvantage of growing with it's own config, rather quickly. - And add a sysctl.d default rule here, or more cleanly a separate package - that does exactly this on option 3. ProblemType: Bug DistroRelease: Ubuntu 18.10 - Package: procps 2:3.3.15-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 26 20:33:55 2019 InstallationDate: Installed on 2019-01-01 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) - SourcePackage: procps UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-01-15T04:51:59.517661 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1813403 Title: Better kernel core dump defaults Status in Ubuntu: New Bug description: Currently, `$ sysctl kernel.core_pattern` gives `kernel.core_pattern = |/usr/share/apport/apport %p %s %c %d %P` This should be considered a bug, since a minimal version of ubuntu (server, core etc) and more notoriously when run from containers, this will just error out, with no core dump being produced, due to the absence of apport. Adding to the problem, is with container where you can't just change it per container, and should be changed from the host. I think using apport (a non essential package) as a default without thought as to it's absence is not robust design. There are multiple options to deal with this: 1. Drop apport as default and switch to a simple file in either /var/crash (this requires creating /var/crash as a part of the installation as it's currently created by apport), or /tmp 2. Switch to systemd-coredump, and default to it, since it already does this very well and provides "coredumpctl" which is much nicer to work with. systemd-coredump also is a part of the systemd suite of utils and doesn't pull in a larger dependency as apport -- which to date, isn't as robust (I still have "core" files being left all over the place by apport, mostly in my home folder). This also has a nice advantage of unifying the OSS community in terms of coredump handler. apport can handle things from the core
[Touch-packages] [Bug 1350393] Re: Recent accountsservice update causes login window to hang
I am still suffering from this bug. I am on Ubuntu 16.04 32 bit platform. I installed libvirt-qemu and it adds itself to user group as ` libvirt-qemu:x:64055:128:Libvirt Qemu,,,:/var/lib/libvirt:/bin/false`. Since its user id > 1000 it hangs the lightdm over one minute due to above bug. How can I work around this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1350393 Title: Recent accountsservice update causes login window to hang Status in Light Display Manager: New Status in accountsservice package in Ubuntu: Incomplete Bug description: Hi, The recent 0.6.35-0ubuntu7.1 update (see https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785) seems to have removed the UID_MAX check, which could be used to hide users from the login window. In a large organization where many thousands of users are present on our systems, we relied on the UID_MAX setting in /etc/login.defs to prevent accounts-daemon from trying to frob all our accounts. accounts-daemon's performance is so poor, that not having the UID_MAX check causes lightdm to hang for 5-10mins while accounts-daemon tries to look for something in every users home folder. I've already done things like set the login window to require the user to enter their username and password rather than list all users, but the login window still hangs while accounts-daemon is doing its thing. The behavior I see, is: 1) just after boot, there's a black screen, right after the plymouth splash disappears, for 2-3 minutes before lightdm appears 2) You type a username into the username field and press 'Tab' 3) lightdm appears to hang for 5-10mins before the cursor moves to the password field. During this time, I see an accounts-daemon spawn for each user on the system, sequentially (in alphabetical order). Once the last user's accounts-daemon process finishes, the cursor moves to the password field. This not only happens on first boot, but every time a user logs out and the system returns to the login window. Any chance we can have the UID_MAX check back? Or some equivalent? This is causing a serious problem for us! Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1350393/+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 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
Launchpad has imported 5 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=109102. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-12-19T14:29:06+00:00 Gert van de Kraats wrote: Created attachment 142855 stacktrace This is a copy of ubuntu bug 1797882. It should be directly submitted to mesa. Using ubuntu 18.10 wayland with dual monitors, configured above each other. Dock is configured at both displays, not hiding. Icons for "terminal" and "libreofffice Writer" are present at the dock. Start terminal on primary screen by mouseclick on dock. Start libreoffice Writer on primary screen by mouseclick on dock. Terminate libreoffice Witer by mouseclick on X. Repeat the starting and stopping of Writer. Login-screen will appear. Syslog shows: Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked failed: Resource deadlock avoided Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from display: Connection reset by peer Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE This problem doesnot occur in a dual monitor-session without wayland. It also doesnot occur, if only one monitor used with wayland It also doesnot occur, if the dock is only present at the primary screen. It also doesnot occur if second started application is present at the dock and doesnot add an icon to the dock (as libreoffice does). All other dual monitor/dock configurations seem to have this problem. No idea if this is helpful info, but the used graphics card does not support OpenGL version 2.1: Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 2.1 or later. Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor, falling back to sw glxinfo: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 18.2.2 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: Extra info: Without solving this problem, wayland cannot be used after logon, when using dual monitor. The sesssion stops very easy and often. Work is lost; you have to logon again. E.g. the simple switching between 2 overlapping windows causes the end of the session. I changed src/mesa/drivers/dri/i915/intel_batchbuffer.c to force a coredump in this case. The stacktrace is added to this bug-report. Linenumbers might deviate a little bit because of extra coding of tracing. The deadlock always occurs at cogl_onscreen_swap_buffers calling cogl_flush(), at the first journal-batch-flush for the offscreen-framebuffer. The deadlock disappeared as soon as cogl is compiled with disabled batching! To minimize this disabling of batching, I made a very dirty but working patch, which is attached to this bug. At program clutter_stage_cogl_redraw_view routine paint_stage is called for the "Unclipped stage paint". This call is manipulated to flush immedately the first journal-entry of the default onscreen framebuffer. This is done by misusing and changing program cogl_framebuffer_set_viewport and by changing _cogl_journal_flush. Apparenly this early flushing causes a lock to be set which avoids the deadlock. I do not know how to see which locks are held and by which process, so I cannot solve the root-cause of the problem, but I assume some extra lock must be set in this case to avoid deadlock. With this dirty patch combined with other suggested (simple) patches at #1790525, #1795774 and #1795760 wayland can be run without any problems on dual monitor and "old" intel graphic card. It performs better than lightdm, specially if the monitors are positioned aside of each other. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1797882/comments/6 On 2018-12-19T14:31:37+00:00 Gert van de Kraats wrote: Created attachment 142856 ubuntu-cogl-patch Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1797882/comments/7 On 2018-12-19T14:35:07+00:00 Chris Wilson wrote: -EDEADLOCK = userspace tried to use mo
[Touch-packages] [Bug 1812247] Re: ssh-agent fails for ssh-add -c: agent refused operation
@paelzer, you put a lot of work into this. Much appreciated! Thanks a lot! There's an important difference between your approach and mine: You start another ssh-agent within a terminal that you do not leave. So, this ssh-agent is available, it's plain OpenSSH ssh-agent, nothing seems to interfere, and everything works fine. I can confirm this. However, an ssh-agent is already running, started by the X (or GNOME) session. And that's the ssh-agent we want to use so that the keys are available to all programs started by the window manager (e.g. a file manager accessing sftp://...). Thanks to your input, though, and thanks to the fact that I got a new VirtualBox set up, I found that it's not just `ssh-add -c` that is failing. ssh-askpass itself (tried with the plain X11 one and the GNOME version) is not shown when it should. So, I got a step further but, unfortunately, I still don't know where the actual bug is located. I am confused by a (new?) feature of GNOME keyring (I think) that makes locally saved SSH keys available and presents a full-screen dialog to ask for the password of the key. There are 2 big problems with this: (1) It works only for locally saved keys, but we want ssh-agent to receive keys via ssh-add from anywhere (e.g. a remote server via `ssh -A`). (2) This dialog is not ssh-askpass. So, if ssh-askpass is supposed to work it does not. Hence, `ssh-add -c` and key confirmations fail, too. I am attaching my full console session in Ubuntu 18.04.1 for reference and details. ** Attachment added: "ssh-agent-askpass-bug.txt" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1812247/+attachment/5232794/+files/ssh-agent-askpass-bug.txt ** Tags added: bionic -- 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/1812247 Title: ssh-askpass(-gnome): GNOME fails to show dialog Status in openssh package in Ubuntu: New Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1812247/+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 1812247] Re: ssh-askpass(-gnome): GNOME fails to show dialog
** Summary changed: - ssh-agent fails for ssh-add -c: agent refused operation + ssh-askpass(-gnome): GNOME fails to show dialog -- 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/1812247 Title: ssh-askpass(-gnome): GNOME fails to show dialog Status in openssh package in Ubuntu: New Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1812247/+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 1812247] Re: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation
Gosh, I was mistaken in #7. As in my initial report: ssh-askpass is working, it is only failing for ssh-add -c: tux@vbu1804:~$ ssh-add -D All identities removed. tux@vbu1804:~$ ssh-add -l 2048 SHA256:vHjyOAyTnsn92i47AQ8qu/oL2Y3blesvs09wUoYpDDY tux@vbu1804 (RSA) tux@vbu1804:~$ ssh-add https://bugs.launchpad.net/bugs/1812247 Title: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation Status in openssh package in Ubuntu: New Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1812247/+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 1813428] [NEW] "sorry, you are not running GNOME or KDE" while running GNOME
Public bug reported: 1) run ubuntu-bug with no arguments 2) "What kind of problem do you want to report?" choose "External or internal storage devices(e.g. USB sticks)" 3) OK 4) choose "Removable storage device is not mounted automatically" 5) when ubuntu-bug says "please remove it ..." physically remove USB thumb drive from computer. 6) when ubuntu-bug says "please plug it back in..." physically plug USB thumb back in computer. result: "sorry, you are not running GNOME or KDE automounting needs to be provided by your desktop environment" oddly enough if you leave it in, instead of unplugging, it proceeds to report the bug as usual usb thumb drive device: /dev/sdg Bus 001 Device 016: ID 10d6:1101 Actions Semiconductor Co., Ltd D-Wave 2GB MP4 Player / AK1025 MP3/MP4 Player gnome: 3.28.2 OS type: 64 bit ubuntu: bionic 18.04 apport: Installed: 2.20.9-0ubuntu7.5 Candidate: 2.20.9-0ubuntu7.5 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1813428 Title: "sorry, you are not running GNOME or KDE" while running GNOME Status in apport package in Ubuntu: New Bug description: 1) run ubuntu-bug with no arguments 2) "What kind of problem do you want to report?" choose "External or internal storage devices(e.g. USB sticks)" 3) OK 4) choose "Removable storage device is not mounted automatically" 5) when ubuntu-bug says "please remove it ..." physically remove USB thumb drive from computer. 6) when ubuntu-bug says "please plug it back in..." physically plug USB thumb back in computer. result: "sorry, you are not running GNOME or KDE automounting needs to be provided by your desktop environment" oddly enough if you leave it in, instead of unplugging, it proceeds to report the bug as usual usb thumb drive device: /dev/sdg Bus 001 Device 016: ID 10d6:1101 Actions Semiconductor Co., Ltd D-Wave 2GB MP4 Player / AK1025 MP3/MP4 Player gnome: 3.28.2 OS type: 64 bit ubuntu: bionic 18.04 apport: Installed: 2.20.9-0ubuntu7.5 Candidate: 2.20.9-0ubuntu7.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1813428/+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 1813430] [NEW] fstrim.service should not run inside container
Public bug reported: On LXD containers, the fstrim.service will errored permanently. /sbin/fstrim -av fstrim: /: FITRIM ioctl failed: Operation not permitted The unit file should contain ConditionVirtualization=!container to prevent errors inside containers ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: lxd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1813430 Title: fstrim.service should not run inside container Status in util-linux package in Ubuntu: New Bug description: On LXD containers, the fstrim.service will errored permanently. /sbin/fstrim -av fstrim: /: FITRIM ioctl failed: Operation not permitted The unit file should contain ConditionVirtualization=!container to prevent errors inside containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1813430/+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 1813431] [NEW] Problem with start menu and menu bar
Public bug reported: When I clicked on the start menu in the top right corner, that little window jumped out, and. when I wanted to lock my account, nothing happened, but when I clicked on that panel again, it was like... vibrating... It was moving up and down about 10px (If I remember well). When I left it be and came back later (I have automatic lock after 5 min) There was that menu on the left (I don't know the name :D) After I logged in, I noticed, that when I move my mouse on it, it becomes wider and icons go slightly further apart(When I'm on desktop). When I have Firefox window opened, same happens, but when I aim on Firefox icon, the icons go to normal distance, but bar is still wider. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-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' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 23:29:36 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:805d] InstallationDate: Installed on 2019-01-11 (15 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 0c45:760a Microdia Bus 001 Device 002: ID 0458:0188 KYE Systems Corp. (Mouse Systems) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProDesk 600 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=4d46de66-f485-47e9-905c-9d172082c94d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2016 dmi.bios.vendor: HP dmi.bios.version: N02 Ver. 02.16 dmi.board.name: 805D dmi.board.vendor: HP dmi.board.version: KBC Version 05.22 dmi.chassis.asset.tag: CZC6448GH4 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN02Ver.02.16:bd08/18/2016:svnHP:pnHPProDesk600G2SFF:pvr:rvnHP:rn805D:rvrKBCVersion05.22:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP ProDesk 600 G2 SFF dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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.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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu ** Attachment added: "examples.desktop" https://bugs.launchpad.net/bugs/1813431/+attachment/5232800/+files/examples.desktop -- 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/1813431 Title: Problem with start menu and menu bar Status in xorg package in Ubuntu: New Bug description: When I clicked on the start menu in the top right corner, that little window jumped out, and. when I wanted to lock my account, nothing happened, but when I clicked on that panel again, it was like... vibrating... It was moving up and down about 10px (If I remember well). When I left it be and came back later (I have automatic lock after 5 min) There was that menu on the left (I don't know the name :D) After I logged in, I noticed, that when I move my mouse on it, it becomes wider and icons go slightly further apart(When I'm on desktop). When I have Firefox window opened, same happens, but when I aim on Firefox icon, the icons go to normal distance, but bar is still wider. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-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' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 23:29:36 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:805d] InstallationDate:
[Touch-packages] [Bug 1813432] [NEW] Specific PDF file fails to print to HP m551dn printer
Public bug reported: 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 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ** Attachment added: "error_log" https://bugs.launchpad.net/bugs/1813432/+attachment/5232816/+files/error_log -- 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 Curre
[Touch-packages] [Bug 1813433] [NEW] Xorg freeze
Public bug reported:
Hello,
Thanks for looking forward to fix problems.
I re-installed ubuntu 18.04LTS & 18.10 4 times and every time it's just get
worse! So this time I did my best, And I didn't re-install ubuntu I just
changed gdm to lightdm < after looking for the problem > I notice that Ubuntu +
Ubuntu On WayLand is not working at all, So I logged into GNOME and It's
working perfectly.
--
Problems are:
1- Freezing for the whole system, Even music Freeze Ex. Before Freezing:Lalala
| After: l
2- Black Screen With A lot of [OK] { I guess that ubuntu-desktop couldn't boot
up }
--
That's it
Best Wishes,
Just4you.
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
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sun Jan 27 02:11:30 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GpuHangFrequency: Continuously
GpuHangReproducibility: I don't know
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA
controller])
Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920]
InstallationDate: Installed on 2019-01-24 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 8087:07dc Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA Satellite L50-B
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic
root=UUID=220449dc-de23-41d3-9305-079db3268b33 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 2.00
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - 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:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSatelliteL50-B:pvrPSKTNV-02Y01DAR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: INVALID
dmi.product.name: Satellite L50-B
dmi.product.version: PSKTNV-02Y01DAR
dmi.sys.vendor: TOSHIBA
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 1:1.0.15-2
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic freeze 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/1813433
Title:
Xorg freeze
Status in xorg package in Ubuntu:
New
Bug description:
Hello,
Thanks for looking forward to fix problems.
I re-installed ubuntu 18.04LTS & 18.10 4 times and every time it's just get
worse! So this time I did my best, And I didn't re-install ubuntu I just
changed gdm to lightdm < after looking for the problem > I notice that Ubuntu +
Ubuntu On WayLand is not working at all, So I logged into GNOME and It's
working perfectly.
--
Problems are:
1- Freezing for the whole system, Even music Freeze Ex. Before
Freezing:Lalala | After: l
2- Black Screen With A lot of [OK] { I guess that ubuntu-desktop couldn't
boot up }
--
That's it
Best Wishes,
Just4you.
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
ApportVersion: 2.20.9-0ubuntu7.2
Architecture:
[Touch-packages] [Bug 1813434] [NEW] package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error
Public bug reported: this shows up on startup ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sat Jan 26 18:30:41 2019 DuplicateSignature: package:libpolkit-agent-1-0:0.105-20ubuntu0.18.04.4 Unpacking gir1.2-polkit-1.0 (0.105-20ubuntu0.18.04.4) over (0.105-20ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-STjm8e/008-libpolkit-agent-1-0_0.105-20ubuntu0.18.04.4_amd64.deb (--unpack): unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error ErrorMessage: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error InstallationDate: Installed on 2013-11-13 (1900 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: policykit-1 Title: package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1813434 Title: package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error Status in policykit-1 package in Ubuntu: New Bug description: this shows up on startup ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sat Jan 26 18:30:41 2019 DuplicateSignature: package:libpolkit-agent-1-0:0.105-20ubuntu0.18.04.4 Unpacking gir1.2-polkit-1.0 (0.105-20ubuntu0.18.04.4) over (0.105-20ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-STjm8e/008-libpolkit-agent-1-0_0.105-20ubuntu0.18.04.4_amd64.deb (--unpack): unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error ErrorMessage: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error InstallationDate: Installed on 2013-11-13 (1900 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: policykit-1 Title: package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1813434/+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 1813434] Re: package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1813434 Title: package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error Status in policykit-1 package in Ubuntu: New Bug description: this shows up on startup ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sat Jan 26 18:30:41 2019 DuplicateSignature: package:libpolkit-agent-1-0:0.105-20ubuntu0.18.04.4 Unpacking gir1.2-polkit-1.0 (0.105-20ubuntu0.18.04.4) over (0.105-20ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-STjm8e/008-libpolkit-agent-1-0_0.105-20ubuntu0.18.04.4_amd64.deb (--unpack): unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error ErrorMessage: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error InstallationDate: Installed on 2013-11-13 (1900 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: policykit-1 Title: package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1813434/+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 1789523] Re: The ssh-agent launcher script fails to relaunch ssh-agent
It appears it's still there, but only accessible to project members. Which also excludes me. -- 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/1789523 Title: The ssh-agent launcher script fails to relaunch ssh-agent Status in xorg package in Ubuntu: Confirmed Bug description: There is an issue with the Xsession, in which logging out and logging back in again does not clear environment variables, so the ssh-agent script thinks that the agent is already running, and thus does not bother to start it again. I have altered the script, albeit in not the most pretty way, to detect if the agent is already running, and if not, force a restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 28 17:33:34 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installed anbox, 1, 4.15.0-33-generic, x86_64: installed nvidia, 396.54, 4.15.0-33-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2018-08-04 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7751 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash amdgpu.dc=0 mem=33554428k vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-GD65 (MS-7751) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.11:bd10/09/2013:svnMSI:pnMS-7751:pvr2.0:rvnMSI:rnZ77A-GD65(MS-7751):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7751 dmi.product.version: 2.0 dmi.sys.vendor: MSI mtime.conffile..etc.X11.Xsession.d.90x11-common_ssh-agent: 2018-08-28T17:23:14.025376 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1808281609.f3d90e8~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:18.3~git180816191500.b618d7e~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:18.3~git180816191500.b618d7e~b~padoka0 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.99+git1808290006.cba8fe4~b~padoka0 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1806121919.3d39506~b~padoka0 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/xorg/+bug/1789523/+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 1773007] Re: sntp return code is not EXIT_FAILURE when hostname query is not successful
[Expired for ntp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ntp (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1773007 Title: sntp return code is not EXIT_FAILURE when hostname query is not successful Status in ntp package in Ubuntu: Expired Bug description: # sntp abc sntp 4.2.8p10@1.3728-o (1) kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory abc lookup error Temporary failure in name resolution echo $? 0 from the manpage for sntp: EXIT STATUS One of the following exit values will be returned: 0 (EXIT_SUCCESS) Successful program execution. 1 (EXIT_FAILURE) The operation failed or the command syntax was not valid. 66 (EX_NOINPUT) A specified configuration file could not be loaded. 70 (EX_SOFTWARE) libopts had an internal operational error. Please report it to auto‐ gen-us...@lists.sourceforge.net. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sntp 1:4.2.8p10+dfsg-5ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 23 19:53:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.ntp.conf: 2018-05-23T19:24:22.724839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1773007/+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
