[Bug 1498954] Re: Chromium shows 'aw ! snap' on every page after updating the system
Yes. I can confirm I don't have the issue anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] Re: Chromium shows 'aw ! snap' on every page after updating the system
Ok, perhaps. But the bug 1382929 was reported one year ago and is still unassigned. What can I do to help fixing the issue ? I have all my tools based on chromium-browser/google-chrome and I am stuck at this point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] Re: Chromium shows 'aw ! snap' on every page after updating the system
More infos: apt-cache policy chromium-browser chromium-browser: Installed: 45.0.2454.85-0ubuntu0.14.04.1.1097 Candidate: 45.0.2454.85-0ubuntu0.14.04.1.1097 Version table: *** 45.0.2454.85-0ubuntu0.14.04.1.1097 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/universe i386 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe i386 Packages 100 /var/lib/dpkg/status 34.0.1847.116-0ubuntu2 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages uname -a: Linux mai 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14 21:43:30 UTC 2015 i686 i686 i686 GNU/Linux cat /etc/lsb-release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.3 LTS" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] [NEW] Chromium shows 'aw ! snap' on every page after updating the system
Public bug reported: Hi, when launching chromium, every page shows 'aw ! snap' and all extensions crash (segfault). The dmesg shows: [ 5390.555398] chromium-browse[11974]: segfault at 410 ip 0410 sp ab7febc0 error 14 [ 6100.170017] chromium-browse[12308]: segfault at 410 ip 0410 sp a85febc0 error 14 [ 6100.365223] chromium-browse[12342]: segfault at 410 ip 0410 sp a85febc0 error 14 [ 6100.378622] chromium-browse[12248]: segfault at 410 ip 0410 sp bfff4a00 error 14 [ 6100.396981] chromium-browse[12364]: segfault at 410 ip 0410 sp a87f5bc0 error 14 [ 6100.417267] chromium-browse[12376]: segfault at 410 ip 0410 sp a85febc0 error 14 [ 6100.482647] chromium-browse[12381]: segfault at 410 ip 0410 sp a87f5bc0 error 14 [ 6100.575302] chromium-browse[12389]: segfault at 410 ip 0410 sp a85febc0 error 14 [ 6100.606053] chromium-browse[12394]: segfault at 410 ip 0410 sp a87f5bc0 error 14 [ 6100.626080] chromium-browse[12399]: segfault at 410 ip 0410 sp a85febc0 error 14 That wasn't happening before the update I did for the system. If I launch the browser from the command line I have the error: [12517:12517:0923/074300:ERROR:nss_util.cc(845)] After loading Root Certs, loaded==false: NSS error code: -8018 And finally if launch the browser with the option: "--disable-seccomp-filter-sandbox", it does not show up the error and the extensions still work. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472669/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] gconf-keys.txt
apport information ** Attachment added: "gconf-keys.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472673/+files/gconf-keys.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] modified.conffile..etc.chromium.browser.default.txt
apport information ** Attachment added: "modified.conffile..etc.chromium.browser.default.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472674/+files/modified.conffile..etc.chromium.browser.default.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] etcconfigc00example.txt
apport information ** Attachment added: "etcconfigc00example.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472671/+files/etcconfigc00example.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472664/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] Re: Chromium shows 'aw ! snap' on every page after updating the system
apport information ** Tags added: apport-collected trusty ** Description changed: Hi, when launching chromium, every page shows 'aw ! snap' and all extensions crash (segfault). The dmesg shows: [ 5390.555398] chromium-browse[11974]: segfault at 410 ip 0410 sp ab7febc0 error 14 [ 6100.170017] chromium-browse[12308]: segfault at 410 ip 0410 sp a85febc0 error 14 [ 6100.365223] chromium-browse[12342]: segfault at 410 ip 0410 sp a85febc0 error 14 [ 6100.378622] chromium-browse[12248]: segfault at 410 ip 0410 sp bfff4a00 error 14 [ 6100.396981] chromium-browse[12364]: segfault at 410 ip 0410 sp a87f5bc0 error 14 [ 6100.417267] chromium-browse[12376]: segfault at 410 ip 0410 sp a85febc0 error 14 [ 6100.482647] chromium-browse[12381]: segfault at 410 ip 0410 sp a87f5bc0 error 14 [ 6100.575302] chromium-browse[12389]: segfault at 410 ip 0410 sp a85febc0 error 14 [ 6100.606053] chromium-browse[12394]: segfault at 410 ip 0410 sp a87f5bc0 error 14 [ 6100.626080] chromium-browse[12399]: segfault at 410 ip 0410 sp a85febc0 error 14 That wasn't happening before the update I did for the system. If I launch the browser from the command line I have the error: [12517:12517:0923/074300:ERROR:nss_util.cc(845)] After loading Root Certs, loaded==false: NSS error code: -8018 And finally if launch the browser with the option: "--disable-seccomp-filter-sandbox", it does not show up the error and the extensions still work. + --- + ApportVersion: 2.14.1-0ubuntu3.13 + Architecture: i386 + CurrentDesktop: GNOME + DRM.card0.DP.1: + edid-base64: + dpms: On + modes: + enabled: disabled + status: disconnected + DRM.card0.DP.2: + edid-base64: + dpms: On + modes: + enabled: disabled + status: disconnected + DRM.card0.DP.3: + edid-base64: + dpms: On + modes: + enabled: disabled + status: disconnected + DRM.card0.HDMI.A.1: + edid-base64: + dpms: On + modes: + enabled: disabled + status: disconnected + DRM.card0.HDMI.A.2: + edid-base64: + dpms: On + modes: + enabled: disabled + status: disconnected + DRM.card0.HDMI.A.3: + edid-base64: + dpms: On + modes: + enabled: disabled + status: disconnected + DRM.card0.LVDS.1: + edid-base64: AP///wAw5NgCAAAWAQOAHBB46ohVmVtVjyYdUFQBAQEBAQEBAQEBAQEBAQEBYB1W2FAAGDAwQEcAFZwQAAAb/gBMRyBEaXNwbGF5CiAg/gBMUDEyNVdIMi1TTEIzAFk= + dpms: On + modes: 1366x768 + enabled: enabled + status: connected + DRM.card0.VGA.1: + edid-base64: + dpms: On + modes: + enabled: disabled + status: disconnected + Desktop-Session: + 'gnome' + '/etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg' + '/usr/share/gnome:/usr/local/share/:/usr/share/' + DistroRelease: Ubuntu 14.04 + Env: + 'None' + 'None' + InstallationDate: Installed on 2011-09-21 (1463 days ago) + InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) + Load-Avg-1min: 0.43 + Load-Processes-Running-Percent: 0.2% + MachineType: LENOVO 2320CTO + Package: chromium-browser 45.0.2454.85-0ubuntu0.14.04.1.1097 + PackageArchitecture: i386 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=f346f673-b608-4b88-ade5-a79f92defddb ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 + Tags: trusty + Uname: Linux 3.13.0-63-generic i686 + UpgradeStatus: Upgraded to trusty on 2014-08-14 (405 days ago) + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers + _MarkForUpload: True + dmi.bios.date: 01/14/2013 + dmi.bios.vendor: LENOVO + dmi.bios.version: G2ET91WW (2.51 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 2320CTO + dmi.board.vendor: LENOVO + dmi.board.version: Win8 Pro DPK TPG + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvrG2ET91WW(2.51):bd01/14/2013:svnLENOVO:pn2320CTO:pvrThinkPadX230:rvnLENOVO:rn2320CTO:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.name: 2320CTO + dmi.product.version: ThinkPad X230 + dmi.sys.vendor: LENOVO + modified.conffile..etc.default.chromium.browser: [deleted] + mtime.conffile..etc.chromium.browser.default: 2014-09-03T08:23:02.021302 ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472653/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] ChromiumPrefs.txt
apport information ** Attachment added: "ChromiumPrefs.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472654/+files/ChromiumPrefs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] DiskUsage.txt
apport information ** Attachment added: "DiskUsage.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472659/+files/DiskUsage.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472663/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472661/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472665/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472666/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] RelatedPackagesPolicy.txt
apport information ** Attachment added: "RelatedPackagesPolicy.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472668/+files/RelatedPackagesPolicy.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472670/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] etcconfigc10flash.txt
apport information ** Attachment added: "etcconfigc10flash.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472672/+files/etcconfigc10flash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] RelatedPackageVersions.txt
apport information ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472667/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] InstalledPlugins.txt
apport information ** Attachment added: "InstalledPlugins.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472660/+files/InstalledPlugins.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472655/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472662/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472657/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498954] DetectedPlugins.txt
apport information ** Attachment added: "DetectedPlugins.txt" https://bugs.launchpad.net/bugs/1498954/+attachment/4472658/+files/DetectedPlugins.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498954 Title: Chromium shows 'aw ! snap' on every page after updating the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1498954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242812] Re: ext4 random block I/O write performance regression with 3.11 Saucy Kernel
Is this fix also present in 'trusty' ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242812 Title: ext4 random block I/O write performance regression with 3.11 Saucy Kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Blueprint servercloud-r-lxc] LXC work for R
Blueprint changed by Daniel Lezcano:
Work items changed:
Work items:
[stgraber] Look into shipping logind with cgroup support by defaut: TODO
[serge-hallyn] put utah testcases in upstream tests/ubuntu: POSTPONED
[zulcss] start a libvirt driver for upstream lxc: POSTPONED
[serge-hallyn] Send user namespace delta to kernel-team ASAP: DONE
[serge-hallyn] Post syslog namespace design wiki page: DONE
[serge-hallyn] Send syslog namespace prototype to lkml: DONE
[serge-hallyn] Send syslog namespace description to kernel-team ASAP: DONE
[serge-hallyn] Add set_cgroup_item() and get_cgroup_item() to C API: DONE
- [daniel-lezcano] Improved monitor notification support: TODO
+ [daniel-lezcano] Improved monitor notification support: POSTPONED
[stgraber] Fix lxc-ls (re-write using api): DONE
[serge-hallyn] lxc-create or template option to specify userns mapping:
POSTPONED
[serge-hallyn] push user namespace lxc delta upstream: DONE
[serge-hallyn] add config options for loglevel and output file: DONE
[serge-hallyn] drop lxccontainer.log default logging in api: DONE
[serge-hallyn] lxc-create - set a default log file in
/var/log/lxc/$container: DONE
[serge-hallyn] lxc.autodev: push lxc patch upstream: DONE
[serge-hallyn] lxc.autodev: push lxc patch into package: DONE
[serge-hallyn] lxc.autodev: push mountall patch into package: DONE
[serge-hallyn] list broken functionality in ubuntu container in user
namespace: POSTPONED
[serge-hallyn] improve ubuntu container experience in user namespace:
POSTPONED
[serge-hallyn] add config option for RLIMIT_NPROC in userns container:
POSTPONED
[stgraber] add (not container) to upstart jobs which just fail: DONE
[stgraber] write tool to pass devices into container: DONE
[stgraber] create a separate package for templates: DONE
[stgraber] have lxc-create record the name of template used in container
config file for debugging: DONE
[stgraber] support templates outside of $templatedir (pushed to git): DONE
[stgraber] investigate what's needed to support containers outside of
/var/lib/lxc (part of the scheduled API work): DONE
[serge-hallyn] test apparmor profile stacking; implement any lxc changes
needed to support it: BLOCKED
[stgraber] rebase staging branch on upstream master: DONE
[serge-hallyn] test attach support in userns kernel; shout if anything
missing: DONE
- [daniel-lezcano] investigate/use http://lxc.sourceforge.net/download/procfs
to filter /proc/{cpuinfo,meminfo,etc}: TODO
+ [daniel-lezcano] investigate/use http://lxc.sourceforge.net/download/procfs
to filter /proc/{cpuinfo,meminfo,etc}: POSTPONED
[stgraber] investigate: does dnsmasq save mac-ip across host reboots? (it
does): DONE
[stgraber] Port arkose to python3 (and make it pep8 clean): DONE
[stgraber] Port arkose to python3-lxc: BLOCKED
[stgraber] Port auto-dist-upgrader to python3-lxc: DONE
[stgraber] Tweak the tests to ensure auto-dist-upgrader on LXC gives the same
results as on kvm: DONE
[stgraber] Check what it'd take to make lxc work fine when
creating/starting/stopping containers in parallel (improved locking of
templates): DONE
[stgraber] Add code to detect and install langpacks in containers (at least
-base-en): DONE
[stgraber] Get LXC into main: INPROGRESS
[ebiederm] Push current userns patchset upstream: DONE
[ebiederm] Add support for tmpfs mounts in userns: POSTPONED
--
LXC work for R
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-lxc
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 986956] Re: lxc-execute does not work with commands that require input from terminal
The lxc-execute command is used for 'application container'. Usually, the system container uses a rootfs and the application container do not use a rootfs. So lxc is looking for if the rootfs option is set and then setup the console. Here lxc-execute is used with the rootfs, so it setup the console, that is to say it maps /dev/console to /dev/tty. Of course, that makes sense only if we have the applications writing to /dev/console which is the case when the system containers boot. Doing that with a shell is messy and we have problem with the tty. = Why is needed a rootfs with lxc-execute ? There are 2 solutions to fix this problem: (1) do not specify the rootfs but ro-bind-mount the rootfs/usr to /usr and the other needed directories. (2) change the code to have lxc-execute to take into account a rootfs but I wouldn't recommend that because that will bring much more complexity and more errors with the console by adding a new configuration combination. At least we should decide to ignore the rootfs option when lxc-execute is used. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/986956 Title: lxc-execute does not work with commands that require input from terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/986956/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 986956] Re: lxc-execute does not work with commands that require input from terminal
The lxc-execute command is used for 'application container'. Usually, the system container uses a rootfs and the application container do not use a rootfs. So lxc is looking for if the rootfs option is set and then setup the console. Here lxc-execute is used with the rootfs, so it setup the console, that is to say it maps /dev/console to /dev/tty. Of course, that makes sense only if we have the applications writing to /dev/console which is the case when the system containers boot. Doing that with a shell is messy and we have problem with the tty. = Why is needed a rootfs with lxc-execute ? There are 2 solutions to fix this problem: (1) do not specify the rootfs but ro-bind-mount the rootfs/usr to /usr and the other needed directories. (2) change the code to have lxc-execute to take into account a rootfs but I wouldn't recommend that because that will bring much more complexity and more errors with the console by adding a new configuration combination. At least we should decide to ignore the rootfs option when lxc-execute is used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986956 Title: lxc-execute does not work with commands that require input from terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/986956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Blueprint servercloud-p-lxc] LXC development for Precise
Blueprint changed by Daniel Lezcano: Whiteboard changed: Status: Started NOTE: (jdstrand) jjohansen's work items are being tracked as part ot security-p-apparmor-containers and I added a dependency of this bp to that one Work Items: [serge-hallyn] LXC init script to create default bridge if enabled in /etc/default/lxc: DONE - [daniel-lezcano] Get patchset accepted into kernel so kernel can send reboot signal to container : INPROGRESS + [daniel-lezcano] Get patchset accepted into kernel so kernel can send reboot signal to container : DONE [serge-hallyn] Change userspace lxc to not need to watch utmp for reboot: DONE [serge-hallyn] queue ubuntu package delta for upstream on github: DONE [stgraber] Make sure we can build in a working LXC container for arm on x86 (need new apt): DONE [stgraber] Allow mknod in the default Ubuntu template for precise: DONE [stgraber] modprobe should not work in a container ( check libvirt ): DONE [smoser] open bug for libvirt to check capsys-module, capmac*: TODO [stgraber] make mountall not mount certain things when inside a container: DONE [stgraber] Move lxc-is-container (as generic is-container) into upstart: DONE [stgraber] Move lxc consoles into upstart: DONE [serge-hallyn] Add apparmor profile: DONE [serge-hallyn] When mount controls are in kernel, use them in apparmor profile: TODO [serge-hallyn] Add lxc section to the Ubuntu Server Guide: INPROGRESS [serge-hallyn] Update simple templates to work: INPROGRESS [serge-hallyn] Update fedora template to work: TODO [serge-hallyn] Update opensuse template to work: TODO [serge-hallyn] Update lxc-create manpage: TODO [serge-hallyn] Keep pushing on the patchset for userns vfs patches: POSTPONED Questions/Comments: Would we be able to get some documentation of what we can expect (and not expect) from a security aspect this cycle soon? -- Daviey See wiki.ubuntu.com/LxcSecurity. Please let me know if more is needed. Thanks. -- LXC development for Precise https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-lxc -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-p-lxc] LXC development for Precise
Blueprint changed by Daniel Lezcano: Whiteboard changed: Status: Started NOTE: (jdstrand) jjohansen's work items are being tracked as part ot security-p-apparmor-containers and I added a dependency of this bp to that one Work Items: [serge-hallyn] LXC init script to create default bridge if enabled in /etc/default/lxc: DONE - [daniel-lezcano] Get patchset accepted into kernel so kernel can send reboot signal to lxc monitor: TODO + [daniel-lezcano] Get patchset accepted into kernel so kernel can send reboot signal to container : INPROGRESS [daniel-lezcano] Change upstream lxc to not need to watch utmp for reboot: TODO [serge-hallyn] queue ubuntu package delta for upstream on github: INPROGRESS [serge-hallyn] Keep pushing on the patchset for userns vfs patches: TODO [stgraber] Make sure we can build in a working LXC container for arm on x86 (need new apt): BLOCKED [stgraber] Allow mknod in the default Ubuntu template for precise: DONE [stgraber] modprobe should not work in a container ( check libvirt ): DONE [smoser] open bug for libvirt to check capsys-module, capmac*: TODO [stgraber] make mountall not mount certain things when inside a container: DONE Move lxc-is-container (as generic is-container) into upstart: TODO Move lxc consoles into upstart: TODO Questions/Comments: Would we be able to get some documentation of what we can expect (and not expect) from a security aspect this cycle soon? -- Daviey See wiki.ubuntu.com/LxcSecurity. Please let me know if more is needed. Thanks. -- LXC development for Precise https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-lxc -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-lxc-improvements] LXC improvements
Blueprint changed by Daniel Lezcano: Whiteboard changed: Status: not yet started Work Items: validate LXC support on ARM: DONE [zul] List of missing bits pieces of libvirt for lxc (libvirt 0.9.1-1 merge is pending): TODO [zul] Badger someone into writing libvirt-lxc bridge: TODO [serge-hallyn] quick container cloning with snapshotting using LVM: TODO [serge-hallyn] quick container cloning with snapshotting using overlayfs: TODO - [daniel-lezcano] push core proc virtualization support upstream: TODO - [daniel-lezcano] push kernel patches supporting shutdown/reboot: TODO - [daniel-lezcano] exploit container shutdown/reboot kernel support in lxc: TODO - [daniel-lezcano] push lxc-attach when kernel patches are upstream: TODO + [bootstrap31] push core proc virtualization support upstream: TODO + [bootstrap31] push kernel patches supporting shutdown/reboot: TODO + [bootstrap31] exploit container shutdown/reboot kernel support in lxc: TODO + [bootstrap31] push lxc-attach when kernel patches are upstream: TODO udev and device namespaces: TODO design libcgroup integration: TODO per container syslog: TODO custom per-container firewall rules: TODO lsm integration: TODO templates for other distros (fedora, opensles, gentoo): TODO re-invigorate application checkpoint/restart: TODO improve lxc-ps, lxc-netstat: TODO event notification: TODO -- LXC improvements https://blueprints.launchpad.net/ubuntu/+spec/server-o-lxc-improvements -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 629258] Re: Battery life estimation never comes around
I know it is a maverick bug but it is working for lucid. Running lucid with a kernel version: Linux mai 2.6.35-02063505-generic #201009211107 SMP Tue Sep 21 11:09:35 UTC 2010 x86_64 GNU/Linux ** Attachment added: dmi.txt https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/629258/+attachment/1712266/+files/dmi.txt -- Battery life estimation never comes around https://bugs.launchpad.net/bugs/629258 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 654552] Re: Unable to start LXC Container
On 10/08/2010 12:56 AM, Royston Carter wrote: Daniel, Firstly is it likely that this will come out shortly as a patch to Lucid? If so and in a matter of days rather than weeks then I will wait. The patch in attachment is a fix for this problem. If the package maintainer is willing to merge it that will be great. Alternatively could you point me at documentation that would explain how I apply the fix from the git repository you allude to in you email. The simpler is: * install the quilt tools * save the patch in attachment * cd lxc-topmost-dir * quilt import path-to-patch/0001-use-lazy-... * quilt push Then the usual configure, make, etc ... Let me know if that fixes your problem Thanks -- Daniel ** Patch added: 0001-use-lazy-umount-when-umount-returns-EBUSY.patch https://bugs.launchpad.net/bugs/654552/+attachment/1678598/+files/0001-use-lazy-umount-when-umount-returns-EBUSY.patch -- Unable to start LXC Container https://bugs.launchpad.net/bugs/654552 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 654552] Re: Unable to start LXC Container
On 10/08/2010 12:44 PM, Royston Carter wrote: Daniel, Can we step back a little here please. I have never to date amended or patched a Linux component/application so could do with your second step explaining. You say * cdlxc-topmost-dir but does this assume I have lxc source installed? If this is required could you add a line for how I get this. Thanks for you response to this. Sure, but let's switch to a private mail exchange, as that will be out of the scope of this bug. I will use your contact user in launchpad. -- Daniel -- Unable to start LXC Container https://bugs.launchpad.net/bugs/654552 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 654552] Re: Unable to start LXC Container
This bug was fixed in the next release of lxc. The commit fixing this problem is: http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commit;h=c08556c6ece8ad8308f7636adb0ad25b60e3a16d Does it makes sense to take the lxc-0.7.2 version for lucid ? As it is compatible for the kernel ? -- Unable to start LXC Container https://bugs.launchpad.net/bugs/654552 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 646694] [NEW] autofs does not stop when the system is halted
Public bug reported: Binary package hint: autofs Ubuntu version: Description:Ubuntu 10.04 LTS Release:10.04 Package version: Architecture: amd64 Source: autofs5 Version: 5.0.4-3.1ubuntu5 Depends: autofs5 When the system halts, a signal is delivered to all the processes but automount does not receive it. The sendsigs init script will build a list of processes to be omitted when sending a signal. The omitted processes are the one not killed by the upstart jobs and the ones defined in the /lib/init/rw/sendsigs.omit.d/, /var/run/sendsigs.omit. automount is not killed by upstart because the 'stop' action is not defined in /etc/init/autofs.conf, then it will belongs to the omitted processes list and therefore won't be killed. In the normal use case, this is not visible because the shutdown will happens normally. In the container context (lxc.sourceforge.net), it appears there are some remaining processes while the system is halted. IMO, this is not the right behavior, the automount should receive a SIGTERM at shutdown time, this signal is catched and the daemon will do a proper shutdown. I was wondering if the autofs.conf script shouldn't have: stop on runlevel [!2345] Then the upstart job will deliver the sigterm signal to the process, and the automount will do its shutdown job normally. It is cleaner for the system, and make it works for the container. ** Affects: autofs (Ubuntu) Importance: Undecided Status: New -- autofs does not stop when the system is halted https://bugs.launchpad.net/bugs/646694 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 646694] [NEW] autofs does not stop when the system is halted
Public bug reported: Binary package hint: autofs Ubuntu version: Description:Ubuntu 10.04 LTS Release:10.04 Package version: Architecture: amd64 Source: autofs5 Version: 5.0.4-3.1ubuntu5 Depends: autofs5 When the system halts, a signal is delivered to all the processes but automount does not receive it. The sendsigs init script will build a list of processes to be omitted when sending a signal. The omitted processes are the one not killed by the upstart jobs and the ones defined in the /lib/init/rw/sendsigs.omit.d/, /var/run/sendsigs.omit. automount is not killed by upstart because the 'stop' action is not defined in /etc/init/autofs.conf, then it will belongs to the omitted processes list and therefore won't be killed. In the normal use case, this is not visible because the shutdown will happens normally. In the container context (lxc.sourceforge.net), it appears there are some remaining processes while the system is halted. IMO, this is not the right behavior, the automount should receive a SIGTERM at shutdown time, this signal is catched and the daemon will do a proper shutdown. I was wondering if the autofs.conf script shouldn't have: stop on runlevel [!2345] Then the upstart job will deliver the sigterm signal to the process, and the automount will do its shutdown job normally. It is cleaner for the system, and make it works for the container. ** Affects: autofs (Ubuntu) Importance: Undecided Status: New -- autofs does not stop when the system is halted https://bugs.launchpad.net/bugs/646694 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 646850] [NEW] useless mount of /proc and /sys with init upstart ?
Public bug reported: Binary package hint: mountall I noticed mountall does specify /proc and /sys to be mounted in the fstab by default. I noticed the upstart init process mounts /proc and /sys internally. If mountall is used with the init upstart, is it worth to get rid of these mount points by default ? It is not critical, but that saves a little processing time when booting. ** Affects: mountall (Ubuntu) Importance: Undecided Status: New -- useless mount of /proc and /sys with init upstart ? https://bugs.launchpad.net/bugs/646850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585092] Re: giant IO delays
I tested the v4 and it works perfectly. While the 2.6.32-23-generic was taking more than 12 seconds to accomplish an umount loop, the v4 takes less than 100ms. Great ! Thanks. -- giant IO delays https://bugs.launchpad.net/bugs/585092 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585092] Re: giant IO delays
Please read 2.6.32-22-generic in comment #34. -- giant IO delays https://bugs.launchpad.net/bugs/585092 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
