Public bug reported:
i don't know
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: squid3 3.1.19-1ubuntu3.12.04.2
ProcVersionSignature: Ubuntu 3.2.0-61.93-generic-pae 3.2.55
Uname: Linux 3.2.0-61-generic-pae i686
ApportVersion: 2.0.1-0ubuntu17.6
AptOrdering:
libwebp2: Install
Public bug reported:
I'm using apt-cacher-ng on my workstation, so my local apt specifies
Acquire::http { Proxy http://127.0.0.1:3142;; };
That won't work in a container, because there the IP is 10.0.3.1.
But with lxc-ubuntu's choose_container_proxy() there is no way to get it
right:
- If I
Hmm, and just after filing this bug and after I removed caches, old
containers, etc. and run this again with HTTP_PROXY=http://10.0.3.1:3142
it works again (as it used to for a long time, until yesterday and this
morning). So apparently something weird on my side, sorry for the noise!
** Changed
Thanks Hugo, that works for me
--
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/1310552
Title:
could not extract the package.xml file from
Hi Serge,
I keep getting the crash notification due to kvm crashes with the same
bug title as this one. I see that the status is Fix Released, I'm on
precise and fully up-to-date.
My package is:
ii qemu-kvm 1.0+noroms-0ubuntu14.14
Full virtualization on i386 and
From original packages I have dependencies:
sudo apt-get install corosync-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libcfg-dev libconfdb-dev libcoroipcc-dev libcoroipcs-dev libcpg-dev
Public bug reported:
When trying to join a domain using realmd, this is displayed:
sysoperator@mem4:~$ realm join --verbose test2dc.mdom.com
* Resolving: _ldap._tcp.test2dc.mdom.com
* Performing LDAP DSE lookup on: 192.168.15.23
! Received invalid or unsupported Netlogon data from server
Adding hyperv seemed to work for me too.
--
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/1308341
Title:
Multiple CPUs causes blue screen on Windows guest
To manage notifications about
** Also affects: realmd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: sssd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Public bug reported:
I get this in a fresh install in Ubuntu 14.10 for Mysql server 5.6:
$ sudo mysqld start
2014-05-14 13:54:03 0 [Warning] Using unique option prefix key_buffer instead
of key_buffer_size is deprecated and will be removed in a future release.
Please use the full name instead.
Add my.cnf:
explicit_defaults_for_timestamp
Change key_buffer by key_buffer_size
Create folder:
sudo mkdir -p /var/lib/mysql/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
Then I get:
[ERROR] Fatal error: Can't change to run as user 'mysql' ; Please check
that the user exists!
Workaround:
cd /var/lib/mysql
sudo adduser mysql
sudo chown mysql:mysql -R /var/lib/mysql
Then I get:
[Warning] Using unique option prefix myisam-recover instead of myisam-
Try installing 'openipmi' - it should cause the modules to get loaded at
boot, and it is a Suggests of the ipmitool package.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/908112
Sorry Timo, just had to share the good news with my own little +1. :)
Thanks for the information regarding the process too as I was not aware
of that. I'm sure I speak for everone when I say we thank you for the
PPA to circumvent this issue until it arrives in the main repo. Your
time is
Sorry for the delay - I have enabled proposed and can confirm forced
curve25519-sha...@libssh.org works now :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1310781
Title:
bad
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1310781
Title:
bad bignum encoding for curve25519-sha256 at
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to swift in Ubuntu.
https://bugs.launchpad.net/bugs/1317147
Title:
Swift-proxy needs python-pecan =0.4.5, but
what i checked is a small application called udaddy which is part of the
librdmacm examples.
But this information I think is useless since the method which actually reveled
this issue is part of my own built private version of libibverbs.
however I'm intend to write you a small app to
This is linked to another dependency problem in bug
https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1317147.
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
The full fix can't be tested until we get the lxc fix pushed as well,
however the test22.sh testcase in the cgmanager-tests package tests the
getpidcgroupabs feature which is the cgmanager part of this fix. That
test passes.
** Tags removed: verification-needed
** Tags added: verification-done
I installed openipmi last night -- no joy.
What seems to work, at least for now is just calling modprobe to load
the ipmi modules in /etc/rc.local
I should probably mention I'm on 12.04 LTS, running the
LTSEnablementStack kernels.
--
You received this bug notification because you are a member
In response to comment #9 from Michael Schaller:
Robert, what are HWE kernels on Precise?
Which of these metapackages will install a HWE kernel?
linux-image-generic-lts-quantal
linux-image-generic-lts-raring
linux-image-generic-lts-saucy
linux-image-generic-lts-trusty
All of those install
I'm running 1.18.3 and I'm still seeing this..
Installed: 1.18.3-0ubuntu1~14.04.1~juju1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1306537
Title:
LXC local provider
the full fix requires an lxc patch, however I tested it by doing
sudo cgm create name=systemd u1
sudo cgm chown name=systemd u1 1000 1000
cgm movepid name=systemd u1 $$
cat /proc/self/cgroup | grep systemd
which gave the expected correct result (a cgroup ending in '/u1')
** Tags removed:
Public bug reported:
Run live session and install.
Internet connection works ok during install.
Boot to install - no internet available.
Commenting #dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf and
reboot.
No further issues.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package:
Attaching a diagram to outline the changes here and the upgrade path to
Trusty. The packaging is a bit complex due to the fact that some
packages upstream are virtual packages and this new package in Precise
is bridging the two.
** Attachment added: Package layout and upgrade flow
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1319536
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dnsmasq (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
I've just read through this thread with a view to wether we should
release a related OSSN.
From what I can tell, no fix was ever agreed on, is this likely to
change?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
You have been subscribed to a public bug:
Ubuntu 12.04 LTS has an old 1.5.0 version of ec2-api-tools. Amazon is
reporting that that the old versions of the tooling causing some
problems.
** Affects: ec2-api-tools (Ubuntu)
Importance: High
Assignee: Ben Howard (utlemming)
Public bug reported:
Ubuntu 12.04 LTS has an old 1.5.0 version of ec2-api-tools. Amazon is
reporting that that the old versions of the tooling causing some
problems.
** Affects: ec2-api-tools (Ubuntu)
Importance: High
Assignee: Ben Howard (utlemming)
Status: New
** Package
** Package changed: libvirt (Ubuntu) = qemu (Ubuntu)
** Also affects: qemu
Importance: Undecided
Status: New
--
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/1318830
Title:
Hi,
the cause of this particular bug was introduced during 2014, so could
not have been present in precise. We definately will want to figure out
the cause of your bug, so please open a new bug report using 'ubuntu-bug
qemu-kvm' immediately after a crash has happened.
Thanks!
** Also affects:
Public bug reported:
One of my VMs remounted its filesystem read-only; I discovered this in
the host's /var/log/libvirt/qemu/sec-trusty-amd64.log file:
2014-05-06 19:02:39.735+: shutting down
2014-05-07 18:44:45.578+: starting up
LC_ALL=C
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: etckeeper (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
Attached debdiff, although it is not particularly useful.
** Attachment added: Debdiff
https://bugs.launchpad.net/ubuntu/+source/ec2-api-tools/+bug/1319555/+attachment/4112692/+files/ec2-api-tools-debdiff.txt
--
You received this bug notification because you are a member of Ubuntu
Server
Attached branch updating tools to 1.6.13.0. Confirmed that it works.
** Description changed:
Ubuntu 12.04 LTS has an old 1.5.0 version of ec2-api-tools. Amazon is
reporting that that the old versions of the tooling causing some
- problems.
+ problems. Amazon is requesting the latest version
The verification of the Stable Release Update for corosync has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
Attached debdiff, although it is not particularly useful.
** Attachment added: Debdiff
https://bugs.launchpad.net/ubuntu/+source/ec2-api-tools/+bug/1319555/+attachment/4112691/+files/ec2-api-tools-debdiff.txt
--
You received this bug notification because you are a member of Ubuntu
Server
** Also affects: ec2-api-tools (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ec2-api-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1319555
Title:
update out-dated
This bug was fixed in the package corosync - 1.4.2-2ubuntu0.1
---
corosync (1.4.2-2ubuntu0.1) precise-proposed; urgency=low
[ Martin Loschwitz ]
* debian/control: Make sure that every library development package depends
on its library counterpath (Closes: #671843) (LP:
** Also affects: ec2-api-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ec2-api-tools (Ubuntu Utopic)
Importance: High
Assignee: Ben Howard (utlemming)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server
** Description changed:
Ubuntu 12.04 LTS has an old 1.5.0 version of ec2-api-tools. Amazon is
- reporting that that the old versions of the tooling causing some
+ reporting that that the old versions of the tooling is causing some
problems. Amazon is requesting the latest version of
Public bug reported:
Trusty 14.04 LTS x86_64 Server
The upstart script invokes php5-fpm with --nodaemonize.
This causes several options from the config file to be ignored,
including log file locations, pid file, and others. It also means that
logging is done to /var/log/upstart/ and is no
** Changed in: ec2-api-tools (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: ec2-api-tools (Ubuntu Precise)
Importance: Undecided = High
** Changed in: ec2-api-tools (Ubuntu Trusty)
Assignee: (unassigned) = Ben Howard (utlemming)
** Changed in: ec2-api-tools (Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
--
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/1319595
My workaround for now is to allow zfs module access to all users from the zfs
group, instead of only root.
This way the zfs command can be run by by users from that group.
/etc/udev/rules.d/91-zfs-permissions.rules
#Use this to add a group and more permissive permissions for zfs
#so that you
Sponsored for Utopic.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ec2-api-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1319555
Title:
update out-dated ec2-api-tools for 12.04
To manage notifications about this bug go to:
** Bug watch added: Samba Bugzilla #10607
https://bugzilla.samba.org/show_bug.cgi?id=10607
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=10607
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
The maas command line client is brittle to unexpected inputs. On trusty,
I tried to run the 'sudo maas createsuperuser' command that I used on
precise, quantal, and saucy, but it failed. I wanted detailed help, so I
ran 'maas -h', and that dumped a stack trace because the
I tested 1.5.1+bzr2269-0ubuntu0.1 (from trusty-proposed) by doing a
clean install, and enlisting/commissioning/stopping a node. I also
tested the upgrade path by installing the current trusty release
(1.5+bzr2252-0ubuntu1), enlisting/commissioning/starting a node, and
then upgrading to
I've marked this bug as affecting lxc, since the fix/workaround that
Charles and I came up with involves modifying abstractions/lxc
/container-base.
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** Changed in: lxc
Would it be possible to attach your local wordpress charm?
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: samba
Status: Unknown = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1310792
Title:
dfree command is not working anymore in samba
To manage
** Summary changed:
- juju-local LXC containers hang due to App Armor Denial of rpc_fsbind request
with local charms
+ juju-local LXC containers hang due to AppArmor denial of rpc_pipefs mount
with local charms
--
You received this bug notification because you are a member of Ubuntu
Server
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1317601
Title:
[SRU] SRU New upstream bugfix release of MAAS
To
On 15/05/14 09:22, Seth Arnold wrote:
Public bug reported:
The maas command line client is brittle to unexpected inputs. On trusty,
I tried to run the 'sudo maas createsuperuser' command that I used on
precise, quantal, and saucy, but it failed. I wanted detailed help, so I
ran 'maas -h',
** Also affects: maas
Importance: Undecided
Status: New
** Summary changed:
- maas command line client brittle to unexpected inputs
+ maas-cli stack trace if .maascli.db unreadable
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Importance: Undecided = High
That, therefore, makes this a packaging bug.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1319616
Title:
package samba-libs (not installed) failed to install/upgrade: 子程序 新的
Public bug reported:
For some unknown reason (config errror) that samba failed to upgrade
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: samba-libs (not installed)
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion:
Is there any reason you missed that that we can help to fix?
Only that in the middle of testing an update I followed the same
directions for precise, quantal, saucy, and noticed no problems until
trusty. Fair's fair, things change, but it would have been nice to have
a hint in the right
[Expired for indicator-datetime (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: indicator-datetime (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
[Expired for ntp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ntp (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
64 matches
Mail list logo
