[Bug 1590799] Re: nfs-kernel-server does not start because of dependency failure
Probably due to unrelated problem nfsd did not start for me to yesterday too. I've experienced the original bug this thread is about and I've had it fixed for some time. Should we create another bug or can we track it here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590799 Title: nfs-kernel-server does not start because of dependency failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: intel-microcode is out of date, version 20170707 fixes errata on 6th and 7th generation platforms
Today my manually installed 3.20151106.1+lp1700373b2 auto-updated to 3.20180108.0~ubuntu14.04.2 from repository, system booted successfully: $ dmesg | grep microcode [0.00] microcode: CPU0 microcode updated early to revision 0xc2, date = 2017-11-16 [0.110006] microcode: CPU1 microcode updated early to revision 0xc2, date = 2017-11-16 [1.915519] microcode: CPU0 sig=0x406e3, pf=0x80, revision=0xc2 [1.915537] microcode: CPU1 sig=0x406e3, pf=0x80, revision=0xc2 [1.915557] microcode: CPU2 sig=0x406e3, pf=0x80, revision=0xc2 [1.915576] microcode: CPU3 sig=0x406e3, pf=0x80, revision=0xc2 [1.915702] microcode: Microcode Update Driver: v2.01 , Peter Oruba I presume it contains fixes for both Ocaml crash and recent security problems. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: intel-microcode is out of date, version 20170707 fixes errata on 6th and 7th generation platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741934] Re: Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI fix)
On 14.04 with LTS Enablement Stack I can confirm that 4.4.0-108 was broken in the described way (trap on kfree) and 4.4.0-109 works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741934 Title: Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI fix) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1628289] Re: snapd should depend on squashfuse (for use in containers)
> The problem in your case is that you're trying to get this to work with LXC rather than LXD. Should I understand it as snapd is not currently supported under LXC? No way to reproduce manually in LXC whatever LXD does? > I'd very strongly recommend against anyone using the configuration above with LXC as the lxc.aa_profile=unconfined [...] Obviously not the best solution security-wise, but doesn't snapd provide its own level of isolation? It shouldn't be worse than running snapd on host, for people choosing not to rollout LXD? (Sorry for being increasingly off-topic, but currently Google brings people wishing to install e.g. nextcloud in a container here.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628289 Title: snapd should depend on squashfuse (for use in containers) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1628289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628289] Re: snapd should depend on squashfuse (for use in containers)
My problem was solved by:
1. Adding the following lines to the container config, then stopping and
starting the container:
---
# Make snapd work
lxc.aa_profile = unconfined
# don't drop: mac_admin mac_override
lxc.cap.drop =
lxc.cap.drop = sys_time sys_module sys_rawio
lxc.hook.autodev = sh -c 'mknod -m 666 ${LXC_ROOTFS_MOUNT}/dev/fuse c 10 229'
---
2. Executing the following lines in the container:
---
apt install snapd squashfuse fuse # last one is necessary too!
mkdir -p /lib/modules
---
There can still be some intermittent apparmor errors during snap
installs, just trying again fixes them. I still wonder how it worked for
others out of the box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should depend on squashfuse (for use in containers)
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1628289/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628289] Re: snapd should depend on squashfuse (for use in containers)
--- root@test:/# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial root@test:/# apt install squashfuse Reading package lists... Done Building dependency tree Reading state information... Done squashfuse is already the newest version (0.1.100-0ubuntu1~ubuntu16.04.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@test:/# snap install nextcloud error: cannot perform the following tasks: - Mount snap "core" (3440) ([start snap-core-3440.mount] failed with exit status 1: Job for snap-core-3440.mount failed. See "systemctl status snap-core-3440.mount" and "journalctl -xe" for details. ) root@test:/# snap install hello-world error: cannot perform the following tasks: - Mount snap "core" (3440) ([start snap-core-3440.mount] failed with exit status 1: Job for snap-core-3440.mount failed. See "systemctl status snap-core-3440.mount" and "journalctl -xe" for details. ) root@test:/# --- What I'm doing wrong? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628289 Title: snapd should depend on squashfuse (for use in containers) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1628289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628289] Re: snapd should depend on squashfuse (for use in containers)
> Just to update my previous comment: poking around Stéphane Graber's blog a bit suggests to me that I really shouldn't expect success with this using less than 16.10. Can someone please confirm it is really true? Bug description contains Xenial, and this discussion -- https://github.com/lxc/lxd/issues/3421 -- talks about 16.04. But it indeed doesn't work even with squashfuse. May it depend on container configuration? ** Bug watch added: LXD bug tracker #3421 https://github.com/lxc/lxd/issues/3421 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628289 Title: snapd should depend on squashfuse (for use in containers) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1628289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722763] [NEW] Simply updating kernel regularly exhausts default number of inodes on ext4
Public bug reported: I have a Trusty server system with mostly default configuration and very few additional packages. Root filesystem is ext4 created, I believe, by the installer; /var is on a different filesystem. For the last 18 months this server auto-updated automatically, but without autoremove; 12 months ago linux-generic-lts-xenial package was added. During this period it installed more than 60 kernel packages in total: 34 times for kernel 3.13 and another 27 times for kernel 4.4 (apparently it kept updating 3.13 despite presence of linux-generic-lts-xenial). Each time corresponding linux-headers-$version and linux-headers-$version-generic packages were installed, occupying another ~25K inodes per pair. /usr/src now contains more than 1.5M files and the root filesystem ran out of inodes, since by default it has slightly less than 2M allocated. I'm reluctant to blame the problem on the lack of autoremove, since adding it would reduce reliability of the installation in terms of both unnecessary operations on packages and choice of kernels at boot. I understand that I should monitor inodes when putting a lot of small files (e.g. running some cache) or installing heavy packages, but it is the first time I see an almost empty installation killing itself this way. I don't think this is right. I see the following mitigations for the problem distribution-side: * increase default number of inodes for the ext4 root filesystem (or for all ext4 filesystems); * add warning to the installer that number of root inodes may not be sufficient for the lifetime of the installation; * find out if it's safe to remove linux-headers-generic package when linux-generic-lts-xenial is present and (if yes) add corresponding advice to the https://wiki.ubuntu.com/Kernel/LTSEnablementStack page. ** Affects: 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/1722763 Title: Simply updating kernel regularly exhausts default number of inodes on ext4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1722763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel
Hello, is it going to appear in 4.4? I'm getting tired of running 4.4.0-66 (jk works ok but still would prefer to update). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686099 Title: connection flood to port 445 on mounting cifs volume under kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1686099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: intel-microcode is out of date, version 20170707 fixes errata on 6th and 7th generation platforms
Well, I tried intel-microcode_3.20151106.1+lp1700373b2_amd64.deb on Trusty with 4.4 and it worked. Of course, in someone's case it may start a thermonuclear war, so use this information with care. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: intel-microcode is out of date, version 20170707 fixes errata on 6th and 7th generation platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: intel-microcode is out of date, version 20170511 fixes errata on 6th and 7th generation platforms
Pardon my ignorance, can someone please clarify in more details meaning of "require early initramfs loading code" from comment #12? Because clearly some people will go ahead and update it in Trusty anyways. Judging from other comments new microcode may break something that is unlikely to be present in Trusty at all, and especially unlikely to be running in the first hundred milliseconds when microcode is actually updated. Does not sound very convincing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: intel-microcode is out of date, version 20170511 fixes errata on 6th and 7th generation platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: Please update microcode to version 20170511 on all supported platforms
Concerning microcode update time in Trusty, real test (with linux-generic-lts-xenial installed): --- marat@CM01:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty marat@CM01:~$ uname -a Linux CM01.administration.intranet.rqc.ru 4.4.0-81-generic #104~14.04.1-Ubuntu SMP Wed Jun 14 12:45:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux marat@CM01:~$ dmesg | nl | grep -i microcode 1 [0.00] microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12 226 [0.080489] microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12 229 [0.083195] microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12 230 [0.085331] #3<6>[0.085831] microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12 670 [1.262792] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29 671 [1.262799] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29 672 [1.262836] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29 673 [1.262877] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29 674 [1.262960] microcode: Microcode Update Driver: v2.01 , Peter Oruba 812 [2.696416] [drm] Loading CAICOS Microcode --- So it's in the beginning, though not all quite 0.00. (Last line is apparently unrelated to CPU.) As for microcode updates _from_ container, I thought it should go without saying that it must be prohibited. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: Please update microcode to version 20170511 on all supported platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: Please update microcode to version 20170511 on all supported platforms
Concerning microcode update time in Trusty, real test (with linux-generic-lts-xenial installed): --- marat@CM01:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty marat@CM01:~$ uname -a Linux CM01.administration.intranet.rqc.ru 4.4.0-81-generic #104~14.04.1-Ubuntu SMP Wed Jun 14 12:45:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux marat@CM01:~$ dmesg | nl | grep -i microcode 1 [0.00] microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12 226 [0.080489] microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12 229 [0.083195] microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12 230 [0.085331] #3<6>[0.085831] microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12 670 [1.262792] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29 671 [1.262799] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29 672 [1.262836] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29 673 [1.262877] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29 674 [1.262960] microcode: Microcode Update Driver: v2.01 , Peter Oruba 812 [2.696416] [drm] Loading CAICOS Microcode --- So it's in the beginning, though not all quite 0.00. (Last line is apparently unrelated to CPU.) As for microcode updates _from_ container, I thought it should go without saying that it must be prohibited. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: Please update microcode to version 20170511 on all supported platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: Please update microcode to version 20170511 on all supported platforms
Concerning microcode update time in Trusty, real test (with linux-generic-lts-xenial installed): --- marat@CM01:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty marat@CM01:~$ uname -a Linux CM01.administration.intranet.rqc.ru 4.4.0-81-generic #104~14.04.1-Ubuntu SMP Wed Jun 14 12:45:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux marat@CM01:~$ dmesg | nl | grep -i microcode 1 [0.00] microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12 226 [0.080489] microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12 229 [0.083195] microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12 230 [0.085331] #3<6>[0.085831] microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12 670 [1.262792] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29 671 [1.262799] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29 672 [1.262836] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29 673 [1.262877] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29 674 [1.262960] microcode: Microcode Update Driver: v2.01 , Peter Oruba 812 [2.696416] [drm] Loading CAICOS Microcode --- So it's in the beginning, though not all quite 0.00. (Last line is apparently unrelated to CPU.) As for microcode updates _from_ container, I thought it should go without saying that it must be prohibited. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: Please update microcode to version 20170511 on all supported platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: Please update microcode to version 20170511 on all supported platforms
Concerning microcode update time in Trusty, real test (with linux-generic-lts-xenial installed): --- marat@CM01:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty marat@CM01:~$ uname -a Linux CM01.administration.intranet.rqc.ru 4.4.0-81-generic #104~14.04.1-Ubuntu SMP Wed Jun 14 12:45:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux marat@CM01:~$ dmesg | nl | grep -i microcode 1 [0.00] microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12 226 [0.080489] microcode: CPU1 microcode updated early to revision 0x29, date = 2013-06-12 229 [0.083195] microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12 230 [0.085331] #3<6>[0.085831] microcode: CPU3 microcode updated early to revision 0x29, date = 2013-06-12 670 [1.262792] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29 671 [1.262799] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29 672 [1.262836] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29 673 [1.262877] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29 674 [1.262960] microcode: Microcode Update Driver: v2.01 , Peter Oruba 812 [2.696416] [drm] Loading CAICOS Microcode --- So it's in the beginning, though not all quite 0.00. (Last line is apparently unrelated to CPU.) As for microcode updates _from_ container, I thought it should go without saying that it must be prohibited. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: Please update microcode to version 20170511 on all supported platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: Please update microcode to version 20170511 on all supported platforms
*It is* a security update, unless proven otherwise. "Unpredictable System Behavior" is often just a polite name for hardware vulnerability. I also run Trusty in enterprise environment. Particularly, I run it on a mission critical secondary network server (DNS, NTP etc.) intentionally paired to a primary Xenial machine so as not to create too homogeneous environment. Therefore I need it to be fixed in Trusty. Disabling HT is not very good workaround for i3-6100U in there too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: Please update microcode to version 20170511 on all supported platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel
4.4.0-77-generic #98-Ubuntu, the bug is still here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686099 Title: connection flood to port 445 on mounting cifs volume under kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1686099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423326] Re: lxsession should depend on lxsession-logout
Was just hit by this bug after `apt install lxde` in LXC container under 16.04 server. Considering that it installed tons of other stuff (more than 1GB) it was just shock to find out that logout is missing. How is it even optional, if red button in the south east corner invokes it? Why is it still not fixed in LTS? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423326 Title: lxsession should depend on lxsession-logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1423326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590799] Re: nfs-kernel-server does not start because of dependency failure
Can confirm that it booted successfully (once) with patch live-applied in a system that earlier experienced this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590799 Title: nfs-kernel-server does not start because of dependency failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590799] Re: nfs-kernel-server does not start because of dependency failure
Rafael David Tinoco (inaddy): thank you very much for the diff! Have applied it to live nfs-mountd.service, nfs-server.service, and rpc- statd.service in /lib/systemd/system, will report result of the next reboot here if it happens before official fix arrives for Xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590799 Title: nfs-kernel-server does not start because of dependency failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590799] Re: nfs-kernel-server does not start because of dependency failure
Was just hit by this bug on two production servers. Is it possible to apply a fix manually? For some reason I don't see a diff in https://launchpad.net/~inaddy/+archive/ubuntu/lp1590799 . I have replaced rpcbind.target with rpcbind.service in Requires and After lines of /etc/systemd/system/multi-user.target.wants/nfs- server.service , will this be sufficient? I don't have any other nfs-*.service files, including nfs-mountd.service, in my /etc directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590799 Title: nfs-kernel-server does not start because of dependency failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282294] Re: "Cannot open pixbuf loader module file"
Happened to me during casual dist-upgrade on Ubuntu Gnome 14.04: --- Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ... (gtk-update-icon-cache-3.0:9274): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. --- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282294 Title: "Cannot open pixbuf loader module file" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted
I'm also seeing this on some PDFs in Evince from 14.04. Images appear correctly in main window, but become inverted in print preview and in paper printout. When I extract images from these PDFs using pdfimages tool, extracted images also appear inverted. Looks like some versions of Acrobat embed images inverted and uninvert them on output, and this last step is omitted by Evince when printing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560286 Title: Evince displays pdf file fine, but prints colors inverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608034] [NEW] roundcube configuration fails because mysql is missing, does not work without ca-certificates
Public bug reported: 1. When configuring roundcube in a clean lxc container (ubuntu-xenial- amd64) it asked me to provide root password for MySQL so that it could create its user/database. The problem is, mysql-server was not being simultaneously installed, so there's no way for me to proceed. (Also, after I installed mysql-server manually, I had problems restarting roundcube configuration, found it easier to nuke and re-create the container.) There indeed exists a rare case of using external database server (what for?), but user is not even being asked. 2. Later on it stubbornly refused to establish IMAP connections to my server. Turned out, the system was also missing all root certificates. Considering intended use of the roundcube, I think that package ca- certificates will be needed in the majority of cases. Summarizing: please add mysql-server dependency to roundcube-mysql, and ca-certificates dependency to roundcube itself. ** Affects: roundcube (Ubuntu) Importance: Undecided Status: New ** Summary changed: - roundcube configuration fails because mysql is missing, missing more dependencies + roundcube configuration fails because mysql is missing, does not work without ca-certificates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608034 Title: roundcube configuration fails because mysql is missing, does not work without ca-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/roundcube/+bug/1608034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588396] Re: Bad connectivity to security.ubuntu.com, mirrors.ubuntu.com
In reply to Ubuntu Foundations Team Bug Bot (crichton) message: I believe the problem is in the Ubuntu.org infrastructure, not Ubuntu OS code, therefore singling out specific version or package is not appropriate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588396 Title: Bad connectivity to security.ubuntu.com, mirrors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1588396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588396] Re: Bad connectivity to security.ubuntu.com, mirrors.ubuntu.com
Sorry, I meant Ubuntu.com, not Ubuntu.org which seems unrelated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588396 Title: Bad connectivity to security.ubuntu.com, mirrors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1588396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588396] [NEW] Bad connectivity to security.ubuntu.com, mirrors.ubuntu.com
Public bug reported: Not sure where to report it, but connectivity to security.ubuntu.com and mirrors.ubuntu.com is quite poor right now (2nd of June, 2016), and this causes various problems with system updates for me and probably other people. I've created a couple of measurements on RIPE ATLAS monitoring network, see their results here: * https://atlas.ripe.net/measurements/3904577/#!probes * https://atlas.ripe.net/measurements/3904575/#!probes Right now 6% of probes cannot connect to security.ubuntu.com at all, almost 50% show round-trip times larger than 50 ms. ** Affects: 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/1588396 Title: Bad connectivity to security.ubuntu.com, mirrors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1588396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
