Can't enter folder in file manager, but can enter that folder in terminal?

Help
1

image
image1440×846 18.1 KB

The above image happens when i try to enter .pki through dolphin.

drwx–x–x 1 gooner gooner 10 Apr 26 22:39 .pki/
clearly i own this folder and have execute permissions on this folder

gooner@DESKTOP:~$ cd .pki
gooner@DESKTOP:~/.pki$ ls -A
nssdb

I did this on the dolphin terminal and on the foot terminal and it worked. I also tried editing files inside .pki in the terminal through nano and it worked fine.

There is also a weird issue of me not being able to enter dot folders that were made in the terminal that are in the home dir (as in /home/gooner), though this randomly stopped. And this one time, i just straight up couldnt make any folders in the home dir, though that got solved by reloading dolphin. And sometimes there were some folders in .cache that i ‘did not have permissions’ on

This issue is genuinely getting on my nerves, becuase of how it randomly dissapears and reappears and how weirdly unreproducable it is.

Currently using Dolphin 26.04.0 on CachyOS on kernel Linux 6.18.26-1-cachyos-lts. I’ve tried doing this on Thunar and Nautilus and it did the same thing. This has been an issue since I started using CachyOS on my new laptop so its definitely not filesystem corruption or anything like that, but at first I thought it was a weird feature. I have no idea if this is a bug or a weird config that I messed up or something, and if it ends up being a bug i guess I’ll post it on the kde bug tracker.

(fyi the gooner username was meant to be temporary but it became permanent lol)

2

Hi hat

Considering you have the same problem on Thunar and Nautilus does that mean you are running Thunar and Nautilus on KDE?

Vektor

3

Yep, currently on KDE Plasma 6.6.4.

4

My guess is something in your bashrc enabled the access, but GUI apps don’t have it. Can’t imagine what it is, though.

Try launching Dolphin from a terminal, maybe it can inherit the “magic” of your shell.

(or maybe some selinux or apparmour rubbish).

5

Alright. update

For whatever reason, i can’t seem to make a folder called .wine-storage unless i use mkdir, cant enter it either, and can only remove it with rmdir.

When i use journalctl and try to enter .gnupg or .pki (I’m in the systemd-journal group and the wheel group), it doesnt show anything about apparmor. (I use cachyos’s apparmor and their provided apparmor profiles). Until it randomly did. When I try to enter .gnupg or .pki or .wine-storage, I get

dolphin[10927]: No event config could be found for event id “BellInvisible” under notifyrc file for app “dolphin”

I’ve tried deleting the cache, didn’t help

I still can’t seem to enter .pki and .gnupg, though I’m starting to guess that’s by design.

For whatever reason, I cannot delete .zsh_history (-rw-------) and .viminfo (-rw-------) unless using terminal (btw i use bash so it’s not some weird cannot delete while zsh is running thing)

And while I was writing this, I now gained the ability to make a folder called .wine-storage in the home dir.

I checked my ~/.bashrc, and there seems to be nothing about .gnupg or .pki. (btw i just copied the .bashrc from kubuntu 24.04 lts)

I am so goddamn confused.

EDIT: while editing, I have love the ability to make .wine-storage. I still get No event config could be found for event id “BellInvisible” under notifyrc file for app “dolphin”

6

Here’s my .bashrc file:

~/.bashrc: executed by bash(1) for non-login shells.

see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)

for examples

If not running interactively, don’t do anything

case $- in
*i*) ;;
*) return;;
esac

don’t put duplicate lines or lines starting with space in the history.

See bash(1) for more options

HISTCONTROL=ignoreboth

append to the history file, don’t overwrite it

shopt -s histappend

for setting history length see HISTSIZE and HISTFILESIZE in bash(1)

HISTSIZE=200000
HISTFILESIZE=300000

check the window size after each command and, if necessary,

update the values of LINES and COLUMNS.

shopt -s checkwinsize

If set, the pattern “**” used in a pathname expansion context will

match all files and zero or more directories and subdirectories.

#shopt -s globstar

make less more friendly for non-text input files, see lesspipe(1)

[ -x /usr/bin/lesspipe ] && eval “$(SHELL=/bin/sh lesspipe)”

set variable identifying the chroot you work in (used in the prompt below)

if [ -z “${debian_chroot:-}” ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi

set a fancy prompt (non-color, unless we know we “want” color)

case “$TERM” in
xterm-color|*-256color) color_prompt=yes;;
esac

uncomment for a colored prompt, if the terminal has the capability; turned

off by default to not distract the user: the focus in a terminal window

should be on the output of commands, not on the prompt

#force_color_prompt=yes

if [ -n “$force_color_prompt” ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it’s compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi

if [ “$color_prompt” = yes ]; then
PS1=‘${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ ’
else
PS1=’${debian_chroot:+($debian_chroot)}\u@\h:\w\$ ’
fi
unset color_prompt force_color_prompt

If this is an xterm set the title to user@host:dir

case “$TERM” in
xterm*|rxvt*)
PS1=“\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1”
;;
*)
;;
esac

enable color support of ls and also add handy aliases

if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval “$(dircolors -b ~/.dircolors)” || eval “$(dircolors -b)”
alias ls=‘ls --color=auto’

alias ls=‘eza --color=auto’

alias dir='dir --color=auto'
alias vdir='vdir --color=auto'

alias grep='grep --color=auto'
alias egrep='grep -E'
alias fgrep='grep -F'

fi

colored GCC warnings and errors

#export GCC_COLORS=‘error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01’

some more ls aliases

alias ll=‘ls -Alh’
alias la=‘ls -A’
alias l=‘ls -F’
#alias l=‘ls -CF’

Add an “alert” alias for long running commands. Use like so:

sleep 10; alert

alias alert=‘notify-send --urgency=low -i “$([ $? = 0 ] && echo terminal || echo error)” "$(history|tail -n1|sed -e ‘\’‘s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//’\’‘)"’

Alias definitions.

You may want to put all your additions into a separate file like

~/.bash_aliases, instead of adding them here directly.

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

enable programmable completion features (you don’t need to enable

this, if it’s already enabled in /etc/bash.bashrc and /etc/profile

sources /etc/bash.bashrc).

if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi

export PATH=“$PATH:/home/gooner/.local/bin”

7

When posting files, please do not just copy & paste! Instead put the file contents inside a code block surrounded with an empty lines with three backticks (```) like this:

Here comes some code...

# Enable the subsequent settings only in interactive sessions
case $- in
  *i*) ;;
    *) return;;
esac

Otherwise this forum will interpret the content as Markdown, where # indicates the start of a new heading and so on.

Thank you.

9

Just for completeness - this how your ~/.bashrc looks like when posted as as code and not as text:

# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don’t do anything

case $- in
  *i*) ;;
  *) return;;
esac

# don’t put duplicate lines or lines starting with space in the history.
# See bash(1) for more options

HISTCONTROL=ignoreboth

# append to the history file, don’t overwrite it

shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)

HISTSIZE=200000
HISTFILESIZE=300000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.

shopt -s checkwinsize

# If set, the pattern “**” used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.

#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)

[ -x /usr/bin/lesspipe ] && eval “$(SHELL=/bin/sh lesspipe)”

# set variable identifying the chroot you work in (used in the prompt below)

if [ -z “${debian_chroot:-}” ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we “want” color)

case “$TERM” in
xterm-color|*-256color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n “$force_color_prompt” ]; then
  if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
    # We have color support; assume it’s compliant with Ecma-48
    # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
    # a case would tend to support setf rather than setaf.)
    color_prompt=yes
    else
    color_prompt=
  fi
fi

if [ “$color_prompt” = yes ]; then
  PS1=‘${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ ’
else
  PS1=’${debian_chroot:+($debian_chroot)}\u@\h:\w\$ ’
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir

case “$TERM” in
  xterm*|rxvt*)
    PS1=“\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1”
    ;;
  *)
    ;;
esac

# enable color support of ls and also add handy aliases

if [ -x /usr/bin/dircolors ]; then
  test -r ~/.dircolors && eval “$(dircolors -b ~/.dircolors)” || eval “$(dircolors -b)”
  alias ls=‘ls --color=auto’

  # alias ls=‘eza --color=auto’

  alias dir='dir --color=auto'
  alias vdir='vdir --color=auto'

  alias grep='grep --color=auto'
  alias egrep='grep -E'
  alias fgrep='grep -F'
fi

# colored GCC warnings and errors

#export GCC_COLORS=‘error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01’

# some more ls aliases

alias ll=‘ls -Alh’
alias la=‘ls -A’
alias l=‘ls -F’
#alias l=‘ls -CF’

# Add an “alert” alias for long running commands. Use like so:
# sleep 10; alert

alias alert=‘notify-send --urgency=low -i “$([ $? = 0 ] && echo terminal || echo error)” "$(history|tail -n1|sed -e ‘\’‘s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//’\’‘)"’

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

# enable programmable completion features (you don’t need to enable
# this, if it’s already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).

if ! shopt -oq posix; then
  if [ -f /usr/share/bash-completion/bash_completion ]; then
    . /usr/share/bash-completion/bash_completion
  elif [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
  fi
fi

export PATH=“$PATH:/home/gooner/.local/bin”
10

I forgot to fix the " signs from the original post (the forum replaces colons with “typographic” ones) - but you should get the idea anyway.

11

I think I somehow accidentally removed the ``` while editing because i distinctly remember doing that lol, thanks anyway

Also, the same things still more or less happen, but this one time I couldn’t make any folders in the home folder, though that was solved after a restart of dolphin

I tried thunar again, and yeah the same stuff happens. Except I’m able to delete .zcompdump-emcee-5.9.zwc while in dolphin I can’t (I also can’t do it with the dolphin terminal, which is weird because everything else was doable thru the dolphin terminal)

12

That BellInvisible is a harmless warning, nothing to do with dolphin, it’s a console bell warning, a console bell is just a visual and/or auditory feedback from the console.

Also I noticed you’re using zsh, it would make more sense for you to share your ~/.zshrc instead.

But also, you should probably check this:

Start by showing the contents of:

cat /etc/apparmor.d/abstractions/deny-sensitive-home
13

Btw im not using zsh, i was just testing random crap and seeing if it went wonky on zsh or fish or whatever (i was getting desperate lol). I mainly use bash.

Also yeah, that forum post answered most of my questions, apart from me being unable to make .wine-storage in the home dir. I don’t see anything even remotely related to wine here.

I tried making a file called .d~, and it couldn’t be deleted, so I’m pretty sure this is what caused the problems (apart from the .wine-storage thing i guess. still at a loss on why the hell that happens)

# apparmor.d - Full set of apparmor profiles
# Copyright (C) 2022-2024 Alexandre Pujol <alexandre@pujol.io>
# SPDX-License-Identifier: GPL-2.0-only

# Per the first rule of this project:
#
# !!! quote
#
#     As these are mandatory access control policies only what it explicitly required
#     should be authorized. Meaning, you should not allow everything (or a large area)
#     and blacklist some sub area.
#
# The only legitimate use in this project is for file browser and search engine.

  abi <abi/4.0>,

  # User defined private directories
  deny @{HOMEDIRS}/**/@{XDG_PRIVATE_DIR}/{,**}  mrxwlk,
  deny @{MOUNTS}/**/@{XDG_PRIVATE_DIR}/{,**}    mrxwlk,
  deny @{user_private_dirs}/{,**}               mrxwlk,

  # Files with secret paswords and tokens
  deny @{HOME}/.*age*{,/{,**}}            mrwkl,
  deny @{HOME}/.*aws*{,/{,**}}            mrwkl,
  deny @{HOME}/.*cert*{,/{,**}}           mrwkl,
  deny @{HOME}/.*key*{,/{,**}}            mrwkl,
  deny @{HOME}/.*pass*{,/{,**}}           mrwkl,
  deny @{HOME}/.*pki*{,/{,**}}            mrwkl,
  deny @{HOME}/.*private*{,/{,**}}        mrwkl,
  deny @{HOME}/.*secret*{,/{,**}}         mrwkl,
  deny @{HOME}/.*yubi*{,/{,**}}           mrwkl,
  deny @{HOME}/.aws/{,**}                 mrwkl,
  deny @{HOME}/.kde{,4}/share/apps/kwallet/{,**} mrwkl,
  deny @{HOME}/@{XDG_GPG_DIR}/{,**}       mrwkl,
  deny @{HOME}/@{XDG_SSH_DIR}/{,**}       mrwkl,
  deny @{run}/user/@{uid}/keyring**       mrwkl,
  deny @{user_config_dirs}/*-store/{,**}  mrwkl,
  deny @{user_passwordstore_dirs}/{,**}   mrwkl,
  deny @{user_share_dirs}/kwalletd/{,**}  mrwkl,

  # Privacy violations
  deny @{HOME}/.*.bak                     mrwkl,
  deny @{HOME}/.*.swp                     mrwkl,
  deny @{HOME}/.*~                        mrwkl,
  deny @{HOME}/.*~1~                      mrwkl,
  deny @{HOME}/.*history                  mrwkl,
  deny @{HOME}/.evolution/{,**}           mrwkl,
  deny @{HOME}/.fetchmail*                mrwkl,
  deny @{HOME}/.gnome2_private/{,**}      mrwkl,
  deny @{HOME}/.gnome2/keyrings/{,**}     mrwkl,
  deny @{HOME}/.lesshst*                  mrwkl,
  deny @{HOME}/.mozilla/{,**}             mrwkl,
  deny @{HOME}/.mutt**                    mrwkl,
  deny @{HOME}/.thunderbird/{,**}         mrwkl,
  deny @{HOME}/.viminfo*                  mrwkl,
  deny @{HOME}/.wget-hsts                 mrwkl,
  deny @{user_config_dirs}/chromium/{,**} mrwkl,
  deny @{user_config_dirs}/evolution/{,**} mrwkl,

  # Deny executable mapping in writable space as allowed in abstractions/fonts
  deny @{HOME}/.{,cache/}fontconfig/       rw,
  deny @{HOME}/.{,cache/}fontconfig/**    mrwl,

  # special attention to (potentially) executable files
  deny @{HOME}/bin                          wl,
  deny @{HOME}/bin/{,**}                    wl,

  include if exists <abstractions/deny-sensitive-home.d>

# vim:syntax=apparmor
14

So weirdly, i can’t delete any directories that start with a . and end with storage

It’s probably an apparmor issue and ill research next time but i guess its basically solved

Solution: If you’re using dolphin file manager, just edit /etc/apparmor.d/dolphin and comment out the include /etc/apparmor.d/abstractions/deny-sensitive-home, then do sudo apparmor_parser -r /etc/apparmor.d/dolphin