[Bug 1587154] Re: --working-directory does not work anymore
Works for me, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587154 Title: --working-directory does not work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1587154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327835] Re: light-locker-settings reverts to "never" after reboot.
The problem is that light-locker-settings fails if the expected file does not already exist. There is a simple workaround by creating an empty file in that location before launching light-locker-settings: $ touch ~/.config/autostart/screensaver-settings.desktop $ light-locker-settings I am also attaching a patch that kind of solves this problem by masking any error that the load function might raise. I do not really understand the GLib python bindings here, though. Apparently it is supposed to return an error code, but at the same time it always raises a generic GLib.Error, so the return value cannot be checked at all...? ** Patch added: "light-locker-settings-ignore-error.diff" https://bugs.launchpad.net/light-locker-settings/+bug/1327835/+attachment/5198461/+files/light-locker-settings-ignore-error.diff ** Also affects: light-locker-settings (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/1327835 Title: light-locker-settings reverts to "never" after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker-settings/+bug/1327835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278529] Re: Using S3, BackendException: No connection to backend
I had the same BackendException on Debian wheezy with duplicity 0.6.24-1~bpo70 and python-boto 2.25.0-1~bpo7. I solved this for me by forcing boto to use Signature Version 4 for API requests. Export this variable into the shell environment before running duply: export S3_USE_SIGV4=True duply ... According to the AWS documentation [1], new regions introduced after January 2014 do not support older signature versions in API requests. In my case, the endpoint I use is Frankfurt, EU which was introduced after this date. This version of boto supports the new signatures, but does not seem to use them without being told to do so. Also make sure you use the hostname for your region in the URL such as s3://s3-eu-central-1.amazonaws.com/bucket/. I hope this helps anyone stumbling across this bug report even if it is already fixed in duplicity = 0.7.01 as stated above. [1] http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4 -authenticating-requests.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278529 Title: Using S3, BackendException: No connection to backend To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1278529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278529] Re: Using S3, BackendException: No connection to backend
I had the same BackendException on Debian wheezy with duplicity 0.6.24-1~bpo70 and python-boto 2.25.0-1~bpo7. I solved this for me by forcing boto to use Signature Version 4 for API requests. Export this variable into the shell environment before running duply: export S3_USE_SIGV4=True duply ... According to the AWS documentation [1], new regions introduced after January 2014 do not support older signature versions in API requests. In my case, the endpoint I use is Frankfurt, EU which was introduced after this date. This version of boto supports the new signatures, but does not seem to use them without being told to do so. Also make sure you use the hostname for your region in the URL such as s3://s3-eu-central-1.amazonaws.com/bucket/. I hope this helps anyone stumbling across this bug report even if it is already fixed in duplicity = 0.7.01 as stated above. [1] http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4 -authenticating-requests.html -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1278529 Title: Using S3, BackendException: No connection to backend To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1278529/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955329] Re: bzr: ERROR: No module named xml_errors when running 'bzr help commands' or tab-completion
The bug still exists in the current release bzr-xmloutput 0.8.8. ** Also affects: bzr-xmloutput 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/955329 Title: bzr: ERROR: No module named xml_errors when running 'bzr help commands' or tab-completion To manage notifications about this bug go to: https://bugs.launchpad.net/bzr-xmloutput/+bug/955329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 669046] Re: privmsgs from nicks not to be highlighted are highlighted
This patch is totally wrong as xchat now ignores all users from this instead of just not producing a highlight. Please revert this patch or fix it correctly. For reference: LP #735656 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669046 Title: privmsgs from nicks not to be highlighted are highlighted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat/+bug/669046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 735656] Re: Users on highlight ignore are completely ignored
This broken behavior is caused by the patch added as a result from LP #669046. As this makes the situation worse than before, please revert this patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/735656 Title: Users on highlight ignore are completely ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat/+bug/735656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828381] Re: bzr-svn fails to build against bzr 2.4.0 stable
** Also affects: bzr-svn 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/828381 Title: bzr-svn fails to build against bzr 2.4.0 stable To manage notifications about this bug go to: https://bugs.launchpad.net/bzr-svn/+bug/828381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828381] Re: bzr-svn fails to build against bzr 2.4.0 stable
There is no source release of bzr-svn available to be used with bzr 2.4.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828381 Title: bzr-svn fails to build against bzr 2.4.0 stable To manage notifications about this bug go to: https://bugs.launchpad.net/bzr-svn/+bug/828381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
