You are not logged in.

#1 2018-04-05 20:53:59

sunnylx
Member
Registered: 2015-08-20
Posts: 41

File permission issue creation but only with KDE apps

So I have indeed a very strange problem that after several hours I can't solve:

The issue:   Any file that I create using Kde Apps, for example Dolphin->New or temporary files, for example Okular-> Print (creates a temporary file in /tmp) is created with 000 ---------- permissions!!!

I've checked umask (022) in any location that I can imagine, and it seems fine.

I've created a new user profile same issue.

So if I go to the terminal/Konsole and create a file, the permissions are fine:

touch test.file   -> -rw-r--r--

If I do the same with Dolphin -> the permissions are ----------

The problem with this is that is system wide, and all the temporary files that KDE creates are also with ---------- which means, for example, Okular can't print, because it creates the ps file in /tmp without any permissions, and then lpr fails to open it.

Any ideas?

Offline

#2 2018-04-05 21:00:38

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,846
Website

Re: File permission issue creation but only with KDE apps

That is indeed a very strange problem, but unfortunately I can't reproduce it here.

I'm not sure where this sort of problem would be introduced, but please post the full journal from an affected session (where you create a file with faulty permissions). That might give us some hints on where to look.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#3 2018-04-06 09:47:26

sunnylx
Member
Registered: 2015-08-20
Posts: 41

Re: File permission issue creation but only with KDE apps

Do you mean the journalctl output?

Running from the prompt okular:

okular file.pdf 
Config timer connecting...
Setting the name of  0x556cd5652ee0  to  "org.kde.ActivityManager.ActivityTemplates"
Setting the name of  0x556cd565f700  to  "org.kde.ActivityManager.RunApplication"
Setting the name of  0x556cd56726c0  to  "org.kde.ActivityManager.Resources.Scoring"
Creating directory:  "/home/fdam/.local/share/kactivitymanagerd/resources/"
KActivities: Database connection:  "kactivities_db_resources_139629043771392_readwrite" 
    query_only:          QVariant(qlonglong, 0) 
    journal_mode:        QVariant(QString, "wal") 
    wal_autocheckpoint:  QVariant(qlonglong, 100) 
    synchronous:         QVariant(qlonglong, 1)
Service started, version: 7.0.0
Cleaning up...
/usr/bin/lpr: Error - unable to access "/tmp/okular_ZhBYGK.ps" - Permission denied

The file /tmp/okular_ZhBYGK.ps has zero permissions, hence the lpr command fails. I've tested with other applications for example kate produces zero permission files:

kate test.txt
inotify_add_watch("/home/user/test.txt") failed: "Permission denied"   <- This happens when I save the file from Kate

Last edited by sunnylx (2018-04-06 09:53:41)

Offline

#4 2018-04-06 09:53:04

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,846
Website

Re: File permission issue creation but only with KDE apps

Yes.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#5 2018-04-06 10:00:39

sunnylx
Member
Registered: 2015-08-20
Posts: 41

Re: File permission issue creation but only with KDE apps

Please note that I'm accessing trhough SSH now (with X forwarding) and not running a full desktop session, but the issue is the same either on the desktop or through ssh:

Apr 06 10:34:01 tesla sshd[16897]: Accepted password for puser from 192.168.1.19 port 46890 ssh2
Apr 06 10:34:01 tesla sshd[16897]: pam_unix(sshd:session): session opened for user puser by (uid=0)
Apr 06 10:34:01 tesla systemd[1]: Created slice User Slice of puser.
Apr 06 10:34:01 tesla systemd[1]: Starting User Manager for UID 1000...
Apr 06 10:34:01 tesla systemd[1]: Started Session c7 of user puser.
Apr 06 10:34:01 tesla systemd-logind[312]: New session c7 of user puser.
Apr 06 10:34:01 tesla systemd[16899]: pam_unix(systemd-user:session): session opened for user puser by (uid=0)
Apr 06 10:34:01 tesla systemd[16899]: Reached target Paths.
Apr 06 10:34:01 tesla systemd[16899]: Listening on GnuPG network certificate management daemon.
Apr 06 10:34:01 tesla systemd[16899]: Starting D-Bus User Message Bus Socket.
Apr 06 10:34:01 tesla systemd[16899]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 06 10:34:01 tesla systemd[16899]: Reached target Timers.
Apr 06 10:34:01 tesla systemd[16899]: Listening on Sound System.
Apr 06 10:34:01 tesla systemd[16899]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 06 10:34:01 tesla systemd[16899]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 06 10:34:01 tesla systemd[16899]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 06 10:34:01 tesla systemd[16899]: Listening on D-Bus User Message Bus Socket.
Apr 06 10:34:01 tesla systemd[16899]: Reached target Sockets.
Apr 06 10:34:01 tesla systemd[16899]: Reached target Basic System.
Apr 06 10:34:01 tesla systemd[1]: Started User Manager for UID 1000.
Apr 06 10:34:01 tesla systemd[16899]: Reached target Default.
Apr 06 10:34:01 tesla systemd[16899]: Startup finished in 27ms.
Apr 06 10:34:46 tesla sudo[16920]:     puser : TTY=pts/0 ; PWD=/home/puser ; USER=root ; COMMAND=/bin/bash
Apr 06 10:34:46 tesla sudo[16920]: pam_unix(sudo:session): session opened for user root by puser(uid=0)
Apr 06 10:34:49 tesla su[16922]: (to suser) puser on pts/0
Apr 06 10:34:49 tesla su[16922]: pam_unix(su-l:session): session opened for user suser by puser(uid=0)
Apr 06 10:36:17 tesla NetworkManager[311]: <info>  [1523007377.0013] connectivity: (wlp3s0) timed out
Apr 06 10:40:57 tesla su[16922]: pam_unix(su-l:session): session closed for user suser
Apr 06 10:41:17 tesla NetworkManager[311]: <info>  [1523007677.0016] connectivity: (wlp3s0) timed out
Apr 06 10:46:17 tesla NetworkManager[311]: <info>  [1523007977.0023] connectivity: (wlp3s0) timed out
Apr 06 10:46:53 tesla sudo[16920]: pam_unix(sudo:session): session closed for user root
Apr 06 10:46:54 tesla sshd[16905]: Received disconnect from 192.168.1.19 port 46890:11: disconnected by user
Apr 06 10:46:54 tesla sshd[16905]: Disconnected from user puser 192.168.1.19 port 46890
Apr 06 10:46:54 tesla sshd[16897]: pam_unix(sshd:session): session closed for user puser
Apr 06 10:46:54 tesla systemd-logind[312]: Removed session c7.
Apr 06 10:46:54 tesla systemd[1]: Stopping User Manager for UID 1000...
Apr 06 10:46:54 tesla systemd[16899]: Stopped target Default.
Apr 06 10:46:54 tesla systemd[16899]: Stopped target Basic System.
Apr 06 10:46:54 tesla systemd[16899]: Stopped target Sockets.
Apr 06 10:46:54 tesla systemd[16899]: Closed GnuPG network certificate management daemon.
Apr 06 10:46:54 tesla systemd[16899]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 06 10:46:54 tesla systemd[16899]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 06 10:46:54 tesla systemd[16899]: Closed D-Bus User Message Bus Socket.
Apr 06 10:46:54 tesla systemd[16899]: Closed Sound System.
Apr 06 10:46:54 tesla systemd[16899]: Stopped target Paths.
Apr 06 10:46:54 tesla systemd[16899]: Stopped target Timers.
Apr 06 10:46:54 tesla systemd[16899]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 06 10:46:54 tesla systemd[16899]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 06 10:46:54 tesla systemd[16899]: Reached target Shutdown.
Apr 06 10:46:54 tesla systemd[16899]: Starting Exit the Session...
Apr 06 10:46:54 tesla systemd[16899]: Received SIGRTMIN+24 from PID 17131 (kill).
Apr 06 10:46:54 tesla systemd[16900]: pam_unix(systemd-user:session): session closed for user puser
Apr 06 10:46:54 tesla systemd[1]: Stopped User Manager for UID 1000.
Apr 06 10:46:54 tesla systemd[1]: Removed slice User Slice of puser.
Apr 06 10:48:03 tesla sshd[17133]: Accepted password for puser from 192.168.1.19 port 46891 ssh2
Apr 06 10:48:03 tesla sshd[17133]: pam_unix(sshd:session): session opened for user puser by (uid=0)
Apr 06 10:48:03 tesla systemd[1]: Created slice User Slice of puser.
Apr 06 10:48:03 tesla systemd[1]: Starting User Manager for UID 1000...
Apr 06 10:48:03 tesla systemd[1]: Started Session c8 of user puser.
Apr 06 10:48:03 tesla systemd-logind[312]: New session c8 of user puser.
Apr 06 10:48:03 tesla systemd[17135]: pam_unix(systemd-user:session): session opened for user puser by (uid=0)
Apr 06 10:48:03 tesla systemd[17135]: Listening on Sound System.
Apr 06 10:48:03 tesla systemd[17135]: Reached target Paths.
Apr 06 10:48:03 tesla systemd[17135]: Reached target Timers.
Apr 06 10:48:03 tesla systemd[17135]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 06 10:48:03 tesla systemd[17135]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 06 10:48:03 tesla systemd[17135]: Starting D-Bus User Message Bus Socket.
Apr 06 10:48:03 tesla systemd[17135]: Listening on GnuPG network certificate management daemon.
Apr 06 10:48:03 tesla systemd[17135]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 06 10:48:03 tesla systemd[17135]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 06 10:48:03 tesla systemd[17135]: Listening on D-Bus User Message Bus Socket.
Apr 06 10:48:03 tesla systemd[17135]: Reached target Sockets.
Apr 06 10:48:03 tesla systemd[17135]: Reached target Basic System.
Apr 06 10:48:03 tesla systemd[17135]: Reached target Default.
Apr 06 10:48:03 tesla systemd[17135]: Startup finished in 26ms.
Apr 06 10:48:03 tesla systemd[1]: Started User Manager for UID 1000.
Apr 06 10:48:12 tesla systemd[17135]: Started D-Bus User Message Bus.
Apr 06 10:48:27 tesla dbus-daemon[17166]: [session uid=1000 pid=17166] Activating service name='org.kde.ActivityManager' requested by ':1.2' (uid=1000 pid=17181 comm="okular Cronograma.pdf ")
Apr 06 10:48:27 tesla kactivitymanagerd[17187]: qt.qpa.screen: QXcbConnection: Could not connect to display
Apr 06 10:48:27 tesla kactivitymanagerd[17187]: Could not connect to any X display.
Apr 06 10:48:27 tesla dbus-daemon[17166]: [session uid=1000 pid=17166] Activated service 'org.kde.ActivityManager' failed: Process org.kde.ActivityManager exited with status 1
Apr 06 10:48:27 tesla dbus-daemon[17166]: [session uid=1000 pid=17166] Activating service name='org.kde.ActivityManager' requested by ':1.2' (uid=1000 pid=17181 comm="okular Cronograma.pdf ")
Apr 06 10:48:27 tesla kactivitymanagerd[17193]: qt.qpa.screen: QXcbConnection: Could not connect to display
Apr 06 10:48:27 tesla kactivitymanagerd[17193]: Could not connect to any X display.
Apr 06 10:48:27 tesla dbus-daemon[17166]: [session uid=1000 pid=17166] Activated service 'org.kde.ActivityManager' failed: Process org.kde.ActivityManager exited with status 1
Apr 06 10:51:17 tesla NetworkManager[311]: <info>  [1523008277.0008] connectivity: (wlp3s0) timed out

Offline

#6 2018-04-06 11:02:09

sunnylx
Member
Registered: 2015-08-20
Posts: 41

Re: File permission issue creation but only with KDE apps

Ok,

I've gave up, and did  a full package re-install:

pacman -Qnq | pacman -S -

It seems so far to solve it.

What it was I don't know, but something was borked ... smile

Offline

Board footer

Powered by FluxBB