[Desktop-packages] [Bug 1755538] Re: Invisible mouse cursor on login screen

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mutter (Ubuntu)
   Status: New => Confirmed

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

Title:
  Invisible mouse cursor on login screen

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/68

  ---

  Frequently, but not always, the mouse cursor is invisible in the login
  screen. I can move it, as when passing over a button it lights up, but
  I can't see where the cursor is.

  Once on the desktop, the problems are gone.

  I am running Ubuntu 18.04 dev on a Dell XPS 9360 FHD.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Tue Mar 13 10:30:38 2018
  InstallationDate: Installed on 2018-02-23 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755538/+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 1755538] Re: Invisible mouse cursor on login screen

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gdm3 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Invisible mouse cursor on login screen

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/68

  ---

  Frequently, but not always, the mouse cursor is invisible in the login
  screen. I can move it, as when passing over a button it lights up, but
  I can't see where the cursor is.

  Once on the desktop, the problems are gone.

  I am running Ubuntu 18.04 dev on a Dell XPS 9360 FHD.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Tue Mar 13 10:30:38 2018
  InstallationDate: Installed on 2018-02-23 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755538/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Rohan Paul]

Pin 0x13 does not work as well. Overriding pin 0x13 to use the Internal
Mic causes an undesirable side-effect of static noise in any plugged in
headphone.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Hui Wang]

Probably on this machine, the internal mic is connected to pin 0x13.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1840557] Re: Battery indicator at 66% show full icon on 19.04

[Daniel van Vugt]

Could you please also tell us the laptop model and run:

  dmesg > dmesg.txt

and attach the file 'dmesg.txt' here?

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  Battery indicator at 66% show full icon on 19.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator at 66% show a full battery icon on 19.04
  At about 55%ish he started to show a different icon (about 80% full icon)
  Rebooting system did not help.
  Updating system did not help.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-08-05 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Tags:  disco
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+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 1840557] Re: Battery indicator at 66% show full icon on 19.04

[Daniel van Vugt]

> I was not able to catch executable name using crosshairs: WM_CLASS:
not found

The executable name is 'gnome-shell' :)

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

Title:
  Battery indicator at 66% show full icon on 19.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator at 66% show a full battery icon on 19.04
  At about 55%ish he started to show a different icon (about 80% full icon)
  Rebooting system did not help.
  Updating system did not help.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-08-05 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Tags:  disco
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+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 1812883] Re: Desktop view flashes every time ~/Desktop changes

[Daniel van Vugt]

Thanks for pointing out that test. I will remember to suggest it to
people in future in other CPU-related bugs.

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

Title:
  Desktop view flashes every time ~/Desktop changes

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
  All of the icons on my desktop visibly flash every time I change
  anything in the folder ~/Desktop, even if the change is not something
  that is visible on my desktop.

  For example, "touch ~/Desktop/.#foo".

  I mean, the icons that haven't changed should never flash at all, even
  if a change is made that _does_ affect the visible display -- only the
  things that are actually new or different should change their
  appearance, and everything else should remain the same and not flash.
  But at the very least, there should be no flash when there are no
  visible changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 11:38:30 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+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 1840725] [NEW] Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Rohan Paul]

Public bug reported:

Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
spectre-x360-convertible-15 laptop. The microphone works perfectly on
Windows 10 (present in Dual boot mode).

Initially, Internal Microphone was not even detected but installing
alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed
that issue. [Pin 0x13 does not work and causes static in a headphone if
it is plugged in.]

Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

alsa-info:
http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

arecord -l
 List of CAPTURE Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: alsa internal-mic ubuntu18.04.4lts

** Tags added: internal mic

** Tags added: alsa ubuntu18.04.4lts

** Tags removed: internal mic
** Tags added: internal-mic

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1799974] Re: [MIR] gupnp

[Chris Coulson]

I reviewed gupnp 1.2.1-1 as checked in to eoan. This isn't a full
security audit, but rather a quick gauge of maintainability.

- gupnp is a gobject based library for implementing and consuming UPnP 
services, and is required by Rygel.
- It's part of the GNOME project.
- It's written in C.
- One CVE in our database from 2009 (a DoS). Doesn't affect current releases, 
although it doesn't look like it was fixed in Ubuntu before the affected 
releases went EoL.
- Build-dependencies in main except for libgssdp-doc and libgssdp-1.2-dev (bug 
1799977). Also gnome-pkg-tools, meson, valac, gtk-doc-tools, docbook-xml, 
docbook-xsl - none of these create binary dependencies.

- No maintainer scripts
- No init scripts / systemd units.
- No dbus services.
- No setuid binaries.
- Only binary is gupnp-binding-tool-1.2 in libgupnp-1.2-dev
- No sudo fragments.
- No udev rules.
- There's a few tests that seem to run in the build.
- No cron jobs.
- Build logs clean other than some documentation warnings.
- Lintian clean

- Doesn't spawn any subprocesses.
- Memory management looks ok - there is a g_malloc in strip_camel_case that 
allocates memory based on a multiplication that isn't overflow safe, but the 
source of this isn't attacker controlled and I don't think it can overflow 
anyway.
- The only file IO it seems to do is using glib's GMappedFile API, which is 
used for providing file contents to libsoup for hosting local files. See below 
for how paths are looked up.
- Not much logging - a few g_debugs (not enabled by default) and some g_message 
calls. It doesn't look like anything sensitive is logged.
- Reads a couple of variables from the environment - GUPNP_DEBUG and 
GUPNP_DEBUG_NETLINK. The first one enables logging to stdout of headers + 
request/response bodies in libsoup, and enables reporting of warnings and 
errors in libxml when loading local XML files. The second one enables the 
dumping of netlink packets to stdout.
- Doesn't call any privileged commands.
- No crypto.
- Doesn't use temporary files.

- GUPnPContext creates a HTTP server using libsoup. There is one GUPnPContext 
per network interface, created and managed by GUPnPContextManager. The 
availability of services is advertised via SSDP (using gssdp - GUPnPContext 
sub-classes GSSDPClient for this)
  - The default handler just returns 404.
  - It provides a simple API for hosting local paths for read access. The 
default libsoup handler (host_path_handler) for this supports directory listing 
and automatic redirection to index.html for paths to directories. This API is 
used by root device instances to host device and service XML descriptions.
  - host_path_handler() uses construct_local_path() to build a local file path, 
which just appends the request path to the handler's base path. It's relying on 
a feature of libsoup to not be vulnerable to path traversal attacks, which I've 
tested and seems to work.
  - GUPnPContext provides a mechanism to register handler functions for 
specific server paths, which is used by service instances to implement action 
handlers. I believe rygel also uses this for hosting media files.
  - It provides a mechanism for applications to implement ACLs by registering 
an ACL handler, which is called before server handler functions are executed. 
The ACL handler can make access control decisions based on source IP / source 
user agent and request path.
  - The 2 handlers registered by each service instance can be protected with 
ACLs.
  - The control handler function for each service instance 
(control_server_handler) parses the HTTP body with xmlRecoverMemory. This 
doesn't perform replacement of entity references with content by default, which 
is good. It converts requests to gobject signals which are delivered to 
application code, or returns a 401 if the request doesn't have a corresponding 
gobject signal handler.
  - A service instance provides a way for clients to subscribe to events (via 
subscription_server_handler). A subscription is referenced by a SID, which is a 
uuid created by uuid_generate(). The SID is used in order to unsubscibe and 
provided in the event notification headers. Subscriptions timeout and are 
automatically removed after 5 minutes, unless the client resubscribes with the 
same SID.
  - The subscribe() handler calls gupnp_context_rewrite_url() on each callback 
URL, which are provided by the requesting client device. This function extracts 
the host from the URL, constructs a GInetAddress instance by calling 
g_inet_address_new_from_string() with this host string and then calls 
g_inet_address_get_is_link_local() without any null check. Won't 
g_inet_address_new_from_string() fail if the host isn't a valid IPV4 or IPV6 
address though?

- The default GUPnPContextManager implementation uses NETLINK_ROUTE for
observing network interface changes to manage GUPnPContext instances.
There is a network manager implementation, but it doesn't look like it's
built.

- No webkit.
- No policykit.
- 

[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

[SunBear]

I discovered that the Software & Updates application "Authentication"
tab's "Remove" button does not work properly too. After pressing the
"Remove" button, pkexec was called. After submitting the password for
administration level, nothing happens, i.e. Trusted software keys that
was selected for deletion do not get removed. Not error was shown in
terminal.

$ dpkg -l | grep software-properties
ii  python3-software-properties0.96.24.32.11
all  manage the repositories that you install software from
ii  software-properties-common 0.96.24.32.11
all  manage the repositories that you install software from 
(common)
ii  software-properties-gtk0.96.24.32.11
all  manage the repositories that you install software from 
(gtk)

I had filed a bug report (see https://bugs.launchpad.net/ubuntu/+source
/software-properties/+bug/1840624). Should it fall under this bug report
too and this bug report's title be amended to include the
"Authentication" Tab?

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1840064] Re: need to click shortcut twice to switch input method on Firefox

[Marcus Tomlinson]

Removing LibreOffice from here as it has been reported separately as:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1840693

** No longer affects: libreoffice (Ubuntu)

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

Title:
  need to click shortcut twice to switch input method on Firefox

Status in firefox package in Ubuntu:
  New
Status in gcin package in Ubuntu:
  New

Bug description:
  After recent update, now I need to click my input-method-switching
  shortcut twice "fast", basically press Ctrl and hit space twice fast,
  so I can switch input method in Firefox. I am using gcin. Also now I
  can't switch input method in LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 68.0.1+build1-0ubuntu0.18.04.1
  Uname: Linux 5.2.5-050205-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yenyung_chang   1797 F pulseaudio
  BuildID: 20190718161435
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 13 10:29:04 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-03-26 (140 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 131.215.195.254 dev enx00e04c680c21 proto dhcp metric 100 
   default via 10.6.41.254 dev wlp2s0 proto dhcp metric 600 
   10.6.40.0/23 dev wlp2s0 proto kernel scope link src 10.6.41.210 metric 600 
   131.215.195.0/24 dev enx00e04c680c21 proto kernel scope link src 
131.215.195.209 metric 100 
   169.254.0.0/16 dev enx00e04c680c21 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1141
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=68.0.1/20190718161435 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd06/03/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.

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

Re: [Desktop-packages] [Bug 1812883] Re: Desktop view flashes every time ~/Desktop changes

[Roger James]

Hi Jonathon,

Sorry, I wasn't clear. I really only meant the uninstall as a temporary 
test, to provide more information on what issues this extension was 
causing. For me it also solved a number of seemingly unrelated issues 
mostly to do with excessive cpu usage.

Roger

On 19 August 2019 20:35:40 Jonathan Kamens 
wrote:

> I hardly think enough research into this has been done for it to be
> obvious that this is a duplicate.
>
>
> There are literally eight app indicator icons in my system tray right
> now that disappear when I uninstall gnome-shell-extension-appindicator
> (Synology Drive, Google Hangouts, Google Chrome, Dropbox, Yubico
> Authenticator, Slack, Zoom, Flameshot), and I use them all the time.
> Uninstalling that extension simply is not an option.
>
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1812883
>
>
> Title:
>  Desktop view flashes every time ~/Desktop changes
>
>
> Status in gnome-shell-extension-desktop-icons:
>  New
> Status in gnome-shell-extension-desktop-icons package in Ubuntu:
>  Triaged
>
>
> Bug description:
>  All of the icons on my desktop visibly flash every time I change
>  anything in the folder ~/Desktop, even if the change is not something
>  that is visible on my desktop.
>
>
>  For example, "touch ~/Desktop/.#foo".
>
>
>  I mean, the icons that haven't changed should never flash at all, even
>  if a change is made that _does_ affect the visible display -- only the
>  things that are actually new or different should change their
>  appearance, and everything else should remain the same and not flash.
>  But at the very least, there should be no flash when there are no
>  visible changes.
>
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 19.04
>  Package: nautilus 1:3.30.5-1ubuntu1
>  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
>  Uname: Linux 4.18.0-13-generic x86_64
>  NonfreeKernelModules: nvidia_modeset nvidia
>  ApportVersion: 2.20.10-0ubuntu19
>  Architecture: amd64
>  CurrentDesktop: ubuntu:GNOME
>  Date: Tue Jan 22 11:38:30 2019
>  InstallationDate: Installed on 2019-01-02 (20 days ago)
>  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
>  (20181017.3)
>  SourcePackage: nautilus
>  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)
>
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+subscriptions

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

Title:
  Desktop view flashes every time ~/Desktop changes

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
  All of the icons on my desktop visibly flash every time I change
  anything in the folder ~/Desktop, even if the change is not something
  that is visible on my desktop.

  For example, "touch ~/Desktop/.#foo".

  I mean, the icons that haven't changed should never flash at all, even
  if a change is made that _does_ affect the visible display -- only the
  things that are actually new or different should change their
  appearance, and everything else should remain the same and not flash.
  But at the very least, there should be no flash when there are no
  visible changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 11:38:30 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+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 1840693] Re: [snap] Can't change input method (English->gcin Chinese) in LibreOffice

[Marcus Tomlinson]

** Summary changed:

- Can't change input method (English->gcin Chinese) in LibreOffice
+ [snap] Can't change input method (English->gcin Chinese) in LibreOffice

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

Title:
  [snap] Can't change input method (English->gcin Chinese) in
  LibreOffice

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Hi,

  I can't change input method (English->gcin Chinese) in LibreOffice.
  I'm on LibreOffice 6.3. I have tried using hotkey and clicking on
  icons to change, neither worked. One separated but possibly relevant
  issue I am also having now: Over the past year, there's been a few
  times when I updated, Firefox would also have trouble changing input
  method, but instead of completely unable to change, I found out I
  could still change input method by hitting the hotkey "twice" & "fast"
  (slowly wouldn't work). Also for some(?) browser-based program like
  Jupyter Notebook, Alt would trigger browser behaviour first and
  ignored Jupyter's Alt function. I didn't realize so also couldn't
  confirm this is completely correlated with my LibreOffice input
  switching issue, but I figure it might still be some clue. Thank you.

  - Yen-Yung

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  Uname: Linux 5.2.5-050205-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 19 09:47:26 2019
  InstallationDate: Installed on 2019-03-26 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1840693/+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 1840699] Re: Caps-lock doesn't work correctly in Old Hungarian layout

[Gunnar Hjalmarsson]

Let's fix this one way or the other. Either an upgrade to 2.27, if that
happens in Debian, or we could cherry pick the upstream commit which
fixes it.

** Bug watch added: 
gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues #154
   https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/154

** Also affects: xkeyboard-config via
   https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/154
   Importance: Unknown
   Status: Unknown

** Changed in: xkeyboard-config (Ubuntu)
   Importance: Undecided => Medium

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Triaged

** Changed in: xkeyboard-config (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Caps-lock doesn't work correctly in Old Hungarian layout

Status in xkeyboard-config:
  Unknown
Status in xkeyboard-config package in Ubuntu:
  Triaged

Bug description:
  Xkeyboard-config's version 2.27 resolves this problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1840699/+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 218637] Re: Non-breaking space is easy to write accidentally and impossible to distinguish from regular space.

[Jarno Suni]

** Description changed:

  OS: from Hardy to at least Trusty.
  
  When you use Finnish keyboard, you have to hold Alt Gr down to type | or
  \ or certain other characters. When typing a shell command, you may
  often want to enter a space character after such characters. But it
  easily happens that Alt Gr is still down when you press space, and
  consequently you type non-breaking space character U+00A0 (at least, if
  you use UTF-8 keyboard layout, which is default in Ubuntu).
  
  $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar"
  ls: cannot access foo bar: No such file or directory
  $cat foo bar | grep 0
  No command ' grep' found, but there are 16 similar ones
   grep: command not found
  
  Besides it may be hard to see the typing error, as non-breaking space
  character looks exactly same as regular space character.
  
  A way to avoid such typos would be to use another keyboard shortcut for
  non-breaking space. Besides non-breaking space should look different
  than regular space in terminal emulators and in editors.
  
  A workaround in to run
  setxkbmap -option "nbsp:none"
- to make  type regular space character,
- and use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking space 
in scripts and in command line.
+ to make  type regular space character. To make this default 
setting, you could add 
+ 
+ XKBOPTIONS="nbsp:none"
+ 
+ in '/etc/default/keyboard'.
+ 
+ Then use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking
+ space in scripts and in command line.
  
  Non-breaking space can be typed (in GTK apps) by u 00a0, 
if needed, but it looks exactly like a regular space.
  For me,  would be a good shortcut for non-breaking space.

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

Title:
  Non-breaking space is easy to write accidentally and impossible to
  distinguish from regular space.

Status in Geany:
  New
Status in gedit:
  New
Status in GNOME Terminal:
  New
Status in nano:
  New
Status in xfce4-terminal:
  New
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  OS: from Hardy to at least Trusty.

  When you use Finnish keyboard, you have to hold Alt Gr down to type |
  or \ or certain other characters. When typing a shell command, you may
  often want to enter a space character after such characters. But it
  easily happens that Alt Gr is still down when you press space, and
  consequently you type non-breaking space character U+00A0 (at least,
  if you use UTF-8 keyboard layout, which is default in Ubuntu).

  $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar"
  ls: cannot access foo bar: No such file or directory
  $cat foo bar | grep 0
  No command ' grep' found, but there are 16 similar ones
   grep: command not found

  Besides it may be hard to see the typing error, as non-breaking space
  character looks exactly same as regular space character.

  A way to avoid such typos would be to use another keyboard shortcut
  for non-breaking space. Besides non-breaking space should look
  different than regular space in terminal emulators and in editors.

  A workaround in to run
  setxkbmap -option "nbsp:none"
  to make  type regular space character. To make this default 
setting, you could add 

  XKBOPTIONS="nbsp:none"

  in '/etc/default/keyboard'.

  Then use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-
  breaking space in scripts and in command line.

  Non-breaking space can be typed (in GTK apps) by u 00a0, 
if needed, but it looks exactly like a regular space.
  For me,  would be a good shortcut for non-breaking space.

To manage notifications about this bug go to:
https://bugs.launchpad.net/geany/+bug/218637/+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 1840693] Re: Can't change input method (English->gcin Chinese) in LibreOffice

[Marcus Tomlinson]

** Changed in: libreoffice (Ubuntu)
   Status: Incomplete => New

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

Title:
  Can't change input method (English->gcin Chinese) in LibreOffice

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Hi,

  I can't change input method (English->gcin Chinese) in LibreOffice.
  I'm on LibreOffice 6.3. I have tried using hotkey and clicking on
  icons to change, neither worked. One separated but possibly relevant
  issue I am also having now: Over the past year, there's been a few
  times when I updated, Firefox would also have trouble changing input
  method, but instead of completely unable to change, I found out I
  could still change input method by hitting the hotkey "twice" & "fast"
  (slowly wouldn't work). Also for some(?) browser-based program like
  Jupyter Notebook, Alt would trigger browser behaviour first and
  ignored Jupyter's Alt function. I didn't realize so also couldn't
  confirm this is completely correlated with my LibreOffice input
  switching issue, but I figure it might still be some clue. Thank you.

  - Yen-Yung

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  Uname: Linux 5.2.5-050205-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 19 09:47:26 2019
  InstallationDate: Installed on 2019-03-26 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1840693/+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 1532431] Re: NetworkManager interferes with unmanaged 802.11 monitor mode interfaces

[Roger James]

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  NetworkManager interferes with unmanaged 802.11 monitor mode
  interfaces

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  If a virtual 802.11 interface of type monitor is created on a 802.11
  physical interface that already has a virtual interface of type
  managed created on it, then the managed interface is deleted.
  NetworkManager sets the type of the monitor interface to managed. This
  can be illustrated by the following commands. All the interface names
  have been listed in /etc/network/interfaces as follows so
  NetworkManager should not be managing them in any way.

  # Disable network manager on interface names I want to use for monitoring
  # related purposes
  iface eth1 inet manual
  iface BigTenda inet manual
  iface LittleBelkin inet manual
  iface LittleTenda inet manual
  iface Sinmax inet manual
  iface mon0 inet manual
  iface phy0.mon manual
  iface phy1.mon manual
  iface phy2.mon manual
  iface phy3.mon manual
  iface phy4.mon manual
  iface phy5.mon manual
  iface phy6.mon manual
  iface phy7.mon manual
  iface phy8.mon manual
  iface phy9.mon manual

  root@dragon:/home/roger# systemctl start NetworkManager
  root@dragon:/home/roger# iw dev
  phy#3
Interface Sinmax
ifindex 11
wdev 0x30001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw phy phy3 interface add phy2.mon type monitor 
flags otherbss
  root@dragon:/home/roger# iw dev
  phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 11
wdev 0x30001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw dev Sinmax del
  root@dragon:/home/roger# iw dev
  phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# systemctl stop NetworkManager
  root@dragon:/home/roger# iw dev
  phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# # Unplug the netwaork adapter for a few seconds
  root@dragon:/home/roger# iw dev
  phy#4
Interface Sinmax
ifindex 13
wdev 0x40001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw phy phy4 interface add phy2.mon type monitor 
flags otherbss
  root@dragon:/home/roger# iw dev
  phy#4
Interface phy2.mon
ifindex 14
wdev 0x40002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 13
wdev 0x40001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw dev Sinmax del
  root@dragon:/home/roger# iw dev
  phy#4
Interface phy2.mon
ifindex 14
wdev 0x40002
addr 00:0f:11:92:06:b2
type monitor

  This stops any running or future network traces on this interface
  working.

  This is another example of network manager interfering with interfaces
  it is not supposed to be managing. See bug #1314848 which is still
  unresolved.

  The above test was carried out on Ubuntu 15.10

  network-manager:
Installed: 1.0.4-0ubuntu5.2
Candidate: 1.0.4-0ubuntu5.2
Version table:
   *** 1.0.4-0ubuntu5.2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.4-0ubuntu5 0
  500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532431/+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 1812883] Re: Desktop view flashes every time ~/Desktop changes

[Jonathan Kamens]

I hardly think enough research into this has been done for it to be
obvious that this is a duplicate.

There are literally eight app indicator icons in my system tray right
now that disappear when I uninstall gnome-shell-extension-appindicator
(Synology Drive, Google Hangouts, Google Chrome, Dropbox, Yubico
Authenticator, Slack, Zoom, Flameshot), and I use them all the time.
Uninstalling that extension simply is not an option.

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

Title:
  Desktop view flashes every time ~/Desktop changes

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
  All of the icons on my desktop visibly flash every time I change
  anything in the folder ~/Desktop, even if the change is not something
  that is visible on my desktop.

  For example, "touch ~/Desktop/.#foo".

  I mean, the icons that haven't changed should never flash at all, even
  if a change is made that _does_ affect the visible display -- only the
  things that are actually new or different should change their
  appearance, and everything else should remain the same and not flash.
  But at the very least, there should be no flash when there are no
  visible changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 11:38:30 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+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 1746232] Re: driver looping then crashing

[Roger James]

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: New => Invalid

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

Title:
  driver looping then crashing

Status in linux package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid

Bug description:
  Running driver on Artful with the xwayland compositor. At random times
  the GPU stalls with.

  Jan 30 11:22:28 dragon kernel: [  487.046219] radeon :02:00.0: ring 0 
stalled for more than 29200msec
  Jan 30 11:22:28 dragon kernel: [  487.046224] radeon :02:00.0: GPU lockup 
(current fence id 0x1bdb last fence id 0x1bdc on ring 0)

  Usually when the system is idle.

  The above message is repeated once a second for a while. This usually
  but not always terminates with a page load fault in the driver.

  System can run for a few days without this happening. But on average
  it is once or twice a day.


  
  Jan 30 11:22:30 dragon kernel: [  488.507091] BUG: unable to handle kernel 
paging request at b406c1891ffc
  Jan 30 11:22:30 dragon kernel: [  488.507176] IP: 
radeon_ring_backup+0xd3/0x140 [radeon]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-video-radeon 1:7.10.0-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jan 30 11:40:08 2018
  DistUpgraded: 2017-11-06 18:26:08,552 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.10.0, 4.13.0-21-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.13.0-25-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.13.0-31-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] 
[1002:9442] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-07-01 (577 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/wd-root ro
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: Upgraded to artful on 2017-11-06 (84 days ago)
  dmi.bios.date: 05/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0403
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0403:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Dec  9 13:32:35 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746232/+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 892918] Re: Cannot start jack using qjackctrl via dbus when playback only option is needed

[Roger James]

** Changed in: jackd2 (Ubuntu)
   Status: New => Invalid

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

Title:
  Cannot start jack using qjackctrl via dbus when playback only option
  is needed

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  My audio hardware requires the playback only option to be specified to
  successfully start jackd. However I cannot start jackd with this
  option via qjackctrl unless dbus startup option is disabled. I am
  guessing that qjacktrl causes a dbus jackd with default parameters to
  be started (and stopped) before it tries to start the one with the
  playback only parameter. Starting a jackd without the playback only
  parameter always results in a server that hang and doe not respond to
  any client requests. Catch 22.

  Ubuntu 11.10
  jackd2 1.9.7~dsfg-1ubuntu2
  qjackctl 0.3.8-1

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: jackd2 1.9.7~dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Mon Nov 21 01:32:38 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: jackd2
  UpgradeStatus: Upgraded to oneiric on 2011-10-15 (36 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/892918/+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 1771880] Re: Seahorse unable to import pkcs12 certificates

[Кощеев]

** Bug watch added: Red Hat Bugzilla #1434854
   https://bugzilla.redhat.com/show_bug.cgi?id=1434854

** Also affects: seahorse (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1434854
   Importance: Unknown
   Status: Unknown

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

Title:
  Seahorse unable to import pkcs12 certificates

Status in seahorse:
  New
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in seahorse package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Fedora:
  New
Status in seahorse package in Fedora:
  Unknown

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/1771880/+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 1812883] Re: Desktop view flashes every time ~/Desktop changes

[Roger James]

I think this bug may well be a duplicate of #1825623. Would anyone
object if I marked it as such.

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

Title:
  Desktop view flashes every time ~/Desktop changes

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
  All of the icons on my desktop visibly flash every time I change
  anything in the folder ~/Desktop, even if the change is not something
  that is visible on my desktop.

  For example, "touch ~/Desktop/.#foo".

  I mean, the icons that haven't changed should never flash at all, even
  if a change is made that _does_ affect the visible display -- only the
  things that are actually new or different should change their
  appearance, and everything else should remain the same and not flash.
  But at the very least, there should be no flash when there are no
  visible changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 11:38:30 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+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 1812883] Re: Desktop view flashes every time ~/Desktop changes

[Roger James]

I worked round this issue by uninstalling gnome-shell-extension-
appindicator. This fixed this issue and also a number of high cpu usage
issues I was seeing. The cpu issues were sometimes severe enough to also
expose weaknesses in the compositor.

I suggest that anyone who is getting problems with gnome shell tries
this work around and reports the results back here along with the a
quick summary of the problem they were seeing.

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

Title:
  Desktop view flashes every time ~/Desktop changes

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
  All of the icons on my desktop visibly flash every time I change
  anything in the folder ~/Desktop, even if the change is not something
  that is visible on my desktop.

  For example, "touch ~/Desktop/.#foo".

  I mean, the icons that haven't changed should never flash at all, even
  if a change is made that _does_ affect the visible display -- only the
  things that are actually new or different should change their
  appearance, and everything else should remain the same and not flash.
  But at the very least, there should be no flash when there are no
  visible changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 11:38:30 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+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 1835295] Re: Closing a window on the desktop freezes the desktop for a minute or more.

[Roger James]

Closed bug to reduce confusion.

** This bug is no longer a duplicate of bug 1812883
   Desktop view flashes every time ~/Desktop changes

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Closing a window on the desktop freezes the desktop for a minute or
  more.

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  When I close a window on the gnome desktop. The desktop often freezes
  for anything between 30 seconds and a number of minutes. I notice this
  most often when closing a terminal window with ctrl+d.

  When look at the syslog and cpu usage (top) from a terminal logged in
  via ssh I see gnome-shell running at 100% and various gnome-shell
  error messages being reports. On the longer freezes the display often
  corrupts and the compositor can take a number of minutes to recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  3 20:04:23 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-07-01 (1097 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835295/+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 1840571] Re: ubuntu 18.04.3 startup purple screnn blink and could not start

[Seiichi Nakashima]

I try to Setting, 
Setting -> Region & Language -> Manage Installed Languages -> Install
ubunut-18.04.3(5.0.0-25) boot up normal sometimes,
and sometimes purple screen blink occurd.
but ubunut-18.04.2 Japanese(REMIX) LIVECD, alwayes boot up normal, both PCs.

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

Title:
  ubuntu 18.04.3 startup purple screnn blink and could not start

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I update ubuntu by software-updater.
  I update kernel 5.0.0-25, and reboot ubuntu system,
  but startup purple screen blink for ever,and could not login.
  I reboot kernel 5.0.0-23(before kernel), and login.

  as kernel 5.0.0-23, sometime same event occured,
  but I reset PC, next time restart normaly.

  I upload syslog file.

  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840571/+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 1840699] [NEW] Caps-lock doesn't work correctly in Old Hungarian layout

[Viktor Kovács]

Public bug reported:

Xkeyboard-config's version 2.27 resolves this problem

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xkb-data

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

Title:
  Caps-lock doesn't work correctly in Old Hungarian layout

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  Xkeyboard-config's version 2.27 resolves this problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1840699/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

[Gunnar Hjalmarsson]

@Ananth: That was disappointing, but thanks for letting us know. The
version you mentioned for bionic has the very same patch as the disco
and eoan versions, so the (attempt at a) fix is already in the PPA for
bionic.

Simon's successful test was on 19.04.

@CoderGuy: Which Ubuntu version did you test on?

As regards LiDE 100 I see in the discussion on the upstream merge
request that Jens Böttge explicitly confirmed that the patch worked when
applied to the bionic version of sane-backends.

https://gitlab.com/sane-
project/backends/merge_requests/34#note_141760446

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends source package in Disco:
  In Progress
Status in sane-backends package in Debian:
  Unknown

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+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 1840693] Re: Can't change input method (English->gcin Chinese) in LibreOffice

[Yen-Yung Chang]

Exactly, 6.3.0.4. Thank you.

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

Title:
  Can't change input method (English->gcin Chinese) in LibreOffice

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I can't change input method (English->gcin Chinese) in LibreOffice.
  I'm on LibreOffice 6.3. I have tried using hotkey and clicking on
  icons to change, neither worked. One separated but possibly relevant
  issue I am also having now: Over the past year, there's been a few
  times when I updated, Firefox would also have trouble changing input
  method, but instead of completely unable to change, I found out I
  could still change input method by hitting the hotkey "twice" & "fast"
  (slowly wouldn't work). Also for some(?) browser-based program like
  Jupyter Notebook, Alt would trigger browser behaviour first and
  ignored Jupyter's Alt function. I didn't realize so also couldn't
  confirm this is completely correlated with my LibreOffice input
  switching issue, but I figure it might still be some clue. Thank you.

  - Yen-Yung

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  Uname: Linux 5.2.5-050205-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 19 09:47:26 2019
  InstallationDate: Installed on 2019-03-26 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1840693/+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 1838358] Update Released

[Steve Langasek]

The verification of the Stable Release Update for ibus has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Ibus causes gnome-shell to freeze when password fields are selected in
  Firefox

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  The following has been seen in a VMware Horizon VDI. I cannot reproduce this
  issue myself.

  When a user interacts with any password field in Firefox, gnome-shell
  and Firefox both freeze and the system becomes unusable. If you ssh
  into the system and terminate Firefox, gnome-shell unfreezes.

  This only happens when the environment variable GTK_IM_MODULE is set to 
"ibus". If you unset the variable, or change it to
  GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works 
as intended.

  This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus
  1.5.17-3ubuntu4 and Firefox versions starting with 
68.0+build3-0ubuntu0.18.04.1

  Note: Chrome[ium] and other applications do not trigger it, and it cannot be
  reproduced in other desktop environments.

  This seems to be an interaction issue between ibus and gnome-shell.

  
  [Test Case]

  Launch firefox from within a gnome-session, making sure the
  GTK_IM_MODULE is set to "ibus". Note, this is the default value.

  $ env GTK_IM_MODULE="ibus" firefox

  Navigate to any website which has a password field. Wikipedia or
  Reddit will do.

  Click a password field and attempt to enter text. Firefox and gnome-
  shell both lock up and stay frozen for an extended period of time.

  Now, try it with the fix by enabling:

  $ env IBUS_DISCARD_PASSWORD=1 firefox

  When you enter text into a password field, ibus should directly pass through
  the text and the problem will be solved.

  We can also ask it to always apply for a specific application with:

  $ export IBUS_DISCARD_PASSWORD_APPS="firefox"
  $ firefox

  Again, when you enter text into a password input field, the problem will be
  solved.

  Test package is available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf235370-test

  Please test with the revised version,
  1.5.17-3ubuntu4+sf235370v20190731b1.

  [Regression Potential]

  This change has a low risk of regression, because the default behaviour is
  unchanged. To be able to use the password input field discard functionality, 
a user has to explicitly set an environment variable for the specific process, 
or set a regex that matches a process name.

  This means the fix is not enabled by default on any machines, and will
  only be utilised by those suffering problems and go and manually set
  environment variables or have their system administrator enable the
  environment variables permanently.

  This commit is present in upstream ibus from version ibus-1.5.19
  onward, and is currently present in cosmic, disco and eoan.

  If a regression occurs, users can ensure that the environment
  variables are unset and continue working.

  [Other info]

  * This patch is functionally the same as ibus-xx-f19-password.patch,
  but just hides the features behind environment variables.

  * When ibus is built with the patch ibus-xx-f19-password.patch which
  was dropped in ibus-1.5.17-2, the problem is solved.

  Instead of using ibus-xx-f19-password.patch, we will instead fix it with
  upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0:

  https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0

  Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome
  Author: fujiwarat 

  This implements the password discard functionality found in
  ibus-xx-f19-password.patch and places it behind two environment variables,
  IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS.

  IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS
  lets you set a regex of process names to filter and enable the fix for.

  If IBUS_DISCARD_PASSWORD is set or IBUS_DISCARD_PASSWORD_APPS is set
  with the process name which input is being placed into password
  fields, ibus will pass through the input to the application without
  any processing.

  * This only affect Bionic

  - Upstream first introduction:
  $ git describe --contains  f328fd67f479faa46ca87bf3c85eed7080ec5ec0
  1.5.19~7

  - Ubuntu ibus current version found in the archive:
  $ rmadison ibus
   ==> ibus | 1.5.17-3ubuntu4   | bionic 
   ibus | 

[Desktop-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

[Launchpad Bug Tracker]

This bug was fixed in the package ibus - 1.5.17-3ubuntu5

---
ibus (1.5.17-3ubuntu5) bionic; urgency=medium

  * debian/patches/ubuntu-password-discard-environment-variables.patch:
- Added upstream patch which implements selective ignoring of processing
  inputs to password fields based on two new environment variables,
  IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS (LP: #1838358)

 -- Matthew Ruffell   Thu, 01 Aug 2019
16:07:31 +1200

** Changed in: ibus (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Ibus causes gnome-shell to freeze when password fields are selected in
  Firefox

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  The following has been seen in a VMware Horizon VDI. I cannot reproduce this
  issue myself.

  When a user interacts with any password field in Firefox, gnome-shell
  and Firefox both freeze and the system becomes unusable. If you ssh
  into the system and terminate Firefox, gnome-shell unfreezes.

  This only happens when the environment variable GTK_IM_MODULE is set to 
"ibus". If you unset the variable, or change it to
  GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works 
as intended.

  This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus
  1.5.17-3ubuntu4 and Firefox versions starting with 
68.0+build3-0ubuntu0.18.04.1

  Note: Chrome[ium] and other applications do not trigger it, and it cannot be
  reproduced in other desktop environments.

  This seems to be an interaction issue between ibus and gnome-shell.

  
  [Test Case]

  Launch firefox from within a gnome-session, making sure the
  GTK_IM_MODULE is set to "ibus". Note, this is the default value.

  $ env GTK_IM_MODULE="ibus" firefox

  Navigate to any website which has a password field. Wikipedia or
  Reddit will do.

  Click a password field and attempt to enter text. Firefox and gnome-
  shell both lock up and stay frozen for an extended period of time.

  Now, try it with the fix by enabling:

  $ env IBUS_DISCARD_PASSWORD=1 firefox

  When you enter text into a password field, ibus should directly pass through
  the text and the problem will be solved.

  We can also ask it to always apply for a specific application with:

  $ export IBUS_DISCARD_PASSWORD_APPS="firefox"
  $ firefox

  Again, when you enter text into a password input field, the problem will be
  solved.

  Test package is available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf235370-test

  Please test with the revised version,
  1.5.17-3ubuntu4+sf235370v20190731b1.

  [Regression Potential]

  This change has a low risk of regression, because the default behaviour is
  unchanged. To be able to use the password input field discard functionality, 
a user has to explicitly set an environment variable for the specific process, 
or set a regex that matches a process name.

  This means the fix is not enabled by default on any machines, and will
  only be utilised by those suffering problems and go and manually set
  environment variables or have their system administrator enable the
  environment variables permanently.

  This commit is present in upstream ibus from version ibus-1.5.19
  onward, and is currently present in cosmic, disco and eoan.

  If a regression occurs, users can ensure that the environment
  variables are unset and continue working.

  [Other info]

  * This patch is functionally the same as ibus-xx-f19-password.patch,
  but just hides the features behind environment variables.

  * When ibus is built with the patch ibus-xx-f19-password.patch which
  was dropped in ibus-1.5.17-2, the problem is solved.

  Instead of using ibus-xx-f19-password.patch, we will instead fix it with
  upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0:

  https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0

  Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome
  Author: fujiwarat 

  This implements the password discard functionality found in
  ibus-xx-f19-password.patch and places it behind two environment variables,
  IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS.

  IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS
  lets you set a regex of process names to filter and enable the fix for.

  If IBUS_DISCARD_PASSWORD is set or IBUS_DISCARD_PASSWORD_APPS is set
  with the process name which input is being placed into password
  fields, ibus will pass through the input to the application without
  any processing.

  * This only affect Bionic

  - Upstream first introduction:
  $ git describe --contains  f328fd67f479faa46ca87bf3c85eed7080ec5ec0
  1.5.19~7

  - Ubuntu ibus current version found in the archive:

[Desktop-packages] [Bug 1840693] Re: Can't change input method (English->gcin Chinese) in LibreOffice

[Marcus Tomlinson]

Oh right, you mean the 6.3.0 snap?

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

Title:
  Can't change input method (English->gcin Chinese) in LibreOffice

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I can't change input method (English->gcin Chinese) in LibreOffice.
  I'm on LibreOffice 6.3. I have tried using hotkey and clicking on
  icons to change, neither worked. One separated but possibly relevant
  issue I am also having now: Over the past year, there's been a few
  times when I updated, Firefox would also have trouble changing input
  method, but instead of completely unable to change, I found out I
  could still change input method by hitting the hotkey "twice" & "fast"
  (slowly wouldn't work). Also for some(?) browser-based program like
  Jupyter Notebook, Alt would trigger browser behaviour first and
  ignored Jupyter's Alt function. I didn't realize so also couldn't
  confirm this is completely correlated with my LibreOffice input
  switching issue, but I figure it might still be some clue. Thank you.

  - Yen-Yung

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  Uname: Linux 5.2.5-050205-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 19 09:47:26 2019
  InstallationDate: Installed on 2019-03-26 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1840693/+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 1840693] Re: Can't change input method (English->gcin Chinese) in LibreOffice

[Marcus Tomlinson]

LibreOffice 6.3 has not been officially released to Ubuntu 18.04, from
where did you install this?

Please could you confirm that this occurs on the official 6.0.7 Bionic
release.

** Changed in: libreoffice (Ubuntu)
   Status: New => Incomplete

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

Title:
  Can't change input method (English->gcin Chinese) in LibreOffice

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I can't change input method (English->gcin Chinese) in LibreOffice.
  I'm on LibreOffice 6.3. I have tried using hotkey and clicking on
  icons to change, neither worked. One separated but possibly relevant
  issue I am also having now: Over the past year, there's been a few
  times when I updated, Firefox would also have trouble changing input
  method, but instead of completely unable to change, I found out I
  could still change input method by hitting the hotkey "twice" & "fast"
  (slowly wouldn't work). Also for some(?) browser-based program like
  Jupyter Notebook, Alt would trigger browser behaviour first and
  ignored Jupyter's Alt function. I didn't realize so also couldn't
  confirm this is completely correlated with my LibreOffice input
  switching issue, but I figure it might still be some clue. Thank you.

  - Yen-Yung

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  Uname: Linux 5.2.5-050205-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 19 09:47:26 2019
  InstallationDate: Installed on 2019-03-26 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1840693/+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 1840557] Re: Battery indicator at 66% show full icon on 19.04

[Daniel Szulc]

** Attachment added: "Tooltip_002.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+attachment/5283363/+files/Tooltip_002.png

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

Title:
  Battery indicator at 66% show full icon on 19.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator at 66% show a full battery icon on 19.04
  At about 55%ish he started to show a different icon (about 80% full icon)
  Rebooting system did not help.
  Updating system did not help.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-08-05 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Tags:  disco
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+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 1840693] [NEW] Can't change input method (English->gcin Chinese) in LibreOffice

[Yen-Yung Chang]

Public bug reported:

Hi,

I can't change input method (English->gcin Chinese) in LibreOffice. I'm
on LibreOffice 6.3. I have tried using hotkey and clicking on icons to
change, neither worked. One separated but possibly relevant issue I am
also having now: Over the past year, there's been a few times when I
updated, Firefox would also have trouble changing input method, but
instead of completely unable to change, I found out I could still change
input method by hitting the hotkey "twice" & "fast" (slowly wouldn't
work). Also for some(?) browser-based program like Jupyter Notebook, Alt
would trigger browser behaviour first and ignored Jupyter's Alt
function. I didn't realize so also couldn't confirm this is completely
correlated with my LibreOffice input switching issue, but I figure it
might still be some clue. Thank you.

- Yen-Yung

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice (not installed)
Uname: Linux 5.2.5-050205-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 19 09:47:26 2019
InstallationDate: Installed on 2019-03-26 (146 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libreoffice (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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1840693

Title:
  Can't change input method (English->gcin Chinese) in LibreOffice

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Hi,

  I can't change input method (English->gcin Chinese) in LibreOffice.
  I'm on LibreOffice 6.3. I have tried using hotkey and clicking on
  icons to change, neither worked. One separated but possibly relevant
  issue I am also having now: Over the past year, there's been a few
  times when I updated, Firefox would also have trouble changing input
  method, but instead of completely unable to change, I found out I
  could still change input method by hitting the hotkey "twice" & "fast"
  (slowly wouldn't work). Also for some(?) browser-based program like
  Jupyter Notebook, Alt would trigger browser behaviour first and
  ignored Jupyter's Alt function. I didn't realize so also couldn't
  confirm this is completely correlated with my LibreOffice input
  switching issue, but I figure it might still be some clue. Thank you.

  - Yen-Yung

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  Uname: Linux 5.2.5-050205-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 19 09:47:26 2019
  InstallationDate: Installed on 2019-03-26 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1840693/+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 1840557] Re: Battery indicator at 66% show full icon on 19.04

[Daniel Szulc]

I was not able to catch executable name using crosshairs:
WM_CLASS: not found

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

Title:
  Battery indicator at 66% show full icon on 19.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator at 66% show a full battery icon on 19.04
  At about 55%ish he started to show a different icon (about 80% full icon)
  Rebooting system did not help.
  Updating system did not help.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-08-05 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Tags:  disco
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+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 1840557] Re: Battery indicator at 66% show full icon on 19.04

[Daniel Szulc]

apport information

** Tags added: apport-collected

** Description changed:

  The battery indicator at 66% show a full battery icon on 19.04
  At about 55%ish he started to show a different icon (about 80% full icon)
  Rebooting system did not help.
  Updating system did not help.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 19.04
+ GsettingsChanges:
+  b'org.gnome.shell' b'favorite-apps' redacted by apport
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+ InstallationDate: Installed on 2019-08-05 (13 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-shell 3.32.0+git20190410-1ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
+ Tags:  disco
+ Uname: Linux 5.0.0-25-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1840557/+attachment/5283353/+files/Dependencies.txt

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

Title:
  Battery indicator at 66% show full icon on 19.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator at 66% show a full battery icon on 19.04
  At about 55%ish he started to show a different icon (about 80% full icon)
  Rebooting system did not help.
  Updating system did not help.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-08-05 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Tags:  disco
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+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 1840557] ProcEnviron.txt

[Daniel Szulc]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1840557/+attachment/5283355/+files/ProcEnviron.txt

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

Title:
  Battery indicator at 66% show full icon on 19.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator at 66% show a full battery icon on 19.04
  At about 55%ish he started to show a different icon (about 80% full icon)
  Rebooting system did not help.
  Updating system did not help.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-08-05 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Tags:  disco
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+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 1840557] ProcCpuinfoMinimal.txt

[Daniel Szulc]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1840557/+attachment/5283354/+files/ProcCpuinfoMinimal.txt

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

Title:
  Battery indicator at 66% show full icon on 19.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator at 66% show a full battery icon on 19.04
  At about 55%ish he started to show a different icon (about 80% full icon)
  Rebooting system did not help.
  Updating system did not help.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-08-05 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Tags:  disco
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+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 1804710] Re: apport hook depends on Python 2

[Sebastien Bacher]

** Changed in: gnome-screensaver (Ubuntu)
   Status: New => Fix Committed

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

Title:
  apport hook depends on Python 2

Status in gnome-screensaver package in Ubuntu:
  Fix Committed

Bug description:
  Even once bug 1804709 is addressed and the hook can run at all, it
  still won't work on default Ubuntu installations (which don't have
  Python 2) because the shebang points at /usr/bin/python.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1804710/+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 1774242] Re: Wacom touchscreens should use libinput, not wacom driver

[Jason Gerecke]

Just a note (mostly to other distro maintainers that may come across
this) that an alternative to completely disabling the Wacom driver's
touchscreen handling is to just add `Option "Gesture" "Off"` to the
touchscreen section of 70-wacom.conf instead.

The driver currently defaults to consuming all multitouch events to
power its own (very limited) gesture recognizer, but the above config
option will let it pass everything through to the desktop and
applications.

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

Title:
  Wacom touchscreens should use libinput, not wacom driver

Status in xf86-input-wacom package in Ubuntu:
  Fix Released

Bug description:
  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either.  I also verified it with Peter Hutterer's
  old cairo-based mt-touch test program.

  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)

  Yes, the touchscreen is made by Wacom, but wacom_drv.so has
  historically been only for Wacom tablets and in-screen stylus
  digitizers, and IMO that continues to be the case.  libinput is a much
  better choice of driver for this hardware (so is evdev for that
  matter), so I changed it to Driver "libinput" and got it working.
  (Wayland uses libinput, so in a wayland session, touch already works
  fine in Qt apps on this hardware.)

  I'm one of the Qt Quick maintainers, most concerned with touch
  handling, and I've also written some of the Qt xcb code for dealing
  with XInput touch and tablet devices.  So if you think that there's
  something wrong with Qt, such that it should still work anyway to use
  a wacom driver for a Wacom touchscreen, let me know.  These AES
  devices are still new to me (that's why I got a Yoga, to try it out).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+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 1747891] Re: gsd-color[1032]: failed to set screen _ICC_PROFILE

[Klaus Bielke]

I get this error from the sessiom of GDM3:

$ journalctl -b -u user-120.slice -p 0..6 | grep -e gdm -e icc
Aug 19 16:28:21 lieselotte systemd[1]: Created slice User Slice of gdm.
Aug 19 16:28:21 lieselotte systemd[911]: pam_unix(systemd-user:session): 
session opened for user gdm by (uid=0)
Aug 19 16:28:41 lieselotte gsd-color[1021]: failed to set screen _ICC_PROFILE: 
Datei »/home/klaus/.local/share/icc/edid-7c4f47b635a0342d129ec38f20009786.icc« 
konnte nicht geöffnet werden: Keine Berechtigung
Aug 19 16:28:42 lieselotte gsd-color[1021]: failed to set screen _ICC_PROFILE: 
Datei »/home/klaus/.local/share/icc/edid-7c4f47b635a0342d129ec38f20009786.icc« 
konnte nicht geöffnet werden: Keine Berechtigung

gsd-color from user id 120 trys reading a private file of user id 1000.
That seems wrong by design. It's a security fault.

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

Title:
  gsd-color[1032]: failed to set screen _ICC_PROFILE

Status in GNOME Settings Daemon:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged:

  gsd-color[1032]: failed to set screen _ICC_PROFILE: Failed to open
  file “/home/oem/.local/share/icc/edid-
  3ed66b5b66c8e176b2d44c8563cdad28.icc”: Permission denied

  
  This is related to (colormgr get-profiles output):

  Filename:  
/var/lib/gdm3/.local/share/icc/edid-3ed66b5b66c8e176b2d44c8563cdad28.icc
  Profile ID:icc-b11214f828f359ffc2d54bd918e8de7b
  Metadata:  CMF_version=3.26.2
  Metadata:  EDID_serial=SN-1
  Metadata:  CMF_binary=gnome-settings-daemon
  Metadata:  EDID_md5=3ed66b5b66c8e176b2d44c8563cdad28
  Metadata:  CMF_product=gnome-settings-daemon
  Metadata:  EDID_mnft=MTC
  Metadata:  FILE_checksum=b11214f828f359ffc2d54bd918e8de7b
  Metadata:  EDID_model=MON-SIS289
  Metadata:  DATA_source=edid
  Metadata:  MAPPING_device_id=xrandr-Mars-Tech 
Corporation-MON-SIS289-SN-1
  Metadata:  EDID_manufacturer=Mars-Tech Corporation

  Actual rights (set by the default install):

  oem@ubuntu:~$ ls -l /home/oem/.local/share/icc/
  -rw-rw-r-- 1 oem oem 1552 Dec  1 20:22 
edid-3ed66b5b66c8e176b2d44c8563cdad28.icc

  I've tried to follow that howto; but it should be set out of the box:
  
https://askubuntu.com/questions/199661/how-do-you-set-system-display-color-profiles-in-xubuntu-and-lubuntu

  note: if that apply to an other package than gsd, please do change/add

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Feb  7 12:11:12 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1747891/+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 1765363] Re: prime-select intel is not powering off the nvidia card

[Leonardo]

Same issue for me.

Ubuntu 18.04, lightdm
MSI GS65 Stealth, Geforce GTX 1660 Ti

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

Title:
  prime-select intel is not powering off the nvidia card

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Right now, it seems that prime-select intel makes sure the nvidia driver is 
not loaded, as nvidia-settings reports.
  But my power consumption is > 20W.
  cat /proc/acpi/bbswitch reports the card is still on. 

  
  If bbswitch and powertop are reliable, then the nvidia card is still powered.
  This is a thinkpad w520 in Optimus mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:56:21 2018
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-14 (125 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+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 1831144] Re: GNOME control center UI does not update dconf setting for magnifier mouse tracking m ode

[Amr Ibrahim]

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  GNOME control center UI does not update dconf setting for magnifier
  mouse tracking m ode

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If you attempt to change the mouse cursor tracking mode in the gnome
  control centre UI for the gnome magnifier the radio buttons have no
  effect. If yous use dconf-editor to manual change the option at:
  org.gnome.desktop.a11y.magnifier.mouse-tracking the setting will have
  an effect.

  [Test Case]

  To reproduce
  * Open gnome control centre and select universal access.
  * Click on Zoom.
  * Toggle between "Keep the mouse cursor centred" and the other two options 
(proportional and push).
  * If you enable Zoom and change these settings they have no effect.
  * Open dconf-editor.
  * Navigate to:

  org/gnome/desktop/a11y/magnifier/

  * Select the mouse tracking entry and change the setting to different
  values while the Zoom is enabled. The setting will change the way the
  mouse tracking behaves.

  Then install gnome-control-center{,-data,-faces} from disco-proposed
  and find that the UI now successfully changes the dconf values and the
  mouse tracking behavior.

  [Regression Potential]

  The code changes are specific to the Zoom Options window, where some
  of the options are currently broken. Low regression risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1831144/+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 1840675] [NEW] Expose a button in the Network panel to open nm-connection-editor

[Amr Ibrahim]

Public bug reported:

Upstream reverted showing the desktop launcher of nm-connection-editor because 
it's confusing for the average user, its icon is outdated and does not follow 
the current GNOME icon design guidelines.
https://gitlab.gnome.org/GNOME/network-manager-applet/issues/55
https://gitlab.gnome.org/GNOME/network-manager-applet/commit/a0c31ed5

Upstream follow-up bug: Remove runtime dependency on network-manager-applet 
(nm-connection-editor)
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/512

So in the meantime I suggest exposing a button in the Network panel (or
else where it fits) to open nm-connection-editor in order not to lose
the tool's functionally. The name of the button could be Advanced
Network Configuration.

Note: we are already doing the same thing for Region & Language settings
and Printer settings.

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


** Tags: eoan

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

Title:
  Expose a button in the Network panel to open nm-connection-editor

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

Bug description:
  Upstream reverted showing the desktop launcher of nm-connection-editor 
because it's confusing for the average user, its icon is outdated and does not 
follow the current GNOME icon design guidelines.
  https://gitlab.gnome.org/GNOME/network-manager-applet/issues/55
  https://gitlab.gnome.org/GNOME/network-manager-applet/commit/a0c31ed5

  Upstream follow-up bug: Remove runtime dependency on network-manager-applet 
(nm-connection-editor)
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/512

  So in the meantime I suggest exposing a button in the Network panel
  (or else where it fits) to open nm-connection-editor in order not to
  lose the tool's functionally. The name of the button could be Advanced
  Network Configuration.

  Note: we are already doing the same thing for Region & Language
  settings and Printer settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1840675/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

[Ananth P]

@gunnarhj I have `CanoScan LiDE 100` scanner with this problem on
18.04.3 LTS (bionic). I tried the above mentioned PPA. It does not solve
the issue.

`libsane-common` version is `1.0.27-1~experimental3ubuntu2.2~ppa`. I see
version `1.0.27-3.2...` for later ubuntu versions which is not available
for bionic.

If the fix is posted in PPA for bionic, I can verify and provide the
status here.

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends source package in Disco:
  In Progress
Status in sane-backends package in Debian:
  Unknown

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+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 1840626] Re: [nvidia] Slowness and sometimes the computer freezes

[Rabillon]

I can't disable the discrete Nvidia GPU in my BIOS. I don't have menu to swich 
off this GPU on the BIOS. 
I will run your command in a Term next time, 
Thanks.

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

Title:
  [nvidia] Slowness and sometimes the computer freezes

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Since maybe two months, my computer deosn't work correctly. There is
  slowness and sometime the computer freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug 19 00:42:31 2019
  DistUpgraded: 2019-02-23 11:53:16,014 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.116, 4.15.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0974]
 Subsystem: Acer Incorporated [ALI] GK208BM [GeForce 920M] [1025:0974]
  InstallationDate: Installed on 2019-02-21 (178 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: Acer Aspire E5-772G
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=377aa352-9018-46e8-bfee-2799a1be51e6 ro persistent quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-23 (176 days ago)
  dmi.bios.date: 07/28/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire E5-772G
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd07/28/2015:svnAcer:pnAspireE5-772G:pvrV1.09:rvnAcer:rnAspireE5-772G:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-772G
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 19 00:38:49 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1840626/+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 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34

[Treviño]

Work is in progress in https://github.com/micheleg/dash-to-dock/pull/975

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

Title:
  Extensions don't load in gnome-shell 3.33/3.34

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress

Bug description:
  Some extensions don't load in gnome-shell 3.33/3.34

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1835706/+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 1819082] Re: [snap] LibreOffice lacks support for OpenCL

[Marcus Tomlinson]

This actually turned out to be an issue in the Debian package as well,
which will be fixed in the 6.3.0 release later this week.

I'll keep this bug open though to track the lack of OpenCL support in
the snap.

** Summary changed:

- [snap] LibreOffice crashes after enabling OpenCL in the settings
+ [snap] LibreOffice lacks support for OpenCL

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

Title:
  [snap] LibreOffice lacks support for OpenCL

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Reproduce steps
  ---
  1. Enable OpenCL in settings
  2. Click "Apply"
  3. Choose "restart now" in the restart prompt

  Symptoms
  
  LibreOffice crash prompt appears and terminates with exit status 79.  After 
restarting it the OpenCL option remains untoggled.

  Version
  ---
  ```
  $ snap info libreoffice
  name:libreoffice
  snap-id:  CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v
  tracking: candidate
  refresh-date: today at 02:41 CST
  channels:
stable:6.2.0.3 2019-02-13 (104) 507MB -
candidate: 6.2.1.2 2019-03-02 (106) 507MB -
beta:  6.2.0.3 2019-01-31 (103) 505MB -
edge:  ↑  
  installed:   6.2.1.2(106) 507MB -
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1819082/+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 1754671] Re: Full-tunnel VPN DNS leakage regression

[dwmw2]

Any word on when this CVE will be fixed?

In the meantime I have put the 1.10.14-0ubuntu2 package into an apt
repository at http://david.woodhou.se/cve-2018-1000135/ for users who
need it. I couldn't work out how to copy it into a PPA without
rebuilding it.

In the short term can someone please at least confirm that no new update
will be shipped for Bionic which *doesn't* fix this, so that I don't
have to play games with keeping a package in that repository "newer"
than the latest in bionic-updates?

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1840571] Re: ubuntu 18.04.3 startup purple screnn blink and could not start

[Seiichi Nakashima]

I use two PCs in this place. both PC are install ubuntu-18,04.2,
and updateed to unutu-18.04.3(5.0.0-25 kernel) by software-updater.
my trouble occured both PCs. PC have amd-cpu.
BIOS are old, but work fine until ubuntu-18.04.2(kernel 4).

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

Title:
  ubuntu 18.04.3 startup purple screnn blink and could not start

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I update ubuntu by software-updater.
  I update kernel 5.0.0-25, and reboot ubuntu system,
  but startup purple screen blink for ever,and could not login.
  I reboot kernel 5.0.0-23(before kernel), and login.

  as kernel 5.0.0-23, sometime same event occured,
  but I reset PC, next time restart normaly.

  I upload syslog file.

  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840571/+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 1840634] Re: bionic: GNOME needs update to 3.30

[Daniel van Vugt]

A new version is never guaranteed to fix any given set of bugs. Please
log separate bugs for each of the problems you are experiencing by
running:

  ubuntu-bug gnome-shell


** Tags added: bionic

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gnome-shell (Ubuntu)
   Status: New => Opinion

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

Title:
  bionic: GNOME needs update to 3.30

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  With time going on, more an more minor flaws are occuring in GNOME:

  * mouse movements often are very laggy
  * mouse pointer gets under active windows
  * system gets stuck for several system
  * control for gnome-search is grayed out, so search can no longer be 
configured.

  It does not make much sense to repair each of these petitesses with
  outdated GNOME 3.28 - but if you take the idea of LTS serious, it is
  necessary to update GNOME. I won't update to 18.10, because that was a
  really bad experience last time - so many apps got dysfunctional.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840634/+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 1792085] Re: MTP not working/very slow on Bionic

[Behrouz]

I did something else today. 
Calibre on Flathub detected both my phone and my Kindle perfectly but Calibre 
on Bionic official repo couldn't do that. Well, official repo is version 3.21 
and Flathub version is 3.46. I don't know if that's the problem. 
Anyone knows what is that mean?

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

Title:
  MTP not working/very slow on Bionic

Status in libmtp:
  New
Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmtp/+bug/1792085/+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 1840634] [NEW] bionic: GNOME needs update to 3.30

[Wolf]

Public bug reported:

With time going on, more an more minor flaws are occuring in GNOME:

* mouse movements often are very laggy
* mouse pointer gets under active windows
* system gets stuck for several system
* control for gnome-search is grayed out, so search can no longer be configured.

It does not make much sense to repair each of these petitesses with
outdated GNOME 3.28 - but if you take the idea of LTS serious, it is
necessary to update GNOME. I won't update to 18.10, because that was a
really bad experience last time - so many apps got dysfunctional.

** Affects: gnome-shell (Ubuntu)
 Importance: Wishlist
 Status: Opinion


** Tags: bionic

** Package changed: nvidia-graphics-drivers-384 (Ubuntu) => gnome-shell
(Ubuntu)

** Description changed:

  With time going on, more an more minor flaws are occuring in GNOME:
  
  * mouse movements often are very laggy
  * mouse pointer gets under active windows
  * system gets stuck for several system
  * control for gnome-search is grayed out, so search can no longer be 
configured.
  
- I does not make much sense to repair each of these pettitesses with
+ It does not make much sense to repair each of these petitesses with
  outdated GNOME 3.28 - but if you take the idea of LTS serious, it is
  necessary to update GNOME. I won't update to 18.10, because that was a
  really bad experience last time - so many apps got dysfunctional.

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

Title:
  bionic: GNOME needs update to 3.30

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  With time going on, more an more minor flaws are occuring in GNOME:

  * mouse movements often are very laggy
  * mouse pointer gets under active windows
  * system gets stuck for several system
  * control for gnome-search is grayed out, so search can no longer be 
configured.

  It does not make much sense to repair each of these petitesses with
  outdated GNOME 3.28 - but if you take the idea of LTS serious, it is
  necessary to update GNOME. I won't update to 18.10, because that was a
  really bad experience last time - so many apps got dysfunctional.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840634/+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 1840634] [NEW] bionic: GNOME needs update to 3.30

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

With time going on, more an more minor flaws are occuring in GNOME:

* mouse movements often are very laggy
* mouse pointer gets under active windows
* system gets stuck for several system
* control for gnome-search is grayed out, so search can no longer be configured.

I does not make much sense to repair each of these pettitesses with
outdated GNOME 3.28 - but if you take the idea of LTS serious, it is
necessary to update GNOME. I won't update to 18.10, because that was a
really bad experience last time - so many apps got dysfunctional.

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

-- 
bionic: GNOME needs update to 3.30
https://bugs.launchpad.net/bugs/1840634
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

-- 
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 1840626] Re: [nvidia] Slowness and sometimes the computer freezes

[Daniel van Vugt]

Can you disable the discrete (Nvidia) GPU in your BIOS for a while and
try that? That will help us to identify if the Nvidia driver is related
to the problem.

Also, next time any slowness occurs please run in a Terminal window:

  journalctl -b0 > journal.txt

and then attach the file 'journal.txt' to this bug.

** Tags added: performance

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Incomplete

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  [nvidia] Slowness and sometimes the computer freezes

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Since maybe two months, my computer deosn't work correctly. There is
  slowness and sometime the computer freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug 19 00:42:31 2019
  DistUpgraded: 2019-02-23 11:53:16,014 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.116, 4.15.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0974]
 Subsystem: Acer Incorporated [ALI] GK208BM [GeForce 920M] [1025:0974]
  InstallationDate: Installed on 2019-02-21 (178 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: Acer Aspire E5-772G
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=377aa352-9018-46e8-bfee-2799a1be51e6 ro persistent quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-23 (176 days ago)
  dmi.bios.date: 07/28/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire E5-772G
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd07/28/2015:svnAcer:pnAspireE5-772G:pvrV1.09:rvnAcer:rnAspireE5-772G:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-772G
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 19 00:38:49 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1840626/+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 1840626] Re: Description

[Daniel van Vugt]

I wonder if the slowness is related to this from your Xorg log:

[   137.718] randr: falling back to unsynchronized pixmap sharing

** Tags added: nvidia

** Summary changed:

- Description
+ Slowness and sometimes the computer freezes

** Summary changed:

- Slowness and sometimes the computer freezes
+ [nvidia] Slowness and sometimes the computer freezes

** Tags added: hybrid

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [nvidia] Slowness and sometimes the computer freezes

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Since maybe two months, my computer deosn't work correctly. There is
  slowness and sometime the computer freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug 19 00:42:31 2019
  DistUpgraded: 2019-02-23 11:53:16,014 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.116, 4.15.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0974]
 Subsystem: Acer Incorporated [ALI] GK208BM [GeForce 920M] [1025:0974]
  InstallationDate: Installed on 2019-02-21 (178 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: Acer Aspire E5-772G
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=377aa352-9018-46e8-bfee-2799a1be51e6 ro persistent quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-23 (176 days ago)
  dmi.bios.date: 07/28/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire E5-772G
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd07/28/2015:svnAcer:pnAspireE5-772G:pvrV1.09:rvnAcer:rnAspireE5-772G:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-772G
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 19 00:38:49 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1840626/+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 1840626] [NEW] Description

[Rabillon]

Public bug reported:

Since maybe two months, my computer deosn't work correctly. There is
slowness and sometime the computer freeze.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
Uname: Linux 4.15.0-58-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:04:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Aug 19 00:42:31 2019
DistUpgraded: 2019-02-23 11:53:16,014 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.116, 4.15.0-58-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0974]
   Subsystem: Acer Incorporated [ALI] GK208BM [GeForce 920M] [1025:0974]
InstallationDate: Installed on 2019-02-21 (178 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
MachineType: Acer Aspire E5-772G
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=377aa352-9018-46e8-bfee-2799a1be51e6 ro persistent quiet splash 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-02-23 (176 days ago)
dmi.bios.date: 07/28/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.09
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire E5-772G
dmi.board.vendor: Acer
dmi.board.version: V1.09
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.09
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd07/28/2015:svnAcer:pnAspireE5-772G:pvrV1.09:rvnAcer:rnAspireE5-772G:rvrV1.09:cvnAcer:ct10:cvrV1.09:
dmi.product.family: BDW
dmi.product.name: Aspire E5-772G
dmi.product.version: V1.09
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Aug 19 00:38:49 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.3

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Description

Status in xorg package in Ubuntu:
  New

Bug description:
  Since maybe two months, my computer deosn't work correctly. There is
  slowness and sometime the computer freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug 19 00:42:31 2019
  DistUpgraded: 2019-02-23 11:53:16,014 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.116, 4.15.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0974]
 Subsystem: Acer 

[Desktop-packages] [Bug 1840473] Re: Don't draw | character on the screen while key is typed. :-)

[klfyt]

** Description changed:

- 
- Imho in this case it makes sense not to draw
- | character on the screen while any key is typed,
- perhaps it makes sense a bit later. I am not exactly
- sure then, but not immediately.
- 
+ Edit:
+ more padding.
  
  Problem:
  don't draw | on the screen, it makes no sense!  :)

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

Title:
  Don't draw | character on the screen while key is typed.   :-)

Status in xorg-server package in Ubuntu:
  Invalid
Status in xfwm4 package in Fedora:
  Unknown

Bug description:
  Edit:
  more padding.

  Problem:
  don't draw | on the screen, it makes no sense!  :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1840473/+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 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures

[Daniel van Vugt]

** Tags added: performance

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1207700
   Importance: Unknown
   Status: Unknown

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

Title:
  Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel
  scrolling with touchpad and touch gestures

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version:  Kubuntu 17.04
  Firefox version: 53.0.3+build1-0ubuntu0.17.04.2

  In Firefox, two-finger scroll gestures on a touchpad are interpreted
  as scroll wheel rotations, and the content scrolls three lines at a
  time. This is inappropriate behavior for touchpad scrolling; it should
  scroll pixel-by-pixel.

  Firefox already has the ability to do this, you just need to turn it
  on by running the program with MOZ_USE_XINPUT2=1 in the environment:
  for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to
  /etc/environment or something like that.

  Turning on this behavior yields a large usability improvement for
  laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be
  permanently added to the packaging such that it's always present when
  Firefox runs. This is what Fedora does, and it results in a much
  improved experience for the laptop user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1697122/+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 1840615] [NEW] Slow booting, slow start-up & once a week fsck issues in Ubuntu 19.04

[Pranav bhattarai]

*** This bug is a security vulnerability ***

Private security bug reported:

bond@007:~$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @2min 24.420s
└─multi-user.target @2min 24.419s
  └─kerneloops.service @2min 9.379s +247ms
└─network-online.target @2min 9.354s
  └─NetworkManager-wait-online.service @1min 40.208s +29.145s
└─NetworkManager.service @1min 32.992s +7.213s
  └─dbus.service @1min 32.963s
└─basic.target @1min 32.932s
  └─sockets.target @1min 32.932s
└─snapd.socket @1min 32.900s +29ms
  └─sysinit.target @1min 32.873s
└─apparmor.service @23.447s +2.113s
  └─local-fs.target @23.445s
└─run-user-1000-gvfs.mount @2min 44.750s
  └─run-user-1000.mount @2min 27.618s
└─local-fs-pre.target @4.127s
  └─systemd-tmpfiles-setup-dev.service @3.653s 
+473ms
└─systemd-sysusers.service @2.988s +663ms
  └─systemd-remount-fs.service @2.858s +127ms
└─systemd-journald.socket @2.855s
  └─-.mount @2.827s
└─systemd-journald.socket @2.855s
  └─...
In pictures: https://imgur.com/CT7s2sI

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Logs extracted from Log application which contain every 
infromtion."
   
https://bugs.launchpad.net/bugs/1840615/+attachment/5283247/+files/log%20messages

** Information type changed from Public to Private Security

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

Title:
  Slow booting, slow start-up & once a week fsck issues  in Ubuntu 19.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  bond@007:~$ systemd-analyze critical-chain
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  graphical.target @2min 24.420s
  └─multi-user.target @2min 24.419s
└─kerneloops.service @2min 9.379s +247ms
  └─network-online.target @2min 9.354s
└─NetworkManager-wait-online.service @1min 40.208s +29.145s
  └─NetworkManager.service @1min 32.992s +7.213s
└─dbus.service @1min 32.963s
  └─basic.target @1min 32.932s
└─sockets.target @1min 32.932s
  └─snapd.socket @1min 32.900s +29ms
└─sysinit.target @1min 32.873s
  └─apparmor.service @23.447s +2.113s
└─local-fs.target @23.445s
  └─run-user-1000-gvfs.mount @2min 44.750s
└─run-user-1000.mount @2min 27.618s
  └─local-fs-pre.target @4.127s
└─systemd-tmpfiles-setup-dev.service @3.653s 
+473ms
  └─systemd-sysusers.service @2.988s +663ms
└─systemd-remount-fs.service @2.858s +127ms
  └─systemd-journald.socket @2.855s
└─-.mount @2.827s
  └─systemd-journald.socket @2.855s
└─...
  In pictures: https://imgur.com/CT7s2sI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1840615/+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 1840612] [NEW] Software Center offers multiple version without explanation

[Duncan Lithgow]

Public bug reported:

Ubuntu 19.04
Gnome-software: 3.30.6-2ubuntu4.19.04.1

By default Ubuntu Software offers applications both from the ubuntu
repos and the snap store. that's fine but confusing. The two packages
can have different versions and descriptions, or the same version and
the same descriptions. This is all very confusing for anyone who doesn't
understand the difference.

I'm not going to suggest a specific solution, but here are some
thoughts.

- some key differences could be highlighted in tool-tip text
- the 'snap-store' text could be made into a button like the 'channel and 
'license buttons. An explanatory text could be kept there.
- if Canonical thinks it's unimportant which source is used (which is implied 
by not giving any caveats) then why not just roll the multiple packages into 
one entry (like the current multiple versions available) and make the 'source' 
text into an 'any' button which offers a choice of source. The newest version 
(regardless of source) could be offered by default.

PS. it's inconsistent that the option to include snappy is a setting in
the Gnome-software package and cannot be set in the Software & Updates
package.

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

** Description changed:

+ Ubuntu 19.04
+ Gnome-software: 3.30.6-2ubuntu4.19.04.1
+ 
  By default Ubuntu Software offers applications both from the ubuntu
  repos and the snap store. that's fine but confusing. The two packages
  can have different versions and descriptions, or the same version and
  the same descriptions. This is all very confusing for anyone who doesn't
  understand the difference.
  
  I'm not going to suggest a specific solution, but here are some
  thoughts.
  
  - some key differences could be highlighted in tool-tip text
  - the 'snap-store' text could be made into a button like the 'channel and 
'license buttons. An explanatory text could be kept there.
  - if Canonical thinks it's unimportant which source is used (which is implied 
by not giving any caveats) then why not just roll the multiple packages into 
one entry (like the current multiple versions available) and make the 'source' 
text into an 'any' button which offers a choice of source. The newest version 
(regardless of source) could be offered by default.
+ 
+ PS. it's inconsistent that the option to include snappy is a setting in
+ the Gnome-software package and cannot be set in the Software & Updates
+ package.

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

Title:
  Software Center offers multiple version without explanation

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Ubuntu 19.04
  Gnome-software: 3.30.6-2ubuntu4.19.04.1

  By default Ubuntu Software offers applications both from the ubuntu
  repos and the snap store. that's fine but confusing. The two packages
  can have different versions and descriptions, or the same version and
  the same descriptions. This is all very confusing for anyone who
  doesn't understand the difference.

  I'm not going to suggest a specific solution, but here are some
  thoughts.

  - some key differences could be highlighted in tool-tip text
  - the 'snap-store' text could be made into a button like the 'channel and 
'license buttons. An explanatory text could be kept there.
  - if Canonical thinks it's unimportant which source is used (which is implied 
by not giving any caveats) then why not just roll the multiple packages into 
one entry (like the current multiple versions available) and make the 'source' 
text into an 'any' button which offers a choice of source. The newest version 
(regardless of source) could be offered by default.

  PS. it's inconsistent that the option to include snappy is a setting
  in the Gnome-software package and cannot be set in the Software &
  Updates package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1840612/+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