Bug#1070322: marked as pending in kio

2024-05-29 Thread Andreas B. Mundt
Hi,

I started testing the patched kio. Unfortunatelly, it seems to not fix
all issues.  To ease testing, I export and mount from localhost and
run the following (note the link counter in ls -l):  

andi@kde:/media/samba$ ls -l test.tar.gz
ls: cannot access 'test.tar.gz': No such file or directory
andi@kde:/media/samba$ ark --add-to test.tar.gz 
/usr/share/images/desktop-base/desktop-grub.png && ls -l test.tar.gz
-rwxr-xr-x 1 andi andi 147 May 29 21:59 test.tar.gz
   ^
andi@kde:/media/samba$ ark --add-to test.tar.gz 
/usr/share/images/desktop-base/desktop-grub.png && ls -l test.tar.gz
-rwxr-xr-x 0 andi andi 147 May 29 21:59 test.tar.gz
   ^
andi@kde:/media/samba$ ark --add-to test.tar.gz 
/usr/share/images/desktop-base/desktop-grub.png && ls -l test.tar.gz
-rwxr-xr-x 1 andi andi 147 May 29 22:00 test.tar.gz
   ^
andi@kde:/media/samba$ ark --add-to test.tar.gz 
/usr/share/images/desktop-base/desktop-grub.png && ls -l test.tar.gz
-rwxr-xr-x 0 andi andi 147 May 29 22:00 test.tar.gz
   ^
andi@kde:/media/samba$ ls -l test.tar.gz
ls: cannot access 'test.tar.gz': No such file or directory

So if the archive exists, it is removed, if newly generated, it works.
No idea why the file shows up with link counter 0 if the file is
listed immediately after running ark.  It's gone if listed seperately.

Find below some more information about the setup, perhaps this gives
someone some ideas.  I'll continue tomorrow.

Best regards,

  Andi


andi@kdedaily:/media/samba$ grep -vE "^(#|;|$)" /etc/samba/smb.conf 
[global]
   workgroup = WORKGROUP
   log file = /var/log/samba/log.%m
   max log size = 1000
   logging = file
   panic action = /usr/share/samba/panic-action %d
   server role = standalone server
   obey pam restrictions = yes
   unix password sync = yes
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* 
%n\n *password\supdated\ssuccessfully* .
   pam password change = yes
   map to guest = bad user
   usershare allow guests = yes
[homes]
   comment = Home Directories
   browseable = no
   read only = no
   create mask = 0700
   directory mask = 0700
   valid users = %S
[printers]
   comment = All Printers
   browseable = no
   path = /var/tmp
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no

mount:
//localhost/homes/ on /media/samba type cifs 
(rw,nosuid,nodev,relatime,vers=3.1.1,cache=strict,username=andi,uid=1000,noforceuid,gid=1000,noforcegid,addr=:::::::0001,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,nobrl,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1,user=andi)

fstab:
//localhost/homes/ /media/samba cifs  user,nobrl,user=andi,password=123 0 0

apt list "libkf5kio*" "kio*" | grep install
kio-extras-data/stable,stable,now 4:22.12.3-1 all [installed,automatic]
kio-extras/stable,now 4:22.12.3-1 amd64 [installed,automatic]
kio-ldap/stable,now 22.12.3-1 amd64 [installed,automatic]
kio/now 5.103.0-1+deb12u1 amd64 [installed,local]
libkf5kiocore5/now 5.103.0-1+deb12u1 amd64 [installed,local]
libkf5kiofilewidgets5/now 5.103.0-1+deb12u1 amd64 [installed,local]
libkf5kiogui5/now 5.103.0-1+deb12u1 amd64 [installed,local]
libkf5kiontlm5/now 5.103.0-1+deb12u1 amd64 [installed,local]
libkf5kiowidgets5/now 5.103.0-1+deb12u1 amd64 [installed,local]



Bug#1070322: marked as pending in kio

2024-05-25 Thread Aurélien COUDERC
So I’ve went ahead and backported the 2 additional commits mentioned as fixing 
#1069855 for bookworm (sid doesn’t need them).
You’ll find the changes to the debian/bookworm branch for bookworm [1] and 
master for sid [2].

I’ve uploaded the sid package.

I don’t really have the setup to reproduce or test the fixes so @all involved 
would you be OK with :
- reviewing the changes again and building the package from the bookworm Salsa 
branch,
- testing (testing (and retesting)), CIFS and general use cases. The patches 
look unintrusive and the 2 first ones are exact commits from later KIO 
releases, but if there’s something we don’t want to break in KDE that’s 
probably KIO…
- submitting the bug to release.debian.org and get the sign-off from the 
release team ?

I can handle the actual upload once that’s cleared.


[1] https://salsa.debian.org/qt-kde-team/kde/kio/-/commits/debian%2Fbookworm
[2] https://salsa.debian.org/qt-kde-team/kde/kio/-/commits/master/


Thanks !
--
Aurélien