[Touch-packages] [Bug 1424992] [NEW] files in /tmp not being cleared on boot
Public bug reported: My system has been booted for 2 1/2 hours and yet /tmp contains old files from 2015-02-19. $ sudo systemctl|grep tmpfiles systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories $ sudo journalctl -a|grep tmpfiles Feb 24 07:27:08 faire systemd-tmpfiles[701]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Feb 24 07:41:38 faire systemd-tmpfiles[31258]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. $ sudo du -sh /tmp 481M/tmp $ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --clean /usr/lib/tmpfiles.d/tmp.conf Reading config file "/usr/lib/tmpfiles.d/tmp.conf". Running clean action for entry v /tmp Running clean action for entry X /tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp Running clean action for entry x /tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-* Running clean action for entry x /var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-* Running clean action for entry X /var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp $ sudo du -sh /tmp 481M/tmp $ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-3ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 24 09:55:29 2015 InstallationDate: Installed on 2014-04-11 (318 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro init=/lib/systemd/systemd quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2014-05-08 (291 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1424992 Title: files in /tmp not being cleared on boot Status in systemd package in Ubuntu: New Bug description: My system has been booted for 2 1/2 hours and yet /tmp contains old files from 2015-02-19. $ sudo systemctl|grep tmpfiles systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories $ sudo journalctl -a|grep tmpfiles Feb 24 07:27:08 faire systemd-tmpfiles[701]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Feb 24 07:41:38 faire systemd-tmpfiles[31258]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. $ sudo du -sh /tmp 481M/tmp $ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --clean /usr/lib/tmpfiles.d/tmp.conf Reading config file "/usr/lib/tmpfiles.d/tmp.conf". Running clean action for entry v /tmp Running clean action for entry X /tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp Running clean action for entry x /tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-* Running clean action for entry x /var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-* Running clean action for entry X /var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp $ sudo du -sh /tmp 481M/tmp $ ProblemType: Bug DistroRelease: Ubuntu
[Touch-packages] [Bug 1424992] Re: files in /tmp not being cleared on boot
Thanks Martin! -- 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/1424992 Title: files in /tmp not being cleared on boot Status in systemd package in Ubuntu: Fix Committed Status in systemd package in Debian: New Bug description: My system has been booted for 2 1/2 hours and yet /tmp contains old files from 2015-02-19. $ sudo systemctl|grep tmpfiles systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories $ sudo journalctl -a|grep tmpfiles Feb 24 07:27:08 faire systemd-tmpfiles[701]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Feb 24 07:41:38 faire systemd-tmpfiles[31258]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. $ sudo du -sh /tmp 481M/tmp $ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --clean /usr/lib/tmpfiles.d/tmp.conf Reading config file "/usr/lib/tmpfiles.d/tmp.conf". Running clean action for entry v /tmp Running clean action for entry X /tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp Running clean action for entry x /tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-* Running clean action for entry x /var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-* Running clean action for entry X /var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp $ sudo du -sh /tmp 481M/tmp $ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-3ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 24 09:55:29 2015 InstallationDate: Installed on 2014-04-11 (318 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro init=/lib/systemd/systemd quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2014-05-08 (291 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1424992/+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 1425685] Re: Missing input sanitation in upstart logrotation cronjob
Note - this problem only affects vivid fwics. Further, it does not affect Touch (since that uses Upstart as PID 1). -- 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/1425685 Title: Missing input sanitation in upstart logrotation cronjob Status in upstart package in Ubuntu: New Bug description: Ubuntu Vivid 1504 (development branch) installs an insecure upstart logrotation script which will read user-supplied data from /run/user/[uid]/upstart/sessions and pass then unsanitized to an env command. As user run directory is user-writable, the user may inject arbitrary commands into the logrotation script, which will be executed during daily cron job execution around midnight with root privileges. Problematic part of /etc/cron.daily/upstart: for session in /run/user/*/upstart/sessions/* do env $(cat $session) /sbin/initctl emit rotate-logs >/dev/null 2>&1 || true done On a system with e.g. libpam-systemd installed, standard login on TTY or via SSH will create the directory /run/user/[uid] writable to the user. By preparing a suitable session file, user supplied code will be run during the daily cron-jobs. See [1] for more information. # lsb_release -rd Description:Ubuntu Vivid Vervet (development branch) Release:15.04 # apt-cache policy upstart-bin upstart-bin: Installed: 1.13.2-0ubuntu7 Candidate: 1.13.2-0ubuntu7 Version table: *** 1.13.2-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main i386 Packages 100 /var/lib/dpkg/status [1] http://www.halfdog.net/Security/2015/UpstartLogrotationPrivilegeEscalation/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1425685/+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 1425685] Re: Missing input sanitation in upstart logrotation cronjob
** Changed in: upstart (Ubuntu) Assignee: (unassigned) => James Hunt (jamesodhunt) ** Changed in: upstart (Ubuntu) Importance: Undecided => High -- 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/1425685 Title: Missing input sanitation in upstart logrotation cronjob Status in upstart package in Ubuntu: New Bug description: Ubuntu Vivid 1504 (development branch) installs an insecure upstart logrotation script which will read user-supplied data from /run/user/[uid]/upstart/sessions and pass then unsanitized to an env command. As user run directory is user-writable, the user may inject arbitrary commands into the logrotation script, which will be executed during daily cron job execution around midnight with root privileges. Problematic part of /etc/cron.daily/upstart: for session in /run/user/*/upstart/sessions/* do env $(cat $session) /sbin/initctl emit rotate-logs >/dev/null 2>&1 || true done On a system with e.g. libpam-systemd installed, standard login on TTY or via SSH will create the directory /run/user/[uid] writable to the user. By preparing a suitable session file, user supplied code will be run during the daily cron-jobs. See [1] for more information. # lsb_release -rd Description:Ubuntu Vivid Vervet (development branch) Release:15.04 # apt-cache policy upstart-bin upstart-bin: Installed: 1.13.2-0ubuntu7 Candidate: 1.13.2-0ubuntu7 Version table: *** 1.13.2-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main i386 Packages 100 /var/lib/dpkg/status [1] http://www.halfdog.net/Security/2015/UpstartLogrotationPrivilegeEscalation/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1425685/+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 1425685] Re: Missing input sanitation in upstart logrotation cronjob
** Changed in: upstart (Ubuntu) Status: New => Fix Committed -- 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/1425685 Title: Missing input sanitation in upstart logrotation cronjob Status in upstart package in Ubuntu: Fix Committed Bug description: Ubuntu Vivid 1504 (development branch) installs an insecure upstart logrotation script which will read user-supplied data from /run/user/[uid]/upstart/sessions and pass then unsanitized to an env command. As user run directory is user-writable, the user may inject arbitrary commands into the logrotation script, which will be executed during daily cron job execution around midnight with root privileges. Problematic part of /etc/cron.daily/upstart: for session in /run/user/*/upstart/sessions/* do env $(cat $session) /sbin/initctl emit rotate-logs >/dev/null 2>&1 || true done On a system with e.g. libpam-systemd installed, standard login on TTY or via SSH will create the directory /run/user/[uid] writable to the user. By preparing a suitable session file, user supplied code will be run during the daily cron-jobs. See [1] for more information. # lsb_release -rd Description:Ubuntu Vivid Vervet (development branch) Release:15.04 # apt-cache policy upstart-bin upstart-bin: Installed: 1.13.2-0ubuntu7 Candidate: 1.13.2-0ubuntu7 Version table: *** 1.13.2-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main i386 Packages 100 /var/lib/dpkg/status [1] http://www.halfdog.net/Security/2015/UpstartLogrotationPrivilegeEscalation/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1425685/+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 1425685] Re: Missing input sanitation in upstart logrotation cronjob
Fixed in upstart 1.13.2-0ubuntu9, currently in the proposed pocket. -- 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/1425685 Title: Missing input sanitation in upstart logrotation cronjob Status in upstart package in Ubuntu: Fix Committed Bug description: Ubuntu Vivid 1504 (development branch) installs an insecure upstart logrotation script which will read user-supplied data from /run/user/[uid]/upstart/sessions and pass then unsanitized to an env command. As user run directory is user-writable, the user may inject arbitrary commands into the logrotation script, which will be executed during daily cron job execution around midnight with root privileges. Problematic part of /etc/cron.daily/upstart: for session in /run/user/*/upstart/sessions/* do env $(cat $session) /sbin/initctl emit rotate-logs >/dev/null 2>&1 || true done On a system with e.g. libpam-systemd installed, standard login on TTY or via SSH will create the directory /run/user/[uid] writable to the user. By preparing a suitable session file, user supplied code will be run during the daily cron-jobs. See [1] for more information. # lsb_release -rd Description:Ubuntu Vivid Vervet (development branch) Release:15.04 # apt-cache policy upstart-bin upstart-bin: Installed: 1.13.2-0ubuntu7 Candidate: 1.13.2-0ubuntu7 Version table: *** 1.13.2-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main i386 Packages 100 /var/lib/dpkg/status [1] http://www.halfdog.net/Security/2015/UpstartLogrotationPrivilegeEscalation/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1425685/+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 1429756] Re: FTBFS: test_job_process fails in majority of cases
'mk-sbuild vivid' currently gives an error: You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: systemd-sysv : Conflicts: upstart but 1.13.2-0ubuntu9 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). -- 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/1429756 Title: FTBFS: test_job_process fails in majority of cases Status in upstart package in Ubuntu: New Status in upstart source package in Vivid: New Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+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 1429756] Re: FTBFS: test_job_process fails in majority of cases
mk-sbuild now fails with a different error: Setting up udev (219-4ubuntu3) ... A chroot environment has been detected, udev not started. /var/lib/dpkg/info/udev.postinst: 35: /var/lib/dpkg/info/udev.postinst: update-initramfs: not found dpkg: error processing package udev (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: udev E: Sub-process /usr/bin/dpkg returned an error code (1) But back to the test failure... this test has been running successfully on all platforms for a long time (3+ years). It's possible that the test itself is racy and that a recent change in a different package has exposed that. Do we know when this test first started failing (and ideally what changes triggered it (kernel/libc))? -- 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/1429756 Title: FTBFS: test_job_process fails in majority of cases Status in upstart package in Ubuntu: New Status in upstart source package in Vivid: New Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+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 1429756] Re: FTBFS: test_job_process fails in majority of cases
It does indeed seem to be related to the kernel. I've just run that specific test 77 times on an amd64 system running a 3.18.0-11 kernel with no failures. Once the broken deps issue is resolved, I'll retest on the same system running the latest 3.19 kernel. -- 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/1429756 Title: FTBFS: test_job_process fails in majority of cases Status in upstart package in Ubuntu: New Status in upstart source package in Vivid: New Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+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 1429756] Re: FTBFS: test_job_process fails in majority of cases
Updating the amd64 system, I see the failure on the 2nd test run. The Upstart logging code doesn't seem to be the culprit fwics meaning the most likely area is the pty-handling code (either in upstart or in the kernel). -- 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/1429756 Title: FTBFS: test_job_process fails in majority of cases Status in upstart package in Ubuntu: New Status in upstart source package in Vivid: New Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+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 1429756] Re: FTBFS: test_job_process fails in majority of cases
The "good" news is that this test failure is a real bug: running 1024 job instances of what is effectively the failing tests shows... - 3.18 kernel: 0 job instances have incorrect size. - 3.19 kernel: 848 job instances have the **incorrect** size (!!) Figures are from a fully-updated amd64 vivid system booted to use Upstart and simply toggling the kernel being used. I've tried to recreate the failure using script(1) and dd(1), but so far this has proven unsuccessful. -- 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/1429756 Title: FTBFS: test_job_process fails in majority of cases Status in upstart package in Ubuntu: New Status in upstart source package in Vivid: New Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+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 1429756] Re: FTBFS: test_job_process fails in majority of cases
Some quick tests suggest that this issue only seems to affect long runs of nul bytes (even if they are terminated by visible chars + a '\n'). -- 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/1429756 Title: FTBFS: test_job_process fails in majority of cases Status in upstart package in Ubuntu: New Status in upstart source package in Vivid: New Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+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 1429756] Re: FTBFS: test_job_process fails in majority of cases
** Changed in: upstart (Ubuntu Vivid) Assignee: (unassigned) => James Hunt (jamesodhunt) -- 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/1429756 Title: FTBFS: test_job_process fails in majority of cases Status in upstart package in Ubuntu: New Status in upstart source package in Vivid: New Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+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 1430403] Re: ubuntu-touch livefs builds kill upstart in host
conf_reload_path() calls nih_file_read(). Although the return value of that call is checked, the code is wrong. It looks likely that this bug crept in since, unfortunately, the documentation for nih_file_read() is incorrect. It states: Returns: newly allocated string or NULL if insufficient memory. ... whereas it *should* state: Returns: newly allocated string or NULL on raised error. As such, if the call to nih_file_read() fails, the error object should be destroyed before continuing to avoid the crash seen above. ** Changed in: upstart (Ubuntu) Importance: Undecided => High ** Changed in: upstart (Ubuntu) Assignee: (unassigned) => James Hunt (jamesodhunt) -- 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/1430403 Title: ubuntu-touch livefs builds kill upstart in host Status in upstart package in Ubuntu: Confirmed Bug description: ubuntu-touch livefs builds have started killing upstart in the host system (in this case, precise, although a similar bug appears to be present in current versions). The livefs build completes, but the host dies shortly after launchpad-buildd starts trying to remove the build chroot. The kernel log looks like this: Mar 10 13:46:55 allspice kernel: [3743880.621603] init: /home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf: Unable to reload configuration after override deletion Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core dumped Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core dumped This appears to be because a couple of functions call conf_reload_path, which may leave an nih_error in place if nih_file_read fails, but then do not dispose of the nih_error. The pattern near the end of conf_file_visitor (in precise) is probably appropriate. We're working around this to some extent in livecd-rootfs by removing the .override files first, but it should never be possible for a chroot to crash the host's init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+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 1430403] Re: ubuntu-touch livefs builds kill upstart in host
Attached is a minimal fix for the bug. Note that since this issue does not affect newer releases, we cannot follow the usual process of testing in the dev release. However, as can be seen, the fix is small and quite clear. Note that the change to main.c is required to make upstart build on precise (looks like there was a bzr / source package disconnect somewhere). ** Patch added: "upstart-bug-1430403.diff" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+attachment/4340271/+files/upstart-bug-1430403.diff -- 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/1430403 Title: ubuntu-touch livefs builds kill upstart in host Status in upstart package in Ubuntu: Confirmed Bug description: ubuntu-touch livefs builds have started killing upstart in the host system (in this case, precise, although a similar bug appears to be present in current versions). The livefs build completes, but the host dies shortly after launchpad-buildd starts trying to remove the build chroot. The kernel log looks like this: Mar 10 13:46:55 allspice kernel: [3743880.621603] init: /home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf: Unable to reload configuration after override deletion Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core dumped Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core dumped This appears to be because a couple of functions call conf_reload_path, which may leave an nih_error in place if nih_file_read fails, but then do not dispose of the nih_error. The pattern near the end of conf_file_visitor (in precise) is probably appropriate. We're working around this to some extent in livecd-rootfs by removing the .override files first, but it should never be possible for a chroot to crash the host's init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+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 1430403] Re: ubuntu-touch livefs builds kill upstart in host
lp keeps timing out on me when I attempt to attach a file. Meantime... I've managed to force a crash after ~150 iterations of bug-1430403.sh using http://people.canonical.com/~jhunt/upstart/bug-1430403.tgz. To recreate: $ sudo tar xvfz bug-1430403.tgz $ sudo bash bug-1430403.sh -- 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/1430403 Title: ubuntu-touch livefs builds kill upstart in host Status in upstart package in Ubuntu: Confirmed Bug description: ubuntu-touch livefs builds have started killing upstart in the host system (in this case, precise, although a similar bug appears to be present in current versions). The livefs build completes, but the host dies shortly after launchpad-buildd starts trying to remove the build chroot. The kernel log looks like this: Mar 10 13:46:55 allspice kernel: [3743880.621603] init: /home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf: Unable to reload configuration after override deletion Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core dumped Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core dumped This appears to be because a couple of functions call conf_reload_path, which may leave an nih_error in place if nih_file_read fails, but then do not dispose of the nih_error. The pattern near the end of conf_file_visitor (in precise) is probably appropriate. We're working around this to some extent in livecd-rootfs by removing the .override files first, but it should never be possible for a chroot to crash the host's init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+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 1430403] Re: ubuntu-touch livefs builds kill upstart in host
It is relatively simple to trigger the bug: run a script that loops creating a .conf file and an .override file, then deletes the .conf file before deleting the override file. -- 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/1430403 Title: ubuntu-touch livefs builds kill upstart in host Status in upstart package in Ubuntu: Confirmed Bug description: ubuntu-touch livefs builds have started killing upstart in the host system (in this case, precise, although a similar bug appears to be present in current versions). The livefs build completes, but the host dies shortly after launchpad-buildd starts trying to remove the build chroot. The kernel log looks like this: Mar 10 13:46:55 allspice kernel: [3743880.621603] init: /home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf: Unable to reload configuration after override deletion Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core dumped Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core dumped This appears to be because a couple of functions call conf_reload_path, which may leave an nih_error in place if nih_file_read fails, but then do not dispose of the nih_error. The pattern near the end of conf_file_visitor (in precise) is probably appropriate. We're working around this to some extent in livecd-rootfs by removing the .override files first, but it should never be possible for a chroot to crash the host's init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+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 1430403] Re: ubuntu-touch livefs builds kill upstart in host
Note that we cannot add new unit tests for this fix without making it a much bigger change since the problematic function is static. -- 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/1430403 Title: ubuntu-touch livefs builds kill upstart in host Status in upstart package in Ubuntu: Confirmed Bug description: ubuntu-touch livefs builds have started killing upstart in the host system (in this case, precise, although a similar bug appears to be present in current versions). The livefs build completes, but the host dies shortly after launchpad-buildd starts trying to remove the build chroot. The kernel log looks like this: Mar 10 13:46:55 allspice kernel: [3743880.621603] init: /home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf: Unable to reload configuration after override deletion Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core dumped Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core dumped This appears to be because a couple of functions call conf_reload_path, which may leave an nih_error in place if nih_file_read fails, but then do not dispose of the nih_error. The pattern near the end of conf_file_visitor (in precise) is probably appropriate. We're working around this to some extent in livecd-rootfs by removing the .override files first, but it should never be possible for a chroot to crash the host's init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+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 1430403] Re: ubuntu-touch livefs builds kill upstart in host
** Also affects: upstart (Ubuntu Precise) 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/1430403 Title: ubuntu-touch livefs builds kill upstart in host Status in upstart package in Ubuntu: Confirmed Status in upstart source package in Precise: New Bug description: ubuntu-touch livefs builds have started killing upstart in the host system (in this case, precise, although a similar bug appears to be present in current versions). The livefs build completes, but the host dies shortly after launchpad-buildd starts trying to remove the build chroot. The kernel log looks like this: Mar 10 13:46:55 allspice kernel: [3743880.621603] init: /home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf: Unable to reload configuration after override deletion Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core dumped Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core dumped This appears to be because a couple of functions call conf_reload_path, which may leave an nih_error in place if nih_file_read fails, but then do not dispose of the nih_error. The pattern near the end of conf_file_visitor (in precise) is probably appropriate. We're working around this to some extent in livecd-rootfs by removing the .override files first, but it should never be possible for a chroot to crash the host's init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+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 1430403] Re: ubuntu-touch livefs builds kill upstart in host
** Description changed:
+ = Summary =
+
+ The version of Upstart in precise is affected by a bug in the way that
+ ".override" [1] file handling is performed.
+
+ If a job has an override file ("/etc/init/*.override") and that override
+ file is deleted before the corresponding job configuration file
+ ("/etc/init/*.conf"), there is a possibility of a crash.
+
+ == Explanation ==
+
+ When a "/etc/init/*.override" file is deleted, Upstart will
+ automatically detect this and reload the corresponding
+ "/etc/init/*.conf" file.
+
+ However, if the ".conf" file (which the ".override" file corresponded
+ to) is deleted at the same time Upstart attempts to read the ".conf"
+ file, an assertion failure could result.
+
+
+ = Code Specifics =
+
+ The erroneous function is "conf_delete_handler()" which is called
+ whenever a file Upstart is watching gets deleted. The end of this
+ function calls conf_reload_path() but although it logs an error message,
+ it does not consume the error object that gets raised when
+ conf_reload_path() fails.
+
+
+ = Affected Releases =
+
+ This bug is only present in precise:
+
+ - Upstart override handling was introduced in Upstart v1.3:
+ - Precise currently uses Upstart 1.5-0ubuntu7.2 (and hence is affected).
+ - Lucid currently uses Upstart 0.6.5-8 (hence, not affected).
+ - Trusty and Vivid use much newer versions of the Upstart which no
+ longer contain the problematic code.
+
+
+ = Fix =
+
+ The fix is simply to have conf_delete_handler() consume the error object
+ (by freeing it) when conf_reload_path() fails.
+
+
+ = Test Case =
+
+ A reliable test case is unfortunately not possible to create, since the
problem comes down to Upstart racing with the deletion of the ".conf"
+ file.
+
+ However, the patch is small and it can be seen that every other failing
+ call to conf_reload_path() free's the resulting error object.
+
+
+ = Regression Potential =
+
+ None expected. The problem is difficult to trigger anwyay and the patch
+ can be seen to correct (what is now) an obvious coding error.
+
+
+ [1] - http://upstart.ubuntu.com/cookbook/#override-file
+
+ = Original Description =
+
ubuntu-touch livefs builds have started killing upstart in the host
system (in this case, precise, although a similar bug appears to be
present in current versions). The livefs build completes, but the host
dies shortly after launchpad-buildd starts trying to remove the build
chroot. The kernel log looks like this:
Mar 10 13:46:55 allspice kernel: [3743880.621603] init:
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
Unable to reload configuration after override deletion
Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled
error from nih_file_read: No such file or directory
Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core
dumped
Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled
error from nih_file_read: No such file or directory
Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core
dumped
This appears to be because a couple of functions call conf_reload_path,
which may leave an nih_error in place if nih_file_read fails, but then
do not dispose of the nih_error. The pattern near the end of
conf_file_visitor (in precise) is probably appropriate.
We're working around this to some extent in livecd-rootfs by removing
the .override files first, but it should never be possible for a chroot
to crash the host's init.
--
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/1430403
Title:
ubuntu-touch livefs builds kill upstart in host
Status in upstart package in Ubuntu:
Confirmed
Status in upstart source package in Precise:
New
Bug description:
= Summary =
The version of Upstart in precise is affected by a bug in the way that
".override" [1] file handling is performed.
If a job has an override file ("/etc/init/*.override") and that
override file is deleted before the corresponding job configuration
file ("/etc/init/*.conf"), there is a possibility of a crash.
== Explanation ==
When a "/etc/init/*.override" file is deleted, Upstart will
automatically detect this and reload the corresponding
"/etc/init/*.conf" file.
However, if the ".conf" file (which the ".override" file corresponded
to) is deleted at the same time Upstart attempts to read the ".conf"
file, an assertion failure could result.
= Code Specifics =
The erroneous function is "conf_delete_handler()" which is called
whenever a file Upstart is watching gets deleted. The end of this
function calls conf_reload_path() but although it logs an error
message, it does not consume the error object that gets raised when
conf_reload_path() fails.
= Affected Releases =
Th
[Touch-packages] [Bug 1430403] Re: [SRU] ubuntu-touch livefs builds kill upstart in host
** Description changed:
= Summary =
The version of Upstart in precise is affected by a bug in the way that
".override" [1] file handling is performed.
If a job has an override file ("/etc/init/*.override") and that override
file is deleted before the corresponding job configuration file
("/etc/init/*.conf"), there is a possibility of a crash.
== Explanation ==
When a "/etc/init/*.override" file is deleted, Upstart will
automatically detect this and reload the corresponding
"/etc/init/*.conf" file.
However, if the ".conf" file (which the ".override" file corresponded
to) is deleted at the same time Upstart attempts to read the ".conf"
file, an assertion failure could result.
-
= Code Specifics =
The erroneous function is "conf_delete_handler()" which is called
whenever a file Upstart is watching gets deleted. The end of this
function calls conf_reload_path() but although it logs an error message,
it does not consume the error object that gets raised when
conf_reload_path() fails.
-
= Affected Releases =
This bug is only present in precise:
- Upstart override handling was introduced in Upstart v1.3:
- Precise currently uses Upstart 1.5-0ubuntu7.2 (and hence is affected).
- Lucid currently uses Upstart 0.6.5-8 (hence, not affected).
- Trusty and Vivid use much newer versions of the Upstart which no
- longer contain the problematic code.
-
+ longer contain the problematic code.
= Fix =
The fix is simply to have conf_delete_handler() consume the error object
(by freeing it) when conf_reload_path() fails.
-
= Test Case =
A reliable test case is unfortunately not possible to create, since the
problem comes down to Upstart racing with the deletion of the ".conf"
file.
However, the patch is small and it can be seen that every other failing
call to conf_reload_path() free's the resulting error object.
+ = Workarounds =
+
+ The problem is only manifested if ".conf" and the ".override" file get
+ deleted one after another, with the ".override" file being deleted
+ first. This implies the following work-arounds to avoid the problem if
+ you wish to delete both files "at the same time":
+
+ 1) Ensure the ".conf" file is deleted first.
+
+ 2) Delete the ".override" file first, and then wait for a small period
+ of time before deleting the corresponding ".conf" file.
+
+ 3) Delete the ".override" file first, then call "sudo initctl reload-
+ configuration" and then delete the corresponding ".conf" file.
= Regression Potential =
None expected. The problem is difficult to trigger anwyay and the patch
can be seen to correct (what is now) an obvious coding error.
-
[1] - http://upstart.ubuntu.com/cookbook/#override-file
= Original Description =
ubuntu-touch livefs builds have started killing upstart in the host
system (in this case, precise, although a similar bug appears to be
present in current versions). The livefs build completes, but the host
dies shortly after launchpad-buildd starts trying to remove the build
chroot. The kernel log looks like this:
Mar 10 13:46:55 allspice kernel: [3743880.621603] init:
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
Unable to reload configuration after override deletion
Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled
error from nih_file_read: No such file or directory
Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core
dumped
Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled
error from nih_file_read: No such file or directory
Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core
dumped
This appears to be because a couple of functions call conf_reload_path,
which may leave an nih_error in place if nih_file_read fails, but then
do not dispose of the nih_error. The pattern near the end of
conf_file_visitor (in precise) is probably appropriate.
We're working around this to some extent in livecd-rootfs by removing
the .override files first, but it should never be possible for a chroot
to crash the host's init.
** Description changed:
= Summary =
The version of Upstart in precise is affected by a bug in the way that
".override" [1] file handling is performed.
If a job has an override file ("/etc/init/*.override") and that override
file is deleted before the corresponding job configuration file
("/etc/init/*.conf"), there is a possibility of a crash.
== Explanation ==
When a "/etc/init/*.override" file is deleted, Upstart will
automatically detect this and reload the corresponding
"/etc/init/*.conf" file.
However, if the ".conf" file (which the ".override" file corresponded
to) is deleted at the same time Upstart attempts to read the ".conf"
file, an assertion failure could result.
= Code Specifics =
[Touch-packages] [Bug 1430403] Re: [SRU] ubuntu-touch livefs builds kill upstart in host
** Summary changed:
- ubuntu-touch livefs builds kill upstart in host
+ [SRU] ubuntu-touch livefs builds kill upstart in host
** Changed in: upstart (Ubuntu)
Status: Confirmed => In Progress
--
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/1430403
Title:
[SRU] ubuntu-touch livefs builds kill upstart in host
Status in upstart package in Ubuntu:
In Progress
Status in upstart source package in Precise:
New
Bug description:
= Summary =
The version of Upstart in precise is affected by a bug in the way that
".override" [1] file handling is performed.
If a job has an override file ("/etc/init/*.override") and that
override file is deleted before the corresponding job configuration
file ("/etc/init/*.conf"), there is a possibility of a crash.
== Explanation ==
When a "/etc/init/*.override" file is deleted, Upstart will
automatically detect this and reload the corresponding
"/etc/init/*.conf" file.
However, if the ".conf" file (which the ".override" file corresponded
to) is deleted at the same time Upstart attempts to read the ".conf"
file, an assertion failure could result.
= Code Specifics =
The erroneous function is "conf_delete_handler()" which is called
whenever a file Upstart is watching gets deleted. The end of this
function calls conf_reload_path() but although it logs an error
message, it does not consume the error object that gets raised when
conf_reload_path() fails.
= Affected Releases =
This bug is only present in precise:
- Upstart override handling was introduced in Upstart v1.3:
- Precise currently uses Upstart 1.5-0ubuntu7.2 (and hence is affected).
- Lucid currently uses Upstart 0.6.5-8 (hence, not affected).
- Trusty and Vivid use much newer versions of the Upstart which no
longer contain the problematic code.
= Fix =
The fix is simply to have conf_delete_handler() consume the error
object (by freeing it) when conf_reload_path() fails.
= Test Case =
A reliable test case is unfortunately not possible to create, since the
problem comes down to Upstart racing with the deletion of the ".conf"
file.
However, the patch is small and it can be seen that every other
failing call to conf_reload_path() free's the resulting error object.
= Regression Potential =
None expected. The problem is difficult to trigger anwyay and the
patch can be seen to correct (what is now) an obvious coding error.
[1] - http://upstart.ubuntu.com/cookbook/#override-file
= Original Description =
ubuntu-touch livefs builds have started killing upstart in the host
system (in this case, precise, although a similar bug appears to be
present in current versions). The livefs build completes, but the
host dies shortly after launchpad-buildd starts trying to remove the
build chroot. The kernel log looks like this:
Mar 10 13:46:55 allspice kernel: [3743880.621603] init:
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
Unable to reload configuration after override deletion
Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled
error from nih_file_read: No such file or directory
Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core
dumped
Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled
error from nih_file_read: No such file or directory
Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core
dumped
This appears to be because a couple of functions call
conf_reload_path, which may leave an nih_error in place if
nih_file_read fails, but then do not dispose of the nih_error. The
pattern near the end of conf_file_visitor (in precise) is probably
appropriate.
We're working around this to some extent in livecd-rootfs by removing
the .override files first, but it should never be possible for a
chroot to crash the host's init.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+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 1430403] Re: ubuntu-touch livefs builds kill upstart in host
The crash seems to originate from the conf_delete_handler() where although an error message gets logged, the actual error itself is not cleared. Note that this bug is present in 1.5-0ubuntu7.2 (precise), but is not present in trusty (1.12.1-0ubuntu4.2) or vivid (1.13.2-0ubuntu9). -- 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/1430403 Title: ubuntu-touch livefs builds kill upstart in host Status in upstart package in Ubuntu: Confirmed Bug description: ubuntu-touch livefs builds have started killing upstart in the host system (in this case, precise, although a similar bug appears to be present in current versions). The livefs build completes, but the host dies shortly after launchpad-buildd starts trying to remove the build chroot. The kernel log looks like this: Mar 10 13:46:55 allspice kernel: [3743880.621603] init: /home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf: Unable to reload configuration after override deletion Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core dumped Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled error from nih_file_read: No such file or directory Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core dumped This appears to be because a couple of functions call conf_reload_path, which may leave an nih_error in place if nih_file_read fails, but then do not dispose of the nih_error. The pattern near the end of conf_file_visitor (in precise) is probably appropriate. We're working around this to some extent in livecd-rootfs by removing the .override files first, but it should never be possible for a chroot to crash the host's init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+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 1300235] Re: init (chromium-browser) crashed with SIGSEGV
Playing around with strings(1), I've found this:
$ strings /usr/lib/chromium-browser/libs/libcontent.so|egrep "\"
init
The SUID sandbox created a new PID namespace but Zygote is not the init
process. Please, make sure the SUID binary is up to date.
Error creating an init process to reap zombies
Failed to init random generator!
Failed to init data channel.
SRTP reset to init state
Failed to init SRTP, err=
Image size must match encoder init configuration size
.init
--
The key terms here are:
- "Error creating an init process to reap zombies"
- "SUID binary"
See:
https://code.google.com/p/chromium/codesearch#chromium/src/content/zygote/zygote_main_linux.cc&sq=package:chromium
It appears chromium creates PID namespaces, probably to run plugins/tabs
in an isolated environment. But each pid namespace needs a PID 1
process. So, one possibility is that chromium is inadvertently forking
and exec'ing "init" (ie "/sbin/init") rather than its own init
implementation of an init daemon ("/opt/google/chrome-unstable/chrome
--type=zygote"?). And that init (be it upstart or systemd) is crashing
as it's being run in a very unusual environment.
--
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/1300235
Title:
init (chromium-browser) crashed with SIGSEGV
Status in upstart package in Ubuntu:
Triaged
Bug description:
none
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: upstart 1.12.1-0ubuntu1
Uname: Linux 3.14.0-031400rc8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
Date: Mon Mar 31 09:53:16 2014
Disassembly: => 0x7fa2b65e94d7: Cannot access memory at address
0x7fa2b65e94d7
ExecutablePath: /sbin/init
InstallationDate: Installed on 2014-03-05 (25 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140305)
ProcCmdline: /sbin/init
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic
root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash
SegvAnalysis:
Segfault happened at: 0x7fa2b65e94d7:Cannot access memory at address
0x7fa2b65e94d7
PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable
region)!
Stack pointer not within stack segment
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: upstart
StacktraceTop:
?? ()
?? ()
?? ()
Title: init crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningSystemVersion: init (upstart 1.12.1)
UserGroups:
modified.conffile..etc.default.cups: [modified]
mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1300235/+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 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file
I've written a basic program that surfaces this bug. To recreate: $ cd /tmp $ tar xvf bug-1429756.tgz $ cd bug-1429756 $ make $ ./bug-1429756.sh loop 1 loop 2 ERROR: got failure scenario after 2 loops (got=16, count=17, log=/tmp/tmp.uwZHkHh0mc) $ ** Attachment added: "bug-1429756.tgz" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+attachment/4343995/+files/bug-1429756.tgz -- 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/1429756 Title: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file Status in linux package in Ubuntu: In Progress Status in upstart package in Ubuntu: New Status in linux source package in Vivid: In Progress Status in upstart source package in Vivid: New Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+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 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file
Running with a 3.19.0-8-generic kernel I see: - The Upstart test_job_process test fail within a few seconds when run in a loop looking for the errror. - My test program in #13 also finds the bug within ~30 seconds on my test system. Using the kernel in #11, I have run both tests simultaneously for ~1 hour with no errors observed. ** Changed in: upstart (Ubuntu Vivid) Status: New => Invalid ** Summary changed: - FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file + FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file -- 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/1429756 Title: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file Status in linux package in Ubuntu: In Progress Status in upstart package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Status in upstart source package in Vivid: Invalid Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+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 1300235] Re: init (chromium-browser) crashed with SIGSEGV
** Package changed: upstart (Ubuntu) => chromium-browser (Ubuntu) -- 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/1300235 Title: init (chromium-browser) crashed with SIGSEGV Status in chromium-browser package in Ubuntu: Triaged Bug description: none ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: upstart 1.12.1-0ubuntu1 Uname: Linux 3.14.0-031400rc8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Mon Mar 31 09:53:16 2014 Disassembly: => 0x7fa2b65e94d7: Cannot access memory at address 0x7fa2b65e94d7 ExecutablePath: /sbin/init InstallationDate: Installed on 2014-03-05 (25 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140305) ProcCmdline: /sbin/init ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash SegvAnalysis: Segfault happened at: 0x7fa2b65e94d7:Cannot access memory at address 0x7fa2b65e94d7 PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable region)! Stack pointer not within stack segment SegvReason: executing unknown VMA Signal: 11 SourcePackage: upstart StacktraceTop: ?? () ?? () ?? () Title: init crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSystemVersion: init (upstart 1.12.1) UserGroups: modified.conffile..etc.default.cups: [modified] mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1300235/+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 1447756] Re: segfault in log.c code causes phone reboot loops
Hi ondra/ogra - Can you comment on my suggestions in #6 and #7? My device is still bricked so if you have any suggestions on how to perform a full reset, that'd be great as udf is unable to recover it. -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
I've rebuild the fix in a clean environment and the init binary below now boots fine for me on a bq aquaris E4.5: http://people.canonical.com/~jhunt/upstart/bugs/bug-1447756/armhf/ -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
ondra and I have been hammering away at this, but progress is painfully slow given that: a) the problem is not seen on every boot. b) we can only view the end of kmsg log. c) rebuild times are relatively slow. >From what ondra says he's seen today, it sounds as though we might be hitting a stack corruption issue - the debug I've given him is not being displayed as expected. Even with the initial fix I created based on code inspection alone, ondra is still seeing exactly the same assertion failure which we thought would have been fixed by the initial fix for this bug. I've tried various ways to recreate the issue (both on a device and on a normal system, code review / code analysis tools, runtime checkers), but have so far been unsuccessful. Current work-arounds: 1) Keep using '--no-log' in the kernel command-line. Pros: reliable. Cons: means that no system jobs get their output logged. 2) Disable the /etc/init/flush-early-job-log.conf job. Pros: seems to be reliable (? but needs further testing). Cons: means early job output is not logged (however, on the device in question the only output seems to be from /etc/init/container-detect.conf (and that output is not even required). -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Fix Committed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
Hi Ondrej,
Regarding #15, I'm not sure this is correct. As you say, when the job
process terminates, job_process_terminated() gets called. This calls
log_handle_unflushed() and that function calls log_read_watch(), which
ultimately calls write(2). However, even if the write is successful
before 'initctl notify-disk-writeable' gets called, if you look at
log_handle_unflushed()...
743 log_handle_unflushed (void *parent, Log *log)
744 {
745 NihListEntry *elem;
746
747 nih_assert (log);
748 nih_assert (log->detached == 0);
749
750 log_read_watch (log);
751
752 if (! log->unflushed->len)
753 return 1;
So, if the write is successful and log->unflushed->len becomes zero, the
function returns 1 (meaning "log does not need to be added to the
unflushed list") and crucially the log is not added to the unflushed
list.
--
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/1447756
Title:
segfault in log.c code causes phone reboot loops
Status in the base for Ubuntu mobile products:
Fix Committed
Status in Upstart:
New
Status in upstart package in Ubuntu:
Confirmed
Bug description:
We recently started getting reprots from phone users that their
devices go into a reboot loop after changing the language or getting
an OTA upgrade (either of both end with a reboot of the phone)
after a bit of research we collected the log at
http://pastebin.ubuntu.com/10872934/
this shows a segfault of upstarts init binary in the log.c code:
[6.999083]init: log.c:819: Assertion failed in log_clear_unflushed:
log->unflushed->len
[7.000279]init: Caught abort, core dumped
[7.467176]Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0600
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
Hi Ondrej,
Regarding #15, I'm not sure this is correct. As you say, when the job
process terminates, job_process_terminated() gets called. This calls
log_handle_unflushed() and that function calls log_read_watch(), which
ultimately calls write(2). However, even if the write is successful
before 'initctl notify-disk-writeable' gets called, if you look at
log_handle_unflushed()...
743 log_handle_unflushed (void *parent, Log *log)
744 {
745 NihListEntry *elem;
746
747 nih_assert (log);
748 nih_assert (log->detached == 0);
749
750 log_read_watch (log);
751
752 if (! log->unflushed->len)
753 return 1;
So, if the write is successful and log->unflushed->len becomes zero, the
function returns 1 (meaning "log does not need to be added to the
unflushed list") and crucially the log is not added to the unflushed
list.
Regarding #16, there shouldn't be a problem in that scenario since when
the log gets added to the unflushed list, it is totally detached from
its parent job. Hence, the job can be destroyed but the log lives on as
an element of the unflushed list. If that job gets recreated, it will
get a new set of log objects associated with it.
Did you manage to get the full log_clear_unflushed() debug output in the
end?
--
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/1447756
Title:
segfault in log.c code causes phone reboot loops
Status in the base for Ubuntu mobile products:
Fix Committed
Status in Upstart:
New
Status in upstart package in Ubuntu:
Confirmed
Bug description:
We recently started getting reprots from phone users that their
devices go into a reboot loop after changing the language or getting
an OTA upgrade (either of both end with a reboot of the phone)
after a bit of research we collected the log at
http://pastebin.ubuntu.com/10872934/
this shows a segfault of upstarts init binary in the log.c code:
[6.999083]init: log.c:819: Assertion failed in log_clear_unflushed:
log->unflushed->len
[7.000279]init: Caught abort, core dumped
[7.467176]Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0600
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
Ondrej - aha! with the debug, this is making more sense now. Yes, since the ureadahead-touch job spawns a process in the background (ureadahead) and then the job itself exits, the log associated with the main job process gets added to the unflushed list. ureadahead then writes output and the NihIo is automatically serviced to flush the log to disk and set log->unflushed->len to zero. Later, 'initctl notify-disk-writable' gets called and the assert fires as all the output from both /etc/init /ureadahead-touch.conf and from the ureadahead daemon itself has already been logged. Could you try the following which should be a minimal fix: http://paste.ubuntu.com/11095313/ Another point - the fact that ureadahead-touch is triggering the problem does point to an issue with that job - as can be seen, even when the script section ends (and that associated shell dies), 'ureadahead --daemon' continues and if it produces output, that gets logged. A simple work-around is to remove --daemon so that the job process and the log never become detached. -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Fix Committed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
\o/. Yes, Upstart uses asserts extremely agressively. It's unfortunate that we've never hit this issue in testing but I'm currently working on new tests for this slightly unusual scenario. -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Fix Committed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
** Changed in: upstart (Ubuntu) Status: Confirmed => In Progress ** Changed in: upstart Status: New => In Progress -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Fix Committed Status in Upstart: In Progress Status in upstart package in Ubuntu: In Progress Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix contains the fix and a new test (which correctly fails with the current lp:upstart but passes with the fix in that branch). The code has been tested on a failing device and a server system. I am currently testing on a non-failing krillin device. I understand Ondra is going to test on a couple of other devices that exhibit this bug to further sanity check the code. Once all these tests pass I'll raise an MP for the branch above to get it merged to lp:upstart. We'll then need to cherry pick the fix into both vivid and wily. -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Fix Committed Status in Upstart: In Progress Status in upstart package in Ubuntu: In Progress Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
Applying the top 2 commits (r1665 and r1666) from lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix [1] to https://bugs.launchpad.net/ubuntu- rtm/+source/upstart/1.13.2-0ubuntu1rtm1 is now working for me. I've tested this by building on the device itself and also by building in a ARCH=armhf utopic chroot [2]. __ [1] - Equivalent to the attached patch. [2] - Interestingly, building in an vivid ARCH=armhf chroot generates a binary that fails at runtime. ** Patch added: "bug-1447756-both-fixes.diff" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1447756/+attachment/4396882/+files/bug-1447756-both-fixes.diff -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: In Progress Status in Upstart: In Progress Status in upstart package in Ubuntu: In Progress Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
MP raised on lp:upstart to start the trickle-down to the rtm package. -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: In Progress Status in Upstart: In Progress Status in upstart package in Ubuntu: In Progress Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
** Changed in: upstart Status: In Progress => Fix Committed -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: In Progress Status in Upstart: Fix Committed Status in upstart package in Ubuntu: In Progress Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
** Also affects: upstart (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: upstart (Ubuntu Wily) Importance: Critical Assignee: James Hunt (jamesodhunt) Status: In Progress ** Also affects: upstart (Ubuntu Vivid) 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: In Progress Status in Upstart: Fix Committed Status in upstart package in Ubuntu: In Progress Status in upstart source package in Utopic: New Status in upstart source package in Vivid: New Status in upstart source package in Wily: In Progress Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
Hi Andy - any progress on this? Although the buildd's are running older kernels, it seems that the DEP-8 Jenkins environment is running 3.19 and is thus causing upstart tests to fail. For example: https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt- upstart/ARCH=amd64,label=adt/lastBuild/ If it will take a while to resolve this, I guess we'll have to consider disabling the test for now. However, doing so is going to change the behaviour of the upstart logger. -- 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/1429756 Title: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file Status in linux package in Ubuntu: In Progress Status in upstart package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Status in upstart source package in Vivid: Invalid Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
Looks like kernel bug 1429756 could block 1.13.2-0ubuntu14 landing for wily (being a pre-req to getting this fix into vivid and utopic): https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily- adt-upstart/ARCH=amd64,label=adt/9/ -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: In Progress Status in Upstart: Fix Committed Status in upstart package in Ubuntu: In Progress Status in upstart source package in Utopic: New Status in upstart source package in Vivid: New Status in upstart source package in Wily: In Progress Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
LKML thread: https://lkml.org/lkml/2015/3/16/474 -- 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/1429756 Title: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file Status in linux package in Ubuntu: In Progress Status in upstart package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Status in upstart source package in Vivid: Invalid Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
Thanks for nudging -proposed Steve. I've silo 021 now includes upstart version 1.13.2-0ubuntu13.1 (which sil2100 synced from wily). Basic test plan is here: https://wiki.ubuntu.com/Process/TestPlans /upstart-bug-1447756 I've tested this as follows: $ wget http://people.canonical.com/~jhm/barajas/recovery.img $ ubuntu-device-flash --verbose touch --bootstrap --channel=ubuntu-touch/rc-proposed/bq-aquaris.en --device krillin --recovery-image ./recovery.img $ citrain device-upgrade 021 I then reflashed the boot.img using one from ondra which drops the current '--no-log' option from /proc/cmdline and rebooted. As far as I'm concerned, the fix is good. All that now remains is for ondra or one of the folk in London who have the "failing" krillin devices to test the above. -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: In Progress Status in Upstart: Fix Committed Status in upstart package in Ubuntu: Fix Released Status in upstart source package in Utopic: New Status in upstart source package in Vivid: New Status in upstart source package in Wily: Fix Released Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
Unfortunately, ondra no longer has the failing phones so we may need to take a decision to just land this if QA are happy the change has not regressed the behaviour for non-failing phones. I've tried to raise QA but they are sprinting in the US this week so no direct response. I believe that sil2100 is doing what he can atm, but it's unclear whether this fix will make it into the next OTA at this stage. -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: In Progress Status in Upstart: Fix Committed Status in upstart package in Ubuntu: Fix Released Status in upstart source package in Utopic: New Status in upstart source package in Vivid: New Status in upstart source package in Wily: Fix Released Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
** Changed in: upstart (Ubuntu Vivid) Status: New => In Progress ** Changed in: upstart (Ubuntu Vivid) Assignee: (unassigned) => James Hunt (jamesodhunt) -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Fix Released Status in Upstart: Fix Committed Status in upstart package in Ubuntu: Fix Released Status in upstart source package in Utopic: Won't Fix Status in upstart source package in Vivid: In Progress Status in upstart source package in Wily: Fix Released Status in upstart package in Ubuntu RTM: Fix Released Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
** Description changed:
+ = Summary =
+
+ The version of Upstart in vivid is affected by a coule of bugs relating
+ to the flushing data from early-boot jobs to disk which can both result
+ in a crash:
+
+ == Problem 1 ==
+
+ An internal list is mishandled meaning a crash could occur randomly.
+
+ == Problem 2 ==
+
+ Jobs which spawn processes in the background then themselves exit can
+ cause a crash due.
+
+ = Explanation of how Upstart flushes early job output =
+
+ If an Upstart job starts *and ends* early in the boot sequence (before
+ the log partition is mounted and writable) and produces output to its
+ stdout/stderr, Upstart will cache the output for later flushing by
+ adding the 'Log' object associated with the 'Job' to a list.
+
+ When the log partition is mounted writable, the
+ /etc/init/flush-early-job-log.conf job is run which calls "initctl
+ notify-disk-writeable". This is a signal to Upstart to flush its cache
+ of early-boot job output which takes the form of iterating the
+ 'log_unflushed_files' list and flushing all the 'Log' entries to disk.
+
+ = Code Specifics =
+
+ There are 2 issues (note that the numbers used below match those used in
+ the Summary).
+
+ == Problem 1 detail ==
+
+ Due to a bug in the way the 'log_unflushed_files' list is handled (the
+ 'Log' cannot be added to the list directly, so is added via an
+ intermediary ('NihListElem') node), a crash can result when iterating
+ the list since the 'Log' is freed, but NOT the intermediary node. The
+ implication is that it is possible for the intermediary node to be
+ attempt to dereference already-freed data, resulting in a crash.
+
+ == Problem 2 detail ==
+
+ If a job spawns a process in the background, then itself exits, that
+ jobs 'Log' entry will be added to the 'log_unflushed_files' list. But,
+ if the background process produces output and then exits before Upstart
+ attempts to flush the original jobs data to disk, the 'NihIo'
+ corresponding to the log will be serviced automatically and the data
+ flushed to disk. The problem comes when Upstart receives the
+ notification to flush the 'log_unflushed_files' list, since that list
+ now contains an entry which has already been freed (since all its data
+ has already been flushed). The result is an assertion failure.
+
+ = Fix =
+
+ == Problem 1 fix ==
+
+ Correct the 'log_unflushed_files' list handling by freeing the
+ 'NihListElem' (which will automatically free the 'Log' object), not by
+ simply freeing the 'Log' object itself.
+
+ * Branch: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756/
+ * New Upstart test added to avoid regression?: Yes.
+
+ == Problem 2 fix ==
+
+ Correct the assumption that the only entries in the
+ 'log_unflushed_files' list will always have data to flush by checking if
+ there is in fact any data to flush; if not, remove the entry from the
+ 'log_unflushed_files' list since it has already been handled
+ automatically by the 'NihIo'.
+
+ * Branch: lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix
+ * New Upstart test added to avoid regression?: Yes.
+
+ = Workarounds =
+
+ If a system is affected by this bug, it will be manifested by a crash
+ early in the boot sequence.
+
+ To overcome the issue, either:
+
+ a) Boot by adding "--no-log" to the kernel command-line.
+
+ b) Disable the flush-early-job-log job (assuming the machine is
+ bootable) by running the following:
+
+$ echo manual | sudo tee -a /etc/init/flush-early-job-log.override
+
+ = Impact =
+
+ The issue has been present in Upstart since logging was introduced but
+ no known instances of crashes relating to these problems have been
+ reported prior to this bug being reported (which relates the the issue
+ being seen on a very small subset of specific Ubuntu Touch phone
+ hardware where Upstart is used as the system init daemon).
+
+ Note that vivid still uses Upstart for managing the graphical session,
+ but now uses systemd by default for the system init daemon. Since the session
(Upstart) init does not even require
+ a flush-early-job-log, the exposure to both the bug and the updated fix
codepath is extremely limited.
+
+ = Test Case =
+
+ This bug is extremely hard to surface so the approach is simply to check
+ that the internal list can be iterated correctly by:
+
+ 1) Booting the system with upstart
+(select the Upstart option from the grub menu or add "init=/sbin/upstart"
to the kernel command-line).
+
+ 2) Running the following on a system booted with Upstart:
+
+$ for i in $(seq 17); do sudo start flush-early-job-log; done
+
+ = Regression Potential =
+
+ None expected:
+
+ - As noted in Impact, the problems fixed by this version of Upstart have not
been observed on server/desktop systems before.
+ - The fix is already in wily and no problems have been reported.
+ - See Impact.
+
+ = Original Description =
+
We recently started getting reprots from phone users that their devices
go into a reboot loop aft
[Touch-packages] [Bug 1447756] Re: [SRU] segfault in log.c code causes phone reboot loops
Hi Steve - ah, sorry - hadn't registered that you'd already copied the
package into the queue (we now have 2 :-) Could mine be deleted please?
--
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/1447756
Title:
[SRU] segfault in log.c code causes phone reboot loops
Status in the base for Ubuntu mobile products:
Fix Released
Status in Upstart:
Fix Committed
Status in upstart package in Ubuntu:
Fix Released
Status in upstart source package in Utopic:
Won't Fix
Status in upstart source package in Vivid:
In Progress
Status in upstart source package in Wily:
Fix Released
Status in upstart package in Ubuntu RTM:
Fix Released
Bug description:
= Summary =
The version of Upstart in vivid is affected by a coule of bugs relating
to the flushing data from early-boot jobs to disk which can both result
in a crash:
== Problem 1 ==
An internal list is mishandled meaning a crash could occur randomly.
== Problem 2 ==
Jobs which spawn processes in the background then themselves exit can
cause a crash due.
= Explanation of how Upstart flushes early job output =
If an Upstart job starts *and ends* early in the boot sequence (before
the log partition is mounted and writable) and produces output to its
stdout/stderr, Upstart will cache the output for later flushing by
adding the 'Log' object associated with the 'Job' to a list.
When the log partition is mounted writable, the
/etc/init/flush-early-job-log.conf job is run which calls "initctl
notify-disk-writeable". This is a signal to Upstart to flush its cache
of early-boot job output which takes the form of iterating the
'log_unflushed_files' list and flushing all the 'Log' entries to disk.
= Code Specifics =
There are 2 issues (note that the numbers used below match those used in
the Summary).
== Problem 1 detail ==
Due to a bug in the way the 'log_unflushed_files' list is handled (the
'Log' cannot be added to the list directly, so is added via an
intermediary ('NihListElem') node), a crash can result when iterating
the list since the 'Log' is freed, but NOT the intermediary node. The
implication is that it is possible for the intermediary node to be
attempt to dereference already-freed data, resulting in a crash.
== Problem 2 detail ==
If a job spawns a process in the background, then itself exits, that
jobs 'Log' entry will be added to the 'log_unflushed_files' list. But,
if the background process produces output and then exits before Upstart
attempts to flush the original jobs data to disk, the 'NihIo'
corresponding to the log will be serviced automatically and the data
flushed to disk. The problem comes when Upstart receives the
notification to flush the 'log_unflushed_files' list, since that list
now contains an entry which has already been freed (since all its data
has already been flushed). The result is an assertion failure.
= Fix =
== Problem 1 fix ==
Correct the 'log_unflushed_files' list handling by freeing the
'NihListElem' (which will automatically free the 'Log' object), not by
simply freeing the 'Log' object itself.
* Branch: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756/
* New Upstart test added to avoid regression?: Yes.
== Problem 2 fix ==
Correct the assumption that the only entries in the
'log_unflushed_files' list will always have data to flush by checking if
there is in fact any data to flush; if not, remove the entry from the
'log_unflushed_files' list since it has already been handled
automatically by the 'NihIo'.
* Branch: lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix
* New Upstart test added to avoid regression?: Yes.
= Workarounds =
If a system is affected by this bug, it will be manifested by a crash
early in the boot sequence.
To overcome the issue, either:
a) Boot by adding "--no-log" to the kernel command-line.
b) Disable the flush-early-job-log job (assuming the machine is
bootable) by running the following:
$ echo manual | sudo tee -a /etc/init/flush-early-job-log.override
= Impact =
The issue has been present in Upstart since logging was introduced but
no known instances of crashes relating to these problems have been
reported prior to this bug being reported (which relates the the issue
being seen on a very small subset of specific Ubuntu Touch phone
hardware where Upstart is used as the system init daemon).
Note that vivid still uses Upstart for managing the graphical session,
but now uses systemd by default for the system init daemon. Since the session
(Upstart) init does not even require
a flush-early-job-log, the exposure to both the bug and the updated fix
codepath is extremely limited.
= Test Case =
This bug is extremely hard to surface so the approach is simply to
check that the internal list can be iterated c
[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops
** Changed in: upstart (Ubuntu) Assignee: (unassigned) => James Hunt (jamesodhunt) -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
I think I understand what's happening now - it's not the log that isn't being freed, it's the list entry the log is attached to that is not freed. The effect is the same though - calling log_clear_unflushed() multiple times could trigger this issue since the still-valid (but incorectly so) list entry is now pointing at potentially garbage memory where a Log used to be. -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1368798] Re: [Greeter] horizonal rule on pin unlock screen too thin (looks like a scratch)
Screenshot showing the super-thin divider. ** Attachment added: "scratch.jpg" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368798/+attachment/4382842/+files/scratch.jpg -- 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/1368798 Title: [Greeter] horizonal rule on pin unlock screen too thin (looks like a scratch) Status in Ubuntu UX bugs: In Progress Status in unity8 package in Ubuntu: Incomplete Bug description: The pin code entry screen has what appears to be a 1 pixel high line horizontal line that goes almost to the left and right borders of the screen, just above the unlock keypad. I can see the value of such a horizontal rule but it is _so_ thin that when I looked at it earlier I thought I'd either scratched the screen or damaged it somehow. Could we possibly make it slightly thicker (or dotted or something) to make it more obviously a ruler and less possibly a scratch/screen damage? :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368798/+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 1447756] Re: segfault in log.c code causes phone reboot loops
** Also affects: upstart Importance: Undecided Status: New ** Changed in: upstart Assignee: (unassigned) => James Hunt (jamesodhunt) -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
Test binaries are available here: http://people.canonical.com/~jhunt/upstart/bugs/bug-1447756/armhf/ -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
i386+amd64 are packaged here: https://launchpad.net/~jamesodhunt/+archive/ubuntu/bug-1447756/+packages -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
I've tried the fix on my bq device and it appears to be in a reboot loop (like the one the fix was supposed to resolve). As such, I'd recommend testing the binaries only for the session init initially (/usr/bin/ubuntu-touch-session / /usr/share/lightdm/sessions /ubuntu-touch.desktop). Also, for both system and session scenarios, I'd recommend adding '-- debug' to get as much detail as possible. -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1447756] Re: segfault in log.c code causes phone reboot loops
Something else to try - disable /etc/init/flush-early-job-log.conf on boot... $ sudo mount -oremount,rw / $ echo manual | sudo tee /etc/init/flush-early-job-log.override $ sudo reboot ... and post-boot do the following: $ for i in $(seq 17); do sudo initctl notify-disk-writeable; done As Steve has mentioned, we do need to trace down why 'initctl notify- disk-writeable' seems to be being called multiple times on boot though - it should only really be called once when (in the case of Touch) /var/log/ is writable. -- 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/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+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 1413922] [NEW] lxc unprivileged containers broken
Public bug reported: Seems to be due to 1.1.0~rc1-0ubuntu1 landing? $ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug lxc-start: lxc_start.c: main: 345 The container failed to start. lxc-start: lxc_start.c: main: 347 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 349 Additional information can be obtained by setting the --logfile and --logpriority options. lxc.log attached. On a related note, it seems that the dep8 tests I originally wrote for lxc [1] have been replaced to call lxc's own test suite. However, whereas these new tests are somehow passing in jenkins [2], I belied the crude tests in [1] would have caught this issue as they actually call the command-line tools users run. Could we maybe bring back [1] and run both sets of tests to avoid such a regression in future? [1] - https://code.launchpad.net/~jamesodhunt/ubuntu/raring/lxc/dep-8-tests/+merge/157938 [2] - https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-lxc/ARCH=amd64,label=adt/ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 23 09:15:29 2015 InstallationDate: Installed on 2014-04-11 (286 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: lxc UpgradeStatus: Upgraded to vivid on 2014-05-08 (259 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug vivid ** Attachment added: "lxc.log" https://bugs.launchpad.net/bugs/1413922/+attachment/4304130/+files/lxc.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1413922 Title: lxc unprivileged containers broken Status in lxc package in Ubuntu: New Bug description: Seems to be due to 1.1.0~rc1-0ubuntu1 landing? $ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug lxc-start: lxc_start.c: main: 345 The container failed to start. lxc-start: lxc_start.c: main: 347 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 349 Additional information can be obtained by setting the --logfile and --logpriority options. lxc.log attached. On a related note, it seems that the dep8 tests I originally wrote for lxc [1] have been replaced to call lxc's own test suite. However, whereas these new tests are somehow passing in jenkins [2], I belied the crude tests in [1] would have caught this issue as they actually call the command-line tools users run. Could we maybe bring back [1] and run both sets of tests to avoid such a regression in future? [1] - https://code.launchpad.net/~jamesodhunt/ubuntu/raring/lxc/dep-8-tests/+merge/157938 [2] - https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-lxc/ARCH=amd64,label=adt/ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 23 09:15:29 2015 InstallationDate: Installed on 2014-04-11 (286 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: lxc UpgradeStatus: Upgraded to vivid on 2014-05-08 (259 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+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 1413922] Re: lxc unprivileged containers broken
Ah - seems we'd actually need to add in a couple of loops in those original dep-8 tests: run the tests as root, then run as a non-priv user too! :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1413922 Title: lxc unprivileged containers broken Status in lxc package in Ubuntu: New Bug description: Seems to be due to 1.1.0~rc1-0ubuntu1 landing? $ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug lxc-start: lxc_start.c: main: 345 The container failed to start. lxc-start: lxc_start.c: main: 347 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 349 Additional information can be obtained by setting the --logfile and --logpriority options. lxc.log attached. On a related note, it seems that the dep8 tests I originally wrote for lxc [1] have been replaced to call lxc's own test suite. However, whereas these new tests are somehow passing in jenkins [2], I belied the crude tests in [1] would have caught this issue as they actually call the command-line tools users run. Could we maybe bring back [1] and run both sets of tests to avoid such a regression in future? [1] - https://code.launchpad.net/~jamesodhunt/ubuntu/raring/lxc/dep-8-tests/+merge/157938 [2] - https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-lxc/ARCH=amd64,label=adt/ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 23 09:15:29 2015 InstallationDate: Installed on 2014-04-11 (286 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: lxc UpgradeStatus: Upgraded to vivid on 2014-05-08 (259 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+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 1413922] Re: lxc unprivileged containers broken
Hi Serge, Yep, updating to lxcfs 0.4, killing lxcfs, then a 'sudo chown -R james: /sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-c2.scope' allowed me to start the non-priv container. ** Changed in: lxc (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1413922 Title: lxc unprivileged containers broken Status in lxc package in Ubuntu: New Bug description: Seems to be due to 1.1.0~rc1-0ubuntu1 landing? $ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug lxc-start: lxc_start.c: main: 345 The container failed to start. lxc-start: lxc_start.c: main: 347 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 349 Additional information can be obtained by setting the --logfile and --logpriority options. lxc.log attached. On a related note, it seems that the dep8 tests I originally wrote for lxc [1] have been replaced to call lxc's own test suite. However, whereas these new tests are somehow passing in jenkins [2], I belied the crude tests in [1] would have caught this issue as they actually call the command-line tools users run. Could we maybe bring back [1] and run both sets of tests to avoid such a regression in future? [1] - https://code.launchpad.net/~jamesodhunt/ubuntu/raring/lxc/dep-8-tests/+merge/157938 [2] - https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-lxc/ARCH=amd64,label=adt/ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 23 09:15:29 2015 InstallationDate: Installed on 2014-04-11 (286 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: lxc UpgradeStatus: Upgraded to vivid on 2014-05-08 (259 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+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 1367338] [NEW] unable to open pdf file even with PdfjsViewer installed
Public bug reported: Clicking a pdf link still claims there is no PDF handler to view the file. However, 1) I have PdfjsViewer installed. 2) I should be able to download the file to the disk and open it later. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- 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/1367338 Title: unable to open pdf file even with PdfjsViewer installed Status in “webbrowser-app” package in Ubuntu: New Bug description: Clicking a pdf link still claims there is no PDF handler to view the file. However, 1) I have PdfjsViewer installed. 2) I should be able to download the file to the disk and open it later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1367338/+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 1367379] [NEW] Gets stuck in edit mode
Public bug reported: 1) Touch a contact so that the grey bust icon appears to the right of it. 2) Long-press the same contact by touching the name to go into edit mode - a green tick will appear next to the contact. 3) Press the bust icon to switch to the full details view. 4) Press back. 5) Observe that we are still in edit mode (as we should be), but the cross is missing from the top-left of the screen so it is no longer possible to leave edit mode. root@ubuntu-phablet:~# cat /etc/ubuntu-build 26 root@ubuntu-phablet:~# cat /etc/device-build 20140908-d8c11f3 ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1367379 Title: Gets stuck in edit mode Status in “address-book-app” package in Ubuntu: New Bug description: 1) Touch a contact so that the grey bust icon appears to the right of it. 2) Long-press the same contact by touching the name to go into edit mode - a green tick will appear next to the contact. 3) Press the bust icon to switch to the full details view. 4) Press back. 5) Observe that we are still in edit mode (as we should be), but the cross is missing from the top-left of the screen so it is no longer possible to leave edit mode. root@ubuntu-phablet:~# cat /etc/ubuntu-build 26 root@ubuntu-phablet:~# cat /etc/device-build 20140908-d8c11f3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1367379/+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 1367412] [NEW] no landscape support
Public bug reported: Long contact name handling seems to behave somewhat erratically but normally ends in "...". The expectation is that turning the screen sideways would allow the full contact name to be shown but the app doesn't seem to support this yet. ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1367412 Title: no landscape support Status in “address-book-app” package in Ubuntu: New Bug description: Long contact name handling seems to behave somewhat erratically but normally ends in "...". The expectation is that turning the screen sideways would allow the full contact name to be shown but the app doesn't seem to support this yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1367412/+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 1367411] [NEW] missing URL and notes fields when syncing google contacts
Public bug reported: subject says it all really :) ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1367411 Title: missing URL and notes fields when syncing google contacts Status in “address-book-app” package in Ubuntu: New Bug description: subject says it all really :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1367411/+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 1367410] [NEW] deleting a contact greys it out but leaves it in the list of contacts
Public bug reported: The entry remains in the list but is no longer selectable and has a very slightly darker grey background to the remaining list entries. ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1367410 Title: deleting a contact greys it out but leaves it in the list of contacts Status in “address-book-app” package in Ubuntu: New Bug description: The entry remains in the list but is no longer selectable and has a very slightly darker grey background to the remaining list entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1367410/+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 1367416] [NEW] searching for term not found in contact name spins forever
Public bug reported: Searching for a term that is _not_ in the contact names makes the search dialog spin forever until I touch the cross to cancel it. Expected behaviour: present a message saying "not found". Ideal behaviour: search all contact fields, not only the contact names. ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1367416 Title: searching for term not found in contact name spins forever Status in “address-book-app” package in Ubuntu: New Bug description: Searching for a term that is _not_ in the contact names makes the search dialog spin forever until I touch the cross to cancel it. Expected behaviour: present a message saying "not found". Ideal behaviour: search all contact fields, not only the contact names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1367416/+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 1368135] [NEW] touching ubuntu icon when (non-favourite) scope open does not display home screen.
Public bug reported: 1) swipe up to open "Manage Dash". 2) open a scope. 3) swipe left. 4) touch orange ubuntu logo. Expected outcome: main home screen displayed (phone, messaging, contacts, etc). Actual outcome: the scope you opened in (1) is displayed. Steps to get from the scope back to the home screen: 1) Click "back" at top of scope. 2) Click Done. Note that if you mark the scope as a favourite, the next time you launch it touching the orange ubuntu logo *will* take you to the home screen. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- 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/1368135 Title: touching ubuntu icon when (non-favourite) scope open does not display home screen. Status in “unity8” package in Ubuntu: New Bug description: 1) swipe up to open "Manage Dash". 2) open a scope. 3) swipe left. 4) touch orange ubuntu logo. Expected outcome: main home screen displayed (phone, messaging, contacts, etc). Actual outcome: the scope you opened in (1) is displayed. Steps to get from the scope back to the home screen: 1) Click "back" at top of scope. 2) Click Done. Note that if you mark the scope as a favourite, the next time you launch it touching the orange ubuntu logo *will* take you to the home screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368135/+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 1368140] [NEW] add guide lines overlay option
Public bug reported: Both iOS and Android cameras have an option to overlay 2 evenly-spaced vertical and 2 evenly-spaced horizonal white "guide lines". These are a very useful alignment aid when composing a shot. For details: http://en.wikipedia.org/wiki/Rule_of_thirds Bonus points if we could have a Fibonacci spiral option too :-) : http://en.wikipedia.org/wiki/Golden_spiral ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Summary changed: - add guide lines overlay as an option + add guide lines overlay option -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1368140 Title: add guide lines overlay option Status in “camera-app” package in Ubuntu: New Bug description: Both iOS and Android cameras have an option to overlay 2 evenly-spaced vertical and 2 evenly-spaced horizonal white "guide lines". These are a very useful alignment aid when composing a shot. For details: http://en.wikipedia.org/wiki/Rule_of_thirds Bonus points if we could have a Fibonacci spiral option too :-) : http://en.wikipedia.org/wiki/Golden_spiral To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1368140/+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 1366391] Re: re-prompted for already-known password when switching networks
1) Connect to network A. 2) Connect to network B. 3) Re-connect to network A. 4) Attempt to re-connect to network B - this results in a password prompt (it shouldn't as I've already connected in (2)). 5) If I click "cancel", I *do* connect to network B (not the original network A). -- 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/1366391 Title: re-prompted for already-known password when switching networks Status in “indicator-network” package in Ubuntu: Incomplete Bug description: When I re-connect to a known network, I am prompted for the WPA2 password. However, clicking cancel then successfully connects to this network! This is only happening for one of my networks. Not currently sure why since the other main network I use is also WPA2 protected and I'm not prompted for that networks password. I wonder if the re-prompt only occurs if the user attempts to connect to a different network to the first-joined network on boot (can't test atm). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1366391/+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 1366391] Re: re-prompted for already-known password when switching networks
Hi Antii, Having taken a look at them, I don't think they are actually relevant since they are identical apart from the obvious fields (id, uuid, ssid, psk). I'll try and do further tests over the w/e with both networks... -- 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/1366391 Title: re-prompted for already-known password when switching networks Status in “indicator-network” package in Ubuntu: Incomplete Bug description: When I re-connect to a known network, I am prompted for the WPA2 password. However, clicking cancel then successfully connects to this network! This is only happening for one of my networks. Not currently sure why since the other main network I use is also WPA2 protected and I'm not prompted for that networks password. I wonder if the re-prompt only occurs if the user attempts to connect to a different network to the first-joined network on boot (can't test atm). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1366391/+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 1368798] [NEW] horizonal rule on pin unlock screen too thin (looks like a scratch)
Public bug reported: The pin code entry screen has what appears to be a 1 pixel high line horizontal line that goes almost to the left and right borders of the screen, just above the unlock keypad. I can see the value of such a horizontal rule but it is _so_ thin that when I looked at it earlier I thought I'd either scratched the screen or damaged it somehow. Could we possibly make it slightly thicker (or dotted or something) to make it more obviously a ruler and less possibly a scratch/screen damage? :-) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- 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/1368798 Title: horizonal rule on pin unlock screen too thin (looks like a scratch) Status in “unity8” package in Ubuntu: New Bug description: The pin code entry screen has what appears to be a 1 pixel high line horizontal line that goes almost to the left and right borders of the screen, just above the unlock keypad. I can see the value of such a horizontal rule but it is _so_ thin that when I looked at it earlier I thought I'd either scratched the screen or damaged it somehow. Could we possibly make it slightly thicker (or dotted or something) to make it more obviously a ruler and less possibly a scratch/screen damage? :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368798/+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 1368798] Re: horizonal rule on pin unlock screen too thin (looks like a scratch)
root@ubuntu-phablet:~# cat /etc/ubuntu-build 32 root@ubuntu-phablet:~# cat /etc/device-build 20140908-d8c11f3 device: krillin -- 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/1368798 Title: horizonal rule on pin unlock screen too thin (looks like a scratch) Status in “unity8” package in Ubuntu: New Bug description: The pin code entry screen has what appears to be a 1 pixel high line horizontal line that goes almost to the left and right borders of the screen, just above the unlock keypad. I can see the value of such a horizontal rule but it is _so_ thin that when I looked at it earlier I thought I'd either scratched the screen or damaged it somehow. Could we possibly make it slightly thicker (or dotted or something) to make it more obviously a ruler and less possibly a scratch/screen damage? :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368798/+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 1368851] [NEW] adding image creates a confusing "transfer in progress" window
Public bug reported: 1) Add contact. 2) Touch '+' to add a picture. 3) Select a data source (gallery, camera, file manager, etc). 4) Slow swipe from right to show all running apps windows. 5) Observe an app window that has a spinner on a white dialog background with text "Transfer in progress" along with a cancel button. Presumably (5) is somehow connecting the address book and the data source (file manager say), like an Android Intent, but do we really need to see this app window? The answer currently seems to be "sometimes": - If I select gallery as the data source in (3) the top of the gallery window shows a cross which, if clicked, closes both gallery *and* the "Transfer in progress" window. So for gallery, the "Transfer in progress" seems entirely redundant. - If I select file manager as the data source in (3) the top of the file manager window does not show a cross so the way to abort the "attach image to new contact" operation seems to be to click cancel on the "Transfer in progress" window (or just close the file manager). The above suggests that all the data sources should support the interface that the gallery seems to. That way, this confusing Transfer window can die. ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New ** Tags: avengers ** Summary changed: - adding image creates a confusing "transfer in progress" app + adding image creates a confusing "transfer in progress" window -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1368851 Title: adding image creates a confusing "transfer in progress" window Status in “address-book-app” package in Ubuntu: New Bug description: 1) Add contact. 2) Touch '+' to add a picture. 3) Select a data source (gallery, camera, file manager, etc). 4) Slow swipe from right to show all running apps windows. 5) Observe an app window that has a spinner on a white dialog background with text "Transfer in progress" along with a cancel button. Presumably (5) is somehow connecting the address book and the data source (file manager say), like an Android Intent, but do we really need to see this app window? The answer currently seems to be "sometimes": - If I select gallery as the data source in (3) the top of the gallery window shows a cross which, if clicked, closes both gallery *and* the "Transfer in progress" window. So for gallery, the "Transfer in progress" seems entirely redundant. - If I select file manager as the data source in (3) the top of the file manager window does not show a cross so the way to abort the "attach image to new contact" operation seems to be to click cancel on the "Transfer in progress" window (or just close the file manager). The above suggests that all the data sources should support the interface that the gallery seems to. That way, this confusing Transfer window can die. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1368851/+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 1369450] [NEW] adb shell sudo shows password in the clear
*** This bug is a security vulnerability *** Public security bug reported: $ adb shell sudo id [sudo] password for phablet: you should not be able to see this!!! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: android-tools-adb 4.2.2+git20130218-3ubuntu35 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 15 09:43:59 2014 InstallationDate: Installed on 2014-04-11 (156 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: android-tools UpgradeStatus: Upgraded to utopic on 2014-05-08 (129 days ago) ** Affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1369450 Title: adb shell sudo shows password in the clear Status in “android-tools” package in Ubuntu: New Bug description: $ adb shell sudo id [sudo] password for phablet: you should not be able to see this!!! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: android-tools-adb 4.2.2+git20130218-3ubuntu35 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 15 09:43:59 2014 InstallationDate: Installed on 2014-04-11 (156 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: android-tools UpgradeStatus: Upgraded to utopic on 2014-05-08 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1369450/+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 1369453] [NEW] able to view and change indicators without unlocking phone
*** This bug is a security vulnerability *** Public security bug reported: This is a pretty significant security issue that affects: - networking - able to switch networks without entering pin to unlock phone - GPS - can toggle. - bluetooth - can toggle. - upcoming events - can view. ** Affects: indicator-location (Ubuntu) Importance: Undecided Status: New ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Tags: avengers ** Information type changed from Public to Public Security -- 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/1369453 Title: able to view and change indicators without unlocking phone Status in “indicator-location” package in Ubuntu: New Status in “indicator-network” package in Ubuntu: New Bug description: This is a pretty significant security issue that affects: - networking - able to switch networks without entering pin to unlock phone - GPS - can toggle. - bluetooth - can toggle. - upcoming events - can view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1369453/+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 1369453] Re: able to view and change indicators without unlocking phone
phablet@ubuntu-phablet:~$ cat /etc/ubuntu-build 40 phablet@ubuntu-phablet:~$ cat /etc/device-build 20140908-d8c11f3 phablet@ubuntu-phablet:~$ krillin. ** Also affects: indicator-location (Ubuntu) Importance: Undecided Status: New -- 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/1369453 Title: able to view and change indicators without unlocking phone Status in “indicator-location” package in Ubuntu: New Status in “indicator-network” package in Ubuntu: New Bug description: This is a pretty significant security issue that affects: - networking - able to switch networks without entering pin to unlock phone - GPS - can toggle. - bluetooth - can toggle. - upcoming events - can view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1369453/+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 1369457] [NEW] able to left swipe and see launcher icons without unlocking phone
*** This bug is a security vulnerability *** Public security bug reported: This is atleast a privacy issue but could also be a security depending on exactly what apps the user has pinned to their launcher. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- 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/1369457 Title: able to left swipe and see launcher icons without unlocking phone Status in “unity8” package in Ubuntu: New Bug description: This is atleast a privacy issue but could also be a security depending on exactly what apps the user has pinned to their launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1369457/+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 1369457] Re: able to left swipe and see launcher icons without unlocking phone
phablet@ubuntu-phablet:~$ cat /etc/ubuntu-build 40 phablet@ubuntu-phablet:~$ cat /etc/device-build 20140908-d8c11f3 krillin ** Information type changed from Public to Public Security -- 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/1369457 Title: able to left swipe and see launcher icons without unlocking phone Status in “unity8” package in Ubuntu: New Bug description: This is atleast a privacy issue but could also be a security depending on exactly what apps the user has pinned to their launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1369457/+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 1369468] [NEW] no warning when volume increased to maximum and headphones plugged
Public bug reported: Android gives the user a warning if they attempt to raise the volume to 100% when headphones are plugged. This is a sensible precaution both to save the user from tinnitus and to avoid any potential legal repercussions. ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1369468 Title: no warning when volume increased to maximum and headphones plugged Status in “indicator-sound” package in Ubuntu: New Bug description: Android gives the user a warning if they attempt to raise the volume to 100% when headphones are plugged. This is a sensible precaution both to save the user from tinnitus and to avoid any potential legal repercussions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1369468/+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 1369457] Re: able to left swipe and launch apps without unlocking phone
You can also re-order the launcher icons. -- 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/1369457 Title: able to left swipe and launch apps without unlocking phone Status in “unity8” package in Ubuntu: New Bug description: This is atleast a privacy issue but could also be a security depending on exactly what apps the user has pinned to their launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1369457/+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 1369457] Re: able to left swipe and launch apps without unlocking phone
This is worse that I originally though since you can actually *launch* any app on the launcher without unlocking the phone. You can't see it, but it is running (unlocking confirms this). ** Summary changed: - able to left swipe and see launcher icons without unlocking phone + able to left swipe and launch apps without unlocking phone -- 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/1369457 Title: able to left swipe and launch apps without unlocking phone Status in “unity8” package in Ubuntu: New Bug description: This is atleast a privacy issue but could also be a security depending on exactly what apps the user has pinned to their launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1369457/+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 1369457] Re: able to left swipe and launch apps without unlocking phone
To start an app: 1) Swipe left to show launcher. 2) Keeping finger down in (1) long press an app icon in the launcher. 3) Remove both fingers from screen. 4) Swipe left to show launcher again. 5) Launcher should remain on screen allowing you to touch an app icon to launch it. See attached. ** Attachment added: "launcher-shown-with-screen-locked.png" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1369457/+attachment/4204323/+files/launcher-shown-with-screen-locked.png -- 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/1369457 Title: able to left swipe and launch apps without unlocking phone Status in “unity8” package in Ubuntu: New Bug description: This is atleast a privacy issue but could also be a security depending on exactly what apps the user has pinned to their launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1369457/+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 1369457] Re: able to left swipe and launch apps without unlocking phone
Note sure if this is also a bug (I think it is), but in testing this, I have inadvertantly managed to delete the system settings icon by moving it. It seems the operation failed as shown in the screenshot. ** Attachment added: "floating-system-settings.png" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1369457/+attachment/4204324/+files/floating-system-settings.png -- 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/1369457 Title: able to left swipe and launch apps without unlocking phone Status in “unity8” package in Ubuntu: New Bug description: This is atleast a privacy issue but could also be a security depending on exactly what apps the user has pinned to their launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1369457/+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 1369457] Re: able to left swipe and launch apps without unlocking phone
That failed operation has seemingly corrupted a list somewhere since now touching my gmail icon actually launches system settings (spoofing potential here). Attached screenshot shows this. ** Attachment added: "gmail-is-now-system-settings.png" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1369457/+attachment/4204325/+files/gmail-is-now-system-settings.png -- 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/1369457 Title: able to left swipe and launch apps without unlocking phone Status in “unity8” package in Ubuntu: New Bug description: This is atleast a privacy issue but could also be a security depending on exactly what apps the user has pinned to their launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1369457/+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 1369457] Re: Can re-order and un-pin launcher items while phone is locked
Personally, I'm happy for the lock screen to show date+time but I would
prefer everything else to be hidden (or ateast hideable with a system-
setting) until the phone is unlocked.
The majority of users may not mind if the notification bar is displayed
when the screen is locked (Android does this), but I think it would be
prudent to add an option to hide this as some users/customers will
prefer to minimise any privacy leakage (particularly if we grow the
scope of the notification bar in the future).
Regarding the launcher:
1) What is the use-case for wanting to launch an app when the phone is locked?
2) What is the use-case for wanting to re-order the icons when the phone is
locked?
I don't believe users would be happy if either of the above actions
could occur on a desktop system, so why allow it on Touch?
If nothing else, allowing such features increases the probability of
pocket-dialing-type issues ("I left the phone in state X but now I come
to unlock the phone it's mysteriously in state Y. What happened?")
** Summary changed:
- Can re-order and un-pin launcher items while phone is locked
+ Can re-order and un-pin launcher items and launch apps while phone is locked
--
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/1369457
Title:
Can re-order and un-pin launcher items and launch apps while phone is
locked
Status in Ubuntu UX bugs:
New
Status in “unity8” package in Ubuntu:
New
Bug description:
This is atleast a privacy issue but could also be a security depending
on exactly what apps the user has pinned to their launcher.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1369457/+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 1369457] Re: Can re-order and un-pin launcher items and launch apps while phone is locked
Update to #6: rebooting the phone brought back the original set of icons such that touching system-settings launches the correct app and ditto for gmail. -- 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/1369457 Title: Can re-order and un-pin launcher items and launch apps while phone is locked Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: This is atleast a privacy issue but could also be a security depending on exactly what apps the user has pinned to their launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1369457/+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 1369457] Re: Can re-order and un-pin launcher items and launch apps while phone is locked
Ah thanks - didn't know about those options! Disabled both now :-) > The use case for launching apps from the lockscreen is that as a user, you > think "oh I want to go to facebook", > click facebook, we start the app in the background so that once you enter > your passcode, it's sitting there ready. > Again, Design and Security have already talked about this feature and were > planning to leave it as is. > Please let's not have a title-editing fight over this. The fact that I raised this bug demonstrates that I was not aware of these discussions. Personally, I cannot see a huge benefit in allowing this behaviour. Maybe if a particular app is very slow to start and/or if a user has a particularly long pass-phrase this could be marginally useful? But to counter that, what if you have an app that sucks down huge amounts of data on startup and a nefarious user starts the app without your knowledge when you happen to put your phone down for a minute? That would be more than a little annoying if 3G charges applied. It could be argued that the risk of that scenario playing out is small, but nevertheless the potential is there. > The use case for re-ordering apps is *likely to be* (Design hasn't actually > chimed in) that the person doing the > re-ordering is overwhelmingly likely to be the owner, rather than some > malicious attacker that just loves to re-order > your icons. Again, I personally don't see that feature as particularly compelling, hence I've turned it off :) If these features are perceived as generally useful are we planning on introducing them to desktop Ubuntu? Regardless of whether we decide to leave these features as enabled or not, maybe we should ensure they form part of the initial setup wizard? -- 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/1369457 Title: Can re-order and un-pin launcher items and launch apps while phone is locked Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: This is atleast a privacy issue but could also be a security depending on exactly what apps the user has pinned to their launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1369457/+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 1357252] Re: upstart can race with cgmanager when using remove-on-empty
Back link to test plan: https://wiki.ubuntu.com/Process/TestPlans /systemd-shim -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: upstart can race with cgmanager when using remove-on-empty Status in Ubuntu Application Launcher: Invalid Status in Upstart: Fix Released Status in “cgmanager” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Status in “cgmanager” package in Ubuntu RTM: Fix Released Status in “upstart” package in Ubuntu RTM: Fix Released Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+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 1369703] Re: upstart-monitor requires Gtk GIR bits
*** This bug is a duplicate of bug 1235245 *** https://bugs.launchpad.net/bugs/1235245 ** This bug has been marked a duplicate of bug 1235245 upstart-monitor cannot run without gtk libraries installed -- 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/1369703 Title: upstart-monitor requires Gtk GIR bits Status in “upstart” package in Ubuntu: New Bug description: Hey, due to this: class UpstartEventsGui(Gtk.Window): upstart-monitor fails to start when the gi.repository.Gtk import failed (was skipped). Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1369703/+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 1235245] Re: upstart-monitor cannot run without gtk libraries installed
** Also affects: upstart (Ubuntu) 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/1235245 Title: upstart-monitor cannot run without gtk libraries installed Status in Upstart: New Status in “upstart” package in Ubuntu: Confirmed Bug description: "upstart-monitor -n" should revert to cli operation. It attempts to do this, but then barfs on class UpstartEventsGui(Gtk.Window) since Gtk is not imported unless the required gtk libraries are installed. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235245/+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 1356863] Re: unable to zoom out using pinch
Confirmed - thanks! ** Description changed: Actually, there are a couple of problems here: 1) If you "reverse pinch" to zoom into an image, this appears to trigger "zoom to maximum size" (aka double-tap). Reverse pinch should just "zoom - on". + in". 2) Having zoomed into an image, if you attempt to pinch to zoom out of the image nothing happens. Double-tapping does do revert the image to its original size, but pinching is more intuitive so should work as expected. - $ adb shell cat /etc/ubuntu-build 188 $ adb shell cat /etc/device-build b03133e -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1356863 Title: unable to zoom out using pinch Status in “gallery-app” package in Ubuntu: Fix Released Bug description: Actually, there are a couple of problems here: 1) If you "reverse pinch" to zoom into an image, this appears to trigger "zoom to maximum size" (aka double-tap). Reverse pinch should just "zoom in". 2) Having zoomed into an image, if you attempt to pinch to zoom out of the image nothing happens. Double-tapping does do revert the image to its original size, but pinching is more intuitive so should work as expected. $ adb shell cat /etc/ubuntu-build 188 $ adb shell cat /etc/device-build b03133e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1356863/+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 1365492] Re: selecting previously visited site from address bar does nothing
Testing on krillin image #44, the problem is no longer seen. -- 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/1365492 Title: selecting previously visited site from address bar does nothing Status in “webbrowser-app” package in Ubuntu: Fix Released Bug description: 1) Visit a web site by clicking in the address bar and specifying the URL. 2) Visit a different site by clicking in the address bar and specifying the URL. 3) Touch in the address bar and type a few characters from the URL for the site in (1). 4) The browser will prompt with the full URL for (1) below the address bar. 5) Touch the full URL in (4). Expected outcome: Browser displays site at (1). Actual outcome: phone shakes to confirm that you've touched an element and then nothing happens. root@ubuntu-phablet:~# cat /etc/ubuntu-build 16 root@ubuntu-phablet:~# cat /etc/device-build 20140903-d4c824a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1365492/+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 1338637] Re: continuous re-exec can result in a build-up of inotify fds
** Also affects: upstart (Ubuntu) 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/1338637 Title: continuous re-exec can result in a build-up of inotify fds Status in Upstart: Fix Released Status in “upstart” package in Ubuntu: New Bug description: $ sudo ls -al /proc/1/fd|grep anon|wc -l 2 $ i=0; while [ $i -lt 1024 ]; do sudo telinit u; i=$((i+1)); done $ sudo ls -al /proc/1/fd|grep anon|wc -l 106 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1338637/+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 1338637] Re: continuous re-exec can result in a build-up of inotify fds [SRU]
** Summary changed: - continuous re-exec can result in a build-up of inotify fds + continuous re-exec can result in a build-up of inotify fds [SRU] -- 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/1338637 Title: continuous re-exec can result in a build-up of inotify fds [SRU] Status in Upstart: Fix Released Status in “upstart” package in Ubuntu: New Status in “upstart” source package in Trusty: New Bug description: $ sudo ls -al /proc/1/fd|grep anon|wc -l 2 $ i=0; while [ $i -lt 1024 ]; do sudo telinit u; i=$((i+1)); done $ sudo ls -al /proc/1/fd|grep anon|wc -l 106 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1338637/+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 1338637] Re: continuous re-exec can result in a build-up of inotify fds [SRU]
** Description changed:
+ = PROBLEM =
+
+ The version of Upstart currently in trusty (1.12.1-0ubuntu4.2) suffers
+ from a couple of problems which in combination could make upgrading
+ difficult on systems with high uptimes.
+
+ The 2 issues are:
+
+ == bug 901038 ==
+
+ The issue here is that telinit in trusty is not fully synchronous. This
+ is not normally a problem. However if Upstart is re-exec'ed using
+ 'telinit u', as is done by the maintainer scripts for the following
packages...
+
+ - libc6
+ - libdbus-1-3
+ - libjson-c2
+ - libnih1
+ - libnih-dbus1
+ - libselinux1
+ - libsepol1
+ - upstart
+
+ ... and if that operation is slow (it is normally extremely fast),
+ subsequent package upgrades (part of the same apt-get run) which *also*
+ need to restart Upstart may fail since 'telinit u' is unable to connect
+ to PID 1 as a result of Upstart still being in the process of
+ re-exec'ing from the last call to 'telinit u'.
+
+
+ == bug 1338637 ==
+
+ This bug only really affects server systems which have high uptimes. If
+ a re-exec is triggered via 'telinit u' as part of a package upgrade (see
+ above), Upstart will consume 2 additional inotify watches. Although this
+ doesn't affect the correct behaviour of Upstart, it does have two
+ repercussions:
+
+ a) It wastes inotify watches.
+ b) It slows down an Upstart re-exec ('telinit u').
+
+ Note that the slow-down for a vanilla Trusty server may not be
+ detectable unless the value of /proc/sys/fs/inotify/max_user_instances
+ has been raised above the default value of 128.
+
+
+ = FIX DETAILS =
+
+ == bug 901038 ==
+
+ The fix for this bug now makes 'telinit u' block until the re-exec
+ operation has completed fully.
+
+ Technically, it is not possible to make 'telinit u' synchronous since
+ because D-Bus connections cannot be serialised and since the 'telinit u'
+ request is made via a D-Bus connection, when Upstart re-exec's, it has
+ to sever all D-Bus connections, including the 'telinit u' D-Bus
+ connection. As such, 'telinit u' now performs the following operations:
+
+ - Requests synchronously that Upstart re-exec itself.
+ - Polls Upstart "forever" by attempting to connect to PID 1 and if
+ that operation fails, waiting for a period, the retrying.
+
+ The code is well commented to explain this less-than-ideal but
+ nonetheless essential poll operation:
+
+ http://bazaar.launchpad.net/~upstart-
+ devel/upstart/trunk/view/head:/util/telinit.c#L171
+
+ == bug 1338637 ==
+
+ This was a simple bug fix.
+
+
+ = FIX AVAILABILITY =
+
+ TBD.
+
+
+ = IMPACT =
+
+ On a high uptime server, the more times that 'telinit u' is called (as
+ the result of normal apt-get updates to any of the packages listed under
+ bug 901038 above), the slower the operation will take to complete, and
+ thus the likelihood of bug 901038 being seen will increase.
+
+
+ = JUSTIFICATION =
+
+ System updates need to "just work". However, as outlined above, the
+ longer a systems uptime, the more likely it is to be affected by this
+ issue which increases the likelihood of a system update failure.
+
+ This issue needs to be fixed as soon as possible to minimise issues for
+ trusty users and administrators, particularly before any potential
+ upgrade to Utopic.
+
+
+ = TEST CASE =
+
+ == To demonstrate bug 1338637 ==
+
+ $ sudo telinit u
+ $ sudo ls -l /proc/1/fd|grep inotify|wc -l
+
+ The correct output from the above 2 commands should be simply "2".
+
+ However, on trusty systems, if the commands above are run after a fresh
+ boot, the value will in all likelihood be "4". Also, every subsequent
+ 'telinit u' will increase the number displayed by 2.
+
+ == To demonstrate bug 901038 ==
+
+ for i in $(seq 10); do telinit u; done
+
+ There should be no output from the command-line above, but on a trusty
+ system the chances are that one or more lines will display like this:
+
+ $ for i in $(seq 5); do sudo telinit u;done
+ telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
+ telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
+ telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
+
+ == To prove the overall problem has been fixed ==
+
+ 1) Download the attached "force-reexec.sh" onto a trusty system.
+ 2) Make executable:
+
+$ chmod 755 ./force-reexec.sh
+
+ 3) Run script as root, specifying a number of iterations (100) and
+saving output to file "./typescript.bad":
+
+$ script -c 'sudo ./force-reexec.sh 100' typescript.bad
+
+ 4) Upgrade to latest version of Upstart that fixes the 2 bugs.
+
+ 5) Reboot.
+
+ 6) Re-run the script
+
+$ script -c 'sudo ./force-reexec.sh 100' typescript.good
+
+ 7) Check the results:
+
+- file "typescript.bad" will show an increasing number of watches
+ and *MAY* show a slowly increasing restart time (depending on
+ the value of /proc/sys/fs/inotify/max_user_instances (see a
[Touch-packages] [Bug 1338637] Re: continuous re-exec can result in a build-up of inotify fds [SRU]
** Attachment added: "Output of force-reexec.sh on a trusty system with fixes
for both bugs, showing the problem has been resolved."
https://bugs.launchpad.net/upstart/+bug/1338637/+attachment/4207317/+files/typescript.good
** Description changed:
= PROBLEM =
The version of Upstart currently in trusty (1.12.1-0ubuntu4.2) suffers
from a couple of problems which in combination could make upgrading
difficult on systems with high uptimes.
The 2 issues are:
== bug 901038 ==
The issue here is that telinit in trusty is not fully synchronous. This
is not normally a problem. However if Upstart is re-exec'ed using
'telinit u', as is done by the maintainer scripts for the following
packages...
- - libc6
- - libdbus-1-3
- - libjson-c2
- - libnih1
- - libnih-dbus1
- - libselinux1
- - libsepol1
- - upstart
+ - libc6
+ - libdbus-1-3
+ - libjson-c2
+ - libnih1
+ - libnih-dbus1
+ - libselinux1
+ - libsepol1
+ - upstart
... and if that operation is slow (it is normally extremely fast),
subsequent package upgrades (part of the same apt-get run) which *also*
need to restart Upstart may fail since 'telinit u' is unable to connect
to PID 1 as a result of Upstart still being in the process of
re-exec'ing from the last call to 'telinit u'.
-
== bug 1338637 ==
This bug only really affects server systems which have high uptimes. If
a re-exec is triggered via 'telinit u' as part of a package upgrade (see
above), Upstart will consume 2 additional inotify watches. Although this
doesn't affect the correct behaviour of Upstart, it does have two
repercussions:
a) It wastes inotify watches.
b) It slows down an Upstart re-exec ('telinit u').
Note that the slow-down for a vanilla Trusty server may not be
detectable unless the value of /proc/sys/fs/inotify/max_user_instances
has been raised above the default value of 128.
-
= FIX DETAILS =
== bug 901038 ==
The fix for this bug now makes 'telinit u' block until the re-exec
operation has completed fully.
Technically, it is not possible to make 'telinit u' synchronous since
because D-Bus connections cannot be serialised and since the 'telinit u'
request is made via a D-Bus connection, when Upstart re-exec's, it has
to sever all D-Bus connections, including the 'telinit u' D-Bus
connection. As such, 'telinit u' now performs the following operations:
- - Requests synchronously that Upstart re-exec itself.
- - Polls Upstart "forever" by attempting to connect to PID 1 and if
- that operation fails, waiting for a period, the retrying.
+ - Requests synchronously that Upstart re-exec itself.
+ - Polls Upstart "forever" by attempting to connect to PID 1 and if
+ that operation fails, waiting for a period, the retrying.
The code is well commented to explain this less-than-ideal but
nonetheless essential poll operation:
- http://bazaar.launchpad.net/~upstart-
+ http://bazaar.launchpad.net/~upstart-
devel/upstart/trunk/view/head:/util/telinit.c#L171
== bug 1338637 ==
This was a simple bug fix.
-
= FIX AVAILABILITY =
TBD.
-
= IMPACT =
On a high uptime server, the more times that 'telinit u' is called (as
the result of normal apt-get updates to any of the packages listed under
bug 901038 above), the slower the operation will take to complete, and
thus the likelihood of bug 901038 being seen will increase.
-
= JUSTIFICATION =
System updates need to "just work". However, as outlined above, the
longer a systems uptime, the more likely it is to be affected by this
issue which increases the likelihood of a system update failure.
This issue needs to be fixed as soon as possible to minimise issues for
trusty users and administrators, particularly before any potential
upgrade to Utopic.
-
= TEST CASE =
== To demonstrate bug 1338637 ==
$ sudo telinit u
$ sudo ls -l /proc/1/fd|grep inotify|wc -l
The correct output from the above 2 commands should be simply "2".
However, on trusty systems, if the commands above are run after a fresh
boot, the value will in all likelihood be "4". Also, every subsequent
'telinit u' will increase the number displayed by 2.
== To demonstrate bug 901038 ==
for i in $(seq 10); do telinit u; done
There should be no output from the command-line above, but on a trusty
system the chances are that one or more lines will display like this:
$ for i in $(seq 5); do sudo telinit u;done
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
== To prove the overall problem has been fixed ==
1) Download the attached "force-reexec.sh" onto a trusty system.
2) Make executable:
-$ chmod 755 ./force-reexec.sh
+
[Touch-packages] [Bug 1338637] Re: continuous re-exec can result in a build-up of inotify fds [SRU]
** Attachment added: "Output of force-reexec.sh on a trusty system
demonstrating the problem."
https://bugs.launchpad.net/upstart/+bug/1338637/+attachment/4207316/+files/typescript.bad
--
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/1338637
Title:
continuous re-exec can result in a build-up of inotify fds [SRU]
Status in Upstart:
Fix Released
Status in “upstart” package in Ubuntu:
New
Status in “upstart” source package in Trusty:
New
Bug description:
= PROBLEM =
The version of Upstart currently in trusty (1.12.1-0ubuntu4.2) suffers
from a couple of problems which in combination could make upgrading
difficult on systems with high uptimes.
The 2 issues are:
== bug 901038 ==
The issue here is that telinit in trusty is not fully synchronous. This
is not normally a problem. However if Upstart is re-exec'ed using
'telinit u', as is done by the maintainer scripts for the following
packages...
- libc6
- libdbus-1-3
- libjson-c2
- libnih1
- libnih-dbus1
- libselinux1
- libsepol1
- upstart
... and if that operation is slow (it is normally extremely fast),
subsequent package upgrades (part of the same apt-get run) which *also*
need to restart Upstart may fail since 'telinit u' is unable to connect
to PID 1 as a result of Upstart still being in the process of
re-exec'ing from the last call to 'telinit u'.
== bug 1338637 ==
This bug only really affects server systems which have high uptimes. If
a re-exec is triggered via 'telinit u' as part of a package upgrade (see
above), Upstart will consume 2 additional inotify watches. Although this
doesn't affect the correct behaviour of Upstart, it does have two
repercussions:
a) It wastes inotify watches.
b) It slows down an Upstart re-exec ('telinit u').
Note that the slow-down for a vanilla Trusty server may not be
detectable unless the value of /proc/sys/fs/inotify/max_user_instances
has been raised above the default value of 128.
= FIX DETAILS =
== bug 901038 ==
The fix for this bug now makes 'telinit u' block until the re-exec
operation has completed fully.
Technically, it is not possible to make 'telinit u' synchronous since
because D-Bus connections cannot be serialised and since the 'telinit u'
request is made via a D-Bus connection, when Upstart re-exec's, it has
to sever all D-Bus connections, including the 'telinit u' D-Bus
connection. As such, 'telinit u' now performs the following operations:
- Requests synchronously that Upstart re-exec itself.
- Polls Upstart "forever" by attempting to connect to PID 1 and if
that operation fails, waiting for a period, the retrying.
The code is well commented to explain this less-than-ideal but
nonetheless essential poll operation:
http://bazaar.launchpad.net/~upstart-
devel/upstart/trunk/view/head:/util/telinit.c#L171
== bug 1338637 ==
This was a simple bug fix.
= FIX AVAILABILITY =
TBD.
= IMPACT =
On a high uptime server, the more times that 'telinit u' is called (as
the result of normal apt-get updates to any of the packages listed under
bug 901038 above), the slower the operation will take to complete, and
thus the likelihood of bug 901038 being seen will increase.
= JUSTIFICATION =
System updates need to "just work". However, as outlined above, the
longer a systems uptime, the more likely it is to be affected by this
issue which increases the likelihood of a system update failure.
This issue needs to be fixed as soon as possible to minimise issues for
trusty users and administrators, particularly before any potential
upgrade to Utopic.
= TEST CASE =
== To demonstrate bug 1338637 ==
$ sudo telinit u
$ sudo ls -l /proc/1/fd|grep inotify|wc -l
The correct output from the above 2 commands should be simply "2".
However, on trusty systems, if the commands above are run after a fresh
boot, the value will in all likelihood be "4". Also, every subsequent
'telinit u' will increase the number displayed by 2.
== To demonstrate bug 901038 ==
for i in $(seq 10); do telinit u; done
There should be no output from the command-line above, but on a trusty
system the chances are that one or more lines will display like this:
$ for i in $(seq 5); do sudo telinit u;done
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
== To prove the overall problem has been fixed ==
1) Download the attached "force-reexec.sh" onto a trusty system.
2) Make executable:
$ chmod 755 ./force-reexec.sh
3) Run script as root, specifying a number of iterations (100) and
saving output to file "./typescript.bad":
[Touch-packages] [Bug 1338637] Re: continuous re-exec can result in a build-up of inotify fds [SRU]
The fix for bug 901038 is available upstream but is not yet in Utopic.
Since this is a fundamental system tool, we need to wait until this has
had testing in utopic prior to progressing this SRU.
Plan:
1) Get lp:~jamesodhunt/upstart/bug-1360208 reviewed and landed upstream
(hopefully this week).
2) Release upstart 1.13.3 (including the fix for bug 901038).
3) Land upstart 1.13.3 in utopic.
4) Wait for a few days.
5) Cherry-pick to trusty to allow this SRU to progress.
--
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/1338637
Title:
continuous re-exec can result in a build-up of inotify fds [SRU]
Status in Upstart:
Fix Released
Status in “upstart” package in Ubuntu:
New
Status in “upstart” source package in Trusty:
New
Bug description:
= PROBLEM =
The version of Upstart currently in trusty (1.12.1-0ubuntu4.2) suffers
from a couple of problems which in combination could make upgrading
difficult on systems with high uptimes.
The 2 issues are:
== bug 901038 ==
The issue here is that telinit in trusty is not fully synchronous. This
is not normally a problem. However if Upstart is re-exec'ed using
'telinit u', as is done by the maintainer scripts for the following
packages...
- libc6
- libdbus-1-3
- libjson-c2
- libnih1
- libnih-dbus1
- libselinux1
- libsepol1
- upstart
... and if that operation is slow (it is normally extremely fast),
subsequent package upgrades (part of the same apt-get run) which *also*
need to restart Upstart may fail since 'telinit u' is unable to connect
to PID 1 as a result of Upstart still being in the process of
re-exec'ing from the last call to 'telinit u'.
== bug 1338637 ==
This bug only really affects server systems which have high uptimes. If
a re-exec is triggered via 'telinit u' as part of a package upgrade (see
above), Upstart will consume 2 additional inotify watches. Although this
doesn't affect the correct behaviour of Upstart, it does have two
repercussions:
a) It wastes inotify watches.
b) It slows down an Upstart re-exec ('telinit u').
Note that the slow-down for a vanilla Trusty server may not be
detectable unless the value of /proc/sys/fs/inotify/max_user_instances
has been raised above the default value of 128.
= FIX DETAILS =
== bug 901038 ==
The fix for this bug now makes 'telinit u' block until the re-exec
operation has completed fully.
Technically, it is not possible to make 'telinit u' synchronous since
because D-Bus connections cannot be serialised and since the 'telinit u'
request is made via a D-Bus connection, when Upstart re-exec's, it has
to sever all D-Bus connections, including the 'telinit u' D-Bus
connection. As such, 'telinit u' now performs the following operations:
- Requests synchronously that Upstart re-exec itself.
- Polls Upstart "forever" by attempting to connect to PID 1 and if
that operation fails, waiting for a period, the retrying.
The code is well commented to explain this less-than-ideal but
nonetheless essential poll operation:
http://bazaar.launchpad.net/~upstart-
devel/upstart/trunk/view/head:/util/telinit.c#L171
== bug 1338637 ==
This was a simple bug fix.
= FIX AVAILABILITY =
TBD.
= IMPACT =
On a high uptime server, the more times that 'telinit u' is called (as
the result of normal apt-get updates to any of the packages listed under
bug 901038 above), the slower the operation will take to complete, and
thus the likelihood of bug 901038 being seen will increase.
= JUSTIFICATION =
System updates need to "just work". However, as outlined above, the
longer a systems uptime, the more likely it is to be affected by this
issue which increases the likelihood of a system update failure.
This issue needs to be fixed as soon as possible to minimise issues for
trusty users and administrators, particularly before any potential
upgrade to Utopic.
= TEST CASE =
== To demonstrate bug 1338637 ==
$ sudo telinit u
$ sudo ls -l /proc/1/fd|grep inotify|wc -l
The correct output from the above 2 commands should be simply "2".
However, on trusty systems, if the commands above are run after a fresh
boot, the value will in all likelihood be "4". Also, every subsequent
'telinit u' will increase the number displayed by 2.
== To demonstrate bug 901038 ==
for i in $(seq 10); do telinit u; done
There should be no output from the command-line above, but on a trusty
system the chances are that one or more lines will display like this:
$ for i in $(seq 5); do sudo telinit u;done
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
== To pr
[Touch-packages] [Bug 1338637] Re: continuous re-exec can result in a build-up of inotify fds [SRU]
** Description changed:
= PROBLEM =
The version of Upstart currently in trusty (1.12.1-0ubuntu4.2) suffers
from a couple of problems which in combination could make upgrading
difficult on systems with high uptimes.
The 2 issues are:
== bug 901038 ==
The issue here is that telinit in trusty is not fully synchronous. This
is not normally a problem. However if Upstart is re-exec'ed using
'telinit u', as is done by the maintainer scripts for the following
packages...
- libc6
- libdbus-1-3
- libjson-c2
- libnih1
- libnih-dbus1
- libselinux1
- libsepol1
- upstart
... and if that operation is slow (it is normally extremely fast),
subsequent package upgrades (part of the same apt-get run) which *also*
need to restart Upstart may fail since 'telinit u' is unable to connect
to PID 1 as a result of Upstart still being in the process of
re-exec'ing from the last call to 'telinit u'.
== bug 1338637 ==
This bug only really affects server systems which have high uptimes. If
a re-exec is triggered via 'telinit u' as part of a package upgrade (see
above), Upstart will consume 2 additional inotify watches. Although this
doesn't affect the correct behaviour of Upstart, it does have two
repercussions:
a) It wastes inotify watches.
b) It slows down an Upstart re-exec ('telinit u').
Note that the slow-down for a vanilla Trusty server may not be
detectable unless the value of /proc/sys/fs/inotify/max_user_instances
has been raised above the default value of 128.
= FIX DETAILS =
== bug 901038 ==
The fix for this bug now makes 'telinit u' block until the re-exec
operation has completed fully.
Technically, it is not possible to make 'telinit u' synchronous since
because D-Bus connections cannot be serialised and since the 'telinit u'
request is made via a D-Bus connection, when Upstart re-exec's, it has
to sever all D-Bus connections, including the 'telinit u' D-Bus
connection. As such, 'telinit u' now performs the following operations:
- Requests synchronously that Upstart re-exec itself.
- Polls Upstart "forever" by attempting to connect to PID 1 and if
that operation fails, waiting for a period, the retrying.
The code is well commented to explain this less-than-ideal but
nonetheless essential poll operation:
http://bazaar.launchpad.net/~upstart-
devel/upstart/trunk/view/head:/util/telinit.c#L171
== bug 1338637 ==
This was a simple bug fix.
= FIX AVAILABILITY =
TBD.
= IMPACT =
On a high uptime server, the more times that 'telinit u' is called (as
the result of normal apt-get updates to any of the packages listed under
bug 901038 above), the slower the operation will take to complete, and
thus the likelihood of bug 901038 being seen will increase.
= JUSTIFICATION =
System updates need to "just work". However, as outlined above, the
longer a systems uptime, the more likely it is to be affected by this
issue which increases the likelihood of a system update failure.
This issue needs to be fixed as soon as possible to minimise issues for
trusty users and administrators, particularly before any potential
upgrade to Utopic.
= TEST CASE =
== To demonstrate bug 1338637 ==
$ sudo telinit u
$ sudo ls -l /proc/1/fd|grep inotify|wc -l
The correct output from the above 2 commands should be simply "2".
However, on trusty systems, if the commands above are run after a fresh
boot, the value will in all likelihood be "4". Also, every subsequent
'telinit u' will increase the number displayed by 2.
== To demonstrate bug 901038 ==
for i in $(seq 10); do telinit u; done
There should be no output from the command-line above, but on a trusty
system the chances are that one or more lines will display like this:
$ for i in $(seq 5); do sudo telinit u;done
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
== To prove the overall problem has been fixed ==
1) Download the attached "force-reexec.sh" onto a trusty system.
2) Make executable:
$ chmod 755 ./force-reexec.sh
3) Run script as root, specifying a number of iterations (100) and
saving output to file "./typescript.bad":
$ script -c 'sudo ./force-reexec.sh 100' typescript.bad
4) Upgrade to latest version of Upstart that fixes the 2 bugs.
5) Reboot.
6) Re-run the script
$ script -c 'sudo ./force-reexec.sh 100' typescript.good
7) Check the results:
- file "typescript.bad" will show an increasing number of watches
and *MAY* show a slowly increasing restart time (depending on
the value of /proc/sys/fs/inotify/max_user_instances (see above)).
- fi
[Touch-packages] [Bug 1338637] Re: continuous re-exec can result in a build-up of inotify fds [SRU]
A test branch is available here: lp:~jamesodhunt/ubuntu/trusty/upstart
/SRU-bugs-901038+1338637
--
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/1338637
Title:
continuous re-exec can result in a build-up of inotify fds [SRU]
Status in Upstart:
Fix Released
Status in “upstart” package in Ubuntu:
New
Status in “upstart” source package in Trusty:
New
Bug description:
= PROBLEM =
The version of Upstart currently in trusty (1.12.1-0ubuntu4.2) suffers
from a couple of problems which in combination could make upgrading
difficult on systems with high uptimes.
The 2 issues are:
== bug 901038 ==
The issue here is that telinit in trusty is not fully synchronous. This
is not normally a problem. However if Upstart is re-exec'ed using
'telinit u', as is done by the maintainer scripts for the following
packages...
- libc6
- libdbus-1-3
- libjson-c2
- libnih1
- libnih-dbus1
- libselinux1
- libsepol1
- upstart
... and if that operation is slow (it is normally extremely fast),
subsequent package upgrades (part of the same apt-get run) which *also*
need to restart Upstart may fail since 'telinit u' is unable to connect
to PID 1 as a result of Upstart still being in the process of
re-exec'ing from the last call to 'telinit u'.
== bug 1338637 ==
This bug only really affects server systems which have high uptimes. If
a re-exec is triggered via 'telinit u' as part of a package upgrade (see
above), Upstart will consume 2 additional inotify watches. Although this
doesn't affect the correct behaviour of Upstart, it does have two
repercussions:
a) It wastes inotify watches.
b) It slows down an Upstart re-exec ('telinit u').
Note that the slow-down for a vanilla Trusty server may not be
detectable unless the value of /proc/sys/fs/inotify/max_user_instances
has been raised above the default value of 128.
= FIX DETAILS =
== bug 901038 ==
The fix for this bug now makes 'telinit u' block until the re-exec
operation has completed fully.
Technically, it is not possible to make 'telinit u' synchronous since
because D-Bus connections cannot be serialised and since the 'telinit u'
request is made via a D-Bus connection, when Upstart re-exec's, it has
to sever all D-Bus connections, including the 'telinit u' D-Bus
connection. As such, 'telinit u' now performs the following operations:
- Requests synchronously that Upstart re-exec itself.
- Polls Upstart "forever" by attempting to connect to PID 1 and if
that operation fails, waiting for a period, the retrying.
The code is well commented to explain this less-than-ideal but
nonetheless essential poll operation:
http://bazaar.launchpad.net/~upstart-
devel/upstart/trunk/view/head:/util/telinit.c#L171
== bug 1338637 ==
This was a simple bug fix.
= FIX AVAILABILITY =
TBD.
= IMPACT =
On a high uptime server, the more times that 'telinit u' is called (as
the result of normal apt-get updates to any of the packages listed under
bug 901038 above), the slower the operation will take to complete, and
thus the likelihood of bug 901038 being seen will increase.
= JUSTIFICATION =
System updates need to "just work". However, as outlined above, the
longer a systems uptime, the more likely it is to be affected by this
issue which increases the likelihood of a system update failure.
This issue needs to be fixed as soon as possible to minimise issues for
trusty users and administrators, particularly before any potential
upgrade to Utopic.
= TEST CASE =
== To demonstrate bug 1338637 ==
$ sudo telinit u
$ sudo ls -l /proc/1/fd|grep inotify|wc -l
The correct output from the above 2 commands should be simply "2".
However, on trusty systems, if the commands above are run after a fresh
boot, the value will in all likelihood be "4". Also, every subsequent
'telinit u' will increase the number displayed by 2.
== To demonstrate bug 901038 ==
for i in $(seq 10); do telinit u; done
There should be no output from the command-line above, but on a trusty
system the chances are that one or more lines will display like this:
$ for i in $(seq 5); do sudo telinit u;done
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused
== To prove the overall problem has been fixed ==
1) Download the attached "force-reexec.sh" onto a trusty system.
2) Make executable:
$ chmod 755 ./force-reexec.sh
3) Run script as root, specifying a number of iterations (100) and
saving output to file "./typescript.bad":
$ script -c 'sudo ./force-reexec.sh 100' typescript.bad
4) Upgrade to latest version of
[Touch-packages] [Bug 1371469] Re: system hangs on shutdown/reboot
A few questions: 1) Has this problem always been present for you since upgrading both systems to utopic? 2) Do you have any other systems running utopic that do not manifest the issue? 3) How are you shutting the systems down? Via the Unity menu or via the command line. 4) When you say that the problem doesn't happen immediately after boot do you mean that shutdown is always reliable if the system has just booted? -- 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/1371469 Title: system hangs on shutdown/reboot Status in “upstart” package in Ubuntu: New Bug description: On two machines running Utopic Desktop, the system hangs on shutd own/reboot. It doesn't happen immediately after the boot but after using the machine for a while. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 .etc.init.bluetooth.override: manual .etc.init.mountall.override: console output ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 19 10:01:29 2014 InstallationDate: Installed on 2013-09-03 (380 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-16-generic.efi.signed root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 --debug SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.apport.crashdb.conf: [modified] modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission non accordée: '/etc/at.deny'] modified.conffile..etc.bumblebee.xorg.conf.nouveau: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission non accordée: '/etc/libvirt/qemu.conf'] mtime.conffile..etc.apport.crashdb.conf: 2014-05-16T10:52:39.045793 mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2014-05-07T08:52:59.54 mtime.conffile..etc.default.cups: 2014-03-12T09:14:04.955541 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1371469/+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
