Public bug reported:
Redirection to an empty variable causes `dash` to exit abnormally via
SIGSEGV.
1) $ lsb_release -rd
Description:Ubuntu 16.04.5 LTS
Release:16.04
2) $ apt-cache policy dash
dash:
Installed: 0.5.8-2.1ubuntu2
Candidate: 0.5.8-2.1ubuntu2
Version table:
***
Public bug reported:
The problem is incorrect backporting of [1] to the Ubuntu Trusty kernel
[2].
While original patch moves `dm_get_live_table` to the appropriate
section mutex lock the backported code just adds another call to it
under the mutex leaving the original call under spinlock in
Here is the updated patch for the bug.
All it does is merely setting `tcg_commit' function as
`log_global_start' callback. `tcg_commit' is then flushes all the
appropriate TLBs on `memory_log_global_start' call.
** Patch added: "more clean solution"
Here is the updated patch for the bug.
All it does is merely setting `tcg_commit' function as
`log_global_start' callback. `tcg_commit' is then flushes all the
appropriate TLBs on `memory_log_global_start' call.
** Patch added: "more clean solution"
Applying the attached patch I was able to do around 300 migrations back
and forth successfully.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1493049
Title:
memory corruption during
Applying the attached patch I was able to do around 300 migrations back
and forth successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493049
Title:
memory corruption during live-migration
@serge-hallyn,
This patch is exactly what fixes the problem for me (was able to do
around 150 successful migrations with it).
However, this should be rewritten to only contain exactly calls to
tlb_flush when in TCG mode so there is no extra code and no unrelated
changes.
The reason patches are
@serge-hallyn,
This patch is exactly what fixes the problem for me (was able to do
around 150 successful migrations with it).
However, this should be rewritten to only contain exactly calls to
tlb_flush when in TCG mode so there is no extra code and no unrelated
changes.
The reason patches are
Public bug reported:
[Impact]
* Live-migration of QEMU instances in pure-emulation (TCG) mode
[Test Case]
HOW TO REPRODUCE
1. Run a QEMU instance with a simply VM inside it. The VM should have as few
running daemons as it is posible.
2. Live migrate machine back and forth a few times. Use
Public bug reported:
[Impact]
* Live-migration of QEMU instances in pure-emulation (TCG) mode
[Test Case]
HOW TO REPRODUCE
1. Run a QEMU instance with a simply VM inside it. The VM should have as few
running daemons as it is posible.
2. Live migrate machine back and forth a few times. Use
There is no memory_region_get_dirty_log_mask in the 2.0.0, this was only
introduced later. Strictly speaking, 2.0.0 is quite different from 2.4.0
in this matter but I checked the code logic here and it should be good.
Yes, I was not sure what versions it affects so I only referenced
Trusty. If
There is no memory_region_get_dirty_log_mask in the 2.0.0, this was only
introduced later. Strictly speaking, 2.0.0 is quite different from 2.4.0
in this matter but I checked the code logic here and it should be good.
Yes, I was not sure what versions it affects so I only referenced
Trusty. If
It could be but I will require logs from all the services to be sure.
I think I need to create a log-gathering script.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297849
Title:
[SRU] Virtual
The libvirt code providing selective block migration in case of NBD
migration (non-tunnelled one) have been merged:
https://bugzilla.redhat.com/show_bug.cgi?id=1203032
How can we progress on this issue?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
The libvirt code providing selective block migration in case of NBD
migration (non-tunnelled one) have been merged:
https://bugzilla.redhat.com/show_bug.cgi?id=1203032
How can we progress on this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Can you please provide the logs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297849
Title:
[SRU] Virtual private network connection fails after distribution
upgrade due to outdated Network
@Mathieu,
The patch is not appropriate for the upstream because the upstream has
this code removed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297849
Title:
[SRU] Virtual private network
@Roman, have you tried to reboot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297849
Title:
[SRU] Virtual private network connection fails after distribution
upgrade due to outdated Network
** Description changed:
[Impact]
* People who are using VPN services (of any kind, using vpnc, openvpn, pptp,
etc.
[Test Case]
HOW TO REPRODUCE
1. Upgrade to a newer Ubuntu release.
2. Using the Network Manager application, try to start a virtual private
network connection.
@Marc, the version in the comment with instructions is for the Trusty
and Utopic. The 0.9.10.1-0ubuntu5~fixed is for Vivid.
Can you please show me the output of the following command:
dpkg-query -q network-manager-applet
--
You received this bug notification because you are a member of Ubuntu
I have uploaded a fixed package for Ubuntu Vivid to the my PPA as well:
https://launchpad.net/~pboldin/+archive/ubuntu/nm
Take a look at the https://bugs.launchpad.net/ubuntu/+source/network-
manager-vpnc/+bug/1297849/comments/107 for instructions.
--
You received this bug notification because
If I'm right the fix I've already provided in PPA for the Utopic and
Trusty should work for Vivid as well. The problem is I have not really
compiled it for Vivid yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is a mistery we yet have to solve.
But the assumption on the availability of Shell for the proper operation
of nm-applet is not a right thing to do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Benjamin, I could gather all the logs at my computer if I wanted so --
I had exact the same problem.
Yet, I do think that the fix provided by me is a correct one and there
is no necessity in debugging the problem further.
--
You received this bug notification because you are a member of Ubuntu
@Lonnie,
Just run a `nm-applet' and see if there is messages that the `Shell
version is unable to be found.' or alike.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297849
Title:
[SRU] Virtual
LocutusOfBorg (or should I call you Captain Picard? ;-),
Will this patch be enough for you or is there some more actions I should
take on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297849
Marc, I have uploaded a version for the Ubuntu Utopic.
Please try again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297849
Title:
Virtual private network connection fails after distribution
We have a similar problem with `seabios' but upgrading to 1.7.5 is not
helping. https://bugs.launchpad.net/fuel/+bug/1435501
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to seabios in Ubuntu.
https://bugs.launchpad.net/bugs/1318803
We have a similar problem with `seabios' but upgrading to 1.7.5 is not
helping. https://bugs.launchpad.net/fuel/+bug/1435501
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318803
Title:
FreeBSD
So I managed to provide an PPA with network-manager-applet built with my
fix presented above.
You can use updated package by running:
$ sudo add-apt-repository ppa:pboldin/nm
$ sudo apt-get update
$ sudo apt-get dist-upgrade -y
It should install version 0.9.8.8-0ubuntu4.4~fixed:
$ dpkg-query -s
Well, I provided the patch that works for me (I have built an updated
package for myself).
I can provide a PPA for you to check if it fixes your problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I would like any of you guys to cooperate with my tightly to find the
root cause for that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297849
Title:
Virtual private network connection fails
You seem to have exactly the same problem as I had.
Please, try to run nm-applet with a debug enabled (if VPN is not
appearing at first run -- try to run it twice or so).
Anyway, it is not necessary for you to connect to VPN --- just show the
debug output of nm-applet.
--
You received this bug
Trafex, please do the following to help me realise if my patch is
actually fixes the problem (as it does for me):
1. Kill the `nm-applet` from the shell:
$ killall nm-applet
2. Start nm-applet anew with the debug options specified above:
$ G_MESSAGES_DEBUG=nm-applet nm-applet nmapplet.log 21
3.
tallien,
Yes, you are right that the bug you experience is a different one.
Anyway it would help if you can enable the debug for the NetworkManager
itself and attach the resulting log?
To do so, please do the following:
1. Enable the `debug` syslog output. Find and edit the
tallien, sorry I forgot to say you to restart rsyslog:
$ sudo restart rsyslog
Changes to the configuration file won't work without that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297849
Title:
That is strange, but there are no traces of your attempt to activate in
VPN, at least I don't see any.
OK. I hope that someone with more experience in network-manager will
find this information useful.
If you want us to continue we can do so but in a private manner so we
don't flood the ticket.
Audun, can you please restart nm-applet with:
$ G_MESSAGES_DEBUG=nm-applet nm-applet
and attach the output somewhere? It should output a string like 'Unable
to find ShellVersion' in debug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
So, here is the details I got from investigating this bug.
The error is that during first start `nm-applet` is not registering
itself as a NetworkManager `secrets agent`. This is due to code in
function `constructor` of the file `src/applet.c` (nm-applet code) is
waiting for a
I'm attaching a workaround-like bugfix for this bug.
This emits a shell-notify notification even if there was no connection
to the `org.gnome.Shell` thus making the `nm-applet` to register itself
as a secrets agent.
** Patch added: network-manager-applet-1297849.patch
Public bug reported:
DKMS seems to use default (/usr/bin/gcc) GCC binary to build kernel
modules, without checking either it pointing to version of gcc used to
build kernel or not.
This can be problem when one uses update-alternatives to change default
GCC path to another GCC version. This
41 matches
Mail list logo
