Timeshift doesn’t work with Antix ?

[Member Wallon]

Dear All,

I have installed Timeshift to do a backup but it doesn’t work.
Is it possible to use Timeshift ?
I don’t like to use an snapshot (iso) because the file fstab is modified and some times, I can’t reinstall the iso (Bios or Legacy or EFI not compatible)

———————————————————–
Here it is my installation (apparently all was good);

$ sudo apt install timeshift
Lecture des listes de paquets… Fait
Construction de l’arbre des dépendances
Lecture des informations d’état… Fait
Les paquets supplémentaires suivants seront installés :
libgee-0.8-2
Les NOUVEAUX paquets suivants seront installés :
libgee-0.8-2 timeshift
0 mis à jour, 2 nouvellement installés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 874 ko dans les archives.
Après cette opération, 4.053 ko d’espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] O
Réception de :1 http://ftp.be.debian.org/debian buster/main amd64 libgee-0.8-2 amd64 0.20.1-2 [230 kB]
Réception de :2 http://ftp.be.debian.org/debian buster/main amd64 timeshift amd64 19.01+ds-2+deb10u1 [643 kB]
874 ko réceptionnés en 0s (2.187 ko/s)
Sélection du paquet libgee-0.8-2:amd64 précédemment désélectionné.
(Lecture de la base de données… 184316 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de …/libgee-0.8-2_0.20.1-2_amd64.deb …
Dépaquetage de libgee-0.8-2:amd64 (0.20.1-2) …
Sélection du paquet timeshift précédemment désélectionné.
Préparation du dépaquetage de …/timeshift_19.01+ds-2+deb10u1_amd64.deb …
Dépaquetage de timeshift (19.01+ds-2+deb10u1) …
Paramétrage de libgee-0.8-2:amd64 (0.20.1-2) …
Paramétrage de timeshift (19.01+ds-2+deb10u1) …
Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-4) …
Traitement des actions différées (« triggers ») pour mime-support (3.62) …
Traitement des actions différées (« triggers ») pour hicolor-icon-theme (0.17-2) …
Traitement des actions différées (« triggers ») pour libc-bin (2.28-10) …
Writing Menu: fluxbox
Writing Menu: icewm
Writing Menu: jwm

—————————————————————————————-
Please find the laptop info;

System: Host: ASUS Kernel: 4.9.240-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.9.240-antix.1-amd64-smp
root=UUID=3cafe92e-aadc-43da-b08c-f785f80ec609 ro gfxsave quiet
Desktop: IceWM 2.0.1 dm: SLiM 1.3.6
Distro: antiX-19.3_x64-full Manolis Glezos 15 October 2020
base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: ASUSTeK product: F3U v: 1.0 serial: <filter> Chassis: type: 10
serial: <filter>
Mobo: ASUSTeK model: F3U v: 1.0 serial: <filter> BIOS: American Megatrends v: 208
date: 07/18/2007
Battery: ID-1: BAT0 charge: 7.5 Wh condition: 7.5/51.3 Wh (15%) volts: 12.5/11.1
model: ASUSTEK F3—24 type: Li-ion serial: <filter> status: Full
Memory: RAM: total: 1.71 GiB used: 586.9 MiB (33.5%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
PCI Slots: Permissions: Unable to run dmidecode. Root privileges required.
CPU: Topology: Dual Core model: AMD Athlon 64 X2 TK-55 bits: 64 type: MCP arch: K8 rev.F+
family: F (15) model-id: 68 (104) stepping: 1 microcode: N/A L2 cache: 512 KiB
bogomips: 6383
Speed: 1600 MHz min/max: 800/1800 MHz Core speeds (MHz): 1: 1600 2: 1600
Flags: 3dnow 3dnowext 3dnowprefetch apic clflush cmov cmp_legacy cr8_legacy cx16 cx8 de
extapic extd_apicid fpu fxsr fxsr_opt ht lahf_lm lbrv lm mca mce mmx mmxext msr mtrr
nopl nx pae pat pge pni pse pse36 rdtscp rep_good sep sse sse2 svm syscall tsc vme
vmmcall
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass status: Not affected
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: AMD RS690M [Radeon Xpress 1200/1250/1270] vendor: ASUSTeK driver: radeon
v: kernel bus ID: 01:05.0 chip ID: 1002:791f
Display: x11 server: X.Org 1.20.4 driver: radeon resolution: 1280×800~60Hz
OpenGL: renderer: ATI RS690 v: 2.1 Mesa 18.3.6 direct render: Yes
Audio: Device-1: AMD SBx00 Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1002:4383
Sound Server: ALSA v: k4.9.240-antix.1-amd64-smp
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK
driver: r8169 v: 2.3LK-NAPI port: b800 bus ID: 05:00.0 chip ID: 10ec:8168
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IP v6: <filter> type: dynamic mngtmpaddr scope: global
IP v6: <filter> scope: link
Device-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter driver: ath5k
v: kernel port: b800 bus ID: 06:00.0 chip ID: 168c:001c
IF: wlan0 state: down mac: <filter>
WAN IP: <filter>
Drives: Local Storage: total: 140.44 GiB used: 5.95 GiB (4.2%)
ID-1: /dev/sda vendor: Seagate model: ST9120822AS size: 111.79 GiB block size:
physical: 512 B logical: 512 B speed: 1.5 Gb/s serial: <filter> rev: C scheme: MBR
ID-2: /dev/sdb type: USB vendor: SanDisk model: USB 3.2Gen1 size: 28.65 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR
Optical-1: /dev/sr0 vendor: MATSHITA model: DVD-RAM UJ-850S rev: 1.22
dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
state: running
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: 24.41 GiB size: 24.03 GiB (98.43%) used: 5.94 GiB (24.7%) fs: ext2
dev: /dev/sdb2 label: rootantiX uuid: 3cafe92e-aadc-43da-b08c-f785f80ec609
ID-2: /media/an/DATAWIN raw size: 2.24 GiB size: 2.23 GiB (99.80%) used: 1.3 MiB (0.1%)
fs: vfat dev: /dev/sdb3 label: DATAWIN uuid: 0AE6-1BAB
ID-3: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60)
cache pressure: 50 (default 100) dev: /dev/sdb1 label: SWAP
uuid: 8e0bee22-319d-44fd-95ed-db7522af6734
Unmounted: ID-1: /dev/sda1 size: 6.84 GiB fs: vfat label: RECOVERY uuid: 1489-5F00
ID-2: /dev/sda2 size: 67.07 GiB fs: ntfs label: VistaOS uuid: A4448C70448C46D0
ID-3: /dev/sda3 size: 1 KiB fs: <root required> label: N/A uuid: N/A
ID-4: /dev/sda5 size: 37.88 GiB fs: ntfs label: DATA uuid: 7458901B588FDA6E
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 10 rev: 2.0 speed: 480 Mb/s
chip ID: 1d6b:0002
Device-1: 1-1:2 info: SanDisk Ultra Flair type: Mass Storage driver: usb-storage
interfaces: 1 rev: 2.1 speed: 480 Mb/s chip ID: 0781:5591 serial: <filter>
Device-2: 1-7:4 info: Microdia PC Camera (SN9C201 + OV9650) type: <vendor specific>
driver: gspca_sn9c20x interfaces: 1 rev: 2.0 speed: 480 Mb/s chip ID: 0c45:624f
Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 2-2:2 info: Ortek Targus Number Keypad ports: 3 rev: 1.1 speed: 12 Mb/s
chip ID: 05a4:9837
Device-3: 2-2.2:3 info: Logitech Optical Tilt Wheel Mouse type: Mouse
driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s chip ID: 046d:c019
Device-4: 2-2.3:4 info: Ortek Targus Number Keypad (Composite Device)
type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 05a4:9862
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Sensors: System Temperatures: cpu: 57.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http: //it.mxrepo.com/antix/buster/ buster main nonfree nosystemd
No active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
Active apt repos in: /etc/apt/sources.list.d/buster-backports.list
1: deb http: //deb.debian.org/debian/ buster-backports main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http: //ftp.be.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http: //ftp.be.debian.org/debian/ buster main contrib non-free
2: deb http: //security.debian.org/ buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/eid.list
1: deb http: //files.eid.belgium.be/debian/ buster main
2: deb http: //files2.eid.belgium.be/debian/ buster main
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main
No active apt repos in: /etc/apt/sources.list.d/onion.list
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes: CPU top: 5
1: cpu: 71.0% command: chromium pid: 4821 mem: 174.0 MiB (9.9%)
2: cpu: 32.0% command: yad pid: 6906 mem: 28.4 MiB (1.6%)
3: cpu: 6.6% command: chromium pid: 4537 mem: 295.1 MiB (16.8%)
4: cpu: 6.2% command: chromium pid: 4586 mem: 61.8 MiB (3.5%)
5: cpu: 5.0% command: xorg pid: 2584 mem: 72.6 MiB (4.1%)
Memory top: 5
1: mem: 295.1 MiB (16.8%) command: chromium pid: 4537 cpu: 6.6%
2: mem: 180.3 MiB (10.2%) command: chromium pid: 4589 cpu: 0.6%
3: mem: 174.0 MiB (9.9%) command: chromium pid: 4821 cpu: 71.0%
4: mem: 141.7 MiB (8.0%) command: chromium pid: 4631 cpu: 2.6%
5: mem: 104.1 MiB (5.9%) command: chromium pid: 4560 cpu: 0.0%
Info: Processes: 174 Uptime: 20m Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers:
gcc: 8.3.0 alt: 8 Client: shell wrapper v: 5.0.3-release inxi: 3.0.36

Thank you for your support.
Best regards,
Wallon.

[Member Xecure]

Helpful

Up

0

::

For some reason, timeshift wants to use policykit.exec or some other strange thing.

Try launching it from terminal with:
gksudo timeshift

Also, in the future, try wrapping your terminal output in code tags. Select the text you want inside code tags and click the CODE word above the text editor box in the forum or use
<code> code goes inside </code>

• This reply was modified 2 years, 3 months ago by Xecure.
• This reply was modified 2 years, 3 months ago by Xecure. Reason: fix code tags
• This reply was modified 2 years, 3 months ago by Xecure.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Wallon]

Helpful

Up

0

::

Dear Xecure,

Thank you for your prompt reply.
Following this link, https://www.lifewire.com/what-is-gksu-2189402, it’s also dangerous to use gksudo (unmaintained since 2014, PoliciKit….) and we have to use command lines. Not very practical.
Regarding my terminal output, I will try to use the code tags.

Best regards,
Wallon

[Member Xecure]

Helpful

Up

0

::

Wallon wrote:

Following this link, https://www.lifewire.com/what-is-gksu-2189402, it’s also dangerous to use gksudo (unmaintained since 2014, PoliciKit….) and we have to use command lines. Not very practical.

This is false. They removed gksu because they don’t want “dumb” users to have root privileges, because “they don’t know what they are doing”. Instead, pkexec (policy kit execute) was introduced, as you can “better manage” the privileges with it (gksu gives you complete privileges to everything, as if you were root, while pkexec limits your privilege to only the app it launches, or maybe to other things managed by its configuration).
And it is also false it is “unmaintained”, as skidoo and the antiX team have been maintaining and patching it (that is why it is included in antiX).

In MXLinux, gksu is there but doesn’t run as normal gksu, but instead it links to pkexec (which they could have set up in all major linux distros instead of removing gkus entirely, but “they probably know better”).

People who don’t know just say “security risk” but don’t explain to you what is the “security issue”. A knife is a security risk, as it can harm you (or someone else) if not handled properly. Are we also going to ban them? Are we replacing it with a butter knife instead? Maybe soon there will also be a campaign against kitchen knifes, because they are a security risk, who knows.

The reason why many File Managers can no longer be launched with sudo or root privileges follows the same reasoning. “People are stupid, so if we give them access as root to all files, they will probably do something that will break their system and then blame it on us, the devs, on Linux or say that windows is better”. “Great power means great responsibility, so better take away the people’s power as they are too dumb to use it”.

Sorry for the off-topic.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Moderator caprea]

Helpful

Up

0

::

The command for the GUI is might
timeshift-gtk

[Member Xecure]

Helpful

Up

0

::

I looked at timeshift-gtk.desktop in /usr/share/applications
Exec=timeshift-launcher
It runs timeshift-launcher instead of timeshift-gtk
I suppose it should instead say:
Exec=timeshift-gtk
But when I launch the .desktop, it tells me I need root privileges.

Would replacing this with:
Exec=gksudo timeshift-gtk
be the correct path, caprea? I am no expert with timeshift, so I don’t know.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Moderator caprea]

Helpful

Up

0

::

Never used timeshift either but
Exec=gksudo timeshift-gtk
should work.

[Member oops]

Helpful

Up

0

::

FI: timeshift or timeshift-gtk need to be used and launched into the user account (not into root or with sudo or gksudo)

[Member Wallon]

Helpful

Up

0

::

I have tested the command Exec=gksudo timeshift-gtk and root access is required. It doesn’t work.


$ Exec=gksudo timeshift-gtk
E: Admin access is required to backup and restore system files.
Please re-run the application as admin (using 'sudo' or 'su')

(timeshift-gtk:5342): Gtk-CRITICAL **: 14:11:42.606: gtk_icon_theme_load_icon_for_scale: assertion 'GTK_IS_ICON_THEME (icon_theme)' failed

** (timeshift-gtk:5342): CRITICAL **: 14:11:42.607: gee_abstract_collection_get_size: assertion 'self != NULL' failed


[Member oops]

Helpful

Up

0

::

I have into Icewm and into my statup file: /home/user1/.icewm/startup
(maybe needs to be adapted for you)

...
# redshift ecran
redshift-gtk &
...

Owner user1 not root

And redshift-gtk works great (with the user1 custom config into: /home/user1/.config/redshift.conf)

• This reply was modified 2 years, 3 months ago by oops.
• This reply was modified 2 years, 3 months ago by oops.

[Member Xecure]

Helpful

Up

0

::

oops wrote:

I have into Icewm and into my statup file: /home/user1/.icewm/startup
(maybe needs to be adapted for you)

...
# redshift ecran
redshift-gtk &
...

Owner user1 not root

And redshift-gtk works great (with the user1 custom config into: /home/user1/.config/redshift.conf)

redshift is not timeshift

Wallon wrote:

have tested the command Exec=gksudo timeshift-gtk

As I explained above, this is what needs to be replaced inside /usr/share/applications/timeshift-gtk.desktop, and not something you run in terminal.
This replaces the need to launching from terminal, as it will change the launcher in App select. To change the launcher in the icewm menu, you need to click the “Refresh menu” option in the menu (hopefully this works, as there was a permission issue with this option before).

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Forum Admin anticapitalista]

Helpful

Up

0

::

I installed it and it showed up in the IceWM menu under Applications > System > Timeshift.
I clicked on it and it opened roxterm and prompted a sudo (username) password.

Also try timeshift-launcher in a terminal.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member Xecure]

Helpful

Up

0

::

anticapitalista wrote:

I installed it and it showed up in the IceWM menu under Applications > System > Timeshift.
I clicked on it and it opened roxterm and prompted a sudo (username) password.

It didn’t launch for me on App Select.
It didn’t launch for me from the fluxbox menu.
So my conclusion (as Wallon’s conclusion): it didn’t work.
Tried launching from terminal:

$ timeshift-launcher 
==== AUTHENTICATING FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `
/usr/bin/env' as the super user
Authenticating as: root
Password: 
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.

Running an upgraded antiX 19.2 base x64, so I assumed it would be the same for everyone. Maybe on antiX 19.3 full it is different.

• This reply was modified 2 years, 3 months ago by Xecure. Reason: fix code tags

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member olsztyn]

Helpful

Up

0

::

Xecure wrote:

The reason why many File Managers can no longer be launched with sudo or root privileges follows the same reasoning.

Thankfully SpaceFM still has root window capability… Would not be able to accomplish some important maintenance without it…
Just my two cents…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member Xecure]

Helpful

Up

0

::

olsztyn wrote:

Thankfully SpaceFM still has root window capability…

Try dolphin on KDE. It is very frustrating. Another reason for me to NOT use DEs and for me to use file managers like spacefm.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Author]

Posts