[Bug 1280149] Re: Add Bacula fork Bareos to repository
Although it is true that the Bacula git repo has not been updated for some time, there is a good reason, for more information, please see: http://www.bacula.org - News There is indeed a fork of Bacula, but that fork has only *one* former Bacula developer. Although, like other open source projects, developers come and go, I have been contacted by a number of former and current Bacula developers and they all remain with Bacula. I would appreciate it if people who make incorrect statements such as Most of the devlopers [sic] switched to the Bareos would take the time to investigate or simply look at the Bacula website before making such comments. You should realize that the Bareos fork has some serious problems, including copyright violations and alleged theft of proprietary code, so though anyone is free to download and use the Bareos release, you you will be downloading code that may contain code that Bareos has no right to release. On the other hand, Bacula's copyright is held by the Free Software Foundation, Europe, and I can assure you that all code in Bacula is used by written permission. Bacula has been under development for 14 years now and will continue so in the future at a pace that is faster than any fork that is created by one person in secret over a 3 year period. There will be another release of Bacula in the March-April time frame, which will have a lot of new features, many planned well before the fork. If you are the interested in the saga of the Bareos fork, please see the new Bacula website (under development) at: http://blog.bacula.org Kern Sibbald Bacula Project Manager -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/1280149 Title: Add Bacula fork Bareos to repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1280149/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1280149] Bug 1280149] [NEW] Add Bacula fork Bareos to repository
Although it is true that the git repo has not been updated for some time, there is a good reason, for more information, please see www.bacula.org - News. There is indeed a fork of Bacula, but that fork has only *one* former Bacula developer. Although, like other open source projects, developers come and go, I have been contacted by a number of former and current Bacula developers and they all remain with Bacula. I would appreciate it if people who make incorrect statements such as Most of the devlopers [sic] switched to the Bareos would take the time to investigate or simply look at the Bacula website before making such comments. You should realize that the Bareos fork has some serious problems, including copyright violations and alleged theft of proprietary code, so though anyone is free to download and use the Bareos release, you you will be downloading code that may contain code that Bareos has no right to release. On the other hand, Bacula's copyright is held by the Free Software Foundation, Europe, and I can assure you that all code in Bacula is used by written permission. Bacula has been under development for 14 years now and will continue so in the future at a pace that is faster than any fork that is created by one person in secret over a 3 year period. There will be another release of Bacula in the March-April time frame, which will have a lot of new features, many planned well before the fork. If you are the interested in the saga of the Bareos fork, please see the new Bacula website (under development) at: http://blog.bacula.org -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/1280149 Title: Add Bacula fork Bareos to repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1280149/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 579924] Re: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10
Hello, The upgrade scripts used to update from one Bacula DB schema to the next are kept in bacula-src/src/cats and have names that begin with update_ There is one main script named update_bacula_tables (build during the ./configure command from update_bacula_tables.in). This script then calls the appropriate SQL backend script (e.g. update_postgresql_tables to actually do the schema modifications. That script must be called when installing a new version of Bacula AND when the database changes (normally only during major version changes). The rpm .spec files distributed with the project automatically call the script when needed, but we do not have .deb scripts, so that must be done by each packager (e.g. Ubuntu). That part is fairly straight forward. However, if you are updating Bacula and going from say version 1.38 to version 5.2.x, you may have several DB updates to make. These must be done one at a time, which can be slightly painful to know exactly which scripts need to be called. So to make packagers jobs a bit easier we supply a directory bacula-src/updatedb that has all the scripts necessary to upgrade from one DB version to the next (it may not have the very latest upgrade which is in src/cats). If you look in that directory and read the README file, you should be able to figure out what needs to be done. Also looking at the comments at the top of the upgrade scripts you will probably see what Bacula versions correspond to what DB versions. In the error message included in your subject line, it looks like the prior version of Bacula was running version 10 of the database schema, and the new version of Bacula that was loaded wants DB version 12. This means that the upgrade script from 10_to_11 must be applied followed by the script from 11_to_12. I hope this explanation helps. Best regards, Kern On 08/30/2012 05:38 PM, James Page wrote: As this bug is still being updated with comments I'm assuming its still impacting people. I took a look at the bacula packages in Lucid - they should be using dbconfig-common to do DB upgrades during packaging upgrade and I can see the required update scripts at version 3.0.0 (version 11) and 5.0.0 (version 12). So I'm a little mystified as to why this is not happening automatically. I'll do some more investigation. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/579924 Title: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10 To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/579924/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 579924] Re: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10
Hello, Disclaimer: I don't have anything to do with LTS (other than I develop on a Ubuntu system), so I cannot resolve the Ubuntu problem. However, I suggest you download the source, either from the Ubuntu source or from Source Forge and look in the updatedb directory. It has all the scripts you need to go from one version to the next. Note, there may be more than one script that needs to be applied depending on what Bacula versions involved. In your case, I imagine you must apply the 10_to_11 script, and then the 11_to_12 script, so that the database will be upgraded from version 10 to 11 then from 11 to 12. The text in the script tells you what Bacula versions the upgrade corresponds to. Best regards, Kern On 04/19/2012 10:21 PM, Martin wrote: I am a litte bit surprised: Bacula is NOT an universe package and a LTS to LTS upgrade is broken (8.04 to 10.04). But noone takes care of this issue - even after 2 years... And yes, I am affected by this problem: An upgrade from 8.04 to 10.04 does not work as expected. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/579924 Title: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10 To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/579924/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 579924] Re: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10
It looks like the Bacula version has changed between LTS versions, and in the change, the Bacula catalog database changed format, so it has a new version number. Updating the Bacula catalog is done automatically in rpms, but probably not in .debs. You must apply an update script that you can find in the bacula/src/cats directory or in the bacula/updatedb directory. Sometimes the updatedb is package separately. Actually, it looks like you need to apply two update scripts. One goes from 10 to 11 and the second from 11 to 12. Of course, that all depends on the Bacula version you are starting from and the one you are going to. Normally, if one upgrades each major bacula version (change in second digit of version), you will move only one database version at a time. You might ask packagers to include the update procedure automatically when installing new packages. It is a lot more user friendly. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/579924 Title: Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10 To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/579924/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 265102] Re: bacula not compiled with FORTIFY_SOURCE
This ticket is a bit old. Could someone please try turning on fortify source with a current 5.2.x version and see if there is a problem. If there is I will fix it. That said, I still recommend against using fortify source, as I previously wrote, Bacula has all its own routines since 10 years so adding fortify source will only add unnecessary additional overhead. Just the same, I would like to see this ticket closed one way or another. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/265102 Title: bacula not compiled with FORTIFY_SOURCE To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/265102/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 830108] Re: bacula director eror in initial conf file
Someone must have fat fingered something because upstream we have never had the semicolon misplaced as in the above problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/830108 Title: bacula director eror in initial conf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/830108/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 645097] Re: bat crashed with SIGSEGV in e_msg()
This looks like Bacula (bat) is blowing itself up with a segfault on purpose to get a dump. This usually happens after Bacula has detected an error in the bat.conf file. The only way to know exactly what is going on is to see what Bat has sent to stdout. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/645097 Title: bat crashed with SIGSEGV in e_msg() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/645097/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 735369] Re: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid
On Saturday 02 April 2011 02:23:21 Clint Byrum wrote: Kern, does this mean that there is an explicit fix in the code of 5.2.0 that will make this problem go away on Qt 4.6.2 ? There have been a very large number of changes to bat from 5.0.x to 5.2.0, including new features, bug fixes, and particularly seg fault fixes. I am sorry, I don't remember the specifics, and since I did not explicitly reproduce the reported bug, I am not sure there is an explicit fix, but I think so. While I do think we should put 5.2.0 in backports when it arrives, if the fix is simple it might be worth patching 5.0.1 so it works in lucid. There were a lot of changes, and I believe we have a significant number in the Director too, so any backporting might not be easy. You are free to try backporting but it is not something that I am personally going to do. This one is really hard to confirm as I don't have any files to restore in my test bacula. Is there a shorter test case? I don't know as I haven't explicitly reproduced the reported bug. I'm going to mark this as Incomplete, pending a shorter test case and/or answers from Kern. If its too hard to test, and/or too hard to fix in lucid, it might just have to be a Won't Fix. OK. I am not sure what your procedure is -- it might be good to note fixed in 5.2.x providing that is really the case. * Changed in: bacula (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 735369] Re: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid
On Saturday 02 April 2011 16:40:13 Clint Byrum wrote: Excerpts from Kern Sibbald's message of Sat Apr 02 07:20:23 UTC 2011: On Saturday 02 April 2011 02:23:21 Clint Byrum wrote: Kern, does this mean that there is an explicit fix in the code of 5.2.0 that will make this problem go away on Qt 4.6.2 ? There have been a very large number of changes to bat from 5.0.x to 5.2.0, including new features, bug fixes, and particularly seg fault fixes. I am sorry, I don't remember the specifics, and since I did not explicitly reproduce the reported bug, I am not sure there is an explicit fix, but I think so. While I do think we should put 5.2.0 in backports when it arrives, if the fix is simple it might be worth patching 5.0.1 so it works in lucid. There were a lot of changes, and I believe we have a significant number in the Director too, so any backporting might not be easy. You are free to try backporting but it is not something that I am personally going to do. This one is really hard to confirm as I don't have any files to restore in my test bacula. Is there a shorter test case? I don't know as I haven't explicitly reproduced the reported bug. I'm going to mark this as Incomplete, pending a shorter test case and/or answers from Kern. If its too hard to test, and/or too hard to fix in lucid, it might just have to be a Won't Fix. OK. I am not sure what your procedure is -- it might be good to note fixed in 5.2.x providing that is really the case. Hm. Sounds like this one may not get backported. The procedure is to mark the main bug task Fix Released, but then track each release of the package before that individually. Won't Fix means the bug is in that version, but we're not going to fix it. OK, your procedures are different from ours, which is OK. We normally indicate to the user that it is fixed in a future version. That is all I was trying to say. No problem however you do it :-) * Changed in: bacula (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid Status in Bacula the Network Backup Solution: New Status in “bacula” package in Ubuntu: Confirmed Bug description: Binary package hint: bacula-console-qt On lucid, in the Version Browser of bat, it is impossible to check the latest version of a file. This is described in the following upstream bug report: http://bugs.bacula.org/view.php?id=1550 (login using anonymous/anonymous) For convenience, here is the verbatim of the bug description: -- I often restore a single file, so I use Version Browser. 1) I browse for the file and when clicking on it, I see many different versions of it. 2) When I try to mark the file (tick the checkbox), it cannot be done 3) When I try to mark the most recent version of the file in 'Versions of File', it cannot be done 4) When I try to mark any other version of the file, it works OK 5) When there's another version of the file available (after the next backup), the version which couldn't be marked, can now be marked and the most recent can not It seems to be so for every job and every file within a job. I turned on all the debugging options of Bat, but there's nothing said when marking (or trying to) files/versions. - Response from the lead developer of Bacula: -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 735369] [NEW] Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid
The new version of Bacula (5.2.0) to be released in about a month has a number of fixes, and will work perfectly with Qt 4.6.2 (Lucid) where I have done the development work. There have been quite a number of enhancements and a lot of stability improvements in bat 5.2.0. As I previously reported, bat uses Qt, which has some important compatiblity problems between versions. Hopefully the new 5.2.0 bat will also work on Maveric. If not, I will be releasing a depkgs-qt-4.6.2 that can be used to compile bat on any Ubuntu release. Regards, Kern -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. https://bugs.launchpad.net/bugs/735369 Title: Bacula Admin Tool (bat) does not work well with Qt 4.6.2 in Lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 590887] Re: btraceback utility doesn't work
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 bug report. This will greatly help us in tracking down your problem. ** Changed in: bacula (Ubuntu) Status: New = Incomplete This kind of problem ptrace: Operation not permitted. is common when you run some of your daemons as non-root. The core dump is produced as root because Bacula is started as root, but as user bacula gdb won't work. One solution is for obtaining a traceback, run bacula as root. This is most appropriate for a one-shot reproducible case. Another solution might be to put the appropriate command (e.g. sudo) in the btraceback script so that the debugger is able to do its job. Regards, Kern -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. https://bugs.launchpad.net/bugs/590887 Title: btraceback utility doesn't work -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 590887] Re: btraceback utility doesn't work
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 bug report. This will greatly help us in tracking down your problem. ** Changed in: bacula (Ubuntu) Status: New = Incomplete By the way, I just wanted to mention that these kinds of problems are very clearly explained in the Kaboom chapter of the manual. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. https://bugs.launchpad.net/bugs/590887 Title: btraceback utility doesn't work -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 590894] Re: bacula-director crashes when nsswitch uses wins for hosts
There is an attachment - see on the right side of the page Bug attachments - debug messages and running under gdb It is just as I suspected: Bacula has called gethostbyname, which then seg faults when in the wins code. Unless Bacula is passing bad arguments to gethostbyname, which is highly unlikely, it is not a Bacula bug. It seems to me that someone has reported this some time ago, so I suspect it may not be a Ubuntu version bug. Unless someone can show me that Bacula is doing something wrong, I'm assuming at this point that it as an upstream OS or library bug. Kern -- bacula-director crashes when nsswitch uses wins for hosts https://bugs.launchpad.net/bugs/590894 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 579924] [NEW] Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10
It appears that the upgrade process attempted to upgrade two versions of the database at one time. Bacula only supports upgrading one version at a time, so from database version 10, you must first apply the scripts that do the upgrade to version 11, and then apply the upgrade scripts that upgrade from version 11 to version 12. All the scripts for an upgrade from the prior version to the version of the current release are found in bacula/src/cats ... All scripts for making an upgrade from an old version to a newer version (e.g. 8 to 9 or 10 to 11) are kept in bacula/updatedb. These scripts may need some manual editing to get the install locations to match where your database is installed. Kern On Thursday 13 May 2010 13:59:48 Tomasz wrote: Public bug reported: Binary package hint: bacula After upgrading Ubuntu from 8.04 LTS to 10.04 LTS backup software Bacula stopped working, starting bacula-director MySQL version results in: bacula-dir JobId 0: Fatal error: Version error for database bacula. Wanted 12, got 10 During upgrade Bacula was upgraded from 2.2 series (db version 10) to 5.0 (db version 12), dpkg.log shows. 2010-05-12 21:16:32 upgrade bacula-director-mysql 2.2.8-5ubuntu7.2 5.0.1-1ubuntu1 and /usr/share/bacula-director/update_mysql_tables upgrades only from db version 11: This script will update a Bacula MySQL database from version 11 to 12 which is needed to convert from Bacula Enterprise 2.6 to 4.0 or Standard version 3.0 to 5.0 I expected to have the database upgraded from version 10 to 12 when upgrading Ubuntu LTS series. ** Affects: bacula Importance: Undecided Status: New ** Affects: bacula (Ubuntu) Importance: Undecided Status: New ** Also affects: bacula Importance: Undecided Status: New -- Upgrading Ubuntu LTS skips database version - Fatal error: Version error for database bacula. Wanted 12, got 10 https://bugs.launchpad.net/bugs/579924 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 459573] Re: variable expansion uses outdated data
** Changed in: bacula Status: New = Invalid -- variable expansion uses outdated data https://bugs.launchpad.net/bugs/459573 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 459573] Re: variable expansion uses outdated data
Fair enough, obviously I have misunderstood the use case for variable expansion. My apologies. No need to appologize. Bacula is very complicated, and it is not always obvious what features to use to do what you want (even for me sometimes). Unfortunately, for lots of reasons variable expansion never really worked out in Bacula. Some day, it will be removed once I find something better (probably plugins). Kern -- variable expansion uses outdated data https://bugs.launchpad.net/bugs/459573 You received this bug notification because you are subscribed to Bacula. Status in Bacula the Network Backup Solution: New Status in âbaculaâ package in Ubuntu: Invalid Bug description: Binary package hint: bacula I use $Client-$Year-$Month-$Day as my LabelFormat. Recently I tried to backup a server called ralph (this was a scheduled job). The Volume was created with the correct name but the job failed as the FileDaemon was not running, as below: 24-Oct 08:17 floyd-dir JobId 65: Created new Volume ralph-fd-2009-10-24 in catalog. 24-Oct 08:17 floyd-dir JobId 65: Using Device FileStorage 24-Oct 08:17 floyd-dir JobId 65: Warning: bsock.c:123 Could not connect to Client: ralph-fd on 192.168.1.254:9102. ERR=Connection refused The job eventually terminated itself. Subsequently I tried to run a job manually to backup a different server (benson) and got the following output: 24-Oct 13:43 floyd-dir JobId 66: No prior Full backup Job record found. 24-Oct 13:43 floyd-dir JobId 66: No prior or suitable Full backup found in catalog. Doing FULL backup. 24-Oct 13:43 floyd-dir JobId 66: Start Backup JobId 66, Job=benson.2009-10-24_13.43.03 24-Oct 13:43 floyd-dir JobId 66: Using Device FileStorage 24-Oct 13:43 floyd-sd JobId 66: Labeled new Volume ralph-fd-2009-10-24 on device FileStorage (/bacula-volumes). 24-Oct 13:43 floyd-sd JobId 66: Wrote label to prelabeled Volume ralph-fd-2009-10-24 on device FileStorage (/bacula-volumes) 24-Oct 13:43 floyd-dir JobId 66: Volume used once. Marking Volume ralph-fd-2009-10-24 as Used. Note that the Volume name is again ralph-fd-2009-10-24. It should have been benson-fd-2009-10-24. It looks like the variable expansion has retained the client name ralph-fd from the failed job. Either that or bacula is not trying to create a new volume at all, but instead reusing the volume created previously but not labelled or written to. r...@floyd:~# lsb_release -rd Description: Ubuntu 8.04.3 LTS Release: 8.04 r...@floyd:~# apt-cache policy bacula bacula: Installed: (none) Candidate: 2.2.8-5ubuntu7.2 Version table: 2.2.8-5ubuntu7.2 0 500 http://mirror.internode.on.net hardy-updates/main Packages 2.2.8-5ubuntu7 0 500 http://mirror.internode.on.net hardy/main Packages Best regards, Kern -- variable expansion uses outdated data https://bugs.launchpad.net/bugs/459573 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 459573] Re: variable expansion uses outdated data
One of the reasons for using Bacula is so that you don't have to track what Volumes it is using. It does all the work for you, and if you trust it, you won't need particular Volume labels. That said, If you really want to use Client based Volume labels, you can, but to do so, the only reasonable way is to work with Pools and either prelabel your Volumes, or use some labeling scheme such as you did. If you do not use Pools, there is no way to absolutely guarantee that Bacula will write on a Volume you have just created. With Pools, at least you can guarantee that it will write on a Volume within a given Pool. There is a whole chapter in the manual describing this for Full, Differential, and Incremental backups, which can be easily extrapolated to Clients. So, in my opinion, it isn't so much a question of a feature being worse than useless, but rather learning which features will accomplish what you want. On Monday 02 November 2009 04:38:38 Aidan Furlan wrote: I would certainly consider this a bug. It makes variable expansion worse than useless because I can no longer trust it to label volumes with the correct client or date, so that all the volume names are potentially misleading. To avoid misleading data I have gone back to using LabelFormat=Vol. -- variable expansion uses outdated data https://bugs.launchpad.net/bugs/459573 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 387778] Re: Incorrect application entry for bacula-console-qt
On Tuesday 16 June 2009 20:17:49 Brian Murray wrote: Thanks for taking the time to report this bug and including a patch. However, the .desktop file is generated when building the source package so your patch, while it fixes the resulting .desktop file, won't apply to the package. I'm not quite certain how to fix this myself, but I believe you can investigate the problem further by using 'apt-get source bacula' and then looking at 'scripts/bat.desktop.in' in the package. A few responses: First some gripes about this bug tracking system: 1. Your bug emails generated by your system apparently don't take into account that there may be more one place we get bug emails. I recommend that you add something like Launchpad.bacula or something like that to the Subject line as all other bug systems do. 2. Bug reports should never be directly addressed to people receiving them in a copy form -- as is the case for me. It is very confusing. This emails was addressed to me as: From: Brian Murray br...@ubuntu.com To: k...@sibbald.com Date: Today 20:17:49 which is incorrect since the bug report is copied to me. 3. I would like to unsubscribe from this list, but it seems to be next to impossible. Would you please tell me how? Thanks. = Now to answer the bug report. 4. The problem appears to be that the packaging of Bacula was incorrectly done. Bacula should be configured and built prior to packaging, and the configuration *must* correspond to the exact same places the packager is going to install files. Otherwise you introduce packing bugs as you have here. More specifically. It appears that the packager configured and built Bacula to install in /usr/sbin/bat (or at least that is where Bat was set to be installed), and then during the installation of the Bacula package, bat (the executable) was put into /usr/bin/bat. Thus the desktop files are not in synchronization with where the binary was installed. Regards, Kern Upstream Bacula Project Manager -- Incorrect application entry for bacula-console-qt https://bugs.launchpad.net/bugs/387778 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 387778] Re: Incorrect application entry for bacula-console-qt
On Tuesday 16 June 2009 21:46:08 Martin Kalén wrote: 2009/6/16 Kern Sibbald k...@sibbald.com 1. Your bug emails generated by your system apparently don't take into account that there may be more one place we get bug emails. I recommend that you add something like Launchpad.bacula or something like that to the Subject line as all other bug systems do. Sorry for the noise, as a public Ubuntu bug reporter I was not aware that Launchpad would spam people upstream before someone at Ubuntu had triaged the bug. Sorry I should have been more specific. No need for you to be sorry as a reporter of a problem (at least that is what I imagine). It has something to do with the lauchpad system that I haven't yet figured out. 2. Bug reports should never be directly addressed to people receiving them in a copy form -- as is the case for me. It is very confusing. Indeed - I was just as confused when your Launchpad reply first appeared to be a private e-mail reply. 4. The problem appears to be that the packaging of Bacula was incorrectly done. Bacula should be configured and built prior to packaging, and the configuration *must* correspond to the exact same places the packager is going to install files. Otherwise you introduce packing bugs as you have here. Thanks for your clarification. Obviously the Ubuntu (or Debian) package maintainer needs to fix this. Yes, someone should figure out some way to test these things, but with GUIs it is not so easy :-( I hope you succeed in unsubscribing from the Launchpad notifications Thanks. and once again my apologies for generating noise. For the apologies, thanks, no harm done, but as I said, it is not your fault. Regards, Kern -- Incorrect application entry for bacula-console-qt https://bugs.launchpad.net/bugs/387778 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 286643] Re: bacula client configuration is broken out of the box
On Tuesday 21 October 2008 18:36:11 Mathias Gug wrote: Hi Scott, Thanks for taking the time to get in touch with the Ubuntu Development team. We understand that bacula is planning to send a couple of developers to Fosscamp, and think that might be an appropriate forum to collaborate on a final solution. I'll attend Fooscamp and I'm ready to discuss this issue with them. Is is this an acceptable solution for you? I won't speak for Scott for the above question, but I will be attending FossCamp, and would be more than happy to provide as much help as I can to arrive at solutions for all problems, concerns or questions you may have about Bacula. Kern Sibbald Bacula Project Manager -- bacula client configuration is broken out of the box https://bugs.launchpad.net/bugs/286643 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 227613] Re: [SRU] SIGSEGV in bacula-fd
On Saturday 27 September 2008 09:45:11 Ante Karamatić wrote: On Thu, 25 Sep 2008 20:36:41 - Kern Sibbald [EMAIL PROTECTED] wrote: On Wednesday 24 September 2008 20:04:18 Ante Karamatić wrote: The upstream bug has not been fixed in 2.2.8!! I haven't said that :) OK, no problem. I didn't take offense, hope you didn't, but just wanted to clarify. The bug *was* fixed in the 2.2.8 version with two patches. Did you apply them? We have 2.2.8 version in Ubuntu 8.04, and this bug is filed for 2.2.8. I think it was fixed later in bacula, not in 2.2.8... The bug in the main Bacula 2.2.8 Branch HEAD is fixed because the code is identical to the current 2.4.2 code. That is if 2.2.8 is fully and correctly patched with the released patches, it should have this bug and others fixed. It is possible that there were confusions with the patches in getting from the first 2.2.8 to the version that is in the SVN. In any case, what is clear to me is that we have no problems in the 2.4.x base with this bug and that the 2.4.0 was pulled from the last 2.2.8 and that no additional strippath changes were made in the 2.4.x versions. If not an easy way to fix it is to take src/dird/backup.c from either the last commit to Branch-2.2 or from the current released code (Branch-2.4) rather than trying to apply the patches. I guess you are referring to src/filed/backup.c? If yes, that file is exactly the same in my PPA version and in 2.4.2. Yes, sorry. I should have said src/filed/backup.c src/dird/backup.c has more differences, but I don't think those are relevant for this bug. Yes, you are correct. We'll wait for Sergio to test my PPA version. OK, if you have a 2.2.8 src/filed/backup.c that is the same as on 2.4.2, then the bug *should* be fixed. If not, I will be worried ... By the way, what does PPA mean and where does one find those versions? Thanks ... -- [SRU] SIGSEGV in bacula-fd https://bugs.launchpad.net/bugs/227613 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 241480] Re: bacula-fd does not start when installed via bacula-client
On Wednesday 24 September 2008 11:07:52 Ante Karamatić wrote: It's worth mentioning that after the network is started, avahi (on default install) looks at DNS to see if '.local' domain is served by DNS server. If that's true, avahi doesn't start. If there is no DNS for '.local', avahi will start. Since it takes some time to register an IP with a hostname, it is possible that bacula-fd is started before that registration happens. This results in unresolvable hostname and thuss failure to start. I suggest using 'localhost' if you desire to have '127.0.0.1'. If there is an non-local interface (eth0, eth1, wlan0, ...), d420.local will be a record for non-local IP. This bug is valid, but at the moment is unresolvable. Ubuntu has plans on replacing SysV init system with upstart, which could solve this issue. I'm closing this bug. If you feel that's wrong, please reopen it. ** Changed in: bacula (Ubuntu) Status: Triaged = Won't Fix I don't understand why you cannot start Bacula after the network is up and running and DNS is serving names. That is how it works on all other systems. We have never run into this problem elsewhere, so I cannot understand why it is unresolvable. -- bacula-fd does not start when installed via bacula-client https://bugs.launchpad.net/bugs/241480 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 222558] Re: password in bacula-fd.conf is not auto-generated
On Wednesday 24 September 2008 11:13:20 Ante Karamatić wrote: I'll mark this bug as 'medium' at the moment. But this should be resolved as soon as possible. Kern, of course, any code would be welcome. It's clear that we should generate password on postinstall of package, not during compile-time. ** Changed in: bacula (Ubuntu) Importance: Undecided = Medium Status: New = Confirmed I am not (yet) a Debian packaging expert, so I asked the Bacula .deb guy (Eric), and this is his response. Sorry for emailer wrapping, but you can probably figure it out. On Wednesday 24 September 2008 16:18:58 you wrote: Hello Eric, Do you have some .deb magic I could send off to the Ubuntu Bacula maintainers so that they can generate random passwords when installing Bacula? I use the bacula-common configuration script (debian/bacula-common.config) to compute and store random password for all bacula packages. (my template file is ok too) if ! db_get bacula/director_passwd; then db_set bacula/director_passwd $(cat /dev/urandom | tr -dc _A-Z-a-z-0-9 | head -c33) db_set bacula/director_mpasswd $(cat /dev/urandom | tr -dc _A-Z-a-z-0-9 | head -c33) db_set bacula/fd_passwd $(cat /dev/urandom | tr -dc _A-Z-a-z-0-9 | head -c33) db_set bacula/fd_mpasswd $(cat /dev/urandom | tr -dc _A-Z-a-z-0-9 | head -c33) db_set bacula/sd_passwd $(cat /dev/urandom | tr -dc _A-Z-a-z-0-9 | head -c33) db_set bacula/sd_mpasswd $(cat /dev/urandom | tr -dc _A-Z-a-z-0-9 | head -c33) fi After that, i use special strings to replace password in configuration file (like for RPM) ./configure ... --with-dir-password=XXX_REPLACE_WITH_DIRECTOR_PASSWORD_XXX \ --with-fd-password=XXX_REPLACE_WITH_CLIENT_PASSWORD_XXX \ --with-sd-password=XXX_REPLACE_WITH_STORAGE_PASSWORD_XXX \ --with-mon-dir-password=XXX_REPLACE_WITH_DIRECTOR_MONITOR_PASSWORD_XXX \ --with-mon-fd-password=XXX_REPLACE_WITH_CLIENT_MONITOR_PASSWORD_XXX \ --with-mon-sd-password=XXX_REPLACE_WITH_STORAGE_MONITOR_PASSWORD_XXX \ At the end, i just have to replace XXX_...XXX strings by what we have computed in each package.postinst script. db_get bacula/director_mpasswd db_dir_mpass=$RET db_get bacula/fd_mpasswd db_fd_mpass=$RET db_get bacula/sd_mpasswd db_sd_mpass=$RET db_stop sed \ -e s%XXX_REPLACE_WITH_DIRECTOR_MONITOR_PASSWORD_XXX%$db_dir_mpass% \ -e s%XXX_REPLACE_WITH_STORAGE_MONITOR_PASSWORD_XXX%$db_sd_mpass% \ -e s%XXX_REPLACE_WITH_CLIENT_MONITOR_PASSWORD_XXX%$db_fd_mpass% \ $SRCDIR/$CONFIG $TARGET At the end, if you configure FD/SD/DIR/Console on the same box, all your passwords will be ok. They have also to remove the XXAddress = 127.0.0.1 from all configuration file. -- password in bacula-fd.conf is not auto-generated https://bugs.launchpad.net/bugs/222558 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 241480] Re: bacula-fd does not start when installed via bacula-client
On Wednesday 24 September 2008 19:32:44 Ante Karamatić wrote: On Wed, 24 Sep 2008 13:58:46 - Kern Sibbald [EMAIL PROTECTED] wrote: I don't understand why you cannot start Bacula after the network is up and running and DNS is serving names. That is how it works on all other systems. We have never run into this problem elsewhere, so I cannot understand why it is unresolvable. Avahi is an implementation of the DNS Service Discovery and Multicast DNS specifications for Zeroconf Networking. It uses 'special' '.local' domain. Problem is that network is up, but the user is using 'hostname.local' FQDN. This FQDN isn't managed by DNS, so it isn't resolvable. This domain is managed by interaction between all computers, which over Zeroconf talk to each other and arrange their FQDN inside '.local' domain. This can take a minute or two. This is why Bacula is started before the FQDN is resolvable. We could resolve this problem if we would stall booting of all services untill avahi registers server, but this isn't a nice solution :/. Upstart enables state driven booting, so all services would boot up, except those that depend on avahi. Those will wait until upstart declares that mDNS is up. http://en.wikipedia.org/wiki/Zeroconf OK, thanks for the explanation. I was unaware of the Zeroconf problems, and agree that stalling all services at boot time is not a good solution. I am going to note this because I imagine it will come up in other distros ... -- bacula-fd does not start when installed via bacula-client https://bugs.launchpad.net/bugs/241480 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 222558] Re: password in bacula-fd.conf is not auto-generated
I was not aware of this bug (sorry, I should look at them all), but I think I can shed some light on it and even provide the code necessary to fix it. Basically the user is saying that each Bacula daemon generated needs a shared secrete random password used for authentication, and these passwords *must* be generated at install time to be unique. I have not looked at your packages but I believe that you inherited them from Debian where I have reported this problem. The passwords that you release in the bacula-xx.conf files are generated by Bacula at build time, and thus are installed on all systems, and hence are not secure, and this applies to all versions of Bacula that you have packaged. If you have explicitly added code in the install process that generates random passwords, then this bug should be closed, otherwise, it should be left open and marked as a security problem. Note, this is a packaging problem. Bacula generates random passwords during the ./configure process, so everything is consistent, but once it is packaged, the packager needs to create similar code to the Bacula ./configure so that all installations will have different passwords. If you want, I can provide you with sample code suitable to put in your installation packages. -- password in bacula-fd.conf is not auto-generated https://bugs.launchpad.net/bugs/222558 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 228693] Re: [SRU] bacula-director-pgsql postinstall broken
Thanks for upgrading to the 2.4.2 version, which is much more stable than 2.4.0 and 2.4.1. One additional consideration when producing Bacula packages. I regularly release well tested patches to bugs to the bacula-bugs section of the Source Forge release are. When you are building new packages, you might want to check what has been released there. Sometimes the fixes are trivial, but other times, they are important. These patches are also available in the current branch Branch-2.4 and the trunk SVN (now imported to Lauchpad Bazaar) in bacula/patches and are all named 2.4.2-xxx.patch. It is possible from time to time that the patches are order dependent, so they should be applied in order of their date. In the Notes section of the Source Forge bacula-bugs release the patches are listed with the most recent one on top. Finally, the documentation on what the patch fixes or possibly fixes, if we don't have a positive confirmation, and how to apply the patches is at the top of each patch file. Personally, I prefer to pull the current Branch-2.4 rather than applying patches, but everyone has his own way of handling these things. If there is anything I can do to make this all easier for you, please don't hesitate to let me know: kern at sibbald.com Kern Bacula upstream -- [SRU] bacula-director-pgsql postinstall broken https://bugs.launchpad.net/bugs/228693 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 246298] Re: package bacula-director-sqlite3 2.4.0-1ubuntu1 [modified: usr/sbin/bacula-dir usr/sbin/dbcheck] failed to install/upgrade:
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 generate false positives, and that is indeed the case here. The code reports a buffer overflow where one does *not* exist. This problem is easily detected because after building Bacula and running any test case, it crashes the first and every time. Solution: 1. Build Bacula without the fortify source option. It is unnecessary, a flawed implementation, and Bacula does its own checking for these things. 2. Please always run the regression scripts after building a new version. Best regards, Kern -- 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 member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 246298] Re: package bacula-director-sqlite3 2.4.0-1ubuntu1 [modified: usr/sbin/bacula-dir usr/sbin/dbcheck] failed to install/upgrade:
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 2.4.0 and 2.4.1 that is completely compatible with no major changes other than bug fixes and has proved quite stable. Regards, Kern -- 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 member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 265102] Re: bacula not compiled with FORTIFY_SOURCE
This problem *should* already be fixed in the trunk, though I have never actually tried building and running it with fortify source. We *strongly* recommend not to enable fortify source. Bacula is already well protected and has its own buffer overrun detection that in general detects most overrun problems earlier and better than glibc and produces a reasonable traceback in the process. If you do enable fortify source, we cannot exclude that you will encounter other such problems. -- bacula not compiled with FORTIFY_SOURCE https://bugs.launchpad.net/bugs/265102 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211297] Re: bat crashed with SIGSEGV
The threaded stack trace doesn't make much sense to me because it shows that bat is seg faulting in wait_data_intr() because the class pointer is NULL. Can you answer the following? - What version of the compiler are you using? - Have you or the packaging changed any of Bacula's default compile options? - Can you reproduce the problem? (off hand it looks like it) - Can you show me how to reproduce it? By the way, I use bat all the time via an ssh connection without problems. Thanks, Kern (upstream) -- bat crashed with SIGSEGV https://bugs.launchpad.net/bugs/211297 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 211297] Re: bat crashed with SIGSEGV
Hello Reinhard, On Monday 14 April 2008 19:47:25 meux wrote: Hi Kern, thanks for your answer. I am using the default package provided by Ubuntu Hoary. I haven't compiled it nor have ich changed any compile options. OK. I think this error occurs, when i close bat via File-Quit but i am not sure if it causes same error as above. Yes, we had several problems (seg faults, loops, ...) terminating everything in Qt in the right order. In your traceback, it appeared that you had just entered something into an edit box when it failed. Perhaps you entered quit. I use bat 1.0 in combination with bacula director version 1.36 (Debian Sarge). I'm quite surprised that bat works at all with a Bacula Director version 1.36. The first Director, with which bat works is 2.2.0 -- this is because we added a lot of new console GUI support between version 2.0.x and 2.2.0. In fact, bat can be successfully used only with the Director with which it was shipped because we are still enhancing the console API. To have a supported bat, you really need to move up to a 2.2.x version, which may be a bit of a pain as there were at least 2 Bacula database upgrades in between ... Best regards, Kern -- bat crashed with SIGSEGV https://bugs.launchpad.net/bugs/211297 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 list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
