[Desktop-packages] [Bug 1931907] Re: Spacebar in Incremental search in open-file dialog doesn't work

[edgarswooth]

This might need to be moved to some Gnome or gnome-shell tracker
instead. Let me know, and I'll copy it there.

-- 
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/1931907

Title:
  Spacebar in Incremental search in open-file dialog doesn't work

Status in nautilus package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  
  Stimulate the Nautilus "open-file" dialog to appear somehow. (Say, by Ctrl+O 
in Firefox on Ubuntu 20.04.
  Click the "search" icon (a magnifying glass at top right), or just start 
typing.
  Begin to type a search in the search box that appears.

  Reproducible in:
  "Files" 3.36.3-stable on Ubuntu 20.04

  Current behavior
  There's a race condition, where, if you're faster than the search, you can 
type something including a space. However, if you type slowly, as soon as you 
hit space, the first result will be opened.

  (Note, this incremental search was buggy in a different way back in
  v3.26.4 on Ubuntu 18.04, when I reported this upstream, was told to
  take it downstream, and then had to go back to doing real work. See
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/936#note_454231 )

  Expected behavior
  The incremental search will continue as we type in the search box, without 
any focus-stealing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1931907/+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 1931907] [NEW] Spacebar in Incremental search in open-file dialog doesn't work

[edgarswooth]

Public bug reported:

Steps to reproduce


Stimulate the Nautilus "open-file" dialog to appear somehow. (Say, by Ctrl+O in 
Firefox on Ubuntu 20.04.
Click the "search" icon (a magnifying glass at top right), or just start typing.
Begin to type a search in the search box that appears.

Reproducible in:
"Files" 3.36.3-stable on Ubuntu 20.04

Current behavior
There's a race condition, where, if you're faster than the search, you can type 
something including a space. However, if you type slowly, as soon as you hit 
space, the first result will be opened.

(Note, this incremental search was buggy in a different way back in
v3.26.4 on Ubuntu 18.04, when I reported this upstream, was told to take
it downstream, and then had to go back to doing real work. See
https://gitlab.gnome.org/GNOME/nautilus/-/issues/936#note_454231 )

Expected behavior
The incremental search will continue as we type in the search box, without any 
focus-stealing.

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

-- 
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/1931907

Title:
  Spacebar in Incremental search in open-file dialog doesn't work

Status in nautilus package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  
  Stimulate the Nautilus "open-file" dialog to appear somehow. (Say, by Ctrl+O 
in Firefox on Ubuntu 20.04.
  Click the "search" icon (a magnifying glass at top right), or just start 
typing.
  Begin to type a search in the search box that appears.

  Reproducible in:
  "Files" 3.36.3-stable on Ubuntu 20.04

  Current behavior
  There's a race condition, where, if you're faster than the search, you can 
type something including a space. However, if you type slowly, as soon as you 
hit space, the first result will be opened.

  (Note, this incremental search was buggy in a different way back in
  v3.26.4 on Ubuntu 18.04, when I reported this upstream, was told to
  take it downstream, and then had to go back to doing real work. See
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/936#note_454231 )

  Expected behavior
  The incremental search will continue as we type in the search box, without 
any focus-stealing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1931907/+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 1864244] [NEW] Text selection in address bar does not work as expected

[edgarswooth]

Public bug reported:

In Nautilus, I can click "Ctrl+L" to open the address bar. At this
point, the whole address will be selected, which is desirable. However,
if I then press "Right" to place my cursor at the end of the current
path, and then try to use "Shift+Ctrl+Left" to select word-by-word
(e.g., to select and delete the final folder from the path), the whole
path is again selected. It seems that the logic for preselecting the
whole path upon opening the address bar seems to trigger in more
circumstances than just upon opening, and this makes using Nautilus via
keyboard slower and more frictive than necessary. (In general, text
entry widgets that override the operating system's existing conventions
always really annoy me, on desktop or mobile.)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.4-0~ubuntu18.04.5
ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
Uname: Linux 4.15.0-76-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 21 15:44:24 2020
InstallationDate: Installed on 2018-12-17 (431 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LC_CTYPE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: dropbox 2018.11.28

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


** Tags: amd64 apport-bug bionic

-- 
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/1864244

Title:
  Text selection in address bar does not work as expected

Status in nautilus package in Ubuntu:
  New

Bug description:
  In Nautilus, I can click "Ctrl+L" to open the address bar. At this
  point, the whole address will be selected, which is desirable.
  However, if I then press "Right" to place my cursor at the end of the
  current path, and then try to use "Shift+Ctrl+Left" to select word-by-
  word (e.g., to select and delete the final folder from the path), the
  whole path is again selected. It seems that the logic for preselecting
  the whole path upon opening the address bar seems to trigger in more
  circumstances than just upon opening, and this makes using Nautilus
  via keyboard slower and more frictive than necessary. (In general,
  text entry widgets that override the operating system's existing
  conventions always really annoy me, on desktop or mobile.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
  Uname: Linux 4.15.0-76-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 21 15:44:24 2020
  InstallationDate: Installed on 2018-12-17 (431 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: dropbox 2018.11.28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1864244/+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 1710931] Re: Ctrl+N shortcut does not work when desktop has focus

[edgarswooth]

Status is "expired", but this is still here in late 2019 on Ubuntu
18.04.3 LTS. A behavioral work-around for me is to use Super+# to open
the (pinned) Nautilus from the dock ... then use Ctrl+l to get to
wherever I *really* want to go.

But it's definitely a bug: as Marc Nijdam said, it's obviously due to
some invalid `x-nautilus-desktop:///` argument which is passed to the
Nautilus invocation. I don't know where in the labyrinth of
Ubuntu/Nautilus/Debian/Gnome repositories this argument arises, but it
would seem that a simple fix, valid for most users, would be simply to
hard-code `$USER/Desktop\` instead. This would at least be better than
the current state of affairs, which works for no one.

-- 
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/1710931

Title:
  Ctrl+N shortcut does not work when desktop has focus

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  When a Nautilus window is open, Ctrl+N opens a new window that shows
  the same folder as the focused Nautilus window.

  However, when the desktop is focused, the shortcut doesn't work -
  instead I see an error that x-nautilus-desktop:// is not supported.

  This functionality was previously reported as working in #307229.

  This is on Ubuntu 17.10 Artful Aardvark (fully patched as of today)
  with GNOME Files 3.24.2.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1710931/+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 1838081] [NEW] Local printers crowd out installed printers in list

[edgarswooth]

Public bug reported:

In Ubuntu 18.04, the list of printers show in the control center seems
to include everything which is visible by Bonjour or some other
discovery service on the local network; there is no visual distinction
made between "installed" printers and available ones (this is also true
of print dialogs, but that's another issue).

For networks with many shared printers (many of which seem to be the
result of Apple sharing attached printers by default; see screenshot),
this results in an overwhelming flood of listed printers, which, worse,
is constantly shifting and jumping around as network state changes. This
makes it difficult to find previously installed printers in the list.

My suggestion would be to make a distinction in the UI between installed
and available printers (and perhaps also to have a listing that uses
less vertical space per discovered printer).

Really,system-config-printer CUPS window which is brought up by the
"Additional Printer Settings" button at the bottom is far more
functional, and in fact was the *only* way that I was able to add a new
printer via address alone.

Description:Ubuntu 18.04.2 LTS
Release:18.04


gnome-control-center:
  Installed: 1:3.28.2-0ubuntu0.18.04.4
  Candidate: 1:3.28.2-0ubuntu0.18.04.4
  Version table:
 *** 1:3.28.2-0ubuntu0.18.04.4 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.28.1-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 26 13:52:06 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-12-17 (221 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LC_CTYPE=en_US.UTF-8
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages

** Attachment added: "Screenshot from 2019-07-26 13-55-11.png"
   
https://bugs.launchpad.net/bugs/1838081/+attachment/5279488/+files/Screenshot%20from%202019-07-26%2013-55-11.png

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

Title:
  Local printers crowd out installed printers in list

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04, the list of printers show in the control center seems
  to include everything which is visible by Bonjour or some other
  discovery service on the local network; there is no visual distinction
  made between "installed" printers and available ones (this is also
  true of print dialogs, but that's another issue).

  For networks with many shared printers (many of which seem to be the
  result of Apple sharing attached printers by default; see screenshot),
  this results in an overwhelming flood of listed printers, which,
  worse, is constantly shifting and jumping around as network state
  changes. This makes it difficult to find previously installed printers
  in the list.

  My suggestion would be to make a distinction in the UI between
  installed and available printers (and perhaps also to have a listing
  that uses less vertical space per discovered printer).

  Really,system-config-printer CUPS window which is brought up by the
  "Additional Printer Settings" button at the bottom is far more
  functional, and in fact was the *only* way that I was able to add a
  new printer via address alone.

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 26 13:52:06 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-12-17 (221 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 

[Desktop-packages] [Bug 1562342] Re: unity-control-center crashed with SIGSEGV in gtk_widget_get_scale_factor()

[edgarswooth]

*** This bug is a duplicate of bug 1544819 ***
https://bugs.launchpad.net/bugs/1544819

This happened to me sometime after upgrading from, I think, 14.04 to
16.04. I'm not sure if that caused it, however, as I didn't notice until
sometime later, when I tried to change my microphone settings.

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

Title:
  unity-control-center crashed with SIGSEGV in
  gtk_widget_get_scale_factor()

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 beta2

  Change theme from radiance to ambiance. And now unity-control-center
  dont work.

  
  ubuntu@ubuntu:~$ unity-control-center 

  (unity-control-center:4621): GLib-CRITICAL **: g_strsplit: assertion 'string 
!= NULL' failed
  Ошибка сегментирования (сделан дамп памяти)

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.368
  CurrentDesktop: Unity
  Date: Sat Mar 26 22:52:01 2016
  ExecutablePath: /usr/bin/unity-control-center
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcCmdline: unity-control-center datetime
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7ff0603ddf57 :  
mov0xc0(%rdx),%rax
   PC (0x7ff0603ddf57) ok
   source "0xc0(%rdx)" (0x00c0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   gtk_widget_get_scale_factor () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-control-center crashed with SIGSEGV in 
gtk_widget_get_scale_factor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1562342/+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