[Bug 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
This is still affecting users of the 1.4+bzr1693+dfsg-0ubuntu2 pacakge in Saucy. Steps to reproduce: - Install maas using the saucy server install CD. - Edit /etc/maas/import_pxe_files - set ARCHES to i.e. ARCHES=amd64/generic - Configure the rest of MaaS, click the import boot images in the UI - PXE boot a machine What happens: The machine PXE boots, gets assigned an IP address by MaaS. The node gets stuck on Trying to load: pxelinux.cfg/default and finally reboots after a timeout triggers. This results in an eternal reboot loop. What should be happening: The machine PXE boots, gets assigned an IP address, and successfully downloads a bootable image from tftp, resuming normal operations. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
Further information: Relevant stacktrace: https://pastebin.canonical.com/99705/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
Sorry, I used a private pastebin, here's the public equivalent: http://pastebin.ubuntu.com/6340916/ @rvb: Yeah that looks like what I'm seeing indeed. I'll give it a try and report back! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
@rvb: Yes, adding back the i386 architecture made the boot up work. I'll subscribe to bug 1181334 instead! Thanks for your help. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1181334] Re: i386 required to install amd64
Can confirm, it would save us (the landscape team, but also other users I wager) a lot of time and disk space if we could only download amd64 images and use that successfully. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1181334 Title: i386 required to install amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1181334/+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 1247886] Re: squid-deb-proxy is not started when installing MaaS with 13.10 server CD
Yes, I should have attached that log file in my initial report. It's the same problem :( -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1247886 Title: squid-deb-proxy is not started when installing MaaS with 13.10 server CD To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1247886/+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 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Changing back to juju-core since this affects me, and I'm not using LXC containers at all. ** Package changed: lxc (Ubuntu) = juju-core (Ubuntu) ** Tags added: landscape -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: Juju deploy of Charm in MAAS fails because dbus fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+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 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
I hit the same problem, and don't use LXC at all on my setup. I therefore will change this bug to point back to juju-core. My MaaS lives in a KVM machine on my laptop. It can PXE boot/start-stop other KVM machines living on the same NAT'ed network. - juju bootstrap --upload-tools works (the node is spun up, and after the ubuntu install, juju status works). - I can juju deploy any charm, however: - The machines come up (the node boots, ubuntu gets installed), but juju status reports pending forever. The machine that is brought up has the same symptoms as reported above: The machine log in /var/log/juju show: 2013-11-05 18:39:02 ERROR juju runner.go:211 worker: exited deployer: exec [start --system jujud-unit-rabbitmq-server-0]: exit status 1 (start: Unable to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory) Running this command by hand works when run without --system. Once ran, /var/log/juju contains a unit log as: http://pastebin.ubuntu.com/6371502/ The cloud-init log and cloud-init-output log are: http://pastebin.ubuntu.com/6371297/ http://pastebin.ubuntu.com/6371310/ I further tried to fix the situation manually by symlinking /var/lib/juju/tools/1.16.2.1-saucy-amd64/ to /var/lib/juju/tools /unit-mysql-0, but to no avail. -- 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/1248283 Title: Juju deploy of Charm in MAAS fails because dbus fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+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 1247886] Re: squid-deb-proxy is not started when installing MaaS with 13.10 server CD
For the record, this affects the precise package as well. I would strongly recommend uploading a fixed package to the cloud-archive:tools repository since most people installing maas will use this (it's the recommended way). tribaal@maas:~$ apt-cache policy squid-deb-proxy squid-deb-proxy: Installed: 0.6.3.1 Candidate: 0.6.3.1 Version table: *** 0.6.3.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.3 0 500 http://ch.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages tribaal@maas:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.3 LTS Release:12.04 Codename: precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1247886 Title: squid-deb-proxy is not started when installing MaaS with 13.10 server CD To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1247886/+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 1303617] Re: Latest curtin version prevents Juju from bootstrapping on MAAS
** Also affects: curtin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1303617 Title: Latest curtin version prevents Juju from bootstrapping on MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1303617/+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 1303617] Re: Latest curtin version prevents Juju from bootstrapping on MAAS
** Description changed: Curtin version: 0.1.0~bzr124-0ubuntu1 Curtin-common: 0.1.0~bzr124-0ubuntu1 Bootstrapping a juju environment on an up-to-date trusty MAAS server fails. The bootstrap node becomes pingable but never allows connections to the juju agent. Cloud init output (shows error): http://pastebin.ubuntu.com/7215883/ Cloud init log: http://pastebin.ubuntu.com/7215881/ - Reverting python-curtin and curtin-common to 0.1.0~bzr121-0ubuntu1 works - around the problem. + Reverting python-curtin and curtin-common to 0.1.0~bzr121-0ubuntu1 does + not show the problem anymore. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1303617 Title: Latest curtin version prevents Juju from bootstrapping on MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1303617/+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 1303903] Re: sgdisk zap/clear doesn't wipe all GPT tables
** Tags added: landscape -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gdisk in Ubuntu. https://bugs.launchpad.net/bugs/1303903 Title: sgdisk zap/clear doesn't wipe all GPT tables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdisk/+bug/1303903/+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 1320587] Re: Intermittent 403 Issues
The linked branch should help with the problem, at the cost of an extra round-trip to the upstream archive. ** Branch linked: lp:~tribaal/squid-deb-proxy/refresh-ims -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1320587 Title: Intermittent 403 Issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1320587/+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 889656] Re: installer stops using proxy
This is fixed since the python code (instead of bash) behaves properly now. Closing this bug (it's old, bug triage has taken a lot of dust). Feel free to reopen should this sting you again. ** Changed in: squid-deb-proxy (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/889656 Title: installer stops using proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/889656/+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 1166667] Re: The default configuration is missing the /etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl file
This should be fixed in the next version of squid-deb-proxy when it's released. ** Changed in: squid-deb-proxy (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/117 Title: The default configuration is missing the /etc/squid-deb- proxy/autogenerated/pkg-blacklist-regexp.acl file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/117/+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 872019] Re: pkcs15 profiles not packaged, pkcs15-init not functional
** Branch linked: lp:~tribaal/ubuntu/precise/opensc/fix-for-872019 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/872019 Title: pkcs15 profiles not packaged, pkcs15-init not functional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensc/+bug/872019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 872019] Re: pkcs15 profiles not packaged, pkcs15-init not functional
Ok so I put a branch up for review and assigned this to myself. I hope the process is correct... ** Changed in: opensc (Ubuntu) Status: Confirmed = In Progress ** Changed in: opensc (Ubuntu) Assignee: (unassigned) = Chris Glass (tribaal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/872019 Title: pkcs15 profiles not packaged, pkcs15-init not functional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensc/+bug/872019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303274] Re: landscape-sysinfo - lacks a man page or other documentation
Since I'm already doing a pass on the client I'll take the opportunity to fix this. I'll take the man page from Andreas's branch and make it a txt file (so that we can regenerate it with the same mechanism than other man pages). ** Branch linked: lp:~tribaal/landscape-client/landscape-sysinfo-man- page ** Changed in: landscape-client Assignee: Andreas Hasenack (ahasenack) = Chris Glass (tribaal) ** Changed in: landscape-client Status: Incomplete = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/303274 Title: landscape-sysinfo - lacks a man page or other documentation To manage notifications about this bug go to: https://bugs.launchpad.net/landscape/+bug/303274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303274] Re: landscape-sysinfo - lacks a man page or other documentation
** Changed in: landscape-client Status: In Progress = Fix Committed ** Changed in: landscape-client (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/303274 Title: landscape-sysinfo - lacks a man page or other documentation To manage notifications about this bug go to: https://bugs.launchpad.net/landscape/+bug/303274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247886] Re: squid-deb-proxy is not started when installing MaaS with 13.10 server CD
Yes, I should have attached that log file in my initial report. It's the same problem :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247886 Title: squid-deb-proxy is not started when installing MaaS with 13.10 server CD To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1247886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Changing back to juju-core since this affects me, and I'm not using LXC containers at all. ** Package changed: lxc (Ubuntu) = juju-core (Ubuntu) ** Tags added: landscape -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: Juju deploy of Charm in MAAS fails because dbus fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
I hit the same problem, and don't use LXC at all on my setup. I therefore will change this bug to point back to juju-core. My MaaS lives in a KVM machine on my laptop. It can PXE boot/start-stop other KVM machines living on the same NAT'ed network. - juju bootstrap --upload-tools works (the node is spun up, and after the ubuntu install, juju status works). - I can juju deploy any charm, however: - The machines come up (the node boots, ubuntu gets installed), but juju status reports pending forever. The machine that is brought up has the same symptoms as reported above: The machine log in /var/log/juju show: 2013-11-05 18:39:02 ERROR juju runner.go:211 worker: exited deployer: exec [start --system jujud-unit-rabbitmq-server-0]: exit status 1 (start: Unable to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory) Running this command by hand works when run without --system. Once ran, /var/log/juju contains a unit log as: http://pastebin.ubuntu.com/6371502/ The cloud-init log and cloud-init-output log are: http://pastebin.ubuntu.com/6371297/ http://pastebin.ubuntu.com/6371310/ I further tried to fix the situation manually by symlinking /var/lib/juju/tools/1.16.2.1-saucy-amd64/ to /var/lib/juju/tools /unit-mysql-0, but to no avail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: Juju deploy of Charm in MAAS fails because dbus fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
This is still affecting users of the 1.4+bzr1693+dfsg-0ubuntu2 pacakge in Saucy. Steps to reproduce: - Install maas using the saucy server install CD. - Edit /etc/maas/import_pxe_files - set ARCHES to i.e. ARCHES=amd64/generic - Configure the rest of MaaS, click the import boot images in the UI - PXE boot a machine What happens: The machine PXE boots, gets assigned an IP address by MaaS. The node gets stuck on Trying to load: pxelinux.cfg/default and finally reboots after a timeout triggers. This results in an eternal reboot loop. What should be happening: The machine PXE boots, gets assigned an IP address, and successfully downloads a bootable image from tftp, resuming normal operations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
Further information: Relevant stacktrace: https://pastebin.canonical.com/99705/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
Sorry, I used a private pastebin, here's the public equivalent: http://pastebin.ubuntu.com/6340916/ @rvb: Yeah that looks like what I'm seeing indeed. I'll give it a try and report back! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
@rvb: Yes, adding back the i386 architecture made the boot up work. I'll subscribe to bug 1181334 instead! Thanks for your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181334] Re: i386 required to install amd64
Can confirm, it would save us (the landscape team, but also other users I wager) a lot of time and disk space if we could only download amd64 images and use that successfully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181334 Title: i386 required to install amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1181334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247886] Re: squid-deb-proxy is not started when installing MaaS with 13.10 server CD
For the record, this affects the precise package as well. I would strongly recommend uploading a fixed package to the cloud-archive:tools repository since most people installing maas will use this (it's the recommended way). tribaal@maas:~$ apt-cache policy squid-deb-proxy squid-deb-proxy: Installed: 0.6.3.1 Candidate: 0.6.3.1 Version table: *** 0.6.3.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.3 0 500 http://ch.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages tribaal@maas:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.3 LTS Release:12.04 Codename: precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247886 Title: squid-deb-proxy is not started when installing MaaS with 13.10 server CD To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1247886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190510] Re: Update lucid, raring, quantal, precise to landscape-client 13.07.3
** Description changed: Landscape Client 13.07.3 has been released. We would like to get these changes into raring, quantal, precise and lucid. As far as released version of Ubuntu are concerned, the required pieces of information for the needed SRU follow (as laid out in the Procedure section of https://wiki.ubuntu.com/StableReleaseUpdates). === Statement explaining the impact === This release sports both bug-fixes and new features and we would like to make sure all of our supported customers (even those on raring, quantal, precise and lucid) have access to these improvements. The notable ones are: 1) New annotations exchange mechanism allows clients to send any key-value data to the landscape server (#1123932) - 2) Network devices now report their maximum theoretical speeds, and duplex status to landscape-server (#1126330, #1130130) + 2) Network devices now report their maximum theoretical speeds, and duplex status to landscape-server (#1126330, #1130733) 3) Landscape.client is now HA aware when HA is implemented using juju charms (#1122508) 4) The landscape client will now trigger a reboot if server sends a reboot-required message. (#1133005) - 5) Big AMP code cleanup and refactoring in order to improve testing, improve performance and ease future maintainability (#1165047, #1169102, #1170669, #1170669, #1170669, #1170669, #1170669, #1170669, #1170669, #1170669, #1170669) + 5) Big AMP code cleanup and refactoring in order to improve testing, improve performance and ease future maintainability (#1165047, #1169102, #1170669) 6) Added logic to detect cloned (virtual) computers (#1161856) 7) The landscape-client and landscape-common packages do not use or depend on dbus code anymore, and some legacy plugins using dbus were removed. (#1175553, #1180691) 8) The ceph manager plugin is now a monitor plugin and thus does not require root privileges anymore. (#1186973) Some packaging-only changes are as follows: 9) Removed legacy upgrader code from postinst since support for it was dropped. 10) French translation patches were removed since the changes were merged upstream. 11) The /etc/dbus-1/system.d/landscape.conf file was moved from the landscape-client package to the landscape-client-ui package. A Replaces rule was therefore added to the landscape-client-ui package. No Breaks rule was added since the -ui package requires the exact same version of the -client package, avoiding the case described in http://www.debian.org/doc/debian-policy/footnotes.html#f53 12) dependencies on Dbus and hal/udev (python-dbus and gudev) are dropped from the landscape-client and landscape-common packages, since the client code does not use dbus at all anymore. The landscape-client-ui package however still does. For more details see the aforementioned bugs (all mentioned in the debian/changelog of the proposed packages). === How the bug has been addressed === We have been following the development procedure laid out in https://wiki.ubuntu.com/LandscapeUpdates Furthermore, the testing procedure results can be seen in https://wiki.canonical.com/Landscape/ClientSRUTests/13.07.1?action=recallrev=27 === Patches === Debdiff patches against the currently released landscape version are attached to this bug report, by distribution. === Detailed instructions how to reproduce the bug === N/A === Discussion === All the source packages have been subject to the QA process detailed in the LandscapeUpdates document linked above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190510 Title: Update lucid, raring, quantal, precise to landscape-client 13.07.3 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1190510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190510] Re: Update lucid, raring, quantal, precise to landscape-client 13.07.3
The lucid debdiff ** Patch added: lucid_12.05-0ubuntu0_to_13.07.3-0ubuntu0.debdiff https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3879404/+files/lucid_12.05-0ubuntu0_to_13.07.3-0ubuntu0.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190510 Title: Update lucid, raring, quantal, precise to landscape-client 13.07.3 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1190510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190510] Re: Update lucid, raring, quantal, precise to landscape-client 13.07.3
The precise debdiff ** Patch removed: precise_12.05-0ubuntu1_to_13.07.3-0ubuntu0.debdiff https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3868474/+files/precise_12.05-0ubuntu1_to_13.07.3-0ubuntu0.debdiff ** Patch removed: quantal_12.05-0ubuntu2_to_13.07.3-0ubuntu0.debdiff https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3868477/+files/quantal_12.05-0ubuntu2_to_13.07.3-0ubuntu0.debdiff ** Patch removed: raring_12.12-0ubuntu3_to_13.07.3-0ubuntu0.debdiff https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3868478/+files/raring_12.12-0ubuntu3_to_13.07.3-0ubuntu0.debdiff ** Patch removed: lucid_12.05-0ubuntu0_to_13.07.3-0ubuntu0.debdiff https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3868874/+files/lucid_12.05-0ubuntu0_to_13.07.3-0ubuntu0.debdiff ** Patch added: precise_12.05-0ubuntu1_to_13.07.3-0ubuntu0.debdiff https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3879400/+files/precise_12.05-0ubuntu1_to_13.07.3-0ubuntu0.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190510 Title: Update lucid, raring, quantal, precise to landscape-client 13.07.3 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1190510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190510] Re: Update lucid, raring, quantal, precise to landscape-client 13.07.3
The quantal debdiff ** Patch added: quantal_12.05-0ubuntu2_to_13.07.3-0ubuntu0.debdiff https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3879401/+files/quantal_12.05-0ubuntu2_to_13.07.3-0ubuntu0.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190510 Title: Update lucid, raring, quantal, precise to landscape-client 13.07.3 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1190510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190510] Re: Update lucid, raring, quantal, precise to landscape-client 13.07.3
The raring debdiff ** Patch added: raring_12.12-0ubuntu3_to_13.07.3-0ubuntu0.debdiff https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3879403/+files/raring_12.12-0ubuntu3_to_13.07.3-0ubuntu0.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190510 Title: Update lucid, raring, quantal, precise to landscape-client 13.07.3 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1190510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190510] Re: Update raring, quantal, precise to landscape-client 13.07.3
The raring debdiff for 13.07.3 ** Patch added: raring_12.12-0ubuntu3_to_13.07.3-0ubuntu0.debdiff https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3868478/+files/raring_12.12-0ubuntu3_to_13.07.3-0ubuntu0.debdiff ** Also affects: landscape-client (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/1190510 Title: Update raring, quantal, precise to landscape-client 13.07.3 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1190510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190510] Re: Update lucid, raring, quantal, precise to landscape-client 13.07.3
The lucid debdiff for 13.07.3 ** Summary changed: - Update raring, quantal, precise to landscape-client 13.07.3 + Update lucid, raring, quantal, precise to landscape-client 13.07.3 ** Description changed: - Landscape Client 13.07.1 has been released. We would like to get these + Landscape Client 13.07.3 has been released. We would like to get these changes into raring, quantal, precise and lucid. As far as released version of Ubuntu are concerned, the required pieces of information for the needed SRU follow (as laid out in the Procedure section of https://wiki.ubuntu.com/StableReleaseUpdates). === Statement explaining the impact === This release sports both bug-fixes and new features and we would like to make sure all of our supported customers (even those on raring, quantal, precise and lucid) have access to these improvements. The notable ones are: 1) New annotations exchange mechanism allows clients to send any key-value data to the landscape server (#1123932) 2) Network devices now report their maximum theoretical speeds, and duplex status to landscape-server (#1126330, #1130130) 3) Landscape.client is now HA aware when HA is implemented using juju charms (#1122508) 4) The landscape client will now trigger a reboot if server sends a reboot-required message. (#1133005) 5) Big AMP code cleanup and refactoring in order to improve testing, improve performance and ease future maintainability (#1165047, #1169102, #1170669, #1170669, #1170669, #1170669, #1170669, #1170669, #1170669, #1170669, #1170669) 6) Added logic to detect cloned (virtual) computers (#1161856) 7) The landscape-client and landscape-common packages do not use or depend on dbus code anymore, and some legacy plugins using dbus were removed. (#1175553, #1180691) 8) The ceph manager plugin is now a monitor plugin and thus does not require root privileges anymore. (#1186973) Some packaging-only changes are as follows: 9) Removed legacy upgrader code from postinst since support for it was dropped. 10) French translation patches were removed since the changes were merged upstream. 11) The /etc/dbus-1/system.d/landscape.conf file was moved from the landscape-client package to the landscape-client-ui package. A Replaces rule was therefore added to the landscape-client-ui package. No Breaks rule was added since the -ui package requires the exact same version of the -client package, avoiding the case described in http://www.debian.org/doc/debian-policy/footnotes.html#f53 12) dependencies on Dbus and hal/udev (python-dbus and gudev) are dropped from the landscape-client and landscape-common packages, since the client code does not use dbus at all anymore. The landscape-client-ui package however still does. For more details see the aforementioned bugs (all mentioned in the debian/changelog of the proposed packages). === How the bug has been addressed === We have been following the development procedure laid out in https://wiki.ubuntu.com/LandscapeUpdates Furthermore, the testing procedure results can be seen in https://wiki.canonical.com/Landscape/ClientSRUTests/13.07.1?action=recallrev=27 === Patches === Debdiff patches against the currently released landscape version are attached to this bug report, by distribution. === Detailed instructions how to reproduce the bug === N/A === Discussion === All the source packages have been subject to the QA process detailed in the LandscapeUpdates document linked above. ** Patch added: lucid_12.05-0ubuntu0_to_13.07.3-0ubuntu0.debdiff https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1190510/+attachment/3868874/+files/lucid_12.05-0ubuntu0_to_13.07.3-0ubuntu0.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190510 Title: Update lucid, raring, quantal, precise to landscape-client 13.07.3 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1190510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1110645] Re: lightdm-session fails with x-session-manager: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_registry_interface
As said in the title, running sudo lightdm-session from a tty fails with: x-session-manager: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_registry_interface -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1110645 Title: lightdm-session fails with x-session-manager: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_registry_interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1110645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1110645] [NEW] lightdm-session fails with x-session-manager: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_registry_interface
Public bug reported: (Since this is opened by hand I am unsure how to upload relevant logs) Since some of the following updates http://pastebin.ubuntu.com/1589997/ lightdm fails to start on boot. The Ubuntu loading screens loads, then lightdm fails. It is possible to switch to a tty, and networking is up (not sure if that helps). Intel HD 4000/ core i3 Xorg.0.log: http://pastebin.ubuntu.com/1590073/ /var/log/lightdm/x-0-greeter.log reads (only one line): /usr/sbin/unity-greeter: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined sybol: wl_registry_interface ** Affects: lightdm (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/1110645 Title: lightdm-session fails with x-session-manager: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_registry_interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1110645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1110645] Re: lightdm-session fails with x-session-manager: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_registry_interface
So the way I fixed my installation was to downgrade libwayland0 to 1.0.3-0ubuntu2, and remove ~/.Xauthority (otherwise you can't login). But yeah, this is introduced by using the qt5 PPA as suggested by the phone sdk tutorial, AFAICT. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1110645 Title: lightdm-session fails with x-session-manager: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_registry_interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1110645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644898] Re: required kernel toshiba support not enabled
This is still a problem on Precise. @keks9n - Would you provide a PPA for precise? That would be really appreciated, worked a treat on Oneiric. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/644898 Title: required kernel toshiba support not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/644898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190510] Re: Update lucid, raring, quantal, precise to landscape-client 13.07.3
** Changed in: landscape-client Status: In Progress = Fix Committed ** Changed in: landscape-client Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190510 Title: Update lucid, raring, quantal, precise to landscape-client 13.07.3 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1190510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262663] [NEW] DS9 exits with buffer overflow detected
Public bug reported: When trying to load a file in the saucy version of DS9 (http://pastebin.ubuntu.com/6599685/), the program exits with the following stacktrace: http://pastebin.ubuntu.com/6599657/ The same procedure on raring succeeds. Steps to reproduce: - On Ubuntu 13.10 x86_64, install DS9 (sudo apt-get install saods9) - Open a fits file with DS9 What happened: The program exits with the pasted stacktrace. What was expected to happen: The image loads and DS9 continues normal operation. Please let me know if I can provide further information. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: saods9 7.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 19 14:22:57 2013 InstallationDate: Installed on 2013-11-16 (33 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: saods9 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: saods9 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262663 Title: DS9 exits with buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/saods9/+bug/1262663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105037] [NEW] Steam fails to paint windows after upgrading to raring
Public bug reported: Steam for Ubuntu fails to paint its windows after upgrading to 13.04 (see attached screenshot). Since my steam version didn't change during the upgrade to raring I assume this is a graphics stack regression, although I am not sure if this applies to xorg. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,move,regex,vpswitch,mousepoll,snap,compiztoolbox,gnomecompat,resize,imgpng,animation,place,workarounds,wall,unitymtgrabhandles,grid,expo,session,fade,ezoom,scale,unityshell] CompositorRunning: compiz Date: Fri Jan 25 13:26:29 2013 DistUpgraded: 2013-01-25 09:16:44,887 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0009] InstallationDate: Installed on 2012-10-09 (108 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121009) MachineType: TOSHIBA SATELLITE Z830 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=03938aa1-7f0e-4a93-a7bb-2b6e7b721150 ro quiet splash acpi_backlight=vendor acpi_os=Linux pcie_aspm=force i915.i915_enable_rc6=1 i915.lvds_downclock=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to raring on 2013-01-25 (0 days ago) dmi.bios.date: 10/19/2011 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd10/19/2011:svnTOSHIBA:pnSATELLITEZ830:pvrPT22LE-00F004EN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: SATELLITE Z830 dmi.product.version: PT22LE-00F004EN dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.9~daily13.01.21-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Fri Jan 25 12:19:31 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DP1 HDMI1 LVDS1VGA1 xserver.version: 2:1.13.1.901-0ubuntu2 xserver.video_driver: intel ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring running-unity ubuntu ** Attachment added: screenshot https://bugs.launchpad.net/bugs/1105037/+attachment/3499887/+files/Screenshot%20from%202013-01-25%2013%3A09%3A31.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105037 Title: Steam fails to paint windows after upgrading to raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1105037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105037] Re: Steam fails to paint windows after upgrading to raring
This bug was fix with the latest update to xserver-xorg-video- intel:amd64 Marking as invalid. ** Changed in: xorg (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105037 Title: Steam fails to paint windows after upgrading to raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1105037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303617] Re: Latest curtin version prevents Juju from bootstrapping on MAAS
** Also affects: curtin (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/1303617 Title: Latest curtin version prevents Juju from bootstrapping on MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1303617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303617] Re: Latest curtin version prevents Juju from bootstrapping on MAAS
** Description changed: Curtin version: 0.1.0~bzr124-0ubuntu1 Curtin-common: 0.1.0~bzr124-0ubuntu1 Bootstrapping a juju environment on an up-to-date trusty MAAS server fails. The bootstrap node becomes pingable but never allows connections to the juju agent. Cloud init output (shows error): http://pastebin.ubuntu.com/7215883/ Cloud init log: http://pastebin.ubuntu.com/7215881/ - Reverting python-curtin and curtin-common to 0.1.0~bzr121-0ubuntu1 works - around the problem. + Reverting python-curtin and curtin-common to 0.1.0~bzr121-0ubuntu1 does + not show the problem anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303617 Title: Latest curtin version prevents Juju from bootstrapping on MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1303617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358349] [NEW] Update to upstream 0.5
Public bug reported: Upstream released a new version - 0.5 The Ubuntu package in utopic should be updated as well. ** Affects: ubumirror (Ubuntu) Importance: Undecided Assignee: Chris Glass (tribaal) Status: In Progress ** Changed in: ubumirror (Ubuntu) Assignee: (unassigned) = Chris Glass (tribaal) ** Changed in: ubumirror (Ubuntu) Status: New = In Progress ** Branch linked: lp:~tribaal/ubuntu/utopic/ubumirror/upstream-0.5-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358349 Title: Update to upstream 0.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubumirror/+bug/1358349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1320587] Re: Intermittent 403 Issues
The linked branch should help with the problem, at the cost of an extra round-trip to the upstream archive. ** Branch linked: lp:~tribaal/squid-deb-proxy/refresh-ims -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1320587 Title: Intermittent 403 Issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1320587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303903] Re: sgdisk zap/clear doesn't wipe all GPT tables
** Tags added: landscape -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303903 Title: sgdisk zap/clear doesn't wipe all GPT tables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdisk/+bug/1303903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386455] Re: Chromium 37 has 159 known security issues
As of this morning I got 38.0.2125.111-0ubuntu0.14.10.1.1103 0 in Utopic. Thanks for your hard work Chad! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386455 Title: Chromium 37 has 159 known security issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1386455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341523] [NEW] New upstream release
Public bug reported: Hi, I recently took over the upstream development of ubumirror. I just created a new upstream release that fixes a few of the bugs reported here (as well as general cleanup o fthe codebase and added examples). This bug is meant to track the merge proposal I'm about to submit to the ubuntu ubumirror packaging branch. Since this is my first contribution to Ubuntu (on the packaging side), please feel free to point errors in the workflow/procedure :) ** Affects: ubumirror (Ubuntu) Importance: Undecided Assignee: Chris Glass (tribaal) Status: In Progress ** Changed in: ubumirror (Ubuntu) Assignee: (unassigned) = Chris Glass (tribaal) ** Changed in: ubumirror (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341523 Title: New upstream release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubumirror/+bug/1341523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341523] Re: New upstream release
** Branch linked: lp:~tribaal/ubuntu/utopic/ubumirror/1341523-upstream- release ** Description changed: Hi, I recently took over the upstream development of ubumirror. I just created a new upstream release that fixes a few of the bugs - reported here (as well as general cleanup o fthe codebase and added + reported here (as well as general cleanup of the codebase and added examples). This bug is meant to track the merge proposal I'm about to submit to the ubuntu ubumirror packaging branch. Since this is my first contribution to Ubuntu (on the packaging side), please feel free to point errors in the workflow/procedure :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341523 Title: New upstream release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubumirror/+bug/1341523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341523] Re: Update to upstream 0.4
** Summary changed: - New upstream release + Update to upstream 0.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341523 Title: Update to upstream 0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubumirror/+bug/1341523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595320] Re: example outdated
This should be fixed in the upstream reelase 0.4 (https://launchpad.net/ubumirror/trunk/0.4). A branch against this package was openened to update the packaged verion to upstream, but it is currently in need of sponsorship: https://bugs.launchpad.net/ubuntu/+source/ubumirror/+bug/1341523 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/595320 Title: example outdated To manage notifications about this bug go to: https://bugs.launchpad.net/server-papercuts/+bug/595320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341523] Re: Update to upstream 0.4
Removing myself as assignee as per https://wiki.ubuntu.com/SponsorshipProcess ** Changed in: ubumirror (Ubuntu) Assignee: Chris Glass (tribaal) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341523 Title: Update to upstream 0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubumirror/+bug/1341523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 939379] Re: Unexpected remote arg error
This should be fixed in the upstream release 0.4 (https://launchpad.net/ubumirror/trunk/0.4). A branch against this package was openened to update the packaged verion to upstream, but it is currently in need of sponsorship: https://bugs.launchpad.net/ubuntu/+source/ubumirror/+bug/1341523 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939379 Title: Unexpected remote arg error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubumirror/+bug/939379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889656] Re: installer stops using proxy
This is fixed since the python code (instead of bash) behaves properly now. Closing this bug (it's old, bug triage has taken a lot of dust). Feel free to reopen should this sting you again. ** Changed in: squid-deb-proxy (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889656 Title: installer stops using proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/889656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166667] Re: The default configuration is missing the /etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl file
This should be fixed in the next version of squid-deb-proxy when it's released. ** Changed in: squid-deb-proxy (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/117 Title: The default configuration is missing the /etc/squid-deb- proxy/autogenerated/pkg-blacklist-regexp.acl file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401523] Re: Update lucid, precise, trusty, utopic to landscape-client 14.12
Verification was done for individual bugs on lucid. ** Tags added: verification-done-lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401523 Title: Update lucid, precise, trusty, utopic to landscape-client 14.12 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1401523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1306824] Re: landscape.plugin.PluginConfigError: A processor info reader for 'aarch64' is not available.
Verified with the package in lucid-proposed. As noted there is no arm64 port for lucid, so I simply asserted the code was there (and it is). tribaal@ubuntu:~$ apt-cache policy landscape-client landscape-client: Installed: 14.12-0ubuntu0.10.04 Candidate: 14.12-0ubuntu0.10.04 Version table: *** 14.12-0ubuntu0.10.04 0 500 http://deb-mirror.habari.co.tz/ubuntu/ lucid-proposed/main Packages 100 /var/lib/dpkg/status 13.07.3-0ubuntu0.10.04 0 500 http://deb-mirror.habari.co.tz/ubuntu/ lucid-updates/main Packages 1.5.0.1-0ubuntu0.10.04.0 0 500 http://deb-mirror.habari.co.tz/ubuntu/ lucid/main Packages ** Tags added: verification-done-lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1306824 Title: landscape.plugin.PluginConfigError: A processor info reader for 'aarch64' is not available. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1306824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1374501] Re: Virtual machine detection failing when having QEMU as sys_vendor
Verified with the package in lucid-proposed: tribaal@ubuntu:~$ apt-cache policy landscape-client landscape-client: Installed: 14.12-0ubuntu0.10.04 Candidate: 14.12-0ubuntu0.10.04 Version table: *** 14.12-0ubuntu0.10.04 0 500 http://deb-mirror.habari.co.tz/ubuntu/ lucid-proposed/main Packages 100 /var/lib/dpkg/status 13.07.3-0ubuntu0.10.04 0 500 http://deb-mirror.habari.co.tz/ubuntu/ lucid-updates/main Packages 1.5.0.1-0ubuntu0.10.04.0 0 500 http://deb-mirror.habari.co.tz/ubuntu/ lucid/main Packages ** Tags added: verification-done-lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374501 Title: Virtual machine detection failing when having QEMU as sys_vendor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1374501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1374501] Re: Virtual machine detection failing when having QEMU as sys_vendor
Verified with the package in precise-proposed: tribaal@ubuntu:~$ apt-cache policy landscape-client landscape-client: Installed: 14.12-0ubuntu0.12.04 Candidate: 14.12-0ubuntu0.12.04 Version table: *** 14.12-0ubuntu0.12.04 0 500 http://deb-mirror.habari.co.tz/ubuntu/ precise-proposed/main amd64 Packages 100 /var/lib/dpkg/status 13.07.3-0ubuntu0.12.04 0 500 http://deb-mirror.habari.co.tz/ubuntu/ precise-updates/main amd64 Packages 12.04.3-0ubuntu1 0 500 http://deb-mirror.habari.co.tz/ubuntu/ precise/main amd64 Packages ** Tags removed: verification-needed ** Tags added: verification-done-precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374501 Title: Virtual machine detection failing when having QEMU as sys_vendor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1374501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401523] Re: Update lucid, precise, trusty, utopic to landscape-client 14.12
Verification was done for all individual bugs on Precise. All individual bugs have been verified for all target releases. ** Tags removed: verification-needed ** Tags added: verification-done-precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401523 Title: Update lucid, precise, trusty, utopic to landscape-client 14.12 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1401523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1306824] Re: landscape.plugin.PluginConfigError: A processor info reader for 'aarch64' is not available.
Verified with the pacakge in precise-proposed. I checked the code is the same as the utopic version that succeeds at solving the bug. tribaal@ubuntu:/usr/lib/python2.7/dist-packages/landscape$ apt-cache policy landscape-client landscape-client: Installed: 14.12-0ubuntu0.12.04 Candidate: 14.12-0ubuntu0.12.04 Version table: *** 14.12-0ubuntu0.12.04 0 500 http://deb-mirror.habari.co.tz/ubuntu/ precise-proposed/main amd64 Packages 100 /var/lib/dpkg/status 13.07.3-0ubuntu0.12.04 0 500 http://deb-mirror.habari.co.tz/ubuntu/ precise-updates/main amd64 Packages 12.04.3-0ubuntu1 0 500 http://deb-mirror.habari.co.tz/ubuntu/ precise/main amd64 Packages ** Tags removed: verification-needed ** Tags added: verification-done-precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1306824 Title: landscape.plugin.PluginConfigError: A processor info reader for 'aarch64' is not available. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1306824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401523] Re: Update lucid, precise, trusty, utopic to landscape-client 14.12
I tested 14.12-0ubuntu0.14.04 and this fixes the bug for me (no problems discovered). Changing to verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401523 Title: Update lucid, precise, trusty, utopic to landscape-client 14.12 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1401523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401523] Re: Update lucid, precise, trusty, utopic to landscape-client 14.12
(Re-flipping the tag since it appears it was done a bit prematurely) ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401523 Title: Update lucid, precise, trusty, utopic to landscape-client 14.12 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1401523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
** Also affects: nvidia-graphics-drivers-346 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-346-updates (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/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436723] [NEW] Regression: Nested LXC is broken on Vivid
Public bug reported: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc_container_default_with_nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) 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 -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] [NEW] Regression: Nested LXC is broken on Vivid
Public bug reported: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc_container_default_with_nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
** Tags added: landscape -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
** Tags added: landscape -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
So, the new lxcfs in vivid-proposed does *not* solve this particular problem. Again, running the daily PPA code solved this, but that means using the ppa for both vivid and trusty, not just vivid. Don't hesitate to let me know how I can test more/further versions of LXC, including git branches, if needed. -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
So, the new lxcfs in vivid-proposed does *not* solve this particular problem. Again, running the daily PPA code solved this, but that means using the ppa for both vivid and trusty, not just vivid. Don't hesitate to let me know how I can test more/further versions of LXC, including git branches, if needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
Ok, so it seems this isn't fixed after all. Following the exact steps reported in my original message result in a non-starting container (same error message) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
Ok, so it seems this isn't fixed after all. Following the exact steps reported in my original message result in a non-starting container (same error message) -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
** Changed in: lxc (Ubuntu) Status: Fix Released = Confirmed -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
** Changed in: lxc (Ubuntu) Status: Fix Released = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
This seems to be fixed in vivid with lxc 1.1.2: tribaal@vivid-test:~$ apt-cache policy lxc lxc: Installed: 1.1.2-0ubuntu1 Candidate: 1.1.2-0ubuntu1 Version table: *** 1.1.2-0ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status tribaal@vivid-test:~$ apt-cache policy lxc-templates lxc-templates: Installed: 1.1.2-0ubuntu1 Candidate: 1.1.2-0ubuntu1 Version table: *** 1.1.2-0ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
This seems to be fixed in vivid with lxc 1.1.2: tribaal@vivid-test:~$ apt-cache policy lxc lxc: Installed: 1.1.2-0ubuntu1 Candidate: 1.1.2-0ubuntu1 Version table: *** 1.1.2-0ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status tribaal@vivid-test:~$ apt-cache policy lxc-templates lxc-templates: Installed: 1.1.2-0ubuntu1 Candidate: 1.1.2-0ubuntu1 Version table: *** 1.1.2-0ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
** Description changed: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - - sudo su - - echo 'lxc.aa_profile = lxc_container_default_with_nesting' /var/lib/lxc/outer/config + - sudo su + - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: - lxc.network.type = veth - lxc.network.link = lxcbr0 - lxc.network.flags = up - lxc.network.hwaddr = 00:16:3e:xx:xx:xx + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up + lxc.network.hwaddr = 00:16:3e:xx:xx:xx -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
** Description changed: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - - sudo su - - echo 'lxc.aa_profile = lxc_container_default_with_nesting' /var/lib/lxc/outer/config + - sudo su + - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: - lxc.network.type = veth - lxc.network.link = lxcbr0 - lxc.network.flags = up - lxc.network.hwaddr = 00:16:3e:xx:xx:xx + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up + lxc.network.hwaddr = 00:16:3e:xx:xx:xx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
If both the host (vivid) and the outer guest run LXC from ppa:ubuntu- lxc/daily, the tested scenario works. sudo add-apt-repository ppa:ubuntu-lxc/daily #on both the vivid host and at leas the outer guest (trusty). N.b. Only works if both the host and the first guest run the ppa code - seems like only the host running the newest code doesn't help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
If both the host (vivid) and the outer guest run LXC from ppa:ubuntu- lxc/daily, the tested scenario works. sudo add-apt-repository ppa:ubuntu-lxc/daily #on both the vivid host and at leas the outer guest (trusty). N.b. Only works if both the host and the first guest run the ppa code - seems like only the host running the newest code doesn't help. -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
Oh, good to hear. Can I easily test what's in vivid-proposed, and/or somehow influence the landing? Since I have a pretty good test set up for this particular scenario I might as well help you guys :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
Oh, good to hear. Can I easily test what's in vivid-proposed, and/or somehow influence the landing? Since I have a pretty good test set up for this particular scenario I might as well help you guys :) -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
Adding ppa:ubuntu-lxc/daily seems to solve the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
Adding ppa:ubuntu-lxc/daily seems to solve the problem. -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
On the host. Sorry for taking so long to answer, launchpad seems to have eaten my email answer... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
On the host. Sorry for taking so long to answer, launchpad seems to have eaten my email answer... -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
Correction, on the host and on outer (just tried). -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
Correction, on the host and on outer (just tried). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475247] Re: ceph-disk-prepare --zap-disk hang
** Branch unlinked: lp:~tribaal/ubuntu/trusty/ceph/ceph-zap-in-two- phases ** Branch linked: lp:~tribaal/ubuntu/trusty/ceph/add-zap-fix-patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1475247 Title: ceph-disk-prepare --zap-disk hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+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 1475247] Re: ceph-disk-prepare --zap-disk hang
** Branch unlinked: lp:~tribaal/ubuntu/trusty/ceph/ceph-zap-in-two- phases ** Branch linked: lp:~tribaal/ubuntu/trusty/ceph/add-zap-fix-patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475247 Title: ceph-disk-prepare --zap-disk hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475247] Re: ceph-disk-prepare --zap-disk hang
** Changed in: ceph-osd (Juju Charms Collection) Status: In Progress = Fix Committed ** Changed in: ceph (Juju Charms Collection) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475247 Title: ceph-disk-prepare --zap-disk hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475247] Re: ceph-disk-prepare --zap-disk hang
** Changed in: ceph-osd (Juju Charms Collection) Status: In Progress = Fix Committed ** Changed in: ceph (Juju Charms Collection) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1475247 Title: ceph-disk-prepare --zap-disk hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+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 1475247] Re: ceph-disk-prepare --zap-disk hang
** Branch linked: lp:~tribaal/ubuntu/trusty/ceph/ceph-zap-in-two-phases -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475247 Title: ceph-disk-prepare --zap-disk hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475247] Re: ceph-disk-prepare --zap-disk hang
** Branch linked: lp:~tribaal/ubuntu/trusty/ceph/ceph-zap-in-two-phases -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1475247 Title: ceph-disk-prepare --zap-disk hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+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 1475247] Re: ceph-disk-prepare --zap-disk hang
** Changed in: ceph (Ubuntu Trusty) Assignee: (unassigned) = Chris Glass (tribaal) ** Changed in: ceph (Ubuntu Trusty) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1475247 Title: ceph-disk-prepare --zap-disk hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+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 1475247] Re: ceph-disk-prepare --zap-disk hang
** Changed in: ceph (Ubuntu Trusty) Assignee: (unassigned) = Chris Glass (tribaal) ** Changed in: ceph (Ubuntu Trusty) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475247 Title: ceph-disk-prepare --zap-disk hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482846] [NEW] Wifite 2.0r85-1 fails to capture handshakes
Public bug reported: While auditing my wireless network I realized the -wpa attacks do not work currently since it seems wifite is unable to capture handshake packets (it keeps cycling between deauthing and listening but never manages to capture handshakes). This obviously makes attacks against WPA fail. Versions tested on: vivid, up to date as of 8th of Aug 2015. $ apt-cache policy wifite wifite: Installed: 2.0r85-1 Candidate: 2.0r85-1 Version table: *** 2.0r85-1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: wifite (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/1482846 Title: Wifite 2.0r85-1 fails to capture handshakes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wifite/+bug/1482846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464064] Re: Ubuntu apt repos are not available via HTTPS
As a quick drive-by comment: HTTPS absolutely destroys package cacheability, which is a rather desirable feature for invariant, versionned and signed binary blobs (what deb packages are from an HTTP perspective). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464064 Title: Ubuntu apt repos are not available via HTTPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1464064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
