Your message dated Sat, 28 Feb 2026 18:34:14 +0000
with message-id <[email protected]>
and subject line
has caused the Debian Bug report #995257,
regarding backintime-qt4: does not check if backup directory exists (or drive
is mounted)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
995257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995257
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: backintime-qt4
Version: 1.1.24-0.1
Severity: important
Hello,
when u use backintime and backintime-qt4 on a desktop,
the backup files are mostly on a remote medium, likely physically different
storage,
so this external location should be mounted before the backup is made.
* backup are mostly run regular basis, using (cron) anacron in this case
* a use case is an external usb-drive (harddisk)
the observed behaviour:
* if the backupdrive is mounted, no problem
* if the backupdrive is not mounted, the backup is made on the mountpoint
itself,
(eating up local storage)
* if later the backupdrive is mounted again for a another backup, the backup
continues, no problem
* but in the meanwhile there is local storage that is being occupied for
everytime the backup did not got to the backup drive (ie it was not mounted),
but the directory referring to the local mountpoint
so the problem: after a while using a laptop, with not always the backup-drive
connected, the hard drive gets filled with locally backup files,
that are not visible the backup is mounted, so one starts to wonder where all
the diskspace went :)
expected behaviour:
* no backup is made when the external drive is not mounted
more info about the cronjob
cat /var/spool/cron/crontabs/root
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/tmpisqqmnvj installed on Fri Nov 22 16:55:30 2019)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
#Back In Time system entry, this will be edited by the gui:
*/15 * * * * /usr/bin/nice -n 19 /usr/bin/ionice -c2 -n7 /usr/bin/backintime
backup-job >/dev/null 2>&1
while the setting is once a day in the gui,
and this seems the case in reality,
but this is not the reason, just a note
for now a manual fix is to change the cron entry with a preceeding mountpoint
check
hth,
Wim
-- System Information:
Debian Release: 10.10
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-0.bpo.8-amd64 (SMP w/16 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages backintime-qt4 depends on:
ii backintime-common 1.1.24-0.1
ii libnotify-bin 0.7.7-4
ii policykit-1 0.105-25
ii python3 3.7.3-1
ii python3-dbus.mainloop.qt 4.12.1+dfsg-2+b1
ii python3-pyqt4 4.12.1+dfsg-2+b1
ii x11-utils 7.7+4
Versions of packages backintime-qt4 recommends:
ii python3-secretstorage 2.3.1-2
Versions of packages backintime-qt4 suggests:
ii kompare 4:18.08.1-1
ii meld 3.20.0-2
-- no debconf information
--- End Message ---
--- Begin Message ---
tags -1 wontfix
tags -1 - fixed-upstream
--- End Message ---
