Could not open folder tags

Hi,

For some time every opening of the File Dialog is preceded by the subject message. It’s just an annoyance, yet I’d like to get rid of it. I was not able to discover exactly this case. I can’t even guess what the tags folder is :slight_smile:

:+1: Welcome to Manjaro! :+1:

  1. Please read this:
    How to provide good information
    and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
  2. An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information… (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
    Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.

:+1:

P.S. If you enter a bit more details in your profile, we can also see which Desktop Environment you’re using, which CPU/GPU or Kernel, … you have without typing it every time

Thanks! Are you really sure you want all of this? Some uuids below cleaned up manually, if it makes any difference :slight_smile: . DE: KDE + i3-gaps.

ᐅ inxi --admin --verbosity=7 --filter --no-host --width
System:
  Kernel: 5.10.42-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 
  Desktop: KDE Plasma 5.21.5 tk: Qt 5.15.2 info: i3bar wm: i3 4.19.1 vt: 1 
  dm: SDDM Distro: Manjaro Linux base: Arch Linux 
Machine:
  Type: Desktop Mobo: MSI model: H61M-E23(B3)(MS-7680) v: 2.0 serial: <filter> 
  BIOS: American Megatrends v: 12.3 date: 01/10/2013 
Battery:
  Message: No system battery data found. Is one present? 
Memory:
  RAM: total: 11.59 GiB used: 3.98 GiB (34.3%) 
  RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
CPU:
  Info: Dual Core model: Intel Celeron G530 bits: 64 type: MCP 
  arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F 
  cache: L2: 2 MiB bogomips: 9581 
  Speed: 1885 MHz min/max: 1600/2400 MHz Core speeds (MHz): 1: 1885 2: 1730 
  Flags: acpi aperfmperf apic arat arch_perfmon bts clflush cmov constant_tsc 
  cpuid cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept est flexpriority 
  flush_l1d fpu fxsr ht ibpb ibrs lahf_lm lm mca mce md_clear mmx monitor msr 
  mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pebs pge pln pni 
  popcnt pse pse36 pti pts rdtscp rep_good sep ssbd sse sse2 sse4_1 sse4_2 
  ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_deadline_timer vme vmx vnmi 
  vpid xsave xsaveopt xtopology xtpr 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
  Type: mds mitigation: Clear CPU buffers; SMT disabled 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
  vendor: Micro-Star MSI driver: i915 v: kernel bus-ID: 00:02.0 
  chip-ID: 8086:0102 class-ID: 0300 
  Display: x11 server: X.Org 1.20.11 driver: loaded: intel 
  unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1 
  Screen-1: 0 s-res: 1280x1024 s-dpi: 96 s-size: 338x270mm (13.3x10.6") 
  s-diag: 433mm (17") 
  Monitor-1: VGA1 res: 1280x1024 hz: 60 dpi: 96 size: 340x270mm (13.4x10.6") 
  diag: 434mm (17.1") 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1) 
  v: 3.3 Mesa 21.1.2 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
  vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 
  chip-ID: 8086:1c20 class-ID: 0403 
  Sound Server-1: ALSA v: k5.10.42-1-MANJARO running: yes 
  Sound Server-2: JACK v: 0.125.0 running: no 
  Sound Server-3: PulseAudio v: 14.2 running: yes 
  Sound Server-4: PipeWire v: 0.3.30 running: yes 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Micro-Star MSI driver: r8168 v: 8.048.03-NAPI modules: r8169 
  port: e000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200 
  IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
  IP v4: <filter> type: dynamic noprefixroute scope: global 
  broadcast: <filter> 
  IP v6: <filter> type: noprefixroute scope: link 
  IF-ID-1: br-5fae108757f3 state: down mac: <filter> 
  IP v4: <filter> scope: global broadcast: <filter> 
  IF-ID-2: docker0 state: down mac: <filter> 
  IP v4: <filter> scope: global broadcast: <filter> 
  WAN IP: <filter> 
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB 
  driver: btusb v: 0.8 bus-ID: 1-1.1:3 chip-ID: 0a12:0001 class-ID: fe01 
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends 
Logical:
  Permissions: Unable to run lvs. Root privileges required. 
RAID:
  Message: No RAID data found. 
Drives:
  Local Storage: total: 2.73 TiB used: 2.45 TiB (89.9%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD30EFRX-68EUZN0 
  size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: <unknown> 
  rotation: 5400 rpm serial: <filter> rev: 0A82 scheme: GPT 
  Message: No optical or floppy data found. 
Partition:
  ID-1: / raw-size: 48.83 GiB size: 47.81 GiB (97.92%) used: 33.55 GiB (70.2%) 
  fs: ext4 dev: /dev/sda3 maj-min: 8:3 label: N/A 
  ID-2: /home raw-size: 2.68 TiB size: 2.66 TiB (99.21%) 
  used: 2.42 TiB (91.1%) fs: ext4 dev: /dev/sda4 maj-min: 8:4 label: HomeS 
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 512 MiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/sda2 maj-min: 8:2 label: N/A 
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 1024 KiB fs: <superuser required> 
  label: N/A uuid: N/A 
USB:
  Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 4 rev: 2.0 
  speed: 480 Mb/s chip-ID: 8087:0024 class-ID: 0900 
  Device-1: 1-1.1:3 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) 
  type: Bluetooth driver: btusb interfaces: 4 rev: 2.0 speed: 12 Mb/s 
  chip-ID: 0a12:0001 class-ID: fe01 
  Device-2: 1-1.2:4 info: MosArt Wireless Keyboard/Mouse type: Keyboard,Mouse 
  driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s 
  power: 100mA chip-ID: 062a:4101 class-ID: 0301 
  Hub-3: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0 
  speed: 480 Mb/s chip-ID: 8087:0024 class-ID: 0900 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 225 Uptime: 1d 11h 25m wakeups: 0 Init: systemd v: 248 
  tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.0 Packages: pacman: 1843 
  lib: 450 flatpak: 0 Shell: Zsh v: 5.8 running-in: lxterminal inxi: 3.3.04 
~ ᐅ 

I can’t either - but KDE employs some indexing functionality which makes it possible to tag files for easier retrieval.

I am not a KDE user - so I have no indepth knowledge - my guess is that you have been altering a setting which instructs the indexer and file dialog to search for tags as well as filenames.

1 Like
  1. inxi looks good.
  2. Can you post a screenshot of the File Dialog and also one of your file manager? (Do you have any other than Dolphin in use?)
  3. Does this also happen under a newly created user? (E.G. llama2)

:thinking:

Do you really want a screenshot? It’s a plain message dialog with an OK button. It pops up ahead of any KDE File Dialog (with Okular, Konqueror, Gwenview, etc.; not with Geany, for instance).

With another (specially created) user the subj won’t happen.

So you have an issue in your user profile and finding out which exact setting you changed is going to take weeks if not months, so we’re going to do the following:

  • Verify that the new user has access to the same groups as your old one by executing groups and comparing the output of both users.

    groups llama
    groups llama2
    

    (Where obviously, llama is your old user and llama2 is your new one.)
    E.G. if llama is a member of operator and llama2 isn’t, execute:

    usermod --append --groups operator llama2
    
  • Copy all data files from your old profile into your new one

    cp --verbose --recursive --preserve=time-stamps /home/llama/Documents/* /home/llama2/Documents/
    

    If that worked and you had no errors, remove the documents from your old user:

    rm --recursive /home/llama/Documents/*
    

    repeat for:

    • Pictures
    • Videos
    • Music
    • .thunderbird
    • .mozilla/firefox/
    • Templates, and everything else that is important to you.
    • Linux games like Battle of Wesnoth have their game data stored under ~/.local/share/ E.G. ~/.local/share/wesnoth/

    After everything has been copied over, disable the old user so you cannot accidentally log on:

    usermod --lock llama
    

    If you would have theming going on, don’t do everything in one day but do this at the rate of 1 application / theme / whatever per day and if the same issue crops up again, roll back your last change and thus you’ve now pinpointed the exact setting that made your old user misbehave. :thinking:

  • in 1 month delete the entire home directory of your old user, but don’t delete the user itself so that in 6 months time files still owned by that user will still show up under its username.

  • If you ever migrate to a new machine, just don’t migrate the old user: only the new one.

  • From now on, start making backups so you can roll back and never have to do this again:

Are you prescribing a shave with a guillotine for my running nose? I’ll have to assume the proper attitude first, I’m afraid :smile:

Your comment rang a bell :slight_smile: . A while ago I turned off File Search (baloo_file process) in a not-so-successful attempt to diminish the CPU load. I turned it back on; no more trouble with the tags folder.

Now the real question reads like this: how should I turn off File Search the right way?

No, I’m prescribing a quick shave with a shaver instead of epilation with a tweezer.

:man_shrugging:

Try: balooctl purge
or/and disable baloo and then balooctl purge
maybe: rm ~/file.desktop ??? I don’t know what helped me.

Sometimes it’s quicker, easier, less messy and in general better to start from scratch than it is to troubleshoot something…and that amount of effort and time spent varies from situation to situation and person to person.

You’re telling the wrong person. I’m not OP and I agree.

:man_shrugging:

1 Like

Yeah, just left it out there.

1 Like