If Fortify source is turned of the problem *is* fixed and not simply
hidden.
The output indicates that that this crash is due to the fact that Bacula
was built with -DFORTIFY_SOURCE=2 (please check spelling). The glibc
code that implements this feature according to the authors of the code
may
I would recommend to the packagers to move up to Bacula version 2.4.2 as
quickly as possible. Versions 2.4.0 and 2.4.1 had a number of important
problems concerning mounting tape volumes particularly in manual mount
situations (non-autochanger). Version 2.4.2 is a critical bug fix to
versions
** Changed in: bacula (Ubuntu)
Status: Confirmed = Fix Released
--
package bacula-director-sqlite3 2.4.0-1ubuntu1 [modified: usr/sbin/bacula-dir
usr/sbin/dbcheck] failed to install/upgrade:
https://bugs.launchpad.net/bugs/246298
You received this bug notification because you are a
The crash isn't fixed -- it's just hidden. We need to drill down and
find the root-cause of the overflow.
** Changed in: bacula (Ubuntu)
Importance: Undecided = High
Assignee: (unassigned) = Zulnedi (zul)
Status: Fix Released = Confirmed
Target: None = intrepid-alpha-6
**
** Bug watch added: bugs.bacula.org/ #1138
http://bugs.bacula.org/view.php?id=1138
** Also affects: bacula via
http://bugs.bacula.org/view.php?id=1138
Importance: Unknown
Status: Unknown
--
package bacula-director-sqlite3 2.4.0-1ubuntu1 [modified: usr/sbin/bacula-dir
This has been fixed already in a recent upload.
Thanks
chuck
** Changed in: bacula (Ubuntu)
Status: Confirmed = Fix Released
--
package bacula-director-sqlite3 2.4.0-1ubuntu1 [modified: usr/sbin/bacula-dir
usr/sbin/dbcheck] failed to install/upgrade:
That's because bacula-director-sqlite3 2.4.0-1ubuntu1 fails to start:
Setting up bacula-director-sqlite3 (2.4.0-1ubuntu1) ...
* Stopping Bacula Director:
...done.
* Starting Bacula Director:
*** buffer overflow detected ***: /usr/sbin/bacula-dir terminated
=== Backtrace: =
