Public bug report changed:
https://launchpad.net/malone/bugs/30585
Comment:
Hello,
I have moved from breezy to dapper on the machine having the problem,
and for now I have not had that anymore.
I tried once on another computer still runinng breezy, but I could not get the
problem back. I am no
Public bug report changed:
https://launchpad.net/malone/bugs/30585
Comment:
I know :)
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Public bug report changed:
https://launchpad.net/malone/bugs/30585
Changed in: katapult (upstream)
Status: Unconfirmed => Fix Released
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Public bug report changed:
https://launchpad.net/malone/bugs/30585
Comment:
Sorry - I actually meant strace katapult &> ~/katapult.strace
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
John Dong wrote:
strace by default only outputs to stderr, so redirecting stdout will
just give you the regular output. You can either use "strace katapult
2> filename", or "strace katapult -o filename".
would that be
strace -o filename katapult
(provide the -o to strace, not katapult)
?
strace by default only outputs to stderr, so redirecting stdout will just give you the regular output. You can either use "strace katapult 2> filename", or "strace katapult -o filename".
On 2/14/06, Martin Meredith <[EMAIL PROTECTED]> wrote:
Public bug report changed:https://launchpad.net/malone/bu
Public bug report changed:
https://launchpad.net/malone/bugs/30585
Comment:
can you run the following command
strace katapult > ~/katapult.strace
Then recreate the bug and attach the resulting file here?
Thanks!
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
https://lists.u
