Bug#704482: #704482 general: file copy over kde gui or cp to an usb devices (tried fat/ext3) is showen as finshed while it's still copying

2013-04-07 Thread Manuel Schmidt
Hey,

 I think it would be nice to have a progress bar that
 would show the actual data transfer.
There is, if you are using KDE and plasma. I think it's trough dbus, so maybe 
it works in Gnome too.

Thats the point there is and its fine but its wrong for fat usb devices, i 
tested it now for cp because its easier to stop the time but its at this 
progress bar from kde the same
So i copied a file with 1,5GB and the copy progress is finished in 55sec 
(command prompt comes back) but it isn't, you see that they device is still 
working for another 30sec (i have gkrellm where you see the datarate to 
devices) and in this time you can not unmount the device you get the error i 
posted in my last message. So kde and cp are showing a wrong state of coping 
file to fat usb devices. 


 But if it is at those both are not showing the correct state, doesn't that
 mean that this will be at any data copying over usb?. So it's something
 more generall then konquer? (which i do not use, i use Dolphin)

The correct state is being shown, so I don't see a problem here.

you tried it? for fat usb devices?


thanks
best regards

Bug#704482: #704482 general: file copy over kde gui or cp to an usb devices (tried fat/ext3) is showen as finshed while it's still copying

2013-04-02 Thread Manuel Schmidt
Hello thx to your repley


You marked the bug with patch but I don't see any patch, I assume this
was an error.
yes you are right, sorry for that :(

Severity: criticalok i see i overdid it just saw datalost but i think it 
means it in an other content.

Nothing in man cp guarantees that
the file has been copied to the disk when the command exits.
i know that there is no guarantees but at the bash normaly when the prompt 
comes back, the command is fineshed or? which in this case isn't 

Couldn't this make bad behaivors when i write for example bash scripts which 
makes further actions with the file?

I'm a little bit curios that you don't see that kde and cp is showing that they 
have fineshed the file but it isn't. I think this behaivor wasn't in the last 
two stables (maybe i had luck?) but i never used some unmount or save 
remove.There was no need do it., ok i can do it now.
If i unmount there is an error when its coping what is more or less ok:
Unmount failed: Did not receive a reply. Possible causes include: the remote 
application did not send a reply, the message bus security policy blocked the 
reply, the reply timeout expired, or the network connection was broken.
but at the kde eject there is no feedback, you can not say is it now unmounted 
or not.

I think it would be nice to have a progress bar that
would show the actual data transfer.
But if it is at those both are not showing the correct state, doesn't that mean 
that this will be at any data copying over usb?. So it's something more 
generall then konquer? (which i do not use, i use Dolphin)

thanks for your answers
Best regards

Bug#704482: general: file copy over kde gui or cp to an usb devices (tried fat/ext3) is showen as finshed while it's still copying

2013-04-01 Thread Manuel Schmidt
Package: general
Severity: critical
Tags: patch
Justification: causes serious data loss

Tried to copy files over usb to an usb stick (fat32) , before the files
correctly fineshed copying the progress bar ist fineshed / the bash prompt is
back.
This Problem you can just see if you larger files which are not copied
instantly.
The usb-devices are auto mounted by kde / gnome.

lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 2109:0811
Bus 004 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for
Bluetooth
Bus 002 Device 006: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya
Technology Corp.) 64MB QDI U2 DISK

fat device
fdisk
/dev/sdc1   *1144 7831551 3915204c  W95 FAT32 (LBA)

dmesg
[ 4476.345808] usb 2-1.2: new high-speed USB device number 6 using xhci_hcd
[ 4476.417725] usb 2-1.2: New USB device found, idVendor=090c, idProduct=1000
[ 4476.417730] usb 2-1.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 4476.417732] usb 2-1.2: Product: Flash Disk
[ 4476.417734] usb 2-1.2: Manufacturer: USB
[ 4476.417736] usb 2-1.2: SerialNumber: FBH180313345
[ 4476.417861] usb 2-1.2: ep 0x81 - rounding interval to 128 microframes, ep
desc says 255 microframes
[ 4476.417865] usb 2-1.2: ep 0x2 - rounding interval to 128 microframes, ep
desc says 255 microframes
[ 4476.427350] scsi17 : usb-storage 2-1.2:1.0
[ 4477.640842] scsi 17:0:0:0: Direct-Access USB  Flash Disk   1100
PQ: 0 ANSI: 4
[ 4477.641302] sd 17:0:0:0: Attached scsi generic sg4 type 0
[ 4477.642301] sd 17:0:0:0: [sdc] 7831552 512-byte logical blocks: (4.00
GB/3.73 GiB)
[ 4477.642754] sd 17:0:0:0: [sdc] Write Protect is off
[ 4477.642758] sd 17:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 4477.643135] sd 17:0:0:0: [sdc] No Caching mode page present
[ 4477.643138] sd 17:0:0:0: [sdc] Assuming drive cache: write through
[ 4477.644910] sd 17:0:0:0: [sdc] No Caching mode page present
[ 4477.644915] sd 17:0:0:0: [sdc] Assuming drive cache: write through
[ 4477.645648]  sdc: sdc1
[ 4477.647633] sd 17:0:0:0: [sdc] No Caching mode page present
[ 4477.647639] sd 17:0:0:0: [sdc] Assuming drive cache: write through
[ 4477.647642] sd 17:0:0:0: [sdc] Attached SCSI removable disk



-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org