The libmemcached-1.0.X series seam not to allow you to activate sasl.
There is this conditional in the configure script:
if test x$ac_enable_sasl = xyes; then :
ac_enable_sasl=no
fi
which sets SASL to no even if you use --enable-sasl. Version 0.53
works well though. After issuing
Would love to see this resolved myself. Maybe some SVG icons?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964948
Title:
Poor resolution Volume OSD icons in gnome-shell
To manage notifications
Would love to know at least where we could change this. Can it be
changed in gnome-shell.css?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/878439
Title:
sound volume notification icon is low sized
The encode to ascii fix was a poor one, but i ment it as an example as
to where to start. It will fail if access_token or secret_token will
contain a character with no equivalent in ascii:
u'ă'.encode('ascii') #this will fail
You could try to encode to UTF-8 instead of ascii, but i can't
I have stumbled across this thread:
http://comments.gmane.org/gmane.comp.web.curl.general/11915
In one post it is sugested that the error may be produced by the remote
server not sending a notify before ending the tls connection. The
following quote may be of interest:
Nikos said, Several
Hello Ken!
From what i understand from this post:
http://boredzo.org/blog/archives/2008-06-16/what-to-do-if-python-
says-%E2%80%9Ccharacter-mapping-must-return-integer-none-or-
unicode%E2%80%9D
the problem is in the input given to the hmac library:
key.translate(trans_5C)
It seams like
Found another small bug that does not treat an IndexError.
Google buzz can aggregate feeds from popular sites like twitter. Most
times the feeds look like:
a href=http://twitter.com/TwitterUSERID;TwitterUSERID/a: Message
from Twitter here
But in rare cases the feed looks like this:
** Patch added: fixes KeyError on some buzzez that do not have content, just
title (private buzz i think)
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/626023/+attachment/1693330/+files/gwibber-service.patch
--
Gwibber does not display any messages for Google-Buzz
I created 2 patches that solved this bug on my system. The coding is not
pretty...but it seamed to work. Hope this helps someone.
** Patch added: adds another callback to authorize the oauth_token for google
buzz
Made a few corrections to the patch to handle failure of token
authorisation. Also made a mistake in the try...except statement (mea
culpa).
** Attachment added: gwibber.tar.gz
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/626023/+attachment/1695218/+files/gwibber.tar.gz
--
Gwibber
Sorry about that. Its my first patch :). I created a single file
containing all changes to both /usr/lib/python2.6/dist-
packages/gwibber/lib/gtk/buzz.py and /usr/lib/python2.6/dist-
packages/gwibber/microblog/buzz.py.
cd /usr/lib/python2.6/dist-packages/gwibber patch -p1
~/gwibber.patch
The only way i managed to get rid of that error, was by recompiling
libcurl with OpenSSL instead of GnuTLS and then recompiling python-
pycurl against the new cURL library.
as an ugly hack i did:
apt-get source curl
then modified line 80 of debian/rules to compile using openSSL:
cd
About the avatar. It looks like the json received from google, in some
cases does not include the thumbnailUrl (avatar) in the actor block:
actor: {
profileUrl: http://www.google.com/profiles/samfiragabriel;,
thumbnailUrl: ,
id: 101735734890425678723,
name:
Looks like its a google account feature not to share your photo with
everyone. You can change that behavior by following the instructions
here:
http://mail.google.com/support/bin/answer.py?ctx=mailanswer=35529hl=en
(step 7)
The GnuTLS recv error seems to be of little consequence in regards to
Any news on this?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519836
Title:
MaaS fails to boot Hyper-V Generation 2 virtual machines
To manage notifications about this bug go to:
This still happens in 16.04 on a Thinkpad P50
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404147
Title:
Screen is stretched when using dual monitors
To manage notifications about this bug go
Tested version 0.7.8-49-g9e904bb-0ubuntu1~16.04.2 on an OpenStack Mitaka
install running Hyper-V as compute host.
VM booted successfully and cloud-init finished its run. The following
output is from inside the VM after accessing it via SSH:
https://paste.ubuntu.com/23653864/
** Tags removed:
any update on this? It is really annoying to use containers on a desktop
system witn NetworkManager enabled. I get 12-15 network interfaces show
up in my nm-applet. Can't even select a wifi network because of this in
gnome-sehll. It's silly :)
--
You received this bug notification because you
So essentially the latest upstream stable release of queens should fix
this. Correct?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789425
Title:
magnum deb v6.1.0 not containing queens/stable
** Description changed:
[Impact]
It's about this file:
https://github.com/openstack/magnum/blob/stable/queens/magnum/drivers/common/templates/kubernetes/fragments
/configure-kubernetes-master.sh
The version installed has this condition:
if [ -n "$CERT_MANAGER_API" ]; then
** Description changed:
When resizing a volume, cinder will notify nova that a volume has
changed its size. For iSCSI attached volumes (ie: Dell Unity), the
package lsscsi is required for that to work. Without it, you get this
error:
2021-08-10 09:44:02.400 1816368 INFO
I *think* we also had this problem on systems that had NVMe volumes. The
nvme-cli package is not pulled in, even though it is used by os-brick:
https://github.com/openstack/os-
brick/blob/master/os_brick/initiator/connectors/nvmeof.py#L155
--
You received this bug notification because you are a
** Description changed:
When resizing a volume, cinder will notify nova that a volume has
changed its size. For iSCSI attached volumes (ie: Dell Unity), the
package lsscsi is required for that to work. Without it, you get this
error:
2021-08-10 09:44:02.400 1816368 INFO
> Did it block any operation by missing the nvme command? It looks like
it's in a critical path for NVMe-oF usecase, but it generates a warning
instead of an error when it's not found.
No. It was just a warning when using a Dell Unity all flash storage
appliance. However, it does seem like it
24 matches
Mail list logo