[Touch-packages] [Bug 2027581] Re: useradd grants root privileges to admin user
On UbuntuCore the default user added by console-conf is automatically granted passwordless sudo. the /etc/group file is on a readonly filesystem and contains the sudo group, this usually prevents you from accidentially adding extra sudo users (UbuntuCore exclusively uses /var/lib/extrausers for addtional users and snapd (being the management authority) normally creates snippets in /etc/sudoers.d on a per user basis) in earlier UbuntuCore releases the admin group still existed in the readonly /etc/group so adding such a user would have been prevented by the readonly state of the file. now you can unconditionally create such a user and automatically get sudo privs without having to go through a system-user assertion managed by snapd (which is the only process that can create snippets in /etc/sudoers.d on these systems) if not considered a security hole (due to the fact that you can circumvent the documented locked down user creation process via system- user-assertions for this type of systems) this is at least a heavy inconsistency ... we should either add an admin group to the core snaps readonly /etc/group or wipe the admin line from sudoers so we match the documented behavior. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2027581 Title: useradd grants root privileges to admin user Status in sudo package in Ubuntu: New Bug description: Hi, As part of the Ubuntu Core 20, if a developer creates a user named either admin or Admin, it will have root privileges by default. I think that this is a security issue but it requires input from the security engineers/specialists. Basically, if you look at the sudoers file under `/etc/sudoers`, you will realize the following line; ``` # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL ``` And if someone creates a user by using admin as name, the system provide root privilege. ``` sudo useradd -s /bin/bash -u 8003 -d /home/Admin --extrausers Admin iotuc@ubuntu:~$ su Admin Password: Admin@ubuntu:/home/iotuc$ cat /etc/sudoers cat: /etc/sudoers: Permission denied Admin@ubuntu:/home/iotuc$ sudo cat /etc/sudoers [sudo] password for Admin: # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaultsenv_reset Defaultsmail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification rootALL=(ALL:ALL) ALL # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL # Allow members of group sudo to execute any command %sudoALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d Admin@ubuntu:/home/iotuc$ ``` Similarly, if I create a username called aydogar, it does not have root privilege and this is expected. ``` sudo useradd -s /bin/bash -u 8004 -d /home/aydogar --extrausers aydogar iotuc@ubuntu:~$ su aydogar Password: aydogar@ubuntu:/home/iotuc$ cat /etc/sudoers cat: /etc/sudoers: Permission denied aydogar@ubuntu:/home/iotuc$ sudo cat /etc/sudoers [sudo] password for aydogar: aydogar is not in the sudoers file. This incident will be reported. aydogar@ubuntu:/home/iotuc$ ``` I think, this is a bug but would love here other ideas and inputs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2027581/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
for people not using the official announcement channels, here is a link to the related public announcement (with details on the reasoning and a place for discussion and feedback): https://discourse.ubuntu.com/t/feature-freeze-exception-seeding-the- official-firefox-snap-in-ubuntu-desktop/24210 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Status in ubuntu-meta source package in Impish: New Status in ubuntu-release-upgrader source package in Impish: New Bug description: Per Canonical's distribution agreement with Mozilla, we're making the snap¹ the default installation of firefox on desktop ISOs starting with Ubuntu 21.10. The snap is built and published for amd64, armhf and arm64. It is jointly maintained by Mozilla and the Ubuntu desktop team, and published by Mozilla. This requires updating the desktop-minimal seed, as well as ubuntu- release-upgrader. ¹ https://snapcraft.io/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
@kosharskiy this is completely unrelated to this installer bug (which is about configuring packages prior to/during install time), you should open a new bug for your issue ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0u
[Touch-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
there are various forum and askubuntu threads about this issue already as well: https://forum.snapcraft.io/t/ui-glitch-after-recent-update/15133 https://forum.snapcraft.io/t/some-snaps-app-have-weird-looking-window- control-and-fonts/17859 https://askubuntu.com/q/1206868/66509 https://discourse.ubuntu.com/t/odd-close-button-with-snaps/19392 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+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 1898869] Re: System slow on booting
> a) On theory it compromises the throughput (the whole CPU time that will take > for a > process to finish will be longer) for better responsiveness, even under high > load. So > mouse clicks/UI events should be handled faster and say, when decompressing > large files > or other CPU load by specific process the user interface should not freeze. err, nope ... it will prioritize processes differently (the preemption model is completely different) and is not actually optimized for desktop style performance, i'd really go back to the generic kernel here (we'd ship the lowlatency kernel by default on the desktop images if it would actually behave like you describe ;) ) -- 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/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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 1898869] Re: System slow on booting
oh, and i missed, d) there is a mis-configured postfix install running on that device too ... since it is not configured and crashing in a loop during boot anyway, i'd recomend removing postfix ... -- 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/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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 1898869] Re: System slow on booting
okay, thats quite different ... a) you run the lowlatency kernel for whatever reason ... this is clearly the worst choice you can pick for already slow hardware (low latency -> do one thing as fast as you can ... ignore other things ... i.e. you trade overall system performance for the ability to do one single task very fast (a typical use for this kernel is fully reliable professional audio processing (no crackling, no jitter) at the cost of desktop performance) b) the (third party) wlan driver crashes in a loop, preventing the network from coming up for quite some time ... c) you seem to run dnscrypt-proxy and that seems to effectively delay working DNS resolution until the end of the boot for whatever reason ... same question as before ... have you tired running a completely unmodified install of 20.04.1 on this hardware ? did that behave similarly slow ? -- 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/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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 1898869] Re: System slow on booting
erm ... this is an atom/celeron laptop with 4GB that starts BOINC as a system service during boot ? there seems to also be a lot of broken gnome-shell extensions installed on this system that error out during startup ... there is ifupdown installed which is probably involved with the network manager slowness (was this an upgrade from a former LTS ? (ifupdown is deprecated since years now and should not be installed at all) ... have you ever tried a plain unmodified 20.04.1 on this machine without installing all this extra software on top ? -- 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/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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 1888575] Re: Split motd-news config into a new package
please note that the stable UbuntuCore18 images regressed due to this: https://github.com/snapcore/core18/issues/170 ** Bug watch added: github.com/snapcore/core18/issues #170 https://github.com/snapcore/core18/issues/170 -- 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/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in livecd-rootfs source package in Xenial: Triaged Status in ubuntu-meta source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Released Status in livecd-rootfs source package in Bionic: Invalid Status in ubuntu-meta source package in Bionic: Fix Released Status in base-files source package in Focal: Fix Released Status in livecd-rootfs source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Fix Released Status in base-files source package in Groovy: Fix Released Status in livecd-rootfs source package in Groovy: Invalid Status in ubuntu-meta source package in Groovy: Fix Released Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --force $ (no output) k) Test that supporting changes for xenial are in place: i) verify grub-legacy-ec2 is not in the xenial server seed ii) verify that the rootfs manifest built from the ubuntu-cpc project contains the ubuntu-server package iii) verify that images built from the ubuntu-cpc project which purge grub-legacy-ec2 have retained ubuntu-server [Regression Potential] This update is about config file ownership transfer: /e/d/motd-news belonged to base-files, now it belongs to motd-news-config. We tried to handle two important cases here: a) /e/d/motd-news config was changed while it belonged to base-files. For example, an user could have set ENABLED=0. We need to transfer that change to the
[Touch-packages] [Bug 1895382] Re: Ability to install 2 or more versions at once
for reference: https://forum.snapcraft.io/t/parallel-installs/7679 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1662357] Re: Can't use lsb_release on Ubuntu Core 16
*** This bug is a duplicate of bug 1619420 *** https://bugs.launchpad.net/bugs/1619420 first of all the bug is a duplicate, secondly you can not install deb packages on Ubuntu Core, snap packages (of which Ubuntu Core is built) do use /etc/os-release. Additionally Ubuntu Core only ships the most minimal set of python ... If you see an issue on a Classic Ubuntu installation newer than Ubuntu Core 16, you should open a new bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1662357 Title: Can't use lsb_release on Ubuntu Core 16 Status in lsb: Invalid Status in Snappy: New Status in Snappy Ubuntu Core: New Status in lsb package in Ubuntu: Invalid Bug description: brian-murray@localhost:~$ snap list Name Version Rev Developer Notes core 16.04.1 888 canonical - brian-murray@localhost:~$ lsb_release Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '16.04 LTS' brian-murray@localhost:~$ lsb_release -a Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '6.06 LTS' To manage notifications about this bug go to: https://bugs.launchpad.net/lsb/+bug/1662357/+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 1885901] Re: timedatectl reports wrong status for timesyncd in core18
theer we go ... thanks a lot dimitri, i opened https://github.com/snapcore/core18/issues/157 ** Bug watch added: github.com/snapcore/core18/issues #157 https://github.com/snapcore/core18/issues/157 -- 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/1885901 Title: timedatectl reports wrong status for timesyncd in core18 Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Bionic: Incomplete Status in systemd source package in Focal: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: when calling timedatectl in Ubuntu Core 18 the tool reports the status of the systemd-timesyncd.service ... sadly it does report it wrongly (the tool reports it inactive while the service is actually running): ogra@pi4:~$ timedatectl Local time: Wed 2020-07-01 10:52:48 UTC Universal time: Wed 2020-07-01 10:52:48 UTC RTC time: n/a Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: no RTC in local TZ: no ogra@pi4:~$ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago Docs: man:systemd-timesyncd.service(8) Main PID: 779 (systemd-timesyn) Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 4915) CGroup: /system.slice/systemd-timesyncd.service └─779 /lib/systemd/systemd-timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+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 1885901] Re: timedatectl reports wrong status for timesyncd in core18
i dont know where you guys track core bugs either since foundations took over the responsibility Ubuntu Core with core 18... i can not reproduce it on classic anywhere but on each core18 image i have running at my house ... the customer that initially reported it uses core18, so it is important to get it fixed there, regardless if it works in core 20 (i'll do some testing though, but i currently do not have any core20 installs around). it is likely just core specific (confinement, the different way of assembling the rootfs or the fact that timedatectl has a wrapper on core) -- 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/1885901 Title: timedatectl reports wrong status for timesyncd in core18 Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Bionic: Incomplete Status in systemd source package in Focal: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: when calling timedatectl in Ubuntu Core 18 the tool reports the status of the systemd-timesyncd.service ... sadly it does report it wrongly (the tool reports it inactive while the service is actually running): ogra@pi4:~$ timedatectl Local time: Wed 2020-07-01 10:52:48 UTC Universal time: Wed 2020-07-01 10:52:48 UTC RTC time: n/a Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: no RTC in local TZ: no ogra@pi4:~$ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago Docs: man:systemd-timesyncd.service(8) Main PID: 779 (systemd-timesyn) Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 4915) CGroup: /system.slice/systemd-timesyncd.service └─779 /lib/systemd/systemd-timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+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 1885901] Re: timedatectl reports wrong status for timesyncd in core18
any fix should be SRUed into the respective LTS releases for Ubuntu Core, added tasks for them -- 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/1885901 Title: timedatectl reports wrong status for timesyncd in core18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Focal: New Status in systemd source package in Groovy: New Bug description: when calling timedatectl in Ubuntu Core 18 the tool reports the status of the systemd-timesyncd.service ... sadly it does report it wrongly (the tool reports it inactive while the service is actually running): ogra@pi4:~$ timedatectl Local time: Wed 2020-07-01 10:52:48 UTC Universal time: Wed 2020-07-01 10:52:48 UTC RTC time: n/a Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: no RTC in local TZ: no ogra@pi4:~$ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago Docs: man:systemd-timesyncd.service(8) Main PID: 779 (systemd-timesyn) Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 4915) CGroup: /system.slice/systemd-timesyncd.service └─779 /lib/systemd/systemd-timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+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 1885901] [NEW] timedatectl reports wrong status for timesyncd in core18
Public bug reported: when calling timedatectl in Ubuntu Core 18 the tool reports the status of the systemd-timesyncd.service ... sadly it does report it wrongly (the tool reports it inactive while the service is actually running): ogra@pi4:~$ timedatectl Local time: Wed 2020-07-01 10:52:48 UTC Universal time: Wed 2020-07-01 10:52:48 UTC RTC time: n/a Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: no RTC in local TZ: no ogra@pi4:~$ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago Docs: man:systemd-timesyncd.service(8) Main PID: 779 (systemd-timesyn) Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 4915) CGroup: /system.slice/systemd-timesyncd.service └─779 /lib/systemd/systemd-timesyncd ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) 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/1885901 Title: timedatectl reports wrong status for timesyncd in core18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Focal: New Status in systemd source package in Groovy: New Bug description: when calling timedatectl in Ubuntu Core 18 the tool reports the status of the systemd-timesyncd.service ... sadly it does report it wrongly (the tool reports it inactive while the service is actually running): ogra@pi4:~$ timedatectl Local time: Wed 2020-07-01 10:52:48 UTC Universal time: Wed 2020-07-01 10:52:48 UTC RTC time: n/a Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: no RTC in local TZ: no ogra@pi4:~$ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago Docs: man:systemd-timesyncd.service(8) Main PID: 779 (systemd-timesyn) Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 4915) CGroup: /system.slice/systemd-timesyncd.service └─779 /lib/systemd/systemd-timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+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 1875493] Re: [core] log rotation doesn't properly restart rsyslogd
it is a hard requirement of the SRU process that fixes land in the devel release and then propagate backwards through all other releases ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd Status in Snappy: New Status in rsyslog package in Ubuntu: New Bug description: One of our commercial partners is developing a device agent snap for UC16. One of their engineers just shared the following bug report: I wanted to give you a heads up on an issue that we encountered with one of our gateways (a Dell 3000) regarding a full disk (/writable). It seems as though rsyslog had a bad logrotate config and was holding on to deleted files as described here: - https://www.claudiokuenzler.com/blog/861/after-ubuntu-update-trusty-xenial-disk-filled-syslog-logrotate - https://bugzilla.redhat.com/show_bug.cgi?id=1713358 Both df and du where showing different results for the “/writable” path on the Dell gateway. We were able to copy the lsof binary over and found this: $ sudo /tmp/lsof | grep deleted ... rsyslogd 1765 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) rsyslogd 1765 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) rsyslogd 1765 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) in:imuxso 1765 1776 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) in:imuxso 1765 1776 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) in:imuxso 1765 1776 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) in:imklog 1765 1777 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) in:imklog 1765 1777 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) in:imklog 1765 1777 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) rs:main 1765 1778 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) rs:main 1765 1778 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) rs:main 1765 1778 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) ... Restarting the service freed up the deleted files / disk space: sudo service rsyslog restart The rsyslog config (/etc/logrotate.d/rsyslog) calls this script post rotate: /usr/lib/rsyslog/rsyslog-rotate Which does not actually kill the rsyslog process: admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.7 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2464 0.0 0.0 12984 932 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog admin@GR0GP42:~$ sudo /usr/lib/rsyslog/rsyslog-rotate admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2469 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog The fix appears to be using the following command: sudo systemctl restart rsyslog >/dev/null 2>&1 || true admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2482 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog admin@GR0GP42:~$ sudo systemctl restart rsyslog >/dev/null 2>&1 || true admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2487 1.0 0.1 262692 3432 ? Ssl 20:36 0:00 /usr/sbin/rsyslogd -n admin 2496 0.0 0.0 12984 980 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+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 1875493] Re: [core] log rotation doesn't properly restart rsyslogd
well, rsyslog is completely gone from core after UC16 ... how would you test that in UC18 or UC20 to verify SRUs ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd Status in Snappy: New Status in rsyslog package in Ubuntu: New Bug description: One of our commercial partners is developing a device agent snap for UC16. One of their engineers just shared the following bug report: I wanted to give you a heads up on an issue that we encountered with one of our gateways (a Dell 3000) regarding a full disk (/writable). It seems as though rsyslog had a bad logrotate config and was holding on to deleted files as described here: - https://www.claudiokuenzler.com/blog/861/after-ubuntu-update-trusty-xenial-disk-filled-syslog-logrotate - https://bugzilla.redhat.com/show_bug.cgi?id=1713358 Both df and du where showing different results for the “/writable” path on the Dell gateway. We were able to copy the lsof binary over and found this: $ sudo /tmp/lsof | grep deleted ... rsyslogd 1765 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) rsyslogd 1765 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) rsyslogd 1765 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) in:imuxso 1765 1776 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) in:imuxso 1765 1776 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) in:imuxso 1765 1776 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) in:imklog 1765 1777 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) in:imklog 1765 1777 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) in:imklog 1765 1777 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) rs:main 1765 1778 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) rs:main 1765 1778 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) rs:main 1765 1778 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) ... Restarting the service freed up the deleted files / disk space: sudo service rsyslog restart The rsyslog config (/etc/logrotate.d/rsyslog) calls this script post rotate: /usr/lib/rsyslog/rsyslog-rotate Which does not actually kill the rsyslog process: admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.7 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2464 0.0 0.0 12984 932 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog admin@GR0GP42:~$ sudo /usr/lib/rsyslog/rsyslog-rotate admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2469 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog The fix appears to be using the following command: sudo systemctl restart rsyslog >/dev/null 2>&1 || true admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2482 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog admin@GR0GP42:~$ sudo systemctl restart rsyslog >/dev/null 2>&1 || true admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2487 1.0 0.1 262692 3432 ? Ssl 20:36 0:00 /usr/sbin/rsyslogd -n admin 2496 0.0 0.0 12984 980 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+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 1850977] Re: Snap installs software without user having sudo access
the requirement for policykit (and dropping of gksu/gksudo) came with the switch to gnome upstream, its a hard requirement for the desktop nowadays. while the default here might be wrong (and should be reviewed by someone from the desktop team), this is definitely not a snapd related bug. i added a gnome-software task and will close the snapd one ... ** Changed in: snapd (Ubuntu) Status: Incomplete => Invalid ** Also affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- 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/1850977 Title: Snap installs software without user having sudo access Status in gnome-software package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Status in snapd package in Ubuntu: Invalid Bug description: $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy gnome-software gnome-software: Installed: 3.28.1-0ubuntu4.18.04.8 Candidate: 3.28.1-0ubuntu4.18.04.12 Version table: 3.28.1-0ubuntu4.18.04.12 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 3.28.1-0ubuntu4.18.04.8 100 100 /var/lib/dpkg/status 3.28.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 What I expect to happen: Software is not installed for a user without sudo access. What does happen: I'm logging in with an LDAP user. This user does not have sudo access. When I select software from gnome-software ("Ubuntu Software"), it pops up and asks for my users password. I enter this in, and the software then installs (tested with blender, libreoffice, opencl driver). My user does *not* have sudo access on the system. $ sudo su - [sudo] password for jason: jason is not in the sudoers file. This incident will be reported. It appears these *may* be being installed with Snaps ... which still: How, without having root access, can an unprivileged user install something onto the system? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 13:53:03 2019 InstallationDate: Installed on 2019-11-01 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+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 1850977] Re: Snap installs software without user having sudo access
policyKit does not involve sudo in any way, it uses systemd-logind from the session to elevate privileges. if you are marked as admin in the policyKit setup you will indeed be able to do admin things no matter what is written in sudoers ;) -- 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/1850977 Title: Snap installs software without user having sudo access Status in policykit-1 package in Ubuntu: New Status in snapd package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy gnome-software gnome-software: Installed: 3.28.1-0ubuntu4.18.04.8 Candidate: 3.28.1-0ubuntu4.18.04.12 Version table: 3.28.1-0ubuntu4.18.04.12 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 3.28.1-0ubuntu4.18.04.8 100 100 /var/lib/dpkg/status 3.28.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 What I expect to happen: Software is not installed for a user without sudo access. What does happen: I'm logging in with an LDAP user. This user does not have sudo access. When I select software from gnome-software ("Ubuntu Software"), it pops up and asks for my users password. I enter this in, and the software then installs (tested with blender, libreoffice, opencl driver). My user does *not* have sudo access on the system. $ sudo su - [sudo] password for jason: jason is not in the sudoers file. This incident will be reported. It appears these *may* be being installed with Snaps ... which still: How, without having root access, can an unprivileged user install something onto the system? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 13:53:03 2019 InstallationDate: Installed on 2019-11-01 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software 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/1850977/+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 1831252] [NEW] panic=-1 is completely ignored by the initrd causing unexpected behaviour
Public bug reported: in Ubuntu Core we default to using panic=-1 on the kernel command line (documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a kernel level this works just fine and the system reboots immediately ... when in the initramfs during boot and a panic occurs, no reboot happens at all, the initrd spawns a shell regardless of the panic= value ... this is caused by a filter in /usr/share/initramfs-tools/init panic=*) panic="${x#panic=}" case ${panic} in *[![:digit:].]*) panic= ;; esac ;; this function only lets positive values through, else panic= simply gets unset the panic() function itself is also not capable of handling negative values, it has a sleep call that interprets negative values as commandline options instead of simply ignoring a negative sleep time [2] (line 11). the filter in the init script should allow the -1 value (to comply with the kernel documentation and behaviour) and the panic() function should properly skip the sleep call when a negative value for panic= is set. [1] https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931 [2] https://paste.ubuntu.com/p/mswD8Cd869/ ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: rls-ee-incoming ** Also affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831252 Title: panic=-1 is completely ignored by the initrd causing unexpected behaviour Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Bug description: in Ubuntu Core we default to using panic=-1 on the kernel command line (documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a kernel level this works just fine and the system reboots immediately ... when in the initramfs during boot and a panic occurs, no reboot happens at all, the initrd spawns a shell regardless of the panic= value ... this is caused by a filter in /usr/share/initramfs-tools/init panic=*) panic="${x#panic=}" case ${panic} in *[![:digit:].]*) panic= ;; esac ;; this function only lets positive values through, else panic= simply gets unset the panic() function itself is also not capable of handling negative values, it has a sleep call that interprets negative values as commandline options instead of simply ignoring a negative sleep time [2] (line 11). the filter in the init script should allow the -1 value (to comply with the kernel documentation and behaviour) and the panic() function should properly skip the sleep call when a negative value for panic= is set. [1] https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931 [2] https://paste.ubuntu.com/p/mswD8Cd869/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+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 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour
targeting to xenial and bionic since we need this SRUed for Ubuntu Core installs. ** Description changed: in Ubuntu Core we default to using panic=-1 on the kernel command line (documented at [1]) to speed up the auto-rollback mechanism of the - kernel. on a kernel level this works just fine and teh system reboots + kernel. on a kernel level this works just fine and the system reboots immediately ... when in the initramfs during boot and a panic occurs, no reboot happens at all, the initrd spawns a shell regardless of the panic= value ... this is caused by a filter in /usr/share/initramfs-tools/init - panic=*) - panic="${x#panic=}" - case ${panic} in - *[![:digit:].]*) - panic= - ;; - esac - ;; + panic=*) + panic="${x#panic=}" + case ${panic} in + *[![:digit:].]*) + panic= + ;; + esac + ;; this function only lets positive values through, else panic= simply gets unset the panic() function itself is also not capable of handling negative values, it has a sleep call that interprets negative values as - commandline options instead of simply ignoring a negative sleep time - [2]. + commandline options instead of simply ignoring a negative sleep time [2] + (line 11). the filter in the init script should allow the -1 value (to comply with the kernel documentation and behaviour) and the panic() function should properly skip the sleep call when a negative value for panic= is set. [1] https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931 [2] https://paste.ubuntu.com/p/mswD8Cd869/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831252 Title: panic=-1 is completely ignored by the initrd causing unexpected behaviour Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Bug description: in Ubuntu Core we default to using panic=-1 on the kernel command line (documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a kernel level this works just fine and the system reboots immediately ... when in the initramfs during boot and a panic occurs, no reboot happens at all, the initrd spawns a shell regardless of the panic= value ... this is caused by a filter in /usr/share/initramfs-tools/init panic=*) panic="${x#panic=}" case ${panic} in *[![:digit:].]*) panic= ;; esac ;; this function only lets positive values through, else panic= simply gets unset the panic() function itself is also not capable of handling negative values, it has a sleep call that interprets negative values as commandline options instead of simply ignoring a negative sleep time [2] (line 11). the filter in the init script should allow the -1 value (to comply with the kernel documentation and behaviour) and the panic() function should properly skip the sleep call when a negative value for panic= is set. [1] https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931 [2] https://paste.ubuntu.com/p/mswD8Cd869/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
> Now that Ubuntu has given up on Wayland by default Ubuntu has not given up on Wayland by default but delayed it by one more LTS (particulary because of bugs like this one). Wayland by default is still the plan for the next LTS (and the interim releases between 18.04 and 20.04). The incentive for transitioning the apps has not dropped but it was clear that it could not be finished by 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Ar
[Touch-packages] [Bug 1619258] Re: netplan should allow NICs to be disconnected and not stall the boot
feel free (i set the snappy task to fix-released too) ** Changed in: snappy Status: Confirmed => Fix Released -- 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/1619258 Title: netplan should allow NICs to be disconnected and not stall the boot Status in Snappy: Fix Released Status in nplan package in Ubuntu: In Progress Status in systemd package in Ubuntu: Fix Released Bug description: in older snappy image we used to set "allow-hotplug" in /etc/network/interfaces.d/ when configuring a NIC to avoid the boot to completely stall or to be stuck for 5min when trying to find an internet connection. with recent versions of netplan the configuration seems to be back to require a network to be up before moving on with them boot so that booting takes forever until the network connection times out. netplan should make the system check the physical link status when trying to bring up a network device instead of stalling the boot. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1619258/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
well, my subtle hint would point to simply add it to /etc/environment here, which would globally cover for everything, would allow us to drop the profile.d snippet in ubuntu images/installs and to my knowledge would even be used by systemd (or am i wrong here ?) ... (and i think it would even work for zsh) -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: New Status in snapd source package in Xenial: New Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: New Status in systemd source package in Bionic: Won't Fix Status in snapd source package in Cosmic: New Status in systemd source package in Cosmic: Won't Fix Bug description: This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.). Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment. E.g.: $ sudo mkdir -p /usr/lib/systemd/system-environment-generators $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \ sudo tee /usr/lib/systemd/system-environment-generators/90-snapd Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user. Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up. systemd in xenial does not support system-environment-generators, thus we probably need to upload a patch to change the DEFAULT_PATH compiled in default there. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
i meant to say above is that it would be nice to find a way that covers all use-cases with one code path (sorry, just noticed what i wrote wasnt clear in that regard) -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: New Status in snapd source package in Xenial: New Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: New Status in systemd source package in Bionic: Won't Fix Status in snapd source package in Cosmic: New Status in systemd source package in Cosmic: Won't Fix Bug description: This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.). Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment. E.g.: $ sudo mkdir -p /usr/lib/systemd/system-environment-generators $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \ sudo tee /usr/lib/systemd/system-environment-generators/90-snapd Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user. Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up. systemd in xenial does not support system-environment-generators, thus we probably need to upload a patch to change the DEFAULT_PATH compiled in default there. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
snapd ships a snippet in /etc/profile.d that sets the PATH to /snap/bin and should theoretically work for all login shells (except for zsh which doesn't respect the profile.d standard) ... bug 1640514 and bug 1659719 are related. -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: New Status in snapd source package in Xenial: New Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: New Status in systemd source package in Bionic: Won't Fix Status in snapd source package in Cosmic: New Status in systemd source package in Cosmic: Won't Fix Bug description: This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.). Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment. E.g.: $ sudo mkdir -p /usr/lib/systemd/system-environment-generators $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \ sudo tee /usr/lib/systemd/system-environment-generators/90-snapd Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user. Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up. systemd in xenial does not support system-environment-generators, thus we probably need to upload a patch to change the DEFAULT_PATH compiled in default there. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1658909] Re: lsb_release fails in classic (arm64)
*** This bug is a duplicate of bug 1619420 *** https://bugs.launchpad.net/bugs/1619420 ** This bug is no longer a duplicate of bug 1662357 Can't use lsb_release on Ubuntu Core 16 ** This bug has been marked a duplicate of bug 1619420 snappy removal of dpkg-query breaks lsb_release --all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1658909 Title: lsb_release fails in classic (arm64) Status in Snappy: Confirmed Status in lsb package in Ubuntu: Invalid Status in lsb-release package in Ubuntu: Invalid Bug description: I'm getting this when running lsb_release with classic on a Dragonboard: $ lsb_release -a Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '16.04 LTS' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1658909/+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 1662357] Re: Can't use lsb_release on Ubuntu Core 16
*** This bug is a duplicate of bug 1619420 *** https://bugs.launchpad.net/bugs/1619420 ** Changed in: lsb Status: Confirmed => Invalid ** Changed in: lsb (Ubuntu) Status: Confirmed => Invalid ** This bug has been marked a duplicate of bug 1619420 snappy removal of dpkg-query breaks lsb_release --all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1662357 Title: Can't use lsb_release on Ubuntu Core 16 Status in lsb: Invalid Status in Snappy: New Status in Snappy Ubuntu Core: New Status in lsb package in Ubuntu: Invalid Bug description: brian-murray@localhost:~$ snap list Name Version Rev Developer Notes core 16.04.1 888 canonical - brian-murray@localhost:~$ lsb_release Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '16.04 LTS' brian-murray@localhost:~$ lsb_release -a Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '6.06 LTS' To manage notifications about this bug go to: https://bugs.launchpad.net/lsb/+bug/1662357/+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 1677924] Re: Local privilege escalation via guest user login
This security fix seems to have caused some fallout ... see bug 1733557 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1677924 Title: Local privilege escalation via guest user login Status in Light Display Manager: Fix Released Status in Light Display Manager 1.18 series: Fix Released Status in Light Display Manager 1.20 series: Fix Released Status in Light Display Manager 1.22 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Xenial: Fix Released Status in lightdm source package in Yakkety: Fix Released Status in lightdm source package in Zesty: Fix Released Bug description: It was discovered that a local attacker could watch for lightdm's guest-account script to create a /tmp/guest-XX file and then quickly create the lowercase representation of the guest user's home directory before lightdm could. This allowed the attacker to have control of the guest user's home directory and, subsequently, gain control of an arbitrary directory in the filesystem which could lead to privilege escalation. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1677924/+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 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
I have verified the xenial one with a locally created core and kernel snap now (as mentioned before I can not verify it on artful simply because there is no Ubuntu Core for this release, using the deb from proposed on an artful desktop does not show any regressions though) ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Committed Status in initramfs-tools-ubuntu-core source package in Artful: New Bug description: [TEST CASE] * this will be tested by the snappy team * without this fix the dragonboard will not boot on a freshly written image [REGRESSION POTENTIAL] * low as it only fixes an invalid string trying to boot a new dragonboard image results in: error: assertion is signed with expired public key "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by canonical this is due to a clock skew that should normally be catched by the fixrtc script in the initrd. the script is supposed to check the last mount time of the writable disk (SD card) and if this does not exist, fall back to the filesystem creation time ... in former versions of mkfs.ext4 the last mount time filed was simply left empty, so this fallback worked fine ... in xenial the fields now look like: Filesystem created: Tue Sep 13 17:32:20 2016 Last mount time: n/a Last write time: Tue Sep 13 17:32:20 2016 due to the script running with "set -e" it falls over on the "n/a" and exists before falling back to creation time, there needs to be a check added for the "n/a" string now. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+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 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
since we dont build ubuntu core images based on the artful archive this would just be cosmetic ... (but yeah, technically we could also upload it to artful ... xenial and bionic are the critical ones here though) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Bug description: [TEST CASE] * this will be tested by the snappy team * without this fix the dragonboard will not boot on a freshly written image [REGRESSION POTENTIAL] * low as it only fixes an invalid string trying to boot a new dragonboard image results in: error: assertion is signed with expired public key "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by canonical this is due to a clock skew that should normally be catched by the fixrtc script in the initrd. the script is supposed to check the last mount time of the writable disk (SD card) and if this does not exist, fall back to the filesystem creation time ... in former versions of mkfs.ext4 the last mount time filed was simply left empty, so this fallback worked fine ... in xenial the fields now look like: Filesystem created: Tue Sep 13 17:32:20 2016 Last mount time: n/a Last write time: Tue Sep 13 17:32:20 2016 due to the script running with "set -e" it falls over on the "n/a" and exists before falling back to creation time, there needs to be a check added for the "n/a" string now. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+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 1724756] Re: Updates Available pops up when Check set to Never
** Also affects: update-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1724756 Title: Updates Available pops up when Check set to Never Status in unattended-upgrades package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: In Software & Updates with Automatically Check set to Never and When Security Updates Available set to Display Immediately the system is apparently still checking for updates, as the Software Updates Available is shown when there are updates. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unattended-upgrades 0.93.1ubuntu2.3 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 19 07:26:44 2017 InstallationDate: Installed on 2014-10-21 (1093 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to zesty on 2017-04-26 (175 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "0"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-09-17T16:17:23.842448 mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 2017-05-19T08:12:23.274412 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1724756/+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 1692494] Re: klibc does not support reboot arguments
** Also affects: klibc (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1692494 Title: klibc does not support reboot arguments Status in klibc package in Ubuntu: New Status in klibc source package in Xenial: New Status in klibc package in Debian: New Bug description: ... so we cannot do things like "reboot recovery" in devices that follow the Android partitions conventions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+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 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
Setting snappy task to fix committed, core the ships the workaround from https://github.com/snapcore/core/pull/60 ...until systemd grows the correct defaults via an SRU ** Changed in: snappy Status: New => Fix Committed ** Changed in: snappy Importance: Undecided => High ** Changed in: snappy Assignee: (unassigned) => Michael Vogt (mvo) -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: Fix Committed Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Bug description: Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During the test the dhcp server records correctly leases and their duration. We check directly from console the network interface setting with the tool ip, checking continuously the value for ip address and valid_lft fields for the interested network interface. Please note that if the ip address setting are the same between leases the problem doesn’t jump out. Please note that if the ip address setting are different between lease the problem jumps out and it is very bad: Typically the lease time on consumer router are about some day, then a board that change ip between lease loses the network connectivity for some day without a direct action. Please, after a confirmation from your side of the issue, could you fix the problem or escalate the issue at the upstream project? We are available for further testing. Below syslog annotated with ip address state: Oct 4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:49:25 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:23 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:54:23 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:54:23 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:55:43 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:57:13 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:57:14 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:58:44 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:58:46 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:00:16 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:00
[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
** Summary changed: - Networkd fail to set ip address between leases if ip address changes + Networkd fail to set ip address between leases if ip address changes on UbuntuCore ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: snappy 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: New Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Bug description: Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During the test the dhcp server records correctly leases and their duration. We check directly from console the network interface setting with the tool ip, checking continuously the value for ip address and valid_lft fields for the interested network interface. Please note that if the ip address setting are the same between leases the problem doesn’t jump out. Please note that if the ip address setting are different between lease the problem jumps out and it is very bad: Typically the lease time on consumer router are about some day, then a board that change ip between lease loses the network connectivity for some day without a direct action. Please, after a confirmation from your side of the issue, could you fix the problem or escalate the issue at the upstream project? We are available for further testing. Below syslog annotated with ip address state: Oct 4 09:48:06 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:49:36 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:49:25 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:49:26 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:49:26 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:49:26 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:49:37 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:51:07 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:51:09 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:52:39 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:52:40 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:54:10 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:11 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:55:41 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:54:23 localhost systemd-timesyncd[996]: Network configuration changed, trying to establish connection. Oct 4 09:54:23 localhost systemd[1]: Starting Update resolvconf for networkd DNS... Oct 4 09:54:23 localhost systemd-timesyncd[996]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). Oct 4 09:54:23 localhost systemd[1]: Started Update resolvconf for networkd DNS. Oct 4 09:55:43 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:57:13 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:57:14 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 09:58:44 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 09:58:46 localhost rsyslogd-2007: action 'action 11' suspended, next retry is Wed Oct 4 10:00:16 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Oct 4 10:00:17 localhost rsyslogd-2007: action
[Touch-packages] [Bug 1718900] [NEW] typo in manpage "statisfy"
Public bug reported: the description for "upgrade" in the apt manpage says: New packages will be installed if required to statisfy dependencies, but existing packages will never be removed. this should probably rather read "satisfy" ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1718900 Title: typo in manpage "statisfy" Status in apt package in Ubuntu: New Bug description: the description for "upgrade" in the apt manpage says: New packages will be installed if required to statisfy dependencies, but existing packages will never be removed. this should probably rather read "satisfy" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1718900/+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 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
please note that this rule will also likely be used inside the initrd to set up the console for encyption key input and there will be no systemd around ... you probably want to rather handle it conditionally so it is still available when creating an initrd ... -- 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/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+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 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
might be that we need it on Ubuntu Core (and server) though ... so installing the rule at all should probably be conditional ... -- 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/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: New Status in console-setup package in Ubuntu: Triaged Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+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 1619258] Re: netplan should allow NICs to be disconnected and not stall the boot
Note that this bug is about Ubuntu Core (xenial), i dont think we use systemd-networkd in the rest of xenial ( https://lists.ubuntu.com/archives/ubuntu-devel/2016-January/039066.html ) -- 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/1619258 Title: netplan should allow NICs to be disconnected and not stall the boot Status in Snappy: Confirmed Status in nplan package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: in older snappy image we used to set "allow-hotplug" in /etc/network/interfaces.d/ when configuring a NIC to avoid the boot to completely stall or to be stuck for 5min when trying to find an internet connection. with recent versions of netplan the configuration seems to be back to require a network to be up before moving on with them boot so that booting takes forever until the network connection times out. netplan should make the system check the physical link status when trying to bring up a network device instead of stalling the boot. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1619258/+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 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore
@xnox "As on the 18th systemd migrated that can set Nice in artful yet you disabled it on the 18th." our development focus is 16.04 and we do not have release specific systemd units for the forward ported snapd packages so the comment will have to stay in until xenial has a fixed systemd ... -- 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/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore Status in Snap Layer: New Status in snapd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Artful: Fix Released Bug description: It looks like snapd in ubuntu-core (2.26.14 here) has been modified to use a negative Nice value in systemd. Systemd seems to treat a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values as those are restricted to the real root user. I believe the optimal fix would be for systemd to ignore permission errors when attempting to setup such custom nice values in containers but if that can't be resolved quickly, then it means that snapd will now fail to start inside containers. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here). To manage notifications about this bug go to: https://bugs.launchpad.net/layer-snap/+bug/1709536/+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 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore
this is in snapd since may https://github.com/snapcore/snapd/pull/3270 why did this break all of a sudden ? -- 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/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore Status in snapd: New Status in systemd package in Ubuntu: Fix Committed Bug description: It looks like snapd in ubuntu-core (2.26.14 here) has been modified to use a negative Nice value in systemd. Systemd seems to treat a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values as those are restricted to the real root user. I believe the optimal fix would be for systemd to ignore permission errors when attempting to setup such custom nice values in containers but if that can't be resolved quickly, then it means that snapd will now fail to start inside containers. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here). To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1709536/+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 1702252] [NEW] upstart-sysv in xenial has a copy/paste error in the package description
Public bug reported: Looks like the description of upstart-sysv was a copy/paste from the systemd-sysv package. The text talks confusingly about installing systemd-sysv in the last paragraph... Description-en: event-based init daemon - SysV links upstart is a replacement for the /sbin/init daemon which handles starting of tasks and services during boot, stopping them during shutdown and supervising them while the system is running. . This package provides the manual pages and links needed for upstart to replace sysvinit. Installing systemd-sysv will overwrite /sbin/init with a link to upstart. ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Affects: upstart (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: upstart (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1702252 Title: upstart-sysv in xenial has a copy/paste error in the package description Status in upstart package in Ubuntu: New Status in upstart source package in Xenial: New Bug description: Looks like the description of upstart-sysv was a copy/paste from the systemd-sysv package. The text talks confusingly about installing systemd-sysv in the last paragraph... Description-en: event-based init daemon - SysV links upstart is a replacement for the /sbin/init daemon which handles starting of tasks and services during boot, stopping them during shutdown and supervising them while the system is running. . This package provides the manual pages and links needed for upstart to replace sysvinit. Installing systemd-sysv will overwrite /sbin/init with a link to upstart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1702252/+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 1696981] Re: fixrtc is ineffective when there is no battery for the RTC
well, i'd rather find out why the original fixrtc did not work in the first place ... dumpe2fs output of the respecitve failing disk captured from an initrd shell on first boot of the device would be interesting debug data -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1696981 Title: fixrtc is ineffective when there is no battery for the RTC Status in initramfs-tools package in Ubuntu: New Bug description: When there is no battery for the RTC, fixrtc is not able to find a good enough date. To fix the clock, this script is using the last time the root filesystem was mounted, but as that is done before there is any network, and as after a reboot/poweroff the RTC time is always reset (because time is not kept due to lack of battery), the mount time will never be good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+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 1687507] Re: Memory leak (/run file system filling up)
expanding on: "looking at the listing" i meant to say, there are only very few related snap bits in there, many are simply from the OS itself including apt updates and the like that are completely unrelated to snaps. -- 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/1687507 Title: Memory leak (/run file system filling up) Status in snapd: Invalid Status in systemd package in Ubuntu: New Bug description: (see also related discussion on forum: https://forum.snapcraft.io/t/memory-run-memory-file-system-leaking-with-snap-install-remove/429 ) I have a CI system which tests my snap and does a lot install/remove of snap packages as part of the operation on some small virtual systems. My /tmp is 200MB This is on latest Ubuntu Server 16.04 (all packages updated), with the alternative 4.8 kernel from the Ubuntu Repo) At this time, all packages are updated to latest version. I have this bug for a long time (since I've started building up a CI infrastructure for the Snap - approx 6 months ago), so this is not a new bug, but only the more frequent snap testing made it obvious. In my system the /tmp filesystem fills up - within approx 2..7 days I'm out of space on it. All the space is used up under /run/udev/data/ and approx 95% of the files (around 45'000) start with +cgroup prefix I can provide access to a VM in this state if requested (IPv6 only, contact me with SSH key) Here is some current output (not yet out of space... may need another day) root@ci-comp17-dut:~# df Filesystem 1K-blocksUsed Available Use% Mounted on udev 1002892 0 1002892 0% /dev tmpfs 204796 148196 56600 73% /run /dev/vda16060608 3462628 2267076 61% / tmpfs1023976 0 1023976 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs1023976 0 1023976 0% /sys/fs/cgroup /dev/loop0 80256 80256 0 100% /snap/core/1577 /dev/loop1 77056 77056 0 100% /snap/core/1337 /dev/loop2 80256 80256 0 100% /snap/core/1441 tmpfs 204796 0204796 0% /run/user/0 /dev/loop3 14592 14592 0 100% /snap/frr/x1 Attached is a full dir output of /run/udev/data (ls_run_udev_data.log) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1687507/+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 1687507] Re: Memory leak (/tmp file system filling up)
looking at the listing as well as the fact that the syslog excerpt on the forum is full of: Apr 28 09:36:48 ci-comp11-dut systemd[1]: Started Session 1816 of user root. this is either a systemd bug or a bug with the way systemd is used in the CI ... moving it to systemd to have a systemd maintainer take a look. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd Status: New => Invalid ** Summary changed: - Memory leak (/tmp file system filling up) + Memory leak (/run file system filling up) -- 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/1687507 Title: Memory leak (/run file system filling up) Status in snapd: Invalid Status in systemd package in Ubuntu: New Bug description: (see also related discussion on forum: https://forum.snapcraft.io/t/memory-run-memory-file-system-leaking-with-snap-install-remove/429 ) I have a CI system which tests my snap and does a lot install/remove of snap packages as part of the operation on some small virtual systems. My /tmp is 200MB This is on latest Ubuntu Server 16.04 (all packages updated), with the alternative 4.8 kernel from the Ubuntu Repo) At this time, all packages are updated to latest version. I have this bug for a long time (since I've started building up a CI infrastructure for the Snap - approx 6 months ago), so this is not a new bug, but only the more frequent snap testing made it obvious. In my system the /tmp filesystem fills up - within approx 2..7 days I'm out of space on it. All the space is used up under /run/udev/data/ and approx 95% of the files (around 45'000) start with +cgroup prefix I can provide access to a VM in this state if requested (IPv6 only, contact me with SSH key) Here is some current output (not yet out of space... may need another day) root@ci-comp17-dut:~# df Filesystem 1K-blocksUsed Available Use% Mounted on udev 1002892 0 1002892 0% /dev tmpfs 204796 148196 56600 73% /run /dev/vda16060608 3462628 2267076 61% / tmpfs1023976 0 1023976 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs1023976 0 1023976 0% /sys/fs/cgroup /dev/loop0 80256 80256 0 100% /snap/core/1577 /dev/loop1 77056 77056 0 100% /snap/core/1337 /dev/loop2 80256 80256 0 100% /snap/core/1441 tmpfs 204796 0204796 0% /run/user/0 /dev/loop3 14592 14592 0 100% /snap/frr/x1 Attached is a full dir output of /run/udev/data (ls_run_udev_data.log) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1687507/+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 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM
note that i see the non-starting wayland session on a 16.04 system that does not have the unity8-desktop-session package installed, x11 gnome as well as unity (7) start just fine and there is no trace of any unity8 packages on this laptop. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1632772 Title: Login option 'GNOME on Wayland' does not start from LightDM Status in Ubuntu GNOME: Invalid Status in unity8-desktop-session: Won't Fix Status in gnome-session package in Ubuntu: Invalid Status in lightdm package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: Won't Fix Bug description: When picking GNOME on Wayland as session and attempting to login from LightDM then it fails, all you see is a black screen with a blinking cursor. However, manually running: $ dbus-run-session gnome-shell --display-server --wayland from the console/vt1 (Ctrl+Alt+F1) seems to work. But from LightDM it does not work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-session-wayland 3.20.2-1ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 12 18:06:13 2016 InstallationDate: Installed on 2013-12-26 (1020 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1632772/+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 1614459] Re: daily upgrade on 16.04 hangs
*** This bug is a duplicate of bug 1579135 *** https://bugs.launchpad.net/bugs/1579135 @johnny ... note that you replied to a duplicate ... if you can not update apparmor with an up-to-date kernel that has the fix for the issue, you most likely face a new and unrelated bug and should file it as such. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1614459 Title: daily upgrade on 16.04 hangs Status in apparmor package in Ubuntu: Invalid Bug description: doing a regular upgrade using the update-manager popup on a 16.04 machine, the update process hangs: Setting up apparmor (2.10.95-0ubuntu2.2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' it sits at the last line forever. this machine has no fancy os level hacks, no PPAs in use, was installed with 12.04 initially and has only seen LTS->LTS upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1614459/+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 1662357] Re: Can't use lsb_release on Ubuntu Core 16
*** This bug is a duplicate of bug 1619420 *** https://bugs.launchpad.net/bugs/1619420 ** This bug has been marked a duplicate of bug 1619420 snappy removal of dpkg-query breaks lsb_release --all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1662357 Title: Can't use lsb_release on Ubuntu Core 16 Status in Snappy: New Status in Snappy Ubuntu Core: New Status in lsb package in Ubuntu: New Bug description: brian-murray@localhost:~$ snap list Name Version Rev Developer Notes core 16.04.1 888 canonical - brian-murray@localhost:~$ lsb_release Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '16.04 LTS' brian-murray@localhost:~$ lsb_release -a Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '6.06 LTS' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1662357/+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 1658909] Re: lsb_release fails in classic (arm64)
*** This bug is a duplicate of bug 1650207 *** https://bugs.launchpad.net/bugs/1650207 ** This bug has been marked a duplicate of bug 1650207 original lsb-release file should be preserved for classic mode -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1658909 Title: lsb_release fails in classic (arm64) Status in Snappy: Confirmed Status in lsb package in Ubuntu: Invalid Status in lsb-release package in Ubuntu: Invalid Bug description: I'm getting this when running lsb_release with classic on a Dragonboard: $ lsb_release -a Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '16.04 LTS' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1658909/+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 1659534] Re: userdel doesn't supports extrausers
** Also affects: snappy Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1659534 Title: userdel doesn't supports extrausers Status in Snappy: New Status in shadow package in Ubuntu: New Bug description: On an Ubuntu Core system is impossible to delete an user from the extrausers db: root@localhost:/# userdel --extrausers alice userdel: unrecognized option '--extrausers' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+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 1658909] Re: lsb_release fails in classic (arm64)
potentially a duplicate of Bug #1650207 (for which a fix was just uploaded for the edge channel) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1658909 Title: lsb_release fails in classic (arm64) Status in Snappy: Confirmed Status in lsb package in Ubuntu: Invalid Status in lsb-release package in Ubuntu: Invalid Bug description: I'm getting this when running lsb_release with classic on a Dragonboard: $ lsb_release -a Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '16.04 LTS' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1658909/+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 1658909] Re: lsb_release fails in classic (arm64)
lsb_release is not supposed to be working in core (it should not even be shipped, but there is an issue with a dependency from cloud-init) ... that said, it should work in the classic dimension if it is installed there though. ** Changed in: lsb (Ubuntu) Status: New => Invalid ** Changed in: lsb-release (Ubuntu) Status: New => Invalid ** Changed in: snappy Importance: Undecided => Medium ** Changed in: snappy Assignee: (unassigned) => Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1658909 Title: lsb_release fails in classic (arm64) Status in Snappy: Confirmed Status in lsb package in Ubuntu: Invalid Status in lsb-release package in Ubuntu: Invalid Bug description: I'm getting this when running lsb_release with classic on a Dragonboard: $ lsb_release -a Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '16.04 LTS' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1658909/+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 1576282] Re: Snaps built from deb can't be gettext translated
note that snaps do not get unpacked, they get mounted as-is (compressed) ... so the unpacked size should not really matter.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1576282 Title: Snaps built from deb can't be gettext translated Status in Canonical System Image: In Progress Status in Snapcraft: New Status in Ubuntu App Platform: In Progress Status in snapcraft package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Currently it seems not possible to have working gettext translations without included a patch glibc build in your snap - the core image doesn't have locales definition that can be worked around by including locales definitions in the snap, though that's tedious, ideally snapcraft would help there - traditional desktop applications are built with calls to 'bindtextdomain ("domain", LOCALEDIR)', where LOCALDIR is defined at buildtime and so pointing to /usr there seems to be no way to redirect to another directory at runtime - desktop applications needs system library translations sometime which means langpacks need to be included in snaps To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1576282/+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 1647333] Re: adduser misses extrausers support for group management
the added patch enables usermod to use the extrausers db for groups, we are still missing a similar patch for gpasswd which i'm now working on ** Patch added: "fix a typo ..." https://bugs.launchpad.net/snappy/+bug/1647333/+attachment/487/+files/usermod-extrausers-group.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1647333 Title: adduser misses extrausers support for group management Status in Snappy: New Status in adduser package in Ubuntu: Confirmed Status in shadow package in Ubuntu: In Progress Bug description: trying to add a user to a group in /var/lib/extrausers by using the --extrausers option results in a "group not found" error despite adduser being supposed to be able to do this kind of modification. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647333/+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 1647333] Re: adduser misses extrausers support for group management
** Patch added: "usermod-extrausers-group.patch" https://bugs.launchpad.net/snappy/+bug/1647333/+attachment/4799934/+files/usermod-extrausers-group.patch ** Changed in: shadow (Ubuntu) Assignee: (unassigned) => Oliver Grawert (ogra) ** Changed in: shadow (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1647333 Title: adduser misses extrausers support for group management Status in Snappy: New Status in adduser package in Ubuntu: Confirmed Status in shadow package in Ubuntu: In Progress Bug description: trying to add a user to a group in /var/lib/extrausers by using the --extrausers option results in a "group not found" error despite adduser being supposed to be able to do this kind of modification. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647333/+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 1620559] Re: /etc/resolv.conf is empty on snappy
** Changed in: snappy Status: New => Incomplete ** Changed in: snappy Status: Incomplete => Fix Released -- 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/1620559 Title: /etc/resolv.conf is empty on snappy Status in Snappy: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Bug description: we currently have no working resolver on snappy installs, /etc/resolv.conf is the boilerplate one. on the low level we seem to have DNS from the DHCP server though ogra@localhost:~$ grep -r DNS= /run/systemd/netif /run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205 /run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205 /run/systemd/netif/links/3:MDNS=no ogra@localhost:~$ SRU INFORMATION === Fix: https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=0a96feb1561 Test case: I cannot reproduce this in a VM or normal laptop, this is somehow specific to the reporter's hardware/DHCP server config. * Configure systemd-networkd for an ethernet interface, either directly or via netplan; remove it from /etc/network/interfaces{,.d} * Reboot. * With current xenial's systemd, if /run/systemd/netif/state does not have "DNS=" then /etc/resolv.conf will not have any nameserver. * With the proposed update, /etc/resolv.conf should have the DHCP-provided nameserver. Regression potential: Low; in 16.04 LTS we do not configure networkd by any Ubuntu tool, so networkd is not widely used there yet. For systems which do use it it could happen that interface-specific DNS servers now appear in resolv.conf that should not be global -- but we do not have anything that would configure or obey this setup in 16.04. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1620559/+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 1647333] Re: adduser misses extrausers support for group management
adduser is actually calling groupadd in the backend ... adding the shadow package as well.. ** Also affects: shadow (Ubuntu) Importance: Undecided Status: New ** Changed in: shadow (Ubuntu) Status: New => Confirmed ** Changed in: shadow (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1647333 Title: adduser misses extrausers support for group management Status in Snappy: New Status in adduser package in Ubuntu: Confirmed Status in shadow package in Ubuntu: Confirmed Bug description: trying to add a user to a group in /var/lib/extrausers by using the --extrausers option results in a "group not found" error despite adduser being supposed to be able to do this kind of modification. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647333/+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 1647333] [NEW] adduser misses extrausers support for group management
Public bug reported: trying to add a user to a group in /var/lib/extrausers by using the --extrausers option results in a "group not found" error despite adduser being supposed to be able to do this kind of modification. ** Affects: snappy Importance: Undecided Status: New ** Affects: adduser (Ubuntu) Importance: Undecided Status: New ** Also affects: adduser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1647333 Title: adduser misses extrausers support for group management Status in Snappy: New Status in adduser package in Ubuntu: New Bug description: trying to add a user to a group in /var/lib/extrausers by using the --extrausers option results in a "group not found" error despite adduser being supposed to be able to do this kind of modification. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647333/+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 1644468] Re: pull to refresh text to bright on scopes with new theme
confirming it is fixed in rc-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1644468 Title: pull to refresh text to bright on scopes with new theme Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: the rc-proposed images recently got new scopes and a brighter theme. with this theme the "pull to refresh" text in the scopes became unreadable bright (see attached screenshot). the grey tone of the font is only very minimally brighter than the background. if we want to keep the text there it should be changed to have more contrast so it is readable. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644468/+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 1644237] Re: unity8 fails to start as guest user
related to bug 1593407 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1644237 Title: unity8 fails to start as guest user Status in Canonical System Image: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: This is shown in unity8.log: [2016-11-23 15:59:25.820868] mirserver: Starting ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132): Throw in function mir::DefaultServerConfiguration::the_graphics_platform():: Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Exception while creating graphics platform ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245): Throw in function mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const string&, const string&, const std::shared_ptr&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Nested Mir Platform Connection Error: Failed to connect to server socket: Permission denied [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start initctl: No such variable: UNITY_MIR_SOCKET running current zesty, but I had the same problem on yakkety too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644237/+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 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1611010 Title: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: '' Status in apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in ubiquity source package in Xenial: New Bug description: Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com /daily-live/current/ HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd Preconditions: W10+Xenial xerus installed, internet connection, 3rd party sw and updates selected Steps to reproduce: 1º Click something else on Installation type screen>select /dev/sdaX where Xenial is installed, use it to mount / and leave some space to create the /home partition(ext4) 2º Then click back and select erase ubuntu 16.04.1 and install Yakkety 3º Installation starts Current result: After a little time installing it crashes and a window shows up to let the user know that some info is being gathered to send it to developers, and finally firefox opens on the bug report web on ubiquity package Expected result: No crashes during installation ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.5 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CasperVersion: 1.376 Date: Mon Aug 8 15:50:56 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808) ProcEnviron: LANGUAGE=es_ES.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1611010/+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 1607291] Re: Dual SIM devices show "No SIM" icon in indicators if there is only one SIM installed
well, what about devices like the MXpro5 where when you have an SD card you can not actually use a second sim, it is quite unlogical to show that icon when you have a shared slot that is used in other context ... could we make this not a conditional thing so that if a carrier requires it it can be turned on (with some gsettings key from the custom tarball) for the phones this carrier offers ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1607291 Title: Dual SIM devices show "No SIM" icon in indicators if there is only one SIM installed Status in indicator-network package in Ubuntu: Invalid Bug description: rc-proposed, since about a week I have 2 SIM icons in the indicators panel. One that shows the signal strength for the installed SIM card (which is fine), and then a second one which shows the "no SIM card" icon. When there is a SIM card installed, the indicator should not show a "no SIM installed" icon, even though there would be a second free slot available. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1607291/+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 1620559] Re: /etc/resolv.conf is empty on snappy
works fine now ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1620559 Title: /etc/resolv.conf is empty on snappy Status in Snappy: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: we currently have no working resolver on snappy installs, /etc/resolv.conf is the boilerplate one. on the low level we seem to have DNS from the DHCP server though ogra@localhost:~$ grep -r DNS= /run/systemd/netif /run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205 /run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205 /run/systemd/netif/links/3:MDNS=no ogra@localhost:~$ SRU INFORMATION === Fix: https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=0a96feb1561 Test case: I cannot reproduce this in a VM or normal laptop, this is somehow specific to the reporter's hardware/DHCP server config. * Configure systemd-networkd for an ethernet interface, either directly or via netplan; remove it from /etc/network/interfaces{,.d} * Reboot. * With current xenial's systemd, if /run/systemd/netif/state does not have "DNS=" then /etc/resolv.conf will not have any nameserver. * With the proposed update, /etc/resolv.conf should have the DHCP-provided nameserver. Regression potential: Low; in 16.04 LTS we do not configure networkd by any Ubuntu tool, so networkd is not widely used there yet. For systems which do use it it could happen that interface-specific DNS servers now appear in resolv.conf that should not be global -- but we do not have anything that would configure or obey this setup in 16.04. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1620559/+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 1620559] [NEW] /etc/resolv.conf is empty on snappy
Public bug reported: we currently have no working resolver on snappy installs, /etc/resolv.conf is the boilerplate one. on the low level we seem to have DNS from the DHCP server though ogra@localhost:~$ grep -r DNS= /run/systemd/netif /run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205 /run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205 /run/systemd/netif/links/3:MDNS=no ogra@localhost:~$ ** Affects: snappy Importance: Critical Status: New ** Affects: systemd (Ubuntu) Importance: Critical Status: New ** Also affects: snappy Importance: Undecided Status: New ** Changed in: snappy Importance: Undecided => Critical ** Changed in: systemd (Ubuntu) Importance: Undecided => Critical -- 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/1620559 Title: /etc/resolv.conf is empty on snappy Status in Snappy: New Status in systemd package in Ubuntu: New Bug description: we currently have no working resolver on snappy installs, /etc/resolv.conf is the boilerplate one. on the low level we seem to have DNS from the DHCP server though ogra@localhost:~$ grep -r DNS= /run/systemd/netif /run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205 /run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205 /run/systemd/netif/links/3:MDNS=no ogra@localhost:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1620559/+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 1595558] Re: sudo doesn't have /snap/bin in PATH
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1595558 Title: sudo doesn't have /snap/bin in PATH Status in snapd package in Ubuntu: Won't Fix Status in sudo package in Ubuntu: Fix Released Status in snapd source package in Xenial: Won't Fix Status in sudo source package in Xenial: Fix Committed Bug description: [ SRU Justification ] Snap may contain sysadmin tools as well. They are currently hard to invoke because /snap/bin is not in the PATH when sudo is used because the default secure_path of sudoers does not have it. [ SRU Test Case ] 1. sudo snap install hello-world 2. sudo hello-world 3. verify that this fails with "command not found" 4. install sudo from xenial-proposed 5. verify that sudo hello-world now works [ Regression Potential ] - may trigger conffile prompts on upgrade [Original report] $ nextcloud.occ # prints output $ sudo nextcloud.occ sudo: nextcloud.occ: command not found I need to do `sudo /snap/bin/nextcloud.occ` if I want it to run. $ sudo env | grep PATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1595558/+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 1614459] Re: daily upgrade on 16.04 hangs
while the above report was about my desktop i experience the same on my laptop ... pastebin with the oops is at http://paste.ubuntu.com/23067239/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1614459 Title: daily upgrade on 16.04 hangs Status in apparmor package in Ubuntu: New Bug description: doing a regular upgrade using the update-manager popup on a 16.04 machine, the update process hangs: Setting up apparmor (2.10.95-0ubuntu2.2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' it sits at the last line forever. this machine has no fancy os level hacks, no PPAs in use, was installed with 12.04 initially and has only seen LTS->LTS upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1614459/+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 1614459] Re: daily upgrade on 16.04 hangs
digging deeper i found a kernel Oops http://paste.ubuntu.com/23067079/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1614459 Title: daily upgrade on 16.04 hangs Status in apparmor package in Ubuntu: New Bug description: doing a regular upgrade using the update-manager popup on a 16.04 machine, the update process hangs: Setting up apparmor (2.10.95-0ubuntu2.2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' it sits at the last line forever. this machine has no fancy os level hacks, no PPAs in use, was installed with 12.04 initially and has only seen LTS->LTS upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1614459/+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 1614459] Re: daily upgrade on 16.04 hangs
for a test i commented out the above update-rc.d code, seemingly this is not the issue, now i have apparmor hanging the same way, just without the error messages on "apt-get -f install" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1614459 Title: daily upgrade on 16.04 hangs Status in apparmor package in Ubuntu: New Bug description: doing a regular upgrade using the update-manager popup on a 16.04 machine, the update process hangs: Setting up apparmor (2.10.95-0ubuntu2.2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' it sits at the last line forever. this machine has no fancy os level hacks, no PPAs in use, was installed with 12.04 initially and has only seen LTS->LTS upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1614459/+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 1614459] Re: daily upgrade on 16.04 hangs
looking at /var/lib/dpkg/info/apparmor.postinst, i see: # Automatically added by dh_installinit if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ]; then if [ -x "/etc/init.d/apparmor" ]; then update-rc.d apparmor start 37 S . >/dev/null || true fi fi ogra@anubis:~$ ls -lh /etc/init.d/apparmor -rwxr-xr-x 1 root root 6,0K Feb 16 2016 /etc/init.d/apparmor ogra@anubis:~$ dpkg -S /etc/init.d/apparmor apparmor: /etc/init.d/apparmor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1614459 Title: daily upgrade on 16.04 hangs Status in apparmor package in Ubuntu: New Bug description: doing a regular upgrade using the update-manager popup on a 16.04 machine, the update process hangs: Setting up apparmor (2.10.95-0ubuntu2.2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' it sits at the last line forever. this machine has no fancy os level hacks, no PPAs in use, was installed with 12.04 initially and has only seen LTS->LTS upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1614459/+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 1614459] Re: daily upgrade on 16.04 hangs
re-running "apt-get -f install" in a terminal i can not even ctrl-C out of the hanging apt process, i have to kill -9 the underlying dpkg to get a prompt back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1614459 Title: daily upgrade on 16.04 hangs Status in apparmor package in Ubuntu: New Bug description: doing a regular upgrade using the update-manager popup on a 16.04 machine, the update process hangs: Setting up apparmor (2.10.95-0ubuntu2.2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' it sits at the last line forever. this machine has no fancy os level hacks, no PPAs in use, was installed with 12.04 initially and has only seen LTS->LTS upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1614459/+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 1614459] [NEW] daily upgrade on 16.04 hangs
Public bug reported: doing a regular upgrade using the update-manager popup on a 16.04 machine, the update process hangs: Setting up apparmor (2.10.95-0ubuntu2.2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' it sits at the last line forever. this machine has no fancy os level hacks, no PPAs in use, was installed with 12.04 initially and has only seen LTS->LTS upgrades. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Description changed: doing a regular upgrade using the update-manager popup on a 16.04 machine, the update process hangs: Setting up apparmor (2.10.95-0ubuntu2.2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' it sits at the last line forever. this machine has no fancy os level - hacks, np PPAs in user, was installed with 12.04 initially and has only + hacks, no PPAs in use, was installed with 12.04 initially and has only seen LTS->LTS upgrades. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1614459 Title: daily upgrade on 16.04 hangs Status in apparmor package in Ubuntu: New Bug description: doing a regular upgrade using the update-manager popup on a 16.04 machine, the update process hangs: Setting up apparmor (2.10.95-0ubuntu2.2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' it sits at the last line forever. this machine has no fancy os level hacks, no PPAs in use, was installed with 12.04 initially and has only seen LTS->LTS upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1614459/+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 1612951] Re: /etc/default/keyboard ignored after upgrade to 16.04
your missed one command .. see the top of /etc/default/keyboard. it points to the documentation at /usr/share/doc/keyboard- configuration/README.Debian that tells what you have to do after manually changing the config.. -- 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/1612951 Title: /etc/default/keyboard ignored after upgrade to 16.04 Status in console-setup package in Ubuntu: New Bug description: I just upgraded Xubuntu 14.04 to 16.04, and I noticed my compose key wasn't working in any application in X. I verified my compose key was still set up in /etc/default/keyboard: XKBOPTIONS="compose:ralt" I googled around and ran these two commands: sudo dpkg-reconfigure keyboard-configuration sudo update-initramfs -u But the problem persists. I notice that the compose key works fine in the console, but it doesn't work in any X application, including the terminal. Here's my current workaround: echo "setxkbmap -option compose:ralt" >> ~/.xprofile It looks like I'm not the only one experiencing this, and it doesn't seem limited to Xfce: https://ubuntu-mate.community/t/setxkbmap-option-in-etc-default- keyboard-not-working/4054 $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.108ubuntu15.2 Candidate: 1.108ubuntu15.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 13 09:04:10 2016 InstallationDate: Installed on 2014-05-08 (827 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: Upgraded to xenial on 2016-08-05 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1612951/+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 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
it was closed as invalid for indicator-power because the problem is in powerd ... so a new task against powerd was opened -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in powerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+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 1603358] Re: no tap to click in unity8
oh ! i just tested it again on the laptop, something has changed that made it work since last week :) invalidating the bug ** Changed in: mir (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603358 Title: no tap to click in unity8 Status in Mir: New Status in mir package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: trying out the unity8 session in xenial there is no way to make tap to click on a touchpad work in unity8 ... clicking the touchpad button works fine but means you need both hands for click+drag which breaks the workflow enough to make the touchpad rather unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603358/+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 1603358] Re: no tap to click in unity8
@lukas: yes, it doesnt seem to do anything -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603358 Title: no tap to click in unity8 Status in Mir: New Status in mir package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: trying out the unity8 session in xenial there is no way to make tap to click on a touchpad work in unity8 ... clicking the touchpad button works fine but means you need both hands for click+drag which breaks the workflow enough to make the touchpad rather unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603358/+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 1603358] Re: no tap to click in unity8
@pat: i can confirm it works with a logitech diNovo BT keyboard on the M10 ... but not on the dell XPS13 (first gen) internal touchpad -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603358 Title: no tap to click in unity8 Status in Mir: New Status in mir package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: trying out the unity8 session in xenial there is no way to make tap to click on a touchpad work in unity8 ... clicking the touchpad button works fine but means you need both hands for click+drag which breaks the workflow enough to make the touchpad rather unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603358/+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 1604611] Re: [webapp-container] Undocumented command line option --no-australia-mode
So because i work for Canonical i am not allowed to have any humour ? Please note that I do not work on the phone, I do develop apps for it in my spare time just like you (and I did work on the initial creation of the phone images 2 years ago), obviously nearly everyone else got the joke of having such an absurdly named option and I am really sorry that you did not ... Bug #1563398 exists since a while, is in the process of being fixed for you and was mentioned in the mail thread before. I am not sure what to say really, or why this bothers you so much, it was a joke, I apologized when I noticed you didn't get it and I am not willing to wipe any humour from my mail conversations because you feel like people working for canonical should not have any ... Lets please get on with life and not pull that little misunderstanding out of proportion ... once the phone got switched to a snappy based system you have all the right to blame me for bugs and I will try to remember to only talk to you in a very serious tone then, so we do not repeat this ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1604611 Title: [webapp-container] Undocumented command line option --no-australia- mode Status in webbrowser-app package in Ubuntu: Invalid Bug description: It has been reported by personnel related to Canonical [1] that webapp-container has a (obviously undocumented) command line option `--no-australia-mode`. [1] https://lists.launchpad.net/ubuntu-phone/msg21542.html Analysis - This option doesn't show up when webapp-container is run with `--help`. - The webapp-container binary doesn't refuse to run when the `--no-australia-mode` option is used. Expected Result --- - Running webapp-container with `--help` should mention and explain the `--no-australia-mode` option (if it exists). - The webapp-container binary should refuse to run with unknown or invalid command line options. See Also - Bug 1554202 for related information. - Bug 1563398 / comment 11 (Set the front camera as the default for video media requests) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1604611/+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 1603358] Re: no tap to click in unity8
when researching this i found https://freedesktop.org/wiki/Software/libinput/tapping/ and https://cgit.freedesktop.org/wayland/libinput/commit/?id=2219c12c3aa45b80f235e761e87c17fb9ec70eae so it seems that Mir needs to do something to enable it again -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603358 Title: no tap to click in unity8 Status in Mir: New Status in mir package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: trying out the unity8 session in xenial there is no way to make tap to click on a touchpad work in unity8 ... clicking the touchpad button works fine but means you need both hands for click+drag which breaks the workflow enough to make the touchpad rather unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603358/+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 1603358] [NEW] no tap to click in unity8
Public bug reported: trying out the unity8 session in xenial there is no way to make tap to click on a touchpad work in unity8 ... clicking the touchpad button works fine but means you need both hands for click+drag which breaks the workflow enough to make the touchpad rather unusable. ** Affects: mir (Ubuntu) Importance: Undecided Status: New ** Description changed: trying out the unity8 session in xenial there is no way to make tap to click on a touchpad work in unity8 ... clicking the touchpad button - works fine but means you need both hands fro click+drag which breaks the + works fine but means you need both hands for click+drag which breaks the workflow enough to make the touchpad rather unusable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603358 Title: no tap to click in unity8 Status in mir package in Ubuntu: New Bug description: trying out the unity8 session in xenial there is no way to make tap to click on a touchpad work in unity8 ... clicking the touchpad button works fine but means you need both hands for click+drag which breaks the workflow enough to make the touchpad rather unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1603358/+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 1480654] Re: [regression] Input focus delay after switching app back into focus since OTA5
well, it was never actually solved completely ... (as you can see by daniels comment above) i suspect there are still multipple bugs ... there is: a) the spread animation getting stuck a few pixels before the window sits completely straight on the screen for a split second when you switch apps (doesnt happen every time but well noticeable throughout the day). b) input on re-focus (doesnt matter if with or without spread involved) for all apps using a webview acts delayed (try my G+ app or any other that uses the bottom navigation, bring the app in focus and try to swipe the navigation menu up ... you will notice it takes 3-4 swipes til there is any reaction)) c) general input delay when unlocking ... it usually takes multiple swipes after unlocking to get a reaction (for spread, launcher or app interaction) i think a) and c) are still this bug ... b) should perhaps be an oxide or unity8 one assuming mzanetti is right above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1480654 Title: [regression] Input focus delay after switching app back into focus since OTA5 Status in Canonical System Image: Confirmed Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: i am not sure if it started with OTA4 or OTA5 but since one of the recent OTA upgrades my arale takes between half a second and one second before an app takes input again when one switches it from background back into focus. i'm talking about apps that were only sigstopped, not OOM killed here (i.e. no restart involved, just sigcont). this used to be instant before and gives a weird feeling of sluggishness. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480654/+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 1578628] Re: Upstart log files are not reopened after rolling
note that ~/.cache/upstart is not /var/log/upstart :) so we are looking at session logs here ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1578628 Title: Upstart log files are not reopened after rolling Status in Canonical System Image: Confirmed Status in upstart package in Ubuntu: New Bug description: Seen on stable and proposed vivid based touch images I noticed on two of my devices that after a scheduled rolling of the files in /var/log/upstart that there were no active *.log files at all. The config for upstart includes nocreate but this has always been this way. Is this intended or did something change in logrotate? A similar bug report states that the files will be opened on a subsequent write from the upstart process, but this is clearly not happening. See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation and perhaps bug #1350782 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578628/+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 1578628] Re: Upstart log files are not reopened after rolling
well, if there are actual writes the files should be re-created ... are they also not created newly after a reboot ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1578628 Title: Upstart log files are not reopened after rolling Status in Canonical System Image: Confirmed Status in upstart package in Ubuntu: New Bug description: Seen on stable and proposed vivid based touch images I noticed on two of my devices that after a scheduled rolling of the files in /var/log/upstart that there were no active *.log files at all. The config for upstart includes nocreate but this has always been this way. Is this intended or did something change in logrotate? A similar bug report states that the files will be opened on a subsequent write from the upstart process, but this is clearly not happening. See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation and perhaps bug #1350782 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578628/+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 1342123] Re: evolution-calendar-factory always running with high memory usage
if you have issues with evolution-data-server on a desktop install your chances are way higher to have some desktop people look at it if you file a new bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1342123 Title: evolution-calendar-factory always running with high memory usage Status in Canonical System Image: Confirmed Status in evolution-data-server package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: At boot the process is using over 100MB on my mako (build 129) I sync'd a fairly large set of calendar events from google previously Does this process need to be running all the time? Can we streamline it to not read so much of the data set, which it appears to be doing? With no calendar entries (i.e. removing .local/share/evolution/xxx/calendar.ics) the process still uses over 30MB (looking at RSS with ps aux --sort -rss ) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1342123/+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 1342123] Re: evolution-calendar-factory always running with high memory usage
hmm, this bug seems ot have been dragged away from the actual topic by the audience, please note that this bug talks about phone and tablet installs (as the "Canonical System Image" task implies) where we use a reduced and slightly different installation compared to desktops (and definitely no support for things like ~/.config/autostart and such). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1342123 Title: evolution-calendar-factory always running with high memory usage Status in Canonical System Image: Confirmed Status in evolution-data-server package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: At boot the process is using over 100MB on my mako (build 129) I sync'd a fairly large set of calendar events from google previously Does this process need to be running all the time? Can we streamline it to not read so much of the data set, which it appears to be doing? With no calendar entries (i.e. removing .local/share/evolution/xxx/calendar.ics) the process still uses over 30MB (looking at RSS with ps aux --sort -rss ) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1342123/+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 1552371] Re: Unexpected display on
On the MX4 specifically there is also the issue with the "home" button staying active for about 30sec when the display was turned off, when shoving the phone into your pocket it is easy to create a button press event if you do not wait long enough. -- 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/1552371 Title: Unexpected display on Status in Canonical System Image: Confirmed Status in Mir: New Status in Unity System Compositor: New Status in bluez package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: NOTE: kgunn suggests this bug be about 1) not 2) here 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. Freiza & Arale 2) I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+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 1480654] Re: [regression] Input focus delay after switching app back into focus since OTA5
note that this behaviour is even more noticeable on turbo, seems the Mir slowness is out of the way there, it takes between two and three seconds for an app to accept input ... of which one second is a little "hang" of the animation when flipping it into focus before it sits straight on the screen, this seems like some blocking code in unity8. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1480654 Title: [regression] Input focus delay after switching app back into focus since OTA5 Status in Canonical System Image: New Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: i am not sure if it started with OTA4 or OTA5 but since one of the recent OTA upgrades my arale takes between half a second and one second before an app takes input again when one switches it from background back into focus. i'm talking about apps that were only sigstopped, not OOM killed here (i.e. no restart involved, just sigcont). this used to be instant before and gives a weird feeling of sluggishness. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480654/+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 1545802] Re: activeFocus not being forwarded to TextInput inside TextField
note that the same seems to happen at the login window (waking up the device has the password field auto-focused, enabling a BT keyboard unsets the focus and you have to tap it first) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1545802 Title: activeFocus not being forwarded to TextInput inside TextField Status in Canonical System Image: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Status in webbrowser-app package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: Haven’t managed to reproduce with a standalone example yet, but I can reliably reproduce the following issue with the browser app on a tablet with a bluetooth keyboard connected (this needs to be on a tablet so that the wide layout of the app is used, for example with a Nexus 7 (flo) in landscape orientation): 1) launch the browser app with a bluetooth keyboard attached and ensure that the current tab is not a new tab 2) press Ctrl+T to open a new tab Expected result: the address bar gets active focus so that the user can start entering a URL right away Current result: the address bar gets active focus for a fraction of a second, then looses it. When that happens, pressing Ctrl+L (which forces focus on the address bar) doesn’t fix it. I added some debugging to the browser (printing Window.activeFocusItem whenever it changes), and it appears that when initially forcing active focus on the address bar the QQuickTextInput inside it gets active focus, then looses it. At that point the activeFocusItem is the TextField, but it doesn’t forward it to QQuickTextInput inside itself. That situation can be remedied by using a bluetooth mouse to click on the address bar, which restores active focus on the QQuickTextInput. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545802/+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 1580785] Re: Provide the option to update before running the complete OOBE
it should also not just have a "skip" option but rather make it slightly "harder" to skip the upgrade... like having to check a checkbox "yes, i really do not want to upgrade now, let me skip", before the skip button goes active ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1580785 Title: Provide the option to update before running the complete OOBE Status in Canonical System Image: Confirmed Status in Ubuntu UX: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: Something seen on other platforms, can be useful to provide a better initial user experience. Prompt the user early on offering an update, would be possible after the Wifi is configured. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580785/+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 1579101] [NEW] no keyboard shortcuts in webapp containers
Public bug reported: having a keyboard attached to the phone/tablet i can use things like Ctrl-R or Alt+Left/Right to navigate in the webbrowser app ... none of these shortcuts work in webapp-containers though (while scrolling via cursor keys and PgUp and PgDn works) ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Summary changed: - no keyboard shortcuts in webapp contianers + no keyboard shortcuts in webapp containers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1579101 Title: no keyboard shortcuts in webapp containers Status in webbrowser-app package in Ubuntu: New Bug description: having a keyboard attached to the phone/tablet i can use things like Ctrl-R or Alt+Left/Right to navigate in the webbrowser app ... none of these shortcuts work in webapp-containers though (while scrolling via cursor keys and PgUp and PgDn works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1579101/+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 1565236] Re: AltGr not working on external keyboards
i created http://paste.ubuntu.com/16187883/ that at least gives you the AltGr keys in the terminal app (on a german kbd, other langs might have different needs indeed). save it as /home/phablet/.config/com.ubuntu.terminal/Layouts/AltGrKeys.json on your device and you will have the keys in terminals "extra keys" selection. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1565236 Title: AltGr not working on external keyboards Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in mir package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: Using my keyboard with Spanish layout: - PC: Everything works perfect. - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú). Extra info: - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 (http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2) - Ubuntu Desktop: 12.04 - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+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 1565236] Re: Spanish keyboard layout wrong
same goes for a german keyboard where AltGr is needed for @ € ~ and | signs ... ** Summary changed: - Spanish keyboard layout wrong + AltGr not working on external keyboards -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1565236 Title: AltGr not working on external keyboards Status in Canonical System Image: Confirmed Status in Mir: New Status in mir package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: Using my keyboard with Spanish layout: - PC: Everything works perfect. - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú). Extra info: - Keyboard: http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2 - Ubuntu Desktop: 12.04 - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+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 1350598] Re: AppArmor policy compile improvements
hmm, does generating on shutdown really make sense ? what if i skip a few upgrades (which is a pretty common case, i.e. my moms phone only gets updated when i visit her. and i know enough (non geeky) people that simply ignore upgrade notifications altogether on their phones), meanwhile apparmor changed profile handling in an incompatible way ... the new binary wont be available until after reboot to generate the profiles the right way, so i end up with broken profiles after reboot ... while it is surely easy on deb based systems simply because you have the new app binary around, doing it before reboot on system-image or snappy installs means your existing binary needs to be forward compatible to all possible changes that may come with the new binary only after reboot (this could be a one version, a ten version or even a 100 version jump depending how long you didnt upgrade). having it done after reboot and simply implementing some feedback UI seems to make a lot more sense as it has a lot less risks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1350598 Title: AppArmor policy compile improvements Status in AppArmor: Triaged Status in Canonical System Image: Confirmed Status in apparmor package in Ubuntu: Triaged Status in click-apparmor package in Ubuntu: Triaged Bug description: apparmor_parser can take a long time to compile policy especially when there is a lot of policy, so we want to utilize compiled cache profile as much as possible. Cache files will have to be regenerated in the following cases: * the kernel .features file is updated (eg, new features are added to apparmor in the new kernel) * apparmor itself is updated * on devices with click packages, apparmor-easyprof-ubuntu and/or click-apparmor is updated As of 2014-10-02, what can be expected is: - Systems with system-image updates (eg, Ubuntu Touch): - First boot will use the precompiled cache files in the rootfs or custom tarball and be fast - Reboots will use the cache files on the device and be fast - First boots after upgrades will use the cache files on the device if the above conditions are not met and be fast - Production devices will not meet any of those conditions except under exceptional and rare circumstances (eg, major OS upgrades like 14.10 to 15.04) and be fast - First boots after upgrades that meet one of the conditions will need to regenerate the cache. This can happen on development releases where the kernel features file, apparmor, apparmor-easyprof-ubuntu or click-apparmor are still under development and getting updates - Systems with apt updates (eg, current Ubuntu Desktop and Server): - First boot will compile cache files - Reboots will use the cache files on the machine and be fast - First boots after upgrades will use the cache files on the machine if the above conditions are not met and be fast - Stable releases of Ubuntu will not meet any of those conditions except under exceptional and rare circumstances (eg, major OS upgrades like 14.10 to 15.04) and be fast - First boots after upgrades that meet one of the above conditions will need to regenerate the cache. This can happen on development releases where the kernel features file, apparmor, apparmor-easyprof-ubuntu or click-apparmor are still under development and getting updates In addition to the above, updates to only apparmor-easyprof-ubuntu will regenerate the cache files for only the policy that is affected (eg, if there is a change to the location policy group in policy version 1.2, only apps using this policy version and this policy group will need to be recompiled). Planned improvements (in order of most likely to be done first): 1. Finetuning the checks to invalidate the cache (eg, .md5sums could only be for /etc/apparmor.d/abstractions, ...): WONTFIX (will want an md5sum on apparmor_parser since it could change the cache and the md5sum will always change. Furthermore, apparmor-easyprof-ubuntu is all policy so there is no gain there. click-apparmor could possibly benefit, but it doesn't change often and when it does, it is typically for policy) 2. Investigate ways to utilize the custom tarball and rootfs precompiled cache files on upgrades when apparmor, apparmor-easyprof-ubuntu and click-apparmor are updated: DONE 3. Improve cache handling for app store apps (eg, having the app store server precompile them so that the device can download them when it needs to rather than having to regenerate them itself): WONTFIX (doesn't scale) 4. For systems with apt upgrades, compile the policy either during install or on kernel upgrade rather than on boot. For systems with read-only fs-s
[Touch-packages] [Bug 1547033] Re: make snappy's /etc/mtab symlink agree to tmpfiles.d/debian.conf
seems to work fine now ... closing ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: snappy Status: New => Fix Released ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released ** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided => Medium ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Oliver Grawert (ogra) -- 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/1547033 Title: make snappy's /etc/mtab symlink agree to tmpfiles.d/debian.conf Status in Snappy: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: booting a snappy system which comes with a readonly file system that carries /etc/mtab as pre-created link in the readonly area of the fs (pointing to /proc/mounts), we always get an error message on boot when systemd-tmpfiles tries to re-create the mtab link. systemd-tmpfiles should instead check if /etc/mtab is already there, is a link and points to the desired target. in this case it should just skip the creation attempt gracefully without error. Feb 17 18:56:51 localhost systemd[1]: Starting Create Volatile Files and Directories... Feb 17 18:56:51 localhost systemd-tmpfiles[631]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log" , ignoring. Feb 17 18:56:51 localhost systemd-tmpfiles[631]: symlink(../proc/self/mounts, /etc/mtab) failed: Read-only file syste m Feb 17 18:56:51 localhost systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAIL URE To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1547033/+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 1547033] Re: make snappy's /etc/mtab symlink agree to tmpfiles.d/debian.conf
yes, uploaded that this morning, i can check with tomorrows image if livecd-rootfs makes it out of the beta queue before (currently in "needs approval" state) -- 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/1547033 Title: make snappy's /etc/mtab symlink agree to tmpfiles.d/debian.conf Status in Snappy: New Status in systemd package in Ubuntu: Confirmed Bug description: booting a snappy system which comes with a readonly file system that carries /etc/mtab as pre-created link in the readonly area of the fs (pointing to /proc/mounts), we always get an error message on boot when systemd-tmpfiles tries to re-create the mtab link. systemd-tmpfiles should instead check if /etc/mtab is already there, is a link and points to the desired target. in this case it should just skip the creation attempt gracefully without error. Feb 17 18:56:51 localhost systemd[1]: Starting Create Volatile Files and Directories... Feb 17 18:56:51 localhost systemd-tmpfiles[631]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log" , ignoring. Feb 17 18:56:51 localhost systemd-tmpfiles[631]: symlink(../proc/self/mounts, /etc/mtab) failed: Read-only file syste m Feb 17 18:56:51 localhost systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAIL URE To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1547033/+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 1547033] Re: make snappy's /etc/mtab symlink agree to tmpfiles.d/debian.conf
hmm, i just noticed the symlink in debian.conf is relative, not absolute ... so trying that again with two dots in front :) -- 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/1547033 Title: make snappy's /etc/mtab symlink agree to tmpfiles.d/debian.conf Status in Snappy: New Status in systemd package in Ubuntu: Confirmed Bug description: booting a snappy system which comes with a readonly file system that carries /etc/mtab as pre-created link in the readonly area of the fs (pointing to /proc/mounts), we always get an error message on boot when systemd-tmpfiles tries to re-create the mtab link. systemd-tmpfiles should instead check if /etc/mtab is already there, is a link and points to the desired target. in this case it should just skip the creation attempt gracefully without error. Feb 17 18:56:51 localhost systemd[1]: Starting Create Volatile Files and Directories... Feb 17 18:56:51 localhost systemd-tmpfiles[631]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log" , ignoring. Feb 17 18:56:51 localhost systemd-tmpfiles[631]: symlink(../proc/self/mounts, /etc/mtab) failed: Read-only file syste m Feb 17 18:56:51 localhost systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAIL URE To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1547033/+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 1547033] Re: make snappy's /etc/mtab symlink agree to tmpfiles.d/debian.conf
sadly even with making the link point to /proc/self7mounts it still happens: Mar 23 11:55:12 localhost systemd-tmpfiles[628]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Mar 23 11:55:12 localhost systemd-tmpfiles[628]: symlink(../proc/self/mounts, /etc/mtab) failed: Read-only file system Mar 23 11:55:12 localhost systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- 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/1547033 Title: make snappy's /etc/mtab symlink agree to tmpfiles.d/debian.conf Status in Snappy: New Status in systemd package in Ubuntu: Confirmed Bug description: booting a snappy system which comes with a readonly file system that carries /etc/mtab as pre-created link in the readonly area of the fs (pointing to /proc/mounts), we always get an error message on boot when systemd-tmpfiles tries to re-create the mtab link. systemd-tmpfiles should instead check if /etc/mtab is already there, is a link and points to the desired target. in this case it should just skip the creation attempt gracefully without error. Feb 17 18:56:51 localhost systemd[1]: Starting Create Volatile Files and Directories... Feb 17 18:56:51 localhost systemd-tmpfiles[631]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log" , ignoring. Feb 17 18:56:51 localhost systemd-tmpfiles[631]: symlink(../proc/self/mounts, /etc/mtab) failed: Read-only file syste m Feb 17 18:56:51 localhost systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAIL URE To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1547033/+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 1560899] Re: sqlite triggers syscall error if run as root in snappy default confinement (fchown not allowed)
** Changed in: sqlite3 (Ubuntu) Status: New => Confirmed ** Changed in: sqlite3 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1560899 Title: sqlite triggers syscall error if run as root in snappy default confinement (fchown not allowed) Status in sqlite3 package in Ubuntu: Confirmed Bug description: Code currently tries to change user to uid if geteuid is root; this call triggers fchown syscall exception in snappy. Good news is that in snappy this call is a null op in theory as both geteuid as well as uid are 0, so changing wouldnt do anything. Fix is to not try to chown if geteuid is equal to uid (e.g. if it would be a null op anyway). "Safe" patch should be: Index: sqlite3-3.11.0/src/os_unix.c === --- sqlite3-3.11.0.orig/src/os_unix.c +++ sqlite3-3.11.0/src/os_unix.c @@ -497,7 +497,7 @@ static struct unix_syscall { */ static int robustFchown(int fd, uid_t uid, gid_t gid){ #if defined(HAVE_FCHOWN) - return osGeteuid() ? 0 : osFchown(fd,uid,gid); + return osGeteuid() || osGeteuid() == uid ? 0 : osFchown(fd,uid,gid); #else return 0; #endif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1560899/+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 1552774] Re: /var/spool/cron/ should be readwrite for phablet user
this is a long standing annoyance and easy to fix in /etc/system-image /writable-paths so users can use cron from the commandline if desired ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1552774 Title: /var/spool/cron/ should be readwrite for phablet user Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: Confirmed Bug description: Hi. "crontab -e" is broken unless /var/spool/cron/ is writable. Currently (build 266 vegetahd) this happens: crontab: installing new crontab /var/spool/cron/: mkstemp: Read-only file system crontab: edits left in /tmp/crontab.xvMe2c/crontab phablet@orc:~/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552774/+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 1552774] Re: /var/spool/cron/ should be readwrite for phablet user
the line to be added to the above file would be: /var/spool/cronautopersistent transition none -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1552774 Title: /var/spool/cron/ should be readwrite for phablet user Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: Confirmed Bug description: Hi. "crontab -e" is broken unless /var/spool/cron/ is writable. Currently (build 266 vegetahd) this happens: crontab: installing new crontab /var/spool/cron/: mkstemp: Read-only file system crontab: edits left in /tmp/crontab.xvMe2c/crontab phablet@orc:~/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552774/+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 1517305] Re: Visibility of progress during "update-initramfs" not given
** Package changed: initramfs-tools-ubuntu-core (Ubuntu) => initramfs- tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1517305 Title: Visibility of progress during "update-initramfs" not given Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Hello shortlog: If a new user installs ubuntu and as post-installation task runs the available updates he certainly gets a new Kernel too – this means that the initRAMFS will be updated. Depending on the Hardware equipment, this can be a rather timely + CPU consuming process. The chance to believe the PC stalls is at high risk w/o visual feedback. If the electricty or internet-connection fails to work - and the process was interupted, the system will call for a $ E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem If the user does so, he gets no visul feedback in terms of a progressbar - this could be possible in the terminal! Remember the Knoppix CD, where the boot-process in itself was visible? https://www.youtube.com/watch?v=rPsFmMFwScU @ 5min11sec the progress bar in question is visible. (Source: Semper-Video - Knoppix Rettungs-CD, 2008/07) It can build trust to see that a process is evolving - even the Redmond-guys respect this - still with W10 - giving a visual feedback to the user - not just a blinking cursor. Thinking this would not be to timely to implement. Thanks for making Ubuntu better every day! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1517305/+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