navigation through the kioslave system:/users/ is broken

Bug #42666 reported by mon
12
Affects Status Importance Assigned to Milestone
KDE Utilities
Unknown
Medium
kdeutils (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Hi

Using system:/users/ to access users folders result in the same bugs system:/ io slave produces.

Maybe it would be appropiate to patch the url system:/users/username to go to /home/username so these problems don't ocurr.

As an example, I can't compress anything in a konqueror's location like system:/users/username/folder with rightclick "compress with ark action".

Thanxs

Changed in kdebase:
assignee: nobody → kubuntu-team
Revision history for this message
Andres Mujica (andres.mujica) wrote :

i don't quite understand your bug report,

the expected behaviour (please correct me if i wrong)

is that you cannot access the other's user home directories.

if you can access you cannot write on them.

so if you try to create a file on another user's folder you should have an error message.

Please clarify a litle bit about your bug.

Thanks a lot

Revision history for this message
Noah Medling (noah-medling) wrote :

I think I figured out what he's talking about. Here's what I did (Edgy AMD64, everything up-to-date):

1. Open system:/home/<your username> in Konqueror

2. Right-click on a file (I used a small shell script; should work with anything) -> Compress -> Compress as blahblah.tar.gz

3. Wait for a while before deciding that it's not going to work and hit Cancel.

4. Open /home/<your username> in Konqueror, repeat step 2, everything works.

5. Repeat steps 1 and 2 (the file created in step 4 should still be there). Ark crashes with the following backtace:

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)

... snip ...

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47756256022240 (LWP 8406)]
(no debugging symbols found)

... snip ...

(no debugging symbols found)
0x00002b6f1abcdc71 in nanosleep () from /lib/libc.so.6
#0 0x00002b6f1abcdc71 in nanosleep () from /lib/libc.so.6
#1 0x00002b6f1abcda94 in sleep () from /lib/libc.so.6
#2 0x00002b6f1b363575 in KCrash::startDrKonqi ()
   from /usr/lib/libkdecore.so.4
#3 0x00002b6f1b377b07 in KCrash::defaultCrashHandler ()
   from /usr/lib/libkdecore.so.4
#4 0x00002b6f1ab69510 in killpg () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Note that creating and deleting files and folders, as well as editing in Kate all works just fine for me. I think this is a problem with Ark, not the IO slave. Also, system:/home displays the contents of /home/<username> and system:/users displays the contents of /home, but opening system:/ and clicking on Home Folder takes you to /home/<username> directly.

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

I can confirm that the ark context menu doesn't work with the system:/ kio slave. This kio slave is not used in edgy, but removing those patches in Feisty is under consideration, so I'm keeping this open.

Other than the specific ark issue, this is a duplicate of bug 32159.

Changed in kdebase:
status: Unconfirmed → Confirmed
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Attaching a backtrace from a crash produced by following Noah Medling's procedure on Feisty with latest updates.

Changed in kdeutils:
status: Unknown → Confirmed
Changed in kdeutils:
assignee: kubuntu-bugs → nobody
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

I am closing this since the system:/ KIO slave no longer exists in KDE4 in Intrepid. Please reopen if you can reproduce this with another KIO slave in KDE4.

Changed in kdeutils:
importance: Medium → Low
status: Confirmed → Fix Released
Changed in kdeutils:
status: Confirmed → Invalid
Changed in kdeutils:
status: Invalid → Unknown
Changed in kdeutils:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.