Affected here too after creating a new key in ~/.ssh, this is 14.04 with
all updates as of today.
--
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/1380084
Title:
SSH client requires
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nova (Ubuntu)
--
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/1307791
Title:
Volumes
@Mario, in theory an image that should be taking up 30 GB with four
snapshots should be taking up at most about 150 GB, of course. Now the
question is what you mean by should be taking up 30 GB and by is
taking 600+ GB.
For the latter, did you query the file length (ls -l) or the actual size
*** This bug is a duplicate of bug 1214379 ***
https://bugs.launchpad.net/bugs/1214379
Public bug reported:
this keeps returning
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: squid3 3.3.8-1ubuntu6.2
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux
*** This bug is a duplicate of bug 1214379 ***
https://bugs.launchpad.net/bugs/1214379
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1214379, so is being marked as such.
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1214379
Title:
pinger crashed with SIGSEGV in malloc_consolidate()
To manage notifications about this bug go
** Also affects: corosync (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1340172
Title:
[OSCI] Add mamange/unmanage blocks to
Same as comment #44 I'm running hardware MAAS and I get this on every
deployment. If I let cloud-init error out I can get logged in and juju-
br0 is up by that point but it doesn't come up until after cloud-init
tries to do it's stuff. This makes the nodes I deploy unusable.
I'm going to see if
@mark-dickie Can you please try to reproduce this with the latest juju-
core built from source (master branch) to see if you still have an
issue? If you do, please attach the following logs to help us analyze
the issue better:
Before anything, please add logging-config: root=TRACE to your maas
@mwenning - What's the output of $ juju version? Can you try what I've
proposed in comment #46?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1271144
Title:
br0 not brought up
The second part of the fix (which does not reduce the performance) for
qemu 2.0 (apparently uploading two patches at once is not so easy)
** Patch added: 0502-block-raw-posix-use-seek_hole-ahead-of-fiemap.patch
- 501-block-raw-posix-fix-disk-corruption-in-try-fiemap
- (note - 502-block-raw-posic-use-seek-hole-ahead-of-fiemap (which was
also needed in utopic) appears to be unneeded here as the code being
changed has not yet been switched to using try_fiemap)
Actually such a enforces fsync
@dimitern Thanks for the swift reply. I'll do this now, for your
information I'm currently running juju 1.21-beta3-trusty-amd64 from the
juju-proposed ppa.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Also I've found that if I edit /etc/init/networking.conf and change the
starts on line to:-
starts on stopped cloud-init-local
Then everything works fine although I realise that this is a very poor
solution. Best I could manage with my limited upstart knowledge.
--
You received this bug
@serge, what version would I need to upgrade to be able to use the
external snapshots? that sounds like it would solve my problems
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
@mark-dickie - I can't see 1.21-beta3 in
https://launchpad.net/~juju/+archive/ubuntu/proposed are you sure you
didn't mean https://launchpad.net/~juju/+archive/ubuntu/devel ?
Thanks for sharing the workaround - at least it gives me something to
look into! :)
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/1402763
** Tags added: mos
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1340172
Title:
[OSCI] Add mamange/unmanage blocks to corosync init scripts
To manage notifications about this
Public bug reported:
I can´t install new pack, i dont want to uodate.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libruby1.9.1 1.9.3.484-2ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
@dimitern
Quite right, it is the devel branch I'm using. I was trying to find a
new version which might already have a fix. I'm not very up on building
software based on go. I'm getting the following when I try to run go
install -v launchpad.net/juju-core/...
go build
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ruby1.9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1403049
Title:
package libruby1.9.1 1.9.3.484-2ubuntu1 failed to install/upgrade:
pakket
Hello Stefan, or anyone else affected,
Accepted xen into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/xen/4.4.1-0ubuntu0.14.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Stefan, or anyone else affected,
Accepted xen into utopic-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/xen/4.4.1-0ubuntu0.14.10.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Xing, or anyone else affected,
Accepted qemu into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-
2ubuntu1.10 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Xing, or anyone else affected,
Accepted qemu into utopic-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/qemu/2.1+dfsg-
4ubuntu6.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
@mark-dickie: Ok, 1.21-beta3 actually should have the fix - no need to
build from source. Can you:
1. Edit your ~/.juju/environments.yaml to include logging-config:
root=TRACE for your maas environment.
2. Run $ juju bootstrap --debug ~/maas-bootstrap.log
3. Once the machine is up and you can
Public bug reported:
keystone icehouse package needs dependency for python-six 1.5.2-1, which
is in the cloud archive
2014-12-16 04:05:17 INFO install Setting up keystone
(1:2014.1.3-0ubuntu2~cloud0) ...
2014-12-16 04:05:17 INFO install Traceback (most recent call last):
2014-12-16 04:05:17
** Summary changed:
- icehouse package needs python-six 1.5.2-1 dependency
+ [SRU] icehouse package needs python-six 1.5.2-1 dependency
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
I think my test of juju-quickstart + juju-core failed because my env is
dirty. I get the same errors on trusty with the packages in release and
updates. I will retest with a clean trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug
ubuntu@juju-beis1-machine-8:~$ dpkg -l | egrep 'keystone|six'
iF keystone 1:2014.1.3-0ubuntu2~cloud0
OpenStack identity service - Daemons
ii python-keystone 1:2014.1.3-0ubuntu2~cloud0
OpenStack identity service - Python library
ii
When installing keystone in a fresh enviro using the cloud archive, it
installs cleanly. But if an older version of python-six is already
installed, such as may be provided earlier by another package's
dependency, the older 1.1.0-2 six version remains.
--
You received this bug notification
issue affects precise OpenStack charm deployments
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1403114
Title:
[SRU] icehouse package needs python-six 1.5.2-1 dependency
To
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
** Description changed:
+ [Impact]
+
keystone icehouse package needs dependency for python-six 1.5.2-1, which
is in the cloud archive
2014-12-16 04:05:17 INFO install Setting up keystone
(1:2014.1.3-0ubuntu2~cloud0) ...
2014-12-16 04:05:17 INFO install Traceback (most recent call
** Changed in: nova (Ubuntu Utopic)
Status: New = In Progress
** Changed in: nova (Ubuntu Utopic)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Don't use the dkms package - its not compatible or required for the 3.13
kernel in 14.04.
** Changed in: openvswitch (Ubuntu Vivid)
Status: In Progress = Invalid
** Changed in: openvswitch (Ubuntu Utopic)
Status: Confirmed = Invalid
--
You received this bug notification because
** Changed in: horizon (Ubuntu Vivid)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1382632
Title:
Insecure key file permissions
To manage
For reference:
http://javacruft.wordpress.com/2014/03/03/which-open-vswitch/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1369294
Title:
openvswitch-datapath-dkms
** Changed in: keystone (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1403114
Title:
[SRU] icehouse package needs python-six 1.5.2-1
I've done a bit more testing, and here are my observations:
1) rebooting a container internally/stop-start externally using lxc-*
Works OK - container re-joins the corosync cluster just fine.
2) rebooting the physical host
Fails - containers never re-join the corosync cluster and perform the
Public bug reported:
From man corosync.conf
mcastport
This specifies the UDP port number. It is possible to use the same
multicast address on a network with the corosync services configured for
different UDP ports. Please note corosync uses two UDP ports mcastport (for
mcast receives) and
** Also affects: linux (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.
https://bugs.launchpad.net/bugs/1402763
Title:
Multicast traffic not propating correctly over
** Package changed: keystone (Ubuntu) = keystone (Juju Charms
Collection)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1403132
Title:
hacluster default ports conflict between
Here is the bootstrap log created when I run juju bootstrap --to
db2.ed1.mavennetwork.co.uk --debug ~/maas-bootstrap.log
** Attachment added: maas-bootstrap.log
https://bugs.launchpad.net/juju-core/+bug/1271144/+attachment/4282230/+files/maas-bootstrap.log
--
You received this bug
And these are the juju and cloud logs from the node which was
bootstrapped. This node is working fine right now but once it is
rebooted I will get the cloud-init problem. I'll reboot it now and then
post the logs after the problematic boot.
** Attachment added: logs.zip
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1402763
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
Public bug reported:
When keepalived is reloaded using service keepalived reload (on
controller nodes) it leaks file descriptors.
Steps to reproduce:
1. Locate the vrrp keepalived process
$ ps -elf |grep -i keepalived
1 S root 15129 1 0 80 0 - 12884 poll_s 16:47 ? 00:00:00 /usr/sbin/keepalived
And lastly the logs from the node after it is rebooted. On this boot it
takes a very long time to come up as cloud-init waits for the network
bridge to come up and then eventually errors out.
** Attachment added: logs2.zip
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
This bug was fixed in the package juju-core - 1.20.11-0ubuntu1
---
juju-core (1.20.11-0ubuntu1) vivid; urgency=medium
* New upstream bugfix release (LP: #1386144).
* Build with a version of libgo5 that has the 64k PAGE_SIZE fix
(LP: #1377325).
-- Robie Basak
This bug was fixed in the package juju-core - 1.20.11-0ubuntu1
---
juju-core (1.20.11-0ubuntu1) vivid; urgency=medium
* New upstream bugfix release (LP: #1386144).
* Build with a version of libgo5 that has the 64k PAGE_SIZE fix
(LP: #1377325).
-- Robie Basak
Hi,
I am pretty busy this week. I shall be able to do the test this weekend or
next week. Thanks,
-Xing
On Tue, Dec 16, 2014 at 7:18 AM, Chris J Arges 1394...@bugs.launchpad.net
wrote:
Hello Xing, or anyone else affected,
Accepted qemu into utopic-proposed. The package will build now and be
This bug was fixed in the package ceilometer - 2014.2.1-0ubuntu1
---
ceilometer (2014.2.1-0ubuntu1) utopic; urgency=medium
[ Corey Bryant ]
* Resynchronize with stable/juno (b1fca33) (LP: #1398952):
- [43718e8] Internal error with period overflow
- [37e593e] Validate
The verification of the Stable Release Update for ceilometer 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
This bug was fixed in the package cinder - 1:2014.2.1-0ubuntu1
---
cinder (1:2014.2.1-0ubuntu1) utopic; urgency=medium
[ Corey Bryant ]
* Resynchronize with stable/juno (f17aa46) (LP: #1398952):
- [498fe7e] Revert Fix Brocade FC SAN lookup MITM vulnerability
- [31b5831]
This bug was fixed in the package glance - 1:2014.2.1-0ubuntu1
---
glance (1:2014.2.1-0ubuntu1) utopic; urgency=medium
[ Corey Bryant ]
* Resynchronize with stable/juno (41e143b) (LP: #1398952):
- [640e08f] Disable osprofiler by default
- [c5e302e] Image not downloaded
This bug was fixed in the package nova - 1:2014.2.1-0ubuntu1
---
nova (1:2014.2.1-0ubuntu1) utopic; urgency=medium
[ Corey Bryant ]
* Resynchronize with stable/juno (3136cfc) (LP: #1398952):
- [ee00c80] Instances with NUMA will be packed onto hosts
- [ccb7ef2] Make
This bug was fixed in the package keystone - 1:2014.2.1-0ubuntu1
---
keystone (1:2014.2.1-0ubuntu1) utopic; urgency=medium
[ Corey Bryant ]
* Resynchronize with stable/juno (d7eb999) (LP: #1398952):
- [f54fa8f] Prevent infinite loop in token_flush
- [bd92689] Adds IPv6
This bug was fixed in the package neutron - 1:2014.2.1-0ubuntu1
---
neutron (1:2014.2.1-0ubuntu1) utopic; urgency=medium
[ Corey Bryant ]
* Resynchronize with stable/juno (330ca81) (LP: #1398952):
- [209160b] Fix hostname validation for nameservers
- [d7ee2ff] Alter
This bug was fixed in the package heat - 2014.2.1-0ubuntu2
---
heat (2014.2.1-0ubuntu2) utopic; urgency=medium
* d/control: Add python-oslo.serialization to python-heat depends. Needed for
heat-engine (LP: #1398952).
heat (2014.2.1-0ubuntu1) utopic; urgency=medium
[ Corey
** Summary changed:
- [SRU] icehouse package needs python-six 1.5.2-1 dependency
+ [SRU] icehouse packages need python-six = 1.5.2 Depends
** Description changed:
[Impact]
- keystone icehouse package needs dependency for python-six 1.5.2-1, which
- is in the cloud archive
+ This can
** Also affects: keystone
Importance: Undecided
Status: New
** No longer affects: keystone
** Also affects: cinder (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ceilometer (Ubuntu)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu)
Thanks, Don. I'll post a package set which takes a lock at
cgm_dbus_connect and drops it at disconnect. Which release are you
testing on? Utopic, like James was?
(Odd that I haven't run into that one here!)
** Changed in: libvirt (Ubuntu)
Importance: Undecided = High
** Changed in:
Public bug reported:
Please sync numactl 2.0.10-1 (main) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* Enable arm64 builds (LP: #1283279)
Fixed in debian
Changelog entries since current vivid version 2.0.9~rc5-1ubuntu2:
numactl (2.0.10-1) unstable;
Public bug reported:
Please sync acpica-unix 20141107-1 (main) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* debian/run-misc-tests.sh: Use dpkg-architecture instead of 'uname -m'
Fixed in debian
Changelog entries since current vivid version
Looking at the patch applied in F21, it doesn't seem like Fedora
actually fixed it. They simply check whether /sbin/init is a link to
systemd, and ignore the report if so.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to chkrootkit in
Patchg 0500-block-raw-posix-Try-both-FIEMAP-and-SEEK_HOLE.patch appears
to be part of a bigger re-write of the related code. and is ON TOP of
the patches already applied in this bug.
No doubt the rewirtten code is better but backporting it contains more risk
than the 2 simple fixes I already
The verification of the Stable Release Update for horizon 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 a
This bug was fixed in the package horizon - 1:2014.1.3-0ubuntu2
---
horizon (1:2014.1.3-0ubuntu2) trusty; urgency=medium
* Fix Ubuntu theme region switcher dropdown (LP: #1396318)
-- Chris Johnston chrisjohns...@ubuntu.com Wed, 03 Dec 2014 14:00:30 -0500
** Changed in: horizon
Horizon has also been released into updates:
horizon | 1:2014.2.1-0ubuntu2| utopic-updates
| source
** Changed in: horizon (Ubuntu Utopic)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team,
*** This bug is a security vulnerability ***
Public security bug reported:
The BREACH vulnerability (http://breachattack.com/) is not mitigated in
the default nginx.conf configuration file.
Details on the BREACH vulnerability are available at the link above.
HTTP level compression served over a
** Bug watch added: Debian Bug tracker #773332
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773332
** Also affects: nginx (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773332
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: nginx
Importance: Undecided = High
** Changed in: nginx
Importance: High = Medium
--
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/1403283
Title:
[Security]
** Changed in: nginx (Debian)
Status: Unknown = New
--
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/1403283
Title:
[Security] BREACH vulnerability is not mitigated in default
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-3587
--
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/1403283
Title:
[Security] BREACH vulnerability is not
[Expired for tomcat6 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: tomcat6 (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in Ubuntu.
** Package changed: debian = xen (Debian)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/1396068
Title:
[Xen/xl] dom0 needs to run qemu for qcow access
To manage notifications about
** Package changed: debian = qemu (Debian)
--
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/1394327
Title:
unmapping of persistent grants in qemu
To manage notifications about this bug
*** This bug is a duplicate of bug 1385817 ***
https://bugs.launchpad.net/bugs/1385817
** This bug is no longer a duplicate of bug 1397065
package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
** This bug has
Patch 0500-block-raw-posix-Try-both-FIEMAP-and-SEEK_HOLE.patch appears to be
part of a bigger re-write
of the related code. and is ON TOP of the patches already applied in this bug.
Yep, sorry for not mentioning this. As far as I understand qemu-2.1 package
contains this partially rewritten
Thanks for the logs! None of them show anything alarming.
However something is wrong with your setup. How did you reboot the instance
after the bootstrap was done? Once MAAS provisions a machine cloud-init should
not run anymore - it's only used to boot the initial OS. Did you recommission
or
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1402961
Title:
package linux-image-generic 3.16.0.28.29 failed to install/upgrade:
package linux-image-generic
Correction: I built qtpim both in a 3-arch PPA (armhf i386 amd64) and
6-arch PPA (additionally powerpc arm64 ppc64el), and interestingly the
same problem happens on arm64 too:
https://launchpadlibrarian.net/192757969/buildlog_ubuntu-vivid-arm64
.qtpim-opensource-
** Changed in: ubuntukylin
Milestone: vivid-alpha1 = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325801
Title:
failed to boot from USB disk with error: gfxboot.c32: not a COM32R
Image
Affected here too after creating a new key in ~/.ssh, this is 14.04 with
all updates as of today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380084
Title:
SSH client requires SSH_AUTH_SOCK=0
** Description changed:
- i don't know!
+ 1) lsb_release -rd
+ Description: Ubuntu Vivid Vervet (development branch)
+ Release: 15.04
+
+ 2) apt-cache policy remmina
+ remmina:
+ Installed: 1.1.1-1ubuntu1
+ Candidate: 1.1.1-1ubuntu1
+ Version table:
+ *** 1.1.1-1ubuntu1 0
+ 500
fribid is now in Utopic and Vivid.
** Changed in: ubuntu
Status: Confirmed = Fix Released
** Package changed: ubuntu = fribid (Ubuntu)
** Package changed: debian = fribid (Debian)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- linux-keystone: version to be filled -proposed tracker
+ linux-keystone: 3.13.0-20.33 -proposed tracker
** Description changed:
- This bug is for tracking the version to be filled upload package. This
- bug will contain status and testing results related to that upload.
+
** Changed in: wajig (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182264
Title:
Wajig unable to operate with keywords starting with numbers
To manage
Public bug reported:
There is a new version of the package
** Affects: 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/1402966
Title:
libxcb
1. The compatibility issue is:
error occurred during discovery from the initiator
The log messages at the initiator gives following messages:
root@mcdivitt-c32n1:/var/log# cat syslog|tail
Nov 13 01:55:14 mcdivitt-c32n1 kernel: [656442.898068] scsi10 : iSCSI Initiator
over iSER
Nov 13 01:55:14
Run the command on Unity:
ps aux | grep nautilus
and
gsettings get org.gnome.desktop.background show-desktop-icons
and post the output of both.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Binary package hint: remmina
1) lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
2) apt-cache policy remmina
remmina:
Installed: 1.1.1-1ubuntu1
Candidate: 1.1.1-1ubuntu1
Version table:
***
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
*** This bug is a duplicate of bug 1187140 ***
https://bugs.launchpad.net/bugs/1187140
** This bug has been marked a duplicate of bug 1187140
gvfsd-http using almost 1 GB of memory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Status: Incomplete = Triaged
** Also affects: nvidia
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--- Comment From shrey...@in.ibm.com 2014-12-16 08:25 EDT---
(In reply to comment #3)
Shilpasri,
I would like to ask you to update this bug as soon as the patches get
accepted, with the commit-ids also.
Hi,
These patches have been accepted and are now in the linux-next tree. Commit
Public bug reported:
I got this while doing an apt-get dist-upgrade to my system.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: thunderbird 1:31.2.0+build2-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
The next step would be indeed getting a sponsor. I did the changes to
the bugs so that they would be more ready for sponsoring, but a sponsor
who is core-dev (can upload main packages) should be found. Practically
everything needed from your/our side is done, other than answering
possible future
*** This bug is a duplicate of bug 760344 ***
https://bugs.launchpad.net/bugs/760344
** This bug has been marked a duplicate of bug 760344
gvfsd-http not closing tcp connections
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 1009 matches
Mail list logo
