I'm not sure why you've attached .xsession-errors. bzr and curl have nothing to do with X.
The gdb-ca-certificates.txt attachment doesn't seem relevant either. I don't know command you attached gdb to, but it died with SIGPIPE (due to attaching gdb I suspect) which doesn't give any hints about ca-certificate problems.
None of those bugs you've linked to look like duplicates to me (bug 285623 is this bug!).
Have you tried:
bzr get https+urllib://code.launchpad.net/~ubuntu-core-dev/metacity/ubuntu
as Wouter suggested? Letting us know if that works or not may help us narrow down the problem.
Finally, if you just want to get the code, just use the actual URL of the branch:
https://code.launchpad.net/ is for web browsers, and while it tries to redirect bzr clients it's simpler to just use the actual branch location in the first place.
I'm not sure why you've attached .xsession-errors. bzr and curl have nothing to do with X.
The gdb-ca- certificates. txt attachment doesn't seem relevant either. I don't know command you attached gdb to, but it died with SIGPIPE (due to attaching gdb I suspect) which doesn't give any hints about ca-certificate problems.
None of those bugs you've linked to look like duplicates to me (bug 285623 is this bug!).
Have you tried:
bzr get https+urllib: //code. launchpad. net/~ubuntu- core-dev/ metacity/ ubuntu
as Wouter suggested? Letting us know if that works or not may help us narrow down the problem.
Finally, if you just want to get the code, just use the actual URL of the branch:
bzr get http:// bazaar. launchpad. net/~ubuntu- core-dev/ metacity/ ubuntu
https:/ /code.launchpad .net/ is for web browsers, and while it tries to redirect bzr clients it's simpler to just use the actual branch location in the first place.