I'll have to dig a bit, but I know the package source in Mint 18 is unmodified from Ubuntu xenial, and I didn't see any indication that it was different than what's in debian.

I think what may be happening is, Ubuntu xenial (a LTS release IIRC) tracks something newer than debian stable (maybe testing?) It has 7.0.5. Debian stable is still on 5.x, with an older rules file that probably doesn't have the linker flag that's causing trouble. Debian unstable, and newer Ubuntu have 7.4.3 or 7.4.4, where Kern has worked around the issue. I think people using the director are more likely to be doing so on Debian and thus are getting the 5.x code without the linker flag. Likewise, people's on the newest Ubuntu probably have something >= 7.4.3, where it's worked around. So I think only people on the Ubuntu LTS release (xenial) or Mint 18 (brand new, but based on xenial) are getting hit with it, and like Kern said, it may only manifest if certain defaults are in use.

Even though it's fixed in the 7.4.x from Ubuntu (probably in debian too), if it's indeed broken in debian, I'm going to ask if they can release an update to their 7.0.5 package in testing, so that people who track that, or distros that are derived from it, don't get a broken bacula out of the box.

I think compiler optimizations and linker tweaks that change the fundamental functioning of your code aren't great things to turn on by default :-/ It's hard enough to develop and maintain software without your tools fighting against you!

-Jonathan Hankins

On Sun, Oct 2, 2016, 12:45 AM Kern Sibbald <kern AT sibbald DOT com> wrote:

I have not heard of this on Debian, but it is a problem on Ubuntu and in their bugzilla database.  I suspect that even though Ubuntu takes a number of Debian packages, they probably add some different linking options.

On 10/02/2016 01:41 AM, Sven Hartge wrote:

On 01.10.2016 16:51, Hankins, Jonathan wrote:

It seems weird that the bacula package in Debian and Ubuntu, et al, is
broken and no one has noticed (checked Debian bug database). I know
Debian has been on 5.x in the stable release for years (still is). It's
possible that 7.0.5 got packaged for their testing release and maybe
Ubuntu xenial picked it up and thus Mint 18. My guess is most folks
using bacula on a Debian distro are on Debian stable, and not Ubuntu or
mint (workstation oriented releases...if anything, may be using
bacula-fd) and thus no one has noticed. I'll do a little digging and
talk to the person who packages bacula for Debian and see if I figure it
out.

I don't know about Bacula being broken on Debian.

I've been using Bacula at work on Debian since version 1.34 back in 2004
and had it never not work. Right now I am up to 7.4.3 on Jessie from
backports, running backups for about 250 systems.

Privately I run in Debian Unstable, backuping 10 systems to disk and
tape. Again, never experienced the problems you have.

If Bacula was unusable and broken on Debian, there would be bug reports
in the BTS.

Grüße,
Sven.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

This e-mail is intended only for the recipient and may contain confidential or proprietary information. If you are not the intended recipient, the review, distribution, duplication or retention of this message and its attachments is prohibited. Please notify the sender of this error immediately by reply e-mail, and permanently delete this message and its attachments in any form in which they may have been preserved.