** Changed in: bacula (Ubuntu)
Importance: Medium = Wishlist
** Changed in: bacula (Ubuntu)
Status: Incomplete = Opinion
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
On Monday 07 March 2011 16:12:51 Chuck Short wrote:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the
On Monday 07 March 2011 16:12:51 Chuck Short wrote:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the
So maybe the btraceback script should run gdb within sudo, provided that
the script checks if the user is a member of the bacula group.
Please note that this bug is not about a cause of the signal 11; it is
about the btraceback script not working by default.
--
You received this bug
** Changed in: bacula (Ubuntu)
Importance: Undecided = Medium
--
btraceback utility doesn't work
https://bugs.launchpad.net/bugs/590887
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in ubuntu.
--
Ubuntu-server-bugs mailing
