Bug 121785 - libreoffice webdav owncloud security rights
Summary: libreoffice webdav owncloud security rights
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.1.3.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-29 08:39 UTC by Dr. Fred Albrecht
Modified: 2019-08-12 07:47 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dr. Fred Albrecht 2018-11-29 08:39:21 UTC
Description:
The communication with my owncloud dosn't work proper after update to LO 6.1.3.2
no secure communication
unsecure communication only read-rights
LO 6.1.3.2 on a winX work very well




Steps to Reproduce:
1. writer open remote file (unsecure port 80)
2. load documentreadonly
3. switch to change-modus new copy
4. save as remote file not allowed

Actual Results:
Nov 24 11:15:02 theosolid kiod5[2339]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0
Nov 24 11:15:08 theosolid su[28915]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Nov 24 11:15:08 theosolid su[28915]: gkr-pam: couldn't unlock the login keyring.
Nov 24 11:15:08 theosolid su[28915]: (to root) albrecht on pts/4
Nov 24 11:15:08 theosolid su[28915]: pam_systemd(su-l:session): Cannot create session: Already running in a session or user slice
Nov 24 11:15:08 theosolid su[28915]: pam_unix(su-l:session): session opened for user root by albrecht(uid=1000)
Nov 24 11:15:09 theosolid kdeinit5[29004]: Qt: Session management error: networkIdsList argument is NULL
Nov 24 11:15:12 theosolid kiod5[2339]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0
Nov 24 11:15:22 theosolid kiod5[2339]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0
Nov 24 11:15:32 theosolid kiod5[2339]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0
Nov 24 11:15:42 theosolid kiod5[2339]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0
Nov 24 11:15:44 theosolid drkonqi[28921]: Sending SIGCONT to process
Nov 24 11:15:44 theosolid kwin_x11[2110]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 44234, resource id: 174063621, major code: 18 (ChangeProperty), minor code: 0
Nov 24 11:15:44 theosolid kdeinit5[2075]: Service ":1.343" unregistered
Nov 24 11:15:45 theosolid systemd[1]: Started Process Core Dump (PID 29011/UID 0).
Nov 24 11:15:45 theosolid systemd-coredump[29012]: Resource limits disable core dumping for process 28908 (konsole).
Nov 24 11:15:45 theosolid systemd-coredump[29012]: Process 28908 (konsole) of user 1000 dumped core.
Nov 24 11:15:52 theosolid kiod5[2339]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0
Nov 24 11:16:02 theosolid kiod5[2339]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0
Nov 24 11:16:12 theosolid kiod5[2339]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0


Expected Results:
document with read and write rights in change mode


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
LO 6.1.3.2 on a winX work very well on different computers
all linux-computer show the same behaviour
Comment 1 Alex Thurgood 2018-12-04 09:22:09 UTC
Nothing to do with database module, changing to more appropriate one.
Comment 2 Xisco Faulí 2019-08-09 11:33:09 UTC
Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 3 Dr. Fred Albrecht 2019-08-09 12:15:06 UTC
Thank you,


with this version, installed as an user, it works correct, like older versions on winX-maschines.
Comment 4 Xisco Faulí 2019-08-12 07:47:00 UTC
Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.