Package: bacula-console-qt Version: 5.0.2-1 Severity: normal
bat (from bacula-console-qt package) behaves strangly, showing menus missing information etc, and it goes away after some clicking, but is nevertheless very annoying. For example, you select a "Media" on the left pane, and enter some search filter at the top and click "apply" button to get a list of media. Double click on one media and new "Media Info" subwindows opens. If you right-click on that "Media Info" in right pane, you get only submenu giving only "Undock Media Info Window" option. That is wrong, you should also get "Close Page" option in addition in that submenu. If you however left-click first on "Media" and then right-click on "Media Info", you will get both options. That happens with a lot of other options too. According to posts on bacula users lists, it is probably due to wrong version of Qt used. Bat will apperently build seemlessly OK, but it will function is such broken behaviours. "Release Notes for Bacula 5.0.1" on http://www.bacula.org/en/?page=news say "For Packagers: [...] 3. Bat should be built on every platform that is capabable of running Qt. However, the Qt code is changing rather quickly and is not always compatible from version to version. We have built and verified bat on Qt 4.3.4. We strongly recommend that you do not build and distribute bat with any other version of Qt unless you personally test it. To build against Qt 4.3.4, download the depkgs-qt package from the Bacula Source Forge download location, read the README file and follow the instructions. If you are building for Bacula version 5.0.0, please ensure that you do not have qmake-qt4 loaded on your system. If you do, either remove it or rename it before trying to build bat. If you do not, bat will probably be built using the shared objects on your system. For Bacula 5.0.1 and later, this problem (bug) does not exist. depkgs-qt does not install Qt on your system, nor does it interfere with you having any other version of Qt installed on your system. Once you build bat with depkgs-qt, it should *not* use the Qt shared objects, but rather they will be linked into the program. After fully installing bat (make install), you can run "ldd bat" to see what shared objects it will use. If any Qt shared objects are referenced, something has gone wrong." So bacula-console-qt should probably be built as explained statically against Qt 4.3.4, instead of Qt 4.6.3 (or the code should be fixed to work correctly with different Qt versions). -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores) Locale: LANG=hr_HR.ISO-8859-2, LC_CTYPE=hr_HR.ISO-8859-2 (charmap=ISO-8859-2) Shell: /bin/sh linked to /bin/dash Versions of packages bacula-console-qt depends on: ii bacula-common 5.0.2-1 network backup, recovery and verif ii debconf 1.5.35 Debian configuration management sy ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-8 GCC support library ii libqtcore4 4:4.6.3-1 Qt 4 core module ii libqtgui4 4:4.6.3-1 Qt 4 GUI module ii libssl0.9.8 0.9.8o-1 SSL shared libraries ii libstdc++6 4.4.4-8 The GNU Standard C++ Library v3 ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra bacula-console-qt recommends no packages. bacula-console-qt suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
