[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Thanks fusillo for the report, documentation and test. I did the same thing but failed since I also tried to get coccinelle/flags-set.cocci backported, which was an upstream change: https://github.com/systemd/systemd/commit/d94a24ca2ea769755beaed0659b966b1ec75c8d4 I assumed (wrongly) this upstream change would be needed as well. -- 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: Confirmed Status in systemd source package in Cosmic: Fix Committed 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 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo
Hi Joshua, Have you been able to test the systemd proposed package using your k8s setup reproducer ? I'll be curious to hear about the outcome before I request the release of this package to its final destination: xenial-updates and mark the end of this particular SRU. Regards, Eric -- 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/1795764 Title: systemd: core: Fix edge case when processing /proc/self/mountinfo Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] kubernetes loaded inactive dead transient mount points grows https://github.com/kubernetes/kubernetes/issues/57345 [Test Case] # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test Expected outcome (w/ the fix) : # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test [Regression Potential] This is a adapted version of 2 upstream fixes as the original upstream commit has been made on top on 2 functions mount_setup_new_unit() & mount_setup_existing_unit() that not yet exist systemd 229. It is easily adaptable because the current function mount_setup_unit() is dealing with both of at the moment instead of being individually separate in two distinct function. It is an adaptation of commits : [65d36b495] core: Fix edge case when processing /proc/self/mountinfo [03b8cfede] core: make sure to init mount params before calling mount_is_extrinsic() This patch changes mount_setup_unit() to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialised properly. Additionally, the patch got the blessing of 'xnox' who looked at it and mention it looks fine to him. [Pending SRU] Note: No autopkgtests has been reported since systemd (21.5) ... between 21.5 and now (21.11) everything released has been about security fixes : systemd (229-4ubuntu21.11) xenial; urgency=medium ==> Current SRU systemd (229-4ubuntu21.10) xenial-security; urgency=medium systemd (229-4ubuntu21.9) xenial-security; urgency=medium systemd (229-4ubuntu21.8) xenial-security; urgency=medium systemd (229-4ubuntu21.6) xenial-security; urgency=medium systemd (229-4ubuntu21.5) xenial; urgency=medium ==> Previous SRU Note: I don't know the level of adoption of Netplan in Xenial, but I suspect it is low as Netplan replaced ifupdown as the default configuration utility starting with Ubuntu 17.10 Artful only AFAIK. * Regression in autopkgtest for nplan (s390x): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz Error: modprobe: FATAL: Module cfg80211 not found in directory /lib/modules/4.4.0-138-generic Justification: This above seems to be a recurrent failure since a couple of release already. This wasn't introduce by this particular SRU. I don't think having wifi module is relevant in s390x anyway, so most likely the module is not there on purpose for kernel w/ s390x architecture. * Regression in autopkgtest for nplan (amd64): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nplan/20181217_010129_e07e2@/log.gz Error: (Ran on autopkgtest Ubuntu infra) test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... Error: Could not create NMClient object: Cannot invoke method; proxy is for a well-known name without an owner and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL test_bridge_priority (__main__.TestNetworkManager) ... Error: Could not create NMClient object: Cannot invoke method; proxy is for a well- known name without an owner and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL test_dhcp6 (__main__.TestNetworkManager) ... Error: Could not create NMClient object: Cannot invoke method; proxy is for a well-known name without an owner and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL Justification: The test are "passing" if ran manually in my own HW : autopkgtest [15:29:15]: host ; command line: /usr/bin/autopkgtest nplan -U --apt-pocket=proposed --log-file
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
I didn't find any conflict or overlap applying the btrfs-util-unbreak-tmpfiles-subvol-creation on top of the other patches on the source package systemd_237-3ubuntu10.9.debian, although the codebase of src/basic/btrfs-util.c affected by the patch had different hunks regards to the file in systemd_239. So to apply the patch conceived by Brian Murray on bionic I only had to add the missing macro FLAGS_SET on macro.h and refreshed the patch here's the missing part to make it compile on bionic Index: systemd-237/src/basic/macro.h === --- systemd-237.orig/src/basic/macro.h +++ systemd-237/src/basic/macro.h @@ -351,6 +351,9 @@ static inline unsigned long ALIGN_POWER2 #define SET_FLAG(v, flag, b) \ (v) = (b) ? ((v) | (flag)) : ((v) & ~(flag)) +#define FLAGS_SET(v, flags) \ +(((v) & (flags)) == (flags)) + #define CASE_F(X) case X: #define CASE_F_1(CASE, X) CASE_F(X) #define CASE_F_2(CASE, X, ...) CASE(X) CASE_F_1(CASE, __VA_ARGS__) The error of tmp disappeared at the boot, and the security issues should be patched by the preceding CVE-2018-6954* patches. Let me know if I should submit the patch. Anyway I'm not a good programmer so wait for hints of maintainers, Brian Murray or other guru. Regards -- 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: Confirmed Status in systemd source package in Cosmic: Fix Committed 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 1151682] Re: Sound randomly keeps droping out and takes the terminal with it
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014. Reporter no longer uses Launchpad so cannot ascertain if problem still exists Issue not confirmed by another user Marking "Invalid" to close ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- 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/1151682 Title: Sound randomly keeps droping out and takes the terminal with it Status in alsa-driver package in Ubuntu: Invalid Bug description: When listening to music, occasionally the sound will just cut off after the song has finished. When this happens the terminal will just fail and report the following message: There was an error creating the child process for this terminal getpt failed: No such file or directory And will give me two choises of Relaunching or adjusting the profile preferences, neither of which will fix the problem. Kernel Version: 3.8.2 Ubuntu Version: 13.04 Codename: Raring Ringtail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1151682/+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 1810630] [NEW] Resolution Incorrect
Public bug reported: Despite updating drivers for video through xorg, display cannot change from 1024x768. Default video card is still listed as llvmpipe. 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 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 5 15:19:12 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:7270] Subsystem: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2018-12-24 (12 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Apple Inc. MacBook2,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2d93d825-1bcb-4155-aad5-cfdb5dce95ab ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.family: MacBook dmi.product.name: MacBook2,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96+git1901040630.403f3c~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901050730.884737~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.0~git1901050730.884737~oibaf~b 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.1.99+git1812281934.803f87~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1812031933.e5ff8e~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1812100734.a4283f~oibaf~b ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic resolution third-party-packages 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/1810630 Title: Resolution Incorrect Status in xorg package in Ubuntu: New Bug description: Despite updating drivers for video through xorg, display cannot change from 1024x768. Default video card is still listed as llvmpipe. 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 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 5 15:19:12 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:7270] Subsystem: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2018-12-24 (12 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Apple Inc. MacBook2,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2d93d825-1bcb-4155-aad5-cfdb5dce95ab ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version:
[Touch-packages] [Bug 731526] Re: Old crashdb.conf.d entries with bug_pattern_base (even if it is None) cause crash in apport.
** Changed in: ubuntuone-client (Ubuntu) Status: Triaged => Incomplete ** Changed in: ubuntuone-client (Ubuntu) Status: Incomplete => Opinion -- 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/731526 Title: Old crashdb.conf.d entries with bug_pattern_base (even if it is None) cause crash in apport. Status in Apport: Fix Released Status in Indicator Applet: Invalid Status in Application Menu Indicator: Invalid Status in apport package in Ubuntu: Fix Released Status in ubuntuone-client package in Ubuntu: Opinion Status in apport source package in Natty: Fix Released Status in ubuntuone-client source package in Natty: Won't Fix Bug description: Binary package hint: apport Right now ubuntuone-client in natty suffers from a broken unity library. Upon adding the bugpattern to the bugpatterns.xml and testing it with test-local with positive results I found that apport reporting tool started to crash. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: apport-gtk 1.19-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CrashReports: 600:1000:1000:68754:2011-03-08 20:45:36.604509000 +0200:2011-03-08 20:45:37.604509000 +0200:/var/crash/_usr_lib_ubuntuone-client_ubuntuone-syncdaemon.1000.crash 600:1000:1000:48421:2011-03-08 20:45:36.684509000 +0200:2011-03-08 20:45:41.654509001 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash Date: Tue Mar 8 20:45:37 2011 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gtk InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk PythonArgs: ['/usr/share/apport/apport-gtk'] SourcePackage: apport Title: apport-gtk crashed with KeyError in get_crashdb(): 'bug_pattern_url' UpgradeStatus: Upgraded to natty on 2010-12-05 (93 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin mythtv plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/731526/+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 1799038] Re: Ubuntu 18.10 does not suspend on lid close
I upgraded to 18.10 from 18.04 4 or 5 days ago and have been experiencing this issue. I think I have just resolved it by following steps on: https://askubuntu.com/questions/1086795/upgraded-from-18-04-to-18-10-now-suspend-doesnt-work-anymore edited /etc/default/grub file and changed: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs" then: sudo update-grub -- 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/1799038 Title: Ubuntu 18.10 does not suspend on lid close Status in systemd package in Ubuntu: Incomplete Bug description: After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid on notebooks does not work any more. The machine goes to suspend mode but wakes up immediately due to some events (can be network, or others). In 18.04 this issue was fixed (we had the same situation with any version since 14.04). Seems a regression. Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. The changes do NOTHING. One might spare the time to experiment. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 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: Sun Oct 21 11:55:48 2018 InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+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 736788] Re: 13d3:3304 IMC Networks bluetooth doesn't work
Has it been fixed or not? It doesn't work on Ubuntu 18.04!!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/736788 Title: 13d3:3304 IMC Networks bluetooth doesn't work Status in bluez package in Ubuntu: Fix Released Bug description: Binary package hint: bluez The "13d3:3304 IMC Networks" internal bluetooth module found in Asus U36JC notebook is not working in Ubuntu Maverick nor Natty. The systems certainly knows about presence of the bluetooth module - the icon in status bar is visible and allows to switch it on/off, but nothing else works. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7 Uname: Linux 2.6.38-6-generic x86_64 Architecture: amd64 CheckboxSubmission: 4c3a0145220348e366d02efaed27e66e CheckboxSystem: b8f3ec504801f13fc208edb5c785b099 Date: Thu Mar 17 12:03:47 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302) InterestingModules: sco bnep l2cap btusb bluetooth MachineType: ASUSTeK Computer Inc. U36JC ProcEnviron: LANGUAGE=cs_CZ:en PATH=(custom, user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-6-generic root=UUID=2d566c56-67c7-4af1-a443-a8c80061120c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36JC.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36JC dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36JC.205:bd01/26/2011:svnASUSTeKComputerInc.:pnU36JC:pvr1.0:rvnASUSTeKComputerInc.:rnU36JC:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U36JC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/736788/+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 1780241] Re: no sound in built in speakers after hdmi disconnect
*** This bug is a duplicate of bug 1711101 *** https://bugs.launchpad.net/bugs/1711101 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1780241 Title: no sound in built in speakers after hdmi disconnect Status in pulseaudio package in Ubuntu: Confirmed Bug description: Played a video file on TV via HDMI cable. Sound also playing on TV via HDMI. However sound does not play on the built in laptop speakers on disconecting the hdmi cable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: koli 1815 F pulseaudio /dev/snd/controlC1: koli 1815 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 5 21:58:16 2018 InstallationDate: Installed on 2018-05-12 (53 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1780241/+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 1810601] [NEW] Graphics trouble
Public bug reported: Can't seem to get system to use nvidia driver instead of Nouveau ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-lowlatency 4.15.18 Uname: Linux 4.15.0-43-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 5 16:03:44 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASRock Incorporation 2nd Generation Core Processor Family Integrated Graphics Controller [1849:0102] NVIDIA Corporation GF119 [NVS 310] [10de:107d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF119 [NVS 310] [10de:1154] InstallationDate: Installed on 2018-08-14 (143 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-lowlatency root=UUID=89dc7f0c-2342-4866-bf1f-7d5c9635d42c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: Z77 Extreme4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd03/02/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1810601 Title: Graphics trouble Status in xorg package in Ubuntu: New Bug description: Can't seem to get system to use nvidia driver instead of Nouveau ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-lowlatency 4.15.18 Uname: Linux 4.15.0-43-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 5 16:03:44 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASRock Incorporation 2nd Generation Core Processor Family Integrated Graphics Controller [1849:0102] NVIDIA Corporation GF119 [NVS 310] [10de:107d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF119 [NVS 310] [10de:1154] InstallationDate: Installed on 2018-08-14 (143 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine:
[Touch-packages] [Bug 1784135] Re: libicu-dev and libicu-dev:i386 conflict with each other
Thanks for answering. You are correct, ICU is fine, sorry for being too short. The proplem are the packages using ICU. My current understanding is that a solution for debian-unstable is on the way but it is to me unclear when this will land in Ubuntu 18.04. Currently wine cannot be compiled in Ubuntu 18.04 for 32-bit apps (and these are most apps) because of this bug (and #1772512). Thanks again! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1784135 Title: libicu-dev and libicu-dev:i386 conflict with each other Status in icu package in Ubuntu: Confirmed Status in icu package in Debian: New Bug description: Release is bionic (18.04.1) When trying to install libicu-dev and libicu-dev:i386 together in bionic, the conflict with each other. It is expected that these two libs can be installed together in one system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1784135/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
I could automate the workaround #26 and #30 but putting the said command in my .profile -- 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/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1726873] Re: mount.ecryptfs_private can't mount in 17.10
*** This bug is a duplicate of bug 1718658 *** https://bugs.launchpad.net/bugs/1718658 For those who may not be subscribers of the other bug (this one is marked as duplicate), try this solution: keyctl link @u @s I've put it in my .profile and it works around the problem "automatically". ** Tags added: bionic -- 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/1726873 Title: mount.ecryptfs_private can't mount in 17.10 Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Hi, I am using several ecryptfs mounts with ecryptfs-add-passphrase and mount.ecryptfs_private, configured in ~/.ecryptfs/xxx.conf and ~/.ecryptfs/xxx.sig, which was working well for years up to 17.04. With 17.10 I can't mount these file systems anymore. ecryptfs-add-passphrase says Inserted auth tok with sig [] into the user session keyring with the correct sig (!). Trying to mount with mount.ecryptfs_private then says mount: No such file or directory although all directories present and correct. the Kernel then says (dmesg): [10149.247972] Could not find key with description: [...] [10149.247994] process_request_key_err: No key [10149.248000] Could not find valid key in user session keyring for sig specified in mount option: [...] [10149.248012] One or more global auth toks could not properly register; rc = [-2] [10149.248019] Error parsing options; rc = [-2] with exactly the same sig! So although ecryptfs-add-passphrase claimed to have added the key to the keyring, the kernel complains that it could not find such a key. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ecryptfs-utils 111-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: LXDE Date: Tue Oct 24 15:31:45 2017 InstallationDate: Installed on 2017-10-24 (0 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1726873/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
Trying to mount a personnal dir (not home) with ecryptfs-simple fails, with the same error messages in kern.log as comment #20. (Using Linux Mint 19, Xfce.) The workaround in comments #26 and #30 works for me. (No sudo like in #28 : with sudo the mount works but the key sig gets added to /root/.ecryptfs . So keyctl has to be launched by thenormal user.) This bug affects a cryptographic (read: highly sensitive) feature, is 15 months old, a patch was proposed 12 months ago, but it is still of "Undecided" importance and still "Unassigned"? Come on! Are the ecryptfs-utils and systemd packages unmaintained at Ubuntu? The maintainer of ecryptfs-utils, Dustin Kirkland, is only listed as "may be notified" in the list of subscribers! The group maintainer of systemd, "Ubuntu Developers", is not listed at all! ** Tags added: bionic -- 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/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1799038] Re: Ubuntu 18.10 does not suspend on lid close
logind.conf modification works only when you fresh start a laptop and you're in the login screen. When you close the lid laptop will suspend. When you login closing the lid does nothing. Logs "sudo journalctl -b -u systemd-logind" show "Lid closed" and then "Lid opened" records. But nothing happens. Dell 5510 laptop, pretty old, but in previous versions it worked as expected. With new version introducing Gnome Shell it started misbehaving. -- 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/1799038 Title: Ubuntu 18.10 does not suspend on lid close Status in systemd package in Ubuntu: Incomplete Bug description: After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid on notebooks does not work any more. The machine goes to suspend mode but wakes up immediately due to some events (can be network, or others). In 18.04 this issue was fixed (we had the same situation with any version since 14.04). Seems a regression. Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. The changes do NOTHING. One might spare the time to experiment. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 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: Sun Oct 21 11:55:48 2018 InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+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 1808393] Re: libedit 3.1-20181209-1 causes php7.3 to FTBFS
Robie, is this still an issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libedit in Ubuntu. https://bugs.launchpad.net/bugs/1808393 Title: libedit 3.1-20181209-1 causes php7.3 to FTBFS Status in libedit package in Ubuntu: In Progress Bug description: php7.3 7.3.0-1 did previously build in Launchpad, but doesn't rebuild unless I manually drop the Build-Depends for libedit-dev to force 3.1-20180525-1 from the release pocket to be used. Since we noticed this before proposed migration I'm adding a block since it causes a known regression in the release pocket. If this is the wrong thing to do, let's discuss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1808393/+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 1810578] Re: Set correct terminal size to improve login over serial port experience
&& works better :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1810578 Title: Set correct terminal size to improve login over serial port experience Status in base-files package in Ubuntu: New Bug description: For people who use ipmiconsole or other serial port access to servers a great deal it would be helpful to set LINES and COLUMNS correctly on login. There are a number of ways to do this. I found a small (10k) C application at: http://web.archive.org/web/20081224152013/http://www.davehylands.com /gumstix-wiki/resize/resize.c which works nicely. It appears to be a simplified version of the resize command in xterm (which has too many dependencies for comfortable server usage). It seems quite old (2006) so there may be a better, newer version of this. Perhaps it would be better named tty- resize. I added the following two lines to .profile which then invoke the resize command on login: # size the terminal for login over serial [[ $(tty) == /dev/ttyS* ]] & /usr/local/bin/resize I think remote serial usage is interesting for cloud and server farm use cases which are a big part of Ubuntu usage, so would like to improve experience in these cases across the board. This is a small part of that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1810578/+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 1810578] Re: Set correct terminal size to improve login over serial port experience
Hmm... that .profile causes this on SSH logins, so needs tweaking: Last login: Sat Jan 5 10:49:02 2019 from 192.168.4.70 [1]+ Exit 1 [[ $(tty) == /dev/ttyS* ]] john@xx:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1810578 Title: Set correct terminal size to improve login over serial port experience Status in base-files package in Ubuntu: New Bug description: For people who use ipmiconsole or other serial port access to servers a great deal it would be helpful to set LINES and COLUMNS correctly on login. There are a number of ways to do this. I found a small (10k) C application at: http://web.archive.org/web/20081224152013/http://www.davehylands.com /gumstix-wiki/resize/resize.c which works nicely. It appears to be a simplified version of the resize command in xterm (which has too many dependencies for comfortable server usage). It seems quite old (2006) so there may be a better, newer version of this. Perhaps it would be better named tty- resize. I added the following two lines to .profile which then invoke the resize command on login: # size the terminal for login over serial [[ $(tty) == /dev/ttyS* ]] & /usr/local/bin/resize I think remote serial usage is interesting for cloud and server farm use cases which are a big part of Ubuntu usage, so would like to improve experience in these cases across the board. This is a small part of that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1810578/+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 1810578] [NEW] Set correct terminal size to improve login over serial port experience
Public bug reported: For people who use ipmiconsole or other serial port access to servers a great deal it would be helpful to set LINES and COLUMNS correctly on login. There are a number of ways to do this. I found a small (10k) C application at: http://web.archive.org/web/20081224152013/http://www.davehylands.com /gumstix-wiki/resize/resize.c which works nicely. It appears to be a simplified version of the resize command in xterm (which has too many dependencies for comfortable server usage). It seems quite old (2006) so there may be a better, newer version of this. Perhaps it would be better named tty-resize. I added the following two lines to .profile which then invoke the resize command on login: # size the terminal for login over serial [[ $(tty) == /dev/ttyS* ]] & /usr/local/bin/resize I think remote serial usage is interesting for cloud and server farm use cases which are a big part of Ubuntu usage, so would like to improve experience in these cases across the board. This is a small part of that. ** Affects: base-files (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1810578 Title: Set correct terminal size to improve login over serial port experience Status in base-files package in Ubuntu: New Bug description: For people who use ipmiconsole or other serial port access to servers a great deal it would be helpful to set LINES and COLUMNS correctly on login. There are a number of ways to do this. I found a small (10k) C application at: http://web.archive.org/web/20081224152013/http://www.davehylands.com /gumstix-wiki/resize/resize.c which works nicely. It appears to be a simplified version of the resize command in xterm (which has too many dependencies for comfortable server usage). It seems quite old (2006) so there may be a better, newer version of this. Perhaps it would be better named tty- resize. I added the following two lines to .profile which then invoke the resize command on login: # size the terminal for login over serial [[ $(tty) == /dev/ttyS* ]] & /usr/local/bin/resize I think remote serial usage is interesting for cloud and server farm use cases which are a big part of Ubuntu usage, so would like to improve experience in these cases across the board. This is a small part of that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1810578/+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
