[Bug 1726548] Re: Windows resized after resume
No, I was mistaken; it didn't solve the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726548 Title: Windows resized after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1726548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
I can also confirm that after following the instructions from #51 on Bionic, this bug is fixed. (I would however comment that it would have been easy to miss that safety measure and upgrade a whole bunch of proposed packages by mistake. I would caution everyone to be more careful when directing non- developers to alter developer configurations.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726548] Re: Windows resized after resume
However, changing `glib`'s `scaling-factor` to 2 as described by both answers to https://askubuntu.com/q/906797/142526 did solve the issue on my desktop, running Bionic. This is accomplished by creating `/usr/share/glib-2.0/schemas/93_hidpi.gschema.override` with [org.gnome.desktop.interface] scaling-factor=2 and then running `sudo glib-compile-schemas /usr/share/glib-2.0/schemas` (and restarting). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726548 Title: Windows resized after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1726548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
I can also confirm that after following the instructions from #51 on Bionic, this bug is fixed. (I would however comment that it would have been easy to miss that safety measure and upgrade a whole bunch of proposed packages by mistake. I would caution everyone to be more careful when directing non- developers to alter developer configurations.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726548] Re: Windows resized after resume
I have this issue on a desktop connected to a Dell 28" at a resolution of 3840x2160 and scale of 200%. Running `gsettings set org.gnome.desktop.interface scaling-factor 1` (or `2`) doesn't do the trick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726548 Title: Windows resized after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1726548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602409] Re: Ubuntu 16.04 Should package zfs-auto-snapshot
@pjgoodall, how was a fix released? `apt policy zfs-auto-snapshot` returns no results on Xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602409 Title: Ubuntu 16.04 Should package zfs-auto-snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1602409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380702] Re: No keyboards shortcuts in QT apps
I can also confirm that the bug is fixed (tested with Texmaker; I don't have Qt Assistant). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380702] Re: No keyboards shortcuts in QT apps
@Dimitry, whether or not `appmenu-qt5` is in use in 16.10, that doesn't tell us if running a QT5 program setting `ENV UBUNTU_MENUPROXY= ` returns the use of keyboard shortcuts. Can you confirm / deny? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380702] Re: No keyboards shortcuts in QT apps
@RobertOrzanna, Is that after manually removing it, or does 16.10 come that way? If the latter, I'd still attempt the workaround (as I think it actually works around what's wrong in the relation between QT5 and Ubuntu's Dash, instead of manually 'crippling' Unity to 'force its hand', as it were). If the former, I'm afraid I don't know how to restore it. In any case, have you tried using the workaround with an actual QT5 program, to check for shortcut availability? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380702] Re: No keyboards shortcuts in QT apps
Let me just re-iterate that comment #14 includes another workaround, in my opinion superior to removing the `app-menu-qt5` package altogether. I suspect that it would still works in 16.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Not by design, no. Any of that, really, since I wouldn't have known where to go to make these alterations if I wanted to (well, now that you pointed that out, I should be able to reverse-engineer it and see if it at least assigns IP addresses to containers automatically that way). It's a pretty new installation of Ubuntu server; I can't think of any non-standard thing I did on that machine that might've caused all this mess. By the way, adding `nameserver 8.8.8.8` to /etc/resolv.conf made no difference. Putting it in /etc/resolvconf/resolv.conf.d/base and running `resolvconf -u` resulted in requests hanging for a few seconds before it returns the same message, that the address couldn't have been resolved. All the while I can ping 8.8.8.8 just fine. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Not by design, no. Any of that, really, since I wouldn't have known where to go to make these alterations if I wanted to (well, now that you pointed that out, I should be able to reverse-engineer it and see if it at least assigns IP addresses to containers automatically that way). It's a pretty new installation of Ubuntu server; I can't think of any non-standard thing I did on that machine that might've caused all this mess. By the way, adding `nameserver 8.8.8.8` to /etc/resolv.conf made no difference. Putting it in /etc/resolvconf/resolv.conf.d/base and running `resolvconf -u` resulted in requests hanging for a few seconds before it returns the same message, that the address couldn't have been resolved. All the while I can ping 8.8.8.8 just fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Okay. FYI I went ahead and defined my own bridge to let containers communicate directly with my router's dhcp server, but I've created and started a new privileged container `pr1` and made sure it uses `lxcbr0` and not my `br0`. Still, it's possible I'll have to tell `lxcbr0` to plug into `br0` rather than `eth0`, as `eth0` doesn't get an IP anymore on my machine, and if so I'll need some help doing that. Anyhow: From within container `pr1`: root@pr1:/# netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface root@pr1:/# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:16:3e:b2:93:2b inet6 addr: fe80::216:3eff:feb2:932b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1177 (1.1 KB) TX bytes:7656 (7.6 KB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@pr1:/# cat /etc/ cat: /etc/: Is a directory But then after following your other directions: root@pr1:/# ifconfig eth0 10.0.3.10 netmask 255.255.255.0 root@pr1:/# sudo route add -net default dev eth0 root@pr1:/# ping 10.0.3.1 PING 10.0.3.1 (10.0.3.1) 56(84) bytes of data. 64 bytes from 10.0.3.1: icmp_seq=1 ttl=64 time=0.102 ms 64 bytes from 10.0.3.1: icmp_seq=2 ttl=64 time=0.032 ms 64 bytes from 10.0.3.1: icmp_seq=3 ttl=64 time=0.049 ms Even better, if instead I do root@pr1:/# sudo route add -host 10.0.3.1 dev eth0 root@pr1:/# route add -net default gw 10.0.3.1 dev eth0 then I can now ping to my LAN from within the container, and also ping out to 8.8.8.8. At this point I have: root@pr1:/# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 10.0.3.10.0.0.0 UG0 0 0 eth0 10.0.3.00.0.0.0 255.255.255.0 U 0 0 0 eth0 10.0.3.10.0.0.0 255.255.255.255 UH0 0 0 eth0 root@pr1:/# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:16:3e:b2:93:2b inet addr:10.0.3.10 Bcast:10.0.3.255 Mask:255.255.255.0 inet6 addr: fe80::216:3eff:feb2:932b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:30 errors:0 dropped:0 overruns:0 frame:0 TX packets:80 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3579 (3.5 KB) TX bytes:19728 (19.7 KB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:51 errors:0 dropped:0 overruns:0 frame:0 TX packets:51 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3792 (3.7 KB) TX bytes:3792 (3.7 KB) However, and BTW this is a problem I still have on the unprivileged container using `br0` as well, I can't resolve DNS from within the container. It returns `ping: unknown host www.google.com` immediately. Finally, on my host I get: root@srv-Ub1404:~# ps -ef | grep dnsmasq lxc-dns+ 11309 1 0 Jan15 ?00:00:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --conf-file= --listen-address 10.0.3.1 --dhcp-range 10.0.1.2,10.0.1.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative root 13063 13052 0 00:01 pts/200:00:00 grep --color=auto dnsmasq -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Okay. FYI I went ahead and defined my own bridge to let containers communicate directly with my router's dhcp server, but I've created and started a new privileged container `pr1` and made sure it uses `lxcbr0` and not my `br0`. Still, it's possible I'll have to tell `lxcbr0` to plug into `br0` rather than `eth0`, as `eth0` doesn't get an IP anymore on my machine, and if so I'll need some help doing that. Anyhow: From within container `pr1`: root@pr1:/# netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface root@pr1:/# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:16:3e:b2:93:2b inet6 addr: fe80::216:3eff:feb2:932b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1177 (1.1 KB) TX bytes:7656 (7.6 KB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@pr1:/# cat /etc/ cat: /etc/: Is a directory But then after following your other directions: root@pr1:/# ifconfig eth0 10.0.3.10 netmask 255.255.255.0 root@pr1:/# sudo route add -net default dev eth0 root@pr1:/# ping 10.0.3.1 PING 10.0.3.1 (10.0.3.1) 56(84) bytes of data. 64 bytes from 10.0.3.1: icmp_seq=1 ttl=64 time=0.102 ms 64 bytes from 10.0.3.1: icmp_seq=2 ttl=64 time=0.032 ms 64 bytes from 10.0.3.1: icmp_seq=3 ttl=64 time=0.049 ms Even better, if instead I do root@pr1:/# sudo route add -host 10.0.3.1 dev eth0 root@pr1:/# route add -net default gw 10.0.3.1 dev eth0 then I can now ping to my LAN from within the container, and also ping out to 8.8.8.8. At this point I have: root@pr1:/# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 10.0.3.10.0.0.0 UG0 0 0 eth0 10.0.3.00.0.0.0 255.255.255.0 U 0 0 0 eth0 10.0.3.10.0.0.0 255.255.255.255 UH0 0 0 eth0 root@pr1:/# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:16:3e:b2:93:2b inet addr:10.0.3.10 Bcast:10.0.3.255 Mask:255.255.255.0 inet6 addr: fe80::216:3eff:feb2:932b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:30 errors:0 dropped:0 overruns:0 frame:0 TX packets:80 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3579 (3.5 KB) TX bytes:19728 (19.7 KB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:51 errors:0 dropped:0 overruns:0 frame:0 TX packets:51 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3792 (3.7 KB) TX bytes:3792 (3.7 KB) However, and BTW this is a problem I still have on the unprivileged container using `br0` as well, I can't resolve DNS from within the container. It returns `ping: unknown host www.google.com` immediately. Finally, on my host I get: root@srv-Ub1404:~# ps -ef | grep dnsmasq lxc-dns+ 11309 1 0 Jan15 ?00:00:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --conf-file= --listen-address 10.0.3.1 --dhcp-range 10.0.1.2,10.0.1.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative root 13063 13052 0 00:01 pts/200:00:00 grep --color=auto dnsmasq -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Wait, 'lxc-net' does show as `running` when I run `initctl list`. I guess that's what I get for not checking if the manuals I've been using are 100% compatible with my distro. Regardless, it still gives those errors, and starting containers fails with that seemingly network-related message. Attempting to start with the `-l trace -o debug.out` flags doesn't give me any new information, but perhaps I'm missing something there. In particular, I don't see what 'quota' it is that was reached; could that be relevant? ** Attachment added: debug.out https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4296759/+files/debug.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Wait, 'lxc-net' does show as `running` when I run `initctl list`. I guess that's what I get for not checking if the manuals I've been using are 100% compatible with my distro. Regardless, it still gives those errors, and starting containers fails with that seemingly network-related message. Attempting to start with the `-l trace -o debug.out` flags doesn't give me any new information, but perhaps I'm missing something there. In particular, I don't see what 'quota' it is that was reached; could that be relevant? ** Attachment added: debug.out https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4296759/+files/debug.out -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Well, it does help `lxc-net` create the bridge (shown on `brctl show` and `ifconfig`), but apparently not to configure it appropriately. `lxc-net` is still not listed when I run `service --status-all`, and attempting to start a container returns: server@srv-Ub1404:~$ lxc-start -n u1 Quota reached lxc_container: failed to create the configured network lxc_container: failed to spawn 'u1' lxc_container: The container failed to start. lxc_container: Additional information can be obtained by setting the --logfile and --logpriority options. The log for `lxc-net` (attached) still contains the same errors (odd; why would it look for `dnsmasq.conf`?), but now it also contains something about a bad IPTABLES rule (I'm not sure how to check which one). ** Attachment added: lxc-net.log https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4296741/+files/lxc-net.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Well, it does help `lxc-net` create the bridge (shown on `brctl show` and `ifconfig`), but apparently not to configure it appropriately. `lxc-net` is still not listed when I run `service --status-all`, and attempting to start a container returns: server@srv-Ub1404:~$ lxc-start -n u1 Quota reached lxc_container: failed to create the configured network lxc_container: failed to spawn 'u1' lxc_container: The container failed to start. lxc_container: Additional information can be obtained by setting the --logfile and --logpriority options. The log for `lxc-net` (attached) still contains the same errors (odd; why would it look for `dnsmasq.conf`?), but now it also contains something about a bad IPTABLES rule (I'm not sure how to check which one). ** Attachment added: lxc-net.log https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4296741/+files/lxc-net.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Aha! It was an unprivileged container (I used to get the same error messages with privileged and unprivileged containers), and it turns out in one of my purge - install cycles I forgot to add $USER veth lxcbr0 2 to `/etc/lxc/lxc-usernet`. I did that (it's now the only line there after the first commented title line), and now I can start the container! (I rechecked: privileged containers also start.) In both cases, however, the network is unreachable from within the container, as evident by the response `connect: Network is unreachable` to my pinging my host and/or router. I guess that's not surprising considerng that `lxc-net` still returns all of these error messages. However, that's truly a separate issue now, so it's worth summing up that the uncommented line in `/etc/default/lxc-net` (which was installed that way, for some reason) was the cause of this bug on my machine. I'm not sure what to do regarding the new issue (I haven't googled about it yet), so I'll include what you've asked for just in case you spot an easy fix. (BTW, I don't know if this belongs on this medium, but you have my sincere thanks for your help. It was invaluable.) server@srv-Ub1404:~$ sudo brctl show bridge name bridge id STP enabled interfaces lxcbr0 8000.fedfa607a667 no vethA4H3U6 server@srv-Ub1404:~$ ifconfig -a eth0 Link encap:Ethernet HWaddr 00:1b:fc:8e:95:ba inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::21b:fcff:fe8e:95ba/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7417201 errors:0 dropped:0 overruns:0 frame:0 TX packets:1758168 errors:0 dropped:0 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:10608089410 (10.6 GB) TX bytes:1646751692 (1.6 GB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:42 errors:0 dropped:0 overruns:0 frame:0 TX packets:42 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2867 (2.8 KB) TX bytes:2867 (2.8 KB) lxcbr0Link encap:Ethernet HWaddr fe:df:a6:07:a6:67 inet addr:10.0.3.1 Bcast:10.0.3.255 Mask:255.255.255.0 inet6 addr: fe80::98d6:4cff:fe27:2ea2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:74 errors:0 dropped:0 overruns:0 frame:0 TX packets:53 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:19844 (19.8 KB) TX bytes:7380 (7.3 KB) vethA4H3U6 Link encap:Ethernet HWaddr fe:df:a6:07:a6:67 inet6 addr: fe80::fcdf:a6ff:fe07:a667/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:47 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13986 (13.9 KB) TX bytes:1706 (1.7 KB) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Aha! It was an unprivileged container (I used to get the same error messages with privileged and unprivileged containers), and it turns out in one of my purge - install cycles I forgot to add $USER veth lxcbr0 2 to `/etc/lxc/lxc-usernet`. I did that (it's now the only line there after the first commented title line), and now I can start the container! (I rechecked: privileged containers also start.) In both cases, however, the network is unreachable from within the container, as evident by the response `connect: Network is unreachable` to my pinging my host and/or router. I guess that's not surprising considerng that `lxc-net` still returns all of these error messages. However, that's truly a separate issue now, so it's worth summing up that the uncommented line in `/etc/default/lxc-net` (which was installed that way, for some reason) was the cause of this bug on my machine. I'm not sure what to do regarding the new issue (I haven't googled about it yet), so I'll include what you've asked for just in case you spot an easy fix. (BTW, I don't know if this belongs on this medium, but you have my sincere thanks for your help. It was invaluable.) server@srv-Ub1404:~$ sudo brctl show bridge name bridge id STP enabled interfaces lxcbr0 8000.fedfa607a667 no vethA4H3U6 server@srv-Ub1404:~$ ifconfig -a eth0 Link encap:Ethernet HWaddr 00:1b:fc:8e:95:ba inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::21b:fcff:fe8e:95ba/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7417201 errors:0 dropped:0 overruns:0 frame:0 TX packets:1758168 errors:0 dropped:0 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:10608089410 (10.6 GB) TX bytes:1646751692 (1.6 GB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:42 errors:0 dropped:0 overruns:0 frame:0 TX packets:42 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2867 (2.8 KB) TX bytes:2867 (2.8 KB) lxcbr0Link encap:Ethernet HWaddr fe:df:a6:07:a6:67 inet addr:10.0.3.1 Bcast:10.0.3.255 Mask:255.255.255.0 inet6 addr: fe80::98d6:4cff:fe27:2ea2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:74 errors:0 dropped:0 overruns:0 frame:0 TX packets:53 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:19844 (19.8 KB) TX bytes:7380 (7.3 KB) vethA4H3U6 Link encap:Ethernet HWaddr fe:df:a6:07:a6:67 inet6 addr: fe80::fcdf:a6ff:fe07:a667/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:47 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13986 (13.9 KB) TX bytes:1706 (1.7 KB) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Well, I can't attest to Dan Kegel's setting, but this is my copy of `/etc/default/lxc-net`. Indeed, that line isn't commented out, and I don't have a `dnsmasq.conf` in `/etc/lxc`. ** Attachment added: lxc-net https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4295165/+files/lxc-net -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Well, I can't attest to Dan Kegel's setting, but this is my copy of `/etc/default/lxc-net`. Indeed, that line isn't commented out, and I don't have a `dnsmasq.conf` in `/etc/lxc`. ** Attachment added: lxc-net https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4295165/+files/lxc-net -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
This is odd. On advice from Flockport community I attempted to manually configure the bridge (its basic elements, at least) by entering sudo brctl addbr lxcbr0 sudo ifconfig lxcbr0 10.0.3.1 netmask 255.255.255.0 up This went just fine, with `ifconfig` reporting (beyond those interfaces already present in the attached file: lxcbr0Link encap:Ethernet HWaddr 8e:8c:5c:47:3b:bd inet addr:10.0.3.1 Bcast:10.0.3.255 Mask:255.255.255.0 inet6 addr: fe80::8c8c:5cff:fe47:3bbd/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:3632 (3.6 KB) Note in particular the `inet addr`, which is the same one `lxc-net.log` claimed couldn't be used. However, recycling `lxc-net` fails, either with: server@srv-Ub1404:~$ sudo restart lxc-net restart: Job failed to restart Or server@srv-Ub1404:~$ sudo stop lxc-net stop: Job failed while stopping server@srv-Ub1404:~$ sudo start lxc-net lxc-net start/running In both cases, the bridge is gone from the output of `ifconfig` as a result. `/var/log/upstart/lxc-net.log` is exactly as it is in the attached version (complaining about `dnsmasq.conf`, which is understandable, but also about 10.0.3.1 already being in use). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
This is odd. On advice from Flockport community I attempted to manually configure the bridge (its basic elements, at least) by entering sudo brctl addbr lxcbr0 sudo ifconfig lxcbr0 10.0.3.1 netmask 255.255.255.0 up This went just fine, with `ifconfig` reporting (beyond those interfaces already present in the attached file: lxcbr0Link encap:Ethernet HWaddr 8e:8c:5c:47:3b:bd inet addr:10.0.3.1 Bcast:10.0.3.255 Mask:255.255.255.0 inet6 addr: fe80::8c8c:5cff:fe47:3bbd/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:3632 (3.6 KB) Note in particular the `inet addr`, which is the same one `lxc-net.log` claimed couldn't be used. However, recycling `lxc-net` fails, either with: server@srv-Ub1404:~$ sudo restart lxc-net restart: Job failed to restart Or server@srv-Ub1404:~$ sudo stop lxc-net stop: Job failed while stopping server@srv-Ub1404:~$ sudo start lxc-net lxc-net start/running In both cases, the bridge is gone from the output of `ifconfig` as a result. `/var/log/upstart/lxc-net.log` is exactly as it is in the attached version (complaining about `dnsmasq.conf`, which is understandable, but also about 10.0.3.1 already being in use). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
** Attachment added: ps.txt https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294749/+files/ps.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
** Attachment added: brctl.txt https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294748/+files/brctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
** Attachment added: brctl.txt https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294748/+files/brctl.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
** Attachment added: ifconfig.txt https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294747/+files/ifconfig.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
** Attachment added: ifconfig.txt https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294747/+files/ifconfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
** Attachment added: ps.txt https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294749/+files/ps.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
** Changed in: lxc (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
** Changed in: lxc (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Certainly. The service was already running, so I stopped and restarted it for good measure. root@srv-Ub1404:~# start lxc-net start: Job is already running: lxc-net root@srv-Ub1404:~# stop lxc-net lxc-net stop/waiting root@srv-Ub1404:~# start lxc-net lxc-net start/running I'm attaching `/var/log/upstart/lxc-net.log` ** Attachment added: lxc-net.log https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294857/+files/lxc-net.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
Certainly. The service was already running, so I stopped and restarted it for good measure. root@srv-Ub1404:~# start lxc-net start: Job is already running: lxc-net root@srv-Ub1404:~# stop lxc-net lxc-net stop/waiting root@srv-Ub1404:~# start lxc-net lxc-net start/running I'm attaching `/var/log/upstart/lxc-net.log` ** Attachment added: lxc-net.log https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294857/+files/lxc-net.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
`sudo netstat -nr` returns: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 my-net.1 0.0.0.0 UG0 0 0 eth0 my-net.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 `sudo netstat -lnp | grep 10.0` returns nothing. `traceroute 10.0.3.1` goes up my ISP's network, but after 8 hops there it only returns `* * *` for hops 9-30. If I interpret that correctly, 10.0.3.1 isn't anywhere on my local network (and of course I can't get into other people's so there's no point in trying for more hops). `dpkg -l | grep dnsmasq` returns: ii dnsmasq 2.68-1 all Small caching DNS proxy and DHCP/TFTP server ii dnsmasq-base2.68-1 amd64Small caching DNS proxy and DHCP/TFTP server And, finally, `dpkg -l | grep lxc` returns: ii liblxc1 1.0.6-0ubuntu0.1 amd64Linux Containers userspace tools (library) ii lxc 1.0.6-0ubuntu0.1 amd64Linux Containers userspace tools ii lxc-templates 1.0.6-0ubuntu0.1 amd64Linux Containers userspace tools (templates) ii python3-lxc 1.0.6-0ubuntu0.1 amd64Linux Containers userspace tools (Python 3.x bindings) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1367495] Re: Bridge still not created if bind9 is on
`sudo netstat -nr` returns: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 my-net.1 0.0.0.0 UG0 0 0 eth0 my-net.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 `sudo netstat -lnp | grep 10.0` returns nothing. `traceroute 10.0.3.1` goes up my ISP's network, but after 8 hops there it only returns `* * *` for hops 9-30. If I interpret that correctly, 10.0.3.1 isn't anywhere on my local network (and of course I can't get into other people's so there's no point in trying for more hops). `dpkg -l | grep dnsmasq` returns: ii dnsmasq 2.68-1 all Small caching DNS proxy and DHCP/TFTP server ii dnsmasq-base2.68-1 amd64Small caching DNS proxy and DHCP/TFTP server And, finally, `dpkg -l | grep lxc` returns: ii liblxc1 1.0.6-0ubuntu0.1 amd64Linux Containers userspace tools (library) ii lxc 1.0.6-0ubuntu0.1 amd64Linux Containers userspace tools ii lxc-templates 1.0.6-0ubuntu0.1 amd64Linux Containers userspace tools (templates) ii python3-lxc 1.0.6-0ubuntu0.1 amd64Linux Containers userspace tools (Python 3.x bindings) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367495 Title: Bridge still not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242914] Re: tlmgr unable to set up TLPDB
@Robert yes, you would, as this bug appears in the version of TeXlive contained in the official repository. Purge TeXlive again, but next time follow the instructions on https://www.tug.org/texlive/quickinstall.html to install a vanilla instance of TeXlive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242914 Title: tlmgr unable to set up TLPDB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1242914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242914] Re: tlmgr unable to set up TLPDB
@YihuiXie(xie) of course; I don't mean to imply the bug is any less important to address because of this workaround. Just to point @RobertBlankenship in the right direction (as he indicated he wishes). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242914 Title: tlmgr unable to set up TLPDB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1242914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242914] Re: tlmgr unable to set up TLPDB
@Robert what response do you get when you type `whereis tlmgr`? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242914 Title: tlmgr unable to set up TLPDB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1242914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282518] [NEW] Hotkey assignment for Next Source under Text Entry Settings deactivates at startup
Public bug reported: When I originally upgraded to Saucy, I encountered the same bug many reported with using modifier-only combinations to switch keyboard layout (but 1218322?). Thankfully, that was swiftly resolved with suggested updates (I didn't employ any special ppa solution back then, but rather temporarily used a combination I wasn't used to). However, lately I've noted that whenever I restart Ubuntu my designated combination of ALT+SHIFT L stops working to switch layout. It's still listed as the combination in Text Entry Settings Switch to next source and in Settings Keyboard Shortcuts Typing Switch to next source, but it doesn't work. However, if I use either console to designate a new combination (doesn't matter which), then return to ALT+SHIFT L, it works again (for the duration of my session). This bug is unrelated to modifier-only combination: the same behavior is exhibited when I choose ALT+= for my combination (on new session, combination is still listed, but doesn't work until it is reset). However, this *doesn't* happen when I use 3-key-combinations like ALT+SHIFT+Q or ALT+SHIFT++. To be clear: this is a relatively new bug (last month, for sure). I was happily using ALT+SHIFT L for some time now. To replicate this bug: 1. Go into Text Entry settings. 2. Click on the combination for Switch to next source, hold ALT then click and release =. 3. Log out, log back in. 4. Hit ALT+=. The layout should change to the next source, but (for me, at least) it doesn't. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Feb 20 12:43:22 2014 InstallationDate: Installed on 2012-11-23 (453 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-10-18 (124 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282518 Title: Hotkey assignment for Next Source under Text Entry Settings deactivates at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1282518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242914] Re: tlmgr unable to set up TLPDB
@NorbertPreining: Ok, that's reasonable enough (though not clear from previous remarks; certainly, I see no reason to close this bug considering it is still present in Ubuntu). If it helps anyone, this issue affected me on a machine which shouldn't have had `texlive-base' installed; something in the process of upgrading Ubuntu to 13.10 (from 13.04) created another instance of `tlmgr' in addition to the one present from a vanilla installation of texlive 2012. Purging texlive (by following the steps outlined in http://tex.stackexchange.com/a/95502/46339) and performing a clean install of vanilla texlive 2013 cleared the issue (as was to be expected, I suppose). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242914 Title: tlmgr unable to set up TLPDB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1242914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242914] Re: tlmgr unable to set up TLPDB
@NorbertPreining have you noted the fact that this error is given in response to tlmgr init-usertree as well? It seems one cannot set up user-mode. I presume that's not how it's *supposed* to work? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242914 Title: tlmgr unable to set up TLPDB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1242914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
