I'm having trouble reproducing this...
What version of isc-dhcp-server is running here?
Does it change anything if you (manually) reorder the 2 subnets in
dhcpd.conf and restart the dhcp server?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Seen in 3.0.3-2, but likely to have been there for a while.
** Affects: node-gyp (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Patch added: "debian/rules patch to fix the issue."
3.0.3-2ubuntu1 uploaded with the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523699
Title:
install delivers non-executable usr/share/node-gyp/bin/node-gyp.js
To manage notifications about
Can we also get the output of the following on the cluster controller:
ip addr list; ip route list
thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521618
Title:
wrong subnet in DHCP answer
Version 1.0.7-1~12.04.1 works on precise, with the needed (hwe-t)
kernel.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449099
Version 1.0.7-1~12.04.1 works on precise, with the needed (hwe-t)
kernel.
** 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 bcache-tools in Ubuntu.
** Changed in: maas/1.9
Assignee: (unassigned) => LaMont Jones (lamont)
** Changed in: maas/trunk
Assignee: (unassigned) => LaMont Jones (lamont)
** Changed in: maas/trunk
Status: Triaged => In Progress
** Changed in: maas/trunk
Assignee: LaMont Jone
** Changed in: maas/1.9
Assignee: (unassigned) => LaMont Jones (lamont)
** Changed in: maas/trunk
Assignee: (unassigned) => LaMont Jones (lamont)
** Changed in: maas/trunk
Status: Triaged => In Progress
** Changed in: maas/trunk
Assignee: LaMont Jone
I forget exactly what the error message was, but I think it was the
difference between whatever output is, and that write wanted a
bytestring. -- it's possibl;e that should be
fout.write(unicode(output))...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
gconf2 3.2.6-3ubuntu5 (xenial) has gsettings-schema-convert requiring
python3, but without correct syntax:
gsettings-schema-convert --force --gconf --xml --schema-id
"org.freedesktop.ibus" --output lamont.in ../../data/ibus.schemas.in
File
I have verified this fix.
** 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 cloud-initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515661
Title:
[SRU]
I have verified this fix.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515661
Title:
[SRU] sync 14.04 cloud-initramfs-tools
bcache-tools_1.0.7-1~12.04.1 (in my ppa) has been tested and is known to
work. I'll be uploading that to precise-proposed shortly.
lamont
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-tools in Ubuntu.
bcache-tools_1.0.7-1~12.04.1 (in my ppa) has been tested and is known to
work. I'll be uploading that to precise-proposed shortly.
lamont
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449099
Of course, once the package is in the various -proposed, we'll do a
final round of testing, including upgrade testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509147
Title:
[SRU] MAAS 1.8.3
Of course, once the package is in the various -proposed, we'll do a
final round of testing, including upgrade testing.
--
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/1509147
Title:
Public bug reported:
A common name for bridge interfaces is 'br0'. Currently, the pre-up and
post-down scripts do not support those, so the interaface fails to
autocreate.
Seen on trusty (1.9-3ubuntu10) and confirmed as not fixed on xenial
(1.9-3.2ubuntu1)
** Affects: vlan (Ubuntu)
Public bug reported:
A common name for bridge interfaces is 'br0'. Currently, the pre-up and
post-down scripts do not support those, so the interaface fails to
autocreate.
Seen on trusty (1.9-3ubuntu10) and confirmed as not fixed on xenial
(1.9-3.2ubuntu1)
** Affects: vlan (Ubuntu)
the "2001::" IP would be the 2601:... IP address used throughout. Once
it is specifically routed to the fe80: IP for the host, then ipv6
connectivity works just fine to the 2601 IP (since no neighbor discovery
is involved -- it's a link address for nexthop.
I'll make some time to disable the
This is the actual and verified patch for 15.2.1-1ubutnu1
** Patch added: "lp1505748.diff"
https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/1505748/+attachment/4494713/+files/lp1505748.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: "patch for 13.2.0-1ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/1505748/+attachment/4494715/+files/lp1505748.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
attaching the correct patch
** Patch added: "Patch for 15.2.1-1ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/1505748/+attachment/4493628/+files/twisted.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Certainly by 13.2.0-1ubuntu1 (trusty), fromBytes blows up when handed an
ipv6 address, because of an assumption that the only valid use of a
colon is as part of a port specification. See also bug #1372767.
Patch attached which should fix the issue, though it is against
Public bug reported:
3 hosts involved here:
kailan is connected to a cisco switch, which is also connected to kurrat
(eth3), which is running a bridge with tigernut connected to eth1.
kurrat's controllers are 06:00.0 Ethernet controller: Intel Corporation
82574L Gigabit Network Connection,
If you change the IP address of the server, you need to dpkg-reconfigure
maas-region-controller.
** Changed in: maas
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If you change the IP address of the server, you need to dpkg-reconfigure
maas-region-controller.
** Changed in: maas
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
In cases where there is no clear "best default", a high-priority debconf
question is warranted. If the package is being installed on a machine
with multiple configured network interfaces, I don't think we have a
clear "best" answer. OTOH, I think that if there is only one interface,
then it
In cases where there is no clear "best default", a high-priority debconf
question is warranted. If the package is being installed on a machine
with multiple configured network interfaces, I don't think we have a
clear "best" answer. OTOH, I think that if there is only one interface,
then it
** Changed in: maas
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1272016
Title:
Which interface to bind maas-region-controller to should be a debconf
question
To
** Changed in: maas
Status: New => Triaged
--
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/1272016
Title:
Which interface to bind maas-region-controller to should be a debconf
** Also affects: bcache-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: bcache-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
** Also affects: bcache-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: bcache-tools (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When nickserv drops a user registration and ChanServCore::OnDelCore is
called, the pointer handling is wrong and sometimes results in a
SIGSEGV.
The attached patch fixes it.
** Affects: anope (Ubuntu)
Importance: Undecided
Status: New
** Patch added:
The issue only occurs when we have a non-trivial list of channels for
which the user is the founder, and there is no specified successor
founder. The following reproduces the issue handily:
as non-oper nick lj_test:
/msg nickserv register foobaz lam...@ubuntu.com
/join #chan1
/join #chan2
/msg
Looking at the changelog:
20111025: Drop bogus c_rehash on upgrades, ...
20110421: * Depend on openssl 1.0.0 and force a call of c_rehash so that we
have both the old and new style of symlinks. (Closes: #611102)
I fully suspect that the bug was introduced upstream in oct 2011.
If that's the
Public bug reported:
Found this (finally) upgrading a web server from lucid to precise (via
do-release-upgrade):
Preparing to replace ca-certificates 20141019ubuntu0.10.04.1 (using
.../ca-certificates_20141019ubuntu0.12.04.1_all.deb) ...^M
Unpacking replacement ca-certificates ...^M
...
Setting
This shows up as weechat failing to connect because the key length is
less than 2048 bits (weechat's default behavior). Needless to say, if I
ask for 2048 bits of temp key, I should get (at least) 2048 bits of temp
key.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I have several hosts (running inspircd) that call
gnutls_dh_params_generate2 to generate their dh params.
The key lengths that openssl s_client reports are not always the correct
length.
It seems that gnutls is not following the crypto-community standard of
forcing the high
Public bug reported:
After a careful review of
https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, I believe that
anope should be included in main. Our evaluation of IRC daemons led us
to anope as the only set of IRC services that is actively maintained and
sane.
Package: anope
Public bug reported:
After careful review of
https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, I believe that
inspircd should be included in main. Our evaluation of IRC daemons led
us to inspircd as the only one that met our needs (open source, ldap
integration, without a history of
Public bug reported:
The following apparmor profile appears to be working for us. Please add
it to the package.
** Affects: inspircd (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: apparmor profile
Trusty-proposed package tested and verified to correctly label images.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454775
Title:
incorrect architecture label on i386 images
To manage
Public bug reported:
Trusty's python-simplestreams uploads i386 images as architecture: i386,
which nova filters out, since it is not 'i686'.
See also
http://bazaar.launchpad.net/~smoser/simplestreams/trunk/revision/366
Can we please get this into trusty-updates?
thanks,
lamont
** Affects:
Public bug reported:
Trusty's python-simplestreams uploads i386 images as architecture: i386,
which nova filters out, since it is not 'i686'.
See also
http://bazaar.launchpad.net/~smoser/simplestreams/trunk/revision/366
Can we please get this into trusty-updates?
thanks,
lamont
** Affects:
Public bug reported:
Affects (at least) 2.0.5 thru 2.0.18
When a client fails to authenticate to inspircd (using ldapauth, or
maybe always), it would be useful if the message going back to inform
the client of the failure included the nick that the client actually
used.
This would help the user
Public bug reported:
inspircd has no concept of logrotation. The attached patch (1) adds a
reopen of the logfiles to the SIGHUP handler (which also rehashes the
config), and (2) fixes a bug in LogManager::CloseLogs where it forgot to
clear one list.
Relative to 2.0.17-2.
** Affects: inspircd
Public bug reported:
We needed to have more information logged for ldapauth users. The
attached patch adds that logging.
** Affects: inspircd (Ubuntu)
Importance: Undecided
Status: New
** Patch added: additional ldapauth logging detail
Public bug reported:
There are a couple of issues with m_ldapauth's handling of
password=$USER:$PASS (2.0.17-2 and still in 2.0.18. I didn't look at
2.0.5)
1) When it does the second ldapsearch, it asks for '$USER' rather than
'$ATTRIBUTE=$USER' as in the first search
2) if the first search
patch to fix the various issues
** Patch added: 10_fix_ldapauth_userpass.diff
https://bugs.launchpad.net/ubuntu/+source/inspircd/+bug/1428209/+attachment/4334473/+files/10_fix_ldapauth_userpass.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I believe that this happens because the config
(/proc/sys/net/ipv6/conf/all/accept_ra_defrtr) says to accept a default
route, and you have one specified in /etc/network/interfaces, and
therefore the advertised default route fails to get added to the routing
table.
It would be a good thing if the
Looks good to me. I'll get it added into the debian source next time I
upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/583216
Title:
inet_protocols can't be preseeded
To manage
Looks good to me. I'll get it added into the debian source next time I
upload.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/583216
Title:
inet_protocols can't be preseeded
To
Public bug reported:
It would be wonderful to be able to override the default values for
--keepalive. However, nm-openvpn ignores such settings on import, and
has no UI for setting them.
** Affects: network-manager-openvpn (Ubuntu)
Importance: Wishlist
Status: New
** Changed in:
Public bug reported:
all versions
The default cipher for openvpn is BF-CBC (blowfish), which was likely
once a good choice.
Virtually all modern hardware has hardware acceleration/support for AES
instructions, and can therefore do AES-128-CBC far faster and more
efficiently than it can
Public bug reported:
all versions
The default cipher for openvpn is BF-CBC (blowfish), which was likely
once a good choice.
Virtually all modern hardware has hardware acceleration/support for AES
instructions, and can therefore do AES-128-CBC far faster and more
efficiently than it can
Public bug reported:
By default, sflphone chooses the IP address for a connection poorly. It
should be trivial to have it query the routing table to get the
interface through which our traffic to the SIP server will go, and use
that IP, rather than hardcoding all of them to one interface and IP
See also https://www.ietf.org/rfc/rfc2317.txt for a very nice (still
current best practice 16 years later) writeup on how to handle zones
smaller than /24.
If you guys have any other DNS questions, feel free to ask me, or one of
the other admins.
--
You received this bug notification because
See also https://www.ietf.org/rfc/rfc2317.txt for a very nice (still
current best practice 16 years later) writeup on how to handle zones
smaller than /24.
If you guys have any other DNS questions, feel free to ask me, or one of
the other admins.
--
You received this bug notification because
See also https://bugs.launchpad.net/juju-core/+bug/1335179
--
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/1358586
Title:
fails to deploy machines when eth0 does not exist
To manage
See also https://bugs.launchpad.net/juju-core/+bug/1335179
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358586
Title:
fails to deploy machines when eth0 does not exist
To manage notifications
Public bug reported:
The lxc postinst assumes that only /24 networks are used in 10.0.0.0/8.
If the host has a route for 10.0.0.2/23 (or 10.0.0.0/22, or any other
block that includes 10.0.3.0/24 or whatever other block it is checking)
then the postinst chooses a chunk of the existing network
Public bug reported:
Trying to use MAAS to deploy a machine, it would go offline early in the
deployment. It turns out that the networking was being overwritten to
use br0 with eth0 as the underlying interface.
The only problem is, there is no eth0 on the machine: 'em1' is the
interface that
FWIW, the machine in question has this:
cat /proc/net/dev
Inter-| Receive| Transmit
face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo: 0 0000
Public bug reported:
The lxc postinst assumes that only /24 networks are used in 10.0.0.0/8.
If the host has a route for 10.0.0.2/23 (or 10.0.0.0/22, or any other
block that includes 10.0.3.0/24 or whatever other block it is checking)
then the postinst chooses a chunk of the existing network
Public bug reported:
Trying to use MAAS to deploy a machine, it would go offline early in the
deployment. It turns out that the networking was being overwritten to
use br0 with eth0 as the underlying interface.
The only problem is, there is no eth0 on the machine: 'em1' is the
interface that
FWIW, the machine in question has this:
cat /proc/net/dev
Inter-| Receive| Transmit
face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo: 0 0000
Public bug reported:
There is evidence in both the trusty and utopic versions of curtin that
swraid support is on its way, but it appears to only think raid0 is
needed/desirable, at least thus far.
Installing machines that lack cciss (and therefore hardware raid) under
MAAS, we would still like
Following up on a discussion from today with more detail.
For metal in the datacenters, everything that can be RAID, is. The
driving reason for this is to avoid a disk failure resulting in machine
downtime. Given the number of drives in a modern datacenter, it's not a
question of if a drive
Public bug reported:
There is evidence in both the trusty and utopic versions of curtin that
swraid support is on its way, but it appears to only think raid0 is
needed/desirable, at least thus far.
Installing machines that lack cciss (and therefore hardware raid) under
MAAS, we would still like
Following up on a discussion from today with more detail.
For metal in the datacenters, everything that can be RAID, is. The
driving reason for this is to avoid a disk failure resulting in machine
downtime. Given the number of drives in a modern datacenter, it's not a
question of if a drive
Public bug reported:
when I configure maas to manage DNS and DHCP for 10.89.64.0/20, it
creates a reverse zone for 89.10.in-addr.arpa.
If 10.89.0.0/16 is in use for other things, and only 10.89.64.0/20 was
delegated to scalingstack, then no reverse DNS can happen, since the
parent zone will win
Public bug reported:
when I configure maas to manage DNS and DHCP for 10.89.64.0/20, it
creates a reverse zone for 89.10.in-addr.arpa.
If 10.89.0.0/16 is in use for other things, and only 10.89.64.0/20 was
delegated to scalingstack, then no reverse DNS can happen, since the
parent zone will win
I will get this added to the package.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1305232
Title:
Postfix fails to start, failure to copy certificates
To manage notifications
I will get this added to the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305232
Title:
Postfix fails to start, failure to copy certificates
To manage notifications about this bug go
Public bug reported:
If I tell network manager to always bring up a vpn when I connect to a
network, and the vpn fails to come up, then NM happily decides that the
(wireless in this case) network is unusable and disconnects from it,
only to discover it and try again.
Once I disabled the
Public bug reported:
with a precise server (openvpn 2.2.1-8ubuntu1.2) and trusty client
(2.3.2-7ubuntu3):
In the config, I had:
push route xx.xx.xx.xx 255.255.255.255 net_gateway
push route yy.yy.yy.yy 255.255.255.255 net_gateway
(and another route for the /21 containing both of the hosts
Public bug reported:
with a precise server (openvpn 2.2.1-8ubuntu1.2) and trusty client
(2.3.2-7ubuntu3):
In the config, I had:
push route xx.xx.xx.xx 255.255.255.255 net_gateway
push route yy.yy.yy.yy 255.255.255.255 net_gateway
(and another route for the /21 containing both of the hosts
This is network-manager-openvpn 0.9.8.2-1ubuntu4 on trusty.
** Package changed: network-manager (Ubuntu) = network-manager-openvpn
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303835
Public bug reported:
I need to be able to specifiy multiple host/port combinations for the
remote end of an openvpn tunnel, and NM won't let me do that. (If I
attempt to import a config that has that, I get a SEGV, though that may
be something completely unrelated.)
** Affects:
That is, host and port belong together, not on two separate screens...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303838
Title:
nm-openvpn does not allow multiple remote statements
To manage
Public bug reported:
NM currently believes that a VPN is a subset of a particular SSID on
wireless. That is, that I want different VPNs to come up based on what
SSID I have connected to.
What this means is that if I have a VPN that I always want to bring up,
regardless of where I'm connected,
Public bug reported:
Found in: 2.02~beta2-6
My upgrade from saucy to trusty ran into problems, with grub-probe
failing with unknown filesystem, which propogated up to cause the
kernel install to fail, resulting in a machine where I cannot install
packages. After some debugging:
(missing here
Here is the output of: grub-probe -d -vv --target=fs_uuid --device
/dev/mapper/rover3-saucy--save
** Attachment added: grub-probe debug/verbose trace
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1287436/+attachment/4005978/+files/grub-probe-out
--
You received this bug notification
Public bug reported:
in nova.conf:
compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
scheduler_default_filters=RetryFilter,AvailabilityZoneFilter,DiskFilter,CoreFilter,RamFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter
The openstack deployment has
We are seeing this in both: nova-scheduler=1:2013.1.4-0ubuntu1~cloud0
and nova-scheduler=1:2013.2-0ubuntu1~cloud0
lamont
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1265877
Title:
Public bug reported:
in nova.conf:
compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
scheduler_default_filters=RetryFilter,AvailabilityZoneFilter,DiskFilter,CoreFilter,RamFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter
The openstack deployment has
We are seeing this in both: nova-scheduler=1:2013.1.4-0ubuntu1~cloud0
and nova-scheduler=1:2013.2-0ubuntu1~cloud0
lamont
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265877
Title:
nova fails to
Public bug reported:
snmpd does not notice when a disk is added to the system after snmpd is
started.
It should at a minimum arrange to do so.
Observed in snmpd 5.4.3~dfsg-2.4ubuntu1.1
** Affects: net-snmp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
snmpd does not notice when a disk is added to the system after snmpd is
started.
It should at a minimum arrange to do so.
Observed in snmpd 5.4.3~dfsg-2.4ubuntu1.1
** Affects: net-snmp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
I have a saucy/amd64 instance that was booted using the 20130822 image
(checksum c19841cd672d6fcb3d4e78f0f918f8e1) and last updated on
2013-08-29, which I finally updated today. During the upgrade, modprobe
btrfs hung in init_module(). If I kill modprobe, the upgrade
Attaching the apt history.log (files).
** Attachment added: apt history.log (concatenated through all of time)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1260431/+attachment/3928217/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: geoip (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/1239127
Title:
stuck at timezone selection screen, only if within geoip
Public bug reported:
When I run various nova commands, stderr gets assertion failure warnings
spewed on it.
Unsure if this is a gobject issue, or a nova client issue, so marking it
as both.
lamot
% nova list
/usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning:
Public bug reported:
When I run various nova commands, stderr gets assertion failure warnings
spewed on it.
Unsure if this is a gobject issue, or a nova client issue, so marking it
as both.
lamot
% nova list
/usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning:
Public bug reported:
% evince foo.pdf
** (evince:26162): WARNING **: Couldn't register with accessibility bus:
An AppArmor policy prevents this sender from sending this message to
this recipient, 0 matched rules; type=method_call, sender=(null)
(inactive) interface=org.freedesktop.DBus
In response to ctl-P:
** (evince:26301): WARNING **: Couldn't connect to D-Bus system bus,
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy
prevents this sender from sending this message to this recipient, 0
matched rules; type=method_call, sender=(null) (inactive)
Postfix delivers no /usr/bin/mail, nor any mail user agent.
** Package changed: postfix (Ubuntu) = bsd-mailx (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bsd-mailx in Ubuntu.
https://bugs.launchpad.net/bugs/1222179
Title:
Fixed in 2.10.2-1
** Changed in: postfix (Ubuntu Saucy)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1222180
Title:
postfix package
Fixed in 2.10.2-1
** Changed in: postfix (Ubuntu Saucy)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222180
Title:
postfix package produces errors in
Postfix delivers no /usr/bin/mail, nor any mail user agent.
** Package changed: postfix (Ubuntu) = bsd-mailx (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222179
Title:
/usr/bin/mail has
301 - 400 of 1183 matches
Mail list logo
