[Desktop-packages] [Bug 1970978] [NEW] On Save As dialog, any navigation operation (e.g. change to sub-folder) takes focus away from file name entry and instead switches to search

2022-04-29 Thread Dan Sorak
Public bug reported:

Within "Save As" dialogs from any desktop application, all navigation
operations, specifically the most common one of changing folders,
switches focus away from the file name input, resulting in the search
input box accepting keyboard input instead of the filename input box.
This is extremely frustrating for a several reasons:

1. After navigating to the desired folder, typing the name for the file
is instead captured by the search input box instead of the expected
filename input box

2. The search input box does not even appear until key presses are
received, making it even more surprising that the filename is not being
altered and is instead the beginning of a search

3. Using the mouse to re-focus on the filename input box deselects the
originally selected default file name text, causing the user to have to
re-select everything

4. Re-selecting everything (see previous item) causes the default file
name extension (which is excluded in the initial selection) to also be
selected, requiring the user to think about what it was and to re-enter
that extension as well

5. "Tab" key navigation takes an inordinate number of tab key presses to
return to the filename input box

Sorry to complain about this, but I almost ALWAYS choose to change
folders, and then when I type in the name, I have to re-do all the steps
described above because the search input has invariably captured my key
presses instead of the changing the filename. It is very annoying.

I would like to suggest that the search input box either not be
automatically switched to in the  "Save As" mode of the dialog, or to
have a separate and explicit search input box that does not
automatically receive input after folder navigation operations.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 29 11:06:32 2022
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2021-09-13 (227 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal save-as

** Description changed:

  Within "Save As" dialogs from any desktop application, all navigation
  operations, specifically the most common one of changing folders,
  switches focus away from the file name input, resulting in the search
  input box accepting keyboard input instead of the filename input box.
  This is extremely frustrating for a several reasons:
  
  1. After navigating to the desired folder, typing the name for the file
  is instead captured by the search input box instead of the expected
  filename input box
  
  2. The search input box does not even appear until key presses are
  received, making it even more surprising that the filename is not being
  altered and is instead the beginning of a search
  
  3. Using the mouse to re-focus on the filename input box deselects the
  originally selected default file name text, causing the user to have to
  re-select everything
  
- 4. Re-selecting everything (see #2 above) causes the default file name
+ 4. Re-selecting everything (see #3 above) causes the default file name
  extension (which is excluded in the initial selection) to also be
  selected, requiring the user to think about what it was and to re-enter
  that extension as well
  
  5. "Tab" key navigation takes an inordinate number of tab key presses to
  return to the filename input box
  
  Sorry to complain about this, but I almost ALWAYS choose to change
  folders, and then when I type in the name, I have to re-do all 4 steps
  described above because the search input has invariably captured my key
  presses instead of the changing the filename. It is very annoying.
  
  I would like to suggest that the search input box either not be
  automatically switched to in the  "Save As" mode of the dialog, or to
  have a separate and explicit search input box that does not
  automatically receive input on folder navigation operations.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 11:06:32 2022
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2021-09-13 (227 days ago)

[Desktop-packages] [Bug 1962593] Re: SMB Mount to backup directory prevents mounting parent directories

2022-04-06 Thread Dan Sorak
** Summary changed:

- SMB Mount to backup directory prevents mounting parent directory
+ SMB Mount to backup directory prevents mounting parent directories

** Summary changed:

- SMB Mount to backup directory prevents mounting parent directories
+ SMB Mount to backup directory prevents mounting parent directories of share

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

Title:
  SMB Mount to backup directory prevents mounting parent directories of
  share

Status in Déjà Dup:
  New
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  May also apply to the "duplicity" package and is related to network
  "mount"s:

  To reproduce:
  * Set up a writeable SMB share: smb://1.2.3.4/backup
  * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup
  * Using "deja-dup" -> "Storage location" set:
  Storage location: Network Server
  Network Location: smb://1.2.3.4/backup/UbuntuBackup
  Folder: MyMachineBackup
  * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup")
  * Select "deja-dup" -> "Overview" -> "Back Up Now..."
  * Allow the backup to start, but not finish
  * Go to Nautilus (file browser) -> "+ Other Locations"
    - At the bottom set "Connect to server" to: smb://1.2.3.4/backup

  Result:
  * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the 
"UbuntuBackup" subdir is currently mounted
  * Can happen at semi-random times if the backup is on a schedule
  * This is especially a problem when backing up remotely over a VPN which can 
take a long time
  * Prevents access to all parent folders of the backup folder
  * Nautilus will hang, unable to mount the "backup" parent directory
  * Also a problem if the "smb://1.2.3.4/backup" folder is bookmarked in 
nautilus
  * This problem is persistent throughout backup process and for a period of 
time afterwards until the mount to "UbuntuBackup" times out or the backup 
process exits

  Possible solutions:
  * Add a configuration option to deja-dup/duplicity to specify the "Share 
root" and mount that first before accessing the configured "Network Location"
  * Have deja-dup or duplicity attempt to mount the parent 
directory/directories first by starting at the root of the SMB share and 
walking down the directory tree until a successful mount is made. In the above 
example, start by attempting to mount "smb://1.2.3.4/backup" first and then 
"smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, 
try each one successively)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.7-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 08:51:47 2022
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2021-09-13 (168 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1962593/+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 1962593] Re: SMB Mount to backup directory prevents mounting parent directory

2022-03-01 Thread Dan Sorak
** Also affects: deja-dup
   Importance: Undecided
   Status: New

** Also affects: duplicity
   Importance: Undecided
   Status: New

** Description changed:

  May also apply to the "duplicity" package and is related to network
  "mount"s:
  
  To reproduce:
  * Set up a writeable SMB share: smb://1.2.3.4/backup
  * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup
  * Using "deja-dup" -> "Storage location" set:
- Storage location: Network Server
- Network Location: smb://1.2.3.4/backup/UbuntuBackup
- Folder: MyMachineBackup
+ Storage location: Network Server
+ Network Location: smb://1.2.3.4/backup/UbuntuBackup
+ Folder: MyMachineBackup
  * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup")
  * Select "deja-dup" -> "Overview" -> "Back Up Now..."
  * Allow the backup to start, but not finish
  * Go to Nautilus (file browser) -> "+ Other Locations"
-   - At the bottom set "Connect to server" to: smb://1.2.3.4/backup
+   - At the bottom set "Connect to server" to: smb://1.2.3.4/backup
  
- Result: 
+ Result:
  * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the 
"UbuntuBackup" subdir is currently mounted
- * This causes a hanging problem if the "smb://1.2.3.4/backup" folder is 
bookmarked in nautilus
- * Prevents all access to all parent folders of the backup folder
+ * Can happen at semi-random times if the backup is on a schedule
+ * This is especially a problem when backing up remotely over a VPN which can 
take a long time
+ * Prevents access to all parent folders of the backup folder
  * Nautilus will hang, unable to mount the "backup" parent directory
- * This problem is persistent throughout backup process and for a period of 
time afterwards until the mount to "UbuntuBackup" times out
- * This is especially a problem when backing up remotely over a VPN which can 
take a long time
+ * Also a problem if the "smb://1.2.3.4/backup" folder is bookmarked in 
nautilus
+ * This problem is persistent throughout backup process and for a period of 
time afterwards until the mount to "UbuntuBackup" times out or the backup 
process exits
  
  Possible solutions:
  * Add a configuration option to deja-dup/duplicity to specify the "Share 
root" and mount that first before accessing the configured "Network Location"
  * Have deja-dup or duplicity attempt to mount the parent 
directory/directories first by starting at the root of the SMB share and 
walking down the directory tree until a successful mount is made. In the above 
example, start by attempting to mount "smb://1.2.3.4/backup" first and then 
"smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, 
try each one successively)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.7-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 08:51:47 2022
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2021-09-13 (168 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
-  XDG_RUNTIME_DIR=
-  SHELL=/bin/bash
-  PATH=(custom, user)
-  LANG=en_US.UTF-8
+  XDG_RUNTIME_DIR=
+  SHELL=/bin/bash
+  PATH=(custom, user)
+  LANG=en_US.UTF-8
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  SMB Mount to backup directory prevents mounting parent directory

Status in Déjà Dup:
  New
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  New

Bug description:
  May also apply to the "duplicity" package and is related to network
  "mount"s:

  To reproduce:
  * Set up a writeable SMB share: smb://1.2.3.4/backup
  * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup
  * Using "deja-dup" -> "Storage location" set:
  Storage location: Network Server
  Network Location: smb://1.2.3.4/backup/UbuntuBackup
  Folder: MyMachineBackup
  * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup")
  * Select "deja-dup" -> "Overview" -> "Back Up Now..."
  * Allow the backup to start, but not finish
  * Go to Nautilus (file browser) -> "+ Other Locations"
    - At the bottom set "Connect to server" to: smb://1.2.3.4/backup

  Result:
  * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the 
"UbuntuBackup" subdir is currently mounted
  * Can happen at semi-random times if the backup is on a schedule
  * This is especially a problem when backing up remotely over a VPN which can 
take a long time
  * Prevents access to all parent folders of the backup folder
  * Nautilus will 

[Desktop-packages] [Bug 1962593] Re: SMB Mount to backup directory prevents mounting parent directory

2022-03-01 Thread Dan Sorak
Maybe not a "bug" per se, but definitely an unwanted side-effect of the
network backup process.

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

Title:
  SMB Mount to backup directory prevents mounting parent directory

Status in deja-dup package in Ubuntu:
  New

Bug description:
  May also apply to the "duplicity" package and is related to network
  "mount"s:

  To reproduce:
  * Set up a writeable SMB share: smb://1.2.3.4/backup
  * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup
  * Using "deja-dup" -> "Storage location" set:
  Storage location: Network Server
  Network Location: smb://1.2.3.4/backup/UbuntuBackup
  Folder: MyMachineBackup
  * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup")
  * Select "deja-dup" -> "Overview" -> "Back Up Now..."
  * Allow the backup to start, but not finish
  * Go to Nautilus (file browser) -> "+ Other Locations"
- At the bottom set "Connect to server" to: smb://1.2.3.4/backup

  Result: 
  * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the 
"UbuntuBackup" subdir is currently mounted
  * This causes a hanging problem if the "smb://1.2.3.4/backup" folder is 
bookmarked in nautilus
  * Prevents all access to all parent folders of the backup folder
  * Nautilus will hang, unable to mount the "backup" parent directory
  * This problem is persistent throughout backup process and for a period of 
time afterwards until the mount to "UbuntuBackup" times out
  * This is especially a problem when backing up remotely over a VPN which can 
take a long time

  Possible solutions:
  * Add a configuration option to deja-dup/duplicity to specify the "Share 
root" and mount that first before accessing the configured "Network Location"
  * Have deja-dup or duplicity attempt to mount the parent 
directory/directories first by starting at the root of the SMB share and 
walking down the directory tree until a successful mount is made. In the above 
example, start by attempting to mount "smb://1.2.3.4/backup" first and then 
"smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, 
try each one successively)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.7-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 08:51:47 2022
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2021-09-13 (168 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1962593/+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 1962593] [NEW] SMB Mount to backup directory prevents mounting parent directory

2022-03-01 Thread Dan Sorak
Public bug reported:

May also apply to the "duplicity" package and is related to network
"mount"s:

To reproduce:
* Set up a writeable SMB share: smb://1.2.3.4/backup
* Create a subdir: smb://1.2.3.4/backup/UbuntuBackup
* Using "deja-dup" -> "Storage location" set:
Storage location: Network Server
Network Location: smb://1.2.3.4/backup/UbuntuBackup
Folder: MyMachineBackup
* REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup")
* Select "deja-dup" -> "Overview" -> "Back Up Now..."
* Allow the backup to start, but not finish
* Go to Nautilus (file browser) -> "+ Other Locations"
  - At the bottom set "Connect to server" to: smb://1.2.3.4/backup

Result: 
* The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the 
"UbuntuBackup" subdir is currently mounted
* This causes a hanging problem if the "smb://1.2.3.4/backup" folder is 
bookmarked in nautilus
* Prevents all access to all parent folders of the backup folder
* Nautilus will hang, unable to mount the "backup" parent directory
* This problem is persistent throughout backup process and for a period of time 
afterwards until the mount to "UbuntuBackup" times out
* This is especially a problem when backing up remotely over a VPN which can 
take a long time

Possible solutions:
* Add a configuration option to deja-dup/duplicity to specify the "Share root" 
and mount that first before accessing the configured "Network Location"
* Have deja-dup or duplicity attempt to mount the parent directory/directories 
first by starting at the root of the SMB share and walking down the directory 
tree until a successful mount is made. In the above example, start by 
attempting to mount "smb://1.2.3.4/backup" first and then 
"smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, 
try each one successively)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: deja-dup 40.7-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  1 08:51:47 2022
ExecutablePath: /usr/bin/deja-dup
InstallationDate: Installed on 2021-09-13 (168 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug backup focal network smb

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

Title:
  SMB Mount to backup directory prevents mounting parent directory

Status in deja-dup package in Ubuntu:
  New

Bug description:
  May also apply to the "duplicity" package and is related to network
  "mount"s:

  To reproduce:
  * Set up a writeable SMB share: smb://1.2.3.4/backup
  * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup
  * Using "deja-dup" -> "Storage location" set:
  Storage location: Network Server
  Network Location: smb://1.2.3.4/backup/UbuntuBackup
  Folder: MyMachineBackup
  * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup")
  * Select "deja-dup" -> "Overview" -> "Back Up Now..."
  * Allow the backup to start, but not finish
  * Go to Nautilus (file browser) -> "+ Other Locations"
- At the bottom set "Connect to server" to: smb://1.2.3.4/backup

  Result: 
  * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the 
"UbuntuBackup" subdir is currently mounted
  * This causes a hanging problem if the "smb://1.2.3.4/backup" folder is 
bookmarked in nautilus
  * Prevents all access to all parent folders of the backup folder
  * Nautilus will hang, unable to mount the "backup" parent directory
  * This problem is persistent throughout backup process and for a period of 
time afterwards until the mount to "UbuntuBackup" times out
  * This is especially a problem when backing up remotely over a VPN which can 
take a long time

  Possible solutions:
  * Add a configuration option to deja-dup/duplicity to specify the "Share 
root" and mount that first before accessing the configured "Network Location"
  * Have deja-dup or duplicity attempt to mount the parent 
directory/directories first by starting at the root of the SMB share and 
walking down the directory tree until a successful mount is made. In the above 
example, start by attempting to mount "smb://1.2.3.4/backup" first and then 
"smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, 
try each one successively)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.7-0ubuntu1
  ProcVersionSignature: Ubuntu