I'm seeing this with 16.10 i.e no vpn nameservers or domains added to
resolv.conf when the vpn activated. Doing as suggested in prev(#62) and
commenting out 'dns=dnsmasq entry' gets the nameservers appearing in
resolv.conf, but *not* the extra domains. So progress, but not there
yet!
--
You
I suspect this bug has aged out of existence now...bit disappointing to
see now *actual* updates to reflect progress mind you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/311637
Title:
dmraid
...*no* updates was what I meant to say.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/311637
Title:
dmraid enabled on install target even if disabled during installation
To manage notifications
Public bug reported:
The init script for pgpool2 merely returns 'exit 3' for the reload
operation. This is less than ideal. It should either:
- fail noisily with 'not implemented' or (better)
- do a pgpool reload (i.e actually reload the config)
The currert state of affairs is confusing at
** Patch added: Something like this should be ok
https://bugs.launchpad.net/ubuntu/+source/pgpool2/+bug/1433403/+attachment/4348640/+files/pgpool2.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see that they have releases here https://github.com/openstack/python-
troveclient/releases , I'll take a look at them and see which one(s)
have the api to match the trove server package we have in Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Looks like /python-troveclient-1.0.4 is where the relevant changes
occur.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315255
Title:
Unable to create instance when multiple networks found
To
It looks like they are not tagging or branching the python-troveclient
code sufficiently, e.g:
$ cd python-trove
$ git branch -a
* master
remotes/origin/HEAD - origin/master
remotes/origin/master
I merely patched the package with the latest client, which is what you
guys should probably do -
Right, that does seem to improve things immensly. I'm still seeing a
'disconnected' alerm from network manager, but it does not *actually*
seems to be disconnecting eth0.
I'm still seeing a process appearing:
root 26471 0.0 0.0 10232 2412 ?Ss 13:04 0:00
dhclient -1 -v -pf
It has occurred to me that I have not rebooted since installing
lxc...I'll try that just in case it makes a difference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331276
Title:
Starting lxc
Sorry - I should have been clearer that the 'permission denied' errors
where from 'destroy lxc1' and the process concerned was dhcp. Yeah,
amending apparmor as indicated sorts that problem out.
Rebooting made no difference (worth checking I guess).
With respect to the eth0 business, I note a lot
** Attachment added: Syslog activity when the domain is started from virsh
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1331276/+attachment/4135213/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Some more info:
Before I do virsh -c lxc:/// start lxc1 here are running dhcp processes:
root 1707 0.0 0.0 10232 3696 ?S10:04 0:00
/sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf
/run/sendsigs.omit.d/network-manager.dhclient-eth0.pid -lf
How I created the container:
(root) $ apt-get install lxc
(root) $ lxc-create -t ubuntu -n lxc1
(root) $ /etc/libvirt/lxc/lxc1.xml # see above
(root) $ virsh -c lxc:///
start lxc1
Host net config
$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
Public bug reported:
Starting an lxc container, defined via the XML below, results in the
host's eth0 getting disconnected. I see DHCP messages beng generated and
notice this process:
root 5640 0.0 0.0 10232 2416 ?Ss 13:05 0:00
dhclient -1 -v -pf /run/dhclient.eth0.pid -lf
Public bug reported:
Starting an lxc container, defined via the XML below, results in the
host's eth0 getting disconnected. I see DHCP messages beng generated and
notice this process:
root 5640 0.0 0.0 10232 2416 ?Ss 13:05 0:00
dhclient -1 -v -pf /run/dhclient.eth0.pid -lf
Ping...
This looks to be pretty straightforward to solve - the client api set
should really match the servers one. You guys have been so proactive
with updating to the current *server* capabilities - but it is sad that
this is essentially let down by having the older client that is
completely
Further examination shows that the issue appears to be confined to the
trove client package (python-troveclient) only. The server packages have
been updated and have the nic parameter in their various object and
method definitions, however the client code has not been updated to
match.
I
Public bug reported:
Ubuntu version 14.04 on x84_64.
This has been noted (and fixed) upstream:
https://bugs.launchpad.net/trove/+bug/1257838
I am running into this - in fact anyone will run into this if they
configure neutron. Is an update from the latest icehouse branch planned?
** Affects:
Interesting - sorry to state obvious, but you did run update-grub
afterwards, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876520
Title:
mouse cursor gone
To manage notifications about
I seem to have run into this with lightdm 1.0.1-0ubuntu6 (oneiric
64-bit). Doing some poking around I note that restarting lightdm from a
terminal (i.e /etc/init.d/lightdm restart or similar) makes the cursor
reappear properly again. Further experimentation seems to point to some
interaction with
Dennis, I have run into this on oneiric too (see bug 818852). I found
removing splash from GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub
results in the cursor showing properly every boot. It would be
interesting to see if this works for you too (remember to run update-
grub...).
--
You
Awesome, glad it helped!
I also note that my hardware is an Asus mobo (a8v-x) with Radeon gpu
(9800 pro), so we are probably both running the radeon Xorg driver. So
this guy could be the culprit (might be interesting to switch login
display managers to gdm and see if mouse issue persists)...
--
Hmm, interesting - the trick seems to help with lightdm 1.0.1 (see bug
876520). However over there both of us are running radeon gpus, so there
might be another factor in play too. I did wonder if it might be
interesting to switch to gdm and see if the mouse cursor is still
missing then (would
I think I have a workaround for this. I noticed that:
gconf:/apps/update-notifier/regular_auto_launch_interval = 7
and amended this to 1. Now update manager pops up every day. This is
probably inelegant (i.e bash update manager with a hammer kind of), but
at least I'm seeing updates!
--
Update
I also am not seeing the update manager pop up after a post Karmic
upgrade that (otherwise) went very smoothly. Arch is amd64. Update
manager is set to check daily. If I run it from the menu I see the
updates ok (and can install 'em).
--
Update manager not showing notification of daily updates
Public bug reported:
Binary package hint: initramfs-tools
The Ubuntu version is 8.10 Server x86 (no updates, directly from the cd)
The hardware is Supermicro P3TDER with Promise TX4000 fake raid card.
I'm using software (md) raid, so *disable* SATA/fake raid during the
install. However on 1st
27 matches
Mail list logo
