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.
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.
** 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
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
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
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 ...
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 ...
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
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:
