Bug 154527

Summary: Mount point character escape failure
Product: [Unmaintained] kdelibs Reporter: Dan Becker <d.b.becker>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Dan Becker 2007-12-23 14:14:22 UTC
Version:           0.9.2-0ubuntu2 (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
Compiler:          Target: i486-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.1.3 --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release i486-linux-gnu
Thread model: posix
gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)
OS:                Linux

The file manager Konqueror also has this issue.

When inserting a thumb drive automount creates the mount point and mounts the drive. When attempting to browse to the directory created dolphin cannot find the directory.

Screen shot of browsing attempt found here.

http://www.danbecker.us/dolphin-bug/dolphin-screen1.png

Screen shot of autmount creating desktop icon.

http://www.danbecker.us/dolphin-bug/automount-screenshot.png

** output of mount **

root@lappy2:/media# mount
/dev/sda3 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.22-14-386/volatile type tmpfs (rw)
securityfs on /sys/kernel/security type securityfs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
/dev/sdb1 on /media/AZBACK# 001 type vfat (rw,nosuid,nodev,noatime,flush,uid=1000,utf8,shortname=lower)

** output of dmesg when inserting thumbdrive **

[85416.052000] usb 5-5: new high speed USB device using ehci_hcd and address 3
[85416.184000] usb 5-5: configuration #1 chosen from 1 choice
[85416.184000] scsi3 : SCSI emulation for USB Mass Storage devices
[85416.184000] usb-storage: device found at 3
[85416.184000] usb-storage: waiting for device to settle before scanning
[85421.184000] usb-storage: device scan complete
[85421.184000] scsi 3:0:0:0: Direct-Access     SanDisk  Cruzer Micro     0.1  PQ: 0 ANSI: 2
[85421.184000] sd 3:0:0:0: [sdb] 1000944 512-byte hardware sectors (512 MB)
[85421.184000] sd 3:0:0:0: [sdb] Write Protect is off
[85421.184000] sd 3:0:0:0: [sdb] Mode Sense: 03 00 00 00
[85421.184000] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[85421.188000] sd 3:0:0:0: [sdb] 1000944 512-byte hardware sectors (512 MB)
[85421.188000] sd 3:0:0:0: [sdb] Write Protect is off
[85421.188000] sd 3:0:0:0: [sdb] Mode Sense: 03 00 00 00
[85421.188000] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[85421.188000]  sdb: sdb1
[85421.188000] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[85421.188000] sd 3:0:0:0: Attached scsi generic sg2 type 0

** output of df ** 
root@lappy2:/media# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda3              46G   41G  3.2G  93% /
varrun                248M  264K  248M   1% /var/run
varlock               248M  8.0K  248M   1% /var/lock
udev                  248M   84K  248M   1% /dev
devshm                248M     0  248M   0% /dev/shm
lrm                   248M   35M  214M  14% /lib/modules/2.6.22-14-386/volatile
/dev/sdb1             489M   84M  405M  18% /media/AZBACK# 001
Comment 1 Peter Penz 2007-12-23 14:46:03 UTC
Thanks for the bug-report! I know it has not been communicated very well, but bugs.kde.org for Dolphin is only valid for the KDE 4 version of Dolphin, the KDE 3 version is not maintained anymore (see also http://enzosworld.gmxhome.de/download.html section "Dolphin 0.8.2 (KDE 3.5.5)" for more infos).

From the problem description this seems to be more a KDE 3 issue or a distribution issue than a Dolphin issue.
Comment 2 Andrew Crouthamel 2018-11-02 04:14:46 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-16 02:42:38 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2022-12-07 00:24:02 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-12-22 05:19:14 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-01-06 05:23:05 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!