As a point of information, the virtual instance works fine on the second
boot.
i.e. if you vagrant up: vagrant halt; vagrant up everything works as
expected with the exception that the post provisioning/configuration
process will have failed.
System configuration:
Ubuntu image:
** Attachment added: Debug output of manual attempt to SSH in to VM as
vagrant
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1217950/+attachment/3827671/+files/SSHdebug.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
As a point of information, the virtual instance works fine on the second
boot.
i.e. if you vagrant up: vagrant halt; vagrant up everything works as
expected with the exception that the post provisioning/configuration
process will have failed.
System configuration:
Ubuntu image:
** Attachment added: Debug output of manual attempt to SSH in to VM as
vagrant
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1217950/+attachment/3827671/+files/SSHdebug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Looks like it's been fixed upstream. See:
http://redmine.yorba.org/issues/5566
Perhaps this can be closed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025598
Title:
shotwell doesn't get the
I can confirm this happened after on my Samsung Galaxy after it upgraded
from, if I recall correctly, v4.0.1 to v4.1.1.
What's interesting is after the upgrade I was able to sync only those
photos which were taken before the updated, i.e. it's specific to the
images and not the OS in general.
** Attachment added: EXIF data from a photo taken under v4.1.1
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1025598/+attachment/3233611/+files/EXIF.4.1.1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A bit of me too but hopefully with another reference point or two.
Issue exactly as described by DigiAngel on 2012-05-26.
Server: synergy version 1.3.6, Ubuntu 11.04 on x86_64
Client: synergy version 1.3.8, Linux Mint 13 Maya on i686
Both packages installed from the respective distro
--- On Mon, 10/26/09, Jamie Strandboge ja...@ubuntu.com wrote:
From: Jamie Strandboge ja...@ubuntu.com
Subject: [Bug 396336] Re: AppArmor logprof gets stuck in recursive loop
To: allpoints...@yahoo.com
Date: Monday, October 26, 2009, 5:09 AM
Thank you for using Ubuntu and taking
the time
Public bug reported:
Binary package hint: apparmor
jaunty 2.28.13
from terminal:
$ sudo aa-logprof
[sudo] password for xxx:
Reading log entries from /var/log/messages.
Updating AppArmor profiles in /etc/apparmor.d.
Profile: /sbin/dhclient3
Execute:
** Attachment added: ldap.conf
http://launchpadlibrarian.net/26188570/ldap.conf
--
TLS_CACERTDIR not supported in gnutls
https://bugs.launchpad.net/bugs/242313
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in ubuntu.
--
The work-around for this in Intrepid was to use tls_cacert instead of
tls_cacertdir in /etc/ldap.conf.
I recently upgraded to jaunty and now the work-around no longer works.
Attached are
1) Output of: ldapsearch -d1 -H ldap://OUR.LDAPSERVER.COM -ZZ -x -D
'uid=SOMEUID,DC=SOME,DC=DOMAIN' -W -b
** Attachment added: ldap.conf
http://launchpadlibrarian.net/26188570/ldap.conf
--
TLS_CACERTDIR not supported in gnutls
https://bugs.launchpad.net/bugs/242313
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
13 matches
Mail list logo
