Lost Dolphin “Comment” in Properties>Details

I did something that changed Dolphin’s [Alt-Return or right click on a file to get to] “Properties>Details.” There used to be a place there that I could click on and enter information. It was called “Remark” or “Comment” – I can’t remember which (but NOT “Comment” in the menu bar}. It is no longer there and I have been unable to figure out how to get it back. I have searched through “Settings>Configure Dolphin,” tried enabling “Comment” in “View>View Display Style—Dolphin,” tried “View>Show Additional Information,” and other things, including restoring defaults and re-installing Dolphin. Can anyone tell me how to get this back?

System:
  Kernel: 6.6.41-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=837c4445-d72c-4f7d-85c9-da3a06e79088 rw quiet splash
    resume=UUID=28e59c87-02a4-44b7-bba3-d5bcc321aa68 udev.log_priority=3
  Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.4.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME Z690-A v: Rev 1.xx serial: <superuser required>
    part-nu: SKU uuid: <superuser required> UEFI: American Megatrends v: 2403
    date: 05/11/2023
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: 12th Gen Intel Core i7-12700 bits: 64 type: MST AMCP
    arch: Alder Lake gen: core 12 level: v3 note: check built: 2021+
    process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151) stepping: 2
    microcode: 0x35
  Topology: cpus: 1x cores: 12 mt: 8 tpc: 2 st: 4 threads: 20 smt: enabled
    cache: L1: 1024 KiB desc: d-4x32 KiB, 8x48 KiB; i-8x32 KiB, 4x64 KiB
    L2: 12 MiB desc: 8x1.2 MiB, 1x2 MiB L3: 25 MiB desc: 1x25 MiB
  Speed (MHz): avg: 800 min/max: 800/4800:4900:3600 scaling:
    driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 800 4: 800
    5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800
    15: 800 16: 800 17: 800 18: 800 19: 800 20: 800 bogomips: 84500
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  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: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  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: Enhanced / Automatic IBRS; IBPB: conditional;
    RSB filling; PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
    vendor: XFX Pine driver: amdgpu v: kernel arch: GCN-4 code: Arctic Islands
    process: GF 14nm built: 2016-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 ports:
    active: DVI-D-1,HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 01:00.0
    chip-ID: 1002:67df class-ID: 0300 temp: 54.0 C
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.1
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1200 s-dpi: 96 s-size: 1016x317mm (40.00x12.48")
    s-diag: 1064mm (41.9") monitors: <missing: xrandr>
  Monitor-1: DVI-D-1 model: Samsung SyncMaster serial: <filter> built: 2007
    res: 1920x1200 dpi: 94 gamma: 1.6 size: 518x324mm (20.39x12.76")
    diag: 611mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 720x400
  Monitor-2: HDMI-A-1 model: Acer G276HL serial: <filter> built: 2016
    res: 1920x1080 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23")
    diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
    inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.3-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 580 Series (radeonsi
    polaris10 LLVM 18.1.8 DRM 3.54 6.6.41-1-MANJARO) device-ID: 1002:67df
    memory: 7.81 GiB unified: no
  API: Vulkan v: 1.3.279 layers: N/A device: 0 type: discrete-gpu name: AMD
    Radeon RX 580 Series (RADV POLARIS10) driver: mesa radv
    v: 24.1.3-manjaro1.1 device-ID: 1002:67df surfaces: xcb,xlib
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:7ad0
    class-ID: 0403
  Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
    vendor: XFX Pine driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 16 bus-ID: 01:00.1 chip-ID: 1002:aaf0 class-ID: 0403
  API: ALSA v: k6.6.41-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.2.1 status: off with: wireplumber status: active
    tools: pw-cli,wpctl
  Server-3: PulseAudio v: 17.0 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl
Network:
  Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie:
    gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 07:00.0 chip-ID: 8086:15f3
    class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager,systemd-timesyncd
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 port: N/A bus-ID: 00:0e.0 chip-ID: 8086:467f rev: class-ID: 0104
Drives:
  Local Storage: total: 5.49 TiB used: 673.68 GiB (12.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 37.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 2000GB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 04RL scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Kingston model: DataTraveler 3.0
    size: 28.87 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.2
    spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: 0000 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD20SDRW-11VUUS0 size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
    tech: HDD rpm: 5400 serial: <filter> fw-rev: 1034 scheme: GPT
Partition:
  ID-1: / raw-size: 1.81 TiB size: 1.78 TiB (98.37%) used: 111.03 GiB (6.1%)
    fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 288 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 25.0 C mobo: N/A gpu: amdgpu temp: 54.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 784
Info:
  Memory: total: 64 GiB available: 62.54 GiB used: 3.02 GiB (4.8%)
  Processes: 384 Power: uptime: 22m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 25 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Packages: 1554 pm: pacman pkgs: 1549 libs: 431 tools: pamac,yay pm: flatpak
    pkgs: 5 Compilers: clang: 18.1.8 gcc: 14.1.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.2.26 running-in: konsole inxi: 3.3.35

```

That doesn’t have any effect. GNU/Linux is a multi-user operating system, and user-specific settings are never overwritten by reinstalling the software.

Either way, is this what you are talking about? :point_down:

Right-click the file, select the highlighted tab, and there it is. :stuck_out_tongue:

Yes, as I indicated in the first line of my message I know how to get there, but the Comment: and Tags: options are not present. There must be a place where these options are selected or de-selected. That’s what I need to find.

I’ve gone through all of my dolphin settings, and I can find no option to configure this. There is the option to display comments via the “View → Show additional information” menu, but that’s not even enabled on my system.

I suspect that your dolphin user configuration has become corrupted. So the first thing I would recommend is to close dolphin, rename ~/.local/share/dolphin to ~/.local/share/dolphin.bak, and to then restart dolphin and see whether the option has returned.

Nope. Didn’t work.

Just a wild guess… What filesystem are the files on where you wish to enter a comment for them?

If it’s vfat, exfat or ntfs, then the option is probably not available simply because those filesystems do not support POSIX-style metadata.

On my system here, it’s not even available for files on ext4, but then again, that could be because those are root-owned files, which means that I don’t have write permission on them — my /boot is ext4, and the rest of my system is on btrfs.

Edit: Yes, I’ve just checked, and it’s a permissions issue. If the file is not owned by you, then the Comment entry is not available.

Good guess! Media with fstype ext4 work, whereas the problem files are on a flash drive with fstype vfat. However, I was leaving comments on the vfat flash drive yesterday – it just went kaflewie today. The option is present on all my ext4 directories. I have no idea what to do about this or what could have happened between yesterday and today. Can a file system change on its own? I don’t think so. If you have further suggestions I welcome them. Otherwise thank you very much for your time today.

Not the filesystem itself, but considering that vfat is not a POSIX filesystem, its usability when mounted into the directory hierarchy of a POSIX operating system depends on the mount options, and if the filesystem is auto-mounted, then those auto-mount options may have changed since yesterday’s update. It is therefore possible that the filesystem is now root-owned, or read-only-mounted.

The command… :point_down:

mount | grep fat

… should provide you with the information regarding that. However, in the same vein, I would recommend that you read the following one of my — ahemexcellently written tutorials. :stuck_out_tongue: :point_down:

Well, Aragorn, when you’re right, you’re right. It is an excellently written tutorial. It is a rare pleasure to read a bit of technical, non-fiction screed that has obviously been proof-read, is grammatically correct, comprehensive with lots of meat, and well organized. Kudos to you. The information is relevant and useful to me, and I now have some work to do. And will probably have even more after I head down the rabbit hole of the additional links to further information attached to the tail of your tutorial I just read. Thanks again.

If you are reading this and you are not Aragorn, you might find it worthwhile to click over and take a look at the above tutorial, “Working with additional ‘drives’.”

1 Like

Ah, but the rules are simple. There are only three of them. :point_down:

  1. @Aragorn is right.
  2. @Aragorn is always right.
  3. If @Aragorn is wrong, see rule #2.

:rofl: :face_with_hand_over_mouth:

1 Like

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