Delete action auto-selects next list item in Dolphin

Hello,

First of all I would like to appreciate and highlight positively the silent developer(s) who don’t reply to posts but just give them the :eyes: then silently head back to their workspace and grind at our challenges. I know there here because I have had some issues resolved just by merely posting them here and receive no response on them only for an update like a week ago to resolve them (seen below).

  • I had a weird issue where I would reboot my system and have two sets of bluetooth devices with one of them being a ghost (hci0 and hci1) appearing and disappearing randomly but now it’s been resolved.
  • I would intermittently have brief system freezes from time to time with no detectable reason it was happening, now it’s gone.
  • Boot times have notably significantly reduced*
  • My WiFi ftp server setup is now so fast I’ve stopped using a usb cable to copy items in GBs from my phone to & fro PC, it won’t matter the distance between them as long as they are in the same vicinity.
System:
Kernel: 6.17.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=da58b7be-731a-48ea-9895-88abd0814fb4 rw rootflags=subvol=@
quiet splash resume=UUID=da58b7be-731a-48ea-9895-88abd0814fb4
resume_offset=4485180 loglevel=3
Desktop: KDE Plasma v: 6.5.1 tk: Qt v: N/A info: frameworks v: 6.19.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: P8Z77-V v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
BIOS: American Megatrends v: 2104 date: 08/13/2013
CPU:
Info: model: Intel Core i7-3770K bits: 64 type: MT MCP arch: Ivy Bridge
gen: core 3 level: v2 built: 2012-15 process: Intel 22nm family: 6
model-id: 0x3A (58) stepping: 9 microcode: 0x21
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 4100 min/max: 1600/4100 scaling: driver: intel_cpufreq
governor: performance cores: 1: 4100 2: 4100 3: 4100 4: 4100 5: 4100 6: 4100
7: 4100 8: 4100 bogomips: 57695
Flags-basic: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: ASUSTeK P8 series
driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports:
active: HDMI-A-1 empty: DP-1, DP-2, DP-3, HDMI-A-2, HDMI-A-3, VGA-1
bus-ID: 00:02.0 chip-ID: 8086:0162 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.20 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: crocus gpu: i915 display-ID: 0
Monitor-1: HDMI-A-1 model: Samsung S24C450 serial: <filter> built: 2013
res: mode: 1920x1200 hz: 60 scale: 100% (1) dpi: 94 gamma: 1.2
size: 518x324mm (20.39x12.76") diag: 611mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus wayland:
drv: crocus x11: drv: crocus
API: OpenGL v: 4.5 compat-v: 4.2 vendor: intel mesa v: 25.2.6-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 4000 (IVB
GT2) device-ID: 8086:0162 memory: 1.46 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.4.328 layers: 14 device: 0 type: integrated-gpu
name: Intel HD Graphics 4000 (IVB GT2) driver: mesa intel v: 25.2.6-arch1.1
device-ID: 8086:0162 surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 21.1.4 256 bits) driver: mesa llvmpipe v: 25.2.6-arch1.1 (LLVM
21.1.4) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20
class-ID: 0403
Device-2: JMTek LLC. CMTECK driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3:3
chip-ID: 0c76:165f class-ID: 0300 serial: <filter>
API: ALSA v: k6.17.7-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel 82579V Gigabit Network vendor: ASUSTeK P8P67 Deluxe
driver: e1000e v: kernel port: f080 bus-ID: 00:19.0 chip-ID: 8086:1503
class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: ASUSTeK
driver: ath9k v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 06:00.0 chip-ID: 168c:0032 class-ID: 0280
IF: wlp6s0 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Realtek Bluetooth 5.1 Radio driver: btusb v: 0.8 type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 4-1.3:3
chip-ID: 0bda:a725 class-ID: e001 serial: <filter>
Report: btmgmt ID: hci1 rfk-id: 4 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 2.73 TiB used: 82.04 GiB (2.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: PNY model: CS900 1TB SSD
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 06B5 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: Backup+ Hub BK
size: 1.82 TiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.1
spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: D781 scheme: MBR
Partition:
ID-1: / raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 82.04 GiB (8.8%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-2: /home raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 82.04 GiB (8.8%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-3: /var/log raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 82.04 GiB (8.8%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-4: /var/tmp raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 82.04 GiB (8.8%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: file size: 34.37 GiB used: 0 KiB (0.0%) priority: -2
file: /swp/swapfile
ID-2: swap-2 type: zram size: 31.03 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 34.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 31.03 GiB used: 3.9 GiB (12.6%)
Processes: 284 Power: uptime: 19m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.39 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1941 libs: 524 tools: octopi,paru Compilers:
clang: 21.1.4 gcc: 15.2.1 Shell: Bash v: 5.3.3 default: fish v: 4.1.2
running-in: konsole inxi: 3.3.39
Garuda (2.11.1-1):
System install date:     2025-09-16
Garuda release:          250907
Last full system update: 2025-11-05
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut garuda-hardware-profile-standard
Windows dual boot:       <superuser required>
Failed units:
--- System Health Check Report ---
23/25 checks run in 0.88 seconds ⌛
Powered by garuda-health 🦅

So here’s my predicament, three days ago when I was doing a clean up of my folders from items I no longer need after placing them on observation for 2 weeks so these are items I would delete and never look back (haven’t had a problem ever since). There’s this function in Garuda that auto-selects next item right after you’ve deleted a selected item in current folder.

When I started using Garuda, I noticed it but didn’t think much of it and I wasn’t really bothered about it until three days ago. So what happened was I was doing my routine clean up for delete items randomly placed withing a folder. The folder had other folders and files in it with a mixed count of about 200.
Technically they would be arranged such that many are not in your immediate view, you’d have to scroll down to view them all. So I started my routine, after two weeks of observation, delete selected items.

It wasn’t until 3 hrs later when tried to revisited the folder (that had the collectors items folder) I worked on in need of some media file I had trans-coded and some edited that were collector items I had gathered for about 2 yrs (some with experiences that cannot re-live).

Well… when you are permanently deleting files from your folder, Dolphin does ask you if you are sure you want them eliminated & I’d say yes, go right ahead since I’ve considered them.

Given that I was trying to get the list done and some selected items were also out of view as I scrolled down to add more items to the main delete procedure, the collectors folder items was buried in the list of randomly selected items on Dolphin’s prompt to confirm the delete.

Since I’d delete in small batches of selected items, the folder got auto-selected in between delete actions, and also got deleted. That’s how I lost it, it was also out of view having scrolled down verifying others to be deleted. This could have been mitigated by clicking away immediately after deleting but at the time it didn’t occur to me to do so because it was scrolled out of view during selecting delete items.

So my question is this, is there any way you can stop the behavior of Dolphin auto-selecting the next item in your folder after you have just deleted a previous item in that same folder?

Given this specific Dolphin behavior, my best guess would be to check in the Preferences/Settings of Dolphin for such setting, if it exists. If not then it could be coded that way and I would then post your exact post here. KDE even says it’s the right place to ask something when unsure if it’s a bug or something else.

Last time I posted there I got a response a few mins later. But don’t assume that happens all the time. :rofl:

7 Likes

hi,

Just a Tipp. After deleting files you can press the ESC Key and the next file isnt marked anymore if i understand it right. (meanin glowing file after delete) I use others filemanager too like double-commander and Nemo from Cinnamon base.

I also would say to report it like FDG already mentioned to KDE :wink:

4 Likes

Can you move this post there or who can do it?

No one can do it, it’s a different forum and it’s not Garuda, it’s KDE specifically.
You have to create an account and post it there.

2 Likes

Ohhh I see… Understood.

1 Like

Yeah this actually works but is such a killjoy, basically that’s the only issue I have with Dolphin. It also seems like many people don’t like this function from way back. I’ve installed Nemo incase nothing is done about it since it’s not like here where :eyes: is enough from the back office team.

Personally, I would modify the method you use to delete files to reduce the chances of this happening in the future. I usually change several things to reduce the chances of deleting files by mistake.

I rarely permanently delete files directly with Dolphin. I always configure Dolphin to send files to the trash bin, (before I consider permanently deleting anything). This at least gives you a bit of a cushion to recover files you’ve mistakenly trashed before you do any permanent deletions.

Another thing that can also help, is to reduce the size of your trash bin settings considerably. That way, if a directory with large size media files is mistakenly selected to be trashed, it will automatically throw an error. That way, if the files destined for deletion are too large for the trash you will receive a notification. This change alone has saved my ass quite a few times, as it is made clear whenever a large size directory has been mistakenly selected to be trashed.

If you do end up mistakenly permanently deleting irreplaceable file(s), stop using that drive immediately. Use the program testdisk to scan your drive for deleted files, and hopefully testdisk can recover the lost files for you. You don’t want to write any data to the drive you want to recover your lost files from. The files are still on the drive as long as you don’t overwrite the sectors where the files you want to recover were originally stored. If you continue using the drive, and the the location where the lost files were originally stored are overwritten, then there is zero chance of recovering the lost files.

Test disk is pretty good at recovering lost files if you scan for recovery immediately after making a mistake. It can be a real lifesaver.

In the end as the old saying goes, “better an ounce of prevention, than a pound of cure”.

4 Likes

Thanks for this.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.