[kio-extras] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."
https://bugs.kde.org/show_bug.cgi?id=431050 fdkde changed: What|Removed |Added CC||fd483721...@mailbox.org --- Comment #11 from fdkde --- No write access with the same error displayed. I can delete stuff and create new folders but writing files is impossible. I use smb4k as a workaround but it opens a huge amount of files on our Windows Server shares (can be seen in the server logs) which are connected through DFS. Dolphin: 22.12.2 Operating System: Fedora Linux 37 (KDE Spin) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.11-200.fc37.x86_64 (64-bit) Graphics platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."
https://bugs.kde.org/show_bug.cgi?id=431050 --- Comment #14 from fdkde --- (In reply to Harald Sitter from comment #13) > Interesting data points might be what dolphin reports as free space > (Alt+Return in a folder) versus what the actual space reported on the server > is. In the folder properties of my personal root directory (which is limited by a quota of 100 GB) for example Dolphin is reporting that "0 B of 0 B free" and that are 0 % are being used. A Windows 10 VM is reporting that the directory has a size of 70,1 GB. When I look at the disk space bar at the bottom right of the main window Dolphin shows 476,7 GiB as free. However I don't think that number is accurate. Last week a colleague at work said that smb clients only see the amount of space which is left on the system partition of the domain controller which hosts the particular smb share. On shares without a per-user-quota the behavior is the same - 0 B of 0 B and 0 % used. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."
https://bugs.kde.org/show_bug.cgi?id=431050 --- Comment #15 from fdkde --- (In reply to fdkde from comment #14) > (In reply to Harald Sitter from comment #13) > > Interesting data points might be what dolphin reports as free space > > (Alt+Return in a folder) versus what the actual space reported on the server > > is. > > In the folder properties of my personal root directory (which is limited by > a quota of 100 GB) for example Dolphin is reporting that "0 B of 0 B free" > and that are 0 % are being used. A Windows 10 VM is reporting that the > directory has a size of 70,1 GB. When I look at the disk space bar at the > bottom right of the main window Dolphin shows 476,7 GiB as free. However I > don't think that number is accurate. Last week a colleague at work said that > smb clients only see the amount of space which is left on the system > partition of the domain controller which hosts the particular smb share. > > On shares without a per-user-quota the behavior is the same - 0 B of 0 B and > 0 % used. Addition: The data itself is not located on the domain controllers. They only provide the smb shares to the clients. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."
https://bugs.kde.org/show_bug.cgi?id=431050
--- Comment #18 from fdkde ---
Thanks for your patch. I tested a build of the kio-extras master branch on a
Fedora VM. Dolphin does not not complain anymore about having insuffient space
on the network share. Kudos to you 👍 👏 😊
However LibreOffice which uses the KDE file chooser window (through
xdg-desktop-portal? I don't know) is throwing me an error, when I try to save a
file directly on the smb share by entering the full path
("smb://user@domain.example/home/username..."): "Error saving the document
Testdocument: Object not accessible. The object cannot be accessed due to
insufficient user rights.". When the file is already existing on the smb share,
changes are getting saved without error messages.
Mozilla Firefox (configured with widget.use-xdg-desktop-portal.mime-handler = 1
and widget.use-xdg-desktop-portal.file-picker =1 to use the KDE file picker
through xdg-desktop-portal) doesn't show my personal network folder, only the
folders above and no content on any smb-based folder. On some but not all smb
shares I see an other error message which states that the file or folder I try
to access doesn't exist.
Maybe I have those problems due to the fact that I tested your changes in a VM.
Maybe it's just the infrastructure of my enterprise network environment. I will
test it on a normal system and report back if the issues still appear.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."
https://bugs.kde.org/show_bug.cgi?id=431050
--- Comment #19 from fdkde ---
(In reply to fdkde from comment #18)
> Thanks for your patch. I tested a build of the kio-extras master branch on a
> Fedora VM. Dolphin does not not complain anymore about having insuffient
> space on the network share. Kudos to you 👍 👏 😊
>
> However LibreOffice which uses the KDE file chooser window (through
> xdg-desktop-portal? I don't know) is throwing me an error, when I try to
> save a file directly on the smb share by entering the full path
> ("smb://user@domain.example/home/username..."): "Error saving the document
> Testdocument: Object not accessible. The object cannot be accessed due to
> insufficient user rights.". When the file is already existing on the smb
> share, changes are getting saved without error messages.
>
> Mozilla Firefox (configured with widget.use-xdg-desktop-portal.mime-handler
> = 1 and widget.use-xdg-desktop-portal.file-picker =1 to use the KDE file
> picker through xdg-desktop-portal) doesn't show my personal network folder,
> only the folders above and no content on any smb-based folder. On some but
> not all smb shares I see an other error message which states that the file
> or folder I try to access doesn't exist.
> Maybe I have those problems due to the fact that I tested your changes in a
> VM.
>
> Maybe it's just the infrastructure of my enterprise network environment. I
> will test it on a normal system and report back if the issues still appear.
EDIT: Sorry for the doubled negation. Dolphin does not complain anymore
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."
https://bugs.kde.org/show_bug.cgi?id=431050 --- Comment #23 from fdkde --- I hope that adds some more information which is helpful to track down the issue: While browsing through some smb shares and folders with the modified kio-extras version I noticed some repeating error messages that Dolphin put out into the terminal session where I started it from: session setup failed: NT_STATUS_NO_MEMORY Unable to follow dfs referral [path to smb share] Couldn't resolve [path to the accessed folder, starting from the smb share] Info: I had to redact the smb share path and folders for confidential reasons. Unfortunately I was too busy today to test if I get the same error messages on with my productive system without the modified kio-extras version. The problems I had on the VM are gone on a physical system but I got a new error message from LibreOffice when trying to write new files via smb: Fehler beim Speichern des Dokuments Unbenannt 1: Kein Zugriff auf Objekt. Aufgrund fehlender Benutzerrechte kann auf das Objekt nicht zugegriffen werden. Translated freely: Error while saving the document Unbenannt 1: No access on object. It isn't possible to access the object due to missing user rights. Saving existing file is working without problems. I don't know if the reason for that is our infrastructure or something that can be fixed by KDE or LibreOffice developers. One thing I've noticed when trying the same with Kate is that the KDE file pickers for LibreOffice and Kate look quite similar. But there is one detail what catched my eye: The network/foreign devices section in the left pane of the file picker for LibreOffice is/was missing. Two question for better understanding: How are the file pickers are getting created and configured? Can application developers decide if the KDE file picker is showing/supporting the network/foreign section or not? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."
https://bugs.kde.org/show_bug.cgi?id=431050 --- Comment #26 from fdkde --- For some time I was able to access the network shares via our fully qualified domain name. When I joined the machine with the domain by using sssd and realmd, the access to the DFS shares broke again. First I thought the domain join was the cause why it reappeared but on a fresh VM install with Fedora 39 I run into the same problem again: session setup failed: NT_STATUS_NO_MEMORY Unable to follow dfs referral [\filecluster\personal$] Could not resolve \Personal\* session setup failed: NT_STATUS_NO_MEMORY Unable to follow dfs referral [\filecluster\personal$] Could not resolve \Personal\ The only configuration changes I did to the VM: - Put our domain as workgroup in /etc/samba/smb.conf - Put the FQDN as search domain in the NetworkManager GUI for the Ethernet connection - Changed the hostname in /etc/hostname including the actual domain name as the hostname of the VM defaulted to "fedora" For some reason the VM can access the share via //filecluster (as proof see screenshot above) which is a (virtual) DNS name and a Active Directory object for our file server cluster. However KIO (still) complains about having not enough memory: kf.kio.core: "Fehler. Nicht genügend Speicher.\nsmb://filecluster/personal$" That doesn't work at all on my domain-joined host machine. Dolphin: 23.08.1 Operating System: Fedora Linux 39 (KDE Spin) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.11-300.fc39.x86_64 (64-bit) Graphics platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."
https://bugs.kde.org/show_bug.cgi?id=431050 --- Comment #27 from fdkde --- Created attachment 163110 --> https://bugs.kde.org/attachment.cgi?id=163110&action=edit NT_STATUS_NO_MEMORY when accessing DFS shares -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."
https://bugs.kde.org/show_bug.cgi?id=431050 --- Comment #28 from fdkde --- Created attachment 163111 --> https://bugs.kde.org/attachment.cgi?id=163111&action=edit Accessing file clusters directly via SMB without DFS works -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 fdkde changed: What|Removed |Added CC||fd483721...@mailbox.org --- Comment #52 from fdkde --- (In reply to Yasin Zähringer from comment #33) > While investigating a different issue I found a workaround (which however > does not address the root cause): > start the akonadi console, select the browser tab and find the affected > inbox. Right click on it and select folder properties. Now you find a tab > called ACL and where probably all check boxes are deselected. I checked all > boxes except the two boxes of the second row (link,unlink) because a > subfolder also had these boxes unchecked. After I restarted KMail, I was > finally able to move mails again. Thanks for the workaround, but it is only working temporarily - at least for me on Version 5.22.1 (22.12.1). Everytime I create a new folder in my IMAP account, the issue reappears and the ACL changes are getting reverted to the previous settings. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 fdkde changed: What|Removed |Added Platform|Ubuntu |Archlinux Version|4.9.4 |5.22.1 -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 464328] New: PIM events plugin shows events twice after dissociation from the event series
https://bugs.kde.org/show_bug.cgi?id=464328
Bug ID: 464328
Summary: PIM events plugin shows events twice after
dissociation from the event series
Classification: Applications
Product: kdepim
Version: 5.22.1
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: fd483721...@mailbox.org
Target Milestone: ---
Created attachment 155315
--> https://bugs.kde.org/attachment.cgi?id=155315&action=edit
Screenshot of the dissociated event in Kontact/Korganizer and the corresponding
calendar widget entries
SUMMARY
The PIM events plugin in the digital clock widget shows events twice after
dissociation from the event series - once as part of the event series and once
as single event.
STEPS TO REPRODUCE
1. Configure the Plasma digital clock widget to use the PIM events plugin for
the calendar: Right-click on the digital clock widget -> "Configure Digital
Clock..." > "Calendar" > "Available Plugins" > tick checkbox for "PIM Events
Plugin".
2. Configure the PIM events plugin to use your calendar: Still in "Digital
Clock Settings" > "PIM Events Plugin" > tick checkbox for your calendar > "OK".
3. Apply your changes by clicking on "Apply" and "OK".
4. Create a new event in Korganizer ("New Event...") and configure it as
recurring event (tab "Recurrence"- I chose "Repeats" > "Weekly") and save it
with "Apply" and "OK".
5. Dissociate one event of the recurring event (series) by choosing one event
of the series with by right-clicking on it and click on the "Dissociate from
Recurrence..." context menu entry. If Korganizer asks for confirmation, hit
"Dissociate".
6. Open the settings of the newly dissociated event by right-clicking on it and
choosing "Edit...".
7. Edit the time and/or date for the newly dissociated event (right-click on
event -> "Edit...") and save your changes.
8. Open the calendar of the digital clock widget by left-clicking on it and
choose the day of the dissociated event.
OBSERVED RESULT
The dissociated and modified event is now displayed twice in the calendar of
the digital clock widget - as a recurring event and as a dissociated event.
EXPECTED RESULT
The event that is now dissociated from the recurring event (series) should only
be visible once in the calendar of the digital clock widget and should not be
displayed a second time as part of the recurring event.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: KDE neon 5.26 and Arch Linux (rolling)
(available in About System)
KDE Plasma Version: Both 5.26.5
KDE Frameworks Version: Both 5.101.0
Qt Version: Both 5.15.8
ADDITIONAL INFORMATION
I'm not really sure if the bug is related to the PIM events plugin or to
Korganizer's. Do they treat recurring and dissociated events in the same way?
I'm wondering if the series of events internally/database-wise consists out of
single events or if the series is treated as one single object for both of
them.
--
You are receiving this mail because:
You are watching all bug changes.
