Snapshot file is "Too large to be trashed."  [Solved]

Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
Solon
Posts: 70
Joined: Thu Mar 25, 2021 3:33 pm

Snapshot file is "Too large to be trashed."

#1 Post by Solon »

Hi guys!

I was planning to migrate over to MX 23 now that it is settled and I have some time, so I made a Snapshot as suggested. Then I noticed the User Installed Programs recommendation, so I did that, and I also made a file of my Browser settings just in case.

So I thought I would make another copy of Snapshot with the new additions. Well, I read the instructions, and was surprised to see that the file was very large. I also thought it would overwrite the old file, kind of like a Back-in-Time type of program, but apparently not.

So I went in to delete it, so I would only have the new one. I accessed it under "homeMX", broke down into three parts, and two were small so I deleted them, then the big one, at 39GB, refused to delete. Now, whether I hit the Delete Key on the keyboard, or use the right click and "move to trash", I get the following message,

"The file is too large to be trashed."

I then used "Cut", and restarted my computer. No luck, it is still hanging in there somewhere on my "Devices" homeMX Directory.

I still plan to move to MX 23, but now I not only can't use the old Snapshot (I presume so, since I took out the two small enabling files), but if I make a new one, I will be consuming around 80GB total between the two, and I will have no way of removing either of them!

Final point, under the homeMX directory there are three folders. The Delete Key on my keyboard when this file is highlighted has no effect. Also, if I right click on the folder, the "move to trash" is greyed out. There does not seem to be any way to get rid of this!

I am mostly clueless when it comes to Linux, although I am not afraid to use the command lines when I have very clear instructions to follow. So if this requires using Yakuake, here is what the remaining large file in - Dolphin -, in the section labeled: "Devices" inside the Directory which is called: homeMX. The file is called:

snapshot-20250616_0846.iso

Appreciate any help on this... Here is my Quick Info:

Code: Select all

Snapshot created on: 20250616_0849
System:    Kernel: 6.1.0-2mx-amd64 [6.1.7-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-2mx-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_KDE_x64 Wildflower September 18  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Acer product: Aspire A715-42G v: V1.08 serial: <filter> 
           Mobo: LN model: Azalea_CAS v: V1.08 serial: <filter> UEFI: Insyde v: 1.08 
           date: 09/15/2021 
Battery:   ID-1: BAT1 charge: 43.3 Wh (100.0%) condition: 43.3/47.8 Wh (90.6%) volts: 12.4 
           min: 11.2 model: LGC AP18C8K type: Li-ion serial: <filter> status: Full 
CPU:       Info: 6-Core model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64 type: MT MCP 
           arch: Zen 2 family: 17 (23) model-id: 68 (104) stepping: 1 microcode: 8608108 cache: 
           L2: 3 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 50305 
           Speed: 1400 MHz min/max: 1400/2100 MHz boost: enabled Core speeds (MHz): 1: 1400 
           2: 1400 3: 1700 4: 1400 5: 1400 6: 1400 7: 1400 8: 1400 9: 4042 10: 1524 11: 1400 
           12: 1400 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: always-on, RSB 
           filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: Acer Incorporated ALI 
           driver: nvidia v: 535.216.03 bus-ID: 01:00.0 chip-ID: 10de:1f9d class-ID: 0302 
           Device-2: AMD Lucienne vendor: Acer Incorporated ALI driver: amdgpu v: kernel 
           bus-ID: 05:00.0 chip-ID: 1002:164c class-ID: 0300 
           Device-3: Chicony HD User Facing type: USB driver: uvcvideo bus-ID: 3-3:3 
           chip-ID: 04f2:b72b class-ID: fe01 serial: <filter> 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: 
           loaded: amdgpu,ati,nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
           display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: eDP res: 1920x1080 hz: 144 dpi: 142 size: 344x194mm (13.5x7.6") 
           diag: 395mm (15.5") 
           OpenGL: renderer: AMD RENOIR (LLVM 14.0.5 DRM 3.49 6.1.0-2mx-amd64) v: 4.6 Mesa 22.0.5 
           direct render: Yes 
Audio:     Device-1: AMD Renoir Radeon High Definition Audio vendor: Acer Incorporated ALI 
           driver: snd_hda_intel v: kernel bus-ID: 05:00.1 chip-ID: 1002:1637 class-ID: 0403 
           Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor 
           vendor: Acer Incorporated ALI Raven/Raven2/FireFlight/Renoir Processor driver: N/A 
           alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x 
           bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480 
           Device-3: AMD Family 17h/19h/1ah HD Audio vendor: Acer Incorporated ALI 
           driver: snd_hda_intel v: kernel bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403 
           Sound Server-1: ALSA v: k6.1.0-2mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 15.0 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet 
           vendor: Acer Incorporated ALI RTL8111/8168/8411 driver: r8169 v: kernel port: 2000 
           bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter vendor: Lite-On 
           driver: mt7921e v: kernel modules: wl port: 2000 bus-ID: 04:00.0 chip-ID: 14c3:7961 
           class-ID: 0280 
           IF: wlan0 state: down mac: <filter> 
Bluetooth: Device-1: Lite-On Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 1-4:3 
           chip-ID: 04ca:3802 class-ID: e001 serial: <filter> 
           Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2 
           sub-v: 2202 hci-v: 5.2 rev: 2220 
           Info: acl-mtu: 1021:6 sco-mtu: 240:8 link-policy: rswitch sniff link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio, telephony 
Drives:    Local Storage: total: 931.51 GiB used: 133.64 GiB (14.3%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD Blue SN570 1TB 
           size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
           type: SSD serial: <filter> rev: 234110WD temp: 38.9 C scheme: GPT 
Partition: ID-1: / raw-size: 34.18 GiB size: 33.35 GiB (97.56%) used: 22.76 GiB (68.3%) fs: ext4 
           dev: /dev/nvme0n1p5 maj-min: 259:5 
           ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%) used: 55.4 MiB (21.6%) 
           fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 
           ID-3: /home raw-size: 195.31 GiB size: 191.19 GiB (97.89%) used: 75.46 GiB (39.5%) 
           fs: ext4 dev: /dev/nvme0n1p6 maj-min: 259:6 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 9.77 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/nvme0n1p7 maj-min: 259:7 
Sensors:   Message: No sensor data found. Is lm-sensors configured? 
Repos:     Packages: 2653 note: see --pkg apt: 2643 lib: 1450 flatpak: 10 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.kku.ac.th/mx-packages/mx/repo/ bullseye main non-free
           2: deb https://mirror.kku.ac.th/mx-packages/mx/repo/ bullseye ahs
Info:      Processes: 268 Uptime: 11m wakeups: 2 Memory: 7.11 GiB used: 1.54 GiB (21.6%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

User avatar
asqwerth
Developer
Posts: 7985
Joined: Sun May 27, 2007 5:37 am

Re: Snapshot file is "Too large to be trashed."

#2 Post by asqwerth »

1. where did you save the old snapshot? Was it in the top level home menu (ie, not in your user home) which is the default location? If so, you will need root permissions (or open root thunar) to delete the same.
2. For deletion, use the option in "File" in the toolbar to delete permanently instead of moving it to the trashcan.

There should be no need to break it into pieces.

[EDIT]
OK you are using dolphin.

I'm not sure if there is still an option to open dolphin as root, but I think there are some root actions you can use in the right click options menu.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
DukeComposed
Posts: 1454
Joined: Thu Mar 16, 2023 1:57 pm

Re: Snapshot file is "Too large to be trashed."

#3 Post by DukeComposed »

Solon wrote: Mon Jun 16, 2025 11:59 pm Now, whether I hit the Delete Key on the keyboard, or use the right click and "move to trash", I get the following message,

"The file is too large to be trashed."

I then used "Cut", and restarted my computer. No luck, it is still hanging in there somewhere on my "Devices" homeMX Directory.
Selecting the file and using Shift+Delete usually works for me in Xfce. And when all else fails, "rm filename.iso" from a Terminal in that directory does the trick.

User avatar
Solon
Posts: 70
Joined: Thu Mar 25, 2021 3:33 pm

Re: Snapshot file is "Too large to be trashed."  [Solved]

#4 Post by Solon »

DukeComposed

Well done sir!

It just completely disappeared.

Thanks!

:popcorn:

User avatar
DukeComposed
Posts: 1454
Joined: Thu Mar 16, 2023 1:57 pm

Re: Snapshot file is "Too large to be trashed."

#5 Post by DukeComposed »

Solon wrote: Tue Jun 17, 2025 12:26 am Well done sir!

It just completely disappeared.
The bad news about using Shift+Delete and rm is that it's now difficult, or prohibitively expensive to the point of saying it's impossible, to recover that file. So use this tactic carefully. Windows will warn you when a file is too large to fit in the Recycle Bin and ask if you'd rather permanently delete it instead. KDE doesn't appear to offer this trade-off.

User avatar
Solon
Posts: 70
Joined: Thu Mar 25, 2021 3:33 pm

Re: Snapshot file is "Too large to be trashed."

#6 Post by Solon »

asqwerth wrote: Tue Jun 17, 2025 12:13 am 1. where did you save the old snapshot?

...

I'm not sure if there is still an option to open dolphin as root, but I think there are some root actions you can use in the right click options menu.
I am a simple user, and I just hit the normal buttons on Snapshot. Why it ended up there, I don't know.

However, I while the Shift Delete worked for the file, it would not delete the Folder. But...
I tried your suggestion, and after right clicking on the Folder, I went down to "Root Actions", and a whole other menu appears, including a Delete option. I clicked on that, it opened an Authorization window, and when I entered my PS, it worked.

All's well that ends well. Interesting that Shift Delete works on files, but only the Right click works on Folders.

Thanks!

:exclamation:

Post Reply

Return to “MX KDE Official Release”