Description of problem: I installed Mageia 9 today (08/31/2023) without problems and it works well. However, having installed backintime, the backup/restore program (as a simple user or as root) does not run. backintime-common Version : 1.3.3-1.mga9 Version actuellement installée : 1.3.3-1.mga9 Groupe : Archivage/Sauvegarde Architecture : noarch Taille : 1301 Ko Média : Aucun (installé) /etc/xdg/autostart/backintime.desktop /usr/bin/backintime /usr/bin/backintime-askpass /usr/share/backintime /usr/share/backintime/common /usr/share/backintime/common/applicationinstance.py /usr/share/backintime/common/askpass.py /usr/share/backintime/common/backintime.py /usr/share/backintime/common/bcolors.py /usr/share/backintime/common/cli.py /usr/share/backintime/common/config.py /usr/share/backintime/common/configfile.py /usr/share/backintime/common/create-manpage-backintime-config.py /usr/share/backintime/common/diagnostics.py /usr/share/backintime/common/driveinfo.py /usr/share/backintime/common/dummytools.py /usr/share/backintime/common/encfstools.py /usr/share/backintime/common/exceptions.py /usr/share/backintime/common/guiapplicationinstance.py /usr/share/backintime/common/logger.py /usr/share/backintime/common/mount.py /usr/share/backintime/common/password.py /usr/share/backintime/common/password_ipc.py /usr/share/backintime/common/pluginmanager.py /usr/share/backintime/common/progress.py /usr/share/backintime/common/snapshotlog.py /usr/share/backintime/common/snapshots.py /usr/share/backintime/common/sshMaxArg.py /usr/share/backintime/common/sshtools.py /usr/share/backintime/common/tools.py /usr/share/backintime/plugins /usr/share/backintime/plugins/usercallbackplugin.py /usr/share/bash-completion/completions/backintime /usr/share/doc/backintime /usr/share/doc/backintime/AUTHORS /usr/share/doc/backintime/CHANGES /usr/share/doc/backintime/LICENSE /usr/share/doc/backintime/README.md /usr/share/doc/backintime/TRANSLATIONS /usr/share/doc/backintime/VERSION /usr/share/doc/backintime/copyright /usr/share/doc/backintime/examples /usr/share/doc/backintime/examples/config-example-local.gz /usr/share/doc/backintime/examples/config-example-ssh.gz /usr/share/locale/ar/LC_MESSAGES/backintime.mo /usr/share/locale/bg/LC_MESSAGES/backintime.mo /usr/share/locale/bs/LC_MESSAGES/backintime.mo /usr/share/locale/ca/LC_MESSAGES/backintime.mo /usr/share/locale/cs/LC_MESSAGES/backintime.mo /usr/share/locale/da/LC_MESSAGES/backintime.mo /usr/share/locale/de/LC_MESSAGES/backintime.mo /usr/share/locale/el/LC_MESSAGES/backintime.mo /usr/share/locale/en_CA/LC_MESSAGES/backintime.mo /usr/share/locale/en_GB/LC_MESSAGES/backintime.mo /usr/share/locale/eo/LC_MESSAGES/backintime.mo /usr/share/locale/es/LC_MESSAGES/backintime.mo /usr/share/locale/et/LC_MESSAGES/backintime.mo /usr/share/locale/eu/LC_MESSAGES/backintime.mo /usr/share/locale/fi/LC_MESSAGES/backintime.mo /usr/share/locale/fo/LC_MESSAGES/backintime.mo /usr/share/locale/fr/LC_MESSAGES/backintime.mo /usr/share/locale/gl/LC_MESSAGES/backintime.mo /usr/share/locale/he/LC_MESSAGES/backintime.mo /usr/share/locale/hr/LC_MESSAGES/backintime.mo /usr/share/locale/hu/LC_MESSAGES/backintime.mo /usr/share/locale/id/LC_MESSAGES/backintime.mo /usr/share/locale/is/LC_MESSAGES/backintime.mo /usr/share/locale/it/LC_MESSAGES/backintime.mo /usr/share/locale/ja/LC_MESSAGES/backintime.mo /usr/share/locale/jv/LC_MESSAGES/backintime.mo /usr/share/locale/ko/LC_MESSAGES/backintime.mo /usr/share/locale/lt/LC_MESSAGES/backintime.mo /usr/share/locale/nb/LC_MESSAGES/backintime.mo /usr/share/locale/nl/LC_MESSAGES/backintime.mo /usr/share/locale/nn/LC_MESSAGES/backintime.mo /usr/share/locale/pl/LC_MESSAGES/backintime.mo /usr/share/locale/pt/LC_MESSAGES/backintime.mo /usr/share/locale/pt_BR/LC_MESSAGES/backintime.mo /usr/share/locale/ro/LC_MESSAGES/backintime.mo /usr/share/locale/ru/LC_MESSAGES/backintime.mo /usr/share/locale/sk/LC_MESSAGES/backintime.mo /usr/share/locale/sl/LC_MESSAGES/backintime.mo /usr/share/locale/sr/LC_MESSAGES/backintime.mo /usr/share/locale/sv/LC_MESSAGES/backintime.mo /usr/share/locale/th/LC_MESSAGES/backintime.mo /usr/share/locale/tr/LC_MESSAGES/backintime.mo /usr/share/locale/uk/LC_MESSAGES/backintime.mo /usr/share/locale/zh_CN/LC_MESSAGES/backintime.mo /usr/share/locale/zh_TW/LC_MESSAGES/backintime.mo /usr/share/man/man1/backintime-askpass.1.xz /usr/share/man/man1/backintime-config.1.xz /usr/share/man/man1/backintime.1.xz and backintime-qt Version : 1.3.3-1.mga9 Version actuellement installée : 1.3.3-1.mga9 Groupe : Archivage/Sauvegarde Architecture : noarch Taille : 595 Ko Média : Aucun (installé /etc/dbus-1/system.d/net.launchpad.backintime.serviceHelper.conf /etc/pam.d/backintime-qt-root /etc/security/console.apps/backintime-qt-root /usr/bin/backintime-qt /usr/bin/backintime-qt-root /usr/bin/backintime-qt_polkit /usr/sbin/backintime-qt-root /usr/share/applications/backintime-qt-root.desktop /usr/share/applications/backintime-qt.desktop /usr/share/backintime/plugins/notifyplugin.py /usr/share/backintime/plugins/qt4plugin.py /usr/share/backintime/qt /usr/share/backintime/qt/__pycache__ /usr/share/backintime/qt/__pycache__/app.cpython-310.opt-1.pyc /usr/share/backintime/qt/__pycache__/app.cpython-310.pyc /usr/share/backintime/qt/__pycache__/icon.cpython-310.opt-1.pyc /usr/share/backintime/qt/__pycache__/icon.cpython-310.pyc /usr/share/backintime/qt/__pycache__/logviewdialog.cpython-310.opt-1.pyc /usr/share/backintime/qt/__pycache__/logviewdialog.cpython-310.pyc /usr/share/backintime/qt/__pycache__/messagebox.cpython-310.opt-1.pyc /usr/share/backintime/qt/__pycache__/messagebox.cpython-310.pyc /usr/share/backintime/qt/__pycache__/qtsystrayicon.cpython-310.opt-1.pyc /usr/share/backintime/qt/__pycache__/qtsystrayicon.cpython-310.pyc /usr/share/backintime/qt/__pycache__/qttools.cpython-310.opt-1.pyc /usr/share/backintime/qt/__pycache__/qttools.cpython-310.pyc /usr/share/backintime/qt/__pycache__/restoredialog.cpython-310.opt-1.pyc /usr/share/backintime/qt/__pycache__/restoredialog.cpython-310.pyc /usr/share/backintime/qt/__pycache__/serviceHelper.cpython-310.opt-1.pyc /usr/share/backintime/qt/__pycache__/serviceHelper.cpython-310.pyc /usr/share/backintime/qt/__pycache__/settingsdialog.cpython-310.opt-1.pyc /usr/share/backintime/qt/__pycache__/settingsdialog.cpython-310.pyc /usr/share/backintime/qt/__pycache__/snapshotsdialog.cpython-310.opt-1.pyc /usr/share/backintime/qt/__pycache__/snapshotsdialog.cpython-310.pyc /usr/share/backintime/qt/app.py /usr/share/backintime/qt/icon.py /usr/share/backintime/qt/logviewdialog.py /usr/share/backintime/qt/messagebox.py /usr/share/backintime/qt/qtsystrayicon.py /usr/share/backintime/qt/qttools.py /usr/share/backintime/qt/restoredialog.py /usr/share/backintime/qt/serviceHelper.py /usr/share/backintime/qt/settingsdialog.py /usr/share/backintime/qt/snapshotsdialog.py /usr/share/bash-completion/completions/backintime-qt /usr/share/dbus-1/system-services/net.launchpad.backintime.serviceHelper.service /usr/share/doc/backintime-qt /usr/share/doc/backintime-qt/AUTHORS /usr/share/doc/backintime-qt/CHANGES /usr/share/doc/backintime-qt/LICENSE /usr/share/doc/backintime-qt/README.md /usr/share/doc/backintime-qt/TRANSLATIONS /usr/share/doc/backintime-qt/VERSION /usr/share/doc/backintime-qt/copyright /usr/share/doc/qt/HTML/en/backintime/index.docbook /usr/share/icons/hicolor/16x16/actions/show-hidden.svg /usr/share/icons/hicolor/22x22/actions/show-hidden.svg /usr/share/icons/hicolor/24x24/actions/show-hidden.svg /usr/share/icons/hicolor/32x32/actions/show-hidden.svg /usr/share/icons/hicolor/48x48/actions/show-hidden.svg /usr/share/icons/hicolor/scalable/actions/show-hidden.svg /usr/share/man/man1/backintime-qt.1.xz /usr/share/polkit-1/actions/net.launchpad.backintime.policy THANKS. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Please provide the terminal output from starting the application (prepend the terminal output with LC_ALL=C to have the output in english!). Works just fine here. If you have never used it before it asks to create a profile at first start...
Source RPM: /usr/bin/backintime-qt_polkit => backintime-1.3.3-1.mga9.src.rpmComponent: New RPM package request => RPM Packages
Just installed to try backintime-qt, fired it up, here is terminal output: $ backintime-qt Back In Time Version: 1.3.3 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. and it pops a dialogue Question "Back in time is not configured. Would you like to restore a previous configuration?". No|Yes I did not go further. Your first example 'backintime-common' does not exist as a command (as a package, yes): $ urpmf backintime | grep /bin/ backintime-qt:/usr/bin/backintime-qt backintime-qt:/usr/bin/backintime-qt-root backintime-qt:/usr/bin/backintime-qt_polkit backintime-common:/usr/bin/backintime backintime-common:/usr/bin/backintime-askpass Trying this: $ backintime Back In Time Version: 1.3.3 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. $ showed no GUI, did nothing.
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0CC: (none) => lewyssmith
Another user reported that python3-packaging is lacking. Does its installation solve the problem? https://www.mageialinux-online.org/forum/topic-30887.php#m315589
CC: (none) => yvesbrungard
One of my friends from MLO (papoteur) asked me to install the python3-packaging module, which I did. It appears that the problem is resolved but, before reporting it as resolved, I am waiting for the current backup to complete. Sincerely, Yves
CC: (none) => lsdm
Done for cauldron, adding the requires on python3-packaging Submitting: backintime-qt-1.3.3-1.1.mga9.noarch.rpm backintime-common-1.3.3-1.1.mga9.noarch.rpm Source: backintime-1.3.3-1.1.mga9
Ever confirmed: 0 => 1Status: UNCONFIRMED => NEWAssignee: bugsquad => qa-bugs
Thanks for this work, papoteur. Is it in Mageia 9 Updates_Testing?
In testing, in drakrpm I selected backintime-qt-1.3.3-1.1 and got with deps: - appres-1.0.6-1.mga9.x86_64 - backintime-common-1.3.3-1.1.mga9.noarch - backintime-qt-1.3.3-1.1.mga9.noarch - editres-1.0.8-1.mga9.x86_64 - encfs-1.9.5-7.mga9.x86_64 - lib64encfs1.9-1.9.5-7.mga9.x86_64 - lib64fs6-1.0.9-1.mga9.x86_64 - lib64tinyxml2_9-9.0.0-2.mga9.x86_64 - listres-1.0.5-1.mga9.x86_64 - luit-2.0.20230201-3.mga9.x86_64 - makedepend-1.0.8-1.mga9.x86_64 - python3-jaraco-8.2.1-4.mga9.noarch - python3-jaraco-classes-3.2.3-1.mga9.noarch - python3-jeepney-0.8.0-1.mga9.noarch - python3-keyring-23.9.3-1.mga9.noarch - python3-more-itertools-8.12.0-3.mga9.noarch - python3-secretstorage-3.3.3-1.mga9.noarch - rstart-1.0.6-1.mga9.x86_64 - smproxy-1.0.7-1.mga9.x86_64 - viewres-1.0.7-1.mga9.x86_64 - x11-scripts-1.0.1-19.mga9.noarch - x11-tools-1.0.0-21.mga9.noarch - x11perf-1.6.2-1.mga9.x86_64 - xcmsdb-1.0.6-1.mga9.x86_64 - xconsole-1.0.8-1.mga9.x86_64 - xcursorgen-1.0.8-1.mga9.x86_64 - xev-1.2.5-1.mga9.x86_64 - xfsinfo-1.0.7-1.mga9.x86_64 - xgamma-1.0.7-1.mga9.x86_64 - xkbevd-1.1.5-1.mga9.x86_64 - xkbprint-1.0.6-1.mga9.x86_64 - xkbutils-1.0.5-1.mga9.x86_64 - xkill-1.0.6-1.mga9.x86_64 - xlsatoms-1.1.4-1.mga9.x86_64 - xlsclients-1.1.5-1.mga9.x86_64 - xrefresh-1.0.7-1.mga9.x86_64 - xstdcmap-1.0.5-1.mga9.x86_64 - xvidtune-1.0.4-1.mga9.x86_64 - xvinfo-1.1.5-1.mga9.x86_64 - xwininfo-1.1.5-3.mga9.x86_64 $ backintime-qt brought up the dialogue about restoring configuration, I answered no, and got the configuration GUI. I will try to use it another week.
CC: (none) => fri
I see from https://github.com/bit-team/backintime/releases That 1.40 was released two days ago with many bugfixes. And bugfixing is what upstream itself say they are focusing on, not new features. So I suggest we update to this 1.40 current release now while we are at it.
URL: (none) => https://github.com/bit-team/backintime
Done for this new release: Packages in 9/Core/Updates_testing: ====================== backintime-qt-1.4.0-1.mga9.noarch.rpm backintime-common-1.4.0-1.mga9.noarch.rpm From SRPMS: backintime-1.4.0-1.mga9.src.rpm
CC: (none) => geiger.david68210
Many thanks :) Cant test myself now, away for a couple days.
CC: lewyssmith => (none)
Advisory based on comment 9 and other comments added to SVN. Please remove the "advisory" keyword if it needs to be changed. It also helps when obsolete advisories are tagged as "obsolete" Uploaded advisory: type: bugfix subject: Updated backintime packages fix many bugs src: 9: core: - backintime-1.4.0-1.mga9 description: | Back in Time 1.4.0 is a bugfix release with many bugfixes. This update also fixes a missing require. references: - https://bugs.mageia.org/show_bug.cgi?id=32222 - https://github.com/bit-team/backintime/releases Yves and Morgan, do you get a chance to test the update? @ Yves please don't test it on a production system, but on a seperate installation. Please read https://wiki.mageia.org/en/QA_process_for_validating_updates French: https://wiki.mageia.org/en/Processus_QA_pour_valider_les_mises_a_jour-fr
Keywords: (none) => advisoryCC: (none) => marja11
Created attachment 14052 [details] Backintime (Mageia 9) Yesterday I received the following message: Yves and Morgan, are you able to test the update? @Yves, please don't test it on a production system, but on a separate installation. Please read https://wiki.mageia.org/en/QA_process_for_validating_updates French: https://wiki.mageia.org/en/Processus_QA_pour_valider_les_mises_a_jour-fr For the moment, I do not have the opportunity to test your solution but, during the weekend, I can, if it makes sense, try with the "live" version of Mageia 9. Should it be done? Good day. Yves
(In reply to Yves Specht from comment #12) > > For the moment, I do not have the opportunity to test your solution but, > during the weekend, I can, if it makes sense, try with the "live" version of > Mageia 9. > Should it be done? > The live version doesn't have all the updates that have already been pushed for Mageia 9, so it can't count as a test made by our QA team. But please do it, anyway, your information will certainly be useful. Or, if you know how to do that, install the live ISO on a large enough USB-key and make sure to put the bootloader on that USB-key (I once killed a laptop by putting it in the EFI partition of the laptop the USB-device was attached to... that worked well, until the USB-device was unavailable at start-up). If you choose to do that, you can fetch the updates as you normally would and, after reboot, do the test.
(In reply to Marja Van Waes from comment #13) > The live version doesn't have all the updates It can if you use persistence https://wiki.mageia.org/en/Persistent_live_systems
mga9-64 quick test OK... Launced it from terminal so i can see what it do, some info lines every snapshot run. I let it back up a new folder on my main disk, to a new folder on another disk. Set it to execute every 5 minutes. Put some files in it....Edited file. Watched backups being taken by time, and also when I tell it to. ...but note: * Major bug, fixed in new release * https://github.com/bit-team/backintime/releases So I suggest to package 1.4.1 now in this bug
Assignee: qa-bugs => geiger.david68210Source RPM: backintime-1.3.3-1.mga9.src.rpm => backintime-1.4.0-1.mga9.src.rpmKeywords: advisory => (none)
1.4.1 is now in cauldron. Submitted in Mageia 9: backintime-qt-1.4.1-1.mga9.noarch.rpm backintime-common-1.4.1-1.mga9.noarch.rpm
Assignee: geiger.david68210 => qa-bugs
Summary: Backintime (user or root) d'nt lauch. => Backintime (user or root) does not launch.
Good morning, I just installed Mageia 9 (kde) on a very old PC. As it is very slow, the upgrade of official packages is not yet complete. Can you tell me the procedure to test Backintime in the test version? (rpm location etc.) Freely and friendly, Yves
(In reply to Yves Specht from comment #17) > Can you tell me the procedure to test Backintime in the test version? (rpm > location etc.) Hi, urpmi.update Testing for updating metadata urpmq -y backintime -f --media Testing to check that you get 1.4.1 version. If yes (thus not 1.4.0), then urpmi backintime-qt backintime-common --media Testing
Seem OK here in quick test: Continuing from Comment 5 where I hit the major bug which made it never launch again: after updating to 1.4.1, it launch with kept configuration and continues operation. --- @ Yves: if that computer is really slow you may like to switch from KDE Plasma to a lighter desktop such as xfce, lxqt, ... (Not Plasma or Gnome)
( I meant to write continuing from comment *15* (not 5))
Updating backintime-qt backintime-common to 1.4.1. launching backintime-qt as user Asking for a snapshot of already configured backup. The run is OK, no error reported. This is valid for me. ========== Source: backintime-1.4.1-1.mga9.src.rpm
Updated advisory in SVN to: type: bugfix subject: Updated backintime packages fix many bugs src: 9: core: - backintime-1.4.1-1.mga9 description: | Back in Time 1.4.1 is a bugfix release with many bugfixes. This update also fixes a missing require. references: - https://bugs.mageia.org/show_bug.cgi?id=32222 - https://github.com/bit-team/backintime/releases
Keywords: (none) => advisory
Hello, I have just very briefly tested your solution for switching to backintime on my snail PC. It's just installed and doesn't yet have everything I'm going to put in it. It's a real desert. Here is what I did (as root) - urpmi.update Testing - urpmq -y -f --media Testing After a long time, I requested the installation of backintime and version 1.4.1 was indeed "clickable" in the list of available packages. Installation, click click, a few parameters and voila!, what I asked was saved with backintime. I hope this little message will be useful to you. Freely and friendly, Yves
Good morning, Today, On my very old computer, I temporarily finished installing Mageia 9. I have just configured Backintime 1.4.4 for a complete backup of folders and files (except for a few insipid folders and files (/tmp, .cache, /proc, ...). Backing up (as root)to an external SSD worked perfectly. For me, the correction is perfect. Your turn now. Freely and friendly, Yves
Oups ! read 1.4.1
Good. Could you test if it can also restore some folder from backup?
OK, I'm taking a moment to eat and, this afternoon, I'm going to delete a folder (eg /home) and try to restore it. @+
I have not learned how this works yet, but i assume configuration is stored somewhere under home of you run it as user on that system. So try someting less like the documents folder - first make sure there was/is something there backed up.
And yes dont forget to eat, i have heard it is important ;)
Here is the content of the desktop folder (before the test): - backintime-qt-root.desktop - mail.wav - gimp.desktop - hydrogen.desktop (gray, not installed) - google-chrome.desktop (gray, not installed) - isodumper-gtk.desktop (gray, not installed) - libreoffice-writer.desktop - MuseScore 3.5.desktop (gray, not installed) - org.bleachbit.BleachBit.desktop - org.kde.okular.desktop - org.kde.skanlite.deskto (gray, not installed) - org.kde.spectacle.desktop - org.kde.trash.desktop - org.musecore.MuseScore.desktop - pavucontrol-qt.desktop - register.desktop - simplescreenrecorder.desktop (gray, not installed) - stellarium.desktop - teamviewer_15.39.3.x86_64.rpm - thunderbird.desktop - vlc.desktop I now do a full backup with backintime. Zzzz..., Zzzz..., Zzzz (about 12837 times), ... (I sleep). A few hours later .... Yes!, I have a backup of the snail! On the desktop, I delete all the grayed icons (uninstalled packages). I make a backup again (keeping the same settings). It only lasts a few seconds. Last step, I take the full backup to see if the gray icons return to the desktop. Very good, the gray icons are back. @+
Many thanks I would say it is enough testing for this app Especially as it have been broken all time in mga9
Keywords: (none) => validated_updateWhiteboard: (none) => MGA9-64-OKCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2023-0097.html
Status: NEW => RESOLVEDResolution: (none) => FIXED
Hello Mageia Developers and other staff members. I am not a kernel specialist, nor a good developer, nor a great specialist in Linux architecture, but I like Mageia (I have been using it for a very long time) I started with the Mandrake magician and then continued with all his descendants. Being now retired, I have a lot more time and, if you have tests on packages that are not too difficult to install and use (especially for everyday management), do not hesitate to ask me. I will do it with pleasure. I know this is not the place to make these remarks but I don't know where in the Mageia bubble to write it. Long live Mageia, Yves
Thanks Yves for for your offer. Thus, you are candidate for QA team. I think that the starting point is to subscribe to QA mailing list and to introduce yourself. Hopefully, you will be guided after that.
Yves, you are much welcome :) In addition to the reply of Papoteur, see "Contributors Corner" at https://wiki.mageia.org/en/Main_Page Basically we need much tests of updates that everybody use like kernel and other system parts, browser and office things... Drivers for hardware you have (i.e graphics, wifi, printers...), and of course if you find personal interest in some packages.