[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported

[Pedro Côrte-Real]

I don't know what automation concluded that a fix was released but what
happened instead is that upstream has once again refused to address this
and just closed the bug reports. I suggest Ubuntu just ship the patch in
its packages.

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  Fix Released
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+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 1852911] Re: CriticalPowerAction=Suspend should be supported

[Pedro Côrte-Real]

I've been running patched upower for a year and a half now. It has saved
me in a few occasions. By far the most common scenario is that I've
forgotten to plugin and it just suspends and I reconnect it and get
going again. Shutdown is just useless, you still lose your work so might
as well let the power fail completely. Ubuntu should just ship the
patch.

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  New
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+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 1988422] Re: Bluetooth discoverability is not communicated to the user adequately in Settings

[Pedro Daniel Vieira Rosado]

Correct, and a prompt should be shown when possible malicious files are
sent, to let the user decide if he wants to receive it or not.

It's surreal that you can send any file type with any content and it
will automatically be sent to the download folder without user input, as
long as the device is paired.

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

Title:
  Bluetooth discoverability is not communicated to the user adequately
  in Settings

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

Bug description:
  When bluetooth is turned on ubuntu it is discoverable to all nearby devices.
  It's strange that any "dumb" bluetooth device offers the option to be turned 
on but not be discoverable, but gnome bluetooth manager doesn't offer such 
option.

  Any device can be paired with a device using the gnome desktop, as
  long as the user gets the prompt to pair. After that, gnome desktop
  can receive any file to the downloads folder.

  There should be an option to make the gnome desktop device not show up
  to other devices, and another one to restrict what files can be sent
  via BT to the downloads folder

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgnome-bluetooth13 3.34.5-8
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 12:12:16 2022
  InstallationDate: Installed on 2022-08-31 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988422/+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 1988422] Re: device discoverable by default

[Pedro Daniel Vieira Rosado]

There could be at least a prompt to turn off visibility to other devices.
As for the sent files, a simple grep or zgrep to exclude some files from being 
sent to host via BT would be a security improvement. Specially because if the 
user has wine installed and a malicious .exe is sent... it can put the whole 
host in danger. Same for malicious scripts that can be used to escalate 
privileges on /home/user/downloads.

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

Title:
  device discoverable by default

Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  When bluetooth is turned on ubuntu it is discoverable to all nearby devices.
  It's strange that any "dumb" bluetooth device offers the option to be turned 
on but not be discoverable, but gnome bluetooth manager doesn't offer such 
option.

  Any device can be paired with a device using the gnome desktop, as
  long as the user gets the prompt to pair. After that, gnome desktop
  can receive any file to the downloads folder.

  There should be an option to make the gnome desktop device not show up
  to other devices, and another one to restrict what files can be sent
  via BT to the downloads folder

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgnome-bluetooth13 3.34.5-8
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 12:12:16 2022
  InstallationDate: Installed on 2022-08-31 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1988422/+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 1988422] Re: device discoverable by default

[Pedro Daniel Vieira Rosado]

Open setting on top right of the screen. Turn bluetooth on. As soon as BT is 
turned on for ubuntu 22.04, my laptop or desktop are visible to all nearby BT 
devices. 
Click pair with any device, the prompt will show up in ubuntu 22.04. From that 
on, I can send any files over BT and will be sent directly to downloads folder, 
malicious or not.

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

Title:
  device discoverable by default

Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  When bluetooth is turned on ubuntu it is discoverable to all nearby devices.
  It's strange that any "dumb" bluetooth device offers the option to be turned 
on but not be discoverable, but gnome bluetooth manager doesn't offer such 
option.

  Any device can be paired with a device using the gnome desktop, as
  long as the user gets the prompt to pair. After that, gnome desktop
  can receive any file to the downloads folder.

  There should be an option to make the gnome desktop device not show up
  to other devices, and another one to restrict what files can be sent
  via BT to the downloads folder

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgnome-bluetooth13 3.34.5-8
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 12:12:16 2022
  InstallationDate: Installed on 2022-08-31 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1988422/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Pedro Serrano]

Happens since I upgraded to Ubuntu 22.04.  I can force focus on the Save
As dialog, hit  to be able to rename my download, but the focus
doesn't stay on the file name and instead - after typing a character -
the focus switches to a search field inside the Save As dialog.

root@pswsl01:~# uname -a 
Linux pswsl01 5.18.10-76051810-generic 
#202207071639~1659403207~22.04~cb5f582~dev-Ubuntu SMP PREEMPT_DY x86_64 x86_64 
x86_64 GNU/Linux

root@pswsl01:~# cat /proc/version
Linux version 5.18.10-76051810-generic (buildd@lcy02-amd64-047) (gcc (Ubuntu 
11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) 
#202207071639~1659403207~22.04~cb5f582~dev-Ubuntu SMP PREEMPT_DY

root@pswsl01:~# lscpu
Architecture:x86_64
  CPU op-mode(s):32-bit, 64-bit
  Address sizes: 48 bits physical, 48 bits virtual
  Byte Order:Little Endian
CPU(s):  12
  On-line CPU(s) list:   0-11
Vendor ID:   AuthenticAMD
  Model name:AMD Ryzen 5 5500U with Radeon Graphics
CPU family:  23
Model:   104
Thread(s) per core:  2
Core(s) per socket:  6
Socket(s):   1
Stepping:1

root@pswsl01:~# snap list
Name   Version RevTracking 
Publisher Notes
airshark   0.4 3  latest/stablepd   
 -
bare   1.0 5  latest/stable
canonical✓base
chromium   105.0.5195.52   2076   latest/stable
canonical✓-
core   16-2.56.2   13425  latest/stable
canonical✓core
core18 202207062538   latest/stable
canonical✓base
core20 202208051611   latest/stable
canonical✓base
firefox104.0.1-1   1775   latest/stablemozilla✓ 
 -
gh 2.6.0-15-g1a10fd5a  502latest/stable
casper-dcl-
gnome-3-28-18043.28.0-19-g98f9e67.98f9e67  161latest/stable
canonical✓-
gnome-3-34-18040+git.3556cb3   77 latest/stable/…  
canonical✓-
gnome-3-38-20040+git.891e5bc   115latest/stable
canonical✓-
gtk-common-themes  0.1-81-g442e511 1535   latest/stable/…  
canonical✓-
signal-desktop 5.52.0  392latest/stable
snapcrafters  -
snap-store 3.38.0-66-gbd5b8f7  558latest/stable/…  
canonical✓-
snapd  2.56.2  16292  latest/stable
canonical✓snapd

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1988408] [NEW] bluetooth gaming controller

[Pedro Daniel Vieira Rosado]

Public bug reported:

On 2 different ubuntu machines (laptop and desktop, with same ubuntu
version and bluez) I can pair my generic BT game controller without any
issues except for the fact that I can't send or receive any input.

This controller with the same bluetooth dongle connects perfectly on
windows 10 and 11 (had to dual boot to test it).

The laptop itself, via dongle or via integrated BT receiver, can also
connect perfectly and use it for steam on windows. There's something
wrong going on with Bluez stack.

Tried to use jstest-gtk and install xbox-drv to no avail.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep  1 10:41:31 2022
InstallationDate: Installed on 2022-08-31 (1 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=pt:pt_BR:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_PT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=4f492b24-bcc5-4d68-917d-b6fed9e56b0f ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/23/2015
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.asset.tag: BC5FF494092A
dmi.board.name: 960GM-VGS3 FX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd07/23/2015:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM-VGS3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 5C:F3:70:A8:A2:8B  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING 
RX bytes:1035 acl:0 sco:0 events:60 errors:0
TX bytes:3694 acl:0 sco:0 commands:60 errors:0
rfkill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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


** Tags: amd64 apport-bug jammy

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

Title:
  bluetooth gaming controller

Status in bluez package in Ubuntu:
  New

Bug description:
  On 2 different ubuntu machines (laptop and desktop, with same ubuntu
  version and bluez) I can pair my generic BT game controller without
  any issues except for the fact that I can't send or receive any input.

  This controller with the same bluetooth dongle connects perfectly on
  windows 10 and 11 (had to dual boot to test it).

  The laptop itself, via dongle or via integrated BT receiver, can also
  connect perfectly and use it for steam on windows. There's something
  wrong going on with Bluez stack.

  Tried to use jstest-gtk and install xbox-drv to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 10:41:31 2022
  InstallationDate: Installed on 2022-08-31 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=4f492b24-bcc5-4d68-917d-b6fed9e56b0f ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2015
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.asset.tag: BC5FF494092A
  dmi.board.name: 960GM-VGS3 FX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Desktop-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

[Pedro Ribeiro]

Got it, thanks for the explanation.

At least we know the overwrite doesn't happen, which removes the
potential security issue out of the equation.

To be honest I'm not completely convinced it was exploitable, but I'm
not convinced it wasn't either, so better play it safe and patch it out.
The side effects on other apps are unfortunate, but like you say, it's
up to the apps to manage errors coming from gdk-pixbuf.

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
   - PCManFM, LXDE's file manager which straight up crashes
   - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
   - Eye of GNOME (eog) triggers the segfault in syslog
   - Eye of MATE (eom) segfaults

   * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.

  [Where problems could occur]

   * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.

   * It is possible, and has happened in the past (which has been
  patched) that other bad GIFs can cause other crashes.

   * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems

   * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs

  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.

  [Other Info]

   * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
   * Files attached are examples or crashes
   * Again, all apps using gdk-pixbuf are affected
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190
   * 
https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

[Pedro Ribeiro]

Tested on Ubuntu 22.04, it seems that EoG / EoM / gdk-
pixbuf-{pixdata,thumbnailer} try to allocate all the system's memory
with the "more_trouble.poc" from the original report.

Out of these, EoM seems not to handle it gracefully, as it gets killed
by oom-killer. The others simply give up at some point without being
killed and do not crash. Seems like a different bug that affects EoM,
but might affect other users of gdk-pixbuf too?

** Attachment added: "Crashes EoM on 22.04 with oom (might crash other 
gdk-pixbuf users too)"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605647/+files/more_trouble.poc

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
   - PCManFM, LXDE's file manager which straight up crashes
   - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
   - Eye of GNOME (eog) triggers the segfault in syslog
   - Eye of MATE (eom) segfaults

   * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.

  [Where problems could occur]

   * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.

   * It is possible, and has happened in the past (which has been
  patched) that other bad GIFs can cause other crashes.

   * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems

   * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs

  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.

  [Other Info]

   * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
   * Files attached are examples or crashes
   * Again, all apps using gdk-pixbuf are affected
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190
   * 
https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

[Pedro Ribeiro]

I just checked, and it seems EOM still crashes with OOM, even with the
patched library (version 2.42.8). I'm guessing this is a separate bug in
EOM?

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
   - PCManFM, LXDE's file manager which straight up crashes
   - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
   - Eye of GNOME (eog) triggers the segfault in syslog

   * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.

  [Where problems could occur]

   * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.

   * It is possible, and has happened in the past (which has been
  patched) that other bad GIFs can cause other crashes.

   * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems

   * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs

  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.

  [Other Info]

   * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
   * Files attached are examples or crashes
   * Again, all apps using gdk-pixbuf are affected
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
   * 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1648319] Re: Failed to use bus name org.freedesktop.DisplayManager

[Pedro Serrano]

Folks,

I get the Same error.

lightdm --test-mode 
Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate 
permissions?

It's been a few years without activity...  Thanks for your attention.

Regards

Pedro

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

Title:
  Failed to use bus name org.freedesktop.DisplayManager

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I have implemented the command lightdm --test-mode --debug and I happened 
here such error:
  ==
  [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.01s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=1683
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.01s] DEBUG: Using Xephyr for X servers
  [+0.01s] DEBUG: Registered seat module xlocal
  [+0.01s] DEBUG: Registered seat module xremote
  [+0.01s] DEBUG: Registered seat module unity
  [+0.01s] DEBUG: Registered seat module surfaceflinger
  [+1.13s] DEBUG: Adding default seat
  [+1.13s] DEBUG: Seat: Starting
  [+1.13s] DEBUG: Seat: Creating greeter session
  [+1.17s] DEBUG: Seat: Creating display server of type x
  [+1.20s] DEBUG: Could not run plymouth --ping: Failed to execute child 
process "plymouth" (No such file or directory)
  [+1.20s] DEBUG: Using VT 7
  [+1.20s] DEBUG: Seat: Starting local X display on VT 7
  [+1.20s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+1.36s] DEBUG: DisplayServer x-1: Writing X server authority to 
/var/run/lightdm/root/:1
  [+1.36s] DEBUG: DisplayServer x-1: Launching X Server
  [+1.36s] DEBUG: Launching process 1687: /usr/bin/Xephyr :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
  [+1.36s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
  [+1.36s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+1.36s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  Failed to use bus name org.freedesktop.DisplayManager, do you have 
appropriate permissions?
  =
  On the Internet I have the exact solution to this problem is not found. The 
computer I have is only one graphics card and built-in The controller is not 
present. Somebody help than you can!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648319/+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 1648319] Re: Failed to use bus name org.freedesktop.DisplayManager

[Pedro Serrano]

BTW..
root@###:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04 LTS
Release:22.04
Codename:   jammy
root@###:~# apt list lightdm --installed
Listing... Done
lightdm/jammy,now 1.30.0-0ubuntu5 amd64 [installed,automatic]

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

Title:
  Failed to use bus name org.freedesktop.DisplayManager

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I have implemented the command lightdm --test-mode --debug and I happened 
here such error:
  ==
  [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.01s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=1683
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.01s] DEBUG: Using Xephyr for X servers
  [+0.01s] DEBUG: Registered seat module xlocal
  [+0.01s] DEBUG: Registered seat module xremote
  [+0.01s] DEBUG: Registered seat module unity
  [+0.01s] DEBUG: Registered seat module surfaceflinger
  [+1.13s] DEBUG: Adding default seat
  [+1.13s] DEBUG: Seat: Starting
  [+1.13s] DEBUG: Seat: Creating greeter session
  [+1.17s] DEBUG: Seat: Creating display server of type x
  [+1.20s] DEBUG: Could not run plymouth --ping: Failed to execute child 
process "plymouth" (No such file or directory)
  [+1.20s] DEBUG: Using VT 7
  [+1.20s] DEBUG: Seat: Starting local X display on VT 7
  [+1.20s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+1.36s] DEBUG: DisplayServer x-1: Writing X server authority to 
/var/run/lightdm/root/:1
  [+1.36s] DEBUG: DisplayServer x-1: Launching X Server
  [+1.36s] DEBUG: Launching process 1687: /usr/bin/Xephyr :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
  [+1.36s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
  [+1.36s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+1.36s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  Failed to use bus name org.freedesktop.DisplayManager, do you have 
appropriate permissions?
  =
  On the Internet I have the exact solution to this problem is not found. The 
computer I have is only one graphics card and built-in The controller is not 
present. Somebody help than you can!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648319/+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 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click

[João Pedro Seara]

Daniel,

I have corrected my last post. Thanks!

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

Title:
  The Activities top left button reacts to a mouse-up (e.g. drag and
  drop) instead of a click

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  Honestly I have no idea which package this is in and I could not
  identify it by following the wiki page for identifying packages. I had
  no luck with the ubuntu-bug command either. Feel free to migrate at
  your discretion.

  The Activities menu/button at the top left in the desktop menu(?) bar
  seems to listen to left-mouse-up instead of a full click with the
  mouse.

  If I want to e.g. select all my files on the desktop by click-and-
  dragging a selection box and then end the selection at the top left of
  the screen I will then also activate the Activities button if I
  release the mouse button over it.

  I expect most button-like UI controls to only trigger on complete
  mouse clicks: mouse down, mouse up.

  Pretty much the *only* exception to this expectation -- that I can
  think of -- is when a click is initiated on one menu item and finishes
  on a menu item that is its peer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1725814/+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 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click

[João Pedro Seara]

Hello, Daniel.

Yep, I didn't want to open a duplicate.

By the way, the current workaround for this is to disable Wayland:

1. sudo vi /etc/gdm3/custom.conf
2. WaylandEnable=false
3. Reboot

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

Title:
  The Activities top left button reacts to a mouse-up (e.g. drag and
  drop) instead of a click

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  Honestly I have no idea which package this is in and I could not
  identify it by following the wiki page for identifying packages. I had
  no luck with the ubuntu-bug command either. Feel free to migrate at
  your discretion.

  The Activities menu/button at the top left in the desktop menu(?) bar
  seems to listen to left-mouse-up instead of a full click with the
  mouse.

  If I want to e.g. select all my files on the desktop by click-and-
  dragging a selection box and then end the selection at the top left of
  the screen I will then also activate the Activities button if I
  release the mouse button over it.

  I expect most button-like UI controls to only trigger on complete
  mouse clicks: mouse down, mouse up.

  Pretty much the *only* exception to this expectation -- that I can
  think of -- is when a click is initiated on one menu item and finishes
  on a menu item that is its peer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1725814/+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 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click

[João Pedro Seara]

Daniel, I am reporting it in Jammy.

This is definitely a regression in the sense that we're now having a
problem that we didn't before. This bug is defined as an "opinion" where
it should definitely be a "bug", IMO.

Please check the attached video where I clearly compare 20.04 vs 22.04.

** Attachment added: "Screencast from 04-05-2022 11:50:47.webm"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725814/+attachment/5586638/+files/Screencast%20from%2004-05-2022%2011%3A50%3A47.webm

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

Title:
  The Activities top left button reacts to a mouse-up (e.g. drag and
  drop) instead of a click

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  Honestly I have no idea which package this is in and I could not
  identify it by following the wiki page for identifying packages. I had
  no luck with the ubuntu-bug command either. Feel free to migrate at
  your discretion.


  The Activities menu/button at the top left in the desktop menu(?) bar
  seems to listen to left-mouse-up instead of a full click with the
  mouse.

  If I want to e.g. select all my files on the desktop by click-and-
  dragging a selection box and then end the selection at the top left of
  the screen I will then also activate the Activities button if I
  release the mouse button over it.

  I expect most button-like UI controls to only trigger on complete
  mouse clicks: mouse down, mouse up.

  Pretty much the *only* exception to this expectation -- that I can
  think of -- is when a click is initiated on one menu item and finishes
  on a menu item that is its peer.

  
  ---

  Description:  Ubuntu 17.10
  Release:  17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725814/+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 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click

[João Pedro Seara]

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

Title:
  The Activities top left button reacts to a mouse-up (e.g. drag and
  drop) instead of a click

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  Honestly I have no idea which package this is in and I could not
  identify it by following the wiki page for identifying packages. I had
  no luck with the ubuntu-bug command either. Feel free to migrate at
  your discretion.


  The Activities menu/button at the top left in the desktop menu(?) bar
  seems to listen to left-mouse-up instead of a full click with the
  mouse.

  If I want to e.g. select all my files on the desktop by click-and-
  dragging a selection box and then end the selection at the top left of
  the screen I will then also activate the Activities button if I
  release the mouse button over it.

  I expect most button-like UI controls to only trigger on complete
  mouse clicks: mouse down, mouse up.

  Pretty much the *only* exception to this expectation -- that I can
  think of -- is when a click is initiated on one menu item and finishes
  on a menu item that is its peer.

  
  ---

  Description:  Ubuntu 17.10
  Release:  17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725814/+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 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click

[João Pedro Seara]

Sebastien,

This issue is very annoying in 22.04 indeed. I didn't notice this in
20.04 at all. Seems to be a re-occurrence.

Here is the link to the upstream bug:

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4897

Someone kindly attach it to this case's header.

Thanks.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4897
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4897

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

Title:
  The Activities top left button reacts to a mouse-up (e.g. drag and
  drop) instead of a click

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Honestly I have no idea which package this is in and I could not
  identify it by following the wiki page for identifying packages. I had
  no luck with the ubuntu-bug command either. Feel free to migrate at
  your discretion.


  The Activities menu/button at the top left in the desktop menu(?) bar
  seems to listen to left-mouse-up instead of a full click with the
  mouse.

  If I want to e.g. select all my files on the desktop by click-and-
  dragging a selection box and then end the selection at the top left of
  the screen I will then also activate the Activities button if I
  release the mouse button over it.

  I expect most button-like UI controls to only trigger on complete
  mouse clicks: mouse down, mouse up.

  Pretty much the *only* exception to this expectation -- that I can
  think of -- is when a click is initiated on one menu item and finishes
  on a menu item that is its peer.

  
  ---

  Description:  Ubuntu 17.10
  Release:  17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725814/+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 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click

[João Pedro Seara]

Can someone please look into this?

This is happening * again * in Ubuntu 22.04 and is incredibly annoying.

JP

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

Title:
  The Activities top left button reacts to a mouse-up (e.g. drag and
  drop) instead of a click

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Honestly I have no idea which package this is in and I could not
  identify it by following the wiki page for identifying packages. I had
  no luck with the ubuntu-bug command either. Feel free to migrate at
  your discretion.


  The Activities menu/button at the top left in the desktop menu(?) bar
  seems to listen to left-mouse-up instead of a full click with the
  mouse.

  If I want to e.g. select all my files on the desktop by click-and-
  dragging a selection box and then end the selection at the top left of
  the screen I will then also activate the Activities button if I
  release the mouse button over it.

  I expect most button-like UI controls to only trigger on complete
  mouse clicks: mouse down, mouse up.

  Pretty much the *only* exception to this expectation -- that I can
  think of -- is when a click is initiated on one menu item and finishes
  on a menu item that is its peer.

  
  ---

  Description:  Ubuntu 17.10
  Release:  17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725814/+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 1970069] [NEW] Annoying boot messages interfering with splash screen, since upgrading to Jammy

[João Pedro Seara]

Public bug reported:

Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as
clean as it used to be.

Basically, the flow used to be in 20.04:

GRUB > Splash screen > Login prompt

Currently in 22.04:

GRUB > Splash screen > Messages (in the attached file) > Splash screen
again for a sec > Login prompt

All of those messages already existed in 20.04, the difference is that
they were not appearing during boot.

I was able to get rid of the "usb" related messages by just adding
"loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

However, the fsck related message, I was not available to get rid of.

Something definitely changed here. To me, these messages are not of
enough relevance to be shown at boot by default.

Obviously a minor issue, but important to the whole look and feel of the
OS for desktop.

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

** Attachment added: "20220422_014058.jpg"
   
https://bugs.launchpad.net/bugs/1970069/+attachment/5582941/+files/20220422_014058.jpg

** Description changed:

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as
  clean as it used to be.
  
  Basically, the flow used to be in 20.04:
  
  GRUB > Splash screen > Login prompt
  
  Currently in 22.04:
  
  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt
  
  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.
  
  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".
  
  However, the fsck related messages, I was not available to get rid of.
  
+ Something definitely changed here. To me, these messages are not of
+ enough relevance to be shown at boot by default.
+ 
  Obviously a minor issue, but important to the whole look and feel of the
  OS for desktop.
- 
- Something definitely changed here.

** Description changed:

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as
  clean as it used to be.
  
  Basically, the flow used to be in 20.04:
  
  GRUB > Splash screen > Login prompt
  
  Currently in 22.04:
  
  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt
  
  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.
  
  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".
  
- However, the fsck related messages, I was not available to get rid of.
+ However, the fsck related message, I was not available to get rid of.
  
  Something definitely changed here. To me, these messages are not of
  enough relevance to be shown at boot by default.
  
  Obviously a minor issue, but important to the whole look and feel of the
  OS for desktop.

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

Title:
  Annoying boot messages interfering with splash screen, since upgrading
  to Jammy

Status in plymouth package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  However, the fsck related message, I was not available to get rid of.

  Something definitely changed here. To me, these messages are not of
  enough relevance to be shown at boot by default.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+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 1969622] Re: save file dialog doesn't allow saving to a directory without files

[João Pedro Seara]

Hello folks. Facing this issue as well, thank you very much for jumping
on it so quickly.

The workaround I found is to, instead of navigating to the inside of the
folder, just navigate to one level above, then click on the directory,
click on Save (this will make you enter the directory), and then click
on Save again.

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

Title:
  save file dialog doesn't allow saving to a directory without files

Status in GTK+:
  Unknown
Status in gtk4 package in Ubuntu:
  Fix Committed
Status in gtk4 source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  Ubuntu uses xdg-desktop-portal-gnome for the save dialog for snaps (like 
Firefox or Chromium). xdg-desktop-portal-gnome in Ubuntu 22.04 uses gtk4
  This issue also affects gnome-text-editor which uses gtk4 directly.

  Attempting to save a file to an empty folder won't work in many cases
  because the Save button is insensitive (unable to be clicked).

  Test Case
  -
  View this page with the Firefox or Chromium snaps.
  Press Ctrl+S to try to save this page.
  Navigate to a folder without any files in it. (It can have other folders in 
it.)
  The Save button should stay lit up.
  Save the file.

  Note that I wasn't able to reproduce the bug for bookmarked folders in
  the left sidebar so just navigate using the main view area.

  What Could Go Wrong
  
  This is a one-line bug fix from the stable gtk-4-6 branch targeted to 
directly fix this issue.

  Other Notes
  ---
  I do not believe we need to respin the Ubuntu 22.04 ISOs for this issue.
  I do request a 0-day SRU since this is a small high impact fix that affects 
the usability of the Firefox snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1969622/+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 1852911] Re: CriticalPowerAction=Suspend should be supported

[Pedro Côrte-Real]

I've attached a patch already. I've been running for over a year now
with no issues.

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  New
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+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 1959780] [NEW] package libreoffice-common (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debi

[pedro noriega]

Public bug reported:

no permite actualizar, ni desinstalar paquete

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libreoffice-common (not installed)
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Feb  1 17:24:04 2022
ErrorMessage: intentando sobreescribir `/usr/bin/soffice', que está también en 
el paquete openoffice-debian-menus 4.1.11-9808
InstallationDate: Installed on 2021-11-06 (87 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: libreoffice
Title: package libreoffice-common (not installed) failed to install/upgrade: 
intentando sobreescribir `/usr/bin/soffice', que está también en el paquete 
openoffice-debian-menus 4.1.11-9808
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package libreoffice-common (not installed) failed to install/upgrade:
  intentando sobreescribir `/usr/bin/soffice', que está también en el
  paquete openoffice-debian-menus 4.1.11-9808

Status in libreoffice package in Ubuntu:
  New

Bug description:
  no permite actualizar, ni desinstalar paquete

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-common (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Feb  1 17:24:04 2022
  ErrorMessage: intentando sobreescribir `/usr/bin/soffice', que está también 
en el paquete openoffice-debian-menus 4.1.11-9808
  InstallationDate: Installed on 2021-11-06 (87 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: libreoffice
  Title: package libreoffice-common (not installed) failed to install/upgrade: 
intentando sobreescribir `/usr/bin/soffice', que está también en el paquete 
openoffice-debian-menus 4.1.11-9808
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1959780/+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 1959695] [NEW] Xorg crash

[Pedro David Lopez Mendoza]

Public bug reported:

Una disculpa si me llego a equivocar, soy un usuario principiante.

Desde que instale "Ubuntu" (tanto en la versión LTS como en la actual)
la pantalla llega a tener un problema, se pone en negro y tiene lineas
que están parpadeando como si fueran guiones (___---) de color verde o
blanco tanto en el borde superior e inferior, una vez se pasa eso no
vuelve a dar imagen sin importar cuanto tiempo pase o haga cualquier
otra cosa y dejando como única opción el apagar el equipo de forma
forzada con el botón.

Hay varios puntos con respecto a esto:

-Esto sucede desde que se termina de instalar, ya sea con la instalación normal 
o la mínima e incluso sin mover ninguna configuración.
-Sucede después de iniciar el sistema e ingresar la contraseña de usuario, debo 
de forzar el apagado varias veces e iniciar sesión hasta que funciona, ademas 
no hay ni un numero de veces que deba hacerlo para que funcione o algo en 
especifico, parece que es completamente aleatorio si funciona o no.
-Sucede cuando el equipo entra en suspencion o cambio de usuario.
-En el momento de iniciar el sistema después de pasar el GRUB y antes de la 
pantalla que muestra los usuarios, en la pantalla que muestra la imagen de 
Lenovo, no se pierde la imagen pero por un segundo muestra una linea horizontal 
blanca aprox. a la altura de la rueda de carga.

-Adicional a esto aunque desconozco si es el mismo problema, al momento
de apagar el equipo, el sistema se cierra, lleva a la pantalla negra con
el logo de "Ubuntu", se apaga la pantalla, etc. pero no corta la
energía, el ventilador sigue funcionando y el equipo sigue encendido. De
igual forma esto no cambia hasta que se apaga forzosamente con el botón.

Eh intentado varias cosas sin exito dentro de las cuales están:

-Instalar los drivers Radeon descargados directamente de la pagina de AMD
-Instalar Xorg-edgers con el comando "sudo add-apt-repository 
ppa:xorg-edgers/ppa"

-Respecto al ultimo problema intente solucionarlo con
"GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force apm=power_off""

Nada de lo anterior funciono.

Agradezco la atención.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb  1 10:40:09 2022
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev e2) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a]
InstallationDate: Installed on 2022-01-28 (4 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 81ST
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic 
root=UUID=31c16c62-8a32-4efd-bccc-3e10e3b1b103 ro quiet splash acpi=force 
apm=power_off vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2021
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: AYCN25WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T31540WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-14AST
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrAYCN25WW:bd05/14/2021:br1.25:efr1.25:svnLENOVO:pn81ST:pvrLenovoIdeaPadS145-14AST:rvnLENOVO:rnLNVNB161216:rvrSDK0T31540WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-14AST:skuLENOVO_MT_81ST_BU_idea_FM_IdeaPadS145-14AST:
dmi.product.family: IdeaPad S145-14AST
dmi.product.name: 81ST
dmi.product.sku: LENOVO_MT_81ST_BU_idea_FM_IdeaPad S145-14AST
dmi.product.version: Lenovo IdeaPad S145-14AST
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug crash impish ubuntu wayland-session

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

Title:
  Xorg crash

Status in xorg 

[Desktop-packages] [Bug 1939999] Re: https://www.photodo.com/ filter option does not work

[Pedro]

Hi, thank you
After last update, http://www.photodo.com/browse-lenses, just works fine. Now 
it lets me apply filter option.
Best regards

** Changed in: firefox (Ubuntu)
   Status: New => Fix Released

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

Title:
  https://www.photodo.com/ filter option does not work

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  The same web page work in ubuntu 18.04 and does not work in ubuntu 20.04
  In 18.04 let me use the filter optión, f.e. manufacturer
  In 20.04 It doesn't matter which filter is selected, it doesn't work, it just 
doesn't filter 

  I'm not exactly an expert, sorry if it's silly, and thanks for your
  time

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 91.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a103037 F pulseaudio
   /dev/snd/pcmC0D0p:   a103037 F...m pulseaudio
   /dev/snd/controlC1:  a103037 F pulseaudio
  BuildID: 20210804193234
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 15 19:09:24 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-10-08 (2503 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  IpRoute:
   default via 192.168.1.3 dev eth0 proto dhcp metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.191 metric 100
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-1eb2066e-86ba-4d93-9ad5-058091171003
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=91.0/20210804193234 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-1eb2066e-86ba-4d93-9ad5-058091171003
   bp-91bb0303-c87a-4e15-8b22-df93e2150405
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-10-01 (318 days ago)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/193/+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 1939999] Re: https://www.photodo.com/ filter option does not work

[Pedro]

At http://www.photodo.com/browse-lenses, it lets me select each filter
option, but nothing happens, no matter which filter is selected, it
doesn't filter

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

Title:
  https://www.photodo.com/ filter option does not work

Status in firefox package in Ubuntu:
  New

Bug description:
  The same web page work in ubuntu 18.04 and does not work in ubuntu 20.04
  In 18.04 let me use the filter optión, f.e. manufacturer
  In 20.04 It doesn't matter which filter is selected, it doesn't work, it just 
doesn't filter 

  I'm not exactly an expert, sorry if it's silly, and thanks for your
  time

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 91.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a103037 F pulseaudio
   /dev/snd/pcmC0D0p:   a103037 F...m pulseaudio
   /dev/snd/controlC1:  a103037 F pulseaudio
  BuildID: 20210804193234
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 15 19:09:24 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-10-08 (2503 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  IpRoute:
   default via 192.168.1.3 dev eth0 proto dhcp metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.191 metric 100
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-1eb2066e-86ba-4d93-9ad5-058091171003
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=91.0/20210804193234 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-1eb2066e-86ba-4d93-9ad5-058091171003
   bp-91bb0303-c87a-4e15-8b22-df93e2150405
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-10-01 (318 days ago)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/193/+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 1939999] Re: https://www.photodo.com/ filter option does not work

[Pedro]

the filter option is at http://www.photodo.com/browse-lenses

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

Title:
  https://www.photodo.com/ filter option does not work

Status in firefox package in Ubuntu:
  New

Bug description:
  The same web page work in ubuntu 18.04 and does not work in ubuntu 20.04
  In 18.04 let me use the filter optión, f.e. manufacturer
  In 20.04 It doesn't matter which filter is selected, it doesn't work, it just 
doesn't filter 

  I'm not exactly an expert, sorry if it's silly, and thanks for your
  time

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 91.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a103037 F pulseaudio
   /dev/snd/pcmC0D0p:   a103037 F...m pulseaudio
   /dev/snd/controlC1:  a103037 F pulseaudio
  BuildID: 20210804193234
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 15 19:09:24 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-10-08 (2503 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  IpRoute:
   default via 192.168.1.3 dev eth0 proto dhcp metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.191 metric 100
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-1eb2066e-86ba-4d93-9ad5-058091171003
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=91.0/20210804193234 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-1eb2066e-86ba-4d93-9ad5-058091171003
   bp-91bb0303-c87a-4e15-8b22-df93e2150405
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-10-01 (318 days ago)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/193/+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 1939999] [NEW] https://www.photodo.com/ filter option does not work

[Pedro]

Public bug reported:

The same web page work in ubuntu 18.04 and does not work in ubuntu 20.04
In 18.04 let me use the filter optión, f.e. manufacturer
In 20.04 It doesn't matter which filter is selected, it doesn't work, it just 
doesn't filter 

I'm not exactly an expert, sorry if it's silly, and thanks for your time

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 91.0+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
Uname: Linux 5.4.0-80-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  a103037 F pulseaudio
 /dev/snd/pcmC0D0p:   a103037 F...m pulseaudio
 /dev/snd/controlC1:  a103037 F pulseaudio
BuildID: 20210804193234
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 15 19:09:24 2021
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2014-10-08 (2503 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
IpRoute:
 default via 192.168.1.3 dev eth0 proto dhcp metric 100 
 169.254.0.0/16 dev eth0 scope link metric 1000 
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.191 metric 100
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-1eb2066e-86ba-4d93-9ad5-058091171003
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
PrefSources: prefs.js
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=91.0/20210804193234 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs:
 bp-1eb2066e-86ba-4d93-9ad5-058091171003
 bp-91bb0303-c87a-4e15-8b22-df93e2150405
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to focal on 2020-10-01 (318 days ago)
dmi.bios.date: 12/01/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.70
dmi.board.name: FM2A75M-DGS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

Title:
  https://www.photodo.com/ filter option does not work

Status in firefox package in Ubuntu:
  New

Bug description:
  The same web page work in ubuntu 18.04 and does not work in ubuntu 20.04
  In 18.04 let me use the filter optión, f.e. manufacturer
  In 20.04 It doesn't matter which filter is selected, it doesn't work, it just 
doesn't filter 

  I'm not exactly an expert, sorry if it's silly, and thanks for your
  time

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 91.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  a103037 F pulseaudio
   /dev/snd/pcmC0D0p:   a103037 F...m pulseaudio
   /dev/snd/controlC1:  a103037 F pulseaudio
  BuildID: 20210804193234
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 15 19:09:24 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-10-08 (2503 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  IpRoute:
   default via 192.168.1.3 dev eth0 proto dhcp metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.191 metric 100
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-1eb2066e-86ba-4d93-9ad5-058091171003
  PrefErrors: Unexpected character ',' before 

[Desktop-packages] [Bug 1933310] [NEW] power_saving_bluetooth_toggle_button disables Bluetooth instead of power saving

[Pedro Nunes]

Public bug reported:

On the Settings window Power/Power Saving/Bluetooth there is a toggle button to 
turn off/on for power saving.
but what it does, if its on the BT is on, if you toggle it to off, the BT gets 
turned off instantly.
And if you go to Bluetooth devices and turn BT on, and you go back to power 
saving window, you see the toggle button turned on.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.5-0ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-59-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 23 08:54:49 2021
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2021-03-30 (84 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  power_saving_bluetooth_toggle_button disables Bluetooth instead of
  power saving

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

Bug description:
  On the Settings window Power/Power Saving/Bluetooth there is a toggle button 
to turn off/on for power saving.
  but what it does, if its on the BT is on, if you toggle it to off, the BT 
gets turned off instantly.
  And if you go to Bluetooth devices and turn BT on, and you go back to power 
saving window, you see the toggle button turned on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 23 08:54:49 2021
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2021-03-30 (84 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1933310/+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 1852911] Re: CriticalPowerAction=Suspend should be supported

[Pedro Côrte-Real]

I've once again lost my open session because upower has decided a
shutdown is a sensible thing to do instead of just suspending and
allowing me to just find a charger. Please consider this an actual bug
and not just a "Wishlist" item. It's something that deeply frustrates
users continuously. Orderly shutdowns are a relic of the past. Suspend
or just dieing from lack of battery are both much better options for a
laptop. That upstream has decided to force this behavior is unfortunate
but the patches are simple enough.

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  New
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+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 1852911] Re: CriticalPowerAction=Suspend should be supported

[Pedro Côrte-Real]

You may also want to consider just having Suspend be a fallback option
before PowerOff. These days users are much more likely to have a laptop
that suspends properly and prefer that to happen and just quickly grab a
charger and continue instead of having their computer do a full
poweroff.

** Patch added: "Patch to make Suspend a fallback option before PowerOff"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1852911/+attachment/5463642/+files/upower-suspend.patch

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  New
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+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 1852911] Re: CriticalPowerAction=Suspend should be supported

[Pedro Côrte-Real]

Please include at least this patch on the package. It allows setting
Suspend as the action but does nothing if the user hasn't explicitly
done that.

** Patch added: "Patch that keeps the defaults unchanged but allows the setting 
in the config file"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1852911/+attachment/5463625/+files/upower-suspend-defaults-unchanged.patch

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  New
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+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 1911024] [NEW] segfault crash after fresh restart

[Luís Pedro Carvalho]

Public bug reported:

segfault not located in a known VMA region (needed readable region)!
destination rdi ok

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
Uname: Linux 5.10.4-051004-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 11 15:52:40 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-12-30 (12 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  segfault crash after fresh restart

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  segfault not located in a known VMA region (needed readable region)!
  destination rdi ok

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  Uname: Linux 5.10.4-051004-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 15:52:40 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-12-30 (12 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  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/1911024/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Pedro Ribeiro]

More details about the backlight control can be found in
https://forums.developer.nvidia.com/t/legion-5-no-backlight-control-in-
discrete-graphics-mode/160292/11

If you have any questions please create a topic in the nvidia forums or
open a new bug!

/thread hijack off

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  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: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Pedro Ribeiro]

Again my apologies to everyone for hijacking this thread, But since
people are asking, and I was able to solve the backlight problem after
days of pain, here are the instructions. Two caveats though:

- you need to have the laptop in "Discrete" mode in the BIOS (in my experience, 
Hybrid mode gives little battery life advantage, even in Windows)
- the instructions below are for Debian, but the only different thing to have 
in mind is the /experimental release in the apt install command, which should 
be adapted to the Ubuntu release you want to install the drivers from

1. make sure that you remove all nvidia stuff:
apt --purge remove nvidia*
(this includes any nvidia configuration files in /etc/X11/xorg.conf.d)

2. install the proprietary nvidia driver version you want (replace experimental 
with the target release)
sudo apt install libegl-nvidia0/experimental 
libgl1-nvidia-glvnd-glx/experimental libglx-nvidia0/experimental 
libnvidia-eglcore/experimental libnvidia-glcore/experimental 
libnvidia-ml1/experimental nvidia-alternative/experimental 
nvidia-driver/experimental nvidia-driver-bin/experimental 
nvidia-driver-libs/experimental nvidia-egl-common/experimental 
nvidia-egl-icd/experimental nvidia-kernel-dkms/experimental 
nvidia-kernel-support/experimental nvidia-modprobe/experimental 
nvidia-vdpau-driver/experimental xserver-xorg-video-nvidia/experimental 
libgles-nvidia1/experimental libgles-nvidia2/experimental 
nvidia-vulkan-icd/experimental libnvidia-cfg1/experimental 
libcuda1/experimental libnvcuvid1/experimental libnvidia-encode1/experimental 
nvidia-opencl-icd/experimental nvidia-smi/experimental  
libnvidia-cbl/experimental libnvidia-rtcore/experimental 
nvidia-cuda-mps/experimental libnvidia-ptxjitcompiler1/experimental 
libnvidia-compiler/experimental libnvidia-glvkspirv/experimental nvidia-settings

3. create a file /etc/X11/xorg.conf.d/21-nvidia-brightness.conf with the 
following contents:
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "RegistryDwords" "EnableBrightnessControl=1"
EndSection

4. reboot and backlight control should be working!

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the 

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Pedro Ribeiro]

Don't want to hijack this thread, but has anyone here with a Legion 5
(AMD version) has gotten the backlight working in Discrete graphics mode
(only the nvidia GPU enabled)?

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  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: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: 

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Pedro Ribeiro]

@Azizkhan (injkgz)

I don't think it is, I believe the for-next branch in linux-gpio will
only be integrated in 5.11, but @Coiby Xu (coiby) should be able to
confirm that.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  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: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: 

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Pedro Ribeiro]

To be specific, this is the branch I built:
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/log/?h=for-next

The kernel I built had 0f2c7af45d7eef8455d7ad39c5326229bf19a2ed as the
latest commit.

I have a Legion 5 15ARH05H (slightly different than 15ARH05).

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  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: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Pedro Ribeiro]

@Coiby Xu (coiby)

I build the next branch of linux-gpio (which contains the patch you mentioned 
in #251), and the trackpad works just fine without the hid polling on the 
kernel command line.
You can contact me if you'd like further testing, my email is 
pedrib_at_gmail_dot_com

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  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: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 

[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

[Pedro Miguel Baptista Machado]

I solved the problem with
$ sudo killall -9 gnome-shell

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1824874/+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 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time

[Pedro Palhares]

I have updated to 20.10 and can confirm disabling scroll lock workaround
is still working.

Another thing i've just realized is without this hack, there is a huge
lag during lock/unlock/login animations. Commenting scroll lock line in
/usr/share/X11/xkb/symbols/br made animations a lot better.

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

Title:
  Desktop briefly becomes unresponsive when typing on 2 keyboards at the
  same time

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates
  from the repos.

  If I connect 2 (or more) keyboards to my computer and type on both at
  the same time, the desktop briefly becomes unresponsive. More
  keypresses increase the time of unresponsiveness.

  E.g. when typing a full sentence in gedit or the terminal, only very
  few characters show up on the screen (I guess up until something is
  pressed on both keyboards at the same time), then everything freezes.
  Then after a while (some seconds), all the characters show up. And the
  desktop becomes responsive again.

  Symptoms: During the freeze, windows stop updating their content. If
  seconds are enabled on the clock at the top middle, these freeze too.
  But I'm still able to move the mouse pointer around during the freeze
  without any problems.

  The back story:

  I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and
  quickly noticed the issue. But initiallly I thought it was an issue
  with the keyboard, and the problem wasn't that bad. But as I've gotten
  more used to the keyboard since yesterday and started picking up a
  proper typing speed, things got worse.

  The keyboard is technically two separate cabled USB keyboards each
  with only about half of they keys of a normal keyboard (or at least
  that's very much my impression).

  After getting the suspicion that this was a software issue, not a
  hardware issue, I tried typing on my old Logitech keyboard (Unifying
  Receiver) along with one of the R-Go halves: Same issue. Then I tried
  each of the halves without the other (as in "single" keyboard typing):
  No issue. Then I connected another Logitech keyboard (separate UR),
  typed on both Logitechs: Same issue.

  Some further observations:

  1) Nothing of significance in my syslog.
  2) If I drop to a non-graphical shell, there's no problem. I suspect this 
issue is related to X.org or Gnome, but I'm in no position to say anything 
credible about that.
  3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS 
machine.

  Let me know if there are any logs I can provide or things I can run to
  produce useful debug output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[PEDRO PORTO BUARQUE DE GUSMAO]

Hi,

Can I do this with Secure Boot on?

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  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: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  

[Desktop-packages] [Bug 1889102] Re: [ubuntu-dock] App grid has too many page dots on right

[Pedro Ryan]

Version 69 of Dash to Dock fixed this bug, at least in my tests. 
Can someone else test if it works? 

Disable Ubuntu Dock in Extensions app and install version 69 of Dash to
Dock in extensions.gnome.com

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

Title:
  [ubuntu-dock] App grid has too many page dots on right

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  I have noticed a bug with the applications menu. I am having a weird
  issue with adding apps into folders on the menu. If I try opening a
  folder, the entire screen glitches out and the bar on the right-hand
  size showing how many pages are on the menu show more pages than there
  actually is.

  Occasionally if I try adding or removing an app to a folder, the
  entire system freezes. The only way I am able to get things back to
  normal is a forced restart by holding down the power button.

  The only way I have been able to not come across this issue is to have
  no folders in my menu at all, which took a while as the system kept
  crashing during the process. However, I am no longer experiencing the
  issue with no folders, but it returns when I try creating a folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 27 16:31:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3f1a]
  InstallationDate: Installed on 2020-07-22 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56b2 IMC Networks Integrated Camera
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 004: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge 
Mini Keyboard]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81VV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=1664842e-9af5-44b6-a3c8-f9235f094044 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CUCN21WW(V1.10)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32776 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrCUCN21WW(V1.10):bd05/27/2020:svnLENOVO:pn81VV:pvrLenovoIdeaPadS340-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32776WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14IIL:
  dmi.product.family: IdeaPad S340-14IIL
  dmi.product.name: 81VV
  dmi.product.sku: LENOVO_MT_81VV_BU_idea_FM_IdeaPad S340-14IIL
  dmi.product.version: Lenovo IdeaPad S340-14IIL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889102/+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 214786] Re: Apple USB ISO keyboard has incorrectly swapped keys

[Pedro A. Aranda]

After posting, I tried 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/214786/comments/78
and it worked for me on a Spanish USB apple keyboard.

Currently I have my laptop's and the USB Apple keyboard working
correctly _and_ simultaneously

Just my .2 cents

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

Title:
  Apple USB ISO keyboard has incorrectly swapped keys

Status in Mactel Support:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel to version 2.6.24-12.22 two keys are now
  swapped on my Apple USB aluminium keyboard with danish layout. Now the
  keys "<" and "½" are swapped and no longer matches the actual print on
  the keycaps.

  The error is isolated to the following commit:
  http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
  hardy.git;a=commitdiff;h=efb3031b446d441dca5b10619503ac0bba7f9748

  This commit introduced a key swapping for all "ISO" type Apple
  keyboards. In my case this swapping is incorrect, and generally it
  seems like a very bad idea to perform hard coded locale specific key
  mapping in kernel space as this is also done several places in user
  space.

  The included patch reverts the behavior to the default that matches
  the keycap printing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mactel-support/+bug/214786/+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 214786] Re: Apple USB ISO keyboard has incorrectly swapped keys

[Pedro A. Aranda]

I'm having this issue with a Spanish USB Mac keyboard. Is it really so
difficult to detect when you have a Mac keyboard connected and/or
disconnected? Can't anything be done with hotplug, udev, etc. ?

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

Title:
  Apple USB ISO keyboard has incorrectly swapped keys

Status in Mactel Support:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel to version 2.6.24-12.22 two keys are now
  swapped on my Apple USB aluminium keyboard with danish layout. Now the
  keys "<" and "½" are swapped and no longer matches the actual print on
  the keycaps.

  The error is isolated to the following commit:
  http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
  hardy.git;a=commitdiff;h=efb3031b446d441dca5b10619503ac0bba7f9748

  This commit introduced a key swapping for all "ISO" type Apple
  keyboards. In my case this swapping is incorrect, and generally it
  seems like a very bad idea to perform hard coded locale specific key
  mapping in kernel space as this is also done several places in user
  space.

  The included patch reverts the behavior to the default that matches
  the keycap printing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mactel-support/+bug/214786/+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 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition

[Pedro Guimarães]

Using focal desktop and I am seeing the same issue.
I was seeing tracker-store and tracker-miner-fs taking an entire core of my 
notebook.
Tried: tracker reset --hard and reboot.
Did not work for me.

Only effective solution was to disable search engine on "Settings".

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

Title:
  tracker-store uses 100% cpu and fills all the disk space in home
  partition

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I recently noticed that several tracker related programs were using
  100% cpu on my system and in particular tracker-store filled up
  completely all the available disk space in my home partition.

  I rerun tracker-preferences to make sure that indexing would not
  proceed if less than 20% of free space is available, but it seems that
  tracker-store ignores it.  After I noticed that I had left only 44Kb
  free on the home partition,  I deleted the cache from another program
  and I noticed that tracker-store filled up again the disk space that I
  freed few minutes before.

  This is the content of my .cache/tracker/ directory:
  totale 772068
  -rw-r--r-- 1 eclipse eclipse  3072 2011-06-26 22:56 contents.db
  -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt
  -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt
  -rw-r--r-- 1 eclipse eclipse  3072 2010-12-05 21:29 email-contents.db
  -rw-r--r-- 1 eclipse eclipse  3072 2009-05-06 19:16 email-fulltext.db
  -rw-r--r-- 1 eclipse eclipse   2359292 2011-06-26 22:54 email-index.db
  -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db
  -rw-r--r-- 1 eclipse eclipse  17062912 2011-06-26 19:30 file-contents.db
  -rw-r--r-- 1 eclipse eclipse  15014912 2010-01-12 20:26 file-fulltext.db
  -rw-r--r-- 1 eclipse eclipse  75609207 2011-06-26 22:54 file-index.db
  -rw-r--r-- 1 eclipse eclipse  37027840 2011-06-26 19:31 file-meta.db
  -rw--- 1 eclipse eclipse   1180048 2009-05-05 22:57 file-update-index.db
  -rw-r--r-- 1 eclipse eclipse  28376064 2011-10-20 09:34 fulltext.db
  -rw-r--r-- 1 eclipse eclipse  1024 2012-01-04 21:24 meta.db
  -rw-r--r-- 1 eclipse eclipse   4653056 2012-01-04 21:26 meta.db-shm
  -rw-r--r-- 1 eclipse eclipse 608064304 2012-01-04 21:26 meta.db-wal
  -rw-r--r-- 1 eclipse eclipse11 2011-12-12 04:02 
miner-applications-locale.txt
  -rw-r--r-- 1 eclipse eclipse345110 2012-01-04 21:24 ontologies.gvdb

  and this is  how much space I have left on my home partition after I KILLED 
the tracker-store process:
  /dev/sda8  31G   30G  418M  99% /home
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  Package: tracker 0.10.24-1build2
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=it_IT:it:en_GB:en
   PATH=(custom, user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric
  Uname: Linux 3.0.0-14-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-20 (76 days ago)
  UserGroups: adm admin audio cdrom dip fuse lpadmin plugdev polkituser 
pulse-access sambashare src video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/911981/+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 1879406] [NEW] Dark mode on gedit - unable to see text

[Pedro Galvao]

Public bug reported:

Unable to see current line of text on gedit when in dark mode and with
default gedit setting to highlight current line. Highilght is the same
colour as the text.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gedit 3.36.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 18 22:20:55 2020
InstallationDate: Installed on 2020-05-17 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Dark mode on gedit - unable to see text

Status in gedit package in Ubuntu:
  New

Bug description:
  Unable to see current line of text on gedit when in dark mode and with
  default gedit setting to highlight current line. Highilght is the same
  colour as the text.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gedit 3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 22:20:55 2020
  InstallationDate: Installed on 2020-05-17 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1879406/+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 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders

[Pedro Ryan]

I couldn't reproduce the bug without Ubuntu Dock.

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

Title:
  Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside
  of app icon folders

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  Bug: Gnome shell while opening app drawer, clicking on an app folder
  and clicking on the blank area freezes gnome shell and it makes the
  session completely unusable and non recoverable.

  How to reproduce:  1- Click 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.

  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  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/1872268/+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 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders

[Pedro Ryan]

In my experience, when I open an app and meanwhile open and close a
folder the GNOME freezes.

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

Title:
  Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside
  of app icon folders

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  Bug: Gnome shell while opening app drawer, clicking on an app folder
  and clicking on the blank area freezes gnome shell and it makes the
  session completely unusable and non recoverable.

  How to reproduce:  1- Click 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.

  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  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/1872268/+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 1870847] Re: App grid has too many page dots on right

[Pedro Ryan]

That's odd... for me, with Ubuntu Dock v68 in GNOME 3.36.1, the bug no
longer happen. But when I updated to GNOME 3.36.2, the bug appeared
again.

Does it happen to someone else? Does that even make sense?

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

Title:
  App grid has too many page dots on right

Status in GNOME Shell:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock source package in Groovy:
  Fix Released

Bug description:
  When I click the "Show Applications" button in the lower left, it brings up a 
matrix of application icons, which takes a page and a half.  There should be 
two dots on the right to match the two pages, but instead there are * dots.  
Moving up and down, the first and second dots highlight to show which page I am 
on.  But only the top dot, and the bottom two, can be clicked on to change the 
page.
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  final beta April 3
  nautilus:
Installed: 1:3.36.1-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:35:20 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gnome-shell 3.36.0-2ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1870847/+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 1870847] Re: App grid has too many page dots on right

[Pedro Ryan]

This bug is fixed in groovy, but shouldn't it be fixed in focal?

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

Title:
  App grid has too many page dots on right

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  When I click the "Show Applications" button in the lower left, it brings up a 
matrix of application icons, which takes a page and a half.  There should be 
two dots on the right to match the two pages, but instead there are * dots.  
Moving up and down, the first and second dots highlight to show which page I am 
on.  But only the top dot, and the bottom two, can be clicked on to change the 
page.
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  final beta April 3
  nautilus:
Installed: 1:3.36.1-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:35:20 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gnome-shell 3.36.0-2ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1870847/+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 1870847] Re: App grid has too many page dots on right

[Pedro Ryan]

I disabled the Ubuntu Dock extension using the Gnome Extensions app and tried 
to reproduce the bug, and the bug didn't happen anymore.
When I installed the Dash to Dock extension by the Gnome Extensions site, and 
tried to reproduce the error, nothing wrong happened.

I think that the bug is caused by the dock, and the version 68 of Dash
to Dock fixed this bug. The Ubuntu dock is still in version 67.

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

Title:
  App grid has too many page dots on right

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  When I click the "Show Applications" button in the lower left, it brings up a 
matrix of application icons, which takes a page and a half.  There should be 
two dots on the right to match the two pages, but instead there are * dots.  
Moving up and down, the first and second dots highlight to show which page I am 
on.  But only the top dot, and the bottom two, can be clicked on to change the 
page.
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  final beta April 3
  nautilus:
Installed: 1:3.36.1-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:35:20 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gnome-shell 3.36.0-2ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1870847/+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 1871913] Re: super key does not work with secondary keyboard layout

[Pedro Teixeira]

I also tried different configs in gnome-tweaks for the Alt/Win key
behavior (under Additional Layout Options) but it did not seem to make
any difference.

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

Title:
  super key does not work with secondary keyboard layout

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When keyboard layout is set on Persian, pressing Super does not open
  Activities overview. It just works when the input is set on English.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 00:02:55 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-01 (159 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1871913/+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 1871913] Re: super key does not work with secondary keyboard layout

[Pedro Teixeira]

I am facing the same problem. 
Can confirm  that only input 1 works regardless of language. And that keyboard 
shortcuts with Super work regardless.

Here is my extra 2 cents:

When I go into 'Show keyboard layout' to see which keypresses are registered, 
the left super key is not registered but the right one is.
 
One more thing: if I change the activities overview to be triggered by the 
right super key instead of left (via gnome-tweaks), then the left super key 
will be registered but the right super key will not.

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

Title:
  super key does not work with secondary keyboard layout

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When keyboard layout is set on Persian, pressing Super does not open
  Activities overview. It just works when the input is set on English.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 00:02:55 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-01 (159 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1871913/+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 1874557] [NEW] super key works in shortcuts but does not show activities overview

[Pedro Teixeira]

Public bug reported:

Super key works in normal keyboard shortcuts but not by itself whenever
the input method is not the first one in the priority list. When testing
keys with the keyboard layout on screen all keys are registered but the
super key that is configured to display the activities overview.

When the left Super is configured to show the activities overview, the
left Super key is ignored. If the right Super is assigned to that
function (via gnome-tweaks) then the left one will be registered but the
right one will not.

Language does not matter. I tried having the keyboard in pt-pt then en-
us, they both exhibit the issue according to where in the priority I
order them. Input 1 always works and the others do not.

Issue started with update to gnome-shell 3.36.1 (via 20.04 LTS update).

Mentioned in gnome-project
https://gitlab.gnome.org/GNOME/mutter/-/issues/1144

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 23 23:57:42 2020
DisplayManager: gdm3
InstallationDate: Installed on 2016-08-25 (1337 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)

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


** Tags: amd64 apport-bug focal

** Attachment removed: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874557/+attachment/5358743/+files/GsettingsChanges.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/1874557

Title:
  super key works in shortcuts but does not show activities overview

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Super key works in normal keyboard shortcuts but not by itself
  whenever the input method is not the first one in the priority list.
  When testing keys with the keyboard layout on screen all keys are
  registered but the super key that is configured to display the
  activities overview.

  When the left Super is configured to show the activities overview, the
  left Super key is ignored. If the right Super is assigned to that
  function (via gnome-tweaks) then the left one will be registered but
  the right one will not.

  Language does not matter. I tried having the keyboard in pt-pt then
  en-us, they both exhibit the issue according to where in the priority
  I order them. Input 1 always works and the others do not.

  Issue started with update to gnome-shell 3.36.1 (via 20.04 LTS
  update).

  Mentioned in gnome-project
  https://gitlab.gnome.org/GNOME/mutter/-/issues/1144

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 23 23:57:42 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-08-25 (1337 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874557/+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 1874557] Re: super key works in shortcuts but does not show activities overview

[Pedro Teixeira]

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874557/+attachment/5358747/+files/GsettingsChanges.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/1874557

Title:
  super key works in shortcuts but does not show activities overview

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Super key works in normal keyboard shortcuts but not by itself
  whenever the input method is not the first one in the priority list.
  When testing keys with the keyboard layout on screen all keys are
  registered but the super key that is configured to display the
  activities overview.

  When the left Super is configured to show the activities overview, the
  left Super key is ignored. If the right Super is assigned to that
  function (via gnome-tweaks) then the left one will be registered but
  the right one will not.

  Language does not matter. I tried having the keyboard in pt-pt then
  en-us, they both exhibit the issue according to where in the priority
  I order them. Input 1 always works and the others do not.

  Issue started with update to gnome-shell 3.36.1 (via 20.04 LTS
  update).

  Mentioned in gnome-project
  https://gitlab.gnome.org/GNOME/mutter/-/issues/1144

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 23 23:57:42 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-08-25 (1337 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874557/+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 1866250] [NEW] nautilus crashes under wayland when trying to unmount an external drive

[Pedro Côrte-Real]

Public bug reported:

I can 100% reliably crash nautilus when running under a sway session.
The steps to reproduce it are simple:

1. Connect an external drive and mount it by browsing to it in nautilus
2. Open a terminal and cd into the drive mount
3. Press the unmount icon for the drive in nautilus

At this point nautilus 100% reliably crashes. It will not crash if the
drive is not being used. Looking at the backtrace it seems it is somehow
trying to do X calls when running under wayland. Here's the trace:

(gdb) bt
#0  0x in  ()
#1  0x77eb3393 in g_hash_table_lookup_node (hash_return=, key=0x60, hash_table=0x561e8000) at ../../../glib/ghash.c:473
#2  0x77eb3393 in g_hash_table_lookup (hash_table=0x561e8000, 
key=key@entry=0x60) at ../../../glib/ghash.c:1509
#3  0x776d35b8 in lookup_cached_xatom (atom=0x60, 
display=0x561b1040 [GdkWaylandDisplay]) at 
../../../../../gdk/x11/gdkproperty-x11.c:76
#4  0x776d35b8 in lookup_cached_xatom (atom=0x60, 
display=0x561b1040 [GdkWaylandDisplay]) at 
../../../../../gdk/x11/gdkproperty-x11.c:67
#5  0x776d35b8 in gdk_x11_atom_to_xatom_for_display (atom=0x60, 
display=0x561b1040 [GdkWaylandDisplay]) at 
../../../../../gdk/x11/gdkproperty-x11.c:109
#6  0x776d35b8 in gdk_x11_atom_to_xatom_for_display 
(display=0x561b1040 [GdkWaylandDisplay], atom=0x60) at 
../../../../../gdk/x11/gdkproperty-x11.c:96
#7  0x77b3fc8d in _gtk_mount_operation_lookup_context_get 
(display=0x561b1040 [GdkWaylandDisplay]) at 
../../../../gtk/gtkmountoperation-x11.c:534
#8  0x779cf800 in update_process_list_store (processes=0x569ce670, 
list_store=, mount_operation=) at 
../../../../gtk/gtkmountoperation.c:1286
#9  0x779cf800 in gtk_mount_operation_show_processes_do_gtk 
(choices=0x0, processes=0x569ce670, message=0x56930a90 "", 
op=) at ../../../../gtk/gtkmountoperation.c:1679
#10 0x779cf800 in gtk_mount_operation_show_processes
(op=, message=message@entry=0x567dfac0 "Volume is 
busy\nOne or more applications are keeping the volume busy.", 
processes=processes@entry=0x569ce670, choices=choices@entry=0x56578420)
at ../../../../gtk/gtkmountoperation.c:1704
#11 0x77329b5b in _g_cclosure_marshal_VOID__STRING_BOXED_BOXEDv
(closure=0x569572e0, return_value=, instance=, args=, marshal_data=, n_params=, param_types=0x569e27f0) at ../../../gio/gmarshal-internal.c:2059
#12 0x7725c936 in _g_closure_invoke_va (closure=0x569572e0, 
return_value=0x0, instance=0x569d32d0, args=0x7fffd1f8, n_params=3, 
param_types=0x569e27f0) at ../../../gobject/gclosure.c:873
#13 0x7727936c in g_signal_emit_valist 
(instance=instance@entry=0x569d32d0, signal_id=signal_id@entry=566, 
detail=detail@entry=0, var_args=var_args@entry=0x7fffd1f8) at 
../../../gobject/gsignal.c:3306
#14 0x77279fa9 in g_signal_emit_by_name (instance=0x569d32d0, 
detailed_signal=0x7fffdae3a1d2 "show-processes") at 
../../../gobject/gsignal.c:3493
#15 0x7fffdae33fa8 in  () at 
/usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
#16 0x7fffdae385a8 in  () at 
/usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
#17 0x7616c81e in ffi_call_unix64 () at ../src/x86/unix64.S:76
#18 0x7616c1ef in ffi_call (cif=cif@entry=0x7fffd660, 
fn=fn@entry=0x7fffdae38530, rvalue=, 
avalue=avalue@entry=0x7fffd570) at ../src/x86/ffi64.c:525
Python Exception  There is no member named v_pointer.: 
#22 0x772783ea in #23 0x7fffdae2d7e5 in  () at 
/usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
#27 0x772799b3 in  (instance=instance@entry=0x562b6f70, 
signal_id=, detail=detail@entry=0) at 
../../../gobject/gsignal.c:3453
#24 0x7725c6e2 in g_closure_invoke (closure=0x557441a0, 
return_value=0x0, n_param_values=4, param_values=0x7fffdbe0, 
invocation_hint=0x7fffdb60) at ../../../gobject/gclosure.c:810
#25 0x7726fcc6 in signal_emit_unlocked_R
(node=node@entry=0x557441d0, detail=detail@entry=0, 
instance=instance@entry=0x562b6f70, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffdbe0)
at ../../../gobject/gsignal.c:3679
#26 0x77279327 in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffdde0) at ../../../gobject/gsignal.c:3397
#28 0x773bc638 in on_signal_received
(connection=, sender_name=0x7fffe4014460 ":1.39", 
object_path=, interface_name=, 
signal_name=0x7fffe401b220 "MountOpShowProcesses", parameters=0x569d7670, 
user_data=0x55a52610) at ../../../gio/gdbusproxy.c:924
#29 0x773ab118 in emit_signal_instance_in_idle_cb (data=0x7fffe401fe60) 
at ../../../gio/gdbusconnection.c:3747
#30 0x77ec571e in g_main_dispatch (context=0x55745480) at 

[Desktop-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

[Pedro Principeza]

Changed the status to New, since I was still able to reproduce the issue
on Bionic, using the "patched" network-manager version.

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

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.
   
  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
 valid_lft 353sec preferred_lft 353sec
  inet6 fe80::ff:feb3:b522/64 scope link 
 valid_lft forever preferred_lft forever

  
  
+++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in 
/var/log/syslog
  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute 
 valid_lft forever preferred_lft forever

  
  ==> Correct LP-Package need to be assigned...!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

[Pedro Principeza]

Hi, all.  I'm afraid I'll need to reopen this bug.

I was able to reproduce the issue on Bionic, using network-manager
1.10.6-2ubuntu1.2.  However, when testing this on Eoan, using network-
manager 1.20.4-2ubuntu2, I didn't reproduce the behaviour.

The steps one takes to reproduce the issue, either on a s390 system or
x86 (the issue is reproducible regardless of the platform) is:

1.) Create the bond interface with:
nmcli conn add type bond con-name  ifname  ipv4.method disabled 
ipv6.method ignore

2.) Modify it to so set a manual IPv6 Address and auto-assign IPv4:
nmcli c m  bond.options " mode=active-backup, downdelay=0 , miimon=100 , 
updelay=0 , fail_over_mac=none , num_grat_arp=0 , primary_reselect=always " 
connection.interface-name  ipv4.method auto ipv4.gateway "" 
ipv6.method manual 802-3-ethernet.mac-address "" ipv4.routes "" connection.id 
 ipv6.never-default no ipv4.addresses "" ipv6.addresses 


3.) Add the two slave ethernet devices, and change them with:

nmcli c m  connection.id  connection
.interface-name 
802-3-ethernet.s390-subchannels 
802-3-ethernet.s390-nettype qeth connection.autoconnect yes
802-3-ethernet.mac-address "" ipv4.method disabled ipv6.method ignore
802-3-ethernet.s390-options portno=

^ For repro steps on amd64 or ppc64, the s390-* parameters can be
removed from the command.

4.) Add the two slave ethernet devices to the bond:

nmcli c m  802-3-ethernet.mac-address "" connection.master
 connection.slave-type bond

[ . . . ]

You'll see that, on Bionic, the bond interface isn't assigned an IPv4
address.  On Eoan, an IPv4 address is assigned as expected.

I have reviewed network-manager's changelog [1], but I didn't find any
smoking guns that could've solved the issue, hence the re-opening of the
bug.

Let me know if further evidence is needed to proceed.  Thanks!

[1] https://changelogs.ubuntu.com/changelogs/pool/main/n/network-manager
/network-manager_1.20.4-2ubuntu2/changelog

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.
   
  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
 valid_lft 353sec preferred_lft 353sec
  inet6 fe80::ff:feb3:b522/64 scope link 
 valid_lft forever preferred_lft forever

  
  
+++
  Bond interface, ipv4 

[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported

[Pedro Côrte-Real]

By the way the actual discussion seems to be this one:

https://gitlab.freedesktop.org/upower/upower/issues/59

And this is the unmerged PR with the simple patch:

https://gitlab.freedesktop.org/upower/upower/merge_requests/11

** Bug watch added: gitlab.freedesktop.org/upower/upower/issues #59
   https://gitlab.freedesktop.org/upower/upower/issues/59

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  Unknown
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+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 1852911] Re: CriticalPowerAction=Suspend should be supported

[Pedro Côrte-Real]

Upstream seems to be ignoring the user's wishes. Would Ubuntu be willing
to take the patch?

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  Unknown
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+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 1852911] [NEW] CriticalPowerAction=Suspend should be supported

[Pedro Côrte-Real]

Public bug reported:

The action to take when the battery is critical can only be one of the
following:

# Possible values are:
# PowerOff
# Hibernate
# HybridSleep

Adding Suspend to that list makes perfect sense. My laptop is currently
powering off on low power which is useless as I'll be losing my work
anyway. Might as well suspend and allow me to notice that and connect a
charger. If the thinking is that suspend uses power I can set a high
enough threshold to give me some margin.

The failovers are:

# If HybridSleep isn't available, Hibernate will be used
# If Hibernate isn't available, PowerOff will be used

I'd argue Suspend should actually come before PowerOff in that list. For
most laptop users having their computer suspend because they didn't
notice the battery was running out is very easy to fix and takes no
time. They'll just connect the charger. If however the computer needs to
be completely rebooted, not only does that take a lot more time it will
very likely cause lost work.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: upower 0.99.10-1
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.3
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov 17 14:32:13 2019
InstallationDate: Installed on 2019-05-09 (191 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco wayland-session

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in upower package in Ubuntu:
  New

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1852911/+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 1846505] [NEW] package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: problemas com dependências - a deixar triggers por processar

[Pedro Ivo Marques e Silva Brito]

Public bug reported:

Erro ao instalar o pacote.
O que fazer?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: desktop-file-utils 0.22-1ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu Oct  3 11:18:46 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
ErrorMessage: problemas com dependências - a deixar triggers por processar
InstallationDate: Installed on 2019-06-21 (103 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.26
SourcePackage: desktop-file-utils
Title: package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: 
problemas com dependências - a deixar triggers por processar
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: desktop-file-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade:
  problemas com dependências - a deixar triggers por processar

Status in desktop-file-utils package in Ubuntu:
  New

Bug description:
  Erro ao instalar o pacote.
  O que fazer?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: desktop-file-utils 0.22-1ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Oct  3 11:18:46 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: problemas com dependências - a deixar triggers por processar
  InstallationDate: Installed on 2019-06-21 (103 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.26
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: 
problemas com dependências - a deixar triggers por processar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1846505/+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 1809880] Re: Fullscreen vlc sometimes freezes until you Alt-Tab away and back from the window

[Pedro Côrte-Real]

This is most likely a vlc bug and should be reassigned to it. I am
experiencing it in VLC under sway so unless the same bug exists across
sway and mutter it's probably a vlc thing.

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

Title:
  Fullscreen vlc sometimes freezes until you Alt-Tab away and back from
  the window

Status in mutter package in Ubuntu:
  New

Bug description:
  There seems to be a bug, which I assume is in mutter, when viewing
  multiple vlc videos fullscreen. The steps to reproduce are simple:

  1. Open a bunch of videos in vlc in sequence with something like "vlc *" in a 
directory full of video files
  2. Press N to move to the next video before it finishes (if you have short 
videos I don't think this is even needed, just let the videos finish)
  3. Notice that sometimes the video freezes right after starting but if you 
open the activities or Alt-Tab away and back the video has been playing and 
will resume

  I've only noticed this bug in VLC but assume it's most likely a mutter
  or gnome-shell issue so I filed it in mutter.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.3-2~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 27 09:41:40 2018
  InstallationDate: Installed on 2018-05-31 (209 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809880/+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 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Pedro]

Thank you, Ahmed Mamdouh.
After your suggestion, I update gnome-shell.
Finally, it won't be crash.
I was waitting for a long time, and can not use "workspace".
Now I can use multi workspaces again.

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell source package in Eoan:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  [ Impact ]

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  [ Test case ]

  Open Android Emulator and switch workspace
  or
  Open Skype, start a test call and switch workspace

  GNOME-Shell should not crash

  [ Regression potential ]

  Very low, we remove windows from Javascript array when they're destroyed.
  A possible regression could be not switching to workspace when selecting a 
window that is in another one.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  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-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1812527/+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 1780790]

[Pedro Côrte-Real]

I see the tooltip and context menu issue repeatedly. I'm now on a fresh
install of Ubuntu 19.04 on Wayland and running Firefox 66.0.4. So it
doesn't seem to be anything too specific to my install.

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

Title:
  Menus, tooltips and dropdowns are often misplaced on screen

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

Bug description:
  I've noticed a few problems with misplaced elements in firefox UI that
  I am not sure are all the same bug:

  - In what appears to be random chance tooltips and menus are often misplaced 
on screen. It's common but not fully reproducible. What I see is right-clicking 
an element on a page or hovering over a link and having the menu/tooltip show 
up somewhere different on the page. Doing it again immediately after often 
results in it appearing in the right place the second time.
  - When using an external screen placed on top of the internal one with 
firefox maximized on the internal screen the URL bar's dropdown would 
consistently appear on the external screen, completely outside the firefox 
window, instead of the normal location

  Let me know what extra information is needed do diagnose this. I'm
  running gnome-shell and have used both Xorg and Wayland sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 61.0+build3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr2259 F pulseaudio
  BuildID: 20180703115938
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  9 15:00:50 2018
  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 2018-05-31 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 
   10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 
   10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.203.246 metric 
600 
   169.254.0.0/16 dev tun0 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-a9ef45a0-cbbc-451a-a76b-c36ed1180623
  PrefErrors: Unexpected character ',' whilst parsing int @ 
/usr/lib/firefox/defaults/pref/vendor-gre.js:8
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=61.0/20180703115938 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1780790/+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 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Pedro]

My ubuntu 18.04 have already been updated to the latest state! 
But it still crash when I swich workspace.
Is any package I need to install to solve this bug? Or other suggestion?

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  In Progress
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell source package in Eoan:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  [ Impact ]

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  [ Test case ]

  Open Android Emulator and switch workspace
  or
  Open Skype, start a test call and switch workspace

  GNOME-Shell should not crash

  [ Regression potential ]

  Very low, we remove windows from Javascript array when they're destroyed.
  A possible regression could be not switching to workspace when selecting a 
window that is in another one.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  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-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1812527/+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 220263]

[Pedro Côrte-Real]

Here's a simple way to replicate this bug for me. In both cases I have
the Light theme selected:

$ GTK_THEME="Adwaita:dark" firefox
(firefox runs and the Find box has white text on white background)

$ GTK_THEME="Adwaita:light" firefox
(firefox runs and the Find box has the correct black text on white background)

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

Title:
  Bad Firefox integration with dark themes

Status in Mozilla Firefox:
  Fix Released
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme.
  Now I see all the input boxes and buttons filled with grey colour.
  This happened even with Firefox 2, but I solved that problem with a
  quick guide under the comment "firefox fix" by Proton at the bottom of
  this page: http://www.gnome-
  look.org/content/show.php/Grey+Neu?content=60824

  In Firefox 3 I can't correct this problem.

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

[Pedro Côrte-Real]

I seem to have e10s enabled:

Multiprocess Windows1/1 Enabled by default

and have set Adwaita:light:

widget.content.gtk-theme-override;Adwaita:light

I still get white text on white background on the Find textbox within
webpages.

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

Title:
  Bad Firefox integration with dark themes

Status in Mozilla Firefox:
  Fix Released
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme.
  Now I see all the input boxes and buttons filled with grey colour.
  This happened even with Firefox 2, but I solved that problem with a
  quick guide under the comment "firefox fix" by Proton at the bottom of
  this page: http://www.gnome-
  look.org/content/show.php/Grey+Neu?content=60824

  In Firefox 3 I can't correct this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/220263/+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 1820936] Re: When I switch workspace, gnome-shell will have a very high chance of crashing, especially running "PlayOnLinux"

[Pedro]

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

Yes, I think it is the same bug, just happen in different application.

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

Title:
  When I switch workspace, gnome-shell will have a very high chance of
  crashing, especially running "PlayOnLinux"

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I use "PlayOnLinux" to run a windows application "KakaoTalk".
  But recently, when I run the "KakaoTalk" on "PlayOnLinux", if I switch the 
workspace, gnome-shell is easy to crash, sometimes I will be log out, I need to 
log in again.
  But If "KakaoTalk" on "PlayOnLinux" not open, it just on system tray, the 
probability of occurrence is much lower.
  The bug just happen after one day I update the system.
  When I disabled animation between workspace, the probability of occurrence is 
much lower, but it still happened.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 20 09:33:59 2019
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-12-29 (445 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (217 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820936/+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 1820936] [NEW] When I switch workspace, gnome-shell will have a very high chance of crashing, especially running "PlayOnLinux"

[Pedro]

Public bug reported:

I use "PlayOnLinux" to run a windows application "KakaoTalk".
But recently, when I run the "KakaoTalk" on "PlayOnLinux", if I switch the 
workspace, gnome-shell is easy to crash, sometimes I will be log out, I need to 
log in again.
But If "KakaoTalk" on "PlayOnLinux" not open, it just on system tray, the 
probability of occurrence is much lower.
The bug just happen after one day I update the system.
When I disabled animation between workspace, the probability of occurrence is 
much lower, but it still happened.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 20 09:33:59 2019
DisplayManager: lightdm
InstallationDate: Installed on 2017-12-29 (445 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2018-08-14 (217 days ago)

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

Title:
  When I switch workspace, gnome-shell will have a very high chance of
  crashing, especially running "PlayOnLinux"

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I use "PlayOnLinux" to run a windows application "KakaoTalk".
  But recently, when I run the "KakaoTalk" on "PlayOnLinux", if I switch the 
workspace, gnome-shell is easy to crash, sometimes I will be log out, I need to 
log in again.
  But If "KakaoTalk" on "PlayOnLinux" not open, it just on system tray, the 
probability of occurrence is much lower.
  The bug just happen after one day I update the system.
  When I disabled animation between workspace, the probability of occurrence is 
much lower, but it still happened.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 20 09:33:59 2019
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-12-29 (445 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (217 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820936/+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 1820743] [NEW] Pulseaudio is sometimes broken after resume from suspend

[Pedro Côrte-Real]

Public bug reported:

Sometimes when resuming from suspend pulseaudio is broken and only the
dummy output is available. After "pulseaudio -k" audio again works.
Here's what I found in the logs:

$ journalctl --since "1 day ago" | grep pulseaudio
Mar 17 19:40:51 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 17 21:29:49 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 18 09:01:13 coulson pulseaudio[9869]: [alsa-sink-ALC293 Analog] 
alsa-sink.c: snd_pcm_mmap_begin: File descriptor in bad state
Mar 18 09:06:25 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 18 09:32:40 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 18 09:47:36 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 18 18:16:42 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.

--- Here I ran pulseaudio -k ---

Mar 18 19:08:13 coulson pulseaudio[26606]: [pulseaudio] backend-ofono.c: Failed 
to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
Mar 18 19:08:13 coulson pulseaudio[26612]: [pulseaudio] pid.c: Daemon already 
running.
Mar 18 19:08:13 coulson pulseaudio[26614]: [pulseaudio] pid.c: Daemon already 
running.
Mar 18 19:08:13 coulson pulseaudio[26616]: [pulseaudio] pid.c: Daemon already 
running.


The "Failed to create sink input" seems to happen on every resume but only some 
times does it actually break. Don't know if the ofono message is related or not.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pedrocr   26606 F pulseaudio
CurrentDesktop: GNOME
Date: Mon Mar 18 19:11:09 2019
InstallationDate: Installed on 2018-05-31 (291 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1CET66W (1.34 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FAS5TS00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460s
dmi.product.name: 20FAS5TS00
dmi.product.version: ThinkPad T460s
dmi.sys.vendor: LENOVO

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

Title:
  Pulseaudio is sometimes broken after resume from suspend

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sometimes when resuming from suspend pulseaudio is broken and only the
  dummy output is available. After "pulseaudio -k" audio again works.
  Here's what I found in the logs:

  $ journalctl --since "1 day ago" | grep pulseaudio
  Mar 17 19:40:51 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 17 21:29:49 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 18 09:01:13 coulson pulseaudio[9869]: [alsa-sink-ALC293 Analog] 
alsa-sink.c: snd_pcm_mmap_begin: File descriptor in bad state
  Mar 18 09:06:25 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 18 09:32:40 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 18 09:47:36 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 18 18:16:42 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.

  --- Here I ran pulseaudio -k ---

  Mar 18 19:08:13 coulson pulseaudio[26606]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Mar 18 19:08:13 coulson pulseaudio[26612]: [pulseaudio] pid.c: Daemon already 
running.
  Mar 18 19:08:13 coulson pulseaudio[26614]: [pulseaudio] pid.c: Daemon already 

[Desktop-packages] [Bug 220263]

[Pedro Côrte-Real]

I'm also using Ubuntu 18.04 but using the vanilla GNOME session (that
uses Wayland) with the dark Adwaita theme selected. Could you please
test with that to see if you get the same result?

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

Title:
  Bad Firefox integration with dark themes

Status in Mozilla Firefox:
  Fix Released
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme.
  Now I see all the input boxes and buttons filled with grey colour.
  This happened even with Firefox 2, but I solved that problem with a
  quick guide under the comment "firefox fix" by Proton at the bottom of
  this page: http://www.gnome-
  look.org/content/show.php/Grey+Neu?content=60824

  In Firefox 3 I can't correct this problem.

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

[Pedro Côrte-Real]

I have "Use System Colors" unchecked, `widget.content.gtk-theme-
override` set to `Adwaita` and the Light theme selected. And yet even
then the Ctrl-F input has white text over white background.

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

Title:
  Bad Firefox integration with dark themes

Status in Mozilla Firefox:
  Fix Released
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme.
  Now I see all the input boxes and buttons filled with grey colour.
  This happened even with Firefox 2, but I solved that problem with a
  quick guide under the comment "firefox fix" by Proton at the bottom of
  this page: http://www.gnome-
  look.org/content/show.php/Grey+Neu?content=60824

  In Firefox 3 I can't correct this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/220263/+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 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal

[Pedro Côrte-Real]

Hi Daniel. I can't even reproduce it in 18.04 anymore. I tried:

- Booting 18.04.2 from a usb disk
- The 18.04 GNOME Wayland session (what I'm trying now to avoid a bunch of 
other bugs)
- The 18.04 default Ubuntu Xorg session

all of them seem to be showing reasonable <1% gnome-shell CPU usage when
showing just a gnome-terminal running top. Don't know what fixed it but
it does seem fixed. I can live boot 18.10 if that's useful or even 19.04
if there are images for that already somewhere.

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

Title:
  High CPU usage by gnome-shell when only running gnome-terminal

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Even when doing nothing but displaying a terminal screen with top
  running gnome-shell uses 10% of a CPU. That seems excessive. I
  disabled all extensions to try and make the test fair. Enabling the
  system monitor extension increases the load to 13-14%. It seems that
  the gnome-shell screen painting is highly CPU consuming even if screen
  updates are infrequent (1 a second for all these cases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 29 11:38:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-27 (578 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+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 1752813] Re: Pointer speed is too slow even in the fastest setting

[Pedro Côrte-Real]

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

I'm not sure if this is a duplicate of it's actually a bug in the
underlying driver and not GNOME.

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

Title:
  Pointer speed is too slow even in the fastest setting

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

Bug description:
  I use the trackpoint on my Lenovo T460s almost exclusively. Even in
  the fastest setting on a 2560x1440 screen it is much too slow. I've
  had to add the following udev rule to get it to be usable:

  ACTION=="add",
  SUBSYSTEM=="input",
  ATTR{name}=="TPPS/2 IBM TrackPoint",
  ATTR{device/sensitivity}="190",
  ATTR{device/speed}="220",
  ATTR{device/inertia}="6",
  ATTR{device/press_to_select}="0"

  And even with this and the speed in the control center set to maximum
  it is still a bit slow. Trying to push the sensitivity/speed settings
  higher will break the trackpoint and even with these settings it seems
  that sometimes on resume from sleep the trackpoint fails. After
  cycling suspend/resume again it comes back.

  There should be a way to set much higher speed settings for the mouse.
  Current settings make trackpoints very hard to use which even carries
  risk of hand/arm injuries.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.18.2-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar  2 08:47:44 2018
  InstallationDate: Installed on 2016-10-27 (490 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1752813/+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 1752813] Re: Pointer speed is too slow even in the fastest setting

[Pedro Côrte-Real]

Another strange thing that happens is that sometimes after
suspend/resume the pointer speed is changed. Right now, using that
250/250 udev rule I was before having just enough speed at maximum
setting. Today after a suspend/resume cycle I now had to set the
trackpoint speed to around 40% to get a reasonable level. So it seems
somewhere in kernerl/libinput/mutter there is also a bug that makes the
speed inconsistent over suspend/resume.

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

Title:
  Pointer speed is too slow even in the fastest setting

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

Bug description:
  I use the trackpoint on my Lenovo T460s almost exclusively. Even in
  the fastest setting on a 2560x1440 screen it is much too slow. I've
  had to add the following udev rule to get it to be usable:

  ACTION=="add",
  SUBSYSTEM=="input",
  ATTR{name}=="TPPS/2 IBM TrackPoint",
  ATTR{device/sensitivity}="190",
  ATTR{device/speed}="220",
  ATTR{device/inertia}="6",
  ATTR{device/press_to_select}="0"

  And even with this and the speed in the control center set to maximum
  it is still a bit slow. Trying to push the sensitivity/speed settings
  higher will break the trackpoint and even with these settings it seems
  that sometimes on resume from sleep the trackpoint fails. After
  cycling suspend/resume again it comes back.

  There should be a way to set much higher speed settings for the mouse.
  Current settings make trackpoints very hard to use which even carries
  risk of hand/arm injuries.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.18.2-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar  2 08:47:44 2018
  InstallationDate: Installed on 2016-10-27 (490 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1752813/+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 1817617] [NEW] Video driver

[Pedro Henrique Freitas de Paula]

Public bug reported:

~apt-get install xserver-xorg-vt-get install xserver-xorg-video-intel
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xserver-xorg-video-intel : Depends: xorg-video-abi-23
Depends: xserver-xorg-core (>= 2:1.18.99.901)
E: Unable to correct problems, you have held broken packages.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompositorRunning: None
Date: Mon Feb 25 17:05:43 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.18, 4.18.0-15-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
InstallationDate: Installed on 2019-02-22 (2 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Dell Inc. Inspiron 3442
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0P8H6J
dmi.board.vendor: Dell Inc.
dmi.board.version: A14
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3442
dmi.product.sku: 0651
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** 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/1817617

Title:
  Video driver

Status in xorg package in Ubuntu:
  New

Bug description:
  ~apt-get install xserver-xorg-vt-get install xserver-xorg-video-intel
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Feb 25 17:05:43 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.18.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2019-02-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 3442
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Desktop-packages] [Bug 1752813] Re: Pointer speed is too slow even in the fastest setting

[Pedro Côrte-Real]

Currently the settings are just barely usable at max speed. Is there any
upstream I can coordinate with to try and get this solved? This is a
really annoying issue. Using these same laptops in Windows has a much
faster pointer.

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

Title:
  Pointer speed is too slow even in the fastest setting

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

Bug description:
  I use the trackpoint on my Lenovo T460s almost exclusively. Even in
  the fastest setting on a 2560x1440 screen it is much too slow. I've
  had to add the following udev rule to get it to be usable:

  ACTION=="add",
  SUBSYSTEM=="input",
  ATTR{name}=="TPPS/2 IBM TrackPoint",
  ATTR{device/sensitivity}="190",
  ATTR{device/speed}="220",
  ATTR{device/inertia}="6",
  ATTR{device/press_to_select}="0"

  And even with this and the speed in the control center set to maximum
  it is still a bit slow. Trying to push the sensitivity/speed settings
  higher will break the trackpoint and even with these settings it seems
  that sometimes on resume from sleep the trackpoint fails. After
  cycling suspend/resume again it comes back.

  There should be a way to set much higher speed settings for the mouse.
  Current settings make trackpoints very hard to use which even carries
  risk of hand/arm injuries.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.18.2-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar  2 08:47:44 2018
  InstallationDate: Installed on 2016-10-27 (490 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Pedro Côrte-Real]

I hit this bug today by choosing the dark Adwaita theme in Gnome 3.28
and Firefox 65.0. It's amazing that this is an 18 year old bug. I found
it surprising the system theme did anything to webpages and had two
consecutive surprises:

- First setting the system theme to Adwaita-dark changed the Firefox theme. 
That makes sense. What was surprising was that the Firefox theme then changed 
the content of the web pages. My mental model of a browser is that within the 
page view it's a different world and there's no reason for the web to look 
different to match the browser chrome or the system theme.
- Because I didn't actually like the dark version of Firefox I switched it to 
the Light theme manually (webpages are usually light colored and so dark chrome 
in browsers looks weird). And yet even after doing this pages still had dark 
buttons and input areas. That was even stranger. Now Firefox had a light theme 
and yet the webpages were still picking up broken colors from the system theme 
inconsistent with the Firefox chrome theme.

I fixed this after some web searches by setting "widget.content.gtk-
theme-override:Adwaita". That at least sets a light theme for UI
controls and is back to looking reasonable. I found that in bug #1283086
which seems to be a 3 year old duplicate of this 18 year old bug. The
proposal for removal of all native theming in #1411425 makes perfect
sense.

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

Title:
  Bad Firefox integration with dark themes

Status in Mozilla Firefox:
  Fix Released
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme.
  Now I see all the input boxes and buttons filled with grey colour.
  This happened even with Firefox 2, but I solved that problem with a
  quick guide under the comment "firefox fix" by Proton at the bottom of
  this page: http://www.gnome-
  look.org/content/show.php/Grey+Neu?content=60824

  In Firefox 3 I can't correct this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/220263/+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 1775637] Re: Screen tearing both in scrolling and videos

[Pedro Côrte-Real]

This is probably the same bug as the one I submitted against mutter:

https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1810126

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

Title:
  Screen tearing both in scrolling and videos

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Using firefox on the 18.04 default session (gnome-shell on Xorg) I get
  screen tearing when scrolling and also in videos. It's evident in this
  video for example:

  https://www.youtube.com/watch?v=9hIRq5HTh5s

  Where the lines between white and black areas seem to jump around and
  that's not visible in a screenshot.

  When scrolling it's common to see horizontal discontinuities in the
  text.

  Here's the details of my graphics card:

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) 
(prog-if 00 [VGA controller])
Subsystem: Lenovo Skylake GT2 [HD Graphics 520]
Flags: bus master, fast devsel, latency 0, IRQ 126
Memory at f000 (64-bit, non-prefetchable) [size=16M]
Memory at e000 (64-bit, prefetchable) [size=256M]
I/O ports at e000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

  I'm using a Lenovo T460s

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 60.0.1+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pedrocr1619 F...m pulseaudio
   /dev/snd/controlC0:  pedrocr1619 F pulseaudio
  BuildID: 20180517114003
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  7 15:35:20 2018
  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 2018-05-31 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 
   10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 
   10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.202.17 metric 
600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-eee55497-e2e4-4c82-a862-236a81180223
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=60.0.1/20180517114003 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-eee55497-e2e4-4c82-a862-236a81180223
   bp-db2b7d55-dbe6-47a3-b50d-e9b691171230
   bp-280d460e-d837-442d-8543-17f3c1171202
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1775637/+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 1810126] Re: Extremely visible screen tearing with VLC and Firefox/Chromium

[Pedro Côrte-Real]

This seems to at least help:

https://extensions.gnome.org/extension/1445/fix-fullscreen-tearing/

Maybe something like that should be shipped by default

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

Title:
  Extremely visible screen tearing with VLC and Firefox/Chromium

Status in mutter package in Ubuntu:
  New

Bug description:
  When watching videos in VLC on an external screen there is extremely
  visible screen tearing. But it's likely that the external screen only
  makes the problem worse as this website shows a lot of vsync issues in
  both Firefox and Chromium even with just the single screen:

  https://www.vsynctester.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.3-2~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 30 23:16:26 2018
  InstallationDate: Installed on 2018-05-31 (213 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1810126/+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 1815135] [NEW] On resume unlocked desktop with completely broken shell

[Pedro Côrte-Real]

Public bug reported:

Recently I've had gnome-shell be completely broken on resume from
suspend. The screen contents show the apps with broken positions and
missing decorations and the top bar is shown twice, once in 200% once in
100%. The screen lock is not in place so screen contents are revealed
without a password (there's a long-standing bug on this).

Switching to a terminal and killing gnome-shell doesn't make it respawn
and the system is completely broken. I haven't been able to take a
screenshot because the session is unresponsive. I wonder if it has
something to do with virt-manager running with a fullscreen VM, as I've
reported another bug where gnome-shell is broken when apps are
fullscreen.

At this point I'm planning on trying Kubuntu to see if I get a
reasonable desktop. The change to gnome-shell in 18.04 has made the
default Ubuntu desktop well below the standard for an LTS. Please let me
know if there are logs I can provide or if there is a way to take a
screenshot of a broken Xorg session from the console.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  7 20:50:22 2019
DisplayManager: gdm3
InstallationDate: Installed on 2018-05-31 (252 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  On resume unlocked desktop with completely broken shell

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Recently I've had gnome-shell be completely broken on resume from
  suspend. The screen contents show the apps with broken positions and
  missing decorations and the top bar is shown twice, once in 200% once
  in 100%. The screen lock is not in place so screen contents are
  revealed without a password (there's a long-standing bug on this).

  Switching to a terminal and killing gnome-shell doesn't make it
  respawn and the system is completely broken. I haven't been able to
  take a screenshot because the session is unresponsive. I wonder if it
  has something to do with virt-manager running with a fullscreen VM, as
  I've reported another bug where gnome-shell is broken when apps are
  fullscreen.

  At this point I'm planning on trying Kubuntu to see if I get a
  reasonable desktop. The change to gnome-shell in 18.04 has made the
  default Ubuntu desktop well below the standard for an LTS. Please let
  me know if there are logs I can provide or if there is a way to take a
  screenshot of a broken Xorg session from the console.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 20:50:22 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-05-31 (252 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  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/1815135/+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 1573728] Re: Files opened with gedit on command line no longer open within the existing gedit session

[Pedro Côrte-Real]

That will only come out with newer gnome versions, so this would only be
fixed in 20.04 if you're using LTS releases. I'm running the original
patch with no issues, so maybe it would be nice to just add that to the
current package?

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

Title:
  Files opened with gedit on command line no longer open within the
  existing gedit session

Status in gedit:
  Unknown
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  Prior to my update today to Ubuntu 16.04, I could open a file using
  gedit on the command line and it would open in the gedit window i
  already have open. After updating to 16.04 when I open a file with say
  `gedit /tmp/myleakycode.c` it opens in a new window.

  Oddly, as I was writing this bug report it's now working I expect it
  to, where opening files on the CLI adds to my existing session.

  I'll follow up if I find some pattern as to what triggers this.

  I am running Ubuntu Gnome 16.04 with the 4.4.0-21-generic kernel,
  gedit 3.18.3, terminator 0.98 to open the files.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr 22 12:54:04 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gedit
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1573728/+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 1573728] Re: Files opened with gedit on command line no longer open within the existing gedit session

[Pedro Côrte-Real]

I've ran the patch for a few months now with no issues. A new update has
now reverted that so I have to go back and reapply it. Could the patch
just be added to the ubuntu package and be done with it?

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

Title:
  Files opened with gedit on command line no longer open within the
  existing gedit session

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  Prior to my update today to Ubuntu 16.04, I could open a file using
  gedit on the command line and it would open in the gedit window i
  already have open. After updating to 16.04 when I open a file with say
  `gedit /tmp/myleakycode.c` it opens in a new window.

  Oddly, as I was writing this bug report it's now working I expect it
  to, where opening files on the CLI adds to my existing session.

  I'll follow up if I find some pattern as to what triggers this.

  I am running Ubuntu Gnome 16.04 with the 4.4.0-21-generic kernel,
  gedit 3.18.3, terminator 0.98 to open the files.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr 22 12:54:04 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gedit
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1573728/+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 1811902] Re: Echo cancelation should be enabled by default

[Pedro Côrte-Real]

Thanks for that.

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

Title:
  Echo cancelation should be enabled by default

Status in pulseaudio package in Ubuntu:
  Opinion

Bug description:
  Echo cancellation is a basic feature for anything where you are using
  a video or audio conference. According to instructions like these:

  https://bugs.launchpad.net/elementaryos/+bug/1682253
  
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation
  
https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb

  There is now enough support in pulseaudio to do this well, but it's
  just not enabled by default. Users shouldn't need to fish around for
  strange things to add to config files. More complete defaults should
  be included.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pedrocr2684 F...m pulseaudio
   /dev/snd/controlC0:  pedrocr2684 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 23:45:10 2019
  InstallationDate: Installed on 2018-05-31 (229 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+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 1811902] Re: Echo cancelation should be enabled by default

[Pedro Côrte-Real]

I don't agree that it's just a Firefox issue. There should be a simple
way to enable this in the normal sound UI, at least as default for
everything and ideally per-app.

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

Title:
  Echo cancelation should be enabled by default

Status in pulseaudio package in Ubuntu:
  Opinion

Bug description:
  Echo cancellation is a basic feature for anything where you are using
  a video or audio conference. According to instructions like these:

  https://bugs.launchpad.net/elementaryos/+bug/1682253
  
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation
  
https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb

  There is now enough support in pulseaudio to do this well, but it's
  just not enabled by default. Users shouldn't need to fish around for
  strange things to add to config files. More complete defaults should
  be included.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pedrocr2684 F...m pulseaudio
   /dev/snd/controlC0:  pedrocr2684 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 23:45:10 2019
  InstallationDate: Installed on 2018-05-31 (229 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+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 1811902] Re: Echo cancelation should be enabled by default

[Pedro Côrte-Real]

I agree with your point so won't be opening a bug to change the
defaults. But it should be easy to enable somewhere in the GUI sound
settings at least for specific applications. Video conferencing like
appear.in is only really usable with headphones because of this.
Adjusting text config files is not a good user experience. And I suspect
most people only care about the microphone because of these kinds of
uses.

According to this:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/196

It's possible for apps to request echo cancelation with 'filter.want
=echo-cancel' so maybe this is actually a bug in firefox?

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

Title:
  Echo cancelation should be enabled by default

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Echo cancellation is a basic feature for anything where you are using
  a video or audio conference. According to instructions like these:

  https://bugs.launchpad.net/elementaryos/+bug/1682253
  
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation
  
https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb

  There is now enough support in pulseaudio to do this well, but it's
  just not enabled by default. Users shouldn't need to fish around for
  strange things to add to config files. More complete defaults should
  be included.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pedrocr2684 F...m pulseaudio
   /dev/snd/controlC0:  pedrocr2684 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 23:45:10 2019
  InstallationDate: Installed on 2018-05-31 (229 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+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 1811902] [NEW] Echo cancelation should be enabled by default

[Pedro Côrte-Real]

Public bug reported:

Echo cancellation is a basic feature for anything where you are using a
video or audio conference. According to instructions like these:

https://bugs.launchpad.net/elementaryos/+bug/1682253
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation
https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb

There is now enough support in pulseaudio to do this well, but it's just
not enabled by default. Users shouldn't need to fish around for strange
things to add to config files. More complete defaults should be
included.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   pedrocr2684 F...m pulseaudio
 /dev/snd/controlC0:  pedrocr2684 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 15 23:45:10 2019
InstallationDate: Installed on 2018-05-31 (229 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1CET66W (1.34 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FAS5TS00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460s
dmi.product.name: 20FAS5TS00
dmi.product.version: ThinkPad T460s
dmi.sys.vendor: LENOVO

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

Title:
  Echo cancelation should be enabled by default

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Echo cancellation is a basic feature for anything where you are using
  a video or audio conference. According to instructions like these:

  https://bugs.launchpad.net/elementaryos/+bug/1682253
  
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation
  
https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb

  There is now enough support in pulseaudio to do this well, but it's
  just not enabled by default. Users shouldn't need to fish around for
  strange things to add to config files. More complete defaults should
  be included.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pedrocr2684 F...m pulseaudio
   /dev/snd/controlC0:  pedrocr2684 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 23:45:10 2019
  InstallationDate: Installed on 2018-05-31 (229 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+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 1810126] [NEW] Extremely visible screen tearing with VLC and Firefox/Chromium

[Pedro Côrte-Real]

Public bug reported:

When watching videos in VLC on an external screen there is extremely
visible screen tearing. But it's likely that the external screen only
makes the problem worse as this website shows a lot of vsync issues in
both Firefox and Chromium even with just the single screen:

https://www.vsynctester.com/

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mutter 3.28.3-2~ubuntu18.04.2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 30 23:16:26 2018
InstallationDate: Installed on 2018-05-31 (213 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Extremely visible screen tearing with VLC and Firefox/Chromium

Status in mutter package in Ubuntu:
  New

Bug description:
  When watching videos in VLC on an external screen there is extremely
  visible screen tearing. But it's likely that the external screen only
  makes the problem worse as this website shows a lot of vsync issues in
  both Firefox and Chromium even with just the single screen:

  https://www.vsynctester.com/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.3-2~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 30 23:16:26 2018
  InstallationDate: Installed on 2018-05-31 (213 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1810126/+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 1809880] [NEW] Fullscreen vlc sometimes freezes until you Alt-Tab away and back from the window

[Pedro Côrte-Real]

Public bug reported:

There seems to be a bug, which I assume is in mutter, when viewing
multiple vlc videos fullscreen. The steps to reproduce are simple:

1. Open a bunch of videos in vlc in sequence with something like "vlc *" in a 
directory full of video files
2. Press N to move to the next video before it finishes (if you have short 
videos I don't think this is even needed, just let the videos finish)
3. Notice that sometimes the video freezes right after starting but if you open 
the activities or Alt-Tab away and back the video has been playing and will 
resume

I've only noticed this bug in VLC but assume it's most likely a mutter
or gnome-shell issue so I filed it in mutter.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mutter 3.28.3-2~ubuntu18.04.2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 27 09:41:40 2018
InstallationDate: Installed on 2018-05-31 (209 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Fullscreen vlc sometimes freezes until you Alt-Tab away and back from
  the window

Status in mutter package in Ubuntu:
  New

Bug description:
  There seems to be a bug, which I assume is in mutter, when viewing
  multiple vlc videos fullscreen. The steps to reproduce are simple:

  1. Open a bunch of videos in vlc in sequence with something like "vlc *" in a 
directory full of video files
  2. Press N to move to the next video before it finishes (if you have short 
videos I don't think this is even needed, just let the videos finish)
  3. Notice that sometimes the video freezes right after starting but if you 
open the activities or Alt-Tab away and back the video has been playing and 
will resume

  I've only noticed this bug in VLC but assume it's most likely a mutter
  or gnome-shell issue so I filed it in mutter.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.3-2~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 27 09:41:40 2018
  InstallationDate: Installed on 2018-05-31 (209 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809880/+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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Pedro]

After read your mail, I installed gnome-shell from bionic-proposed and 
also the problem is gone, after restarting.
Thankyou very much for your time

El 12/12/18 a las 15:54, Olivier Tilloy escribió:
> I installed gnome-shell 3.28.3-0ubuntu0.18.04.4 from bionic-proposed in
> a fully up-to-date bionic VM (amd64) and verified that after restarting
> the shell (Alt+F2, r), the problem with password fields in firefox is
> gone.
>
> I used the instructions in duplicate bug #1795169 for testing, as they
> don't involve installing an extension, and test case #2 in this bug
> report (which involves reddit login page) doesn't exhibit the problem
> any longer.
>
> ** Tags removed: verification-needed-bionic
> ** Tags added: verification-done-bionic
>
>

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  In Progress
Status in ibus source package in Cosmic:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/391

  ---

  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean
  users are simply unable to fill in password fields that previously
  were working fine. (see "ACTUAL RESULTS" below)

  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
    (click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).

  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  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: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  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/1765304/+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 1795279] Re: Slack and possibly other Electron snap apps crash under Wayland

[João Pedro Figueiredo Martins]

Same thing happens for me. Ubuntu 18.04 on Wayland. It also happens with
the Vscode snap.

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

Title:
  18.10 Wayland session closes when using Slack and possibly other
  Electron snap app

Status in snapd:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,
  it seems that whenever I launch Slack snap app (doesn't apply to the Debian 
packaged app) under Wayland the whole desktop crashes - applies to Ubuntu 18.10 
- updated to on 30 September 2018.

  To reproduce this, launch Slack snap app (or possibly any other
  Electron snap app, not sure about that though) under Wayland and after
  a moment the whole desktop crashes => user re-appears on the login
  screen.

  If launched under X11 Slack launches normally.

  I've already reported this to the Slack team themselves in April 2018
  but soon after that wrote another message informing about this being
  fixed - possibly close to the final release of 18.04. Now on Ubuntu
  18.10 this has reappeared again. However, it may possibly be broken
  under 18.04 as well now - I haven't tested it for a while.

  Best regards,
  Martin

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1795279/+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 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

[José Pedro Saraiva]

Fix for cinnamon in case someone is interested:
https://github.com/linuxmint/Cinnamon/commit/3e366ce3f5cfe118ae1ab594bf2ce8c7872d8b4d

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+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 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

[José Pedro Saraiva]

Unreal, 3 years later and this is still a thing.
It's not even an issue exclusive to ubuntu, it's present in most, if not all, 
linux distros and then we wonder why people have switched to OSX.

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+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 1780790] Re: Menus, tooltips and dropdowns are often misplaced on screen

[Pedro Côrte-Real]

Bug submitted here:

https://bugzilla.mozilla.org/show_bug.cgi?id=1499336

I searched the related bugs and while there are a bunch of positioning
bugs none seemed to be this one. The firefox subreddit only turned up
one other person with a vaguely similar issue:

https://www.reddit.com/r/firefox/comments/91kf3n/tooltips_and_context_menus_out_of_place/

** Bug watch added: Mozilla Bugzilla #1499336
   https://bugzilla.mozilla.org/show_bug.cgi?id=1499336

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

Title:
  Menus, tooltips and dropdowns are often misplaced on screen

Status in firefox package in Ubuntu:
  New

Bug description:
  I've noticed a few problems with misplaced elements in firefox UI that
  I am not sure are all the same bug:

  - In what appears to be random chance tooltips and menus are often misplaced 
on screen. It's common but not fully reproducible. What I see is right-clicking 
an element on a page or hovering over a link and having the menu/tooltip show 
up somewhere different on the page. Doing it again immediately after often 
results in it appearing in the right place the second time.
  - When using an external screen placed on top of the internal one with 
firefox maximized on the internal screen the URL bar's dropdown would 
consistently appear on the external screen, completely outside the firefox 
window, instead of the normal location

  Let me know what extra information is needed do diagnose this. I'm
  running gnome-shell and have used both Xorg and Wayland sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 61.0+build3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr2259 F pulseaudio
  BuildID: 20180703115938
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  9 15:00:50 2018
  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 2018-05-31 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 
   10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 
   10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.203.246 metric 
600 
   169.254.0.0/16 dev tun0 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-a9ef45a0-cbbc-451a-a76b-c36ed1180623
  PrefErrors: Unexpected character ',' whilst parsing int @ 
/usr/lib/firefox/defaults/pref/vendor-gre.js:8
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=61.0/20180703115938 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/+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 1780790] Re: Menus, tooltips and dropdowns are often misplaced on screen

[Pedro Côrte-Real]

I haven't been able to replicate it in a Unity session but I can't
replicate this at will in gnome-shell either so it's hard to confirm
it's a gnome-shell issue. I wouldn't be surprised though as it's been
extremely buggy so far.

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

Title:
  Menus, tooltips and dropdowns are often misplaced on screen

Status in firefox package in Ubuntu:
  New

Bug description:
  I've noticed a few problems with misplaced elements in firefox UI that
  I am not sure are all the same bug:

  - In what appears to be random chance tooltips and menus are often misplaced 
on screen. It's common but not fully reproducible. What I see is right-clicking 
an element on a page or hovering over a link and having the menu/tooltip show 
up somewhere different on the page. Doing it again immediately after often 
results in it appearing in the right place the second time.
  - When using an external screen placed on top of the internal one with 
firefox maximized on the internal screen the URL bar's dropdown would 
consistently appear on the external screen, completely outside the firefox 
window, instead of the normal location

  Let me know what extra information is needed do diagnose this. I'm
  running gnome-shell and have used both Xorg and Wayland sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 61.0+build3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr2259 F pulseaudio
  BuildID: 20180703115938
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  9 15:00:50 2018
  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 2018-05-31 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 
   10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 
   10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.203.246 metric 
600 
   169.254.0.0/16 dev tun0 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-a9ef45a0-cbbc-451a-a76b-c36ed1180623
  PrefErrors: Unexpected character ',' whilst parsing int @ 
/usr/lib/firefox/defaults/pref/vendor-gre.js:8
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=61.0/20180703115938 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/+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 1774177] Re: Personal scaling settings not used on the unlock screen

[Pedro Côrte-Real]

This bug doesn't exist on Wayland. It does seem like GNOME developers
don't care about Xorg anymore and these kinds of bugs won't get fixed.

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

Title:
  Personal scaling settings not used on the unlock screen

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/331

  ---

  I run my screen on 100% scaling even though the ubuntu default for my
  2560x1440 screen is 200%. After resume from suspend it's common for
  GDM to display at 200% and only after switch back to 100%. Sometimes
  this extends to after unlock with the mouse cursor being double size
  but only when hovering over the gnome shell top bar. I tried taking a
  screenshot but running the screenshot app fixed it and the cursor was
  normal sized again.

  I've now submitted or subscribed to several gnome-shell and gdm3 bugs.
  The 18.04 transition from unity to gnome-shell was clearly a step back
  in terms of polish of the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 13:21:49 2018
  InstallationDate: Installed on 2016-10-27 (579 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774177/+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 1774177] Re: Personal scaling settings not used on the unlock screen

[Pedro Côrte-Real]

This happens to me 100% of the time now and is extremely annoying.
Issues like this have made the 18.04 GNOME transition a clear step back
in desktop polish.

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

Title:
  Personal scaling settings not used on the unlock screen

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/331

  ---

  I run my screen on 100% scaling even though the ubuntu default for my
  2560x1440 screen is 200%. After resume from suspend it's common for
  GDM to display at 200% and only after switch back to 100%. Sometimes
  this extends to after unlock with the mouse cursor being double size
  but only when hovering over the gnome shell top bar. I tried taking a
  screenshot but running the screenshot app fixed it and the cursor was
  normal sized again.

  I've now submitted or subscribed to several gnome-shell and gdm3 bugs.
  The 18.04 transition from unity to gnome-shell was clearly a step back
  in terms of polish of the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 13:21:49 2018
  InstallationDate: Installed on 2016-10-27 (579 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774177/+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 1780790] Re: Menus, tooltips and dropdowns are often misplaced on screen

[Pedro Côrte-Real]

This is an extremely annoying bug which creates quite a lot of lack of
polish of the desktop. Should I be submitting it upstream or something?

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

Title:
  Menus, tooltips and dropdowns are often misplaced on screen

Status in firefox package in Ubuntu:
  New

Bug description:
  I've noticed a few problems with misplaced elements in firefox UI that
  I am not sure are all the same bug:

  - In what appears to be random chance tooltips and menus are often misplaced 
on screen. It's common but not fully reproducible. What I see is right-clicking 
an element on a page or hovering over a link and having the menu/tooltip show 
up somewhere different on the page. Doing it again immediately after often 
results in it appearing in the right place the second time.
  - When using an external screen placed on top of the internal one with 
firefox maximized on the internal screen the URL bar's dropdown would 
consistently appear on the external screen, completely outside the firefox 
window, instead of the normal location

  Let me know what extra information is needed do diagnose this. I'm
  running gnome-shell and have used both Xorg and Wayland sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 61.0+build3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr2259 F pulseaudio
  BuildID: 20180703115938
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  9 15:00:50 2018
  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 2018-05-31 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 
   10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 
   10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.203.246 metric 
600 
   169.254.0.0/16 dev tun0 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-a9ef45a0-cbbc-451a-a76b-c36ed1180623
  PrefErrors: Unexpected character ',' whilst parsing int @ 
/usr/lib/firefox/defaults/pref/vendor-gre.js:8
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=61.0/20180703115938 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/+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 1795169] Re: Focus switches constantly between username and password fields

[Pedro]

thanks for your time

best regards


El 01/10/18 a las 10:54, Olivier Tilloy escribió:
> I installed firefox 62.0+build2-0ubuntu1 in a cosmic VM (it's in cosmic-
> proposed) and I cannot reproduce the issue there, so it appears to be
> 18.04-specific.
>
> ** Also affects: firefox (Ubuntu Bionic)
> Importance: Undecided
> Status: New
>
> ** Changed in: firefox (Ubuntu Bionic)
> Status: New => Confirmed
>
> ** Changed in: firefox (Ubuntu)
> Status: Confirmed => Invalid
>

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

Title:
  Focus switches constantly between username and password fields

Status in firefox package in Ubuntu:
  Invalid
Status in firefox source package in Bionic:
  Confirmed

Bug description:
  https://www.bbva.es/particulares/index.jsp

  If you click on "Entrar"(Log in) the pop-up window that opens allows you to 
enter a username when you click in "usuario"(user) but when you click on "clave 
de acceso"(password) the selection cursor changes continuously between "user" 
and " password ", preventing the introduction of the password.
  Ubuntu 16.04 with firefox 62.0 work fine, when update to ubuntu 18.04.1 LTS 
with firefox 62.0 fail.
  The 18.04 with Chromium 69.0.3497.81, also works well.
  I have the same problem in two computers.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  firefox:
Instalados: 62.0+build2-0ubuntu0.18.04.5
Candidato:  62.0+build2-0ubuntu0.18.04.5
Tabla de versión:
   *** 62.0+build2-0ubuntu0.18.04.5 500
  500 http://es.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   59.0.2+build1-0ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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