Re: [Bug 1021375] Re: Nautilus says the USB stick is read only when it is not

2019-06-25 Thread Sergio B
@h23 if you are seeing the same behaviour in the terminal the Nautilus is
not the problem. Your USB is write protected or your computer is picking it
up like that for some reason.

You can insert the USB Stick and then run:

dmesg | tail

To see the system log. There you can see if the write protection is turned
on. If you see something like `Write Protect is off`then you should be
okay, otherwise the USB Stick is protected.

On Tue, 25 Jun 2019 at 09:35, li <1021...@bugs.launchpad.net> wrote:

> I see that many people say that killall nautilus works for them but it
> doesn't change anything for me. Perhaps someone could spell out the
> exact sequence of actions so that I can make sure that I am the problem?
>
> What I am doing right now is
> insert USB
> try to paste something into it using nautilus (same with using terminal
> though), see that it's read only.
> run killall nautilus in terminal.
> (restart or not, I've tried both)
> nautilus window disappears.
> I try to copy something onto the USB again using Nautilus
> still doesn't work.
>
> What am I doing wrong?
> I am working on 16.04.6 LTS
>
> Thanks!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1021375
>
> Title:
>   Nautilus says the USB stick is read only when it is not
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nautilus/+bug/1021375/+subscriptions
>


-- 
*Sergio Bobillier Ceballos*
Ing. de Sistemas
Universidad Nacional de Colombia
+57 (318) 676-3415

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1021375

Title:
  Nautilus says the USB stick is read only when it is not

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1021375/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1021375] [NEW] Nautilus says the USB stick is read only when it is not

2012-07-05 Thread Sergio B
Public bug reported:

First time I use an USB drive since I updated to 12.04 and I found a
really annoying bug on Nautilus. Nautilus claims that the destination
drive is read-only when in fact it is not.

How to reproduce:

1. Connect a USB stick drive to your competer.
2. The USB will appear in the desktop.
3. Open two Nautilus windows one in your home folder, other in the USB stick 
drive.
4. Select any file from your home folder (small enough to fit the free space in 
the USB drive)
5. Drag the file and drop it in the USB drive window.

-- Nautilus will say that it cannot copy the file because the
destination is read ony --

If you try the copy the same file with the terminal you will see that
the file is copied without problem, other programs like gedit or
LibreOffice can write in the usb stick drive just fine.

It is not a problem with the USB stick, as shown here:

[ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd
[ 6232.426378] scsi8 : usb-storage 2-1:1.0
[ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP 
PQ: 0 ANSI: 0 CCS
[ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0
[ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 GB/1.86 
GiB)
[ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off
[ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present
[ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present
[ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[ 6234.210138]  sdb: sdb1
[ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present
[ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk

The permisions on the removable drive are set correctly:

sergio@shana:/media$ ls -lah
total 12K
drwxr-xr-x  3 root   root   4,0K jul  5 10:20 .
drwxr-xr-x 23 root   root   4,0K jul  3 11:01 ..
drwx--  5 sergio sergio 4,0K dic 31  1969 DESIGNPLUS

There is enough free space in the drive:

sergio@shana:/media/DESIGNPLUS$ df -h
S.ficheros TamaƱo Usado  Disp Uso% Montado en
/dev/sda2 50G  5,5G   42G  12% /
udev 1,5G  4,0K  1,5G   1% /dev
tmpfs579M  872K  579M   1% /run
none 5,0M 0  5,0M   0% /run/lock
none 1,5G  1,1M  1,5G   1% /run/shm
/dev/sda1497M  113M  360M  24% /boot
/dev/sda5245G  111G  122G  48% /home
/dev/sdb11,9G  681M  1,2G  36% /media/DESIGNPLUS

A file can be copied to the USB stick using the cp command for example.

sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS
sergio@shana:~/Trash$ cd /media/DESIGNPLUS
sergio@shana:/media/DESIGNPLUS$ ls -lah
total 204K
drwx-- 5 sergio sergio 4,0K jul  5 10:38 .
drwxr-xr-x 3 root   root   4,0K jul  5 10:20 ..
-rw-r--r-- 1 sergio sergio 117K jul  5 10:14 ._Screen Shot 2012-06-30 at 
8.50.37 AM.png
-rw-r--r-- 1 sergio sergio  55K jun 30 08:51 Screen Shot 2012-06-30 at 8.50.37 
AM.png
drwx-- 4 sergio sergio 4,0K jul  5 10:05 .Spotlight-V100
drwx-- 2 sergio sergio 4,0K jul  5 10:05 .Trashes
-rw-r--r-- 1 sergio sergio 4,0K jul  5 10:05 ._.Trashes
-rw-r--r-- 1 sergio sergio   73 jul  5 10:38 wireless.txt

But nautilus just dennies to copy the file claming that the destination
is read only, when it is not.

I tested it with two different USB sticks in two different computers
running Ubuntu 12.04 and the same result.

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  First time I use an USB drive since I updated to 12.04 and I found a
  really annoying bug on Nautilus. Nautilus claims that the destination
  drive is read-only when in fact it is not.
  
  How to reproduce:
  
  1. Connect a USB stick drive to your competer.
  2. The USB will appear in the desktop.
  3. Open two Nautilus windows one in your home folder, other in the USB stick 
drive.
  4. Select any file from your home folder (small enough to fit the free space 
in the USB drive)
  5. Drag the file and drop it in the USB drive window.
  
  -- Nautilus will say that it cannot copy the file because the
  destination is read ony --
  
  If you try the copy the same file with the terminal you will see that
  the file is copied without problem, other programs like gedit or
  LibreOffice can write in the usb stick drive just fine.
  
  It is not a problem with the USB stick, as shown here:
  
  [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd
  [ 6232.426378] scsi8 : usb-storage 2-1:1.0
  [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP 
PQ: 0 ANSI: 0 CCS
  [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0
  [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 
GB/1.86 GiB)
  [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off
  [ 6234.178740] sd 8:0:0:0: 

[Bug 703697] Re: Rhythmbox fails to recognize all unicode characters

2011-07-08 Thread Sergio B
Sorry this bug is outdated and it wasn't reported correctly.

What happens is this:

The files I mentioned in this bug had two ID3 tag frames (I didn't know
that Mp3 files could have more than one ID3 tag frame) and what happened
with Rhythmbox is that it was reading the first (or last I don't know
for sure) frame it found while other players like Amarok, Winamp and the
music tagger Cowbell were doing the opposite thing.

I used Winamp to remove one of the ID3 Tag Frames and  the frame with
the incorrectly encoded characters emerged, then i re-tagged the files
and the incident never happened again (Because now the files only have
on ID3 tag frame).

So this wasn't a bug after all it is just that Rhythmbox doesn't behave
like other players do when reading the ID3 Tag information. Banshee was
also showing this behavior and i thought that Banshee and Rhythmbox
might be sharing the same ID3 tag library or something.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/703697

Title:
  Rhythmbox fails to recognize all unicode characters

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/703697/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 703697] [NEW] Rhythmbox fails to recognize all unicode characters

2011-01-16 Thread Sergio B
Public bug reported:

Binary package hint: rhythmbox

Bugs similar to this one have been reported a few times but this is not
the same as the other bugs. I have some songs in my music library that
have Japanese characters which are stored in the Id3 tag as unicode
characters and Rhythmbox fails to recognize and properly display them.
Instead of the Japanese character Rhythmbox display a square with some
small numbers inside (which i presume are the characters code) I have
tried to re tag the mp3 files a couple of times but Rhythmbox still
display them wrong. Here's what I have done.

1. I though that it may be a encoding error caused by Winamp so I went back to 
Windows and re-tagged the songs with the Windows Explorer. It didn't solve the 
problem.
2. I though it wold be solved if I re-tagged the songs from within Rhythmbox so 
I re-tagged all songs and they displayed OK in that session. I closed Rhythmbox 
and opened it again and the wrong displayed characters were back in place.
3. I used cowbell to re-tag the songs (although in cowbell the characters were 
properly displayed) and Rhythmbox still displays them wrong.
4. I removed the files from the music library and imported them again. Still 
the characters were not show properly.

I attached a Screenshot of this behavior, from left to right; 1)
Rhytmbox on each start. 2) Rhytmbox after re-tagging the songs with it,
3) Cowbell with the same album loaded.

This might also be related to another bug I noticed when I re-tagged
some other songs. I re-tagged some songs using Rhythmbox and replaced
some romaji for the corresponding Japanese characters and it displayed
well for that session when i restarted Rhytmbox it displayed the songs
with romaji again but if I open the songs with cowbell it shows me the
Japanese characters I put in tags with Rhytmbox this looks to me that
Rhythmbox doesn't refresh the songs tags when it starts but instead it
just keep the tags it had in it's database which is undesirable.

I hope this get fixed soon.

Ubuntu 10.10
Rhythmbox 0.13.1-0ubuntu6

** Affects: rhythmbox (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in ubuntu.
https://bugs.launchpad.net/bugs/703697

Title:
  Rhythmbox fails to recognize all unicode characters

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 703697] Re: Rhythmbox fails to recognize all unicode characters

2011-01-16 Thread Sergio B

** Attachment added: screenshot.jpg
   
https://bugs.launchpad.net/bugs/703697/+attachment/1796076/+files/screenshot.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in ubuntu.
https://bugs.launchpad.net/bugs/703697

Title:
  Rhythmbox fails to recognize all unicode characters

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs