[Bug 1569424] Re: Please update python-docker to 1.8.0 from upstream
** Changed in: python-docker (Ubuntu) Status: Triaged => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569424 Title: [FFe] Please update python-docker to 1.8.0 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/1569424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569424] Re: Please update python-docker to 1.8.0 from upstream
** Changed in: python-docker (Ubuntu) Importance: Undecided => Wishlist ** Changed in: python-docker (Ubuntu) Status: New => Triaged ** Changed in: python-docker (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569424 Title: Please update python-docker to 1.8.0 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/1569424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569424] [NEW] Please update python-docker to 1.8.0 from upstream
Public bug reported: For openstack-magnum project, there is a need to update python-docker to 1.8.0 Python-docker is in universe, and apparently (through apt-rdepends) only docker-compose from universe depend on it. A proposal package is ready, and somehow tested. It has been tested via python cli, to check if it can create a simple container, units tests passed (coreycb). On a vm I installed docker-compose, a basic docker-compose.yml, ran it, upgrade python-docker, and re-run docker-compose. It seems to work well on this very simple test. I included a debdiff against python-docker-1.5.0-1ubuntu1 and the proposed package. Package logs can be found here: amd64:https://launchpad.net/~kick-d/+archive/ubuntu/upload-2/+build/9562825 http://paste.ubuntu.com/15793575/ ** Affects: python-docker (Ubuntu) Importance: Undecided Status: New ** Attachment added: "debdiff.patch" https://bugs.launchpad.net/bugs/1569424/+attachment/4634302/+files/debdiff.patch ** Description changed: For openstack-magnum project, there is a need to update python-docker to 1.8.0 - Python-docker is in univers, and apparently (through apt-rdepends) only + Python-docker is in universe, and apparently (through apt-rdepends) only docker-compose from universe depend on it. A proposal package is ready, and somehow tested. It has been tested via python cli, to check if it can create a simple - container, units tests passed. + container, units tests passed (coreycb). On a vm I installed docker-compose, a basic docker-compose.yml, ran it, upgrade python-docker, and re-run docker-compose. It seems to work well. I included a debdiff against python-docker-1.5.0-1ubuntu1 and the proposed package. + Package logs can be found here: + amd64:https://launchpad.net/~kick-d/+archive/ubuntu/upload-2/+build/9562825 + http://paste.ubuntu.com/15793575/ ** Description changed: For openstack-magnum project, there is a need to update python-docker to 1.8.0 Python-docker is in universe, and apparently (through apt-rdepends) only docker-compose from universe depend on it. A proposal package is ready, and somehow tested. It has been tested via python cli, to check if it can create a simple container, units tests passed (coreycb). On a vm I installed docker-compose, a basic docker-compose.yml, ran it, - upgrade python-docker, and re-run docker-compose. It seems to work well. + upgrade python-docker, and re-run docker-compose. It seems to work well + on this very simple test. I included a debdiff against python-docker-1.5.0-1ubuntu1 and the proposed package. Package logs can be found here: amd64:https://launchpad.net/~kick-d/+archive/ubuntu/upload-2/+build/9562825 http://paste.ubuntu.com/15793575/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569424 Title: Please update python-docker to 1.8.0 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/1569424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488962] Re: systemd does not notice when services created via systemd-sysv-generator fail
For reference, a systemd discussion for apache2 in a debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798430 ** Bug watch added: Debian Bug tracker #798430 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798430 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488962 Title: systemd does not notice when services created via systemd-sysv- generator fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1488962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543572] Re: mod_http2 is not available under Apache 2.4.18 / Ubuntu 16.04 xenial
** Changed in: apache2 (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543572 Title: mod_http2 is not available under Apache 2.4.18 / Ubuntu 16.04 xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1543572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488962] Re: systemd does not notice when services created via systemd-sysv-generator fail
(debhelper >= 9) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488962 Title: systemd does not notice when services created via systemd-sysv- generator fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1488962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1488962] Re: systemd does not notice when services created via systemd-sysv-generator fail
Yes, but I wanted to rename it with dh-exec, but it requires debhelper >9, and I thought creating a subdir just for that file would have been overkill. But I can change the name. Le 08/04/2016 12:18, Martin Pitt a écrit : > Calling the drop-in apache2.service.d/apache2-systemd.conf sounds a bit > redundant, I think a name like forking.conf would be a bit more > expressive. But this is just a nitpick, looks good to me in general. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488962 Title: systemd does not notice when services created via systemd-sysv- generator fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1488962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488962] Re: systemd does not notice when services created via systemd-sysv-generator fail
Here is a debdiff proposal: http://paste.ubuntu.com/15684047/ tests: http://paste.ubuntu.com/15683923/ ** Patch added: "debdiff" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1488962/+attachment/4628793/+files/debdiff.patch ** Changed in: apache2 (Ubuntu) Status: Confirmed => 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/1488962 Title: systemd does not notice when services created via systemd-sysv- generator fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1488962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508225] Re: tipc tool isn't built in iproute2
Thanks for testing. It will be available soon in the archive. Regards, Pierre-André -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508225 Title: tipc tool isn't built in iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1508225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508225] Re: tipc tool isn't built in iproute2
Hi Jon, Can you test a new iproute2 package in this ppa:kick-d/upload ? Regards, Pierre-André -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508225 Title: tipc tool isn't built in iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1508225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508225] Re: tipc tool isn't built in iproute2
** Changed in: iproute2 (Ubuntu) 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/1508225 Title: tipc tool isn't built in iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1508225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560474] Re: Please merge clamav (0.99+dfsg-2) from Debian unstable
debdiff without '~ppa1' appended to version: http://paste.ubuntu.com/15487552/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560474 Title: Please merge clamav (0.99+dfsg-2) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1560474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)
I did some upgrade testing on squid3 and there are some troubles apparently, I suspect and will try to modify debian/control to make it work (at least for upgrade from xenial to xenial-proposed). - >From precise to trusty with squid3 + squid-deb-proxy +squidguard (to check >squid/squid3 renaming with ubuntu deltas) Last week it was ok (3.3.8-1ubuntu6.4), now upgrading from squid(3) + squid-deb-proxy + squidguard is broken 3.3.8-1ubuntu6.6. So it appears that I won't be able to test the full upgrade path from precise to xenial Squidguard would have created some troubles as it was still using /etc/squid or /var/log/squid in precise version. It would have been interesting to test because of this, but last upstream broke release upgrade (last week it failed at starting service but continued upgrade, now it doesn't allow the upgrade to finish). The following are my upgrade tests from trusty to xenial: long story short: it fails. I'm in a two stages update due to the squid package being in proposed, first stage from trusty to xenial current, and then to xenial-proposed. I did the test two times one with installing with 'squid', and then with 'squid3'. Both trusty setup were working squid3 + squidguard +squid-deb-proxy, and basic conf was apply to check. First step upgrade caused squidguard to stop working (certainly some API related stuff), and squid-deb-proxy service seems broken, as I can run it by hand. squid3 was still working. squid3 service is renamed to squid, we need to warn or take appropriate disposition as done in docker.io upgrade path. Second step upgrade broke squid3. Logs/reference to follow. squidguard and squid-deb-proxy are universe, but the upgrade path must be checked with them also to get some real-world upgrade path. http://paste.ubuntu.com/15480862/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473691 Title: [FFe] squid: Update to latest upstream release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560474] Re: Please merge clamav (0.99+dfsg-2) from Debian unstable
I do not believe a FFe is necessary, as the Debian changes between 0.99+dfsg-1 and 0.99+dfsg-2 are all bugfixes or debian/cleanups. debdiff: http://paste.ubuntu.com/15471802/ build successful on all arches; logs: amd64: https://launchpad.net/~canonical-server/+archive/ubuntu/devirt/+build/9380535 arm64: https://launchpad.net/~canonical-server/+archive/ubuntu/devirt/+build/9380536 armhf: https://launchpad.net/~canonical-server/+archive/ubuntu/devirt/+build/9380537 i386: https://launchpad.net/~canonical-server/+archive/ubuntu/devirt/+build/9380538 powerpc: https://launchpad.net/~canonical-server/+archive/ubuntu/devirt/+build/9380539 ppc64el: https://launchpad.net/~canonical-server/+archive/ubuntu/devirt/+build/9380540 s390x: https://launchpad.net/~canonical-server/+archive/ubuntu/devirt/+build/9380541 Install on xenial OK http://pastebin.ubuntu.com/15471831/ Upgrade on xenial OK http://pastebin.ubuntu.com/15471858/ Freshclam updated virus bases correctly on both install and clamscan seemed to work correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560474 Title: Please merge clamav (0.99+dfsg-2) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1560474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560474] [NEW] Please merge clamav (0.99+dfsg-2) from Debian unstable
Public bug reported: clamav (0.99+dfsg-2ubuntu1~ppa1) xenial; urgency=medium Merge from Debian. Remaining changes: * Explicitly build using llvm-3.6. * Ignore test results on armhf. * debian/rules: Restore --with-llvm-linking=dynamic to avoid underlinkage causing FTBS * d/p/llvm-don-t-use-system-libs.patch: Do not use system libraries for linking : We are not linking the .a files so we don't care about the libs llvm links against (like -ledit) Dropping this patch will cause FTBS on Ubuntu with unresolvable -ledit Dropped changes : * d/p/fix-ssize_t-size_t-off_t-printf-modifier.patch. Some differences in the file without any impact were added, reverted those cosmetic changes to minimize delta with upstream. -- Pierre-André MOREY Thu, 17 Mar 2016 15:44:10 +0100 clamav (0.99+dfsg-2) unstable; urgency=medium * Use compat 9 and drop clamav-dbg in favour of dbgsym. * use libtfm-dev instead of in-tree copy and drop all tfm related patches. * Add libclamav-yara-avoid-unaliged-access-to-64bit-variab.patch to get the testsuite passed on sparc. It also seem avoid invalid loads on ARMv5 cpus. -- Sebastian Andrzej Siewior Sun, 21 Feb 2016 15:25:59 +0100 ** Affects: clamav (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/1560474 Title: Please merge clamav (0.99+dfsg-2) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1560474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1546358] Re: policycoreutils (in universe) is installed by default by isc-dhcp-server as it is a Recommends
I did install all binaries, and there is no errorr messages related to postinst. There is a test to check if the restorecon binary from policycoreutils is present or not preventing the error to show up if it is not installed. 2016-02-19 0:48 GMT+01:00 Andres Rodriguez : > Here's the output of installing without Recommends (and coreutils): > > roaksoax@unleashed:~$ lxc exec xenial6 -- /bin/sh > # sudo apt-get install isc-dhcp-server --no-install-recommends > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following additional packages will be installed: > libirs-export91 libisccfg-export90 > Suggested packages: > isc-dhcp-server-ldap apparmor > Recommended packages: > policycoreutils > The following NEW packages will be installed: > isc-dhcp-server libirs-export91 libisccfg-export90 > 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. > Need to get 483 kB of archives. > After this operation, 1,718 kB of additional disk space will be used. > Do you want to continue? [Y/n] y > Get:1 http://archive.ubuntu.com/ubuntu xenial/main i386 libisccfg-export90 > i386 1:9.9.5.dfsg-12.1ubuntu1 [21.7 kB] > Get:2 http://archive.ubuntu.com/ubuntu xenial/main i386 libirs-export91 > i386 1:9.9.5.dfsg-12.1ubuntu1 [18.5 kB] > Get:3 http://archive.ubuntu.com/ubuntu xenial/main i386 isc-dhcp-server > i386 4.3.3-5ubuntu5 [443 kB] > Fetched 483 kB in 1s (405 kB/s) > Preconfiguring packages ... > Selecting previously unselected package libisccfg-export90. > (Reading database ... 12764 files and directories currently installed.) > Preparing to unpack > .../libisccfg-export90_1%3a9.9.5.dfsg-12.1ubuntu1_i386.deb ... > Unpacking libisccfg-export90 (1:9.9.5.dfsg-12.1ubuntu1) ... > Selecting previously unselected package libirs-export91. > Preparing to unpack .../libirs-export91_1%3a9.9.5.dfsg-12.1ubuntu1_i386.deb > ... > Unpacking libirs-export91 (1:9.9.5.dfsg-12.1ubuntu1) ... > Selecting previously unselected package isc-dhcp-server. > Preparing to unpack .../isc-dhcp-server_4.3.3-5ubuntu5_i386.deb ... > Unpacking isc-dhcp-server (4.3.3-5ubuntu5) ... > Processing triggers for libc-bin (2.21-0ubuntu6) ... > Processing triggers for ureadahead (0.100.0-19) ... > Processing triggers for systemd (229-1ubuntu2) ... > Setting up libisccfg-export90 (1:9.9.5.dfsg-12.1ubuntu1) ... > Setting up libirs-export91 (1:9.9.5.dfsg-12.1ubuntu1) ... > Setting up isc-dhcp-server (4.3.3-5ubuntu5) ... > Generating /etc/default/isc-dhcp-server... > Processing triggers for libc-bin (2.21-0ubuntu6) ... > Processing triggers for ureadahead (0.100.0-19) ... > Processing triggers for systemd (229-1ubuntu2) ... > # dpkg -l | grep policy > ii libsemanage-common2.3-1build2 all > Common files for SELinux policy management libraries > ii libsemanage1:i386 2.3-1build2 i386 > SELinux policy management library > # dpkg -l | grep policycoreutils > > On Thu, Feb 18, 2016 at 6:28 PM, Robie Basak <1546...@bugs.launchpad.net> > wrote: > > > Downgrading to Medium, as I feel that Critical needs a justification. > > > > ** Changed in: isc-dhcp (Ubuntu) > >Importance: Critical => Medium > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1546358 > > > > Title: > > policycoreutils (in universe) is installed by default by isc-dhcp- > > server as it is a Recommends > > > > To manage notifications about this bug go to: > > > > > https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1546358/+subscriptions > > > > > -- > Andres Rodriguez (RoAkSoAx) > Ubuntu Server Developer > MSc. Telecom & Networking > Systems Engineer > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1546358 > > Title: > policycoreutils (in universe) is installed by default by isc-dhcp- > server as it is a Recommends > > Status in isc-dhcp package in Ubuntu: > New > > Bug description: > Policycoreutils is being installed by default because the package is > listed as a Recommends. This package, however, is in universe and > seems to be pulling selinux. This should not be a recommends but > rather, it should be a Suggests. > > It seems that the postinst requires a binary being shipped in > policycoreutils: > > debian/isc-dhcp-server.postinst:test ! -x /sbin/restorecon || > /sbin/restorecon /var/lib/dhcp/dhcpd.leases > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1546358/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546358 Title: policycoreutils (in universe) is installed by default by isc-dhcp- server as it is a Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1546358/+subscriptio
Re: [Bug 1532145] Re: Kernel Panic wrt btrfs while sbuild/schroot
Thanks Colin! 2016-02-16 19:20 GMT+01:00 Colin Ian King <1532...@bugs.launchpad.net>: > I suggest a workaround for the moment, using aufs as the overlay to see > if this helps. > > Modify the chroot config and set the union-type to aufs: > > union-type=aufs > > you may see an error like: > > "aufs au_xino_create:778:mount[3600]: xino doesn't support > /tmp/.aufs.xino(btrfs)" > > this is caused by the fact that btrfs cannot store aufs xino files. > aufs tries to store these files alongside the rw layer. If that fails, > it tries to store them in /tmp/.aufs.xino, however, if this is btrfs it > will fail. So the workaround for that is to mount /tmp as something > other than btrfs, e.g. tmpfs > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1532145 > > Title: > Kernel Panic wrt btrfs while sbuild/schroot > > Status in Linux: > Unknown > Status in linux package in Ubuntu: > In Progress > > Bug description: > I'm running ubuntu Wily amd64 on a MSI Ghost Pro laptop. > > I'm running btrfs on top of a bcached dmraid setup(intel software > raid0). > > I can't use sbuild, cause it crashes. > > I tried to use a schroot env, and when updating it I got it to crash > also. > > All the keyboard/mouse/X11 are stalled, but I could ssh to it. > Trying to restart lightdm service didn't help. > > I've got a kernel trace in the dmesg: > > [76610.550953] BUG: unable to handle kernel NULL pointer dereference at > 0334 > [76610.550983] IP: [] btrfs_sync_file+0xcc/0x360 > [btrfs] > [76610.551025] PGD 160aaf067 PUD 161531067 PMD 0 > [76610.551039] Oops: 0002 [#1] SMP > [76610.551050] Modules linked in: dm_crypt algif_skcipher af_alg drbg > ansi_cprng ctr ccm rfcomm ipt_REJECT nf_reject_ipv4 nvram msr xt_multiport > ebtable_filter ebtables ip6table_filter ip6_tables overlay bnep uvcvideo > btusb videobuf2_vmalloc videobuf2_memops btrtl btbcm videobuf2_core btintel > v4l2_common bluetooth videodev media xt_addrtype xt_conntrack xt_CHECKSUM > iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat > nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp > bridge aufs stp llc iptable_filter ip_tables x_tables binfmt_misc arc4 > nls_iso8859_1 msi_wmi sparse_keymap intel_rapl iosf_mbi > x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp coretemp > crct10dif_pclmul snd_hda_codec_realtek snd_hda_codec_generic crc32_pclmul > aesni_intel aes_x86_64 lrw gf128mul > [76610.551253] snd_hda_intel iwlmvm glue_helper snd_hda_codec > ablk_helper mac80211 cryptd snd_hda_core snd_hwdep snd_pcm snd_seq_midi > joydev input_leds snd_seq_midi_event snd_rawmidi serio_raw iwlwifi lpc_ich > mei_me snd_seq mei cfg80211 snd_seq_device snd_timer snd ie31200_edac > edac_core soundcore shpchp mac_hid kvm_intel kvm parport_pc ppdev lp > parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log uas > usb_storage bcache hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper > psmouse ahci drm alx libahci mdio wmi video > [76610.551395] CPU: 1 PID: 32090 Comm: dpkg Not tainted 4.2.0-23-generic > #28-Ubuntu > [76610.551414] Hardware name: Micro-Star International Co., Ltd. GS60 > 2PE Ghost Pro/MS-16H2, BIOS E16H2IMS.112 05/05/2015 > [76610.551438] task: 8803cf422940 ti: 8801a0be4000 task.ti: > 8801a0be4000 > [76610.551455] RIP: 0010:[] [] > btrfs_sync_file+0xcc/0x360 [btrfs] > [76610.551485] RSP: 0018:8801a0be7e28 EFLAGS: 00010292 > [76610.551497] RAX: 8803cf422940 RBX: 880273bff100 RCX: > > [76610.551513] RDX: 8000 RSI: RDI: > 88040a2fb178 > [76610.551530] RBP: 8801a0be7eb8 R08: 0001 R09: > > [76610.551546] R10: 01f6 R11: 0246 R12: > 88040a2fb178 > [76610.551563] R13: 88040a2fb0d0 R14: R15: > > [76610.551580] FS: 7f3c27bca800() GS:88041fa4() > knlGS: > [76610.551598] CS: 0010 DS: ES: CR0: 80050033 > [76610.551611] CR2: 0334 CR3: 00016159a000 CR4: > 001406e0 > [76610.551628] Stack: > [76610.551633] 80033fffa865 000b 8000 > 88008a657e40 > [76610.551652] 7fff 8801a0be7ea8 > 8804069544a0 > [76610.551671] 800173bff000 10b6e564 > 10b6e564 > [76610.551691] Call Trace: > [76610.551703] [] vfs_fsync_range+0x4b/0xb0 > [76610.551718] [] do_fsync+0x3d/0x70 > [76610.551732] [] SyS_fsync+0x10/0x20 > [76610.551751] [] entry_SYSCALL_64_fastpath+0x16/0x75 > [76610.551766] Code: 8b 0e 48 85 c9 75 e8 eb 9e 48 8b 45 90 4c 8b 75 98 > 4d 8d a5 a8 00 00 00 4c 89 e7 4c 29 f0 48 83 c0 01 48 89 45 80 e8 f4 e2 4b > c1 41 ff 87 34 03 00 00 49 8b 85 70 ff ff ff 48 c1 e8 07 83 e0 > [76610.551845] RIP [] btrfs_sync_f
[Bug 1545699] [NEW] [MIR] pps-tools
Public bug reported: [Availability] The package is already present in universe: pps-tools | 0.20120406+g0deb9c7e-2 | trusty/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el pps-tools | 0.20120406+g0deb9c7e-2 | vivid/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el pps-tools | 0.20120406+g0deb9c7e-2 | wily/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el pps-tools | 0.20120406+g0deb9c7e-2 | xenial/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x It is in sync with debian: pps-tools | 0.20120406+g0deb9c7e-2 | oldstable | source, amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc pps-tools | 0.20120406+g0deb9c7e-2 | stable | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x pps-tools | 0.20120406+g0deb9c7e-2 | stable-kfreebsd | source pps-tools | 0.20120406+g0deb9c7e-2 | testing | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x pps-tools | 0.20120406+g0deb9c7e-2 | unstable| source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, powerpc, ppc64el, s390 [Rationale] This package is a new build-dependency for NTP. It is needed to be able to build PPS support into NTP (as per request in bug: #1512980) https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980 [Security] This package doesn't seem to have known vulnerabilities as per Debian CVE, Ubuntu CVE, or othere vulnerabilities tracker https://security-tracker.debian.org/tracker/source-package/pps-tools http://people.canonical.com/~ubuntu-security/cve/pkg/pps-tools.html http://cve.mitre.org/cgi-bin/cvekey.cgi, searched for pps and pps-tools). There are some warnings though, because there is a hardening-no-relro warning and an ancient-standards-version warning. https://lintian.debian.org/maintainer/b...@debian.org.html#pps-tools So, if the security requires it, we can create a temporary delta to fix those issues while reasonably request those changes to be included into Debian archives. [Quality assurance] This package is mainly needed because it contains the necessary headers to make PPS support available for NTP. There are some user-space binaries to allow setup and use of the PPS kernel discipline. This is the package description: This package includes the necessary headers for using LinuxPPS PPSAPI kernel interface in user-space applications and several support tools: * ppstest: PPSAPI interface tester * ppsldisc: setup correct RS232 line discipline * ppswatch: continuously print PPS timestamps * ppsctl: PPS device manager * ppsfind: find pps device by name [Dependencies] It only depends on 'already in main' dependencies. [Standards compliance] It complies to standard compliances (FHS and Debian policy). [Maintenance] Seems to not require much maintenance. Can be kept in sync with Debian, except if we need to change the build flags to add fPIE, bindnow, and relro. [Background information] This is a new dependency required to be able to build PPS support into NTP. ** Affects: pps-tools (Ubuntu) Importance: Undecided Status: New ** Description changed: [Availability] The package is already present in universe: - pps-tools | 0.20120406+g0deb9c7e-2 | trusty/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el - pps-tools | 0.20120406+g0deb9c7e-2 | vivid/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el - pps-tools | 0.20120406+g0deb9c7e-2 | wily/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el - pps-tools | 0.20120406+g0deb9c7e-2 | xenial/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x - + pps-tools | 0.20120406+g0deb9c7e-2 | trusty/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el + pps-tools | 0.20120406+g0deb9c7e-2 | vivid/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el + pps-tools | 0.20120406+g0deb9c7e-2 | wily/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el + pps-tools | 0.20120406+g0deb9c7e-2 | xenial/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x + It is in sync with debian: pps-tools | 0.20120406+g0deb9c7e-2 | oldstable | source, amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc pps-tools | 0.20120406+g0deb9c7e-2 | stable | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x pps-tools | 0.20120406+g0deb9c7e-2 | stable-kfreebsd | source pps-tools | 0.20120406+g0deb9c7e-2 | testing | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x pps-tools | 0.20120406+g0deb9c7e-2 | unstable| source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, powerpc, ppc64el, s390 [Rationale] - This package is a new build-dependency for NTP. It is needed to be able to build - PPS support into NTP (as per request in bug: #1512
[Bug 1532145] Re: Kernel Panic wrt btrfs while sbuild/schroot
** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=101951 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532145 Title: Kernel Panic wrt btrfs while sbuild/schroot To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1532145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532145] Re: Kernel Panic wrt btrfs while sbuild/schroot
Same bug that I already had with another laptop, it seems to be related to overlay and btrfs: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496438 Happens also on coreos: https://github.com/coreos/rkt/issues/1498 Kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=101951 ** Bug watch added: Linux Kernel Bug Tracker #101951 http://bugzilla.kernel.org/show_bug.cgi?id=101951 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532145 Title: Kernel Panic wrt btrfs while sbuild/schroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512980] Re: Please enable PPS in the Ubuntu build of ntpd
** Changed in: ntp (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/1512980 Title: Please enable PPS in the Ubuntu build of ntpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357424] Re: Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main)
Hi, Yes the work is being done currently. It is awaiting review. Thanks! 2016-01-14 0:17 GMT+01:00 Artur Rona : > Any news on that one? > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1357424 > > Title: > Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main) > > Status in amavisd-new package in Ubuntu: > Confirmed > > Bug description: > Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1357424/+subscriptions > ** Changed in: amavisd-new (Ubuntu) Status: Confirmed => 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/1357424 Title: Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1357424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227195] Re: new upstream release
** Changed in: amavisd-new (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1227195 Title: new upstream release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1227195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357424] Re: Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main)
** Changed in: amavisd-new (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357424 Title: Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1357424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532145] Re: Kernel Panic wrt btrfs while sbuild/schroot
output of lsblk: http://paste.ubuntu.com/14468218/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532145 Title: Kernel Panic wrt btrfs while sbuild/schroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532145] Re: Kernel Panic wrt btrfs while sbuild/schroot
I tried with the upstream v4.4-wily kernel. kick@kick-gs60:~/work/merges/freeipmi$ uname -a Linux kick-gs60 4.4.0-040400-generic #201601101930 SMP Mon Jan 11 00:32:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux I couldn't re-use my previous schroot (couldn't mount with overlayfs). I've created a new one with --type=btrfs-snapshot. My latop didn't freeze, but I still got traces in the syslog: [ 458.091294] BUG: unable to handle kernel NULL pointer dereference at 0334 [ 458.091320] IP: [] btrfs_sync_file+0xcc/0x350 [btrfs] [ 458.091363] PGD 3e8de9067 PUD 3e8de8067 PMD 0 [ 458.091374] Oops: 0002 [#1] SMP [ 458.091383] Modules linked in: overlay drbg ansi_cprng ctr ccm rfcomm nvram msr xt_multiport ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables xt_addrtype xt_conntrack xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables binfmt_misc bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btusb btrtl v4l2_common btbcm btintel videodev bluetooth media arc4 nls_iso8859_1 intel_rapl iwlmvm x86_pkg_temp_thermal intel_powerclamp coretemp msi_wmi sparse_keymap crct10dif_pclmul snd_hda_codec_realtek crc32_pclmul snd_hda_codec_hdmi snd_hda_codec_generic aesni_intel aes_x86_64 mac80211 lrw gf128mul glue_helper ablk_helper [ 458.091575] cryptd snd_hda_intel input_leds snd_hda_codec iwlwifi snd_hda_core snd_hwdep joydev snd_seq_midi snd_seq_midi_event serio_raw snd_pcm snd_rawmidi snd_seq snd_seq_device snd_timer lpc_ich cfg80211 mei_me snd mei soundcore ie31200_edac shpchp edac_core mac_hid kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log bcache hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm ahci alx libahci mdio wmi video fjes [ 458.091711] CPU: 1 PID: 5615 Comm: debconf-set-sel Not tainted 4.4.0-040400-generic #201601101930 [ 458.091731] Hardware name: Micro-Star International Co., Ltd. GS60 2PE Ghost Pro/MS-16H2, BIOS E16H2IMS.112 05/05/2015 [ 458.091755] task: 8803e1013700 ti: 8803e8d38000 task.ti: 8803e8d38000 [ 458.091771] RIP: 0010:[] [] btrfs_sync_file+0xcc/0x350 [btrfs] [ 458.091804] RSP: 0018:8803e8d3be48 EFLAGS: 00010246 [ 458.091815] RAX: 8803e1013700 RBX: 8803af242700 RCX: [ 458.091831] RDX: 8000 RSI: RDI: 880409d9c988 [ 458.091846] RBP: 8803e8d3bec8 R08: 0001 R09: 021f5338 [ 458.091861] R10: 009c R11: 0246 R12: 880409d9c988 [ 458.091876] R13: 880409d9c8e0 R14: R15: [ 458.091892] FS: 7f31a0444700() GS:88041fa4() knlGS: [ 458.091910] CS: 0010 DS: ES: CR0: 80050033 [ 458.091922] CR2: 0334 CR3: 0003e8f05000 CR4: 001406e0 [ 458.091937] Stack: [ 458.091942] 027bf270 0001 8000 8803bbc02540 [ 458.091960] 7fff [ 458.091978] 92eff2d8 92eff2d8 8803af242700 [ 458.091995] Call Trace: [ 458.092006] [] vfs_fsync_range+0x4b/0xb0 [ 458.092019] [] do_fsync+0x3d/0x70 [ 458.092030] [] SyS_fsync+0x10/0x20 [ 458.092043] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 458.092057] Code: 8b 0e 48 85 c9 75 e8 eb 9e 48 8b 45 a0 4c 8b 75 a8 4d 8d a5 a8 00 00 00 4c 89 e7 4c 29 f0 48 83 c0 01 48 89 45 90 e8 d4 48 4b c1 41 ff 87 34 03 00 00 49 8b 85 70 ff ff ff 48 c1 e8 07 83 e0 [ 458.092132] RIP [] btrfs_sync_file+0xcc/0x350 [btrfs] [ 458.092155] RSP [ 458.092163] CR2: 0334 [ 458.097834] ---[ end trace ff869f7e0dc1efc8 ]--- [ 467.516336] general protection fault: [#2] SMP [ 467.516353] Modules linked in: overlay drbg ansi_cprng ctr ccm rfcomm nvram msr xt_multiport ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables xt_addrtype xt_conntrack xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables binfmt_misc bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btusb btrtl v4l2_common btbcm btintel videodev bluetooth media arc4 nls_iso8859_1 intel_rapl iwlmvm x86_pkg_temp_thermal intel_powerclamp coretemp msi_wmi sparse_keymap crct10dif_pclmul snd_hda_codec_realtek crc32_pclmul snd_hda_codec_hdmi snd_hda_codec_generic aesni_intel aes_x86_64 mac80211 lrw gf128mul glue_helper ablk_helper [ 467.516558] cryptd snd_hda_intel input_leds snd_hda_codec iwlwifi snd_hda_core snd_hwdep joydev snd_seq_midi snd_seq_midi_event serio_raw snd_pcm s
[Bug 1532145] [NEW] Kernel Panic wrt btrfs while sbuild/schroot
Public bug reported: I'm running ubuntu Wily amd64 on a MSI Ghost Pro laptop. I'm running btrfs on top of a bcached dmraid setup(intel software raid0). I can't use sbuild, cause it crashes. I tried to use a schroot env, and when updating it I got it to crash also. All the keyboard/mouse/X11 are stalled, but I could ssh to it. Trying to restart lightdm service didn't help. I've got a kernel trace in the dmesg: [76610.550953] BUG: unable to handle kernel NULL pointer dereference at 0334 [76610.550983] IP: [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551025] PGD 160aaf067 PUD 161531067 PMD 0 [76610.551039] Oops: 0002 [#1] SMP [76610.551050] Modules linked in: dm_crypt algif_skcipher af_alg drbg ansi_cprng ctr ccm rfcomm ipt_REJECT nf_reject_ipv4 nvram msr xt_multiport ebtable_filter ebtables ip6table_filter ip6_tables overlay bnep uvcvideo btusb videobuf2_vmalloc videobuf2_memops btrtl btbcm videobuf2_core btintel v4l2_common bluetooth videodev media xt_addrtype xt_conntrack xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge aufs stp llc iptable_filter ip_tables x_tables binfmt_misc arc4 nls_iso8859_1 msi_wmi sparse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp coretemp crct10dif_pclmul snd_hda_codec_realtek snd_hda_codec_generic crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul [76610.551253] snd_hda_intel iwlmvm glue_helper snd_hda_codec ablk_helper mac80211 cryptd snd_hda_core snd_hwdep snd_pcm snd_seq_midi joydev input_leds snd_seq_midi_event snd_rawmidi serio_raw iwlwifi lpc_ich mei_me snd_seq mei cfg80211 snd_seq_device snd_timer snd ie31200_edac edac_core soundcore shpchp mac_hid kvm_intel kvm parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log uas usb_storage bcache hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper psmouse ahci drm alx libahci mdio wmi video [76610.551395] CPU: 1 PID: 32090 Comm: dpkg Not tainted 4.2.0-23-generic #28-Ubuntu [76610.551414] Hardware name: Micro-Star International Co., Ltd. GS60 2PE Ghost Pro/MS-16H2, BIOS E16H2IMS.112 05/05/2015 [76610.551438] task: 8803cf422940 ti: 8801a0be4000 task.ti: 8801a0be4000 [76610.551455] RIP: 0010:[] [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551485] RSP: 0018:8801a0be7e28 EFLAGS: 00010292 [76610.551497] RAX: 8803cf422940 RBX: 880273bff100 RCX: [76610.551513] RDX: 8000 RSI: RDI: 88040a2fb178 [76610.551530] RBP: 8801a0be7eb8 R08: 0001 R09: [76610.551546] R10: 01f6 R11: 0246 R12: 88040a2fb178 [76610.551563] R13: 88040a2fb0d0 R14: R15: [76610.551580] FS: 7f3c27bca800() GS:88041fa4() knlGS: [76610.551598] CS: 0010 DS: ES: CR0: 80050033 [76610.551611] CR2: 0334 CR3: 00016159a000 CR4: 001406e0 [76610.551628] Stack: [76610.551633] 80033fffa865 000b 8000 88008a657e40 [76610.551652] 7fff 8801a0be7ea8 8804069544a0 [76610.551671] 800173bff000 10b6e564 10b6e564 [76610.551691] Call Trace: [76610.551703] [] vfs_fsync_range+0x4b/0xb0 [76610.551718] [] do_fsync+0x3d/0x70 [76610.551732] [] SyS_fsync+0x10/0x20 [76610.551751] [] entry_SYSCALL_64_fastpath+0x16/0x75 [76610.551766] Code: 8b 0e 48 85 c9 75 e8 eb 9e 48 8b 45 90 4c 8b 75 98 4d 8d a5 a8 00 00 00 4c 89 e7 4c 29 f0 48 83 c0 01 48 89 45 80 e8 f4 e2 4b c1 41 ff 87 34 03 00 00 49 8b 85 70 ff ff ff 48 c1 e8 07 83 e0 [76610.551845] RIP [] btrfs_sync_file+0xcc/0x360 [btrfs] [76610.551871] RSP [76610.551881] CR2: 0334 [76610.558028] ---[ end trace 33509d397c46cd18 ]--- ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-23-generic 4.2.0-23.28 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Jan 8 11:02:06 2016 HibernationDevice: RESUME=UUID=1699e24b-be2c-494d-90ff-0f313a5eed84 InstallationDate: Installed on 2015-11-24 (44 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151016) MachineType: Micro-Star International Co., Ltd. GS60 2PE Ghost Pro ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-23-generic.efi.signed root=UUID=e8f9dc8a-aa49-481d-8fcc-be8cff0f61b1 ro rootflags=subvol=@ blacklist=nouveau quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-23-generic N/A linux-backports-modules-4.2.0-23-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Err
[Bug 1483093] Re: .archive.ubuntu.com is non inclusive
Hi José, I tried to re-create your setup for reproducing the bug. This is what I've done using Trusty 14.04.3 for all machines: Created a router vm that will nat all traffic and manage dns/dhcp of a dedicated subnet for those tests. On this subnet there is a apt-mirror setup vm with squid-deb-proxy installed (using apache2 default setup to serve files) The dns redirect fr.archive.ubuntu.com and archive.ubuntu.com to the apt-mirror setup (mirror: 192.168.101.2) I have a client vm in this subnet, with a squid-deb-proxy-client setup. I could update and install packages both from fr.archive.ubuntu.com and archive.ubuntu.com, while checking that it really end-up in the apt- mirror vm, and that was the case for both targets. No 403 errors, and using stock squid-deb-proxy mirror-dstdomain.acl file. So I will mark it as incomplete, because I couldn't reproduce it, feel free to re-open with more details if you think it is still relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1483093 Title: .archive.ubuntu.com is non inclusive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1483093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1483093] Re: .archive.ubuntu.com is non inclusive
** Changed in: squid-deb-proxy (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1483093 Title: .archive.ubuntu.com is non inclusive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1483093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1454719] Re: docker.io update to 1.6.2
Thanks, for reporting this. 2015-11-02 21:14 GMT+01:00 Fathi Boudra : > > For now we have no plan for supporting docker on arm64 on trusty, even if > > go-md2man could be made building on trusty arm64, docker won't build on > > arm64 trusty. > > fwiw, we can run successfully docker armhf on trusty arm64. > > > Docker for arm64 is available from vivid. > > so I've installed wily and docker arm64 seems broken: > > [ 166.631586] docker[1582]: syscall 1042 > [ 166.631593] Code: d284 d285 f94007e8 d401 (b13ffc1f) > [ 166.631599] CPU: 3 PID: 1582 Comm: docker Tainted: GW > 4.2.0-16-generic #19-Ubuntu > [ 166.631602] Hardware name: APM X-Gene Mustang board (DT) > [ 166.631605] task: ffc3eb91cc80 ti: ffc3e66c task.ti: > ffc3e66c > [ 166.631609] PC is at 0x619b30 > [ 166.631611] LR is at 0x6155f8 > [ 166.631613] pc : [<00619b30>] lr : [<006155f8>] pstate: > 2000 > [ 166.631615] sp : 0048202cb3d0 > [ 166.631617] x29: 007fabada870 x28: 0048200f0600 > [ 166.631621] x27: 00fc41e5 x26: 0048202cb3e0 > [ 166.631624] x25: 306414c4 x24: 3ed678b1 > [ 166.631627] x23: 37af13b0 x22: 0002 > [ 166.631630] x21: x20: 000b > [ 166.631632] x19: 000c x18: > [ 166.631635] x17: 00d5e6c8 x16: 0048205405a8 > [ 166.631638] x15: 0070 x14: > [ 166.631640] x13: x12: 0008 > [ 166.631643] x11: x10: 00d5a958 > [ 166.631646] x9 : 0002 x8 : 0412 > [ 166.631648] x7 : 0003 x6 : > [ 166.631651] x5 : x4 : > [ 166.631653] x3 : x2 : > [ 166.631655] x1 : x0 : 0001 > > docker is calling epoll_create, which is replaced with epoll_create1. > > I've built docker 1.7.1 from > https://github.com/coreos/docker/commits/coreos-1.7.1 which contains > some arm64 fixes and it worked fine. > > -- > You received this bug notification because you are a member of Docker > Ubuntu Maintainers, which is subscribed to docker.io in Ubuntu. > Matching subscriptions: kick > https://bugs.launchpad.net/bugs/1454719 > > Title: > docker.io update to 1.6.2 > > Status in docker.io package in Ubuntu: > Fix Released > Status in go-md2man package in Ubuntu: > Fix Released > Status in golang-blackfriday package in Ubuntu: > Fix Released > Status in golang-context-dev package in Ubuntu: > Fix Released > Status in golang-dbus package in Ubuntu: > Fix Released > Status in golang-fsnotify package in Ubuntu: > Fix Released > Status in golang-go-patricia package in Ubuntu: > Fix Released > Status in golang-gocapability-dev package in Ubuntu: > Fix Released > Status in golang-logrus package in Ubuntu: > Fix Released > Status in golang-objx package in Ubuntu: > Fix Released > Status in golang-pty-dev package in Ubuntu: > Fix Released > Status in golang-testify package in Ubuntu: > Fix Released > Status in docker.io source package in Trusty: > Fix Released > Status in go-md2man source package in Trusty: > Fix Released > Status in golang-blackfriday source package in Trusty: > Fix Released > Status in golang-context-dev source package in Trusty: > Fix Released > Status in golang-dbus source package in Trusty: > Fix Released > Status in golang-fsnotify source package in Trusty: > Fix Released > Status in golang-go-patricia source package in Trusty: > Fix Released > Status in golang-gocapability-dev source package in Trusty: > Fix Released > Status in golang-logrus source package in Trusty: > Fix Released > Status in golang-objx source package in Trusty: > Fix Released > Status in golang-pty-dev source package in Trusty: > Fix Released > Status in golang-testify source package in Trusty: > Fix Released > Status in docker.io source package in Utopic: > Won't Fix > Status in go-md2man source package in Utopic: > Won't Fix > Status in golang-dbus source package in Utopic: > Won't Fix > Status in golang-fsnotify source package in Utopic: > Won't Fix > Status in golang-go-patricia source package in Utopic: > Won't Fix > Status in golang-gocapability-dev source package in Utopic: > Won't Fix > Status in golang-logrus source package in Utopic: > Won't Fix > Status in golang-objx source package in Utopic: > Won't Fix > Status in golang-pty-dev source package in Utopic: > Won't Fix > Status in golang-testify source package in Utopic: > Won't Fix > Status in docker.io source package in Vivid: > Fix Released > Status in go-md2man source package in Vivid: > Fix Released > Status in golang-dbus source package in Vivid: > Fix Released > Status in golang-fsnotify source package in Vivid: > Fix Released > Status in golang-go-patricia source package in Vivid: > Fix Released > Status in golang-g
Re: [Bug 1454719] Re: docker.io update to 1.6.2
How can I reproduce this error on arm64? 2015-11-03 8:12 GMT+01:00 Pierre-Andre Morey < pierre-andre.mo...@canonical.com>: > Thanks, for reporting this. > > 2015-11-02 21:14 GMT+01:00 Fathi Boudra : > >> > For now we have no plan for supporting docker on arm64 on trusty, even >> if >> > go-md2man could be made building on trusty arm64, docker won't build on >> > arm64 trusty. >> >> fwiw, we can run successfully docker armhf on trusty arm64. >> >> > Docker for arm64 is available from vivid. >> >> so I've installed wily and docker arm64 seems broken: >> >> [ 166.631586] docker[1582]: syscall 1042 >> [ 166.631593] Code: d284 d285 f94007e8 d401 (b13ffc1f) >> [ 166.631599] CPU: 3 PID: 1582 Comm: docker Tainted: GW >> 4.2.0-16-generic #19-Ubuntu >> [ 166.631602] Hardware name: APM X-Gene Mustang board (DT) >> [ 166.631605] task: ffc3eb91cc80 ti: ffc3e66c task.ti: >> ffc3e66c >> [ 166.631609] PC is at 0x619b30 >> [ 166.631611] LR is at 0x6155f8 >> [ 166.631613] pc : [<00619b30>] lr : [<006155f8>] >> pstate: 2000 >> [ 166.631615] sp : 0048202cb3d0 >> [ 166.631617] x29: 007fabada870 x28: 0048200f0600 >> [ 166.631621] x27: 00fc41e5 x26: 0048202cb3e0 >> [ 166.631624] x25: 306414c4 x24: 3ed678b1 >> [ 166.631627] x23: 37af13b0 x22: 0002 >> [ 166.631630] x21: x20: 000b >> [ 166.631632] x19: 000c x18: >> [ 166.631635] x17: 00d5e6c8 x16: 0048205405a8 >> [ 166.631638] x15: 0070 x14: >> [ 166.631640] x13: x12: 0008 >> [ 166.631643] x11: x10: 00d5a958 >> [ 166.631646] x9 : 0002 x8 : 0412 >> [ 166.631648] x7 : 0003 x6 : >> [ 166.631651] x5 : x4 : >> [ 166.631653] x3 : x2 : >> [ 166.631655] x1 : x0 : 0001 >> >> docker is calling epoll_create, which is replaced with epoll_create1. >> >> I've built docker 1.7.1 from >> https://github.com/coreos/docker/commits/coreos-1.7.1 which contains >> some arm64 fixes and it worked fine. >> >> -- >> You received this bug notification because you are a member of Docker >> Ubuntu Maintainers, which is subscribed to docker.io in Ubuntu. >> Matching subscriptions: kick >> https://bugs.launchpad.net/bugs/1454719 >> >> Title: >> docker.io update to 1.6.2 >> >> Status in docker.io package in Ubuntu: >> Fix Released >> Status in go-md2man package in Ubuntu: >> Fix Released >> Status in golang-blackfriday package in Ubuntu: >> Fix Released >> Status in golang-context-dev package in Ubuntu: >> Fix Released >> Status in golang-dbus package in Ubuntu: >> Fix Released >> Status in golang-fsnotify package in Ubuntu: >> Fix Released >> Status in golang-go-patricia package in Ubuntu: >> Fix Released >> Status in golang-gocapability-dev package in Ubuntu: >> Fix Released >> Status in golang-logrus package in Ubuntu: >> Fix Released >> Status in golang-objx package in Ubuntu: >> Fix Released >> Status in golang-pty-dev package in Ubuntu: >> Fix Released >> Status in golang-testify package in Ubuntu: >> Fix Released >> Status in docker.io source package in Trusty: >> Fix Released >> Status in go-md2man source package in Trusty: >> Fix Released >> Status in golang-blackfriday source package in Trusty: >> Fix Released >> Status in golang-context-dev source package in Trusty: >> Fix Released >> Status in golang-dbus source package in Trusty: >> Fix Released >> Status in golang-fsnotify source package in Trusty: >> Fix Released >> Status in golang-go-patricia source package in Trusty: >> Fix Released >> Status in golang-gocapability-dev source package in Trusty: >> Fix Released >> Status in golang-logrus source package in Trusty: >> Fix Released >> Status in golang-objx source package in Trusty: >> Fix Released >> Status in golang-pty-dev source package in Trusty: >> Fix Released >> Status in golang-testify source package in Trusty: >> Fix Released >> Status in docker.io source package in Utopic: >> Won't Fix >> Status in go-md2man source package in Utopic: >> Won't Fix >> Status in golang-dbus source package in Utopic: >> Won't Fix >> Status in golang-fsnotify source package in Utopic: >> Won't Fix >> Status in golang-go-patricia source package in Utopic: >> Won't Fix >> Status in golang-gocapability-dev source package in Utopic: >> Won't Fix >> Status in golang-logrus source package in Utopic: >> Won't Fix >> Status in golang-objx source package in Utopic: >> Won't Fix >> Status in golang-pty-dev source package in Utopic: >> Won't Fix >> Status in golang-testify source package in Utopic: >> Won't Fix >> Status in docker.io source package in Vivid: >> Fix Released >> Status in go-md2man source packag
[Bug 1511803] Re: /etc/default/docker is read by systemd and contains invalid export statement
** Changed in: docker.io (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511803 Title: /etc/default/docker is read by systemd and contains invalid export statement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1511803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511784] Re: Starting docker.io remounts root filesystem read-only
** Changed in: docker.io (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511784 Title: Starting docker.io remounts root filesystem read-only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1511784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1454719] Re: docker.io update to 1.6.2
Hi, For now we have no plan for supporting docker on arm64 on trusty, even if go-md2man could be made building on trusty arm64, docker won't build on arm64 trusty. Docker for arm64 is available from vivid. 2015-10-31 9:13 GMT+01:00 Fathi Boudra : > go-md2man failed to build on trusty arm64, hence blocking docker.io for > trusty arm64. > > -- > You received this bug notification because you are a member of Docker > Ubuntu Maintainers, which is subscribed to docker.io in Ubuntu. > Matching subscriptions: kick > https://bugs.launchpad.net/bugs/1454719 > > Title: > docker.io update to 1.6.2 > > Status in docker.io package in Ubuntu: > Fix Released > Status in go-md2man package in Ubuntu: > Fix Released > Status in golang-blackfriday package in Ubuntu: > Fix Released > Status in golang-context-dev package in Ubuntu: > Fix Released > Status in golang-dbus package in Ubuntu: > Fix Released > Status in golang-fsnotify package in Ubuntu: > Fix Released > Status in golang-go-patricia package in Ubuntu: > Fix Released > Status in golang-gocapability-dev package in Ubuntu: > Fix Released > Status in golang-logrus package in Ubuntu: > Fix Released > Status in golang-objx package in Ubuntu: > Fix Released > Status in golang-pty-dev package in Ubuntu: > Fix Released > Status in golang-testify package in Ubuntu: > Fix Released > Status in docker.io source package in Trusty: > Fix Released > Status in go-md2man source package in Trusty: > Fix Released > Status in golang-blackfriday source package in Trusty: > Fix Released > Status in golang-context-dev source package in Trusty: > Fix Released > Status in golang-dbus source package in Trusty: > Fix Released > Status in golang-fsnotify source package in Trusty: > Fix Released > Status in golang-go-patricia source package in Trusty: > Fix Released > Status in golang-gocapability-dev source package in Trusty: > Fix Released > Status in golang-logrus source package in Trusty: > Fix Released > Status in golang-objx source package in Trusty: > Fix Released > Status in golang-pty-dev source package in Trusty: > Fix Released > Status in golang-testify source package in Trusty: > Fix Released > Status in docker.io source package in Utopic: > Won't Fix > Status in go-md2man source package in Utopic: > Won't Fix > Status in golang-dbus source package in Utopic: > Won't Fix > Status in golang-fsnotify source package in Utopic: > Won't Fix > Status in golang-go-patricia source package in Utopic: > Won't Fix > Status in golang-gocapability-dev source package in Utopic: > Won't Fix > Status in golang-logrus source package in Utopic: > Won't Fix > Status in golang-objx source package in Utopic: > Won't Fix > Status in golang-pty-dev source package in Utopic: > Won't Fix > Status in golang-testify source package in Utopic: > Won't Fix > Status in docker.io source package in Vivid: > Fix Released > Status in go-md2man source package in Vivid: > Fix Released > Status in golang-dbus source package in Vivid: > Fix Released > Status in golang-fsnotify source package in Vivid: > Fix Released > Status in golang-go-patricia source package in Vivid: > Fix Released > Status in golang-gocapability-dev source package in Vivid: > Fix Released > Status in golang-logrus source package in Vivid: > Fix Released > Status in golang-objx source package in Vivid: > Fix Released > > Bug description: > 1.6.2 is available in Debian. This needs to be merged to Wily and > backported in SRUs to Trusty, Utopic and Vivid as approved by the > technical board[0]. > > [0]: https://lists.ubuntu.com/archives/technical- > board/2015-April/002090.html > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1454719/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454719 Title: docker.io update to 1.6.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1454719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509867] Re: docker network connection only working after daemon restart
Hi, I could reproduce with a full blown ubuntu, I'm trying to find the issue. With docker inspect, you can get the Pid of the container you want to debug on. Then as root you create if it doesn't exist /var/run/netns, then you link /proc/$pid/ns/net /var/run/netns/container_name. Then you can issue commands like ip netns exec container_name ip addr, ip netns exec container_name ping etc... I'm still looking at what is creating this behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509867 Title: docker network connection only working after daemon restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1509867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466550] Re: docker lxc driver fails
** Changed in: docker.io (Ubuntu Vivid) Status: In Progress => 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/1466550 Title: docker lxc driver fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1466550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509867] Re: docker network connection only working after daemon restart
Hi, Thanks for your report. I tried to reproduce on a minimal ubuntu install, steps I've done yet: 1- install docker on vivid host (1.5.0, for now), start an openssh-server container 2-so-release-upgrade of the vivid host to wily host (upgraded to docker.io-1.6.2) 3-after reboot start container, I can login into the container (after a proper docker port to get the right port to connect to). 4-reboot again, and start and try to connect to the container: working. Will try with redirects, and if I can't reproduce with full-blown ubuntu. You did the upgrade from vivid to wily? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509867 Title: docker network connection only working after daemon restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1509867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509867] Re: docker network connection only working after daemon restart
** Changed in: docker.io (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509867 Title: docker network connection only working after daemon restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1509867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454719] Re: docker.io update to 1.6.2
** 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/1454719 Title: docker.io update to 1.6.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1454719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469204] Re: /etc/default/docker format is wrong for systemd service
Hi Guido Serra, Which version of docker did you install ? The one from ubuntu wily archive? I just installed docker.io from archive on a wily vm, and I got this systemd unit: docker.io 1.6.2~dfsg1-1ubuntu3amd64 Linux container runtime [Unit] Description=Docker Application Container Engine Documentation=http://docs.docker.com After=network.target docker.socket Requires=docker.socket [Service] EnvironmentFile=-/etc/default/docker ExecStart=/usr/bin/docker -d -H fd:// $DOCKER_OPTS MountFlags=slave LimitNOFILE=1048576 LimitNPROC=1048576 LimitCORE=infinity [Install] WantedBy=multi-user.target -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1469204 Title: /etc/default/docker format is wrong for systemd service To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1469204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488669] Re: consider building with golang-go on wily-arm64
** Changed in: docker.io (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488669 Title: consider building with golang-go on wily-arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1488669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496438] [NEW] 4.2.0.7 BUG: unable to handle kernel NULL pointer dereference at 0000000000000334
Public bug reported: I don't know how to reproduce this, as it worked for 2 weeks before happening, but was consistent then. I used btrfs on top of bcache on top of lvm. While trying to sbuild a package I got strange errors, got this messge in dmesg. Kernel 4.2.0-7-lowlatency release: wily: lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda8:00 465,8G 0 disk ├─hdd-Work 252:40 232,9G 0 lvm │ └─bcache0 251:00 232,9G 0 disk /home └─hdd-Home 252:50 232,9G 0 lvm └─bcache1 251:10 232,9G 0 disk /media/Work sdb8:16 0 238,5G 0 disk ├─sdb1 8:17 0 512M 0 part /boot/efi ├─sdb2 8:18 0 244M 0 part /boot └─sdb3 8:19 0 237,8G 0 part ├─ssd-root 252:0064G 0 lvm / ├─ssd-bcache 252:1064G 0 lvm │ ├─bcache0251:00 232,9G 0 disk /home │ └─bcache1251:10 232,9G 0 disk /media/Work ├─ssd-swap 252:20 8G 0 lvm │ └─cryptswap1 252:60 8G 0 crypt [SWAP] └─ssd-Free 252:30 101,8G 0 lvm /media/Free loop0 7:00 800M 0 loop └─secrets252:70 798M 0 crypt /home/kick/Secrets Kernel traces: [ 224.670454] BUG: unable to handle kernel NULL pointer dereference at 0334 [ 224.672387] IP: [] btrfs_sync_file+0xc1/0x360 [btrfs] [ 224.674261] PGD 8451a067 PUD 84527067 PMD 0 [ 224.676056] Oops: 0002 [#1] PREEMPT SMP [ 224.677810] Modules linked in: algif_skcipher af_alg ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6_tables overlay xt_addrtype xt_conntrack xt_CHECKSUM ax88179_178a iptable_mangle usbnet ipt_MASQUERADE rtsx_usb_ms nf_nat_masquerade_ipv4 aufs iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 mii memstick nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc binfmt_misc iptable_filter ip_tables x_tables bnep drbg ansi_cprng dm_crypt nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul snd_soc_rt5640 glue_helper ablk_helper snd_soc_rl6231 cryptd snd_soc_core input_leds serio_raw hid_sensor_rotation snd_compress ac97_bus snd_pcm_dmaengine snd_seq_midi snd_seq_midi_event snd_hda_codec_realtek [ 224.683606] hid_sensor_incl_3d uvcvideo videobuf2_vmalloc snd_hda_codec_generic hid_sensor_als videobuf2_memops hid_sensor_magn_3d snd_hda_codec_hdmi hid_sensor_accel_3d hid_sensor_gyro_3d btusb hid_sensor_trigger btrtl industrialio_triggered_buffer btbcm snd_rawmidi joydev btintel videobuf2_core kfifo_buf snd_hda_intel industrialio snd_hda_codec hid_sensor_iio_common v4l2_common videodev snd_hda_core hid_multitouch snd_hwdep media bluetooth mei_me snd_seq lpc_ich mei snd_pcm snd_seq_device dw_dmac dw_dmac_core snd_timer snd soundcore ideapad_laptop sparse_keymap 8250_dw i2c_designware_platform mac_hid spi_pxa2xx_platform soc_button_array i2c_designware_core snd_soc_sst_acpi kvm_intel kvm parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_sensor_custom hid_sensor_hub uas usb_storage bcache [ 224.689905] hid_generic usbhid rtsx_usb_sdmmc rtsx_usb i915 i2c_algo_bit drm_kms_helper drm psmouse ahci libahci sdhci_acpi sdhci video i2c_hid hid [ 224.694241] CPU: 1 PID: 2915 Comm: debconf-set-sel Tainted: GW 4.2.0-7-lowlatency #7-Ubuntu [ 224.696433] Hardware name: LENOVO 20344/INVALID, BIOS 96CN25WW(V1.11) 07/09/2014 [ 224.698641] task: 880099723800 ti: 88008451 task.ti: 88008451 [ 224.700843] RIP: 0010:[] [] btrfs_sync_file+0xc1/0x360 [btrfs] [ 224.703068] RSP: 0018:880084513e38 EFLAGS: 00010292 [ 224.705272] RAX: 880099723800 RBX: 880159625400 RCX: [ 224.707505] RDX: RSI: RDI: 880098237a58 [ 224.709733] RBP: 880084513eb8 R08: 0001 R09: 01f94ff0 [ 224.711962] R10: 009c R11: 0246 R12: 880098237a58 [ 224.714191] R13: 8800982379b0 R14: R15: [ 224.716431] FS: 7fdffa459700() GS:88015f24() knlGS: [ 224.718656] CS: 0010 DS: ES: CR0: 80050033 [ 224.720882] CR2: 0334 CR3: 8456a000 CR4: 001406e0 [ 224.723098] Stack: [ 224.725289] 880159625410 00020001 8000 8800981d7d80 [ 224.727494] 7fff 88009a803000 [ 224.729686] 1144 0002 880084513ea8 880159625400 [ 224.731860] Call Trace: [ 224.733994] [] vfs_fsync_range+0x4b/0xb0 [ 224.736142] [] do_fsync+0x3d/0x70 [ 224.738275] [] SyS_fsync+0x10/0x20 [ 224.740379] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 224.742476] Code: eb a1 e8 37 da cf c0 eb 9a 48 8b 45 a0 4c 8b 75 a8 4d 8d a5 a8 00 00 00 4c 89 e7 4c 29 f0 48 83 c0 01 48 89 45 90 e8 0f d4 4b c1 41
[Bug 1496433] [NEW] Error in i915 driver
Public bug reported: The 7th of september I lost my Xorg display on wily. I was always in failsafe mode. I still could get openbox to run, which was still loading i915, but didn't consume any 3D/advanced instruction I thinK. I didn't got too much time to go beyond. As I got also a btrfs kernel dump message, so I checked my ram at least with memtest86+, all was OK. Reverting to vivid allowed me to be back on unity. Wily-amd64, kernel 4.2.0.7-7-generic/low-latency Here are the traces I got: [ 22.335530] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) [ 22.335535] [ cut here ] [ 22.335562] WARNING: CPU: 0 PID: 2190 at /build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 check_crtc_state+0x2c5/0x440 [i915]() [ 22.335564] pipe state doesn't match! [ 22.335566] Modules linked in: ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6_tables overlay xt_addrtype xt_conntrack xt_CHECKSUM ax88179_178a iptable_mangle usbnet ipt_MASQUERADE rtsx_usb_ms nf_nat_masquerade_ipv4 aufs iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 mii memstick nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc binfmt_misc iptable_filter ip_tables x_tables bnep drbg ansi_cprng dm_crypt nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul snd_soc_rt5640 glue_helper ablk_helper snd_soc_rl6231 cryptd snd_soc_core input_leds serio_raw hid_sensor_rotation snd_compress ac97_bus snd_pcm_dmaengine snd_seq_midi snd_seq_midi_event snd_hda_codec_realtek hid_sensor_incl_3d [ 22.335625] uvcvideo videobuf2_vmalloc snd_hda_codec_generic hid_sensor_als videobuf2_memops hid_sensor_magn_3d snd_hda_codec_hdmi hid_sensor_accel_3d hid_sensor_gyro_3d btusb hid_sensor_trigger btrtl industrialio_triggered_buffer btbcm snd_rawmidi joydev btintel videobuf2_core kfifo_buf snd_hda_intel industrialio snd_hda_codec hid_sensor_iio_common v4l2_common videodev snd_hda_core hid_multitouch snd_hwdep media bluetooth mei_me snd_seq lpc_ich mei snd_pcm snd_seq_device dw_dmac dw_dmac_core snd_timer snd soundcore ideapad_laptop sparse_keymap 8250_dw i2c_designware_platform mac_hid spi_pxa2xx_platform soc_button_array i2c_designware_core snd_soc_sst_acpi kvm_intel kvm parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_sensor_custom hid_sensor_hub uas usb_storage bcache hid_generic usbhid [ 22.335682] rtsx_usb_sdmmc rtsx_usb i915 i2c_algo_bit drm_kms_helper drm psmouse ahci libahci sdhci_acpi sdhci video i2c_hid hid [ 22.335698] CPU: 0 PID: 2190 Comm: Xorg Tainted: GW 4.2.0-7-lowlatency #7-Ubuntu [ 22.335700] Hardware name: LENOVO 20344/INVALID, BIOS 96CN25WW(V1.11) 07/09/2014 [ 22.335703] c02081e8 8800995c77e8 817bdf25 [ 22.335708] 8800995c7838 8800995c7828 81078016 8800995c7858 [ 22.335712] 8800995c78c0 880035571000 0001 880035571350 [ 22.335717] Call Trace: [ 22.335724] [] dump_stack+0x4c/0x6e [ 22.335729] [] warn_slowpath_common+0x86/0xc0 [ 22.335734] [] warn_slowpath_fmt+0x46/0x50 [ 22.335758] [] ? intel_pipe_config_compare+0xb31/0xc60 [i915] [ 22.335781] [] check_crtc_state+0x2c5/0x440 [i915] [ 22.335809] [] intel_modeset_check_state+0x20e/0x6b0 [i915] [ 22.335834] [] intel_crtc_set_config+0x4c7/0x580 [i915] [ 22.335852] [] drm_mode_set_config_internal+0x66/0x100 [drm] [ 22.335870] [] drm_mode_setcrtc+0x3a8/0x4c0 [drm] [ 22.335883] [] drm_ioctl+0x125/0x610 [drm] [ 22.335898] [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [ 22.335903] [] do_vfs_ioctl+0x285/0x460 [ 22.335908] [] ? recalc_sigpending+0x1f/0x60 [ 22.335912] [] ? __fget+0x77/0xb0 [ 22.335916] [] SyS_ioctl+0x79/0x90 [ 22.335921] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 22.335924] ---[ end trace 7e8588f0d9eb10f9 ]--- ** Affects: linux (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/1496433 Title: Error in i915 driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219752] Re: FFe: Please merge cifs-utils 6.4-1 from Debian testing/unstable to Ubuntu 14.10 - Ubuntu Utopic still has buggy 1.5 year old 6.0 release :(
** Changed in: cifs-utils (Ubuntu) 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/1219752 Title: FFe: Please merge cifs-utils 6.4-1 from Debian testing/unstable to Ubuntu 14.10 - Ubuntu Utopic still has buggy 1.5 year old 6.0 release :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1219752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227195] Re: new upstream release
** Changed in: amavisd-new (Ubuntu) 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/1227195 Title: new upstream release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1227195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423498] Re: FTP upload causes squid hang
** Changed in: squid3 (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423498 Title: FTP upload causes squid hang To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1423498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227195] Re: new upstream release
** Changed in: amavisd-new (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1227195 Title: new upstream release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1227195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454719] Re: docker.io update to 1.6.2
Hello, Found an upgrade bug when a docker container is running and busy while docker.io is upgrading, where docker/systemd left over some scope files blocking the container to start again. Need a fix, so tagging failed. ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454719 Title: docker.io update to 1.6.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1454719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466550] Re: docker lxc driver fails
** Description changed: [Impact] * This bug breaks lxc engine support of docker. * There is an upstreamed fix issued to manage newer version of LXC, which enable lxc.autodev by default. * patch is lxc.autodev-support.patch that is a cherry-pick of https://github.com/docker/docker/commit/6089e679a2fb2494fd3e599a9eab9327e6a509fc [Test Case] * To reproduce the bug: on a fresh vivid server: sudo apt-get install -y lxc docker.io edit /dev/default/docker: DOCKER_OPTS="-e lxc" restart docker-daemon service: sudo service docker start (see bug: LP: #1459916) ensure docker is running with the correct options with ps or docker: - sudo ps -ef | grep docker + sudo ps -ef | grep docker root 20458 1 0 07:48 ?00:00:19 /usr/bin/docker -d -H fd:// -e lxc - sudo docker info | grep lxc: - Execution Driver: lxc-1.1.2 - WARNING: No swap limit support + sudo docker info | grep lxc: + Execution Driver: lxc-1.1.2 + WARNING: No swap limit support pull a docker image (amd64): docker pull ubuntu:latest + after download is successfull: it will fail to start like reported: + ubuntu@vd2:~$ sudo docker run -it ubuntu:latest /bin/bash Unable to find image 'ubuntu:latest' locally Pulling repository ubuntu 6d4946999d4f: Download complete 428b411c28f0: Download complete 435050075b3f: Download complete 9fd3c8c9af32: Download complete Status: Image is up to date for ubuntu:latest lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. FATA[0015] Error response from daemon: Cannot start container 5b7ee6181a49a1fa5c6ac47eab666ea05611f6f7f8b3610bfacb9a150c966501: Container is not running ( for bandwidth consideration, you might want to save the downloaded image for other testing, sudo docker images sudo docker save -o ubuntu_latest.tar ubuntu:latest bzip2 ubuntu_latest.tar, to reload it on an other sytem: sudo docker load -i ubuntu_latest.tar.bz2 sudo run -it ubuntu:latest /bin/bash ) With fix: Now, restart a fresh vivid server, install the new proposed package sudo apt-get install -y lxc - sudo service docker stop - edit /etc/default/docker (DOCKER_OPTS="-e lxc") + + sudo service docker stop + edit /etc/default/docker (DOCKER_OPTS="-e lxc") sudo service docker start + ensure docker is running with the correct options with ps or docker: - sudo ps -ef | grep docker - root 20458 1 0 07:48 ?00:00:19 /usr/bin/docker -d -H fd:// -e lxc - sudo docker info | grep lxc: - Execution Driver: lxc-1.1.2 - WARNING: No swap limit support + sudo ps -ef | grep docker + root 20458 1 0 07:48 ?00:00:19 /usr/bin/docker -d -H fd:// -e lxc + + sudo docker info | grep lxc: + Execution Driver: lxc-1.1.2 + WARNING: No swap limit support sudo docker run -it ubuntu:latest /bin/bash Unable to find image 'ubuntu:latest' locally latest: Pulling from ubuntu 428b411c28f0: Already exists 435050075b3f: Already exists 9fd3c8c9af32: Already exists 6d4946999d4f: Already exists Digest: sha256:45e42b43f2ff4850dcf52960ee89c21cda79ec657302d36f07d880215dd9 Status: Image is up to date for ubuntu:latest root@e433f427c0f2:/# lsb_release -c Codename: trusty root@e433f427c0f2:/# exit [Original Description] Start docker daemon with "-e lxc" option. pulll & run ubuntu image. Expect to get a bash prompt, instead I get: $ docker run -ti ubuntu bash lxc-start: conf.c: mount_entry: 1711 No such file or directory - failed to mount '/dev/pts/5' on '/usr/lib/x86_64-linux-gnu/lxc//dev/console' lxc-start: conf.c: lxc_setup: 3831 failed to setup the mount entries for '9b33b115f6ba2f4882f79745f1c8397b4f57ef3547fea30cfb01b3d03acd2f6c' lxc-start: start.c: do_start: 699 failed to setup the container lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2 lxc-start: start.c: __lxc_start: 1164 failed to spawn '9b33b115f6ba2f4882f79745f1c8397b4f57ef3547fea30cfb01b3d03acd2f6c' lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. ** Description changed: [Impact] * This bug breaks lxc engine support of docker. * There is an upstreamed fix issued to manage newer version of LXC, which enable lxc.autodev by default. * patch is lxc.autodev-support.patch that is a cherry-pick of https://github.com/docker/docker/commit/6089e679a2fb2494fd3e5
[Bug 1466550] Re: docker lxc driver fails
** Description changed: [Impact] - * This bug breaks lxc engine support of docker. + * This bug breaks lxc engine support of docker. - * There is an upstreamed fix issued to manage newer version of LXC, + * There is an upstreamed fix issued to manage newer version of LXC, which enable lxc.autodev by default. - * patch is lxc.autodev-support.patch that is a cherry-pick of + * patch is lxc.autodev-support.patch that is a cherry-pick of https://github.com/docker/docker/commit/6089e679a2fb2494fd3e599a9eab9327e6a509fc [Test Case] - * To reproduce the bug: + * To reproduce the bug: - on a fresh vivid server: - sudo apt-get install -y lxc docker.io - edit /dev/default/docker: - DOCKER_OPTS="-e lxc" - - restart docker-daemon service: - sudo service docker start (see bug: LP: #1459916) + on a fresh vivid server: + sudo apt-get install -y lxc docker.io + edit /dev/default/docker: + DOCKER_OPTS="-e lxc" - ensure docker is running with the correct options: - root 20458 1 0 07:48 ?00:00:19 /usr/bin/docker -d -H fd:// -e lxc + restart docker-daemon service: + sudo service docker start (see bug: LP: #1459916) - pull a docker image (amd64): - docker pull ubuntu:latest - after download is successfull: - it will fail to start like reported: - ubuntu@vd2:~$ sudo docker run -it ubuntu:latest /bin/bash - Unable to find image 'ubuntu:latest' locally - Pulling repository ubuntu - 6d4946999d4f: Download complete - 428b411c28f0: Download complete - 435050075b3f: Download complete - 9fd3c8c9af32: Download complete - Status: Image is up to date for ubuntu:latest - lxc-start: lxc_start.c: main: 344 The container failed to start. - lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. - lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. - FATA[0015] Error response from daemon: Cannot start container 5b7ee6181a49a1fa5c6ac47eab666ea05611f6f7f8b3610bfacb9a150c966501: Container is not running + ensure docker is running with the correct options with ps or docker: + sudo ps -ef | grep docker + root 20458 1 0 07:48 ?00:00:19 /usr/bin/docker -d -H fd:// -e lxc + sudo docker info | grep lxc: + Execution Driver: lxc-1.1.2 + WARNING: No swap limit support - ( for bandwidth consideration, you might want to save the downloaded image for other testing, - sudo docker images - sudo docker save -o ubuntu_latest.tar ubuntu:latest - bzip2 ubuntu_latest.tar, + pull a docker image (amd64): + docker pull ubuntu:latest + after download is successfull: + it will fail to start like reported: + ubuntu@vd2:~$ sudo docker run -it ubuntu:latest /bin/bash + Unable to find image 'ubuntu:latest' locally + Pulling repository ubuntu + 6d4946999d4f: Download complete + 428b411c28f0: Download complete + 435050075b3f: Download complete + 9fd3c8c9af32: Download complete + Status: Image is up to date for ubuntu:latest + lxc-start: lxc_start.c: main: 344 The container failed to start. + lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. + lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. + FATA[0015] Error response from daemon: Cannot start container 5b7ee6181a49a1fa5c6ac47eab666ea05611f6f7f8b3610bfacb9a150c966501: Container is not running - to reload it on an other sytem: - sudo docker load -i ubuntu_latest.tar.bz2 - sudo run -it ubuntu:latest /bin/bash + ( for bandwidth consideration, you might want to save the downloaded image for other testing, + sudo docker images + sudo docker save -o ubuntu_latest.tar ubuntu:latest + bzip2 ubuntu_latest.tar, + + to reload it on an other sytem: + sudo docker load -i ubuntu_latest.tar.bz2 + sudo run -it ubuntu:latest /bin/bash ) With fix: - Now, restart a fresh vivid server, - install the new proposed package - sudo apt-get install -y lxc - sudo service docker stop - edit /etc/default/docker (DOCKER_OPTS="-e lxc") - sudo service docker start - sudo docker run -it ubuntu:latest /bin/bash - Unable to find image 'ubuntu:latest' locally - latest: Pulling from ubuntu - 428b411c28f0: Already exists - 435050075b3f: Already exists - 9fd3c8c9af32: Already exists - 6d4946999d4f: Already exists - Digest: sha256:45e42b43f2ff4850dcf52960ee89c21cda79ec657302d36f07d880215dd9 - Status: Image is up to date for ubuntu:latest - root@e433f427c0f2:/# lsb_release -c - Codename: trusty - root@e433f427c0f2:/# exit + Now, restart a fresh vivid server, + install the new proposed package + sudo apt-get install -y lxc + sudo service docker stop + edit /etc/default/docker (DOCK
[Bug 1459916] Re: Doesn't start after installation
Here is the diff for the docker.io.postinst between vivid and wily: http://paste.ubuntu.com/11792608/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459916 Title: Doesn't start after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1459916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466550] Re: docker lxc driver fails
** Description changed: + [Impact] + + * This bug breaks lxc engine support of docker. + + * There is an upstreamed fix issued to manage newer version of LXC, + which enable lxc.autodev by default. + + * patch is lxc.autodev-support.patch that is a cherry-pick of + https://github.com/docker/docker/commit/6089e679a2fb2494fd3e599a9eab9327e6a509fc + + [Test Case] + + * To reproduce the bug: + + on a fresh vivid server: + sudo apt-get install -y lxc docker.io + edit /dev/default/docker: + DOCKER_OPTS="-e lxc" + + restart docker-daemon service: + sudo service docker start (see bug: LP: #1459916) + + ensure docker is running with the correct options: + root 20458 1 0 07:48 ?00:00:19 /usr/bin/docker -d -H fd:// -e lxc + + pull a docker image (amd64): + docker pull ubuntu:latest + after download is successfull: + it will fail to start like reported: + ubuntu@vd2:~$ sudo docker run -it ubuntu:latest /bin/bash + Unable to find image 'ubuntu:latest' locally + Pulling repository ubuntu + 6d4946999d4f: Download complete + 428b411c28f0: Download complete + 435050075b3f: Download complete + 9fd3c8c9af32: Download complete + Status: Image is up to date for ubuntu:latest + lxc-start: lxc_start.c: main: 344 The container failed to start. + lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. + lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. + FATA[0015] Error response from daemon: Cannot start container 5b7ee6181a49a1fa5c6ac47eab666ea05611f6f7f8b3610bfacb9a150c966501: Container is not running + + ( for bandwidth consideration, you might want to save the downloaded image for other testing, + sudo docker images + sudo docker save -o ubuntu_latest.tar ubuntu:latest + bzip2 ubuntu_latest.tar, + + to reload it on an other sytem: + sudo docker load -i ubuntu_latest.tar.bz2 + sudo run -it ubuntu:latest /bin/bash + ) + + With fix: + Now, restart a fresh vivid server, + install the new proposed package + sudo apt-get install -y lxc + sudo service docker stop + edit /etc/default/docker (DOCKER_OPTS="-e lxc") + sudo service docker start + sudo docker run -it ubuntu:latest /bin/bash + Unable to find image 'ubuntu:latest' locally + latest: Pulling from ubuntu + 428b411c28f0: Already exists + 435050075b3f: Already exists + 9fd3c8c9af32: Already exists + 6d4946999d4f: Already exists + Digest: sha256:45e42b43f2ff4850dcf52960ee89c21cda79ec657302d36f07d880215dd9 + Status: Image is up to date for ubuntu:latest + root@e433f427c0f2:/# lsb_release -c + Codename: trusty + root@e433f427c0f2:/# exit + + + + [Original Description] + Start docker daemon with "-e lxc" option. pulll & run ubuntu image. Expect to get a bash prompt, instead I get: $ docker run -ti ubuntu bash lxc-start: conf.c: mount_entry: 1711 No such file or directory - failed to mount '/dev/pts/5' on '/usr/lib/x86_64-linux-gnu/lxc//dev/console' lxc-start: conf.c: lxc_setup: 3831 failed to setup the mount entries for '9b33b115f6ba2f4882f79745f1c8397b4f57ef3547fea30cfb01b3d03acd2f6c' lxc-start: start.c: do_start: 699 failed to setup the container lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2 lxc-start: start.c: __lxc_start: 1164 failed to spawn '9b33b115f6ba2f4882f79745f1c8397b4f57ef3547fea30cfb01b3d03acd2f6c' lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466550 Title: docker lxc driver fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1466550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459916] Re: Doesn't start after installation
** Description changed: + [SRU Description] + + [Impact] + This bug affect the start of the docker daemon, as it isn't started after installation. + Upgrade is broken also when using a direct backport from wily. + + Some ajustment had to be done in docker.io.postinst to correct this + upgrade behavior. + + + [Test Case] + start a fresh installed vivid + sudo apt-get update && sudo apt-get install docker.io + sudo systemctl status docker.socket show that the daemon is not started. + + Actual results: + ● docker.socket - Docker Socket for the API +Loaded: loaded (/lib/systemd/system/docker.socket; enabled; vendor reset:enabled) +Active: inactive (dead) +Listen: /var/run/docker.sock (Stream) + + To test this proposed package + you can on a fresh installation each time: + + 1-Install the proposed package directly, and check that docker.socket + service is active + + sudo systemctl status docker.socket + Expected results: + ● docker.socket - Docker Socket for the API +Loaded: loaded (/lib/systemd/system/docker.socket; enabled; vendor preset: enabled) +Active: active (running) since Fri 2015-06-26 16:05:46 UTC; 19s ago +Listen: /var/run/docker.sock (Stream) + + sudo docker version + Expected results: + Client version: 1.6.2 + Client API version: 1.18 + Go version (client): go1.3.3 + Git commit (client): 7c8fca2 + OS/Arch (client): linux/amd64 + Server version: 1.6.2 + Server API version: 1.18 + Go version (server): go1.3.3 + Git commit (server): 7c8fca2 + OS/Arch (server): linux/amd64 + + 2-On a fresh vivid install, install docker-1.5.0, + sudo docker version: + expected results: + Client version: 1.5.0 + Client API version: 1.17 + Go version (client): go1.3.3 + Git commit (client): a8a31ef + OS/Arch (client): linux/amd64 + FATA[] Get http:///var/run/docker.sock/v1.17/version: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS? + + then upgrade to proposed package, and check if docker service is + active. + + sudo systemctl status docker.socket, + expected results: + ● docker.socket - Docker Socket for the API + Loaded: loaded (/lib/systemd/system/docker.socket; enabled; vendor preset: enabled) + Active: active (running) since Fri 2015-06-26 16:15:18 UTC; 23s ago + Listen: /var/run/docker.sock (Stream) + + sudo docker version; + Expected results: + Client version: 1.6.2 + Client API version: 1.18 + Go version (client): go1.3.3 + Git commit (client): 7c8fca2 + OS/Arch (client): linux/amd64 + Server version: 1.6.2 + Server API version: 1.18 + Go version (server): go1.3.3 + Git commit (server): 7c8fca2 + OS/Arch (server): linux/amd64 + + 3-Install docker-1.5.0, + start service manually: + sudo systemctl start docker.socket && sudo systemctl status docker.socket + Expected results: + ● docker.socket - Docker Socket for the API +Loaded: loaded (/lib/systemd/system/docker.socket; enabled; vendor preset: enabled) +Active: active (listening) since Fri 2015-06-26 16:20:41 UTC; 7ms ago +Listen: /var/run/docker.sock (Stream) + + then upgrade to proposed package, and check if docker service is + active. + + sudo systemctl status docker.socket, + expected results: + ● docker.socket - Docker Socket for the API + Loaded: loaded (/lib/systemd/system/docker.socket; enabled; vendor preset: enabled) + Active: active (running) since Fri 2015-06-26 16:15:18 UTC; 23s ago + Listen: /var/run/docker.sock (Stream) + + sudo docker version; + Expected results: + Client version: 1.6.2 + Client API version: 1.18 + Go version (client): go1.3.3 + Git commit (client): 7c8fca2 + OS/Arch (client): linux/amd64 + Server version: 1.6.2 + Server API version: 1.18 + Go version (server): go1.3.3 + Git commit (server): 7c8fca2 + OS/Arch (server): linux/amd64 + + [Regression Potential] + This fix reset the saved state of systemd docker.service and docker.socket units, + so it may affect a user that has installed docker.io (1.5.0~dfsg1-1ubuntu2), + then rebooted or manually started the service, then has manually shutdown the service. + The last state will be reset. + + It is worth noting than since docker.io-1.6.0~rc4~dfsg1-1, + the docker.service is marked on-boot, so docker.socket is not so usefull anymore. + It is retained for minimizing divergence with upstream. + + + [Original Bug Description] + I need to manually invoke "systemctl start docker.socket". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459916 Title: Doesn't start after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io
[Bug 1466550] Re: docker lxc driver fails
** Changed in: docker.io (Ubuntu Vivid) Status: New => In Progress ** Changed in: docker.io (Ubuntu Vivid) Assignee: (unassigned) => Kick In (kick-d) ** Changed in: docker.io (Ubuntu Vivid) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466550 Title: docker lxc driver fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1466550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467847] [NEW] sbuild always purge session even if set to never.
Public bug reported: Hi, sbuild: 0.65.2-1ubuntu2 I'm running a wily instance, I installed and configure sbuild to retrieve wily chroots. I ran sbuild -Ad and the build was unsuccessfull, but schroot -al didn't list any session, it was removed. I then checked my .sbuildrc, and it was set to: $purge_build_directory = 'successful'; $purge_session = 'successful'; $purge_build_deps = 'successful'; I changed it to: $purge_build_directory = 'never'; $purge_session = 'never'; $purge_build_deps = 'never'; launched a watch ls -l /var/lib/schroot/session and re-ran sbuild, I saw session being well created in /var/lib/schroot/session, but at the end of the process it got automatically purged. ** Affects: sbuild (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, sbuild: 0.65.2-1ubuntu2 I'm running a wily instance, I installed and configure sbuild to retrieve wily chroots. I ran sbuild -Ad and the build was unsuccessfull, but schroot -al didn't list any session, it was removed. I then checked my .sbuildrc, and it was set to: $purge_build_directory = 'successful'; $purge_session = 'successful'; $purge_build_deps = 'successful'; I changed it to: $purge_build_directory = 'never'; $purge_session = 'never'; $purge_build_deps = 'never'; launch a watch ls -l /var/lib/schroot/session and re-ran sbuild, I saw session being well created in /var/lib/schroot/session, but at the - end of the proposed it got automatically purged. + end of the process it got automatically purged. ** Description changed: Hi, sbuild: 0.65.2-1ubuntu2 I'm running a wily instance, I installed and configure sbuild to retrieve wily chroots. I ran sbuild -Ad and the build was unsuccessfull, but schroot -al didn't list any session, it was removed. I then checked my .sbuildrc, and it was set to: $purge_build_directory = 'successful'; $purge_session = 'successful'; $purge_build_deps = 'successful'; I changed it to: $purge_build_directory = 'never'; $purge_session = 'never'; $purge_build_deps = 'never'; - launch a watch ls -l /var/lib/schroot/session + launched a watch ls -l /var/lib/schroot/session and re-ran sbuild, I saw session being well created in /var/lib/schroot/session, but at the end of the process it got automatically purged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467847 Title: sbuild always purge session even if set to never. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/1467847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466550] Re: docker lxc driver fails
Sorry I missread my syslog, apparmor denials were not related to docker. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466550 Title: docker lxc driver fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1466550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466550] Re: docker lxc driver fails
I could reproduce on a vivid host and docker-1.6.2. You are getting Apparmor denials. Check syslog cat /var/log/syslog | grep DENIED -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466550 Title: docker lxc driver fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1466550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466550] Re: docker lxc driver fails
HI, Can you specify which ubuntu release and which version of docker? lsb_release -c dpkg -l | grep docker.io Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466550 Title: docker lxc driver fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1466550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459591] [NEW] Keyboard stays US after french selection in Try mode
Public bug reported: Hi, When starting the Vivid 15.04 livecd (on a usb key), I don't change keymap at grub time, just let it boot, then it ask me if I want to install or to try ubuntu. If I select Try ubuntu, after selecting French, it still keep using US keymap. I need to change the Text Entry Setting to get it work as expected. I think it must be automatically switched to default country keymap. If selecting install, the text entry remains EN-US, but ubiquity change its own keymap, and the keyboard works as expected inside ubiquity after keyboard selection. If selecting french language at grub time and select 'try ubuntu', keyboard is correctly setup. ** Affects: casper (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, - When starting the livecd (on a usb key), I don't change keymap at grub - time, just let it boot, then it ask me if I want to install or to try - ubuntu. If I select Try ubuntu, after selecting French, it still keep - using US keymap. I need to change the Text Entry Setting. + When starting the Vivid 15.04 livecd (on a usb key), I don't change + keymap at grub time, just let it boot, then it ask me if I want to + install or to try ubuntu. If I select Try ubuntu, after selecting + French, it still keep using US keymap. I need to change the Text Entry + Setting to get it work as expected. I think it must be automatically switched to default country keymap. If selecting install, the text entry remains EN-US, but ubiquity change - its own keymap, and the keyboard works as expected inside ubiquity. + its own keymap, and the keyboard works as expected inside ubiquity after + keyboard selection. If selecting french language at grub time and select 'try ubuntu', keyboard is correctly setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459591 Title: Keyboard stays US after french selection in Try mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1459591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
Thanks Adam for the Arm64 patch! The systemd patch was already applied as it was coming from docker 1.3.3 ubuntu7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
i386 build log, it was successfull, but I didn't ran smoke tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
** Attachment added: "docker.io_1.5.0~dfsg1-1ubuntu1_i386.build" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4369876/+files/docker.io_1.5.0%7Edfsg1-1ubuntu1_i386.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
ppc64el build log, it was successfull, and smoke test was also susccessfull. smoke test was: sudo docker run -it jjacobso/ubuntucore-ppc64le /bin/bash and inside container: apt-get update && apt-get -y upgrade ** Attachment added: "docker.io_1.5.0~dfsg1-1ubuntu1_ppc64el.build" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4369873/+files/docker.io_1.5.0%7Edfsg1-1ubuntu1_ppc64el.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
arm64 build log, it was successfull, and smoke test was also susccessfull. smoke test was: sudo docker run -it ericvh/arm64-ubuntu and inside container: apt-get update && apt-get -y upgrade ** Attachment added: "docker.io_1.5.0~dfsg1-1ubuntu1_arm64.build" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4369874/+files/docker.io_1.5.0%7Edfsg1-1ubuntu1_arm64.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
amd64 build log, it was successfull, and smoke test was also susccessfull. smoke test was: sudo docker run -it ubuntu and inside container: apt-get update && apt-get -y upgrade ** Attachment added: "docker.io_1.5.0~dfsg1-1ubuntu1_amd64.build" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4369875/+files/docker.io_1.5.0%7Edfsg1-1ubuntu1_amd64.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
Here is the new debdiff, and the build logs for all archs. ** Patch added: "debdiff.patch" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4369871/+files/debdiff.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
armhf build log, it was successfull, and smoke test was also susccessfull. smoke test was: sudo docker run -it armbuild/ubuntu and inside container: apt-get update && apt-get -y upgrade ** Attachment added: "docker.io_1.5.0~dfsg1-1ubuntu1_armhf-20150408-2111.build" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4369872/+files/docker.io_1.5.0%7Edfsg1-1ubuntu1_armhf-20150408-2111.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
New debdiff ** Patch added: "The new debdiff with the requested modifications" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4368387/+files/merge.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
docker.io_1.5.0~dfsg1-1ubuntu1_arm64-20150331-0449.build is a gccgo build sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
Raw dynbinary build (golang): ** Attachment added: "docker.io_1.5.0~dfsg1-1ubuntu1_arm64-20150331-0449.build" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4364431/+files/docker.io_1.5.0%7Edfsg1-1ubuntu1_arm64-20150331-0449.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
Dynbinary arm64 build log (golang) ** Attachment added: "docker.io_1.5.0~dfsg1-1ubuntu1_arm64-20150331-0413.build" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4364432/+files/docker.io_1.5.0%7Edfsg1-1ubuntu1_arm64-20150331-0413.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
golang-fsnotify-dev | 1.1.0-1 | experimental | all golang-fsnotify | 1.1.0-1 | experimental | source golang-logrus | 0.7.1-1 | sid | source golang-logrus-dev | 0.7.1-1 | sid | all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
Compilers versions used: i386: golang (2:1.3.3-1ubuntu4) amd64: golang (2:1.3.3-1ubuntu4) armhf: golang (2:1.3.3-1ubuntu4) pp64el: gccgo-5 (5-20150401-0ubuntu1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
amd64 build log ** Attachment added: "build-amd64.log" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4364320/+files/build-amd64.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
build-i386 build log ** Attachment added: "build-i386.log" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4364321/+files/build-i386.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
Here is the deb diff, and build logs of the proposed docker-1.5.0~dfsg1-1ubuntu1 proposed package. This has been built successfully on amd64, ppc64el, armhf (C1 Cores) and i386. This has failed on arm64, but it was reported not working before, support has been dropped in 1.3.3~dfsg1-2ubuntu5 with the following comment: d/control: Drop arm64 architecture for now as its going to require further work in the dependency chain. This has been tested on amd64, ppc64el, and armhf. Tests were just a docker daemon started, and a docker ubuntu container created, then ran apt-get update && apt-get -y upgrade inside the container and exit if everything seems ok. armhf, amd64 and i386 built with: golang ppc64el built with: gccgo ** Patch added: "Debdiff between debian docker.io 1.5.0 experimental and proposed package" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4364309/+files/merge.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
build log for armhf ** Attachment added: "docker.io_1.5.0~dfsg1-1ubuntu1_armhf-20150402-0919.build" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4364310/+files/docker.io_1.5.0%7Edfsg1-1ubuntu1_armhf-20150402-0919.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to 1.5 in Vivid
ppc64el build log ** Attachment added: "docker.io_1.5.0~dfsg1-1ubuntu1_ppc64el-20150401-1801.build" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+attachment/4364311/+files/docker.io_1.5.0%7Edfsg1-1ubuntu1_ppc64el-20150401-1801.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to 1.5 in Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430760] Re: [FFE] Bump up docker.io version to atleast 1.4.1 for Vivid ppc64el
To release-team: I would like to warn you about this incoming Feature Freeze Exception Request, whilst the work is still ongoing. ** Summary changed: - Bump up docker.io version to atleast 1.4.1 for Vivid ppc64el + [FFE] Bump up docker.io version to atleast 1.4.1 for Vivid ppc64el -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430760 Title: [FFE] Bump up docker.io version to atleast 1.4.1 for Vivid ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1430760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412839] Re: Docker stop command can't be issued, kill is denied
After dicussion with tyhicks, it seems that the docker-default profile is the guilty, particularly this two lines: ptrace (readby, tracedby) peer="docker_docker_1.3.*", signal (receive) peer="docker_docker_1.3.*", when upgrading to docker-1.4.* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412839 Title: Docker stop command can't be issued, kill is denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu-snappy/+bug/1412839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412830] Re: [AHBL] spamassassin is returning false positives by default
** Changed in: spamassassin (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412830 Title: [AHBL] spamassassin is returning false positives by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1412830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412839] [NEW] Docker stop command can't be issued, kill is denied
Public bug reported: On a snappy instance, install docker (here docker-1.4.1), then docker run -it ubuntu in the docker ubuntu just exit next do docker run -t ubuntu now on an other ssh window, just issue docker ps locate the docker container still running and issue docker stop $id you cannot stop the container, if you type exit in the container, it is still running, and your terminal is locked. apparmor message is: https://pastebin.canonical.com/123788/ audit: type=1400 audit(1421766814.720:27): apparmor="DENIED" operation="signal" profile="docker-default" pid=1147 comm="docker" requested_mask="receive" denied_mask="receive" signal=kill peer="docker_docker_1.4.1.001" ** Affects: apparmor-easyprof-ubuntu-snappy (Ubuntu) Importance: Undecided Assignee: Jamie Strandboge (jdstrand) Status: New ** Changed in: apparmor-easyprof-ubuntu-snappy (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412839 Title: Docker stop command can't be issued, kill is denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu-snappy/+bug/1412839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1408943] [NEW] nvidia-331-updates-uvm 331.113-0ubuntu2: nvidia-331-updates-uvm kernel module failed to build
Public bug reported: Auto apport, don't know what caused that. Can help if needed. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: nvidia-331-updates-uvm 331.113-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 3.18.0-8-generic Date: Fri Jan 9 10:20:10 2015 InstallationDate: Installed on 2014-12-30 (9 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141229) PackageVersion: 331.113-0ubuntu2 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.113-0ubuntu2: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1408943 Title: nvidia-331-updates-uvm 331.113-0ubuntu2: nvidia-331-updates-uvm kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1408943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
Hi, I can confirm that it is often the case, and that it previously causes me headaches at installing debian/ubuntu distro via pxe on vlan tagged networks . Those where use of native vlan is reserved/forbiddenand where you must pass many mutualised switches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382054 Title: Add support for configuring VLAN interfaces in the initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377142] Re: Bcache doesn't allow full unregistering without rebooting
Thanks, I didn't wrote to /sys/block/bcache0/bcache/stop, I missed this as I was only looking in /dev/bcache* and in /sys/fs/bcache; which explains why I was left with an used device. I agree that the interface is not very user-fiendly, we may need to improve the bcache-tools command to simplify this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377142 Title: Bcache doesn't allow full unregistering without rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377130] Re: Crash at creation of bcache if caching size > backing size
Yes you can get rid of bcache0, but you can't re-use the device for anything unless you reboot ( re bcache or just plain fdisk/parted ). In fact whether you unmount before stopping the bcache or not doesn't change the behaviour. I did that this way in the description, to show the process. You just stop the caching device with the echo 1 > ... But, the backing is still in use and you have no control over it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377130 Title: Crash at creation of bcache if caching size > backing size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1377142] Re: Bcache doesn't allow full unregistering without rebooting
In fact whether you unmount before stopping the bcache or not doesn't change the behaviour. I did that this way in the description, to show the process. You just stop the caching device with the echo 1 > ... But, the backing is still in use, but you have no control over it. Le 08/10/2014 13:15, Stefan Bader a écrit : > There does not seem to be clear documentation on this. Just a note that from > your description I was not completely sure whether you did unmount before > starting the release procedure. I would say unmount is a must. > Doing so, I also ended up in the state where bcache0 still existed. But I was > able to get rid of that by > > echo 1 >/sys/block/bcache0/bcache/stop > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377142 Title: Bcache doesn't allow full unregistering without rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1377142] Re: Bcache doesn't allow full unregistering without rebooting
Yes you can get rid of bcache0, but you can't re-use the device for anything unless you reboot ( re bcache or just plain fdisk/parted ). Le 08/10/2014 13:15, Stefan Bader a écrit : > There does not seem to be clear documentation on this. Just a note that from > your description I was not completely sure whether you did unmount before > starting the release procedure. I would say unmount is a must. > Doing so, I also ended up in the state where bcache0 still existed. But I was > able to get rid of that by > > echo 1 >/sys/block/bcache0/bcache/stop > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377142 Title: Bcache doesn't allow full unregistering without rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1377130] Re: Crash at creation of bcache if caching size > backing size
Strange, I can reproduce each time, I'm using the iso: ubuntu-14.10-beta2-desktop-amd64.iso from http://releases.ubuntu.com/utopic/ I'm on utopic, with vrit-manager. Regards. Le 08/10/2014 13:17, Stefan Bader a écrit : > +1 on the fail to reproduce. Followed the steps and everything worked > without issues (using kvm/qemu VM with emulated devices and even sda > being backed by a real ssd, but I am not sure the difference gets > propagated). > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377130 Title: Crash at creation of bcache if caching size > backing size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377130] Re: Crash at creation of bcache if caching size > backing size
** Description changed: Hi, I found a bug that crashes the machine if you create a bcache where the caching device size is bigger than backing device. This case may happen if you create a bcache with a plan to add a bigger disk/partition/raid later to it. To reproduce it follow this steps: start a vm with utopic-amd64-desktop iso, it must have 2 disks, one of 16G and on of 8G - apt-get update && apt-get install bcache-tools - /dev/sda is 16G caching device - /dev/sdb is 8G backing device + apt-get update && apt-get install bcache-tools + /dev/sda is 16G caching device + /dev/sdb is 8G backing device - make-bcache --write-back --discard -C /dev/sda -B /dev/sdb - now the machine is hanged. + make-bcache --write-back --discard -C /dev/sda -B + /dev/sdb + + now the machine is hanged! if you reboot and reinstall bcache-tools the bcache device has been created - - bcache-super-show -f /dev/sda: - == - sb.magic ok - sb.first_sector 8 [match] - sb.csum 45C96B38A79275A7 [match] - sb.version0 [cache device] + + bcache-super-show -f /dev/sda: + == + sb.magicok + sb.first_sector 8 [match] + sb.csum 45C96B38A79275A7 [match] + sb.version 0 [cache device] - dev.label (empty) - dev.uuid 155ab65e-e74a-4ca8-91da-467ef696db63 - dev.sectors_per_block 1 - dev.sectors_per_bucket1024 - dev.cache.first_sector1024 - dev.cache.cache_sectors 33553408 - dev.cache.total_sectors 33554432 - dev.cache.ordered no - dev.cache.discard yes - dev.cache.pos 0 - dev.cache.replacement 0 [lru] + dev.label (empty) + dev.uuid155ab65e-e74a-4ca8-91da-467ef696db63 + dev.sectors_per_block 1 + dev.sectors_per_bucket 1024 + dev.cache.first_sector 1024 + dev.cache.cache_sectors 33553408 + dev.cache.total_sectors 33554432 + dev.cache.ordered no + dev.cache.discard yes + dev.cache.pos 0 + dev.cache.replacement 0 [lru] - cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 + cset.uuid + bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 - * - bcache-super-show /dev/sdb: - = - sb.magic ok - sb.first_sector 8 [match] - sb.csum F37A1BB08A7F5DE7 [match] - sb.version1 [backing device] + * + bcache-super-show /dev/sdb: + = + sb.magicok + sb.first_sector 8 [match] + sb.csum F37A1BB08A7F5DE7 [match] + sb.version 1 [backing device] - dev.label (empty) - dev.uuid 341f1c83-1797-4157-aa9e-524107db5606 - dev.sectors_per_block 1 - dev.sectors_per_bucket1024 - dev.data.first_sector 16 - dev.data.cache_mode 1 [writeback] - dev.data.cache_state 0 [detached] + dev.label (empty) + dev.uuid341f1c83-1797-4157-aa9e-524107db5606 + dev.sectors_per_block 1 + dev.sectors_per_bucket 1024 + dev.data.first_sector 16 + dev.data.cache_mode 1 [writeback] + dev.data.cache_state0 [detached] - cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 - * + cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 + * you can format it: - mkfs.ext4 /dev/bcache0 - Rejet des blocs de périphérique : complété - Creating filesystem with 2097150 4k blocks and 524288 inodes - Filesystem UUID: b99a09de-3a92-4a44-82cd-29f75f8bf0c9 - Superblocs de secours stockés sur les blocs : - 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 + mkfs.ext4 /dev/bcache0 + Rejet des blocs de périphérique : complété + Creating filesystem with 2097150 4k blocks and 524288 inodes + Filesystem UUID: b99a09de-3a92-4a44-82cd-29f75f8bf0c9 + Superblocs de secours stockés sur les blocs : +32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 - Allocation des tables de groupe
[Bug 1377142] Re: Bcache doesn't allow full unregistering without rebooting
** Description changed: If you create a bcache device, you can't reuse all your disk/partitions without a reboot. You can reproduce the case this way: start a vm with 2 disks (caching must be bigger or equal to the backing cf bug :1377130) and an iso of utopic desktop amd64 create the bcache device: - make-bcache --writeback --discard -C /dev/sda -B - /dev/sdb - - UUID: b245150d-cfbe-4f90-836a-343e0e1a4c55 - Set UUID: c990a31a-f531-4231-9603-d40230dc6504 - version:0 - nbuckets: 16384 - block_size: 1 - bucket_size:1024 - nr_in_set: 1 - nr_this_dev:0 - first_bucket: 1 - UUID: cc31e0bb-db29-4115-a1b2-e9ff54e5f127 - Set UUID: c990a31a-f531-4231-9603-d40230dc6504 - version:1 - block_size: 1 - data_offset:16 - - ** - command: - lsblk - - result: - NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT - sda 8:008G 0 disk - └─bcache0 251:00 16G 0 disk - sdb 8:16 0 16G 0 disk - └─bcache0 251:00 16G 0 disk - sr011:01 1,1G 0 rom /cdrom - loop0 7:00 1,1G 1 loop /rofs - ** + make-bcache --writeback --discard -C /dev/sda -B /dev/sdb + + UUID: b245150d-cfbe-4f90-836a-343e0e1a4c55 + Set UUID: c990a31a-f531-4231-9603-d40230dc6504 + version:0 + nbuckets: 16384 + block_size: 1 + bucket_size:1024 + nr_in_set: 1 + nr_this_dev:0 + first_bucket: 1 + UUID: cc31e0bb-db29-4115-a1b2-e9ff54e5f127 + Set UUID: c990a31a-f531-4231-9603-d40230dc6504 + version:1 + block_size: 1 + data_offset:16 + + ** + command: + lsblk + + result: + NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT + sda 8:008G 0 disk + └─bcache0 251:00 16G 0 disk + sdb 8:16 0 16G 0 disk + └─bcache0 251:00 16G 0 disk + sr011:01 1,1G 0 rom /cdrom + loop0 7:00 1,1G 1 loop /rofs + ** All is good - lsmod | grep bcache: - bcache227884 3 + lsmod | grep bcache: + bcache227884 3 format the bcache device: - ** - command: - mkfs.ext4 /dev/bcache0 - - result: - Rejet des blocs de périphérique :4096/4194302 complété - Creating filesystem with 4194302 4k blocks and 1048576 inodes - Filesystem UUID: 587d2249-3eaf-4590-a00d-42939f257e99 - Superblocs de secours stockés sur les blocs : - 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, - 4096000 - - Allocation des tables de groupe : 0/128 complété - Écriture des tables d'i-noeuds : 0/128 complété - Création du journal (32768 blocs) : complété - Écriture des superblocs et de l'information de comptabilité du système de - fichiers : 0/128 2/128 complété - - ** + ** + command: + mkfs.ext4 /dev/bcache0 + + result: + Rejet des blocs de périphérique :4096/4194302 complété + Creating filesystem with 4194302 4k blocks and 1048576 inodes + Filesystem UUID: 587d2249-3eaf-4590-a00d-42939f257e99 + Superblocs de secours stockés sur les blocs : + 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, + 4096000 + + Allocation des tables de groupe : 0/128 complété + Écriture des tables d'i-noeuds : 0/128 complété + Création du journal (32768 blocs) : complété + Écriture des superblocs et de l'information de comptabilité du système de + fichiers : 0/128 2/128 complété + + ** Now mount it: - mount /dev/bcache0 /mnt/ - mkdir /mnt/test_dir - touch /mnt/test_file + mount /dev/bcache0 /mnt/ + mkdir /mnt/test_dir + touch /mnt/test_file state of: /sys/fs/bcache/ - ls /sys/fs/bcache/ - - c990a31a-f531-
[Bug 1377142] [NEW] Bcache doesn't allow full unregistering without rebooting
Public bug reported: If you create a bcache device, you can't reuse all your disk/partitions without a reboot. You can reproduce the case this way: start a vm with 2 disks (caching must be bigger or equal to the backing cf bug :1377130) and an iso of utopic desktop amd64 create the bcache device: make-bcache --writeback --discard -C /dev/sda -B /dev/sdb UUID: b245150d-cfbe-4f90-836a-343e0e1a4c55 Set UUID: c990a31a-f531-4231-9603-d40230dc6504 version: 0 nbuckets: 16384 block_size: 1 bucket_size: 1024 nr_in_set:1 nr_this_dev: 0 first_bucket: 1 UUID: cc31e0bb-db29-4115-a1b2-e9ff54e5f127 Set UUID: c990a31a-f531-4231-9603-d40230dc6504 version: 1 block_size: 1 data_offset: 16 ** command: lsblk result: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:008G 0 disk └─bcache0 251:00 16G 0 disk sdb 8:16 0 16G 0 disk └─bcache0 251:00 16G 0 disk sr011:01 1,1G 0 rom /cdrom loop0 7:00 1,1G 1 loop /rofs ** All is good lsmod | grep bcache: bcache227884 3 format the bcache device: ** command: mkfs.ext4 /dev/bcache0 result: Rejet des blocs de périphérique :4096/4194302 complété Creating filesystem with 4194302 4k blocks and 1048576 inodes Filesystem UUID: 587d2249-3eaf-4590-a00d-42939f257e99 Superblocs de secours stockés sur les blocs : 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000 Allocation des tables de groupe : 0/128 complété Écriture des tables d'i-noeuds : 0/128 complété Création du journal (32768 blocs) : complété Écriture des superblocs et de l'information de comptabilité du système de fichiers : 0/128 2/128 complété ** Now mount it: mount /dev/bcache0 /mnt/ mkdir /mnt/test_dir touch /mnt/test_file state of: /sys/fs/bcache/ ls /sys/fs/bcache/ c990a31a-f531-4231-9603-d40230dc6504 register register_quiet bcache-super-show /dev/sda sb.magic ok sb.first_sector 8 [match] sb.csum E6A8D9AC496B0B04 [match] sb.version3 [cache device] dev.label (empty) dev.uuid b245150d-cfbe-4f90-836a-343e0e1a4c55 dev.sectors_per_block 1 dev.sectors_per_bucket1024 dev.cache.first_sector1024 dev.cache.cache_sectors 16776192 dev.cache.total_sectors 16777216 dev.cache.ordered yes dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid c990a31a-f531-4231-9603-d40230dc6504 ** bcache-super-show -f /dev/sdb sb.magic ok sb.first_sector 8 [match] sb.csum 9600B159F36A67DD [match] sb.version1 [backing device] dev.label (empty) dev.uuid cc31e0bb-db29-4115-a1b2-e9ff54e5f127 dev.sectors_per_block 1 dev.sectors_per_bucket1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state 2 [dirty] cset.uuid c990a31a-f531-4231-9603-d40230dc6504 ** mount: /dev/bcache0 on /mnt type ext4 (rw) we will unregister the bcache: echo 1 /sys/fs/bcache/c990a31a-f531-4231-9603-d40230dc6504/unregister check the content of /sys/fs/bcache ls /sys/fs/bcache/ register register_quiet So bcache is unregistered, but status of /dev/sda: bcache-super-show -f /dev/sda sb.magic ok sb.first_sector 8 [match] sb.csum E6A8D9AC496B0B04 [match] sb.version3 [cache device] dev.label (empty) dev.uuid b245150d-cfbe-4f90-836a-343e0e1a4c55 dev.sectors_per_block 1 dev.sectors_per_bucket1024 dev.cache.first_sector1024 dev.cache.cache_sectors 16776192 dev.cache.total_sectors 16777216 dev.cache.ordered yes dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid c990a31a-f531-4231-9603-d40230dc6504 command: bcache-super-show -f /dev/sdb result: sb.magic ok sb.first_sector 8 [match] sb.csum D41799F794675FA8 [match] sb.version1 [backing device] dev.label (empty) dev.uuid cc31e0bb-db29-4115-a1b2-e9ff54e5f127 dev.sectors_per_block 1 dev.sectors_per_bucket1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state 0 [detached] cset.uuid ---- *
[Bug 1377130] Re: Crash at creation of bcache if caching size > backing size
** Also affects: bcache-tools (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/1377130 Title: Crash at creation of bcache if caching size > backing size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1377130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377130] [NEW] Crash at creation of bcache if caching size > backing size
Public bug reported: Hi, I found a bug that crashes the machine if you create a bcache where the caching device size is bigger than backing device. This case may happen if you create a bcache with a plan to add a bigger disk/partition/raid later to it. To reproduce it follow this steps: start a vm with utopic-amd64-desktop iso, it must have 2 disks, one of 16G and on of 8G apt-get update && apt-get install bcache-tools /dev/sda is 16G caching device /dev/sdb is 8G backing device make-bcache --write-back --discard -C /dev/sda -B /dev/sdb now the machine is hanged. if you reboot and reinstall bcache-tools the bcache device has been created bcache-super-show -f /dev/sda: == sb.magicok sb.first_sector 8 [match] sb.csum 45C96B38A79275A7 [match] sb.version 0 [cache device] dev.label (empty) dev.uuid155ab65e-e74a-4ca8-91da-467ef696db63 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.cache.first_sector 1024 dev.cache.cache_sectors 33553408 dev.cache.total_sectors 33554432 dev.cache.ordered no dev.cache.discard yes dev.cache.pos 0 dev.cache.replacement 0 [lru] cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 * bcache-super-show /dev/sdb: = sb.magicok sb.first_sector 8 [match] sb.csum F37A1BB08A7F5DE7 [match] sb.version 1 [backing device] dev.label (empty) dev.uuid341f1c83-1797-4157-aa9e-524107db5606 dev.sectors_per_block 1 dev.sectors_per_bucket 1024 dev.data.first_sector 16 dev.data.cache_mode 1 [writeback] dev.data.cache_state0 [detached] cset.uuid bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 * you can format it: mkfs.ext4 /dev/bcache0 Rejet des blocs de périphérique : complété Creating filesystem with 2097150 4k blocks and 524288 inodes Filesystem UUID: b99a09de-3a92-4a44-82cd-29f75f8bf0c9 Superblocs de secours stockés sur les blocs : 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 Allocation des tables de groupe : complété Écriture des tables d'i-noeuds : complété Création du journal (32768 blocs) : complété Écriture des superblocs et de l'information de comptabilité du système de fichiers : restarting the format gave me an other bug (X.org crashing): free from cli: total used free sharedbuffers cached Mem: 1017168 814040 203128 195568 91264 513064 -/+ buffers/cache: 209712 807456 Swap:0 0 0 tail /var/log/syslog: [ 568.016481] [ 4983] 0 4983 3332 121 110 0 mdadm [ 568.016483] [ 5259] 0 5259 6703 300 190 0 mkfs.ext4 [ 568.016484] Out of memory: Kill process 1947 (Xorg) score 38 or sacrifice child [ 568.016485] Killed process 1947 (Xorg) total-vm:313160kB, anon-rss:35976kB, file-rss:4232kB [ 568.707107] systemd-logind[1396]: Failed to start unit user@112.service: Unknown unit: user@112.service [ 568.707113] systemd-logind[1396]: Failed to start user service: Unknown unit: user@112.service [ 568.709876] systemd-logind[1396]: New session c8 of user lightdm. [ 568.709890] systemd-logind[1396]: Linked /tmp/.X11-unix/X0 to /run/user/112/X11-display. You can unregister the bcache device: [ 830.811150] bcache: cached_dev_detach_finish() Caching disabled for sdb [ 830.949898] bcache: cache_set_free() Cache set bcaa2595-bbc8-43a7-8c44-5d0aca0f3fc8 unregistered ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, I found a bug that crashes the machine if you create a bcache where the - cahcing device size is bigger than backing device. + caching device size is bigger than backing device. + + This case may happen if you create a bcache with a plan to add a bigger + disk/partition/raid later to it. To reproduce it follow this steps: start a vm with utopic-amd64-desktop iso, it must have 2 disks, one of 16G and on of 8G apt-get update && apt-get install bcache-tools /dev/sda is 16G caching device /dev/sdb is 8G backing device make-bcache --write-back --discard -C /dev/sda -B /dev/sdb now the machine is hanged. - if you reboot and reinstall bcache-tools + if you reboot and reinstall bcache-tools the bcache device has been created bcache-super-show -f /dev/sda: == sb.magic ok sb.first_sector 8 [match] sb.csum 45C96B38A79275A7 [match] sb.version0 [cache device] dev.label (empty) dev.uuid 155ab65e-e7
[Bug 1376661] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1376661/+attachment/483/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376661] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1376661/+attachment/480/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376661] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1376661/+attachment/482/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376661] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1376661/+attachment/481/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376661] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1376661/+attachment/475/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376661] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1376661/+attachment/477/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376661 Title: Strange behaviour of ahci driver (intel 82801 Mobile SATA Controller) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
