The tests are successful with both the crun and runc runtimes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040483
Title:
AppArmor denies crun sending signals to containers (stop, kill)
To manage
As above, the tests specified for the SRU complete successfully with the
new packages installed.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
** Tags removed: mantic server-todo
--
You received this bug notification bec
There's a possible additional issue with runc apparmor in
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/2072452
that is affecting k8s in Noble. May be worth testing the fixed package
to see if it corrects that as well.
--
You received this bug notification because you are a member of Ubunt
Upstream fault report:
https://github.com/containerd/containerd/issues/10542
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072452
Title:
AppArmor denies crun sending signals to containers
To manag
unknown error after kill: runc did not terminate successfully: exit
status 1: unable to signal init: permission denied
** Also affects: runc (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/containerd/containerd/issues #10542
https://github.com/containerd/con
You are all very welcome to use the version in the Brightbox
Experimental PPA
(https://launchpad.net/~brightbox/+archive/ubuntu/experimental), which
has a Noble update with the fix in it.
Bear in mind the title of the PPA: "Here be dragons"
--
You received this bug notification because you are a
port.
> https://bugs.launchpad.net/bugs/2040483
>
> Title:
> AppArmor denies crun sending signals to containers (stop, kill)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptio
PR accepted upstream. I've backported the patch the oracular MP above.
What needs to be done now to get this into an SRU for noble?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040483
Title:
AppA
PR opened upstream: https://github.com/containers/common/pull/2004
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040483
Title:
AppArmor denies crun sending signals to containers (stop, kill)
To ma
ubuntu@srv-9vqc0:~$ sudo grep -r "runbindable*/*" /etc/apparmor.d
/etc/apparmor.d/abstractions/passt: mount options=(rw, runbindable) /,
ubuntu@srv-9vqc0:~$ sudo aa-logprof
ERROR: Operation {'runbindable'} cannot have a source. Source =
AARE('/')
HTH
--
You received this bug notification bec
I've pushed the changes based on your comments to the MP above. I've
left the signal set for podman as (int, quit, term, kill).
Do you think that signal set should be tighter, or is that a good
compromise?
If that seems ok with you, I'll happily handle the PR upstream at
GitHub.
--
You received
The debdiff is in the MP above.
Podman does try to kill the container itself, as the error trace above
testifies.
May 14 11:14:41 srv-omzr6 kernel: audit: type=1400
audit(1715685281.392:118): apparmor="DENIED" operation="signal"
class="signal" profile="containers-default-0.57.4" pid=7458
comm="co
Adding the podman signal line, and building a libpod that overrides the
default packages eliminates the errors I was getting.
All the tests in this ticket pass with the updated packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've built a backported 4.9.4 libpod for noble based on an updated
golang-github-containers-common including the above patch.
It's available from ppa:brightbox/experimental
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
The debdiff I've put together for oracular updates the patch to be a bit
more general and cover all the signals I've seen so far in testing. (As
well as dropping the other patch that has been incorporated upstream).
# Allow certain signals from OCI runtimes (podman, runc and crun)
signal (r
The patch above doesn't work as it stands. We are still getting signal
filters in the audit log
May 14 11:13:06 srv-omzr6 kernel: audit: type=1400 audit(1715685186.296:112):
apparmor="DENIED" operation="signal" class="signal"
profile="containers-default-0.57.4" pid=8031 comm="3" requested_mask="
Public bug reported:
On the latest LTS, aa-logprof does nothing other than fail with the
error
ERROR: Operation {'runbindable'} cannot have a source. Source =
AARE('/')
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: apparmor-utils 4.0.0-beta3-0ubuntu3
ProcVersionSignature: User Name 6
To move this on a bit more rapidly as it is a blocking issue for me.
It's the same version in Oracular at present. I've pushed the changes as
an MP against ubuntu/devel.
What needs to happen next?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Merge proposal linked:
https://code.launchpad.net/~neil-aldur/ubuntu/+source/golang-github-containers-common/+git/golang-github-containers-common/+merge/465970
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Wonderful. Thank you.
> On 7 Feb 2021, at 18:05, Dmitry Shachnev <1913...@bugs.launchpad.net> wrote:
>
> And finally it migrated.
>
> ** Changed in: puppet (Ubuntu)
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
I have prepared a 1ubuntu1 version with what I think is the missing
diff.
https://launchpad.net/~brightbox/+archive/ubuntu/experimental?field.series_filter=hirsute
which has been built from the following branch
https://code.launchpad.net/~neil-
aldur/ubuntu/+source/puppet/+git/puppet/+ref/ubuntu
** Changed in: puppet (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913557
Title:
Please merge 5.5.22-1 into hirsute
To manage notifications about this
Similarly the Debian package passes a local Autopkgtest
Following 4.3 here: https://packaging.ubuntu.com/html/auto-pkg-test.html
#executing-the-test
$ sudo autopkgtest puppet -U --apt-pocket=proposed=src:puppet -- qemu
autopkgtest-hirsute-amd64.img
Gives
autopkgtest [10:55:15]: test command4:
Are there know differences between the Debian CI and the Ubuntu CI?
Because it passes autopkgtest over there.
https://ci.debian.net/data/autopkgtest/testing/amd64/p/puppet/10026148/log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Backport to Focal available at
https://launchpad.net/~brightbox/+archive/ubuntu/experimental
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913567
Title:
Sync puppet 5.5.22-1 (universe) from Debian
Public bug reported:
Please sync puppet 5.5.22-1 (universe) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* d/t/control: fix second dep8 test by telling it to not use a proxy
for the "puppet" hostname, and allow stderr because of a ruby
deprecati
** Changed in: puppet (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913557
Title:
Please merge 5.5.22-1 into hirsute
To manage notifications about this
Public bug reported:
tracking bug
** Affects: puppet (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913557
Title:
Please merge 5.5.22-1 int
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: puppet 5.5.10-4ubuntu3
ProcVersionSignature: User Name 5.4.0-62.70-generic 5.4.78
Uname: Linux 5.4.0-62-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jan 27 17:11:14 2021
PackageArchi
*** This bug is a duplicate of bug 1875848 ***
https://bugs.launchpad.net/bugs/1875848
Public bug reported:
The puppet 5.5 version available in Focal throws a lot of ruby warnings,
which interferes with the puppet installation traces.
remote: /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: war
Public bug reported:
remote: ^[[1;31mError: Execution of '/usr/bin/gem install --no-rdoc --no-ri
uricp' returned 1: ERROR: While executing gem ... (OptionParser::InvalidOption)
remote: invalid option: --no-rdoc
remote: Did you mean? no-force^[[0m
remote: ^[[1;31mError: /Stage[main]/Mys_serv
If the fix is not in the security pocket, how does it get sorted if the
updates pocket is turned off?
I understood *-updates are only supposed to be recommended.
As I mentioned if you build an image with a tool like 'mkosi' which utilises
debootstrap and then cleans the cache, the partial direc
Public bug reported:
Clicking 'disable' on the IPv6 tag doesn't appear to remove auto-
configured IPv6 addresses or turn off the IPv6 operations on the
specified interface.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.8-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.
"I think you're trying to start dhclient on an interface that's already
setup."
It just triggers a lease refresh on the existing interface, which has
the same issue.
Nov 15 14:17:10 srv-ywz63 systemd-logind[981]: New session 27 of user ubuntu.
Nov 15 14:17:10 srv-ywz63 systemd[1]: Started Session
LGTM on bionic
ubuntu@srv-ywz63:~$ dpkg -l systemd | grep ii
ii systemd237-3ubuntu10.32 i386 system and service manager
ubuntu@srv-ywz63:~$ journalctl -b -u systemd-resolved | grep Started
Nov 14 17:05:43 srv-ywz63 systemd[1]: Started Network Name Resolution.
Nov 14 17:05:44 srv-y
For me the login screen hangs as the Ubuntu logo at the bottom of the
screen fades in.
The crashes are here
https://errors.ubuntu.com/user/9918ca952fad5050e5d19cd326c70f270fae7631e330cf3c0c0ee4c728f149c2412b9c7bbdbfed5f6d72b3f62f187ada199b6d5ac8043b4329d0bbe352b51487
--
You received this bug n
Public bug reported:
After package updates on 10/6/19 the login screen froze. Turning Wayland
off in the GDM configuration worked around the issue,
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu4.2
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: L
** Summary changed:
- Simplestreams is missing a dependency on gpg
+ Simplestreams
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827502
Title:
Simplestreams
To manage notifications about this bug
** Changed in: simplestreams (Ubuntu)
Status: New => Invalid
** Description changed:
- When installing in docker containers there is no gpg available for use
- by /usr/bin/sstream-sync
-
- Traceback (most recent call last):
- File "/usr/bin/sstream-sync", line 169, in
- main()
-
Public bug reported:
When installing in docker containers there is no gpg available for use
by /usr/bin/sstream-sync
Traceback (most recent call last):
File "/usr/bin/sstream-sync", line 169, in
main()
File "/usr/bin/sstream-sync", line 161, in main
tmirror.sync(smirror, cfg['path'])
I think just a delta change process would be fine. It's restarting when
there is no change in lease details, and just clogging up the logs.
btw I am not suggesting leaving dhclient there is a bug - hence the
title of the bug.
--
You received this bug notification because you are a member of Ubun
Public bug reported:
If a cloud server is upgraded from Xenial to Bionic, the dhclient system
remains in place and any DHCP lease refreshes cause a needless restart
of the system-resolved daemon
Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on ens3
to 10.226.209.105 por
Public bug reported:
When upgrading from Trusty to Xenial it is possible to have a disk that
is half empty but has run out of inodes due to uncleared kernel updates.
This of course causes the upgrade to fail with catastrophic and
irreversible results
Not sure what pre-flight checks upgrader does
For example proxy is LSB generated, not systemd native
$ systemctl status swift-proxy
● swift-proxy.service - LSB: Swift proxy server
Loaded: loaded (/etc/init.d/swift-proxy; generated)
Active: active (running) since Fri 2018-10-26 15:13:07 UTC; 1 weeks 2 days
ago
Docs: man:systemd-sys
Public bug reported:
The Debian upstream packages for swift have had Systemd unit support
since
swift (2.6.0-2) experimental; urgency=medium
[ Ondřej Nový ]
* Added Debian tests.
* Removed swift-init.
* Systemd support.
* Added container-sync config files.
* Changed all dependencies
Does the trick nicely. Thank you.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776927
Title:
RTNL assertion fai
Public bug reported:
Please sync conntrack-tools 1:1.4.5-1 (main) from Debian sid (main)
Explanation of the Ubuntu delta and why it can be dropped:
* d/p/enable-runtime-systemd.patch: Enable systemd runtime support by
default since the package is compiled with --enable-systemd
(LP: #176
Seems to do the trick
ubuntu@srv-uq8mr:~$ uname -a
Linux srv-uq8mr 4.15.0-23-generic #26~lp1776927 SMP Fri Jun 15 17:06:38 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
[ 307.632377] audit: type=1400 audit(1529163746.165:17): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="cri
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/diff/?id=8230819494b3bf284ca7262ac5f877333147b937
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776927
Title:
RTNL assertion
Public bug reported:
Running up two containers using ipvlan with IPv6 autoconf active
triggers an assertion failure in the kernel (cloud image running on
Brightbox)
Jun 14 15:16:37 srv-x3w2q kernel: RTNL: assertion failed at
/build/linux-uT8zSN/linux-4.15.0/drivers/net/ipvlan/ipvlan_core.c (110)
Public bug reported:
Please sync haproxy 1.8.3-1 (main) from Debian experimental (main)
Explanation of the Ubuntu delta and why it can be dropped:
* Backport of -x option from upstream haproxy to enable seamless
reloading of haproxy without dropping connections. This is enabled
by addi
Public bug reported:
Background installation of the package failed and stoppered up dpkg for
a month. There was no indication the update system wasn't work it.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tcpdump 4.9.2-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-97.120-generi
Public bug reported:
If you set the DAEMON_ARGS of etcd so that it runs in gateway or
grpc_proxy mode, the unit file will hang on startup
● etcd.service - etcd - highly-available key value store
Loaded: loaded (/lib/systemd/system/etcd.service; enabled; vendor preset: ena
Active: activating
This appears to be fixed in 3.1.3 of etcd where they have fixed the
sd_notify behaviour.
etcd v3.1.3 (2017-03-10)
- use machine default host when advertise URLs are default
values(localhost:2379,2380) AND if listen URL is 0.0.0.0
- fix 'etcd gateway' schema handling in DNS discovery
- fix sd_not
This doesn't appear to have hit the main archive. I'm still seeing
0.9.1-2 installed today on 16.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1635192
Title:
package depends on pep8 tool instea
The serial update is now in production. Latest zesty image we have is
from 15th Feb and is not picking up the network (probably as expected).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661693
Titl
Public bug reported:
ping to a mapped address
ping :::216.58.213.68
sends an ICMPv6 packet out onto the Internet with the mapped address in
the destination packet and the IPv6 address as the source. Mapped
addresses shouldn't appear on the public internet according to the RFC.
I would have
Following this recipe
http://costiser.ro/2016/07/07/overlay-tunneling-with-openvswitch-gre-
vxlan-geneve-greoipsec/#.WDwlxXecZmB
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645323
Title:
Openvsw
Public bug reported:
The Openvswitch IPSEC daemon fails to start
Nov 28 13:15:57 srv-yz20n systemd[1]: Starting LSB: Open vSwitch GRE-over-IPsec
daemon...
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]: * Starting
ovs-monitor-ipsec
Nov 28 13:15:58 srv-yz20n python[18360]: ovs| 0 | ovs-m
Added both cloud-ini t and init-system-helpers from proposed to the
standard Xenial cloud image
(com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:16.04:amd64/20160907.1/disk1.img)
on a suitably sized server.
Reset the cloud init with rm -rf /var/lib/cloud/instances/*, shutdown
the server
Have we back ported the init-system-helpers changes to Xenial?
I'm only seeing 1.29ubuntu2 this morning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576692
Title:
fully support package installat
Martin,
Probably worth noting that this impacts upon the configuration systems
as well. I'm using the PostgreSQL puppet configuration system, and that
will sit in a loop waiting for PostgresQL to come up before moving onto
the next stage of the configuration.
So if you are using puppet within clo
Public bug reported:
Got the error:
Can't locate File/Copy/Recursive.pm in @INC (you may need to install the
File::Copy::Recursive module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1
/usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/
SRU Verification performed. The proposed package corrects the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521302
Title:
gnome-terminal maximize than un-maximize behaves odd
To manage no
Has the SRU process been kicked of for Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521302
Title:
gnome-terminal maximize than un-maximize behaves odd
To manage notifications about this b
Public bug reported:
If bootstrapping a machine on a trusty cloud image and then directly
installing the gui:
/usr/bin/juju bootstrap && /usr/bin/juju deploy juju-gui --to 0 &&
/usr/bin/juju expose juju-gui
The installation of the charm fails after the bootstrap.
Bootstrapping environment "manu
Public bug reported:
If I have 'prefer-ipv6' set and bootstrap a manual environment, then
the dns-name and public address entries show the IPv6 address, not the
dns-name for that IPv6 address - even though it is available via a DNS
PTR record.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package
Public bug reported:
The tools stream for juju doesn't have tools for 'wily' that correspond
with the version of the packages in the main repository.
ubuntu@srv-2f16s:~$ juju --version
1.22.6-wily-amd64
From
https://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju:released:tools.json
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410288
Title:
qemu-img conversion to qcow2 hangs with blank image less than 100kiB
T
Workaround is to 'fallocate'. Problem seems to be linked to files with
sparse holes in them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410288
Title:
qemu-img conversion to qcow2 hangs with blan
Public bug reported:
If you try to convert a blank image to qcow2 that is less than 100kiB in
size then qemu-img hangs trying to seek to the end of the file.
$ truncate --size 102399 /tmp/temp
$ qemu-img convert -p -O qcow2 /tmp/temp /tmp/temp2.qcow2
I'm finding this on all versions of qemu-img
ubuntu@srv-3wzed:~$ uname -a
Linux srv-3wzed 3.2.0-69-virtual #103-Ubuntu SMP Tue Sep 2 05:28:41 UTC 2014
i686 i686 i386 GNU/Linux
ubuntu@srv-3wzed:~$ dpkg -s qemu-utils | grep Version
Version: 1.0+noroms-0ubuntu14.20
ubuntu@srv-3wzed:~$ qemu-img convert -O qcow2 -o ? a b
Supported options:
size
ubuntu@srv-puxvl:~$ uname -a
Linux srv-puxvl 3.2.0-70-virtual #105-Ubuntu SMP Wed Sep 24 20:06:46 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@srv-puxvl:~$ dpkg -s qemu-utils | grep Version
Version: 1.0+noroms-0ubuntu14.20
ubuntu@srv-puxvl:~$ qemu-img convert -O qcow2 -o ? a b
Supported options
gt; qemu-img segmentation fault when asking for options
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions
>
--
Neil Wilson
--
You received this bug notification because you are a member of Ubun
Public bug reported:
When you ask for options for a command on the precise version of qemu-
img
qemu-img convert -O qcow2 -o ? a b
The tool seg faults:
Supported options:
size Virtual disk size
backing_file File name of a base image
backing_fmt Image format of the base imag
>From RH Bug list:
It appears the cause was identified and fixed in the latest haproxy upstream
release, 1.5.7. From the release announcement on the haproxy mailing list:
- John Leach reported an interesting bug in the way SSL certificates were
loaded : if a certificate with an invalid subj
The issue seems to be caused by a self-signed cert we're using. A cert
from a CA seems to work as expected.
** Attachment added: "ssl_cert.pem.orig.fixed"
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1383704/+attachment/4241193/+files/ssl_cert.pem.orig.fixed
--
You received this b
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383704
Title:
Can't switch off SSLv3 cipher groups in haproxy
To manage notifications abou
gs.launchpad.net/bugs/1068756
>
> Title:
> IPv6 Privacy Extensions enabled on Ubuntu Server by default
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+subscriptions
--
Neil Wilson
--
You received this bug
-
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1068756
>
> Title:
> IPv6 Privacy Extensions enabled on Ubuntu Server by default
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1068756
>
> Title:
> IPv6 Privacy Extensions enabled on Ubuntu Server by default
>
> To manage notifications about this bug go to:
> https://bugs
gs.launchpad.net/ubuntu/+source/cloud-init/+bug/1073204/+subscriptions
--
Neil Wilson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073204
Title:
ssh-authkey-fingerprints fails on boot
To m
Public bug reported:
The version of the requests library on Trusty uses 'data' as the
positional argument.
File "/usr/lib/python2.7/dist-packages/ftpcloudfs/fs.py", line 66, in
request_x_forwarded_for#012fn(method, url, body=body,
headers=headers)#012TypeError: request() got an unexpected key
It would be as well to try it out - particularly as the package has been
updated recently.
I tried a fresh install of Trusty and when 'vmtoolsd' is running from
the 'open-vm-tools' package, the output from 'vmware-toolbox-cmd stat
hosttime' and 'date' are the same after a restore from vmware susp
Barry,
Can you check you VMWare settings for the virtual machine and check that
'synchronise time' is checked in the Advanced Section.
Also do you have the 'open-vm-tools' installed (i.e. is vmtoolsd running
which is what does the time sync to the Host every 60 seconds).
--
You received this bu
I don't see the issue on Windows XP. Only when running Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157914
Title:
time never catches up to reality after VM sleep
To manage notifications a
Public bug reported:
New 13.10 installation, with simplestreams package and a copy of the
'hook-debug' script in bin in the home directory.
When I run
sstream-sync --max 1 --verbose --hook=bin/debug http://cloud-
images.ubuntu.com/releases
I get
Traceback (most recent call last):
File "/usr/
** Changed in: indicator-datetime (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195169
Title:
time and date doesn't update on resume in VM fusion
To manag
No it's both.
The system date is wrong. Nothing appears to be picking up the resume
event (assuming such a thing exists).
>From the help on 'synchronise time' in VM Fusion:
"You can configure whether the clock on the guest operating system is
synchronized with the clock on the host.
If you turn
Public bug reported:
If you're running ubuntu within VM Fusion and you suspend the Ubuntu VM
using the suspend and resume functions within VM fusion then the time
and date doesn't synchronise when the VM is resumed.
The work around is to switch to manual and them back to automatic to
force an NTP
v6addr Scope:Global
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1068756
>
> Title:
> IPv6 Privacy Extensions enabled on Ubuntu Server by default
>
> To manage notifications about thi
his bug go to:
> https://bugs.launchpad.net/friends/+bug/1167205/+subscriptions
>
--
Neil Wilson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1167205
Title:
Twitter integration appears to
sudo apt-get install friends-app
[sudo] password for neil:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package friends-app
Apparently it's in universe. How does that work then?
** Also affects: friends
Importance: Undecid
Public bug reported:
The online account screen is saying that no application is installed
which integrates with the Twitter account
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: friends-twitter 0.1.3daily13.04.05-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
Uname: Linux
Public bug reported:
On this laptop, the lightbox overlays for the dash and particularly the
logout and shutdown screens are too transparent - so much so that I
can't read what they say.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-1
Public bug reported:
If I log out on raring and back in again I get:
Apr 10 09:09:52 lenovo-3000-n100 pulseaudio[14091]: [pulseaudio]
socket-server.c: bind(): Address already in use
Apr 10 09:09:52 lenovo-3000-n100 pulseaudio[14091]: [pulseaudio] module.c:
Failed to load module "module-esound-p
Retested with the mainline kernel requested and the fault cannot be
replicated on that kernel.
However X came up in VESA mode rather than the usual Intel driver and
the framebuffer didn't show on boot.
The drm device (i915) is missing from the X config and the boot
sequence.
** Tags added: kern
neil@lenovo-3000-n100:~$ dmesg | grep -i synaptic
[ 15.312762] psmouse serio4: synaptics: Touchpad model: 1, fw: 6.2, id:
0x1a0b1, caps: 0xa04753/0x20/0x0, board id: 3655, fw id: 187194
[ 15.407465] input: SynPS/2 Synaptics TouchPad as
/devices/platform/i8042/serio4/input/input7
--
You
Public bug reported:
A common problem has popped back up again in raring and quantal (but was
ok in the precise I've just upgraded from).
The Touchpad is regularly losing sync during operation, which causes
jerky operation at best and at worst loses trackpad key function.
Apr 5 17:40:47 lenovo-
* place in
> server environments.
>
> -Tim
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1068756
>
> Title:
> IPv6 Privacy Extensions enabled on Ubuntu Server by default
>
> To man
1 - 100 of 1276 matches
Mail list logo
