I attached a modified version of 55NetworkManager that simply calls
stop network-manager and start network-manager, respectively. This
works for me, i.e. I have a working network connection after resume,
which I hadn't before (Mint 13 Xfce, kernel 3.13.0-43-generic, ThinkPad
R500).
Please
I can confirm the workaround in #8 works for me.
Thanks, much appreciated.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1314058
Title:
app_stack.so: undefined symbol:
I agree, this should be fixed asap!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1230917
Title:
php5-fpm logrotate errors after package switched to upstart
To manage notifications
Public bug reported:
With the previous vivid kernel 3.16.0-28-generic,lxc-start-ephemeral -o
containername works fine. With the current 3.18.0-8-generic it fails
with the container failed to start. This is reproducible in a clean
cloud VM:
$ sudo apt install lxc
$ sudo lxc-create -t busybox -n
Adding linux tasks. This overlayfs change might be due to its
upstreamization, or unintended, so please invalidate if appropriate.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
This is not a sensible solution.
There are numerous patches already to fix the original problem:
On launchpad:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/906347 (mine).
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1007924
On debian:
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1409425
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
** Changed in: linux (Ubuntu)
Status: Incomplete = 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/1409425
Title:
lxc-start-ephemeral stops working with kernel 3.18 -
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = 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/1409425
Title:
Here are the requested informations:
$ ldd /usr/bin/qemu-system-i386 |grep usb
libusb-1.0.so.0 = /lib/libusb-1.0.so.0 (0x7fdcf11e6000)
libusbredirparser.so.1 =
/usr/lib/x86_64-linux-gnu/libusbredirparser.so.1 (0x7fdcf0fde000)
$ dpkg -l | grep libusb
ii libgusb2:amd64
Has anyone tried to get the patch into an update for 12.04 in the past
seven months?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1007924
Title:
pm-utils uses wrong interface
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1409499
Title:
package clamav-milter 0.98.5+addedllvm-0ubuntu0.14.04.1 failed to
** Summary changed:
- pm-utils reset the vm.dirty_ratio and vm.dirty_background_bytes variables
+ pm-utils reset the vm.dirty_ratio and vm.dirty_background_ratio variables
** Description changed:
On a desktop system, on AC power, pm-utils reset the vm.dirty_ratio and
-
** Description changed:
On a desktop system, on AC power, pm-utils reset the vm.dirty_ratio and
vm.dirty_background_ratio at boot time (which also reset the
vm.dirty_bytes and vm.dirty_background_bytes variables).
When setting these variables using sysctl.conf, they are silently reset
Public bug reported:
ubuntu 14.04
i don't have more info
but this happens when the system
tries to update clam
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: clamav-milter 0.98.5+addedllvm-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux
Just a remark as the new maintainer of dbconfig-common in Debian.
Unfortunately, the behavior that you want is the wrong solution to the
problem, as it would blindly overrule system administrators decisions.
Therefore this bug is in essence wontfix.
However, what is a legitimate question is that
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-core (Ubuntu Trusty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Changed in: nginx (Debian)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1098654
Title:
nginx vulnerable to MITM Attack [CVE-2011-4968]
Scratch my supposed fix.; the service started up fine after the reboot,
but failed after any subsequent restarts. I'm currently stuck running
it in debug as well. Box was installed as 14.04 x64 from scratch; not a
12.04 upgrade.
$ dpkg-query --show amavisd-new
amavisd-new 1:2.7.1-2ubuntu3
19 matches
Mail list logo
