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

2017-05-06 Thread lediableboiteux
P.S. “killall nautilus” and restarting it resolved the issue.

-- 
You received this bug notification because you are a member of Desktop
Packages, 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

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed

Bug description:
  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.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


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

2017-05-06 Thread lediableboiteux
Wow, it seems to be still present. Just experienced it on 16.10. This is
weird, because this bug was driving me nuts on 15.10, and now this was
first occurrence since I upgraded from 15.10 to 16.10, which was half a
year ago.

-- 
You received this bug notification because you are a member of Desktop
Packages, 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

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed

Bug description:
  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.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 666418] Re: gnome-terminal.wrapper doesn't wait until program finishes

2017-01-06 Thread lediableboiteux
Still happens in yakkety.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/666418

Title:
  gnome-terminal.wrapper doesn't wait until program finishes

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-terminal

  "gnome-terminal -e some_program"
  usually (if another gnome-terminal is already running) returns immediately; 
most other terminal emulators (e.g. xterm) return only after the program 
finishes, which is much more convenient when opening programs in a terminal 
from scripts.
  "gnome-terminal --disable-factory -e some_program"
  does wait, which solves the issue - unless you're writing a portable script 
and use
  "x-terminal-emulator -e some_program"
  where you'll get different behavior depending on the alternative selected for 
x-terminal-emulator.
  And you can't use "x-terminal-emulator --disable-factory -e some_program" 
because xterm etc. will barf on it.

  IMHO, gnome-terminal itself should always wait for the command to return.
  But defaulting to no-factory mode would lose all benefits for which the 
factory was created;
  waiting for completion notification from the factory would solve it better 
but I have no idea if it's easy to implement.

  An easier solution is to always add --disable-factory in 
gnome-terminal.wrapper.
  This would keep the behavior of "gnome-terminal" but unify the behavior of 
"x-terminal-emulator".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/666418/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 591103] Re: chosing open files can hang system-monitor

2014-01-26 Thread lediableboiteux
Tell what missing information you need and I'm all yours, because this
is still present in 13.10 amd64 (and is annoying). I tried opening Show
open files for some processes; monitor hangs on Transmission and
Firefox with ~200 tabs, partially on Dropbox (by partially I mean it
hangs for a while -- main window goes gray -- then Open files window
is refreshed, processess input (like srolling; main window goes normal),
but is irresponsive and immediately freezes again; loop.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/591103

Title:
  chosing open files can hang system-monitor

Status in “gnome-system-monitor” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-system-monitor

  In the processes tab it is possible to show the files a process has
  open. Sometimes this freezes the system monitor. So far I've only been
  able to find that it alway's hangs with transmission, even when its
  not active and has only 32 fd's open. On the other hand, firefox-bin
  with over 80 fd's doesn't hang system-monitor.

  To reproduce: Start transmission, start gnome-system-monitory, go the
  the processes tab, choose show open files for Transmission and
  observe the hang.

  
  Note: I am aware of another bug rapport similar to this, regarding skype. 
This one seems to be closed due to a lack of information, and it is also more 
than 3 years old, so I opened a new rapport.

  I'll be happy to provide any additional information needed

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-system-monitor 2.28.0-1ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Tue Jun  8 08:11:58 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
  ProcEnviron:
   LANGUAGE=nl_NL:en
   LANG=nl_NL.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-system-monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/591103/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 894591] [NEW] Typeahead functionality involving mouse scroll is broken

2011-11-24 Thread lediableboiteux
Public bug reported:

Description:Ubuntu 11.10
Release:11.10

nautilus:
  Installed: 1:3.2.1-0ubuntu3.1
  Candidate: 1:3.2.1-0ubuntu3.1

Expected behaviour:
- Open the directory that contains files with names starting with a similar 
character/string in nautilus. Example: abc, file1, file2, file3, xyz.
- To select “file3” using typeahead you can either type explicit, unequivocal 
string (“file3” in this case, as the digit distinguishes file in this 
directory) or type common part and USE SCROLL TO NAVIGATE THROUGH THE RESULTS 
(in this case, e.g. “f”, which makes you able to scroll from “file1” to 
“file3”; “abc” and “xyz” are excluded as they don’t match) -- each scroll down 
selects next available item, each scroll up selects every previous item; I do 
not know how to say it more clearly.

Actual behaviour:
- Open the directory that contains files with names starting with a similar 
character/string in nautilus. Example: abc, file1, file2, file3, xyz.
- Type in “f”.
- Scrolling through the results doesn’t work UNLESS you place mouse pointer 
over the typeahead box. This is not very useful as this box is small and 
located in a corner.

I remember the abovementioned expected behaviour to be an actual
behaviour of 9.10 and classic GNOME, from which I turned to oneiric few
weeks ago.

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

** Description changed:

  Description:  Ubuntu 11.10
  Release:  11.10
  
  nautilus:
-   Installed: 1:3.2.1-0ubuntu3.1
-   Candidate: 1:3.2.1-0ubuntu3.1
+   Installed: 1:3.2.1-0ubuntu3.1
+   Candidate: 1:3.2.1-0ubuntu3.1
  
  Expected behaviour:
  - Open the directory that contains files with names starting with a similar 
character/string in nautilus. Example: abc, file1, file2, file3, xyz.
- - To select “file3” using typeahead you can either type explicit, unequivocal 
string (“file3” in this case, as the digit distinguishes file in this 
directory) or type common part and USE SCROLL TO NAVIGATE THROUGH THE RESULTS 
(in this case, e.g. “f”, which makes you able to scroll from “file1” to 
“file3”; “abc” and “xyz” are excluded as they don’t match ) -- each scroll down 
selects next available item, each scroll up selects every previous item; I do 
not know how to say it more clearly.
+ - To select “file3” using typeahead you can either type explicit, unequivocal 
string (“file3” in this case, as the digit distinguishes file in this 
directory) or type common part and USE SCROLL TO NAVIGATE THROUGH THE RESULTS 
(in this case, e.g. “f”, which makes you able to scroll from “file1” to 
“file3”; “abc” and “xyz” are excluded as they don’t match) -- each scroll down 
selects next available item, each scroll up selects every previous item; I do 
not know how to say it more clearly.
  
  Actual behaviour:
  - Open the directory that contains files with names starting with a similar 
character/string in nautilus. Example: abc, file1, file2, file3, xyz.
  - Type in “f”.
  - Scrolling through the results doesn’t work UNLESS you place mouse pointer 
over the typeahead box. This is not very useful as this box is small and 
located in a corner.
+ 
+ I remember the abovementioned expected behaviour to be an actual
+ behaviour of 9.10 and classic GNOME, from which I turned to oneiric few
+ weeks ago.

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

Title:
  Typeahead functionality involving mouse scroll is broken

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 11.10
  Release:  11.10

  nautilus:
    Installed: 1:3.2.1-0ubuntu3.1
    Candidate: 1:3.2.1-0ubuntu3.1

  Expected behaviour:
  - Open the directory that contains files with names starting with a similar 
character/string in nautilus. Example: abc, file1, file2, file3, xyz.
  - To select “file3” using typeahead you can either type explicit, unequivocal 
string (“file3” in this case, as the digit distinguishes file in this 
directory) or type common part and USE SCROLL TO NAVIGATE THROUGH THE RESULTS 
(in this case, e.g. “f”, which makes you able to scroll from “file1” to 
“file3”; “abc” and “xyz” are excluded as they don’t match) -- each scroll down 
selects next available item, each scroll up selects every previous item; I do 
not know how to say it more clearly.

  Actual behaviour:
  - Open the directory that contains files with names starting with a similar 
character/string in nautilus. Example: abc, file1, file2, file3, xyz.
  - Type in “f”.
  - Scrolling through the results doesn’t work UNLESS you place mouse pointer 
over the typeahead box. This is not very useful as this box is small and 
located in a corner.

  I remember the abovementioned expected behaviour to be an actual
  behaviour of 9.10 and classic GNOME, from which I turned to oneiric
  few weeks ago.

To manage notifications about this bug go to: